Jump to content

Recommended Posts

Posted (edited)

Multiple ways really.

 

Any multi user systems where no one really uses on a day to day we are planning on the good old fashioned way. Our build and capture is fully automated except browsers and plugins which get deployed at deployment. So wipe and reload on 80% of our devices.

 

Any devices that have a few users (offices and laptops) we are doing in place upgrades via a task sequence in SCCM.

We might move away from using a TAsk sequence in the future but it allows us to make any modifications each upgrade may or may not need which other in place methods don’t have.

Edited by gaz350b
Posted
In place upgrade task sequence in most cases out of hours. Means you can update drivers and/or office. Build and Cap a new image. Ideally I'd like a monthly image for new Desktops,Laptops. Laptops and tablets are a pain unless u have a SCCM DP reachable from home. You can set them to get upgrades from windows update but you end up with dealing with the file associations/start layout/group policy/extra apps retrospectively.
Posted

The same as above, in place upgrade via task sequence.

I tested the 1703 to 1709 feature update via sccm windows 10 servicing and it brought in the new apps, one drive and a few other settings. I didn't look too closely, one glance was enough to tell me the task sequence is the way to go.

 

I have an upgrade to 1703 TS that applies the upgrade and then removes the extra apps and re applies the various OSD customizations.

 

I've not updated it to 1709 yet but its on my todo list, should be a matter of swapping in the new wim.

  • Thanks 1
Posted (edited)

I've not updated it to 1709 yet but its on my todo list, should be a matter of swapping in the new wim.

 

All I did was duplicate the TS and link to the new WIM. Other than a few gpo changes all was good.

 

Probably just needs a few new apps removing before we deploy it everywhere.

Edited by gaz350b
Posted (edited)
You guys seem to be using SCCM for Windows 10 upgrades. We have only ever used MDT/WDS with Windows 7. Should we be considering a move to SCCM now that we are looking at Windows 10 deployments? Edited by fiza
Posted

@fiza I was thinking the same thing last night reading this thread, however I'm wondering if I could create a different TS in MDT that doesn't format the drives and instead just upgrades the current OS?

 

Not sure what changes other than removing the "Format ad Partition Disk (BIOS)" and "Format ad Partition Disk (UEFI)" tasks would be required. Just thinking out loud here...

Posted
@fiza I was thinking the same thing last night reading this thread, however I'm wondering if I could create a different TS in MDT that doesn't format the drives and instead just upgrades the current OS?Not sure what changes other than removing the "Format ad Partition Disk (BIOS)" and "Format ad Partition Disk (UEFI)" tasks would be required. Just thinking out loud here...

 

Or could the OS upgrade be deployed through MDT as an application? (not something I've looked into... yet)

  • 4 weeks later...
Posted
Same way I always have. Build and test a new up to date image during the summer term, reimage the site over the holiday. 1703 will be supported until September 2018, so I see no reason not to hold off on 1709 and whatever the next release will be (1803?). MDT is set up so we just drop in a WIM with the bundled apps removed and nothing else... Total time before sysprep is less than an hour.
Posted
With Windows 10 are you going for a thin image and then adding software via SCCM or MDT? Ours has always been a fat image with everything in it.
Posted
With Windows 10 are you going for a thin image and then adding software via SCCM or MDT? Ours has always been a fat image with everything in it.

 

Thin, call it a hamburger approach:

 

1) standard Windows 10 1709 Edu WIM direct from Microsoft VLSC

2) drivers injected via the "total control" DriverGroup001 method

3) applications installed based on machine Role from MDT database

4) a couple of manual Application steps e.g. remove Windows 10 apps, join to Domain etc.

5) enjoy :)

Posted
Thin, call it a hamburger approach:

1) standard Windows 10 1709 Edu WIM direct from Microsoft VLSC

2) drivers injected via the "total control" DriverGroup001 method

3) applications installed based on machine Role from MDT database

4) a couple of manual Application steps e.g. remove Windows 10 apps, join to Domain etc.

5) enjoy :)

 

Why not put domain join (and probably app removal) in the MDT task sequence and go completely hands free?

Posted (edited)
Why not put domain join (and probably app removal) in the MDT task sequence and go completely hands free?

 

@Rob_D it is, when I say manual Applications I mean a separate step in the TS rather than all done via database Roles alone aka the "Install Applications" step

 

Once the machine gets started either from F12 boot or Refresh it is completely hands free :)

 

This is the TS I'm currently testing with 1709, does extra logic such as only install Smartboard software for machines named in a certain way, MAK activate for laptops, pre-stage Print Drivers so GPP maps faster on first login etc.

 

1709 TS.png

Edited by gshaw
  • Thanks 2
Posted
@Rob_D it is, when I say manual Applications I mean a separate step in the TS rather than all done via database Roles alone aka the "Install Applications" step

Once the machine gets started either from F12 boot or Refresh it is completely hands free :)

This is the TS I'm currently testing with 1709, does extra logic such as only install Smartboard software for machines named in a certain way, MAK activate for laptops, pre-stage Print Drivers so GPP maps faster on first login etc.

 

Ooh, shiny. Prestaging the printer drivers is a good idea. I'll have to look into that.

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...