But then you get no accurate reporting. Typos courtesy of Apple. Sent from my iOS device.
On Aug 22, 2013, at 8:55 PM, "Trevor Sullivan" <[email protected]<mailto:[email protected]>> wrote: So, the answer to the problem (of msiexec still returning 3010) would be to wrap the command in a batch file, and after the call to msiexec.exe, just do: exit 0. That should prevent the ConfigMgr client, or the task sequence engine, from automatically restarting the computer when it sees a 3010. As far as I know, this would normally only happen from a task sequence, but it’s worth testing as an Application or Package/Program as well. Cheers, Trevor Sullivan <image001.gif><http://trevorsullivan.net/> <image002.gif><http://twitter.com/pcgeek86> <image003.gif><http://facebook.com/trevor.sullivan> <image004.gif><https://plus.google.com/106658223083457664096> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, August 22, 2013 8:26 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Computer Restart Great point Phil. That should have been number 4 on my list below. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, August 22, 2013 6:35 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Computer Restart It should also be pointed out that removing the return code actions and essentially ignoring Windows Installer’s decision to require a reboot may leave your client in a state where they cannot install any other apps until the machine has rebooted. If your clients go extended periods of time without rebooting their systems, this can become very problematic. The /norestart or REBOOT=ReallySuppress doesn’t keep msiexec from returning a 3010 and flagging a pending reboot action, it just prevents msiexec itself from initiating the reboot. So I guess tread carefully with suppressing the reboots this way. -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, August 21, 2013 11:41 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Computer Restart Three things to note here: - It’s REBOOT=REALLYSUPPRESS not /REBOOT=REALLYSUPPRESS The slash would mean that REBOOT is a switch for msiexec which it is not; it’s a public property that the MSI itself uses to dictate the reboot behavior (this leads to the next point) - It’s the MSI itself that dictates the reboot based upon the value of this property which can actually be overridden by a custom action or explicit setting of the value within the MSI itself or perhaps not even honored if the MSI itself wished not to reboot or force a reboot despite this setting. - /norestart was added with Windows Installer 3.0 and thus is just not commonly used. It is exactly equivalent to REBOOT=ReallySuppress J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, August 21, 2013 9:40 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Computer Restart I remember when this issue was first reported, and I have always wondered, why use /REBOOT=REALLYSUPPRESS when you could just as easily use /norestart? Is there a difference from an .msi perspective? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ryan Sent: Wednesday, August 21, 2013 10:25 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Computer Restart Eventually it would see the application as installed from the detection criteria, it just might take a week. :-) On Wed, Aug 21, 2013 at 9:18 AM, Stephen Leuthold <[email protected]<mailto:[email protected]>> wrote: I've seen a few suggest removing return codes. Wouldn't CM consider it a failed install if it sees a return code other than what's defined in the deployment type? The 1e blog post has worked the best for me in the past. Sent from my Windows Phone ________________________________ From: Johan van Dijk<mailto:[email protected]> Sent: 8/20/2013 3:55 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Computer Restart Remove the exit code (probably 3010) From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Taxter, Latisha Sent: Tuesday, August 20, 2013 10:46 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Computer Restart How do I get around a computer restart on the client. My computer restart settings on client settings is set to 90 mins, but I want to have my application not restart. I have msi pushed with REBOOT=ReallySupress. The user is warned that the system will restart in 90 mins. Is there any way to override this on the application push? Thanks. Latisha Taxter Network Analyst IRM, Inland Northwest Health Services Spokane, Washington 99201 [email protected]<mailto:[email protected]> • 509-232-8235<tel:509-232-8235> È509-953-9085<tel:509-953-9085> http://www.inhs.org The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
<<inline: image001.gif>>
<<inline: image002.gif>>
<<inline: image003.gif>>
<<inline: image004.gif>>
