I am hoping some of the intelligent folks on this forum can help me out! I am having some issues with the MDT bundle (MDT 3.2) while trying to use the OS Deployment and Bare Metal Imaging portion for capturing an image. My server/console version is 9.0.787.0, the OS we are running and trying to capture is Windows 7 x64.. I have browsed the forums and come to the conclusion that the full bundle is not being uploaded to the server. The bundle size that has uploaded is 94 kb, but when I look at the bundle where it resides, it is 700 kb (EDIT: typo, it is 700Mb, not 700 Kb). I ran into issues early on with HBSS modules and AV blocking the creation of the bundle, but have since built a VM with no AV or HBSS modules and used it to create the bundle successfully. I also used this VM to upload the bundle. With the bundle uploaded as it is (94 kb) an image capture task fails every single time at the bundle upload portion. Any idea what I might be missing? Thank you in advance for your time.
Pinned topic MDT 3.2 Upload Issue
francesco.latino 060001FV4S54 Posts
Re: MDT 3.2 Upload Issue2014-01-09T16:39:59ZThis is the accepted answer. This is the accepted answer.
I think your MDT Bundle folder (the one being uploaded) is smaller than expected (700Kb is small, the MDT Bundle contains WinPe engines which takes some hundreds of MBs)
May you please go on the machine where you saved, unzipped and started the MDTBundleCreator tool, and can you please check the output folder after the MDT Bundle creation process (see parameters.ini for output folder in case you customize it).
I am interested in looking to the output folder (usually c:\BigFixOSD\MDTBundle\Content\Deploy)...you may send us a recursive listing if you want
Re: MDT 3.2 Upload Issue2014-01-09T16:51:14ZThis is the accepted answer. This is the accepted answer.
Re: MDT 3.2 Upload Issue2014-01-09T17:00:58ZThis is the accepted answer. This is the accepted answer.
Update...the above MDT bundle size of 700kb is incorrect, it was a typo. The actual bundle size (c:\BigFixOSD\MDTBundle\Content\Deploy) is 708 MB. My apologies!
Re: MDT 3.2 Upload Issue2014-01-10T16:01:20ZThis is the accepted answer. This is the accepted answer.
- jaxon1234 270005CA5Q
to verify that the bundle upload had no errors, could you please send the logs of the IEM console where the bundle has been uploaded? They are on the computer where the console is running in the folder %temp%\OSDeployment.
Could you please also check if the green arrow in the Upload MDT Bundle dashboard, in the entry related to the MDT bundle, warning that the MDT bundle upload is still running, disappeared?
Re: MDT 3.2 Upload Issue2014-01-31T15:12:09ZThis is the accepted answer. This is the accepted answer.
- sergio.tarchi 270000FFGT
Good morning all. Sorry for the delayed response. Looking at the console, the green upload arrow is still present. There are two uploads...the MDT and OS Resource. I have tried multiple times to upload the bundle and given it several hours to several days each time, butthe green upload arrow still persists. There did not appear to be a log at the location you specified.
Re: MDT 3.2 Upload Issue2014-02-17T08:30:40ZThis is the accepted answer. This is the accepted answer.
- jaxon1234 270005CA5Q
Hi, could you please look at the following technote to see if it helps?
Re: MDT 3.2 Upload Issue2014-03-06T12:49:48ZThis is the accepted answer. This is the accepted answer.
Good morning Sergio. So I was finally able to figure out most of my issues. I started over at scratch with building the bundle and while doing so I learned that the ISO file you reference in the parameters.ini file has to be at the same Service Pack level as the image you are trying to capture/deploy. So I created a new iso with SP1 slipstreamed. Since I was creating the MDT bundle on a VM that had zero HBSS modules or AV installed, when I ran into the same issue with the MDT bundle not uploading again, I turned off AV on the BigFix server itself. Once I did this the bundle uploaded in a matter of minutes and I was able to capture an image.