1. No more netdom needed, everything it did is now implemented in code. 2. No, unjoin the box before uploading. 3. You don't have to, it will add it should add it with the same name. Someone correct me if I am wrong, I am not a AD guy. We don't clean up entries at all in AD, so after time you will get "stale" entries.
On Mon, 2010-08-16 at 15:12 -0500, K Lesko wrote: > Scott, > > I had this question regarding "Do I need netdom.exe in version 0.29?" > and never did find an answer. I thought for 0.29 you didn't need > this, but I don't remember why I thought that. The cahnge log for > 0.29 has: > > "*changed hostname changer to use unmanaged code to (un)join domain" > Not sure what that means exactually, but I did notice that the user > guide still indicates that netdom.exe is to be included on the system > to be imaged. Did you find out anything more conclusive? > > For #2 My understanding was that the computer should be unjoined from > the domain prior to pulling an image. > > I have no ideal about #3 > > Kevin > > On Sun, Aug 15, 2010 at 11:12 PM, Scott Siri <[email protected]> > wrote: > I checked the forums on this and have read and re-read the > user guide...I'm looking for an experienced answer because I > think the forums are referencing information for older > versions of FOG, but that is not always obvious. > > I'm using 0.29. > > I'm trying to pull and then deploy a simple XP image from one > Optiplex to another. They are identical machines. > > After several image pulls and several deployments, I still > cannot get the newly imaged computer to join the domain. The > namechanger seems to be working fine. Here is where forums > and even the user guide seem to send mixed signals. > > 1. Do I need netdom.exe in version 0.29? > 2. Should the computer I pull the image from be attached > to the domain or not when pulling the image? > 3. Do I need to manually remove all previously used > hostnames from AD before it will join the domain...ie > I'm re-imaging MHS047. Do I need to remove it from AD > before imaging so that after imaging it will join the > domain as MHS047 again? > I checked the logs that I could find, but did not see any > indication as to why it was not joining the domain. I've > checked and rechecked my pw encryption and all that setup for > AD integration. > > Thanks for your thoughts, > Scott > > > *** This Email was sent by an educator at Mendota IL. > | Subscription info at http://www.tech-geeks.org | > > | Subscription info at http://www.tech-geeks.org | | Subscription info at http://www.tech-geeks.org |
