Re: Name reference invalid

In news:D95F078F-DBEF-43F7-BEF7-696A60EC6C45@xxxxxxxxxxxxx,
Peter Lillington <NospamTemp014@xxxxxxxxxxxxx> requesting assistance, typed the following:
Answers to your questions inline below:

Thanks,

Peter

PS As an update - It appears the only accounts affected were those I
targeted with AD Modify .NET (v2), bulk changing the description
field to read (say) "newtext %'description'" - so for example
changing a description of "oldtext" to read "newtext oldtext". Other
accounts without a preexisting description were modified with AD
Modify and do not exhibit this behaviour. In another word, bizarre!


Peter, thanks for posting the info you were able to post.

Apparently and assumingly the ipconfigs are clean, which is ok to assume at this point, it may certaintly have something to do with the way the script wrote the data to the user's attributes.

As for the KCC errors, I assume the DCs will be put back up on the network? If not under 60 days, you may as well remove them.

Possibly some of the scripting gurus can help here, such as Joe Kaplan or Joe Richards. Unfortunately I can't see why it would fail to clone them unless the RID Master is not available to this specific DC that it is not working on, or something in the attribute it does not like, possibly such as that it may be a later attribute available on a 2003 Schema or method that is not available or capable on 2000.

Ace

.