[sccm 2007] How do you set up your collections?

[sonofsanta]

No but its super simple:

 

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemOUName = "top.level/maincontainer/Computers/Laptops/TeacherLaptops"

 

FWIW my SCCM complained about syntax in that statement, and as I am feeling lazy I rebuilt it the long (button clicking) way and copied that query code to edit going forward, so I'm using

select *  from  SMS_R_System where SMS_R_System.SystemOUName like "TOP.LEVEL/MAIN CONTAINER/COMPUTERS/LOCATIONS/"

which seems to do the trick and add in devices from sub OUs

 

(someone at Microsoft seems very angry lately as well, what with the OU query there and Office 2013's SHOUTY CAPS)

[Theblacksheep]

FWIW my SCCM complained about syntax in that statement, and as I am feeling lazy I rebuilt it the long (button clicking) way and copied that query code to edit going forward, so I'm using

select *  from  SMS_R_System where SMS_R_System.SystemOUName like "TOP.LEVEL/MAIN CONTAINER/COMPUTERS/LOCATIONS/"

which seems to do the trick and add in devices from sub OUs

 

(someone at Microsoft seems very angry lately as well, what with the OU query there and Office 2013's SHOUTY CAPS)

 

My query was from SCCM2012, not 2007 if that's any use.

[sonofsanta]

My query was from SCCM2012, not 2007 if that's any use.

 

I'm on 2012 now as well, so Lord only knows. At this point in the year I probably just found a way to fail at copy & paste...

[Theblacksheep]

had a thought about deploying software to staff. In 2012 you could set deploy to users, optional install that requires admin approval. Then you staff can install software on curricular PCs if they need to.

 

Targeting these to normal staff could be messy, depending on your deployments they could install software only intended for their office on a curricular PC. You could for instance provide IT teachers with a custom user login, with all curricular software deployed to this custom user login (still requiring admin approval if you wish).

[sonofsanta]

had a thought about deploying software to staff. In 2012 you could set deploy to users, optional install that requires admin approval. Then you staff can install software on curricular PCs if they need to.

 

Targeting these to normal staff could be messy, depending on your deployments they could install software only intended for their office on a curricular PC. You could for instance provide IT teachers with a custom user login, with all curricular software deployed to this custom user login (still requiring admin approval if you wish).

 

I don't want to get into custom logins and what have you but there are two options that would be worth a bit of effort to get working:

1) All users can access Software Center, but installing anything prompts for an admin login (to be tapped in by $ITperson)

2) Domain admins can access Software Center and install stuff for all users

I suspect the latter is true anyway, but I've only deployed FEP so far which works differently to normal packages in 2012 so not sure. If we could get the former working, though, it would make random software requests much easier to deal with.

[Theblacksheep]

I don't want to get into custom logins and what have you but there are two options that would be worth a bit of effort to get working:

1) All users can access Software Center, but installing anything prompts for an admin login (to be tapped in by $ITperson)

2) Domain admins can access Software Center and install stuff for all users

I suspect the latter is true anyway, but I've only deployed FEP so far which works differently to normal packages in 2012 so not sure. If we could get the former working, though, it would make random software requests much easier to deal with.

 

1 wont work. 2 will but here here's a bit more on how 2012 works and you might find some other ways that'll suit you:

 

Everyone has access to software center. Not much you can do about that.

 

2012 Clients can have 4 install settings: all users, admins, admins and power users, no-one.

 

If you target users rather than computers, you can use approvals. With approvals you can target everyone and allow everyone to install but you'll still have to approve/deny the installs. Without approvals (only machine targeting), you are limited to the 4 basic client settings.

[sonofsanta]

Everyone has access to software center. Not much you can do about that.

 

Redirected Start Menu & Desktop. Already solved

 

2012 Clients can have 4 install settings: all users, admins, admins and power users, no-one.

 

If you target users rather than computers, you can use approvals. With approvals you can target everyone and allow everyone to install but you'll still have to approve/deny the installs. Without approvals (only machine targeting), you are limited to the 4 basic client settings.

 

I suspect it will still be easier to target machines, with both our current way of working and the timetabling. For those programs that will deploy from SCCM I'll set up a security group; if a computer needs software adding, it can just be added to the group and restarted. Which is much as we deal with it now, through group policy and MSIs, so it's not a great loss, just would've been nice to have A Better Way.

 

Cheers!