Looks like some weird issue with the BackupFile name, the WIM's were actually missing the .wim extension... so I think that's what kicked out the error... the latest 2012 R2 build didn't kick that error and had the right extension. So those builds must have been from yesterday and before I modified the BackupFile property again last night.
Regards, Chris Nackers From: [email protected] [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Wednesday, July 22, 2015 10:43 AM To: [email protected] Subject: [MDT-OSD] RE: Strange MDT LTI error Did you specify SLShareDynamicLogging? Sysprep disables networking, so any attempts to log to a network share between the end of Sysprep and the reboot into Windows PE will fail, logging warnings. You can avoid these by not using SLShareDynamicLogging or EventShare (monitoring) when capturing an image. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Nackers Sent: Wednesday, July 22, 2015 8:30 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: [MDT-OSD] Strange MDT LTI error I'm seeing this right at the end of my capture, the capture goes fine, I don't see anything in BDD.log, so I'm not sure what it's complaining about. I have the DeployRoot coded to the IP in bootstrap.ini, and I'm using the following to code the image path/name: SkipCapture=YES BackupFile=%TaskSequenceID%_#year(date) & "-" & day(date) & "-" & month(date)#.wim ComputerBackupLocation=%DEPLOYROOT%\Captures [cid:[email protected]] Regards, Chris Nackers
