Jump to content

Recommended Posts

Posted

Hi Guys,

 

I am a complete newbie to SCCM, and I am trying to implement this in my test lab so I can learn how to implement and support it in the systems I look after. I have managed to successfully install SCCM, I am just wondering on what you guys do when it comes to device collection.

 

For example, in my AD, my structure is Domain - School Name - Computers - User Type (Staff for example) - Staff Desktops or Staff Laptops.

 

That is actually a really bad example of what I have just given, I hope it makes sense.

 

Do you guys create your device collection for every OU folder you have in AD?

 

The same applies to task sequences, how do you guys do your deployment sequences?

 

Do you have a task sequence for each type of machine E.g Staff Laptop or just a generic "Deploy Windows 10" one?

 

Again, I ask this because you can during the task sequence specify which OU to put the computer in. If I was to create this, it would take hours to create Device Collections and Task Sequences for each OU.

 

Final question, do you let SCCM handle Windows Updates, or do you just still use a GPO to point your computers at WSUS? I am a bit confused with how the Windows Update feature works, does this mean each time an update is released I have to create an update package?

 

I am sorry if this is explained terribly, I am completely new to SCCM.

 

I will look forward to your replies.

 

Best regards

James

Posted
Hi Guys,

 

I am a complete newbie to SCCM, and I am trying to implement this in my test lab so I can learn how to implement and support it in the systems I look after. I have managed to successfully install SCCM, I am just wondering on what you guys do when it comes to device collection.

 

For example, in my AD, my structure is Domain - School Name - Computers - User Type (Staff for example) - Staff Desktops or Staff Laptops.

 

That is actually a really bad example of what I have just given, I hope it makes sense.

 

Do you guys create your device collection for every OU folder you have in AD?

 

The same applies to task sequences, how do you guys do your deployment sequences?

 

Do you have a task sequence for each type of machine E.g Staff Laptop or just a generic "Deploy Windows 10" one?

 

Again, I ask this because you can during the task sequence specify which OU to put the computer in. If I was to create this, it would take hours to create Device Collections and Task Sequences for each OU.

 

Final question, do you let SCCM handle Windows Updates, or do you just still use a GPO to point your computers at WSUS? I am a bit confused with how the Windows Update feature works, does this mean each time an update is released I have to create an update package?

 

I am sorry if this is explained terribly, I am completely new to SCCM.

 

I will look forward to your replies.

 

Best regards

James

I usually split my collections into OU location and OS type. But with wmi queries there are 100s of types of collections you can create from hardware / software installed to if a computer has been restarted in 30 days. Here are list of examples https://www.google.co.uk/amp/s/www.enterinit.com/sccm-query-collection-list/amp/
  • Thanks 1
Posted

I have some for staff and student devices. Then broken down to desktops and laptops for staff and student. When I'm deploying a new app I create a collection called Install . Then deploy to that collection. I have rules based on the PC name for these collections. I keep queries for each room.

 

In terms of if you should use SUP instead of standalone WSUS. I think it comes down to maintainence windows. You can do this with SCCM SUP but it's harder with standalone WSUS. If you are updating Office 365 Proplus using a SUP is necessary. These days WSUS is a pain due to the app pool memory. Updates have got a lot bigger and the WUA is doing some more complex stuff than when it was originally designed. If you have the bandwidth and don't mind losing some control. Windows Update for Business might work.

  • Thanks 1
Posted

Groups - a few hints

1. you can link to an ou if you want

2. You can use prefix's for groups . I use OU for ou linked groups, R for rooms (eg ict suite1), G for groups of rooms (eg all ict suites) and S for software. Also you can split things like desktop/laptop or communal use/one user machines.

3. Create a group for each piece of software, then put rooms into that group.

 

Updates, yes. Use Sccm. If you install right click tools you can deploy updates from the console. If you get super clever you can make updates available in the software centre and allow staff to install updates at their convenience.

 

I still do deployment mostly in MDT. You can import all the bits from mdt into SCCM quite easily.

 

pro tip... SCCM is a beast. Don't go too big to early, it takes years and probably a few rebuilds before it's as slick as you would like.

  • Thanks 1
Posted (edited)

As others have said, there's a lot in SCCM.

 

With Device Collections you can be as specific or vague as you need. I tend to group by either the job title of staff requesting software(if it's on their office PC), room numbers or department. Or for things that are needed everywhere I have collections for all desktops or all laptops.

 

My task sequence is generic and only contains software that every computer must have. The task sequence also puts computers into an OU called SCCM Computers(if it's a brand new computer). Once built I move the pc to it's proper OU. if it's a rebuild then it stays in its existing OU and keeps it's name.

 

Whatever you decide, take your time are prepare for lots of trial & error.

Edited by chris11256
  • Thanks 1
Posted

Don’t deploy anything to the All Systems collection. :)

 

SCCM is a huge product. I personally recommend going on a training course for it. I’ve been on them, I found them immensely helpful.

  • Thanks 1
Posted

Thank you so much for these awesome replies guys!

 

At the moment, this is just for a test lab in my home. I am hopefully getting some proper SCCM training which should be good, I just wanted to get a head start. Thanks guys.

 

James

Posted
Don't forget to master MDT as well. It's pretty much the biggest part of sccm, once you've learned it SCCM is how you apply it. With MDT you deploy images and programs, Once you've got that in place you combine it with SCCM to do super fancy stuff.

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