@george1421 said in Imaging a domain controller:

If you are creating a save state system, I would recommend that your client systems not use the FOG client so any fog server actions wouldn’t change the state of the machine post imaging. The fog client is only needed for post install management of the target computers. It has nothing to do with imaging with FOG.

Could you explain how to capture a save state system? Currently what I am doing is replacing the hard drive in my “image computer” the one that I use to capture the image. create a new image on the fog server, associate the image with the image computer then select capture. once this is done I replace the hard drive with the next image and repeat is this the correct procedure?

Another question is it ok to use a single computer to capture all the images? I have a laptop that I am using to switch out hard drives and capture each image from. In our environment, we do not always have dedicated computers that will always be the same thing. We have multiple simulations that we run for the military and have limited hardware so one day the computer is a domain controller the next day it could be a Linux server. This is why I am creating images so when we are tasked to go train the military depending on what we will be doing I can set the computers up for that purpose. Does this make sense? Only a couple of my images will be deployed to multiple computers and those images will be Windows 10 with sysprep ran before it is imaged.

Is there a way to turn off the renaming of the computers? I don’t think anything special about the linux image it captures fine with ghost32. I am running a filesystem check maybe something got messed up.

I rebuilt the FOG server again and was able to successfully capture the Image of the domain controller and push it back down without issues. Also I did the same for a win10 computer. I think what happened was for some reason the domain controller was getting renamed, does FOG rename the computer automatically to the name of the image that I capture. Also, I am trying to capture an image of a Redhat Linux 6.9 computer and I have tried single disk resizeable and multiple partition image and both create and image but when restoring after it is complete it will not boot. It just goes to a black screen and blinks.

I am using FOG as a backup for the domain controller. also the domain controller we have is used on a laptop and shipped to sites where we setup an environment for simulations. My intent is to use this just in case during shipping or even at the event something went wrong with a hard drive i could push the image back to the laptop and continue work. We have done this with ghost32 for years. I am also in the process of capturing images of all the machines that we use in our simulation its about 20-30 computers and we will use these images on different laptops often.

I have a server 2012 domain controller that I am trying to capture an image of and when I capture the image in a virtual environment and deploy it back to a virtual machine it lets me log in and everything works like it should. When I try to deploy the image to a physical laptop that I used to capture the image from it will not allow me to log in I get this message. “The security database on the server does not have a computer account for this workstation trust relationship”. In the past we would use ghost32 to capture our images and I never had issues like this before. I have even tried doing a raw image with the no luck.