Create a new Deployment Package in SCCM

[NetworkNinja]

Hi All,

 

I have started some research on creating a sccm package ready for deployment. currently we only have windows 7 as an option for deployment but these were here before i started the job. I would now like to create a package for windows 10 and wondering how do i go about starting this.

 

Do i just need a standard windows 10 ISO file or do i need to capture an image by using winpe

 

We are currently using system center 2012 and its installed on windows server 2008 r2 standard

 

Any help is apprenticed

[ADMaster]

A lot of folks to a build and capture of a Gold / Master image. I just deploy the base OS and customize on the fly during OSD.

In short import the image from the install source into the operating systems section.

Create a task sequence pointing the OS section to the newly imported OS

Deploy that task to a collection.

 

I suggest reading several of the step by step guides.

https://prajwaldesai.com/sccm-2012-r2-step-by-step-guide/

 

You may need to update your ADK and boot images to support Windows 10, upgrade yourself to the latest CB then deploy 10. Current branch added several features specific to deploying 10.

 

https://www.systemcenterdudes.com/step-by-step-sccm-1610-upgrade-guide/

[NetworkNinja]

Hi ADMaster, thank you for the attached information. It looks like I have a lot of bed time reading. I currently have windows 8.1 pro installed on my machine whereas all other machines have windows 7. Would you suggest as a starting point by upgrading my machine to windows 10 first before I eve consider rolling out windows 10.

[ADMaster]

I would always upgrade my own machine before the users. However I'd do a lot of testing in a VM first.

[Norphy]

If you want to deploy Windows 10 from SCCM 2012, you will need to make sure it's running the latest service pack and the latest cumulative update available for that SP. I would, however, recommend updating it to the latest version in the current branch which I think is 1610. That way, you'll be guaranteed compatibility with the latest branches of Windows 10.

 

As for going for a thin, thick or hybrid deployment, there is no right or wrong answer. Personally, I prefer the hybrid approach because there are certain pieces of software such as Office and Adobe CC which are big, awkward, needed everywhere or a combination of the three. It ends up being quicker to deploy that software as part of the base image. But that's me, do what works for you.

[Fazza]

We have a 'Golden Image' where I have basically created a new VM on my PC, installed the OS (8.1u1 or 10) and then installed all the 'Standard Software' that is found on both Staff and Student computers from Office to 7-Zip etc. Once everything is installed I let SCCM do it's stuff by running the Manual Capture (I don't bother using a Task Sequence as I couldn't get that to work straight away and the Manual Capture just works). Once the captured Image has been added to SCCM you can then create a Task Sequence so you can use PXE boot to deploy it.

[NetworkNinja]

If you want to deploy Windows 10 from SCCM 2012, you will need to make sure it's running the latest service pack and the latest cumulative update available for that SP. I would, however, recommend updating it to the latest version in the current branch which I think is 1610. That way, you'll be guaranteed compatibility with the latest branches of Windows 10.

 

As for going for a thin, thick or hybrid deployment, there is no right or wrong answer. Personally, I prefer the hybrid approach because there are certain pieces of software such as Office and Adobe CC which are big, awkward, needed everywhere or a combination of the three. It ends up being quicker to deploy that software as part of the base image. But that's me, do what works for you.

 

I totally agree with you, we would always try and put the software that we have on every machine into the base image. I Suppose before i even consider trying to make a master image i should consider the following points. 1. Need to update SCCM (Our current Version is 5.0.7711.0) 2. Test out windows 10 as a VM machine through Hyper V and only once have i done those 2 points i can consider creating a master image.

[NetworkNinja]

We have a 'Golden Image' where I have basically created a new VM on my PC, installed the OS (8.1u1 or 10) and then installed all the 'Standard Software' that is found on both Staff and Student computers from Office to 7-Zip etc. Once everything is installed I let SCCM do it's stuff by running the Manual Capture (I don't bother using a Task Sequence as I couldn't get that to work straight away and the Manual Capture just works). Once the captured Image has been added to SCCM you can then create a Task Sequence so you can use PXE boot to deploy it.

 

I like the way you have created your golden image, i think i might end up doing it the same way as you because i am going to create a VM machine with windows 10 installed to test out some policies etc

[Norphy]

1. Need to update SCCM (Our current Version is 5.0.7711.0)

 

That's 2012 RTM, no service pack, no cumulative updates, not R2. At the very least, you should put 2012 SP2 on there along with CU4 for it.

 

But if you're going to do that much work, you may as well go the extra step and put the current branch on too.

[Fazza]

I like the way you have created your golden image, i think i might end up doing it the same way as you because i am going to create a VM machine with windows 10 installed to test out some policies etc

 

It works very well for us and with the very latest version of SCCM it installs a lot quicker than before. I put a couple of things in the Task Sequence that keep changing versions such as Impero so the latest version we've added to SCCM gets installed as part of the task sequence along with some Task Sequences having specific software for just that computer suite it's being installed in to.