Create image from a post allready in a domain
-
Server
- FOG Version: 1.4.2
- OS: unbuntu (netinstall) 17.04
Client
- Service Version: latest
- OS: Win 7 Pro X64
Description
Hi,
I’ve got about twenty PC who i need to get an image but their are allready in a domain.
I took a PC and drop it from AD and take a capture but when i deploy this image, the automatic task for add host in the AD doesn’t work anymore. Power managment does’nt work either.Is their something to do for avoid to remake the image from begining ?
-
sysprep the machine before capture.
-
@x23piracy fogprep isn’t requiered since 1.2 version i think. I can’t find him on 1.4.2 version anyway
-
He’s not talkin about fogprep, sysprep is completly diffrent: https://en.wikipedia.org/wiki/Sysprep
But it should also work without sysprepping the host, I have also taken images from host which were already in the domain. I always deactivate the hostname changer service befor I remove the host from the AD, and capture it afterwards. Never had any problems.
-
@Polii123 said in Create image from a post allready in a domain:
I always deactivate the hostname changer service befor I remove the host from the AD, and capture it afterwards. Never had any problems.
I’ll try to do that. Thanks
-
@Polii123 I tried to desactivate hostname changer service, i make a sysprep (/generalize) but nothing. In fact, it looks like the client won’t work anaymore. And i noticed when i’d reactivated the hostname service that i can’t rename th PC either
-
Were these systems already imaged by FOG in the past? Maybe they have the old FOG client?
Just for clarity you are capturing an image from a target computer for backup purposes and then pushing out a fresh golden image to that computer?
-
@george1421 Yes those was allready imaged by fog (1.2 version with legacy client). I take care about removing old client. But even before i capture my image, i can’t use power managment service. After the deployement, i hav’nt any service working (AD, hostname, …). And these services are working fine on other PCs
Just for clarity you are capturing an image from a target computer for backup purposes and then pushing out a fresh golden image to that computer?
This is exactly it
-
@Lemeunier When you remove the fog client do you purge the fog directory on the client? Also I wonder if you need to remove the client entry in fog and register again. I know with the new FOG client, the fog client tattoo’s the target computer to the FOG server. You can’t just switch target computers to new fog servers.
Does the new golden image have the updated fog client installed?
-
@george1421 Wait, if you are just backing up the old image for archive and not redeploying it then there is no need to remove the fog client.
Tell me a bit more about your new golden image. How did you create this? Was this a new image built from DVD and then sysprep’d?
-
@george1421 In fact i never had to purge the fog directory after removing the legacy client but i’ll try that too. I just remove it and install the new fog service… It works everytime except here. I’m not backing up this image for archive, the idea is to migrate from the 1.2 to the latest version of fog and, by the way, to recapture theses old images (with new fog client, update, etc…) and get better compression of images.
For this PC, the image in the old fog was corrupted. All i can do its taking it from a PC allready in the park. Or remake it…
When i redeploy an old image, update client, and register the host i have no problem.Last thing, i’ve no idea how the image was created the first time i didn’t worked here at this time. But i see a recovery partition so i think it was an pre-installed windows 7 pro x86