PolicyPak CSE Installation using SCCM without forced reboot
2 posters
Page 1 of 1
PolicyPak CSE Installation using SCCM without forced reboot
I'm not sure what I'm missing for this so I thought I'd ask. I am trying to push out the CSE software using SCCM, but once it installs it reboots the machine immediately. I've tried adding the /promptrestart option of msiexec, but that didn't help either. I want it to prompt to restart and let SCCM/the user decide when to reboot. Is there a switch or setting I'm missing? My next step was to modify the MSI using Orca, but thought I'd look for an easier option first.
Thanks in advance,
Kenny
Thanks in advance,
Kenny
kjseever- Posts : 2
Join date : 2013-03-28
MSIs / installing
I'll try to find out if there's a supress reboot switch.
But.. the good news is.. NEXT version has NO reboot requirement.
Just install.. and.. it instantly starts working.
Coming soon.. really soon..
But, for build 537.. hang tight until I can research your question. Thanks.
But.. the good news is.. NEXT version has NO reboot requirement.
Just install.. and.. it instantly starts working.
Coming soon.. really soon..
But, for build 537.. hang tight until I can research your question. Thanks.
jeremym- Posts : 82
Join date : 2013-01-29
Location : Philadelphia
MSI Switches
I haven't tested it, but I was just told that
/norestart /quiet
ought to make it, well.. not restart and quietly install.
Please let us know your progress here.
Thanks.
/norestart /quiet
ought to make it, well.. not restart and quietly install.
Please let us know your progress here.
Thanks.
jeremym- Posts : 82
Join date : 2013-01-29
Location : Philadelphia
Re: PolicyPak CSE Installation using SCCM without forced reboot
Thanks for the reply. I tried adding those switches, and it did install without rebooting. Unfortunately it also doesn't notify SCCM or the user that a reboot is required so they won't know to reboot, nor will it reboot during a maintenance window. I tried using the /quiet /promptrestart switches, but then it was back to auto restarting.
In terms of the next release, is really soon a matter of days, weeks, months? If it's soon enough I'll put of deploying for a little while.
Thanks again,
Kenny
In terms of the next release, is really soon a matter of days, weeks, months? If it's soon enough I'll put of deploying for a little while.
Thanks again,
Kenny
kjseever- Posts : 2
Join date : 2013-03-28
Next version.
Days.
So, stand by.
There's even some built in reporting you can see (without SCCM) to verify it's actually installed.
The target reporting directory DOES need to be set up in advance. Video here: http://www.policypak.com/videos/ac6d9hnteq
So, stand by.
There's even some built in reporting you can see (without SCCM) to verify it's actually installed.
The target reporting directory DOES need to be set up in advance. Video here: http://www.policypak.com/videos/ac6d9hnteq
jeremym- Posts : 82
Join date : 2013-01-29
Location : Philadelphia
Quick Followup for future SCCM deployers
When you use
- Code:
REBOOT=ReallySuppress
It appears that SCCM will do what it's supposed to do; which is:
1. Deploy the CSE and
2. NOT request / require a reboot.
Again, this starts with builds 545 and later.
jeremym- Posts : 82
Join date : 2013-01-29
Location : Philadelphia
Similar topics
» PolicyPak for offline PC
» Updating the PolicyPak License GPO after renewal
» PolicyPak not funtioning with Windows XP
» Nothing in my programs menu after installing policypak admin console
» Get error when exiting IE 10 or 11 after install of PolicyPak CSE Setup x64.msi build 605
» Updating the PolicyPak License GPO after renewal
» PolicyPak not funtioning with Windows XP
» Nothing in my programs menu after installing policypak admin console
» Get error when exiting IE 10 or 11 after install of PolicyPak CSE Setup x64.msi build 605
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum