Guest mrndnjn Posted November 14, 2007 Posted November 14, 2007 I have a network that I would like to replicate in a lab environment. I know how however how the domain name of the production environement came to be. I don't know how to replicate this naming convention in a lab environment. I have two servers that are domain controllers. Full Computer Name: abc01.xyz.local Domain: xyz.local Full Computer Name: abc02.xyz.local Domain: xyz.local The 2003 environment was migrated from a NT4 environment that I believe the PDC had a domain name of COMPANY. All the workstations on the network have been joined to the COMPANY domain and the drop down login option displays this as well. My question is why didn't the new domain xyz.local for the first 2003 global catalog server take precedence? Why are the machines still required to login the old domain of the NT 4 server? What do I need to do on the first domain controller in my lab environment to replicate the production environment as described above?
Guest Chris M Posted November 14, 2007 Posted November 14, 2007 Re: HELP BUILD LAB NETWORK TO MIRROR PRODUCTION ENVIRONMENT mrndnjn wrote: > I have a network that I would like to replicate in a lab environment. I know > how however how the domain name of the production environement came to be. I > don't know how to replicate this naming convention in a lab environment. I > have two servers that are domain controllers. > > Full Computer Name: abc01.xyz.local > Domain: xyz.local > > Full Computer Name: abc02.xyz.local > Domain: xyz.local > > The 2003 environment was migrated from a NT4 environment that I believe the > PDC had a domain name of COMPANY. > > All the workstations on the network have been joined to the COMPANY domain > and the drop down login option displays this as well. My question is why > didn't the new domain xyz.local for the first 2003 global catalog server take > precedence? Why are the machines still required to login the old domain of > the NT 4 server? What do I need to do on the first domain controller in my > lab environment to replicate the production environment as described above? COMPANY is most likely the NetBIOS equivalent domain name of xyz.local that was inherited from the NT4 domain during the upgrade. Even in a pure Windows 2000/2003 domain environment, the drop-down box for the domain will show the NetBIOS name rather than the DNS name. There is a Group Policy option to show the DNS name instead though. -- Chris M. Remove pants to email me.
Guest mrndnjn Posted November 14, 2007 Posted November 14, 2007 Re: HELP BUILD LAB NETWORK TO MIRROR PRODUCTION ENVIRONMENT I see. So when I run DCPROMO (haven't done this in years) I will be allowed to enter a NETBIOS(company) and domain name xyz.local? Thank you for replying! "Chris M" wrote: > mrndnjn wrote: > > I have a network that I would like to replicate in a lab environment. I know > > how however how the domain name of the production environement came to be. I > > don't know how to replicate this naming convention in a lab environment. I > > have two servers that are domain controllers. > > > > Full Computer Name: abc01.xyz.local > > Domain: xyz.local > > > > Full Computer Name: abc02.xyz.local > > Domain: xyz.local > > > > The 2003 environment was migrated from a NT4 environment that I believe the > > PDC had a domain name of COMPANY. > > > > All the workstations on the network have been joined to the COMPANY domain > > and the drop down login option displays this as well. My question is why > > didn't the new domain xyz.local for the first 2003 global catalog server take > > precedence? Why are the machines still required to login the old domain of > > the NT 4 server? What do I need to do on the first domain controller in my > > lab environment to replicate the production environment as described above? > > COMPANY is most likely the NetBIOS equivalent domain name of xyz.local > that was inherited from the NT4 domain during the upgrade. > > Even in a pure Windows 2000/2003 domain environment, the drop-down box > for the domain will show the NetBIOS name rather than the DNS name. > There is a Group Policy option to show the DNS name instead though. > > > -- > Chris M. > > Remove pants to email me. >
Recommended Posts