josephwagner

No, I would love to use offline servicing, but unfortunately that isn't an option. Right now we are using SCCM to deploy our images to new workstations or when we reimage a workstation via PXE. Those images were captured as 1511. I would like to add steps into the task sequence so that while the system is being imaged it is getting upgraded to 1607 at the same time. So for example, it will apply the 1511 wim file and then apply the 1607 upgrade as well as the latest CU.

Is there a way I can upgrade our current images during the OSD process. Our wim files were built on Windows 10 1511 and we are currently in the process of upgrading our current workstations from 1511 to 1607 using the method outlined here: https://osddeployment.dk/2016/08/05/how-to-upgrade-windows-10-1607-with-sccm-1606-inplace-task-sequence/ We would like to update our images as well so new workstation deployments are receiving the update. We are unable to update our wim files at this time. I tried adding the steps in at the end of the task and didn't have any luck when I tested this. (See attached image) Thank you.

I work for a K12 school district and am working on deploying Faronics Insight to multiple computer labs. In Faronics Insight there is the ability to set a channel number for each computer lab that you are using the software in. Last year, when I deployed this software I created a collection and application for each lab and had the specific channel number in the installation program field parameters during the silent installation process. This year, I would like to avoid creating 30+ different collections and applications for each specific lab. What would be the best way to deploy this software creating only one application and collection? So far, I am thinking if I create a PowerShell script to look at the computer name and get the room number from the name and then insert the designated channel number into the installation command line would be my best bet. Would this be a viable option?