Client Management Suite

Hello!

We are currently testing out altiris 8.0 as we use 6.9 currently.  I'm curious on how methods of achieving autonaming may have changed since 6.9.

Currently I have the image setup to: deploy the image, run driver injection, run a script that tokenizes the unattend file's <computername > entry with %NAME% (altiris console display name). Then starts first boot.

I also have console display name sync with hostname turned off.  This is turned off because a PC we need to rename, the computer will grab the old hostname instead of a new name during the image process if the PC is told to reimage while currently turned on. Turning off this sync allows us to change the console display name and have the PC grab that new name instead, super handy!

So with 8.0, do we still need to run the following or is there a better way now?  Because 8.0 integrates, from my understanding, with AD now, I'm assuming this puts a stop to us changing the console display name?

REM Tokenize Unattend File for Specialization Phase

REM ReplaceTokens .\Sysprep4\x64\unattend.xml .\Temp\%ID%.txt

 

REM Copy Unattend File for Specialization Phase

copy .\Temp\%ID%.txt D:\Windows\Panther\unattend.xml /Y

xcopy ".\Drivers\Win7HWII\Scripts x64" "D:\Windows\Setup\Scripts" /s /e /i /h /y /q

The biggest thing for me is automation.  Once I deploy an imaging job, I do not want to have to touch that PC again to finish up any processes, such as naming or joining to the domain.  I prefer it all to happen in the unattend file so when reimaging, the computer gets placed in the same OU in AD without any movement from the tech/admin.

Thank you!

I was told by MS that the computername in the unattend.xml file used in win7 has been deprecated.  You can no longer change the computer name with unattend.xml just let it autogenerate a name and rename post imaging. This is tough b/c we used to have a VB script pop-up so the tech could enter a machine name and it replaced a token in the unattend.xml file during the imaging process (right after ghost, before reboot to production).  we opened a MS case b/c this is no longer working on win10 machines

https://msdn.microsoft.com/en-us/library/windows/hardware/dn922649%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396