(imported comment written by SystemAdmin)
Hmm that is so bizarre. Okay, try this, go into your server where it stores all the files that we upload (e.g. C:\Program Files\BigFix Enterprise\BES Server\wwwrootbes\Uploads) and the zipped file will be in the sha1 folder indicated in that second sub-action that you took.
Try unzipping that manually, or even just opening it to see if the file exists within the zipped folder.
(imported comment written by SystemAdmin)
I opened up the SHA1 value and the bootmgr file does not exist in the zip file. Do you think I should try uploading the MDT Bundle with AV turned off? what else would cause the two bootmgr files (x86 and x64) to not upload.
(imported comment written by SystemAdmin)
yes, try with AV turned off⌠I canât think of anything else that would prevent those files from being zippedâŚ
(imported comment written by SystemAdmin)
I tried turning the AV off when uploading the MDT Bundle and redeploying the image and the same thing happened. I did notice that the SHA1 value appears to be the same for the upload after recreating the MDT Bundle. I thought that was weird so i deleted the MDT Bundle again from the dashboard, deleted the folder in the Uploads directory, turned off AV again and uploaded the MDT Bundle via the dashboard. Once again the SHA1 created for the MDT Bundle is the same. I checked the new MDT Bundle from the Upload folder and once again the bootmgr files are missing.
One thing that I did notice is that on the main server and the deployed endpoints I have the âshow hidden files and foldersâ selected and the bootmgr files do appear to be hidden. Could the upload not be working for these files because the files are hidden?
just brainstorming ideasâŚ
Can I just open up the zip file from the the upload directory and add those two files? I would guess no since the file size would change and cause the check to fail.
(imported comment written by SystemAdmin)
Hi there,
Was trying to follow this thread and have a couple questions that I did not see the answer too.
When you upload the bundle, are you running the console on the same system as where you created the bundle?
What path do you specify in the âUpload MDT Bundleâ dialog?
I am currently able to create the bundle and use it to deploy a Win7 x64 captured image with no issues.
One difference I see is the bundle version info, but not sure if that is an issue or not.
MDTBundleCreatorVersion=3.0.55
WAIKVersion=6.1.7600.0
MDTVersion=5.1.1642.1
RBAgentVersion=7.1.111.19017
Martin Carnegie
Gulf Breeze Software Partners
(imported comment written by SystemAdmin)
We run the console off of Terminal Servers to limit the number of Consoles deployed but if that could be causing issues I can try the upload from the workstation the MDT Bundle was created on.
On the third post on this page of this thread I updated the MDTBundleCreatorVersion and it looks the same as what you are showing.
I uploaded an existing WIM file using the Import Image tool and am trying to deploy that. Do you think it is better to try deploying an image using the Capture Images wizard? I know this WIM file is good as it works in our existing Altiris environment.
(imported comment written by SystemAdmin)
Hey again,
So at this point, it is still not clear why the files go missing when attempting the upload. I donât think the visibility of the files are an issue here (since we cannot reproduce here in the lab).
For future tests, it is enough, after upload, to check the serverâs Upload directory, drilling into the zip to see if the files are there. No need to run a full deployment job just to have it fail.
Please open a support ticket so that we can arrange a more formal investigation into the issue youâre having? Ideally weâd like to setup a live session and play around with manually uploading/etcâŚ
(imported comment written by SystemAdmin)
Here (https://www-947.ibm.com/support/servicerequest/Home.action) is the place youâll want to go to open up the PMR.
(imported comment written by SystemAdmin)
I think that the only process difference is where you copy it to the TEM server and upload. For mine here is what I do (sorry if this seems redundant, but want to make sure I note my steps):
On a Windows 7 x64 system
Activate the required analysis
Navigate to the Health Checks and remediate anything outstanding there
Install all the prereqs under the âMDT Bundle creator setupâ. The âDeploy MDT Bundle Creatorâ does not become relevant until after all the other steps are done.
Deploy the TEM Console to that system
Edit the parameters.ini file modifying the following entries
Changed the target to an alternate drive on the system with more free space
debug=1
set the proxy info for the USMT download
set media1 to the Win7 x64 SP1 iso for the image I captured
commented out the entries for the XP mass storage drivers (may enable later, but not a requirement now)
Logged on to TEM console on the same system
Navigate to Systems Lifecycle > OSD deployment and Bare Metal Imaging > Setup > Upload MDT Bundle
Press the Upload MDT Bundle button
Set the path to D:\TEMOSD\MDTBundle\Content\Deploy
Press the Upload button
I did get some error about not finding the zip.exe but that is a proxy issue that I have here. I followed the instructions on http://www-01.ibm.com/support/docview.wss?uid=swg21616689 and downloaded the zip.exe and put it into the folder %TEMP%\OSDeployment and that fixed it.
When this was all done, the uploaded MDT bundle was 384 MB, but this would vary depending on what was included for you. When I look at the D:\TEMOSD\MDTBundle\Content\Deploy folder, it is 891MB on the disk, with 2051 files.
Martin Carnegie
Gulf Breeze Software Partners
(imported comment written by SystemAdmin)
Thanks Martin.
Your steps are exactly correct. I am running under the assumption that BFAdminCEC is also correct in the steps that he took (BFAdminCEC you should verify that) and that something screwy is happening (perhaps with his environment).
(imported comment written by SystemAdmin)
I will try recreating the MDT Bundle again and upload from the same workstation to see if that is the issue, i was copying the MDT Bundle from the workstation that I created it on to the primary TEM Server as I did not have the console installed on that machine. If following those steps I continue to have issues I will open up a PMR.
(imported comment written by SystemAdmin)
I think at one time I was trying to upload the bundle on the TEM server but had some issue that that think was due to missing one of the prereqs for the bundle creator. That was a while ago so I do not recall the exact details.
Martin Carnegie
Gulf Breeze Software Partners
(imported comment written by SystemAdmin)
When this was all done, the uploaded MDT bundle was 384 MB, but this would vary depending on what was included for you. When I look at the D:\TEMOSD\MDTBundle\Content\Deploy folder, it is 891MB on the disk, with 2051 files.
I am guessing that something is wrong with what I am doing or with the upload, the MDT Bundle that I keep uploading appears to only be 78.5 MB in size which is significantly less than what you see. When I look at that same folder the size is 1.17 GB with 2924 files.
I am going to open up a PMR today and will update this forum with the end result (in case others come across the same issue).
Thanks for the help everyone offered.
(imported comment written by SystemAdmin)
Just to follow up on this issue, it appears the issue with the MDT Bundle upload was due to certain files being hidden and not successfully uploaded into the server. The OSD site was updated to allow hidden files to be uploaded as well and the deployment process is working better now, just fighting other issues that are unreleated.
Thanks again for those that helped.