Windows 10 unattend answer file for use with WDS 2012 R2

[Badaz52]

Hi,

 

I am trying to create an unattend answer file for use with WDS 2012 R2 that will answer some wizard steps and connect the windows 10 client to the domain using the name specified when it was approved in WDS for deployment.

 

We managed to do this for Windows 7 and it works perfectly, the answer file works OK for Windows 10 too but it just doesn't add the client to the domain, it puts it in a workgroup with the same name as the domain we specified and it doesn't re-use the machines name as specified earlier either.

 

Any ideas on how to do this? I tried to use SIM using the WIM file off the Windows 10 DVD but I couldn't find any shell components for naming or adding to a domain like I could with Windows 7.

 

Am I missing something obvious here?

 

Any help would be appreciated

 

Thanks guys.

[dapaulio]

Just registering my interest in this thread as I am building my 10 image and may hit this stumbling block when I get to it.

[Michael]

What I wrote here may give you some clues why Sysprep isn't working as expected.

[Badaz52]

I have managed to get it to join to the domain by using the secure join method in the unattend.xml file.

 

The problem with this is, I name and approve in WDS 2012 R2 as "Win10test", the machine then gets joined to the domain as "Desktop-randomcharacters" but it appears in AD as "Win-randomcharacters", Win10test is still present in AD but has not been used to form any part of the domain membership and is now a redundant entry and has to be removed.

 

With our Windows 7 unattend.xml we just did a unsecure join and set the computer name to %machinename% and it used the same name specified in name and approve in WDS 2012 R2 which is what I want to do with windows 10 but I'm starting to think it isn't possible with windows 10?

[Michael]

I don't think you can use the %machinename% option anymore, but rather let the Sysprep process generate a system name on the prefix and a random string of letters/numbers, whilst putting it in the correct location within AD.

[Badaz52]

So my best bet would be to follow your guide, approve in WDS 2012 R2 rather than name and approve let it generate a name such as "school-random" and then just rename after it has imaged?

[sted]

or use mdt and name it at install time

[Badaz52]

Could you send me a copy of your unattend files so I can have a look?

[Michael]

It really depends on your requirements, but if you specify a prefix (such as your school initials and a hyphen) XYZ- in the Registered Organisation, it'll generate a random string after it. Much quicker than specifying the name manually or from a predetermined list.

 

As part of the Sysprep process you can also specify your OU structure, so GPOs are applied immediately, rather than just a big long list appearing within Computers where you can't link any GPOs.

[Badaz52]

What I wrote here may give you some clues why Sysprep isn't working as expected.

 

This worked perfectly, all I will do is rename the machines once they have been re-imaged

[Michael]

This worked perfectly, all I will do is rename the machines once they have been re-imaged

 

I'm curious to know - why rename machines when you can move them into properly labelled OUs within your structure?

[LeMarchand]

I'm curious to know - why rename machines when you can move them into properly labelled OUs within your structure?

 

I rename all machines so that I know where they are/where they are in a room (fixed machines) and which teacher they're assigned to (laptops).

[Michael]

I rename all machines so that I know where they are/where they are in a room (fixed machines) and which teacher they're assigned to (laptops).

 

With regards to Teacher notebooks, if you double click the object (in AD) you can add a Description and add the Teacher name here. A lot easier/quicker than renaming the machine.

[LeMarchand]

With regards to Teacher notebooks, if you double click the object (in AD) you can add a Description and add the Teacher name here. A lot easier/quicker than renaming the machine.

 

Doesn't help as much if you need to find out on a physical machine or if you're (say) checking wireless logs etc (and doesn't look as neat).