Topics created by TheeGrizzly

Well with FOG 0.32, the answer is to upgrade to 1.2.0.

Have you searched the forums yet? I believe there are several well written posts about exporting the database and backing up the images so you can move them to a new server.

Alright… I’ll do a little research and see how hard it is to move it to something a little faster

[CODE]6/27/2013 11:17 AM FOG::HostnameChanger Domain Error! (‘Unknown Error’ Code: 87)[/CODE]

Always use the code tags when posting logs or code to keep the board from eating it and pooping out smilies.

Double check the information used for AD joining that is stored in the global FOG settings against the information that is stored in the Active Directory page for the particular host. Make sure they match, with the global FOG settings winning out over the host Active Directory settings if there is a difference.

[quote=“madeyem, post: 12683, member: 797”]If you want to use Sysprep with an unattend.xml, you have to run a batch script, in which you specify the location of the unattend.xml. Starting Sysprep via the GUI will always run the default Sysprep process.

For example, create a batch file with the following content:

[CODE]@echo off
cd c:\windows\system32\sysprep
sysprep /oobe /generalize /shutdown /unattend:C:*path to the unattend.xml*\unattend.xml[/CODE][/quote]

I don’t use a .bat file I just call it from command prompt and I point to the unattend but it is still not working right.

Yes, Define them for any scope that has computers or your clients don’t know where to look for the boot server (Fog server). Make sure that these options are not defined for other systems, IP phones sometimes use options 66 & 67.

Ideally if you had IP phones that use options 66 & 67 they would be on a different DHCP scope than your computers