Forgive me, maybe it's too early on Monday, but I'm not sure how that helps me?

The source file is fine, it's getting the accents into SQL Server that's problematic.

Add a column named IgnoreThisRow, and set it to true for empty rows, false for real rows.

Interesting: the prod (and problematic) SQL box is bound to what is, according to our network admin, the PDC for AD; I was forcing AD replication from it to the...

I should have mentioned again that our users are in AD groups, and it's the groups that have logins.

And again, not all members within the same group experienced difficulties, only...

Hi Julian,

Our situation was a little different.

Before we embarked on the renaming method for converting accounts, we had planned to clone the accounts -- creating new ones as copies of...

Next!

Well I can confirm the SIDs before and after a rename are identical.

I think I can also say that SIDhistory is not part of the problem. I found an app,...

I will do that before and after psgestid.

I read just enough about the messing with SIDHistory yesterday to put the fear of the almighty into me -- get it wrong...

Here's a link to the MS site. That bit about retaining properties I quoted also appears elsewhere on the site.

https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/lsm_rename_user.mspx?mfr=true

We're going to mass-update the rest of that group tonight, bounce...

I mentioned the login thing by way of illustrating the persistence of the oldnames.

I don't want logins for individuals at all; they should have access by way of their group...

Ah sorry, posted answer in other forum...

The OS reboot solved everything, the SQL service reboot changed nothing.

-----

Renamed 3 more accounts today.

Last week, netguys created copies of 2 of them...

Full reboot to the rescue! Bouncing SQL services was not enough.

Beginning to suspect this was caused by the cacheing of access tokens at the AD level, since the re-boot also...

Note that everything works fine on all our other SQL Servers. Just not the one to which they really need to connect...

Yesterday, I renamed 3 AD accounts. Every field that showed the old name now shows the new name.

But SQL Server won't permit them to login,

EXECUTE AS Login = NewName

Msg...

If we can't resolve this today, I'll do that tonight and see what happens.