jfmartel Posted January 5, 2006 Posted January 5, 2006 Hello all.I not a newbie into RIS environment since I've already did achieved it in another job I had in the past.Now in my new job, I've got to do the same thing, the main difference for my test setup is I'm working in VMWare. I do know vmware and how it works but I'm getting problem with the RIS thing.Here is my setup in VMWare:Both virtual machine are NATed, and my DHCP server for my NATed adapter is OFF.Is my server, everything works, my workstation gets into the RIS and the CIW.Workstation gets an address from the DHCP server located in my virtual RIS Server so communication between the 2 virtual machine is ok.Here is what I got from my .sif file:[Identification] JoinDomain=%MACHINEDOMAIN% DoOldStyleDomainJoin=YesIn the CIW, machine get added to the right OU in my AD.But when machine boot up in Windows, machine isnt in the domain.Is this because I'm in VMWare or I got a problem elsewhere?Thanks for the help!
Fencer128 Posted January 5, 2006 Posted January 5, 2006 (edited) Hi,In the CIW, machine get added to the right OU in my AD.But when machine boot up in Windows, machine isnt in the domain.Please can you elaborate. If you check AD on the server do you see the machine account of the client PC in the correct container? What I'm trying to tell is whether once you have selected the correct AD credentials from within the CIW the machine account is actually being created.This will allow us to see whether it is a problem with account creation or having the client PC join the domain.I'm sure you know this but I can't be absolutely sure from what you've written so far.Cheers,Andy Edited January 5, 2006 by Fencer128
jfmartel Posted January 5, 2006 Author Posted January 5, 2006 Hello thanks for reply.For testing purpose, I'm using the Administrator account from my test domain with the CIW. So, yes machine account gets created in the AD in the correct OU.
jfmartel Posted January 5, 2006 Author Posted January 5, 2006 It seems like my problem isn't related to VMWare but with Windows 2003 SP1.After searching for solution on google, i saw that a lot of people are having problem since introducing SP1 into their domain.It looks that they added security that disabled the functionality found in the sif file (DoOldStyleDomainJoin).I might have to give a try to this instead, or found registry key/gpo that might reallow me to do this.DomainAdmin = accountname DomainAdminPassword = a domain password with permissions to add machines to domain JoinDomain = our domain nameI'll keep you informed.Thanks
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