George,
I have another question, this time about sysprep. Why do we need to go through OOBE for an installation that is all in the same locale? Wouldn’t it be easier to just generalize and be done? And if doing that, do I still need to disable the Fog Client Service before doing it?
Thank you,
Dave
Thank you, George.
One more question (hopefully) and then I will try this. The unattend.xml method should work whether or not it is an OEM version of Windows, no? Isn’t unattend used regardless, and therefore anything in it executed regardless?
Thank you again,
Dave
Hello,
I am hoping you can help me with this one. I successfully deployed an image to three hosts, however the accompanying snap-in still shows in the Active Snap-in Tasks as queued.
The snap-in is enabled, it is an MSI, actually the FogClient MSI file that I am trying to install on the hosts.
I just found where the snap-in requires FogClient to already be on the host? If that is the case, then how do I push FogClient to the hosts?
When I eventually deploy the FogServer I am going to want to put FogClient on all hosts which will allow me to better manage things, but I don’t want to completely re-image every machine at this time, so is there a recommended way to do this?
Thank you,
Dave
@george1421 @Sebastian-Roth @Quazz
Thanks George, I tried to use your unattend file, but it kept bluescreening on the host once imaged, so I tried creating a new one today and it worked fine. I probably didn’t change enough things in it, and missed something important, but I got around it now.
I greatly appreciate all the help you kind folks have provided. It is very much appreciated. I couldn’t have gotten to this point without it,
Dave
I agree with you that something must be wrong with the image. It has done the same thing on 3 virtual machines so far. I originally had done a multicast for the first 2 and a single machine deploy for the last.
I am going to go back to the VM with the gold image, and re-sysprep and capture it. Then try the deploy again. Do you have recommended sysprep parameters? I was using /oobe /shutdown
@george1421 Okay, but the gold image VM boots fine, and so, I am somewhat unsure what would cause a block by block copy of it to have a bad boot partition.
Interestingly, once I booted from a Win10 ISO file, it then says the registry is missing or has errors. This has me wondering if I should just try to deploy again, as maybe something got lost or corrupted between the image and the target.
What do you think? Can this be a possibility?
Dave
Yes, I syspreped before capture.
I will try the recovery tools. One question which comes to mind though, although since the partition tables are recreated I doubt this is the case, but does that target drive have to have had a working operating system on it prior to the FOG deployment?
Thank you,
Dave
@davemccracken @george1421 @Sebastian-Roth
This is the current screen I get when I try to boot the target VM
The image was deployed, but when I booted the virtual machine, there isn’t a valid boot file at SCSI 0,0 found. I should probably start a new thread?
@george1421 @Sebastian-Roth @Quazz
Thank you all. It was indeed a disk size issue, as the last screenshot showed. I recreated the hard drive the same size as the one on the VM used for the image source and it is now working.
I am learning the things to watch out for so the next test, I will not run into such basic issues again. Thank you.
Dave
@Quazz @george1421 @Sebastian-Roth
Okay, I now went to the tasks page and deleted all tasks, then to the “List all Hosts” page and started the deploy task checking the box next to debug. Whatever I had done before, when clicking deploy it didn’t give me those options, but this time it did, so I must have done something different.
These are the output screens with the lsblk command before and after the Fog run.
Thank you for your responses. They are really helping me.
Dave
Dave
@george1421 I will have to get a physical machine set up to and join it to the domain on the virtual machines then. I have tried to keep it away from physical machines and direct access to the corporate network until tested out, so I will have to work on that.
Having created my first Image the other day, I was trying to lay it down on another VM today and got the following error. I have verfied that the VHDX files for both the Gold Image machine the image was captured from and the target machine are about the same size with the target maybe a couple hundred K bigger.
This is the error I am getting
I really apprecaite your help with this as this is my first attempt to deploy an image using Fog.
Thank you,
Dave
@Sebastian-Roth I must confess I did it. It was my first attempt at anything with Fog and describing a windows host, I used windows nomenclature. I was not considering that PXE boot would boot Linux. I know how Linux represents devices, but… Call it a faux pas.
@george1421 Unfortunately not. It seems I made an error and posted the same screenshot twice. This one shows the second error, which then causes it to reboot.
@george1421 No, it hasn’t changed. It is 192.168.0.5. DHCP on a Windows 2012r2 server (to mimic the way it is set up for our prod environment) is 0.1, forwarding server to provide internet access is 0.2 (also windows) DHCP starts handing out at 0.101. The Gold Image VM is 0.112.
