Pre-shipment Configuration of the Branch Office Domain Controller
This chapter outlines the steps to perform the pre-shipment configuration on a staged domain controller. The procedures in this chapter should be completed only when you are about to ship a staged domain controller. After completing these steps, the staged domain controller will be ready to be shut down and shipped to its destination branch office.
Read the Article
|
Quality Assurance of the Domain Controller at the Branch Office
This chapter outlines the steps to finalize the configuration of the staged domain controller after it is shipped to the branch office. After completing these steps, you will be able to begin normal operation and maintenance of these branch office domain controllers.
Read the Article
|
Ensuring Active Directory Health in Branch Office Environments
This chapter outlines how to monitor Active Directory and FRS to ensure your environment is functioning properly.
Read the Article
|
Disaster Recovery for Branch Office Environments
Regular backups of the Active Directory® directory service are essential for the successful operation of a Microsoft® Windows® 2000 environment. This will help to ensure that Windows 2000 domain controllers can be restored and brought back online in a quick, responsive manner in the event of failure. This chapter outlines the steps necessary to back up and restore Active Directory. After completing these steps, Active Directory on your given domain controller should be functioning correctly. This chapter also discusses the process of staging and shipping replacement domain controllers from a staging site.
Read the Article
|
Troubleshooting Guidelines for Branch Office Environments
This chapter outlines the steps necessary to diagnose, understand, and resolve issues that may arise in large Active Directory® directory service branch office deployments.
Read the Article
|
Windows XP Pro in AD Environments, Part 1
The Windows 2000 Active Directory forest is the collection of one or more Microsoft Windows 2000 domains that share a common schema, configuration, and global catalog. You will find all different types of clients in this setup, everything from Windows 9x systems up to and through Windows XP Professional. You might even find Windows NT 3.51, NT 4 and 2000 member servers in a Windows 2000 forest.
Read the Article
|
Apply Group Policies to Groups
The design created by Microsoft for Group Policies in Windows 2000 is to apply them to Organization Units (OUs) instead of applying them to actual user groups. This works great if you can sort your domain into OUs that don't change often and people don't need to be a part of more than one. But if you have people that belong to different departments (IE sales and marketing) and each department needs it own policies this can lead to some rather unpleasant complications. Another issue is applying the policy to only part of the people in the OU.
Read the Article
|
