localzuk Posted January 27, 2017 Posted January 27, 2017 I am fast coming to the conclusion that I spend too much time getting images to work properly in SCCM - it is a complex beast, perhaps too complex for my needs. So, what are you guys using for deployment these days?
LeMarchand Posted January 27, 2017 Posted January 27, 2017 I'm using WDS + fat images, but all Primary/Junior - so may not be sufficient in more complex environments.
Katy Posted January 27, 2017 Posted January 27, 2017 Used to use WDS with a load of unattend scripts, now I use MDT and I just use the windows ISO as a base image (i.e. I don't install stuff then re-capture and deploy). All application installs are then either as applications pushed through MDT (mostly things that don't supply an MSI so can't be done via group policy). Other software I have startup scripts that install where they are too complicated for group policy or cause problems with MDT (office doesn't reliably install from MDT if you also install Sophos at the same time, as Sophos updates itself after claiming it has completed install and Office then fails with "Another installation is in progress"). All-through with about 450 PCs/laptops here. 1
jertsy Posted January 27, 2017 Posted January 27, 2017 (edited) MDT with a windows base image, MDT installs MS Office and a few plugins, then SCCM deploys certain software depending on what OU the PC is in. I like MDT Edited January 27, 2017 by jertsy
6Foot2 Posted January 27, 2017 Posted January 27, 2017 SCCM deploys the OS and then some core applications (Office 2013 etc) and then deploys other packages depending upon SCCM group membership.
KibosJ Posted January 27, 2017 Posted January 27, 2017 We use SCCM here too, have it load the image then it installs about 9 applications for staff and about 12 for students. Have a few issues every now and then, but works fine for the most part.
Zourous Posted January 27, 2017 Posted January 27, 2017 We've used FOG for quite a few years now and it's better than ever with version 1.3.3. Can deploy images at over 10gb per minute. I'm not sure many other solutions can match that.
3s-gtech Posted January 27, 2017 Posted January 27, 2017 We're still on FOG 0.32. I've used newer versions and they're great, but our crusty old version works lovely so I leave it be. Will probably have to update for Windows 10, and of course I have to set everything to legacy boot at present.
localzuk Posted January 27, 2017 Author Posted January 27, 2017 We've used FOG for quite a few years now and it's better than ever with version 1.3.3. Can deploy images at over 10gb per minute. I'm not sure many other solutions can match that. Yeah, the speed of imaging with FOG is something I miss using SCCM. I could image an entire suite in about 20 mins with it, and that was pre-SSD days.
mrbios Posted January 27, 2017 Posted January 27, 2017 Yeah, the speed of imaging with FOG is something I miss using SCCM. I could image an entire suite in about 20 mins with it, and that was pre-SSD days. With SCCM i can image an entire suite on a schedule without ever entering the room. SCCM is a beast, but it can be tamed, stick with it and you won't regret it in the end Also which version are you using? I had so many weird and not so wonderful bugs with 2012R2, current build on 1610 though seems fantastic, so many little niggley bugs i previously hit in 2012R2 no longer seem to be an issue. (besides multicast, hopefully one day microsoft might fix that...) What does your task sequence look like at the moment? Maybe we can help!
sparkeh Posted January 28, 2017 Posted January 28, 2017 (edited) SCCM, still love it and it's so much more simple than when I started with 2007. Never really had any issues with images, what are you having issues with? Edited January 28, 2017 by sparkeh
Michael Posted January 28, 2017 Posted January 28, 2017 Either optical or USB flash boot into WinPE environment, then deploy fat images. On average 20GB-30GB in size.
snagrat Posted January 28, 2017 Posted January 28, 2017 SCCM at our bigger clients. Works very easily really once you know what you are doing.
localzuk Posted January 28, 2017 Author Posted January 28, 2017 I've been running SCCM for 5 years now, so I know how to do most things. The issue is it just seems unstable. I'm on the 1610 release now, and as an example, yesterday, mid-imaging a PC, the server decided to stop allowing any downloads. It killed the PXE service too. Required a full reboot to remedy. With imaging, as an example, making all the drivers work for each machine can and is a pain. Some machines are a breeze. Others? Not so much. With a fat image, including the drivers, it is basically install, capture and deploy. Done.
dblight Posted January 28, 2017 Posted January 28, 2017 (edited) It can be a royal pain in the backside. I certified in it a few years ago and realistically I'm the only one in our team that knows it inside out. But we wouldn't be without it. With regards to drivers, yes they are the bain of anyone life who has to deal with OS Deployment. What I do is when we have a new model of anything is build it using whatever OS we will be using on it (normally the same as the OEM OS it ships with) then after the OOBE make sure all the drivers are up to date with the latest then use a little utility called Double Driver. Extract all the drivers to your OSD driver storage location. Add them to SCCM and create a driver package. Then add in a new Driver package step to the MDT based on the machines model name from WMI query. Bosh. All drivers sorted for that model. Edited January 28, 2017 by dblight 1
free780 Posted January 28, 2017 Posted January 28, 2017 I usually build a reference PC/laptop/tablet. Then update all the drivers l. Then use powershell export-windowsdrivers. Exclude any print drivers and import into SCCM. Use a wmi query per driver package. It works apart from some lazy OEMs. Who don't encode a system model. Though you can usually use the baseboard. I think things have got better with the more recent updates though it does break multicast every time. The signing key is removed from the registry. I guess I should submit it to uservoice otherwise MS won't change it.
MrFrostmaul Posted January 28, 2017 Posted January 28, 2017 WDS default Windows 7 Enterprise (64bit) and then PDQ to deploy all software (have created a master package with all the individual software packages within). Works well and for our size does the job. 1
dhicks Posted January 28, 2017 Posted January 28, 2017 So, what are you guys using for deployment these days? We use Serva: PXE Server for Windows (UEFI & BIOS) - Serva We have it deploy the basic Windows image, as provided by downloading from Microsoft, with the addition of a few drivers needed by some particular bits of USB-connected hardware we have around the school. We also periodically update the image with the latest Windows Updates. We then have an unattend.xml deployment file that runs a script that renames each computer based on MAC address, so once a machine is imaged it is named and joined to the domain. From there, we could have software deployed via MSI depending on group policy, although at the moment we are using another script as we have several bits of rather old and crusty software that needs a bit of prodding to install properly. 1
winng Posted January 28, 2017 Posted January 28, 2017 Using MDT at my school is painful and takes anything from a few hours to an overnight process. That's probably due to the network performance being &%$£ poor. So, we now just boot from USB to install Windows 10, manually install Office 2016, then use Ninite.com for Chrome, Foxit, Peazip, Java, Silverlight, etc. and deploy other software like Adobe CS6, Papercut, etc. via GPO. It takes about two hours per machine. Much quicker.
mullet_man Posted January 28, 2017 Posted January 28, 2017 MDT here. Although it's totally not the best or MS approved way of deployment I use HyperV to create a base image and then capture in MDT and then deploy that out. Keep snapshots and update it every few months.
Guest obsidianpillar Posted January 28, 2017 Posted January 28, 2017 MDT here. Although it's totally not the best or MS approved way of deployment I use HyperV to create a base image and then capture in MDT and then deploy that out. Keep snapshots and update it every few months. That's what I do also, keep a base image with no applications, just update it and then snapshot before capture and then deployment.
Ephelyon Posted January 28, 2017 Posted January 28, 2017 We use Serva: PXE Server for Windows (UEFI & BIOS) - Serva We have it deploy the basic Windows image, as provided by downloading from Microsoft, with the addition of a few drivers needed by some particular bits of USB-connected hardware we have around the school. We also periodically update the image with the latest Windows Updates. We then have an unattend.xml deployment file that runs a script that renames each computer based on MAC address, so once a machine is imaged it is named and joined to the domain. From there, we could have software deployed via MSI depending on group policy, although at the moment we are using another script as we have several bits of rather old and crusty software that needs a bit of prodding to install properly. I like that find - may give it a go. Crusty old WDS here on Server 2016 (though at least it's not RIS!), and it's nice to see someone else using manual scripting to handle renaming and domain joins...
mdrabble Posted January 28, 2017 Posted January 28, 2017 Not noticed any issue with 1610 sccm imaging machines but have noticed issue with 1610 dpm randomly dropping connections to hosts
mullet_man Posted January 29, 2017 Posted January 29, 2017 That's what I do also, keep a base image with no applications, just update it and then snapshot before capture and then deployment. I have most of the apps in my image though as some e.g CS6 are massive so having that install during deployment would add an age. I've started to use SCCM to deploy out subject specific apps lately too.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now