How are you changing the exit code? Can you provide an example? Thanks!
From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Johns, Damon (DoJ) Sent: Friday, May 6, 2016 1:42 AM To: ms...@lists.myitforum.com Subject: [mssms] RE: Updating Surface Pro 4 firmware during OSD I deploy it them as an app using the MSI that Microsoft provides for existing Surface 3 and 4 devices. When we do builds / refreshes I have a step in my TS that runs the same MSI application which applies the latest drivers & firmware. Be aware though that you need to change the exit code for the application as by default it's a hard reboot. I've also seen bitlocker recovery keys being triggered with the Surface 3 when you apply firmware updates using this method, I don't know if this is being experienced elsewhere, I have seen it a few times in my organisation - maybe 2 or 3 out 100 updates. Cheers Damon From: listsadmin@lists.myitforum.com <mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Murray, Mike Sent: Friday, 6 May 2016 9:31 AM To: ms...@lists.myitforum.com <mailto:ms...@lists.myitforum.com> Subject: [mssms] Updating Surface Pro 4 firmware during OSD I'm curious how you are handling the firmware updates. Do you apply them like drivers during the TS or do you import them into the boot image instead? I'm reading different things, looking for best method. Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 <mailto:mmur...@csuchico.edu> mmur...@csuchico.edu _____ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
smime.p7s
Description: S/MIME cryptographic signature
