Best for imaging

[manamaga2512]

Hi all, having been a Mac school for nearly 7 or so years now, it looks like the new principal is wanting to move back to Windows. Over that time I have become a little rusty so I'm brushing up on a few things. Back then we used to use Symantec Ghost for imaging but I'm guessing time has move on an there maybe many more options available now. We will most probably be going W10 and will also need to deploy a number of apps / software; Office, SIMS client etc. Looking for opinions on imaging software. We were a team of four (network manager, asst. manager, and two techies), but now we are down to just two of us, so ease of use and speed will also be a plus :-)

 

Many thanks.

[LytchettNM]

Have a look at the free deployment solution from Microsoft which uses the built in role and then add Microsoft deployment workbench "MDT" takes a little bit of time to setup but when done you can handle drives, pre-configure the OS and add applications at deployment time or you can build a custom image with any applications you want.

At the hardware end i.e. The new computer all you need do after the server is setup is PXE boot the computer which is just pressing F12 at startup and chose a package you have made available for deployment, and if you spend a little more time on configuring the server you can also assign computer name, pre-select a deployment package and join your domain all recognised by MAC address.

The features that this solution offers for free and backed by Microsoft are in my opinion second excellent plus there's a lot of support on many forums.

https://www.microsoft.com/en-us/download/details.aspx?id=50407

Edited March 6, 2017 by Techforyou

[Davit2005]

Have a look at the free deployment solution from Microsoft which uses the built in role and then add Microsoft deployment workbench "MDT" takes a little bit of time to setup but when done you can handle drives, pre-configure the OS and add applications at deployment time or you can build a custom image with any applications you want.

At the hardware end i.e. The new computer all you need do after the server is setup is PXE boot the computer which is just pressing F12 at startup and chose a package you have made available for deployment, and if you spend a little more time on configuring the server you can also assign computer name, pre-select a deployment package and join your domain all recognised by MAC address.

The features that this solution offers for free and backed by Microsoft are in my opinion second excellent plus there's a lot of support on many forums.

https://www.microsoft.com/en-us/download/details.aspx?id=50407

 

+1 for MDT.

 

Prep a machine in a Virtual environment install all needed software as required and then deploy. When the machine deploys you can add selection profiles to add correct drivers. No need to rebuild for a driver change :-) . Or go full hog and set up SCCM but that may be overkill for your need.

[Fazza]

We use SCCM for imaging our computers. Before SCCM we used Active@ Boot Disk which contained a few utilities including an imaging utility.

[mikkydoos]

Is MDT better than WDS for one off deployments? WDS sucks.

[Arthur]

Is MDT better than WDS for one off deployments? WDS sucks.

Massively better! I don't know why anyone bothers with WDS when you can do so much more with MDT.

[Davit2005]

Massively better! I don't know why anyone bothers with WDS when you can do so much more with MDT.

 

+1 again.

 

MDT is a slightly different way to work. With a bit of time and research you can get all the software installing via switches, batch files etc. Adobe CC, Java ( sorry for the language), Adobe Reader, Office etc. etc..... .

 

MDT'd a class of 24 PC's in 25 mins easy. Think the speed of ghost/fog but not the hassle of a rebuild for a change of driver, the drivers delivered at deployment.

 

SCCM would be one step further and enable application deployment POST deployment based on AD security group etc.

[disk]

