A few times over my career, ive run into certain situations where an application is always running and does not have a nice method of shutting itself down in order to update or install. An example of this is a data terminal in a police car, or a kiosk run by a government department…. both of which have been cobbled together with a mixture of open-source tools, custom code and random other bits. (I have dealt with both of those)
Most of the time, this can be scripted or programmed around…. sometimes it cant (or maybe can’t with my scripting ability!)…. but i’ve always considered SCCM as a deployment infrastrcuture (and a good one) – it doesnt magically make deployments happen (like some people seem to think) – but its gives you all of the tools to target very specific machines/users (via query based collections) and at an appropriate time (via deployment or advertisement scheduling). So why am i having to write code for something the tool could far better than i ?
But….. there is a gap in there…. as any SCCM people will know, we can schedule the deployment + add in a criteria of “only if the user is logged on”, “only if the user is not logged on” or “whether or not the user is logged on” – and the last option accounts for a good 99% of all deployments that we have ever done…. however, “only if the user is not logged on” relates to starting the program only, not completion of the package install….. therefore if a packages takes a long time to install, it may still be running while someone logs on. Additionally, if a machine is set to autologon and start up and application (such as the police car example) – then a time when the machine is logged off (and the sccm client is running) simply does not exist.
I dont seem to be alone in thinking this is an issue – this poor guy over at the technet forums got the usual “people not quite understanding where he’s coming from” thing that the technet forums seem to have – http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/abdf134b-7be2-4bdd-b025-dc5b2e5ff9da
Dont get me wrong, the responders are completely correct… but why is there no-one just agreeing with the guy ? Where’s the “maybe we should consider putting that into the next version of our product” response ? Suggesting to log a DCR is all good, but i have about as much faith in that process as i do PSS.
Anyhoo – while i think thats relevent to show the combative, instead of collaborative mindset, its not productive….
SCCM (in my opinion) is about providing an awesome toolet to administrators to enable deployments with less effort and more flexibility. I would really like to see an option
“Install when no user is logged on – and prevent user from logging on until install is complete” or
“Install after user logoff – and prevent new user logon until install is complete” or
“Install at next reboot – and prevent user logon until install is complete”
They seem to me like relatively small additions….