Jump to content

Recommended Posts

Posted

Hello out there.

 

Having a do-over of my W10 image and I'm not getting what I'd like from unattend.xml.

 

Using fog, doing what I'd assume is the right thing on it. Basically steps look likw:

 

Install W10

Don't let the VM see internet/network at this stage

Get into config mode from the language selection screen

Tweak and defrag Windows slightly

Make up an unattend.xml and stick it in C:\ and C:\windows\system32\sysprep

sysprep.exe /reboot /unattend:C:\unattend.xml (which brings up the sysprep box so I tick "generalise" and ok through it.)

Let it reboot, having set fog hovering to catch the image, which I then upload

Deploy and test

 

To my point and my tinkering then. I'd like to, after the above:

 

- Have the imaged machine join a specific OU in AD - as in, all newly imaged machines go into an OU called "freshly imaged" or similar. Think I have this right already even...

 

- To NOT log in as any account on restart automatically.

 

- To enable the local admin account. Not necessarily set a password (will eventually use LAPS for that.)

 

...can anyone steer me to the right things in unattend.xml for all those? I've tried a generator for the options but don't seem able to get it working right.

 

Thanks MUCH in advance and I'll get you a pint after Bett 2021!

Posted

I dabble in answer files a little.

Fist off, what are you using to generate the answer file? I highly recommend using the Windows System Image Manager found in the Windows ADK for your windows 10 version you are installing (if you are using Windows 10 1903 or 1909, download this patch, extract it after the ADK install and follow the directions in the readme (here):

https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

 

 

Once this is all set up, follow the directions here to get started: https://www.windowscentral.com/how-create-unattended-media-do-automated-installation-windows-10

 

For the unattended domain join components, look at the screenshot here:

untend.PNG

 

The highlighted choice in the lower left is what is needed. Right click that and choose "Add Setting to Pass 2". After that, right click again and choose "Add setting to pass 4"

 

You'll then notice that in the central window of WSIM labeled Answer File, you see these options placed under pass 2 and 4. You can choose each blue box and enter domain credentials and options.

 

 

As for enabling the built in admin account, there are a couple of methods. What I would recommend is setting the password in the unattend file itself instead of leaving it blank. You can do this by right clicking on the below screenshot'ed components in the lower left box and choosing "Add setting to pass 5" This will be added to your Answer file and you will then use the new blue boxes in the center to set the password and enable the account. You will need to use the Autologoon section to enable the account, but you don't have to have it actually auto login.

 

anser.PNG

 

Then you can specify options these places in the answer file

answer.PNG

autolog.PNG

adminpw.PNG

 

So this should now take care of both the join and the admin account. You can explore other things in the Windows SIM for endless options. Hope this helps!

  • Thanks 1
Posted (edited)

If you use Fog, You can tell the computer to join the domain after imaging. That's how we do it. You will need to have the Fog Client installed on the computer pointing to the fog server.

 

Its just some settings within the Client settings on the Fog webpage.

 

Our unattended does very little. (Setting local admin account, region settings etc....)

Edited by newpersn
  • Thanks 2
Posted

+1 to the FOG client as well. Some people have a big aversion to it, but it has become quite the helpful utility. Super light weight and pretty much unnoticeable if you keep it hidden from users. My environment uses it to name the PC, Join the domain, and even install software or run scripts on demand over the network (Snapins they are called). I would highly recommend the FOG forums (biased because I'm a mod there lol). The developers troubleshoot issues quickly and work directly with the users.

https://forums.fogproject.org/

 

Like newpersn, our unattend is very small and does very little compared to the client.

  • Thanks 1
  • 2 weeks later...
Posted

Folks thank you all so much for the above.

 

Back to it now after a little while. Have a few things to wrestle with but I'm sure this'll have what I need.

 

Cheers much all. :) :)

Posted
If you use Fog, You can tell the computer to join the domain after imaging. That's how we do it. You will need to have the Fog Client installed on the computer pointing to the fog server.

 

Its just some settings within the Client settings on the Fog webpage.

 

Our unattended does very little. (Setting local admin account, region settings etc....)

 

Any chance you could post yours up/PM me? Sans passwords ofc.

Posted

Oh my word I did it!

 

Used a generator in the end and hacked out the sections I didn't need. Just now first test VM imaged, rejoined and renamed in FOG etc... beaut.

 

Thank you all so much for the patient help there. This had me unhappy but now all better. :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...