Deployment Solution

Greetings

Just spun up a new reference VM to capture an image of Win10, fully updated with the anniversary update.

Upon deploying the image I find that my configuration task is not renaming the machine after imaging. The task joins the domain, but keeps the name of the captured reference VM, even though "leave existing" is listed under the name field in the configuration task. Same task works fine on Win7.

Anybody know why this would happen? Something finiky with the new Win10 build?

8.0HF1

Thank you much.

T

I had this problem with the pre 1511 build using sysprep and unattend.xml to rename the PC, I did see mention it might have been a bug in the earlier build of Windows. C:\windows\debug\NetSetup.log shows what's going on during sysprep and may help.

Aha! Ok...

So the posts from 8/15 are from the initial configuration of the reference machine. At some point on 8/22 I captured the image and deployed it to MV-S152-02373, but the imaged machine is still named MVSMPDEV-002 even though this file says its being named MV-S152-02373...

Any help would be appreciated. Thanks.

TE

08/15/2016 17:26:25:335 -----------------------------------------------------------------
08/15/2016 17:26:25:335 NetpValidateName: checking to see if 'MVSMPDEV-002' is valid as type 1 name
08/15/2016 17:26:25:350 NetpCheckNetBiosNameNotInUse for 'MVSMPDEV-002' [MACHINE] returned 0x0
08/15/2016 17:26:25:350 NetpValidateName: name 'MVSMPDEV-002' is valid for type 1
08/15/2016 17:26:25:366 -----------------------------------------------------------------
08/15/2016 17:26:25:366 NetpValidateName: checking to see if 'MVSMPDEV-002' is valid as type 5 name
08/15/2016 17:26:25:366 NetpValidateName: name 'MVSMPDEV-002' is valid for type 5
08/22/2016 17:00:43:207 -----------------------------------------------------------------
08/22/2016 17:00:43:207 NetpValidateName: checking to see if 'MV-S152-02373' is valid as type 1 name
08/22/2016 17:00:43:222 NetpCheckNetBiosNameNotInUse for 'MV-S152-02373' [MACHINE] returned 0x0
08/22/2016 17:00:43:222 NetpValidateName: name 'MV-S152-02373' is valid for type 1
08/22/2016 17:00:43:238 -----------------------------------------------------------------
08/22/2016 17:00:43:238 NetpValidateName: checking to see if 'MV-S152-02373' is valid as type 5 name
08/22/2016 17:00:43:238 NetpValidateName: name 'MV-S152-02373' is valid for type 5
 

Maybe try to rename the computer using the Command Line:

WMIC ComputerSystem where Name="MVSMPDEV-002" call Rename MV-S152-02373

Or powershell:

Rename-Computer -NewName MV-S152-02373 -Restart

But it looks like ITMS is doing it's thing correctly & there's a bug in the new Win 10 release.

Haha. I suppose I could use WMIC, but I don't want to have to script that for every computer i deploy the image to...

Grrr...

Any chance upgrading to HF2 and deploying WinPE10 could help some??? That would supply the newest version of sysprep if i'm not mistaken...

It was more as a troubleshooting step.

I don't think WinPE10 will help, if it's a separate configuration task you're using then sysprep isn't involved and WinPE10 wouldn't upgrade the sysprep.exe used in the running image anyway.

Interesting. WMIC did not work, even though it came back as sucsesfull... Powershell did work...  

And presumably WMIC works on older builds, looks like a Windows 10 upgrade feature.

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

Thank you for that information Mhendel05. Thats good to know. 

I also found these articles that indicate that Win10 has problems syspreping when removing windows store apps or running updates. I feel like microsoft is trying to anoy their customers...

https://support.microsoft.com/en-us/kb/2769827

https://support.symantec.com/en_US/article.HOWTO54706.html

Got my image working following these steps: https://support.symantec.com/en_US/article.TECH223595.html

However, what that document does Not indicate is your prepare for image capture task has a field for admin username and password, which is required for windows 10. I had entered the built in administrator account in this, not realizing that Sysprep disabled the account... Changing the account to a separate account allowed the image to pull, and sysprep name it correctly when deploying.