Thanks for the information. Relieves some of my worries.

Just a general question, but has anyone ever had any problems imaging to or from SSDs using FOG? Also, is it possible to make an image from a standard spinning disk drive and then image to an SSD? And vice-versa? I have mini PCs from last year that have the spinning disk drives and we ordered same model machines for this coming year, but they have SSDs. Just wanted to know what the experience was like for someone who has gone through this.

Thanks

Yes, I’ll try to get to those. I am under a time crunch right now so I can not get to that right away.

I deployed the image that gave me the error after it was created, and it deployed successfully.

On the bottom right corner on the dashboard it says Version 1.5.6.

I have not deployed this image. This error is on the source/golden image after it captures and reboots. I added at the end of my original post that I created and deployed a different image for laptops with no problems. This error is on a desktop.

No I do not have the client installed on the source. I have not pushed the image out to another machine. This error is on the source.

Re: Windows 1809 Ent. Error after Upload to FOG

I seem to be having the same problem as mentioned in the above post. On my source Windows 10 computer it completes taking an image and reboots. When it reboots to the windows logo splash screen, I get an “Install windows” error.

I ran my install media and it shows an extra 29 GB partition marked as primary.

I’m thinking it has something to do when it is resized? I left everything at default when creating the image in FOG. Maybe I should try "Multiple Partition Image - Single Disk (Not Resizable). But If I do that then there goes my HD space on the server, or does it take an image of what’s being used? I am not to sure, just want to get ideas before doing something.

I did sysprep and chkdsk /r before creating the image on the source. I have created another image for a laptop with no problems creating or pushing it out, but that was the one with the two partitions, not four when installing windows.

Ok, I understand. Then it seems like I can continue with setting up ProxyDHCP.

Thanks for the info and clearing it up for me.

The ProxyDHCP option seems to fit what I am looking for. I need to leave the current DHCP server running and I can not touch that. In the instructions for ProxyDHCP, it says not to set DHCP address or DNS and not set FOG as a DHCP. I have already set up FOG, months ago, to use our current DHCP, the question is how do I clear the settings in FOG before I start setting up ProxyDHCP?

Forgive my ignorance, but I thought during the initial setup of fog, there was an option that if a person was not able to have access to the dhcp server then they could configure fog to not use a dhcp server. I guess fog would be setup to act as its own dhcp? I am not sure, I may be thinking of something else.

As for the server name change, I will have to look more into those options.