07. april 2003 - 23:45
Der er
3 kommentarer og
1 løsning
Omdøb Domæne
Mit problem består i at jeg har et domæne.dk som jeg hoster en hjemmeside på. Dette domæne er styret ekstern dsn der peger ned på min IP adresse. Da jeg så skulle sætte min server op som domaincontroller til lokalnetværket, kom jeg til at kalde domænet det samme som det eksterne domæne.dk. Så når jeg vil gå ind på mit hjemmesiden på domæne.dk fra en af maskinerne på lokalnetværket, resulterer det i at jeg får den lokale IP, og ikke den globale.
Løsningen på dette problem ville være at omdøbe domænet på serveren til noget andet en domæne.dk og derved undgå denne konflikt. Men jeg har ikke kunne nogen måde hvorpå jeg kan omdøbe domænet på serveren. Jeg går bestemt udfra at der er en metode, da en formatering ikke kan være løsningen.
Håber at der sidder en blandt jer, der kender svaret! :)
07. april 2003 - 23:53
#1
To Rename a Windows 2000 Domain
1. Create a backup of any and/or all domain controllers that may be involved in this process.
2. If there are no existing Windows NT 4.0 BDCs in the Windows 2000 domain, then you have to install one that is preferably running service pack 6 or 6a. If you want, you can install a second BDC and then physically remove it from the domain to serve as a backup for the domain information as it contains all of the domain user accounts, and the Security Accounts Manager (SAM) and security information.
3. Allow sufficient time for this BDC to acquire all domain security and SAM information. To force a full SAM/security database replication, run the following command on the BDC:
net accounts /sync
A record of the successful full replication events should be logged in the System log.
4. If there is only one Windows 2000 domain controller in the domain, leave the Windows NT 4.0 BDC connected to the network, and physically remove the Windows 2000 domain controller from the network. If you have only one Windows 2000 domain controller, you can perform step 6 now before you continue with the demotion of the Windows 2000 domain controller.
5. You must now demote all the Windows 2000 domain controllers to member servers by running the dcpromo command on the actual domain controller. To run this command, click Start, click Run, type dcpromo, and then click OK. If there are more than one Windows 2000 domain controller, run dcpromo on each of them to make each one a member server, until there is only one Windows 2000 domain controller remaining.
Now you can disconnect the Windows 2000 domain controller from the network, while leaving the Windows NT 4.0 BDC connected. Run dcpromo on this last domain controller, and be sure to choose the last domain controller in the domain option. When this completes, and the computer restarts, it will be a member server in a work group, which you can then rejoin to the domain if you want to. If you disconnected one Windows 2000 domain controller in step 4, then you simply run the dcpromo command on it as described in this step.
Note: To run dcpromo successfully, the network adapter must detect a network connection. Therefore, the Windows 2000 domain controller must be attached to an active hub or switch, even if there are no other connections to the hub or switch, and it is isolated from everything else which is desired.
6. Open Server Manager on the Windows NT 4.0 BDC and promote this computer to a primary domain controller (PDC). If a message appears stating that it cannot contact the PDC and asks if you want to continue, click Yes, and then complete the promotion. When this is complete and the server restarts, verify in Server Manager that the computer it is now described as the PDC.
7. Upgrade this Windows NT 4.0 PDC to Windows 2000. When the Windows 2000 upgrade is complete, the computer restarts to begin the Active Directory installation. During this process, enter the desired domain name.
8. If you have demoted other Windows 2000 domain controllers earlier, you can now promote them back to domain controllers by running dcpromo on them.
Men det er IKKE en løsning Microsoft anbefaler.... :)
