Also, if running Ethernet check
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP", "HostName", "REG_SZ".

and

"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNetSup", "ComputerName", "REG_SZ"

to synchronize system name with DNS values.

You may need to explore any possible issues with locally shared drives and/or printers before implementing. Perhaps someone who has implemented can provide further guidance.

Bill

You can use a check file to get around this - if changed once for this user, do not change again - but how do you manage that the user is properly logging into the workstation that should reflect their name when you first install your script?

The INI file you mention will be useful as long as users only log onto 1 machine in the domain. But any duplicate entries will need to be investigated further.

Be interested in seeing your code when completed.

Bill

See also topic
http://kixtart.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=1&t=002151
Greetings.

This is the last step that I have to do and don't want to visit each workstation.

[Workstations]
WKSTA001=0
WKSTA002=0
WKSTA003=0
WKSTA004=0

The script should first check if it's name has been changed yet. It should check HKLM\Software\YourCompany'sName\NameChangeScript and whatever value. Something like "Changed" should be equal to 1. If it is, then the script quits, otherwise, it runs thought the INI file with READPROFILESTRING until it finds an entry with a 0. It should instantly update that entry to 1, and then save the name in the registry. Then it should go about the procedure of changing the machine name, and finally update its registry indicating that its name has indeed been changed via script.
-Steve O

Perhaps you use a message box asking the end-user if logged into their pc or someone elses, and depend upon end-users to help out here. If user responds 'Yes', begin rename process and write check file at end. If 'No,' bypass and perhaps send admin alert.

Have a check file named <userid.txt> so end-user can not update more than one machine. Include old name, MAC and IP address, date/time etc. Then, watch rename process over a few days, contact users logging into the machines that do not get properly updated (info in the DC security event log).

Can also check board for process to limit user login to single machine at a time to help control multiple logins during this name change.

Not the most elegant method, but will take care of the vast majority of your systems and leave you with only a few troublesome ones to correct.

Bill