Best Practice Active Directory Litmus Test
Professionals: Install the Active Directory Feature of Windows Server
Amateurs: Use Windows Servers Only as Member Servers
Implementing Active Directory
While the uptake of Windows Server 2008 has been brisk, only a minority of administrators are confident of installing the Active Directory feature. What amateurs do is only install Windows Server 2008/12 as a member server for their SQL database and mail servers.
Best Practice for Installing Active Directory
When you move to Active Directory, there are crucial decisions to make. By analysing the following factors the best practice will become clear.
1) How will you begin your migration? Reformat the machines and build from scratch; I have heard this strategy called 'Wipe and Roll'. Alternatively, go for an 'In Place' upgrade to the new system. Simple, but no rollback, therefore impractical for big organisations.
2) Understand DNS and choose the best naming system for your new root domain. DNS with its new SRV records is vital for Active Directory. So do not even think about promoting a member server to a domain controller until you are an expert on DNS.
3) Plan how many domains you really need, and how they will be linked?
4) Take advantage of Organizational Units and delegation to manage your users and computers.
5) Develop a vision of your desktops, create that lockdown through Group Policy.
6) Calculate the best distribution of physical sites. Consider upgrading network connections.
7) Take the time to understand the Windows 2000 Schema as it defines all the objects in Active Directory.
8) Upgrade the desktops first. The reasons for this tactic are practical rather than logical - users need the benefits of XP Professional quickly.
See much more about Active Directory here.
Import users from a spreadsheet. Just provide a list of the users with their fields in the top row, and save as .csv file. Then launch this FREE utility and match your fields with AD's attributes, click and import the users.
Optionally, you can provide the name of the OU where the new accounts will be born. Download your FREE bulk import tool.
If you need more comprehensive software, download a free trial of SAM (Server & Application Monitor)
For most operations Windows 2003 uses the multiple master model. For example if you have three domain controllers, you can physically create a new user in the NTDS.dit database on any of the three. Five minutes later, the new user object will be replicated to the other domain controllers.
Unlike NT 4.0, there are no primary and backup domain controllers in Windows 2003. However, a few operations are so critical that only one domain controller can carry out that operation. These operations are called Flexible Single Master Operations (FSMO); creating a new child domain would be one example of a single master operation.
I have to confess a hidden agenda with FSMO. If I want to instantly know how well someone knows Active Directory, I introduce FSMO into the conversation and watch their reaction. Professionals will know what FSMO means and its significance, amateurs just frown.
The Five FSMO Roles Are
See much more about Active Directory here »
Over 40 of Guy's litmus tests. Have fun while you learn about aspects of computing. Stacks of ideas to check your servers, networks and security.
Your eBook has printer friendly pages and lots more screen shots.
Guy's Litmus test is a concept that you can apply anywhere. Each test gives you an instant answer to the simple question:- 'Are you dealing with a professional, or are they an amateur? Is this the real deal, or is it a turkey?' The Litmus Test concept is rather like Best Practice, but it reduces a 27 page report to one sentence.
Learn about Windows 8 and Active Directory