MDT is definitely the way to go. SCCM can do more but is a bit more complicated. You might consider something like PDQDdeploy for installing software after imaging (not to say you can't install software during the imaging phase with MDT because you certainly can!).

[GreyFox]

Another for MDT.

I set up FOG (Free Open Source Ghost) at my previous school, which worked great for Windows XP and 7. We would install Office and a number of other applications on the image, sysprep (using MySysprep2), capture, then deploy. There's a bit more to it than that obviously.

I can't speak for Windows 8/8.1, but things have changed with Windows 10. I tried FOG in my current school, but found it wouldn't quite do what I wanted. Using MDT, with WDS for the boot images seems to work well. As others have said, you can get programs to install as part of the deployment sequence. However, you could just install some on the base image. It does take a bit of setting up, but once you're up and running it is pretty quick and works well. For SIMS, I'd leave the client off the image, but deploy via SOLUS3 once the machine is ready.

[fiza]

+1 again.

 

MDT is a slightly different way to work. With a bit of time and research you can get all the software installing via switches, batch files etc. Adobe CC, Java ( sorry for the language), Adobe Reader, Office etc. etc..... .

 

MDT'd a class of 24 PC's in 25 mins easy. Think the speed of ghost/fog but not the hassle of a rebuild for a change of driver, the drivers delivered at deployment.

 

SCCM would be one step further and enable application deployment POST deployment based on AD security group etc.

 

How big is your image? How many additional software titles are you pushing out as part of the imaging process?

[gaz350b]

As people have said already mdt and later on sccm.do not under estimate how much time you will need to develop windows 10.

 

You will also need to start thinking about how you want to manage updates and upgrades across the organisation.

 

We've just decided to focus on 2 versions at any one time. So our focus is getting rid of the few 8.1 and 10 1511 installs we have. In favour of windows 7 and 10 1607 as our supported o/s types. Once every where is 1607 will we start developing "1705" what ever it will be called.

 

We are then going to try and stick to the windows servicing model with the largest install base being on current branch for business.

 

As for upgrading machines some will then be managed using in place upgrades, and then in labs etc we'll stick with a wipe/install method.

 

As for image design we do not have some items in the image. Those applications such as adobe PDF we deploy post install so that they get the latest version from our repository Or no version as the default position to ensure no security issues are present should a user use the machine before install completes.

Edited March 19, 2017 by gaz350b

[Davit2005]

How big is your image? How many additional software titles are you pushing out as part of the imaging process?

 

50-60Gb for Windows IT suites.

 

No longer involved as no longer work in the organisation but was responsible for the fun of building all the MDT images and documentation. Testing was done by another responsible tech/engineer.

[ITGURU]

Acronis true image

[manamaga2512]

I think I will take a look at MDT. Do you all have a separate server to handle MDT and images / imaging, or do you run it from your DC?

[fiza]

I think I will take a look at MDT. Do you all have a separate server to handle MDT and images / imaging, or do you run it from your DC?

 

On its own VM along with 2 images (admin and curriculum builds).

[manamaga2512]

On its own VM along with 2 images (admin and curriculum builds).

 

Is the VM running windows server or just a standard windows install?

[fiza]

Is the VM running windows server or just a standard windows install?

 

Server 2012 R2

[GreyFox]

Fiza has already answered this one really, but ours is on a Server 2016 VM, with two virtual disks. One for the server OS, the other for the MDT/WDS bits. Mine's already at 117GB used, with updates, packages, OS files and a number of different builds. I don't think it's recommended, but I run two deployment shares from this. A 'Build Lab' and 'Production'. Each one is set up a bit differently, so I thought this would save changing settings all the time. It works fine for me.

[manamaga2512]

Great. Thanks for the feedback. We have a number of spare Dell servers so I will get on building one up this afternoon. I presume we will need a different image for each model of PC?

[GreyFox]

No worries

Good luck!

Not necessarily. In each sequence you can select driver 'profiles'. I've got a profile that includes drivers for 3 different Dell AIO machines, then I've assigned this profile to a single task sequence for 'Dell AIO Desktops'. So one image and task sequence for 3 PC models. Yet under where you select the driver profile (where you can choose 'All drivers', if you like), there's the option to 'Install only matching drivers from the selection profile'. So in theory you can have one image for all of your devices, but I personally like to have a bit of control over these deployments.

Edited March 28, 2017 by GreyFox

[fiza]

Fiza has already answered this one really, but ours is on a Server 2016 VM, with two virtual disks. One for the server OS, the other for the MDT/WDS bits. Mine's already at 117GB used, with updates, packages, OS files and a number of different builds. I don't think it's recommended, but I run two deployment shares from this. A 'Build Lab' and 'Production'. Each one is set up a bit differently, so I thought this would save changing settings all the time. It works fine for me.

 

Exactly how I do it. Two deployment shares, has been working well for the last few years. We have 2 images (admin and curriculum) but we have drivers set up for 6 different machines. MDT just selects the right drivers and away it goes.

 

I used this guide when I first built the server : Deploying Windows 7 - Part 1: Windows AIK 2.0 Enhancements - TechGenix

[Koldov]

Does anyone have issues deploying over different subnets (VLAN)?

[LytchettNM]

Does anyone have issues deploying over different subnets (VLAN)?

 

You can F12 deploy over network but there are some network setting you will need to configure plus setup DHCP to forward to the deployment server.

You can also configure to boot from CD / USB.

[Koldov]

You can F12 deploy over network but there are some network setting you will need to configure plus setup DHCP to forward to the deployment server.

 

Yeah, that's how I read it too. Sadly, the guide I was using only mentioned that halfway down after I'd installed MDT, WDS, AIK and downloaded 3 ISO's to test....

 

DHCP is run from the switches on our network, we do not have the role on our server. Unfortunately they are managed by an external company and so any configuration changes will cost (and actually I have no clue what to ask them to do anyway).

 

You can also configure to boot from CD / USB.

 

If I have an IT suite of 30 pc's to do, wouldn't that be the same as sitting there putting the CD/USB in (minus a few button presses) or would I need 30 CD/USB's in the machines? Or am I missing something?

[LytchettNM]

Yeah, that's how I read it too. Sadly, the guide I was using only mentioned that halfway down after I'd installed MDT, WDS, AIK and downloaded 3 ISO's to test....

 

DHCP is run from the switches on our network, we do not have the role on our server. Unfortunately they are managed by an external company and so any configuration changes will cost (and actually I have no clue what to ask them to do anyway).

 

If I have an IT suite of 30 pc's to do, wouldn't that be the same as sitting there putting the CD/USB in (minus a few button presses) or would I need 30 CD/USB's in the machines? Or am I missing something?

 

For F12/PXE boot to work across a routed network the routing device will need IP helps and bootp relay setup, if this is not an options then the Boot CD/USB would be the best method for your setup.

I have not setup this method so that side will be a google m afraid, but I have seen it in use, the boot CD/USB stick runs winpe and makes the connection back to your deployment server so is only needed for the boot and running the script on the deployment server you can then move he boot CD/USB to another computer no need for 30 of them.