Just be aware that some of the surface devices will show up with a "manufacturing defect" where the model will be "O_E_M_C_" instead of surface. When this happens the MSI will not install because it will only install when the model is the correct "Surface Pro 3" In that case you have to use the PS script to install the drivers. Once the PS installs the drivers, WMI will start reporting the correct Model
Select Distinct Manufacturer0, Model0 >From v_GS_COMPUTER_SYSTEM Where Manufacturer0 Like '%Microsoft%' On Fri, May 6, 2016 at 4:27 PM, Bradley, Matt <[email protected]> wrote: > The default entry in that Return Code tab, for code 1641 calls for a Hard > Reboot. Edit it to the behavior you desire, in this case, Success (No > Reboot). > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Murray, Mike > *Sent:* Friday, May 6, 2016 12:35 PM > *To:* [email protected] > *Subject:* RE: [External] [mssms] RE: Updating Surface Pro 4 firmware > during OSD > > > > What return code would I expect? > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Bradley, Matt > *Sent:* Friday, May 6, 2016 10:25 AM > *To:* [email protected] > *Subject:* RE: [External] [mssms] RE: Updating Surface Pro 4 firmware > during OSD > > > > You don’t change the exit code itself, you change how SCCM reacts to it. > Go to the app > deployment type > properties > Return Code tab. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Murray, Mike > *Sent:* Friday, May 6, 2016 10:33 AM > *To:* [email protected] > *Subject:* [External] [mssms] RE: Updating Surface Pro 4 firmware during > OSD > > > > How are you changing the exit code? Can you provide an example? Thanks! > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Johns, Damon (DoJ) > *Sent:* Friday, May 6, 2016 1:42 AM > *To:* [email protected] > *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:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Murray, Mike > *Sent:* Friday, 6 May 2016 9:31 AM > *To:* [email protected] > *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 > [email protected] > > > > > > > ------------------------------ > > > 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. > > > > > > > > > >
