By installing Active Directory from restored backup media, you can reduce the replication traffic that is initiated during the installation of an additional domain controller in an Active Directory domain. Reducing the replication traffic reduces the time necessary to install the additional domain controller. The procedures in this task are particularly useful for installing domain controllers in remote sites.
To install Active Directory from restored backup media:
1. Click Start, click Run, type dcpromo /adv, and then press ENTER.
2. In the Active Directory Installation Wizard, select Additional domain controller for existing domain.
3. Select From these restored backup files, and point to the same location where you restored the system state data.
4. If the domain controller whose system state backup you are using is a global catalog server, the Active Directory Installation Wizard asks you whether you want this server to also be a global catalog server.
5. Give appropriate credentials for the operation.
6. Enter the domain of the new domain controller. This domain must be the domain of the domain controller whose system state backup you are using.
7. Complete the remaining pages of the Active Directory Installation Wizard.
Dcpromo.exe will install Active Directory using the data present in the restored files, which eliminates the need to replicate every object from a partner domain controller. However, objects that were modified, added, or deleted since the backup was taken must be replicated. If the backup was recent, the amount of replication required will be considerably less than that required for a regular Active Directory installation.
Showing posts with label Windows 2003. Show all posts
Showing posts with label Windows 2003. Show all posts
Sunday, May 11, 2008
Saturday, May 10, 2008
DsRemoveDsDomainW error 0x2015 when removing metadata from Active Directory
From Microsoft KB887424
Description
When you use the Ntdsutil command-line tool to try to remove metadata for a domain controller that was removed from your network, you may receive the following error message:
DsRemoveDsDomainW error 0x2015 (The directory service can perform the requested operation only on a leaf object).
Resolution
To resolve this issue, follow these steps:
1. Click Start, click Run, type ntdsutil, and then press ENTER.
2. At the Ntdsutil command prompt, type domain management, and then press ENTER.
3. Type connections, and then press ENTER.
4. Type connect to server Domain_Controller_Name, and then press ENTER.
5. After the following message appears, type quit, and then press ENTER:
Connected to Domain_Controller_Name using credentials of locally logged on user
6. At the domain management prompt, type list, and then press ENTER.
7. Note the following entry:
DC=DomainDnsZones,DC=Child_Domain, DC=extensionFor example, if the child domain is Contoso.com, note the following entry:
DC=DomainDnsZones,DC=contoso,DC=com
8. Type the following command, and then press ENTER.
delete nc dc=domaindnszones,dc=Child_Domain,dc=extensionNote In this command, Child_Domain represents the name of the child domain that you want to remove. For example, if the child domain is Contoso.com, type the following command, and then press ENTER:
delete nc dc=domaindnszones,dc=contoso,dc=com
9. Quit Ntdsutil.
Description
When you use the Ntdsutil command-line tool to try to remove metadata for a domain controller that was removed from your network, you may receive the following error message:
DsRemoveDsDomainW error 0x2015 (The directory service can perform the requested operation only on a leaf object).
Resolution
To resolve this issue, follow these steps:
1. Click Start, click Run, type ntdsutil, and then press ENTER.
2. At the Ntdsutil command prompt, type domain management, and then press ENTER.
3. Type connections, and then press ENTER.
4. Type connect to server Domain_Controller_Name, and then press ENTER.
5. After the following message appears, type quit, and then press ENTER:
Connected to Domain_Controller_Name using credentials of locally logged on user
6. At the domain management prompt, type list, and then press ENTER.
7. Note the following entry:
DC=DomainDnsZones,DC=Child_Domain, DC=extensionFor example, if the child domain is Contoso.com, note the following entry:
DC=DomainDnsZones,DC=contoso,DC=com
8. Type the following command, and then press ENTER.
delete nc dc=domaindnszones,dc=Child_Domain,dc=extensionNote In this command, Child_Domain represents the name of the child domain that you want to remove. For example, if the child domain is Contoso.com, type the following command, and then press ENTER:
delete nc dc=domaindnszones,dc=contoso,dc=com
9. Quit Ntdsutil.
How to remove an oprhaned domain from Active Directory
Description:
For some reason you have to force demote one of your child domain.
You have follow Microsoft KB216498 "How to remove data in Active Directory after an unsuccessful domain controller demotion". You have remove the cname record in the _msdcs.rootdomain of forest zones in DNS. Also there're no A record and Name Server record of it on DNS. You also have deleted the server name from AD Sites & Services.
However when people logon, they can still see that child domain at the Log on to field. You want it to be disappear from there.
Resolution:
Removing Orphaned Domains from Active Directory (Microsoft KB230306)
3. Click Start, point to Programs, point to Accessories, and then click Command Prompt.
4. At the command prompt, type: ntdsutil.
5. Type: metadata cleanup, and then press ENTER.
6. Type: connections, and then press ENTER. This menu is used to connect to the specific server on which the changes will occur. If the currently logged-on user is not a member of the Enterprise Admins group, alternate credentials can be supplied by specifying the credentials to use before making the connection. To do so, type: set creds domainname username password , and then press ENTER. For a null password, type: null for the password parameter.
7. Type: connect to server servername (where servername is the name of the domain controller holding the Domain Naming Master FSMO Role), and then press ENTER. You should receive confirmation that the connection is successfully established. If an error occurs, verify that the domain controller being used in the connection is available and that the credentials you supplied have administrative permissions on the server.
8. Type: quit, and then press ENTER. The Metadata Cleanup menu is displayed.
9. Type: select operation target, and then press ENTER.
10. Type: list domains, and then press ENTER. A list of domains in the forest is displayed, each with an associated number.
11. Type: select domain number, and then press ENTER, where number is the number associated with the domain to be removed.
12. Type: quit, and then press ENTER. The Metadata Cleanup menu is displayed.
13. Type: remove selected domain, and then press ENTER. You should receive confirmation that the removal was successful. If an error occurs, please refer to the Microsoft Knowledge Base for articles on specific error messages.
14. Type: quit at each menu to quit the NTDSUTIL tool. You should receive confirmation that the connection disconnected successfully.
For some reason you have to force demote one of your child domain.
You have follow Microsoft KB216498 "How to remove data in Active Directory after an unsuccessful domain controller demotion". You have remove the cname record in the _msdcs.rootdomain of forest zones in DNS. Also there're no A record and Name Server record of it on DNS. You also have deleted the server name from AD Sites & Services.
However when people logon, they can still see that child domain at the Log on to field. You want it to be disappear from there.
Resolution:
Removing Orphaned Domains from Active Directory (Microsoft KB230306)
1. Determine the domain controller that holds the Domain Naming Master Flexible Single Master Operations (FSMO) role. To identify the server holding this role:
- Start the Active Directory Domains and Trusts Microsoft Management Console (MMC) snap-in from the Administrative Tools menu.
- Right-click the root node in the left pane titled Active Directory Domains and Trusts, and then click Operations Master.
- The domain controller that currently holds this role is identified in the Current Operations Master frame.NOTE: If this changed recently, not all computer may have received this change yet due to replication.
3. Click Start, point to Programs, point to Accessories, and then click Command Prompt.
4. At the command prompt, type: ntdsutil.
5. Type: metadata cleanup, and then press ENTER.
6. Type: connections, and then press ENTER. This menu is used to connect to the specific server on which the changes will occur. If the currently logged-on user is not a member of the Enterprise Admins group, alternate credentials can be supplied by specifying the credentials to use before making the connection. To do so, type: set creds domainname username password , and then press ENTER. For a null password, type: null for the password parameter.
7. Type: connect to server servername (where servername is the name of the domain controller holding the Domain Naming Master FSMO Role), and then press ENTER. You should receive confirmation that the connection is successfully established. If an error occurs, verify that the domain controller being used in the connection is available and that the credentials you supplied have administrative permissions on the server.
8. Type: quit, and then press ENTER. The Metadata Cleanup menu is displayed.
9. Type: select operation target, and then press ENTER.
10. Type: list domains, and then press ENTER. A list of domains in the forest is displayed, each with an associated number.
11. Type: select domain number, and then press ENTER, where number is the number associated with the domain to be removed.
12. Type: quit, and then press ENTER. The Metadata Cleanup menu is displayed.
13. Type: remove selected domain, and then press ENTER. You should receive confirmation that the removal was successful. If an error occurs, please refer to the Microsoft Knowledge Base for articles on specific error messages.
14. Type: quit at each menu to quit the NTDSUTIL tool. You should receive confirmation that the connection disconnected successfully.
Saturday, April 5, 2008
A duplicate name exist error when connecting to SMB share using CNAME alias
Description
When you are setting up CNAME alias in DNS for a Windows 2003 Server and then try to connect to server using CNAME alias, you may encounter "a duplicate name exists on the network" error.
Resolution
To resolve this problem in Windows Server 2003, complete the following steps:
1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
2. Apply the following registry change to the file server. To do so, follow these steps:
a. Start Registry Editor (Regedt32.exe).
b. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
c. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameCheckingData
type: REG_DWORD
Radix: Decimal
Value: 1
d. Quit Registry Editor.
3. Restart your computer.
When you are setting up CNAME alias in DNS for a Windows 2003 Server and then try to connect to server using CNAME alias, you may encounter "a duplicate name exists on the network" error.
Resolution
To resolve this problem in Windows Server 2003, complete the following steps:
1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
2. Apply the following registry change to the file server. To do so, follow these steps:
a. Start Registry Editor (Regedt32.exe).
b. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
c. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameCheckingData
type: REG_DWORD
Radix: Decimal
Value: 1
d. Quit Registry Editor.
3. Restart your computer.
Sunday, February 24, 2008
How to configure a display message when users log on to the Windows 2003 domain
You can configure Windows Server to display a message to users when they log on. The message appears after the user presses CTRL+ALT+DEL and disappears after the user clicks OK. After the message disappears, the user can complete the logon process.
Configuring a Group Policy Setting for a Domain:
1. On the domain controller, start the Group Policy Management snap-in.
2. Expand the forest object in the left pane.
3. Expand the domains object in the left pane. Expand yourdomain.
4. Right Click Default Domain Policy, and then click Edit.
5. Expand the following folder:
Computer Configuration\Windows Settings \Security Settings\Local Policies\Security Options
6. In the right pane, double-click Policies, and then follow these steps to create the message text:
> On a Windows Server 2003-based domain controller:
a. Click Interactive logon: Message title for users attempting to log on, and then type the text that you want to appear in the title bar of the message dialog box.
b. Click Interactive logon: Message text for users attempting to log on, and then type the text of the message that you want to appear in the message dialog box.
> On a Windows 2000-based domain controller:
a. Click Message title for users attempting to log on, and then type the text that you want to appear in the title bar of the message dialog box.
b. Click Message text for users attempting to log on, and then type the text of the message that you want to appear in the message dialog box
Note: If you do not use carriage returns in your display message, the maximum number of characters that you can add to the logon box is 512. If you add carriage returns, you can add up to 2048 characters (512 characters per line).
Configuring a Group Policy Setting for a Domain:
1. On the domain controller, start the Group Policy Management snap-in.
2. Expand the forest object in the left pane.
3. Expand the domains object in the left pane. Expand yourdomain.
4. Right Click Default Domain Policy, and then click Edit.
5. Expand the following folder:
Computer Configuration\Windows Settings \Security Settings\Local Policies\Security Options
6. In the right pane, double-click Policies, and then follow these steps to create the message text:
> On a Windows Server 2003-based domain controller:
a. Click Interactive logon: Message title for users attempting to log on, and then type the text that you want to appear in the title bar of the message dialog box.
b. Click Interactive logon: Message text for users attempting to log on, and then type the text of the message that you want to appear in the message dialog box.
> On a Windows 2000-based domain controller:
a. Click Message title for users attempting to log on, and then type the text that you want to appear in the title bar of the message dialog box.
b. Click Message text for users attempting to log on, and then type the text of the message that you want to appear in the message dialog box
Note: If you do not use carriage returns in your display message, the maximum number of characters that you can add to the logon box is 512. If you add carriage returns, you can add up to 2048 characters (512 characters per line).
Subscribe to:
Posts (Atom)