@wayne-workman Hello wayne! You were right, I was misunderstanding the storage node concept. Once I got that cleared, it was easy enough to browse through documentation to get fog switched to the mounted share properly. I just followed the wiki and it worked perfectly.
Posts made by Dhruvin.T
-
RE: cant make the presented virtual disk as a storage node.
-
cant make the presented virtual disk as a storage node.
Hello all,
I need help with making the attached virtual disk as a storage node to host all my images that I will be capturing. I have a OS drive on which ubuntu and fog server is installed. How do I make the attached virtual hdd the drive to hold my images?
-
RE: WIM files and FOG
@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!
-
RE: WIM files and 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?
-
RE: WIM files and FOG
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.
-
RE: WIM files and FOG
@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
-
RE: WIM files and FOG
I pxe booted and got this error now… this is on the new VM … not having any luck today. Please see the link below.
-
RE: WIM files and FOG
@george1421 said in WIM files and FOG:
@george1421 Actually before you sysprep the image I want you to update/modify your unattend.xml file.
Hello George, im slightly confused. Didnt you mention to not run sysprep when registering image into fog?
Also at what point do I actually start the full registration and capture to fog? And when you mentioned get my VM registered, you meant just doing pxe boot and approving the host right?
I just want to get it right this time around. Thanks for the unattend link, really helpful!
EDIT: Also, MDT says I need a .wim file to create an unattend file.
-
RE: WIM files and FOG
@dhruvin-t said in WIM files and FOG:
then sysprep the image to convert it into ISO and put it in MDT.
I mean convert it into a WIM.
Also, I still install the FOG client but disable the service when I do the capture from FOG right?
-
RE: WIM files and FOG
I have the MDT setup. However when I open it, its asking me for a wim file.
Now I downloaded a ISO image from MS licensing portal. I have been trying to use the MDT. So my thought process is as follow
Use the fresh ISO that I installed from MS and make a bare VM out of it. Install all my apps for the company on it, remove unnecessary stuff off of it and then sysprep the image to convert it into ISO and put it in MDT.
But I changed my route because my boss agreed to let me use FOG. So since you mentioned that FOG needs the image before the sysprep, I am creating this new VM so I can import the image into fog. After it gets imported into FOG, I was going to sysprep and put it in MDT. How does this sound?
You guys have been great help! Really appreciate your input and help with this.
-
RE: WIM files and FOG
I already have this setup on a dedicated beefed up box in my cubicle!! Its sitting on a win10 machine though.
-
RE: WIM files and FOG
@george1421 said in WIM files and FOG:
ipxe.efi
My current DHCP is set to undionly.kpxe. So I will change that over to ipxe.efi.
Also talking about MDT. I have the latest build MDT installed. Is there a guide you can reference for me to switch over to that methodology? My new VM is almost ready, is MDT something I install on the VM itself?
-
RE: WIM files and FOG
I think this clears up a lot of stuff. The VM was built by someone who was let go and now I am going to just rebuild the VM. I will install a fresh MS build 1709 win 10 image with a EFI setting. I will update you guys on what happens next.
Just to confirm machine should NOT be on the domain at any time right?
-
RE: WIM files and FOG
It does boot for both scenarios. I was trying to change the host management to assign the image to the host that is going to be captured but it keeps on saying “Cannot change image.
Host is in a tasking.”what does this mean?
-
RE: WIM files and FOG
No worries at all, I do have win 10 installed on the disk on the VM. Its very confusing. It wont budge!
-
RE: WIM files and FOG
@tom-elliott said in WIM files and FOG:
change host bios exit to refind
Hello Tom
thanks for the help sir. I am not following you. My vmware options are set following. I have unchecked the option “Boot with EFI instead of BIOS”. If I enable (check) that, bios boots doesnt boot into pxe because it doesnt find the nbp file and it fails. Heres the link
-
RE: WIM files and FOG
so I was messing around and did approve this host. I went to the website and saw the host in there so I set the task to capture. I turned on the VM and it ran some commands and eventually got stuck on init.xz ok…
I turned off the VM again. Deleted the host from website and turned on the vm. It went into pxe and this time it showed the full reg option. I clicked on it and it ran some commands and now it is sitting in a black screen with a _ cursor. I think its stuck but I dont want to touch it incase its doing the capture in the background. Your thoughts?
-
RE: WIM files and FOG
Hey George back at it man!
These are the only options when i try to pxe. No full registration option
-
RE: WIM files and FOG
@george1421 I believe I did disable the FOG service before I sysprep’d. However I have a snapshot of the VM I can revert back to. I took a snapshot just before I hit the OK on Sysprep. So since I already have the wim captured, I will revert back to that snapshot. I will create image def and follow steps you mentioned to capture this image. Unfortunately this is going to have to wait till tomorrow since its getting late for me. I will update again tomorrow on how it went. Thanks again George!