WIM files and FOG
-
Now to test deploy your image.
- Create a new VM with similar characteristics (the same not required).
- PXE boot the VM and register it with FOG.
- Power off the target VM.
- Go into the FOG GUI and associate the new target VM with the image you captured in the previous post.
- Now go into basic tasks and schedule a deployment.
- PXE boot the target computer. It should start deploying right away.
- At the end of imaging the target computer will reboot and it “should” start windows OOBE right away.
-
I pxe booted and got this error now… this is on the new VM
… not having any luck today. Please see the link below. -
@dhruvin-t First question where the heck did the FOS image bzImage4134 come from? This should be just bzImage. Is this a new FOG install?
-
@george1421 said in WIM files and FOG:
@dhruvin-t First question where the heck did the FOS image bzImage4134 come from? This should be just bzImage. Is this a new FOG install?
a wiki mentioned to update the firmware and when doing so, you have to give it the latest firmware name. hence 4.13.4 > 4134
-
hey George
first of all I want to thank you for going above and beyond yesterday to help me out with the issues. I got the image to sysprep today after it was failing yesterday and it turns out that because Twitter and Facebook were installed, it failed to sysprep. After uninstalling those apps, I was able to kick it off. After it shut off, I created the capture task on the web portal and pxe’d the VM. It successfully captured the image and now am able to see the image on the web portal.
My next step is to test out the image by deploying it to a fresh VM. After the test, next steps would be to go through and figure out the driver issue. If the image deployments succeed, I was going to build a new reference image in the MDT like we did yesterday but way more detailed and options to join the PC to the domain. What do you think about my plan?
Again I want to thank you very much for helping out yesterday.
-
@dhruvin-t Your plan sounds solid. As we discussed yesterday you can either have the unattend.xml file connect the computer to AD or you can have the fog client connect the target computer to AD.
In my case I let the unattend.xml file do it. The reason is our AD is a bit complex. So all of our computers don’t go into just one OU. The OU is dynamically calculated based on the subnet where the computer is being installed to, what the image type is (office, vs lab), what type of device it is tablet, laptop, desktop, server. All of that info is calculated to produce the OU and computer name. All of this magic is done in a FOG post install script (what you haven’t done yet) and then the product of the calculations are used to update the unattend.xml script.
Here is one on setting up for driver injection, it is Dell centric. It CAN be used for other system too.
https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injectionThis one here is a bit more advanced. The interesting points are the sed script to change the host name and OU by patching the unattend.xml file during the post install script.
https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-scriptSome other of my tutorials you might want to read is:
PXE booting into the MDT ISO image(that iso that we copied from the MDT server to your VM Host can be pxe booted from FOG)
https://forums.fogproject.org/topic/6284/booting-mdt-2013-litetouch-with-fog -
@george1421 Unfortunately with all those scripts, I kind of got lost and didnt want to break anything. So my plan is to specify a network share location within the unattend file for the drivers and call it a day. Now do I need to do anything post imaging in FOG to have it call the unattend file or does windows automatically get the unattend file and launch it?
-
@dhruvin-t The unattend.xml file is called by windows OOBE before it starts. Thats why you placed it in the /Windows/Panther directory. That is the first place OOBE looks for the file. It will be automatically loaded if found.
-
@Dhruvin-T Any news on this? Can we mark this solved?
-
@sebastian-roth Hello yes you can mark this as solved! I also want to point out that @george1421 has been great help with my troubles with getting Fog to work. He went above and beyond to help me get sorted. Really appreciate the hard work you all are doing! Thank you once again and happy holidays!
