|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
changing domain namehi! How do i change my domain name in a Win2003 AD environment? What will the
effect be in the dns and dhcp svrs? For those dhcp that's not an AD (no dcpromo, only joined domain), can i just unjoin it from the current domain and then join to the new domain? Will that affect the clients connected to it? (of course, i'll manually changed the scope option in there, eg. domain name, suffix, and etc). Thanks.
Show quote
Hide quote
"dkblee" <dkb***@discussions.microsoft.com> wrote in message May I ask wht you want to rename your domain ?? It may prove to be a big news:BDA44553-6472-46B1-8D80-F31B7EB13DDD@microsoft.com... > hi! How do i change my domain name in a Win2003 AD environment? What will > the > effect be in the dns and dhcp svrs? > > For those dhcp that's not an AD (no dcpromo, only joined domain), can i > just > unjoin it from the current domain and then join to the new domain? Will > that > affect the clients connected to it? (of course, i'll manually changed the > scope option in there, eg. domain name, suffix, and etc). > > Thanks. job. What exactly do you expect to accomplish by removing/rejoining your DHCP
servers from/to domain during the rename operation (rather than simply keeping them as domain members throughout its duration)? In addition, as Kev has pointed out, the domain rename is relatively elaborate operation - so make sure you are aware of all its prerequisites/implications (more info at http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx) before you start... hth Marcin Show quoteHide quote "dkblee" <dkb***@discussions.microsoft.com> wrote in message news:BDA44553-6472-46B1-8D80-F31B7EB13DDD@microsoft.com... > hi! How do i change my domain name in a Win2003 AD environment? What will > the > effect be in the dns and dhcp svrs? > > For those dhcp that's not an AD (no dcpromo, only joined domain), can i > just > unjoin it from the current domain and then join to the new domain? Will > that > affect the clients connected to it? (of course, i'll manually changed the > scope option in there, eg. domain name, suffix, and etc). > > Thanks. In news:BDA44553-6472-46B1-8D80-F31B7EB13DDD@microsoft.com, dkblee <dkb***@discussions.microsoft.com>, posted the following:> hi! How do i change my domain name in a Win2003 AD environment? What Once you've thought about the change and what is involved, as Marcin and Kev > will the effect be in the dns and dhcp svrs? > > For those dhcp that's not an AD (no dcpromo, only joined domain), can > i just unjoin it from the current domain and then join to the new > domain? Will that affect the clients connected to it? (of course, > i'll manually changed the scope option in there, eg. domain name, > suffix, and etc). > > Thanks. mentioned, here are pertinent steps and links to read up on what is totally involved, depending on scenario, current operating system, version of Exchange, etc. ====================================================================================================== ====================================================================================================== ====================================================================================================== Domain Rename Procedure and Notes: Note: The Domain and Forest functional levels must be set to 2003. If you have Exchange 2003, make sure it is minimal SP1 in order to support a domain rename. If Exchange 2000, either upgrade to 2003, or Exmerge all of your mailboxes to PSTs, uninstall Exchange 2000, run the domain rename operation, then reinstall Exchange 2000, and use Exmerge to pump the mailboxes back in the user's newly created mailbox accounts. Also, if a PKI infrastructure was installed (Certificate Services), it will need to be removed first prior to a domain rename: How to decommission a Windows enterprise certification authority: http://support.microsoft.com/kb/889250 819145 - Support WebCast Microsoft Windows Server 2003 Implementing an Active Directory Domain Rename Operation: http://support.microsoft.com/default.aspx?scid=kb;en-us;819145&Product=winsvr2003 Windows Server 2003 Active Directory Domain Rename Tools: http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx Domain Rename – Rename a Windows 2003 Forest with Exchange 2003 installed (ifyou don't have Exchange, you can ignore the Exchange part) http://www.msexchange.org/tutorials/Domain-Rename.html Domain Rename Part 1 - Setup http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/07/Domain-Rename-Part-1-_2D00_-Setup.aspx Domain Rename Part 2 - Renaming http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/08/Domain-Rename-Part-2-_2D00_-Renaming.aspx Domain Rename Part 3 - Exchange 2003 http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/09/Domain-Rename-Part-3-_2D00_-Exchange-2003.aspx Now if you have Exchange 2003, here is what you need as well: Supplemental steps for using the Exchange Server Domain Rename Fixup tool together with the Windows Server 2003 domain rename tools: http://support.microsoft.com/kb/842116/ Domain Rename – Rename a Windows 2003 Forest with Exchange 2003 installed http://www.msexchange.org/tutorials/Domain-Rename.html Error messages encountered on renaming domain http://support.microsoft.com/kb/891370 The following was quoted from: http://technet.microsoft.com/en-us/library/cc738208.aspx Keep in mind after a rename procedure, the DC's Primary DNS Suffix is not automatically changed to match the new domain name. You are required to change the Primary DNS Suffix to match the new name. In other words, unlike the names of member computers, the DNS names of domain controllers in a renamed domain will remain unchanged. The domain controllers can be renamed in a separate step, using a special domain controller rename procedure, after the domain rename operation is complete. You must double-check ALL domain members to insure that their Primary DNS Suffix matches the new domain name. 257623 The DNS suffix of the computer name of a new domain controller may not match the name of the domain after you upgrade a Windows NT 4.0 primary domain controller to Windows 2000 http://support.microsoft.com/default.aspx?scid=kb;EN-US;257623 If Exchange 2007 is involved, it is not supported at this time. You must uninstall Exchange 2007, then rename the domain, then reinstall Exchange 2007. I know it is easier said then done, but that seems to be the only option at this time. Exchange 2007 installed is not supported: The Microsoft Exchange System Attendant service does not start on a computer that is running Exchange Server 2007 after you rename a Windows Server 2003 domain http://support.microsoft.com/kb/925822 Exchange 2007 and Domain Rename http://theessentialexchange.com/blogs/michael/archive/2008/04/04/exchange-2007-and-domain-rename.aspx --- ADMT to migrate into a new forest/domain: For 2003: ADMT v3 Migration Guide http://www.microsoft.com/downloads/details.aspx?familyid=D99EF770-3BBB-4B9E-A8BC-01E9F7EF7342&displaylang=en Active Directory Migration Tool v3.0 http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en For 2008: ADMT v3.1 Guide: Migrating and Restructuring Active Directory Domains http://www.microsoft.com/downloads/details.aspx?familyid=6D710919-1BA5-41CA-B2F3-C11BCB4857AF&displaylang=en Active Directory Migration Tool version 3.1 http://www.microsoft.com/downloads/details.aspx?familyid=AE279D01-7DCA-413C-A9D2-B42DFB746059&displaylang=en Password Export Server version 3.1 (x86) http://www.microsoft.com/downloads/details.aspx?familyid=F0D03C3C-4757-40FD-8306-68079BA9C773&displaylang=en Password Export Server version 3.1 (x64) http://www.microsoft.com/downloads/details.aspx?familyid=5B4E5C61-1C00-4DA7-9C0D-130200AED21A&displaylang=en Domain Migration Cookbook - Index and Cover: http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookintr.mspx ====================================================================================================== ====================================================================================================== ====================================================================================================== -- Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT Microsoft Certified Trainer ace***@mvps.RemoveThisPart.org For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers. hi! Thank you all for the reply and info given. The reason i'm thinking of
dijoining and joining of domain (from the old old domain to the new one) for my dhcp, wsus is to avoid renaming of domain, rather to create a new domain with the name i wanted because of change of company name, and move the services one by one to the new domain. will changing of domain name for the dhcp(besides changing the dns suffix in the scope option) and wsus server create any problem? or i need to re-setup both these services? Thanks. Show quoteHide quote "Ace Fekay [Microsoft Certified Trainer]" wrote: > In news:BDA44553-6472-46B1-8D80-F31B7EB13DDD@microsoft.com, > dkblee <dkb***@discussions.microsoft.com>, posted the following: > > hi! How do i change my domain name in a Win2003 AD environment? What > > will the effect be in the dns and dhcp svrs? > > > > For those dhcp that's not an AD (no dcpromo, only joined domain), can > > i just unjoin it from the current domain and then join to the new > > domain? Will that affect the clients connected to it? (of course, > > i'll manually changed the scope option in there, eg. domain name, > > suffix, and etc). > > > > Thanks. > > Once you've thought about the change and what is involved, as Marcin and Kev > mentioned, here are pertinent steps and links to read up on what is totally > involved, depending on scenario, current operating system, version of > Exchange, etc. > > > ====================================================================================================== > ====================================================================================================== > ====================================================================================================== > > > Domain Rename Procedure and Notes: > > Note: The Domain and Forest functional levels must be set to 2003. If you > have Exchange 2003, make sure it is minimal SP1 in order to support a domain > rename. If Exchange 2000, either upgrade to 2003, or Exmerge all of your > mailboxes to PSTs, uninstall Exchange 2000, run the domain rename operation, > then reinstall Exchange 2000, and use Exmerge to pump the mailboxes back in > the user's newly created mailbox accounts. > > Also, if a PKI infrastructure was installed (Certificate Services), it will > need to be removed first prior to a domain rename: > > How to decommission a Windows enterprise certification authority: > http://support.microsoft.com/kb/889250 > > 819145 - Support WebCast Microsoft Windows Server 2003 Implementing an > Active Directory Domain Rename Operation: > http://support.microsoft.com/default.aspx?scid=kb;en-us;819145&Product=winsvr2003 > > Windows Server 2003 Active Directory Domain Rename Tools: > http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx > > Domain Rename – Rename a Windows 2003 Forest with Exchange 2003 installed > (ifyou don't have Exchange, you can ignore the Exchange part) > http://www.msexchange.org/tutorials/Domain-Rename.html > > Domain Rename Part 1 - Setup > http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/07/Domain-Rename-Part-1-_2D00_-Setup.aspx > > Domain Rename Part 2 - Renaming > http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/08/Domain-Rename-Part-2-_2D00_-Renaming.aspx > > Domain Rename Part 3 - Exchange 2003 > http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/09/Domain-Rename-Part-3-_2D00_-Exchange-2003.aspx > > Now if you have Exchange 2003, here is what you need as well: > Supplemental steps for using the Exchange Server Domain Rename Fixup tool > together with the Windows Server 2003 domain rename tools: > http://support.microsoft.com/kb/842116/ > > Domain Rename – Rename a Windows 2003 Forest with Exchange 2003 installed > http://www.msexchange.org/tutorials/Domain-Rename.html > > Error messages encountered on renaming domain > http://support.microsoft.com/kb/891370 > > > > The following was quoted from: > http://technet.microsoft.com/en-us/library/cc738208.aspx > > Keep in mind after a rename procedure, the DC's Primary DNS Suffix is not > automatically changed to match the new domain name. You are required to > change the Primary DNS Suffix to match the new name. In other words, unlike > the names of member computers, the DNS names of domain controllers in a > renamed domain will remain unchanged. The domain controllers can be renamed > in a separate step, using a special domain controller rename procedure, > after the domain rename operation is complete. You must double-check ALL > domain members to insure that their Primary DNS Suffix matches the new > domain name. > > 257623 The DNS suffix of the computer name of a new domain controller may > not match the name of the domain after you upgrade a Windows NT 4.0 primary > domain controller to Windows 2000 > http://support.microsoft.com/default.aspx?scid=kb;EN-US;257623 > > If Exchange 2007 is involved, it is not supported at this time. You must > uninstall Exchange 2007, then rename the domain, then reinstall Exchange > 2007. I know it is easier said then done, but that seems to be the only > option at this time. > > Exchange 2007 installed is not supported: > The Microsoft Exchange System Attendant service does not start on a > computer that is running Exchange Server 2007 after you rename a Windows > Server 2003 domain > http://support.microsoft.com/kb/925822 > > Exchange 2007 and Domain Rename > http://theessentialexchange.com/blogs/michael/archive/2008/04/04/exchange-2007-and-domain-rename.aspx > > > --- > > ADMT to migrate into a new forest/domain: > > For 2003: > ADMT v3 Migration Guide > http://www.microsoft.com/downloads/details.aspx?familyid=D99EF770-3BBB-4B9E-A8BC-01E9F7EF7342&displaylang=en > > Active Directory Migration Tool v3.0 > http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en > > For 2008: > > ADMT v3.1 Guide: Migrating and Restructuring Active Directory Domains > http://www.microsoft.com/downloads/details.aspx?familyid=6D710919-1BA5-41CA-B2F3-C11BCB4857AF&displaylang=en > > Active Directory Migration Tool version 3.1 > http://www.microsoft.com/downloads/details.aspx?familyid=AE279D01-7DCA-413C-A9D2-B42DFB746059&displaylang=en > > Password Export Server version 3.1 (x86) > http://www.microsoft.com/downloads/details.aspx?familyid=F0D03C3C-4757-40FD-8306-68079BA9C773&displaylang=en > > Password Export Server version 3.1 (x64) > http://www.microsoft.com/downloads/details.aspx?familyid=5B4E5C61-1C00-4DA7-9C0D-130200AED21A&displaylang=en > > Domain Migration Cookbook - Index and Cover: > http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookintr.mspx > > ====================================================================================================== > ====================================================================================================== > ====================================================================================================== > > -- > Ace > > This posting is provided "AS-IS" with no warranties or guarantees and > confers no rights. > > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT > Microsoft Certified Trainer > ace***@mvps.RemoveThisPart.org > > For urgent issues, you may want to contact Microsoft PSS directly. Please > check http://support.microsoft.com for regional support phone numbers. > > hi! Thank you all for the reply, the reason i'm thinking of joining-rejoining
of domain for my dhcp and wsus server is to avoid changing of domain name directly on my existing AD. I'm thinking of creating a new AD in a new sets of machines and then move the services 1 by 1 from my current AD. The question is that will disjoining and joining of domain for my current dhcp (besides changing of suffix name in the scope option) and wsus server create any issue? Thanks. In news:759A2A50-B791-4443-8B4A-348DF46FB5DE@microsoft.com, dkblee <dkb***@discussions.microsoft.com>, posted the following:> hi! Thank you all for the reply, the reason i'm thinking of I'm not sure I understand the question. Do you want to disjoin the DHCP > joining-rejoining of domain for my dhcp and wsus server is to avoid > changing of domain name directly on my existing AD. I'm thinking of > creating a new AD in a new sets of machines and then move the > services 1 by 1 from my current AD. > > The question is that will disjoining and joining of domain for my > current dhcp (besides changing of suffix name in the scope option) > and wsus server create any issue? > > Thanks. server from your domain? Or is the question regarding renaming your whole domain, or are you simply disjoiing a client machine from one domain and joining it to another? If so, the Primary DNS Suffix will change on the machine to the domain it will belong to. It will then register (if everything is working properly) to the zone for the domain you are joining it to. Or if deciding to rename a domain because of WSUS or DHCP, I wouldn't bother going through the process, unless your current domain name is a single label name domain. Otherwise, it will not be worth it. WSUS is tied into the AD domain the machine is installed that it is joined to. This allows you to target machines based on either GPO targeting or direct. Ace
Show quote
Hide quote
"Ace Fekay [Microsoft Certified Trainer]" <firstnamelastn***@hotmail.com> Ace - these are fantastic links. Could of done with these a while back wrote in message news:uIpV7a$qJHA.1748@TK2MSFTNGP05.phx.gbl... > In news:BDA44553-6472-46B1-8D80-F31B7EB13DDD@microsoft.com, > dkblee <dkb***@discussions.microsoft.com>, posted the following: >> hi! How do i change my domain name in a Win2003 AD environment? What >> will the effect be in the dns and dhcp svrs? >> >> For those dhcp that's not an AD (no dcpromo, only joined domain), can >> i just unjoin it from the current domain and then join to the new >> domain? Will that affect the clients connected to it? (of course, >> i'll manually changed the scope option in there, eg. domain name, >> suffix, and etc). >> >> Thanks. > > Once you've thought about the change and what is involved, as Marcin and > Kev mentioned, here are pertinent steps and links to read up on what is > totally involved, depending on scenario, current operating system, version > of Exchange, etc. > > > ====================================================================================================== > ====================================================================================================== > ====================================================================================================== > > > Domain Rename Procedure and Notes: > > Note: The Domain and Forest functional levels must be set to 2003. If you > have Exchange 2003, make sure it is minimal SP1 in order to support a > domain rename. If Exchange 2000, either upgrade to 2003, or Exmerge all of > your mailboxes to PSTs, uninstall Exchange 2000, run the domain rename > operation, then reinstall Exchange 2000, and use Exmerge to pump the > mailboxes back in the user's newly created mailbox accounts. > > Also, if a PKI infrastructure was installed (Certificate Services), it > will need to be removed first prior to a domain rename: > > How to decommission a Windows enterprise certification authority: > http://support.microsoft.com/kb/889250 > > 819145 - Support WebCast Microsoft Windows Server 2003 Implementing an > Active Directory Domain Rename Operation: > http://support.microsoft.com/default.aspx?scid=kb;en-us;819145&Product=winsvr2003 > > Windows Server 2003 Active Directory Domain Rename Tools: > http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx > > Domain Rename - Rename a Windows 2003 Forest with Exchange 2003 installed > (ifyou don't have Exchange, you can ignore the Exchange part) > http://www.msexchange.org/tutorials/Domain-Rename.html > > Domain Rename Part 1 - Setup > http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/07/Domain-Rename-Part-1-_2D00_-Setup.aspx > > Domain Rename Part 2 - Renaming > http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/08/Domain-Rename-Part-2-_2D00_-Renaming.aspx > > Domain Rename Part 3 - Exchange 2003 > http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/06/09/Domain-Rename-Part-3-_2D00_-Exchange-2003.aspx > > Now if you have Exchange 2003, here is what you need as well: > Supplemental steps for using the Exchange Server Domain Rename Fixup tool > together with the Windows Server 2003 domain rename tools: > http://support.microsoft.com/kb/842116/ > > Domain Rename - Rename a Windows 2003 Forest with Exchange 2003 installed > http://www.msexchange.org/tutorials/Domain-Rename.html > > Error messages encountered on renaming domain > http://support.microsoft.com/kb/891370 > > > > The following was quoted from: > http://technet.microsoft.com/en-us/library/cc738208.aspx > > Keep in mind after a rename procedure, the DC's Primary DNS Suffix is not > automatically changed to match the new domain name. You are required to > change the Primary DNS Suffix to match the new name. In other words, > unlike the names of member computers, the DNS names of domain controllers > in a renamed domain will remain unchanged. The domain controllers can be > renamed in a separate step, using a special domain controller rename > procedure, after the domain rename operation is complete. You must > double-check ALL domain members to insure that their Primary DNS Suffix > matches the new domain name. > > 257623 The DNS suffix of the computer name of a new domain controller may > not match the name of the domain after you upgrade a Windows NT 4.0 > primary > domain controller to Windows 2000 > http://support.microsoft.com/default.aspx?scid=kb;EN-US;257623 > > If Exchange 2007 is involved, it is not supported at this time. You must > uninstall Exchange 2007, then rename the domain, then reinstall Exchange > 2007. I know it is easier said then done, but that seems to be the only > option at this time. > > Exchange 2007 installed is not supported: > The Microsoft Exchange System Attendant service does not start on a > computer that is running Exchange Server 2007 after you rename a Windows > Server 2003 domain > http://support.microsoft.com/kb/925822 > > Exchange 2007 and Domain Rename > http://theessentialexchange.com/blogs/michael/archive/2008/04/04/exchange-2007-and-domain-rename.aspx > > > --- > > ADMT to migrate into a new forest/domain: > > For 2003: > ADMT v3 Migration Guide > http://www.microsoft.com/downloads/details.aspx?familyid=D99EF770-3BBB-4B9E-A8BC-01E9F7EF7342&displaylang=en > > Active Directory Migration Tool v3.0 > http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en > > For 2008: > > ADMT v3.1 Guide: Migrating and Restructuring Active Directory Domains > http://www.microsoft.com/downloads/details.aspx?familyid=6D710919-1BA5-41CA-B2F3-C11BCB4857AF&displaylang=en > > Active Directory Migration Tool version 3.1 > http://www.microsoft.com/downloads/details.aspx?familyid=AE279D01-7DCA-413C-A9D2-B42DFB746059&displaylang=en > > Password Export Server version 3.1 (x86) > http://www.microsoft.com/downloads/details.aspx?familyid=F0D03C3C-4757-40FD-8306-68079BA9C773&displaylang=en > > Password Export Server version 3.1 (x64) > http://www.microsoft.com/downloads/details.aspx?familyid=5B4E5C61-1C00-4DA7-9C0D-130200AED21A&displaylang=en > > Domain Migration Cookbook - Index and Cover: > http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookintr.mspx > > ====================================================================================================== > ====================================================================================================== > ====================================================================================================== > > -- > Ace > > This posting is provided "AS-IS" with no warranties or guarantees and > confers no rights. > > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT > Microsoft Certified Trainer > ace***@mvps.RemoveThisPart.org > > For urgent issues, you may want to contact Microsoft PSS directly. Please > check http://support.microsoft.com for regional support phone numbers. myself. Lol Kev In news:ukQGSXKrJHA.3864@TK2MSFTNGP02.phx.gbl, -= Kev =- <kev***@dsl.pipex.com>, posted the following:> Ace - these are fantastic links. Could of done with these a while Thanks! I must have missed your post when you needed them, otherwise I would > back myself. Lol > > Kev have been more than happy to post them! Cheers! :-) Ace Hi
I recommend that you read the MS documentation about domain rename. After that decide or ask yourself if domain rename is what you're looking for, your question is also answered in those documents. -- Show quoteHide quoteI hope that the information above helps you. Have a Nice day. Jorge Silva MVP Directory Services "dkblee" <dkb***@discussions.microsoft.com> wrote in message news:BDA44553-6472-46B1-8D80-F31B7EB13DDD@microsoft.com... > hi! How do i change my domain name in a Win2003 AD environment? What will > the > effect be in the dns and dhcp svrs? > > For those dhcp that's not an AD (no dcpromo, only joined domain), can i > just > unjoin it from the current domain and then join to the new domain? Will > that > affect the clients connected to it? (of course, i'll manually changed the > scope option in there, eg. domain name, suffix, and etc). > > Thanks. Hello dkblee,
Domain rename can be done with minimum functional level windows server 2003. But the question is, if there is really the need for it. All necessary links you got already from the previous posters. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm Show quoteHide quote > hi! How do i change my domain name in a Win2003 AD environment? What > will the effect be in the dns and dhcp svrs? > > For those dhcp that's not an AD (no dcpromo, only joined domain), can > i just unjoin it from the current domain and then join to the new > domain? Will that affect the clients connected to it? (of course, i'll > manually changed the scope option in there, eg. domain name, suffix, > and etc). > > Thanks. >  
Thread options
Other interesting topics
Is this the last step we need to do?
Do Child DC's need unrestricted IP access to Root DC's? After 2000 to 2003 upgrade sysvol is not accessable Manually removing cert server from AD DNS/DHCP problem while migrating computers using ADMT Validation for 2000 to 2003 upgrade DC's not Replicating Way to set using Active Directory, which ports for remote desktop? DC fails when isolated from network ADAM UserProxy Authentication (Which Domain Controller?) |
|||||||||||||||||||||||
