Starting MDT Media Update Opened the media deployment share. Folders to be copied to the media deployment share: 6 Copied: DS003:\Selection Profiles Copied: DS003:\Selection Profiles with Replace option Copied standard folders. System.Management.Automation.CmdletInvocationException: The file 'C:\Users\USERNAME\AppData\Local\Temp\MDTUpdate.396\Mount\windows\system32\winpeshl.ini' already exists. ---> System.IO.IOException: The file 'C:\Users\USERNAME\AppData\Local\Temp\MDTUpdate.396\Mount\windows\system32\winpeshl.ini' already exists. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at System.IO.File.Copy(String sourceFileName, String destFileName) at Microsoft.BDD.PSSnapIn.PEManager.IncludeDart8(String dpPath, String architecture) at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName) at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord() --- End of inner exception stack trace --- at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context) at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
i have read about this issue in this forum topic: http://social.technet.microsoft.com/Forums/en-US/mdt/thread/61a44cb1-1379-4668-bb8f-6ecae3665e66
the thing is that the solution provided does NOT work... i have done all of the following:
- my installation is from start a fresch start with 2012u1, ADK and WAIK and all other tools needed
- complete removal of all WIM-files mounted with IMAGEX (just in case)
- complete clean-out of TEMP-folders (as this is on the error-message)
- new destination folder never before used
- as clean as possible Media content (no drivers or anything)
- recreating the error by completely recreating the Media-job
- logging on to server using local administrator account
i am still nowhere close to find a solution, and we really need the USB-media in order to provide re-imaging possibilites in sites with no or very slow LAN-connections
anyone have any ideas? the one and only idea in my head is lack of diskspace in either location as i have no idea how large the ISO-file will become and have seen frightening examples up to 32 GB... but should that really create an error message like the one i get?