Will auto-upgrade still work if the clients are several versions behind? From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, March 16, 2016 6:28 AM To: [email protected] Subject: Re: [mssms] Client upgrade deployment reporting as failure
This is known behavior because you are using the client agent to upgrade itself and so the reporting mechanism for this doesn’t always work well. That’s why auto-upgrade is so much better. Why do you want to micro-manage the process though? J From: <[email protected]<mailto:[email protected]>> on behalf of Nag P <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Wednesday, March 16, 2016 at 6:02 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [mssms] Client upgrade deployment reporting as failure Hi, Recently we upgraded SCCM to R2 SP1 CU3 and now planning to upgrade clients using software distribution. We are not using Auto client upgrade because we want to schedule client installation on few machines at a particular time. I have created a package and deployed on few test machines but i see the status as Program failed (unexpected restart) but client installation is successful. Package we used is standard one with default parameters. I think this is expected behavior as ccmexec gets restarted during the upgrade process. Is there any way to get the deployment status as successful when the installation is is completed.
