I hope you can help me because I am pulling my hear out on this subject.
My employer chose to use BigFix to deploy windows images in the organisation.
I am familiar with MDT and hoped that wold help- didn’t help so far.
The steps I have taken so far are:
Uploaded ISO of windows 7 & windows 10
Uploded co-respondig drivers for the models I am testing on
install MDT bundle and all its prerequisites
Added records: 60 & 43 on the DHCP to enable the PXE
I am straggling with the MDT bundle. It does not create the folder structure it supposed to.
The “Deployment Share\Operating systems” folder is empty.
The “Deployment Share\Control” folder is full but the folders names look like this:
“D_W7X64_01” instead of “W7X64”
The MDT Bundle structure that you found derives from having created the bundle using the OSD MDT Bundle Creator.
If the MDT Bundle has been created via the OSD MDT Bundle Creator, the folders in “Deployment Share\Control” are a bit different. They are named like C_W7X64_01 and D_W7X64_01 where C and D stand for Deploy and Capture respectively. According to the OSD flow a different task sequence will be used.
To populate the folder “Deployment Share\Operating systems” you need to leave the default option in the MDT Bundle Creator wizard “Create both MDT Bundle and OS Resources” and then specify at least a path for either an iso image or a folder containing iso images.
A clarification regarding my comment about os resources.
I was referring to the following path: “MDTBundle\Content\Deploy\Operating Systems”, but you mentioned a different path so not sure if my reply is helpful for this point.
If in the MDT Bundle Creator wizard you used the option “Create both MDT Bundle and OS Resources” and you specified a valid path for the iso image (located in the creator machine or in a network shared path), then you should find the OS resource here:
C:\BigFixOSD\MDTBundle\Content\Deploy\Operating Systems
Whereas if in the creator wizard you specify the option “Create new OS Resource only” you will find the OS resource in a path like this one:
C:\BigFixOSD\W2012R2X64SP0
If you cannot find the created os resources, then check the task status in the BigFix console. I expect it failed. In this case investigate the error in the log: C:\OSDSETUP\MDTBundleCreator\LastRunLog (in the creator machine).
Consider that there is another way to import an OS resource in the environment. In the Image Library when you import an image from Installation Media, if the related OS resource has not already been uploaded then the UI will show a checkbox to import also the OS resource.
Its not there, I suspect that the issue run dipper.
I did not implement the rest of BigFix, only the imaging part.
Our “\BigFixOSD” folder in under D.
When I use the wizard to install MDT bundle creator I dont see an option for OS resources files.
When I use the bundle creator itself I only have the : parameters.ini file to customize.
In the “\OSDSETUP\MDTBundleCreator” folder I don’t have “LastRunLog” - I have setup.log.
MDT bundle creator is version: 3.9.01
Bare metal server version is: 7.1.1.20
Maybe that the issue?
Instead of the MDT bundle creator- do I have a wizard that I can download from somewhere?
After you created the MDT Bundle Creator via the OSD wizard, in the same dashboard in the BigFix console you can create the MDT Bundle and/or the OS Resources. In the “Available MDT Bundle Creators” section select a target and then the button “Create MDT Bundle”.
Only if you use the OSD wizard you have the LastRunLog.
Your advise helped a lo! thank you.
but the issue that got me here still exists.
When I try to edit the unattend.xml file for windows 7 deployment task sequence (MDT workbench) - I get the following error:
“Path ‘C:\BigFixOSD\MDTBundle\Content\Deploy\Operating Systems\W7X64\install.wim’ does not exist.”
The file is not there. its not in the “C:\BigFixOSD\MDTBundle\Content\Deploy\Operating Systems\W7X64SP0\sources” folder as well.
I do have the file boot.wim in the sources folder.
Should I add the file “install.wim” manually?
I added the install.wim file manually & changed the folder name from “W10X64SPO” to “W10X64” and it working.
The names are probably used in other situations?
It does not look like the best way to solve it…
Any thoughts?
I do not think that install.wim is supposed to be moved or a folder to be renamed. A MDT bundle created via OSD can be customized using the MDT workbench but I would not apply the same changes you did on a MDT created outside OSD.
Could you please better explain exactly what you are doing?
For a standard installation with OSD you do not need to customize the MDT bundle. Create the bundle (with os resource if not already imported), import this bundle and then create a Bare Metal profile that contains that bundle. PXE boot the target and select the bare metal profile to be deployed. Does this flow work?
Hi,
you can edit the unattend.xml file, but it is an activity that may bring you to failure during deployments (both New Computer and Refresh types). If you want to do that, my suggestion is to
create a MDT Bundle with official steps described in user guide
apply changes to unattend.xml (remember that import to Big Fix server is performed from C:\BigFix OSD\MDT Bundle\Content\Deploy; then be sure to customize files in this path)
