SCCM - Software Allocation question

[CyBeRkId2002]

Hi all,

 

Is there a way to use SCCM like WPKG in getting all Applications/Packages to install at boot before the user can log-on. Can see it causing a lot of confusion for us at rebuild time if people are logging on too soon and half the software is missing etc.

 

Cheers,

Michael

[AngryTechnician]

Pretty sure SCCM doesn't work like that. This is however the way the GPO Software Installation works, so for packages that install using an MSI that could be an option.

 

Peronsally I just put an 'out of use' sign on machines while they are rebuilding. Doesn't work if your users are morons, however.

[FN-GM]

Hi all,

 

Is there a way to use SCCM like WPKG in getting all Applications/Packages to install at boot before the user can log-on. Can see it causing a lot of confusion for us at rebuild time if people are logging on too soon and half the software is missing etc.

 

Cheers,

Michael

 

You can install it during the image process if using OSD but you can't do it at boot.

[gshaw]

This is the biggest weakness of SCCM and I'm amazed MS didn't sort it in the 2012 release. If old-school GPO deployment can install applications at boot why can't their flagship management product?!

 

Had some problems with doing an Office 2007 > 2010 upgrade because of this... disabled every user control and left the status bar showing but people still shut down their machines while the installation was in progress! Would be easy to blame the users for this but (imo) an enterprise-level software deployment tool should at the very least lock the workstation or deploy at boot time before the user sees the logon screen.

[FN-GM]

This is the biggest weakness of SCCM and I'm amazed MS didn't sort it in the 2012 release. If old-school GPO deployment can install applications at boot why can't their flagship management product?!

 

Had some problems with doing an Office 2007 > 2010 upgrade because of this... disabled every user control and left the status bar showing but people still shut down their machines while the installation was in progress! Would be easy to blame the users for this but (imo) an enterprise-level software deployment tool should at the very least lock the workstation or deploy at boot time before the user sees the logon screen.

 

We set the maintenance window when the school is physically closed then shut the machines down when finished

[gshaw]

We set the maintenance window when the school is physically closed then shut the machines down when finished

 

Assuming all the machines are on (WoL only helps if the plugs don't get turned off as well lol)

 

Just seems like a realy kludge to something that should be a simple process