Nope, that was not it. I was hopeful. I have noticed that when it does reboot it run chkdsk. Is it possible that sysprep is messing things up? I am doing this for Windows 7 x64.
From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Monday, September 28, 2015 10:27 AM To: [email protected] Subject: [MDT-OSD] RE: Build and capture logs Make sure you are using fixed disks, not dynamic or dependent. Only other thing that comes to mind. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Monday, September 28, 2015 11:20 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Build and capture logs That does not work either. Just reboots. I am doing this on Hyper-V VM's. I have tried 3 different ones and same result when scanning Volume 2 of 2. That makes me wonder if there is a bug or something somewhere. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Friday, September 25, 2015 3:27 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Build and capture logs Hmm, yeah that's a new one. Sounds like maybe a hardware failure. Try opening the cmd prompt with F8 and see if it prevents the reboot. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Friday, September 25, 2015 3:45 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Build and capture logs Will put the errordialog timeout on the list for Monday. I am not sure it will work though as I can sit here and watch it and that dialog never pops up. It says scanning volume 2 of 2 for the capture, then just reboots and does not ever capture the volume. This is one problem I have never seen before. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Friday, September 25, 2015 2:26 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Build and capture logs You can copy the 'Copy Logs' step from a deploy task sequence, just set the SLSHARE variable. For the delay on errors, set the SMSTSErrorDialogTimeout variable, by default its 15 minutes. We set ours to 1 day. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Friday, September 25, 2015 1:58 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Build and capture logs That is the thing, when it blows up, I am not sure it will even copy logs, it just reboots. How do you make it wait on errors? Never have done that before. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Friday, September 25, 2015 12:33 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Build and capture logs It does the capture in WinPE, so the logs get wiped because they are stored on X:\. Setup your B&C to wait on errors, or copy the logs off before the reboot. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Friday, September 25, 2015 1:05 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Build and capture logs When you are doing a build and capture where are the logs stored? My TS starts to capture the images and does volume 1 and then blows up on volume 2 and quits the whole capture process. Trying to figure out where the problem is logged. If I try and get into the OS after all of this, the circle starts over again! 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. 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. 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. 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.
