[mssms] RE: Handling Unexpected Reboots in Task Sequences

2017-05-25 Thread Beardsley, James
Ah, good idea. I'll try that. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Gleason, Joey J. Sent: Thursday, May 25, 2017 9:07 AM To: 'mssms@lists.myitforum.com' <mssms@lists.myitforum.com> Subject: [mssms] RE: Handling Unexpected Reboots i

[mssms] RE: Handling Unexpected Reboots in Task Sequences

2017-05-25 Thread Beardsley, James
You're right, that was a mistype. I was using /norestart. Neither of them work. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Thursday, May 25, 2017 8:34 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Handling Unexpected

[mssms] RE: Handling Unexpected Reboots in Task Sequences

2017-05-25 Thread Gleason, Joey J.
I fought with that DisplayLink driver for a long time as well. Very confusing using their Enterprise MSI or the .EXE install. What I did was download the latest driver/software for it: DisplayLinkUSBGraphicsSoftwareforWindows8_1-M0.exe Once you have that, this command line worked to

[mssms] RE: Handling Unexpected Reboots in Task Sequences

2017-05-25 Thread Daniel Ratliff
The switch you want is /norestart, not /noreboot. That should do it. Daniel Ratliff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Beardsley, James Sent: Wednesday, May 24, 2017 5:46 PM To: mssms@lists.myitforum.com Subject: [mssms] Handling Unexpected