If you're using ConfigMgr 2012 applications, you can configure your
application so that
ConfigMgr client will force a reboot. This way, the machine reboots and
continues
executing the task sequence after that.
-T
On 5.4.2014 12:26, Ranvir singh wrote:
due to some process constraints i cont change the program or source of
that package..
Is their any way to suppress the restart settings in task sequence
itself.. or if i add any variable in TS is it possible
On Sat, Apr 5, 2014 at 1:24 PM, David O'Brien
<[email protected] <mailto:[email protected]>> wrote:
Tell the application to suppress the restart.
Don't ever let an application restart without you explicitly
telling it to do so...
Sent from my Windows Phone
------------------------------------------------------------------------
From: Ranvir singh
Sent: 5/04/2014 5:41 PM
To: [email protected] <mailto:[email protected]>
Subject: [mssms] OSD custom task sequence to skip the restart (3010)
Hi All,
I have a custom task sequence which have 5 applications ..
When I deploy the task sequence to the machine, 2nd sequence
application getting rebooted with 3010.. So How I can skip the
reboot,When it executed with error 3010..
Ideally I want to restart the machine after all 5 application
installed, not after 2nd application installed..
How i can achieve with Task sequence
