thetob Posted February 12, 2011 Posted February 12, 2011 Hi! I have one annoying problem with fog. I have choosen to run fog instead of symantec ghost because of expensive licensing etc. And man i like FOG, but... Im in charge of couple companies and i choose to test fog on a XP-only company. I do all necessary things that are needed for the ghost image and it still wont work. - Install XP - Updates etc - Run an working sysprep(been used for this company for about 1 year without problem) - Image it - Boot and the sysprep runs When i enter windows i can choose to login local or to the domain. When i try to login in to the domain it wont work because the computer(name) havent been added to AD for some reason. So i have to login local and rejoin the computer to the domain and that works perfect! Is this a common problem or do i just suck Because even if this sysprep has worked on symantec it shouldnt be any problem with fog. Anyone has any ideas? Regards, Tobias 1
morganw Posted February 12, 2011 Posted February 12, 2011 You need to install the FOG service into your image. You need to do this as the last thing before you run sysprep as on the next boot the service will attempt to rename the workstation, then reboot, then try to join the domain (if you have this configured for the host in FOG). The service runs independently from the imaging process. Most of the issues you will encounter with a domain join are covered here. 2
dhicks Posted February 12, 2011 Posted February 12, 2011 Most of the issues you will encounter with a domain join are covered here. Oh yea. Drat - there wasn't any need for me to write my own convoluted domain join script...
thetob Posted February 13, 2011 Author Posted February 13, 2011 (edited) Thank you for a quick answer! Im not sure what the "FOG service" is, u mean that FOG client installation? So if i understand this correct, it should be like this: - Install XP - Updates etc - Install Fog service - Run an working sysprep(been used for this company for about 1 year without problem) - Reboot and image it - Boot and let the sysrep and fog service run Edited February 13, 2011 by thetob
morganw Posted February 14, 2011 Posted February 14, 2011 Yes, you can pick it up from http://yourfogservername/fog/client When you install it you can either set it to reference your FOG server by name, or make a DNS alias for it called FOGSERVER. The service requires .Net framework 2.0 so that will have to be in the image as well. Potentially you could install it after the after the mini-setup stage using group policy or a script but you would need to also script a reboot or service restart so that it will do the rename / domain join unattended.
glennda Posted February 14, 2011 Posted February 14, 2011 So if i understand this correct, it should be like this: - Install XP - Updates etc - Install Fog service - Run an working sysprep(been used for this company for about 1 year without problem) - Reboot and image it - Boot and let the sysrep and fog service run if your going to be using the fog service to rename/join the domain for you - you will need to change the sysprep file so that it just names it whatever the random name it assigns and leaves it in the workgroup. Then the fog service should run check see if the name is right if not it will rename and restart. it will then check to see if it is joined to the domain - if not join the domain and restart then you have a useable machine
glennda Posted February 14, 2011 Posted February 14, 2011 just remember if you are using fog for the machine names you need to change it in fog before changing the clients name - becuase otherwise fog changes it back
thetob Posted February 14, 2011 Author Posted February 14, 2011 You guys are awesome! I will try it later this afternoon and hope i get it right! I will let you know about the results! Big thanks for your nice attitude and willing to help!! 1
reggiep Posted February 14, 2011 Posted February 14, 2011 (edited) Glad I found this thread. I'm going to try to get our clients to auto join the domain using fog and will use the advice here. Cheers. Edited February 14, 2011 by reggiep Spelling. Whoops.
thetob Posted February 14, 2011 Author Posted February 14, 2011 It worked perfect! I removed everything(name,domain etc) from sysprep and let FOG handle that part instead. FOG service rebooted as you guys said and joined the domain. Thanks again guys!
ozydave Posted March 10, 2011 Posted March 10, 2011 At last after a few day of battling with FOG to get it to join the imaged PC to the domain I stumbled across the answer (for me anyway). Might be worth a look if others are having the same problem. What I was doing wrong was typing in the LDAP location of the OU I wanted it to join and not typing capital letters where needed. Forgot Linux is very case sensitive. So rather than typing I ran ‘dsquery ou’ and copied / pasted the LDAP string into FOG. Working great now. Now onto multicasting……. Cheers All 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now