Re: Name reference invalid

Thanks for your reply Ace. I'm still somewhat stumpted as to what happened,
and the lack of information on the net regarding this error does not help.

The script shouldn't have been anything overcomplex, I was using AD Modify
which, while not officially supported, is pretty well known and stable. The
attribute itself was the Description field, common to W2K and W2K3 and hardly
rocket science. Indeed, the field got changed just like it was supposed to.

Also, the accounts themselves work just fine in every other aspect apart
from the copy (clone) operation. Examining the account attributes in ADSI
EDit does not throw up a problem that I can detect.

I'm open to any other ideas out there as to what might have gone wrong?
Also, what error_ds_name_reference_invalid actually means? Right now all I
get is an 'explanation' that just tells me that the name reference is
invalid. What name, what reference and what is invalid, that's what I'd like
to know!

"Ace Fekay [MVP Direcrtory Services]" wrote:

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

.

Relevant Pages

  • Re: Deploying user list to workgroup
    ... If you put all the old users in a text file, one username per line, I could ... modify the script to remove the accounts. ...
    (microsoft.public.win2000.general)
  • Modifying DACL
    ... script which can modify the DACL for an given file - but I ... ' Obtain the trustee for each access control entry (ACE) ... For each wmiAce in DACL ...
    (microsoft.public.win2000.security)
  • Re: Last Logon Time Stamp
    ... > I am new to script. ... > I need to list out inactive accounts more than 90 days in both AD accounts ... Use ADO to retrieve lastLogonTimeStamp for all users. ... And here is a sample program that retrieves the distinguishedName for all ...
    (microsoft.public.windows.server.scripting)
  • Re: Script to delete computer accounts not working
    ... thanks for the initial script as well. ... computer accounts that are disabled and haven't been modified for 30 days. ... Set objCommand = CreateObject ...
    (microsoft.public.scripting.vbscript)
  • Re: Running a script against an OU
    ... Do I need to place a forward slash between Computer and Accounts? ... run the script against an OU called lab1? ... the WinNT provider is blind to OU's, so you must use the LDAP provider to ... bind to the OU. ...
    (microsoft.public.scripting.vbscript)