Using WSNAME as a postinstall task
Hi,
I'm trying to change a computername after imaging as a postinstall task using wsname.
What i did was make a namedb.dat with all the computernames and corresponding MAC-addresses we currently have.
We want to use it this way, as we are currently in the process of migrating to Windows 7 and some applications rely on the computername to give access elsewhere.
I've name a namechange postinstall job (for running in windows) and uploaded the namedb.dat in there.
The settings i used in the job are these:
wsname.exe /RDF:namedb.dat /DFK:$MAC /EXCLUDEADAPTERS[WIRELESS WIFI WLAN BLUETOOTH PPP VMWARE IPSEC CENTRINO] /RCID /USER:MyDomain\Username /passm:H#54F2C8E5A771F6AB4527 /DELETEEXISTING /REBOOT /ADR
The image we're using finishes with a bogus name and in a workgroup.
When I test it locally, it seems to work ok, doing the namechange and rebooting, but as a postinstall task, it doesn't work.
I also tried to set it up as a scripting job, but although it copies everything, it doesn't work.
Does anyone know where i went wrong?
Answers (5)
Does the task force the reboot? I notice you have that option but was wondering if it actually is performing the reboot as it will be necessary to do a reboot for the name to apply. You can also create a bat script to do a reboot as well.
OK seems the issue is with the RunOnce Task. I can duplicate it at will. When I do a scripted with the RunOnceTask in the Run Mid-Level Tasks section my wsname task DOES NOT RUN.
When I take the RunOnceTask out the Run Mid-Level Tasks, my wsname task does run. Still doing some investigating. I like the RunOnceTask and would like to use it.
Are you using the Naming Rule task that is created through the PostInstall Tasks tab? If not, I would go ahead and use that task as your naming task. Then as mentioned here, I would include the reboot as a separate task. I like including Reboots as separate tasks, as then it is easier to not only troubleshoot, but it is clearer what is going on when you look at your deployments. When making a separate Reboot task, I would add the Windows 7 Task Converter, so your deployments can continue post reboot. You can find that info here:
http://www.kace.com/support/resources/kb/article/K2000-postinstall-task-converter
A reboot task is discussed there as well. Good Luck!
Comments:
-
Thanks. I also tried putting it in the image and then running several reboots for each task. Although it works from scratch, it didn't work (the domain-join didn't, the name change did) properly, which is kinda strange. - dmace 11 years ago
I am having the same issue. About to drive me crazy. This is with Windows 7 scripted install. My XP scripted install work fine. I copy some files down as a midlevel task, like $oem folder and wsname run fine.
But my newer Windows 7 scripted install does not seem to run wsname properly. I am running wsname first thing then have a reboot. I am using wsname.exe /RDF:namedb.dat /DFK:$MAC /EXCLUDEADAPTERS[WIRELESS WIFI WLAN BLUETOOTH PPP VMWARE IPSEC CENTRINO].
After the install completes, I can run my wsname script manual it it work fine. Since my computer is now part of the domain I have to run
wsname.exe /RDF:MAC2name.txt /DFK:$MAC /EXCLUDEADAPTERS[WIRELESS WIFI WLAN BLUETOOTH PPP VMWARE IPSEC CENTRINO] /RCID /USER:domain\user /pass:XXXXXXX /DELETEEXISTING /REBOOT /ADR. THIS WORKS FINE. Not sure why this is not renameing.
I have a joind domain script at the end wich work great.
Comments:
-
So, it does seem to be an issue with RunnceTask. Looks like the first item in the Postinstallation Tasks list does not run. I had my WSname task first, when I moved it down to second in the list it would run. Looks like It will put some kind of bogus entry in the #1 spot since it does not want to run the first item. - mike.henderson 11 years ago
