Article DirectoryJust another article directory

To support users who work at multiple computers, you can set up mcitp 2008 roaming user profiles. A roaming user profile is based at the server and is downloaded to the local computer every time a user logs on. In contrast to a local user profile, which resides on only one client computer, a roaming user profile is available at any workstation or server computer on the network. Changes made to a user’s roaming user profile are updated locally and on the server when the user logs off. This profile is created by a system administrator and is stored in a shared folder on a server.
The first time that a user logs on at a computer, Windows Server 2003 copies all documents to the local computer. Thereafter, when the user logs on to the computer, Windows Server 2003 compares the locally stored user profile files and the roaming user profile files. It copies only the files that have changed since the last time the user logged on at the computer, which makes the logon process shorter.
Mandatory User Profiles
To specify a profile for individuals or an entire group of users, you can set up mandatory user profiles. A mandatory user profile is a read-only roaming profile, based at the server and downloaded to the local computer every time a user logs on. It is available at any workstation or server computer on the network. Users can modify the desktop settings of the computer while they are logged on, but none of these changes are saved when they log off. The next time that the user logs on, the profile is the same as the last time that he or she logged on. Only system administrators can make changes to mandatory user profiles. The mandatory profile settings are downloaded to the local mcitp enterprise administrator computer each time the user logs on. You can assign one mandatory profile to multiple users who require the same desktop settings. If you need to change the desktop environment for this set of users, you can do so by changing only one profile.
Preferably, profiles should be managed by using Group Policy. Although mandatory user profiles are permitted, they are more likely to create administration problems. For information about Group Policy, see Chapter 11, “Administering Group Policy.”
Local User Profiles
A local user profile is based at the local computer and is available at only the local com?puter. When a user logs on to the client computer running Windows Server 2003, he or she always receives his or her individual desktop settings and connections, regardless of how many users share the same client computer. Windows Server 2003 automatically creates a local user profile the first time that a user logs on to a workstation or server computer. The local user profile is stored in the C:\Documents and SettingsX User_logon_name folder on the computer, where C is the name of your system drive and User_logon_name is the name the user types when logging on to the system.
A user changes his or her local user profile by changing desktop settings. For example, a user might make a new network connection or add a file to My Documents. Then, when a user logs off, Windows Server 2003 incorporates the changes into the user profile stored on the computer. The next time the user logs on to the local a certification exam computer, the new network connection and the file are present.

Read more on Roaming User Profiles…

In this exercise, you use Repadmin to display the replication partners for a n10-004 network server, display the highest USN on the server, determine if the server is up-to-date with another server, display the connection objects for the server, and force replication between replication partners.

Read more on The Exercise 2: Using Repadmin…

Use the Active Directory Users And Computers console and the Security tab in the 70-680 exam Properties dialog box for the OU to create OUs for the purpose of hiding objects. Only users who can modify the ACL on an OU are able to hide objects using this procedure.
To create an OU to hide objects, complete the following steps:
1.Create the OU where you will hide objects, as described in “Creating OUs.”
2.Right-click the OU and select Properties.
3.In the Properties dialog box for the OU, click the Security tab.
Note To view the Security tab in the Properties dialog box for an OU, you must select Advanced Features from the View menu on the Active Directory Users And Computers console.
4.In the Properties dialog box Security tab, shown in Figure 6-6, remove all existing permissions from the OU. Click Advanced.
5.In the Advanced Security Settings dialog box for the OU, clear the Allow Inheritable Permissions From The Parent To Propagate To This Object And All Child Objects check box.
6.In the Security message box, click Remove. Click OK.
7.In the Properties dialog box Security tab, identify the groups that you want to have full control on the OU. Grant those groups full control.
8.Identify the groups that should have generic read access on the OU and its contents. Grant those groups read access.
9.Identify any other groups that might need specific access, such as the windows 7 certification right to create or delete a particular class of objects, on the OU. Grant those groups the specific access. Click OK.
10. Move the objects you want to hide into the OU.
A site is a set of IP subnets connected by a highly reliable and fast link (usually a LAN). Site structure mirrors the location of user communities. Sites have two main roles: to facilitate authentication and the replication of data between sites. Active Directory replicates information in two ways: intrasite (within a site) and intersite (between sites).
For optimum network response time and application availability, place at least one domain controller in each site or two domain controllers in each domain.
Intersite replication is replication that occurs between sites.
A site link is a logical, transitive connection between two or more sites that mirrors the network links and allows replication to occur.
Bridgehead servers are the contact point for exchange of directory information between sites. When two sites are connected by a site link, the KCC automatically selects MCITP Enterprise Administrator bridgehead servers. You can designate bridgehead servers manually, called “preferred” bridgehead servers.

Read more on Creating OUs to Hide Objects…