[sccm 2012] Let's hear your SCCM ideas...

[Planehazza]

So I've been using SCCM for about a year now, but I'm not getting a huge amount of time to focus on it and put my ideas into practice. Essentially, I'd like one smart Task Sequence that, depending on several variables, will automatically place clients into correct collections, AD groups etc, deploy apps/settings/registry etc. OCD me doesn't really like having loads of post OS deployment app installations - I want users to see that it's on the sign in screen and correctly assume all is ready to rock. I want to get away from an 'image' entirely too. I just want latest 22H2 ISO followed by updates, apps, config, domain join etc all in one nice sequence.

 

I already have a few apps pushing out depending on the detected subnet, so that only Site A gets app 7, and Site B gets app 3 and 4 etc.

 

I've got several device collections looking up AD groups or OUs, and driver collections (using DELL Command integration) pushing out drivers depending on queried hardware etc.

 

What have you got that's fancy so that I may develop skills with some fresh ideas?

[Jamoire]

How I have done it in the past is assigning variables to a collection and then use the options tab in the Install Application step in the task sequence so to set conditions to look for the variable.

 

So then any client that is in this collection directly or indirectly will get that App installed during the task sequence.

 

 

Only real drawback is that it doesnt work with unknown clients to SCCM as they aren't in the collections yet but it works great for reimaging or if you prerevision the device into SCCM before imaging for the first time and get it in the right collections.

 

Have also used it with the OS Installation steps so all our clients in School A get Windows 10 and all the ones in School B, C and D get Windows 11 etc based on variables in the collections.

Edited April 4, 2024 by Jamoire

[Planehazza]

How I have done it in the past is assigning variables to a collection and then use the options tab in the Install Application step in the task sequence so to set conditions to look for the variable.

 

So then any client that is in this collection directly or indirectly will get that App installed during the task sequence.

 

[ATTACH=CONFIG]71201[/ATTACH]

 

Only real drawback is that it doesnt work with unknown clients to SCCM as they aren't in the collections yet but it works great for reimaging or if you prerevision the device into SCCM before imaging for the first time and get it in the right collections.

 

Have also used it with the OS Installation steps so all our clients in School A get Windows 10 and all the ones in School B, C and D get Windows 11 etc based on variables in the collections.

 

 

Literally what I'm doing now dude, good timing

[kevin_lane]

Thanks for tip of the day never thought of this

[clareq]

There is a free third party app called TSGui. I used it extensively to set up a screen at PXE boot with drop downs that linked to OUs. I then used the variables created to put unknown machines into the correct OU and assign the appropriate software.

[dapaulio]

We use a set naming convention which would determine whether it’s a desktop or laptop and also to detect whether it’s a staff student or office computer. The variable will look at the naming of a device and appropriately allocate to a certain ou and also install relevant software. Eg sims on a teacher workstation, wireless networks on laptops Etc

[Planehazza]

We use a set naming convention which would determine whether it’s a desktop or laptop and also to detect whether it’s a staff student or office computer. The variable will look at the naming of a device and appropriately allocate to a certain ou and also install relevant software. Eg sims on a teacher workstation, wireless networks on laptops Etc

 

This is the route I was going to go down too. We have naming conventions too, and I'm very OCD with it, but getting others to stick to it is the problem.

[Planehazza]

We use a set naming convention which would determine whether it’s a desktop or laptop and also to detect whether it’s a staff student or office computer. The variable will look at the naming of a device and appropriately allocate to a certain ou and also install relevant software. Eg sims on a teacher workstation, wireless networks on laptops Etc

 

Just a thought, dude, what's your catch all? I currently have a variable that sets up the OU path per subnet, but if we take on a new site and forget to add the new value (I mean I've never done this... ) it doesn't domain join and the whole thing fails. If you enter an OU that doesn't exist in AD, what happens?

[Planehazza]

Perhaps this is a rookie 101 question, but how do you handle remote deployments of the OS? Say you want to image 5 IT suites of 32 PCs, and your AD, DNS, and SCCM clients are all nice, correct, and neat?

[dapaulio]

Just a thought, dude, what's your catch all? I currently have a variable that sets up the OU path per subnet, but if we take on a new site and forget to add the new value (I mean I've never done this... ) it doesn't domain join and the whole thing fails. If you enter an OU that doesn't exist in AD, what happens?

 

So the build will start from its static ou.

Then in our structure we have a student and teacher ou with laptops and desktops in each. And the naming convention will associate itself with the type of device.

the last task in the sequence queries the name you preassigned to it before the build and move the computer account to its designated ou from a build ou that has inheritance block and the important gps like default domain policy, security and laps config. If the build completes successfully it applies all group policies including branding etc. if it fails branding itsnt applied and indicates to us there is a problem for us to investigate.

[kevin_lane]

For us

 

We have 2 task sequences one for staff and one pupils.

 

They both run the same windows ISO

 

One task sequence will install a few other software deployments to the other task sequence

 

the computer accounts get popped into an OU.

 

once in the OU after installation, we then move it to its final OU.

 

we then give the device to the staff member or placed back into general population (pupils devices)

 

All our devices collections are based on OU but we do have a few custom collections based on name of devices