Getting deployment right

[garethEds]

Morning all,

 

So, the plan now is to start looking at Windows 10 deployment after half term. I'm trying to put a list together of what needs to be done. Besides the standard import into MDT etc etc what steps do we have already? Is it worth making a sticky post that details the steps (have I missed one)?

 

Remove unwanted apps - when? During deployment of the final image or during capture of the reference image?

AppLocker - if apps are deleted as above, then why does this need to be activated?

Start Menu - does a redirected start menu work now with the standard Windows 10 setup?

 

What software are people putting into their reference build? We usually install the standard Microsoft libraries - the Visual C++ stuff.

 

Office will go into the reference build of course as will our other standard stuff.

 

Capture then deploy.

 

What other steps do people have in there to make that perfect build for them?

 

Gareth

[simpsonj]

Following this as I'm planning something similar...

 

From what I've read, for the start I would do this:

 

1, Download the latest version of Windows 10 you want to deploy (not necessarily the latest update, upto you).

2, From the .iso, export the .wim file and remove the apps (there's a thread on this somewhere...)

3, Import that .wim into MDT ready to deploy.

4, Applocker, I believe, does more than just stop those apps, but prevent other things from running that you may not want to remove, such as the Windows Store app, though I may be wrong on this point.

 

As for the rest, I can't help as I'm not there yet!

 

Would be interested in how other people are rolling this out, I'm planning on doing a step by step blog once I've got a way that works for us...

[simpsonj]

This is thread to remove apps, though @Arthur should get the credit! The last page has a powershell script, and I think @Arthur has a .zip file with scripts in to get rid of the apps, so use whichever you're more comfortable with.

[ADMaster]

I do not capture a reference image, everything is done via scripts during OSD, I use SCCM but I think you can do similar with MDT.

In any case here is my list of customizations.

Disable SMBV1

Disable startup repair

Disable PC Reset

remove default apps

set default file associations

start layout xml

disable consumer experience

remove one drive

set search

branding

 

Branding script does theme, background, user account pictures etc , but also disables chrome and defender first run popups.

 

Then I install the apps, office, chrome, vlc, adobe as part of the osd task.

 

Specialty software that doesn't go to everyone such as photoshop gets pushed out later with PDQ.

 

All of these customizations can be found across the forum, but I think I got the most of them from here All the scripts are provided as a zip download.

[Duke5A]

I build my images in a VM, use sysprep and capture using WinPE and DISM. Drop the image straight into WDS and off I go. If you start with the LTSB version of Win10 you'll save yourself a lot of headache as the bundled crapware isn't there (No xbox, Cortana, Windows Store, etc).

[ninjafish]

I do the same as @Duke5A, the only other step I do is to create a snapshot just before the sysprep, this means you can then revert to the snap shot after capturing the image and not have any sysprep flags. Then you can easily edit and recapture using the same process as many times as required