Get questions answered, anywhere
Nowadays it is pretty common for most people to carry some type of cellular phone with them wherever they go.
Nowadays it is pretty common for most people to carry some type of cellular phone with them wherever they go.
Active Directory (AD) has been around since Windows 2000 and has changed the way that many administrators think about and actually manage domain environments. Microsoft has upped the ante again for the Windows Server 2008 version of AD. This tip will look at some of the newly reshaped services for Active Directory included with Windows Server 2008.
The 2008 release of AD has allowed Microsoft to configure more server side items to function as a part of the directory service. Active Directory for Windows Server 2008 includes the following services:
The newly integrated services have existed in previous versions of Windows as individual server components, however in Windows Server 2008 the functionalities have been Active Directory Integrated for simplified management and control.
Now that Windows Server 2008 has been released and I have had a chance or two to dig into some of the new Server OS I will be posting here as I learn more about the new platform and feel confident that information I learn will be of use to someone.
I have a few posts scheduled for release this week and the Windows 2008 items among them will be posted hopefully with a good deal more to follow.
But enough with the administrative babble let’s get back to regularly scheduled content.
In Windows Server 2003 R2 you can centralize the storage of user data so that information stored by a user within your environment is stored on the network rather than on each of their desktops. This will allow the data to be backed up during normal disaster recovery planning and backup operations and keep everything in a central location in case the user needs to change PCs.
This tip will look at the basics for redirecting folders in Windows Server 2003 R2.
To configure folder redirection throughout your environment in Windows Server 2003 R2, you can use a group policy object.
Note: Before configuring a Group Policy Object to manage Folder Redirection, you will need to create a share on the server that will hold the redirected folders.
Here you will see the following choices for user folder redirection:
· Application Data –
· Desktop –
· My Documents –
· Start Menu –
The redirection for each of these user folders can be configured separately, allowing you to redirect only the My Documents folder for the Accounting OU and the Start Menu for the IT OU.
This will display the Properties Dialog for the selected folder providing options for the redirection.
· Redirect to The User’s Home Folder – using this option will place the contents of the My Documents folder within the Home Folder configured in the users account settings. This option only applies to My Documents.
· Create a Folder for Each User under the Root Path – using this option will create a folder for each affected user under the root path (also specified in this dialog). A common setting, this can help keep all of the user’s redirected folder data in the same location. This setting is not available for the Start Menu folder.
· Redirect to the following location – this will allow all of the redirected user folders to exist in the same location, adding %UserName% to the path can also create individual folders for each user, similar to the second option above. If a user specific environment variable such as %UserName% is not included, all of the redirected content will be moved to the same folder.
· Redirect to the local user profile location – using this setting will redirect the folder content to the location of the local user profile. This is the default setting.
Once the target settings are selected you will need to specify a root share for the data redirection. You will enter the Root Path in the format of \\Servername\sharename . This path should point to the share you configured earlier.
If you select the advanced setting for this folder in the setting dropdown you would also be able to specify settings independently for groups of users. For example, you can redirect the My Documents folder for Domain Admins to a different location than the My Documents folder for the Accounting group. This target location may be configured so that permissions prevent other users from seeing or accessing the contents. The other settings remain the same.
Using folder redirection takes only a few minutes to configure and can help keep user data in your environment in a centrally managed location instead of scattered across desktop computers.
Monitoring resources on your system is not limited to functions available in the previously mentioned Performance Monitor. Using this method will provide you with a plethora of information about your system and should not be ignored, but here I want to focus on disks.
Windows Server 2003 includes another tool in the Computer Management Console for working with Disks that are connected to the system. This snap-in is called Disk Management and aides in changing drive letters, managing partitions, viewing free space and other things.
The Disk Management snap-in can perform the following tasks from a central view:
· Display a listing all of the drives connected to the system
· Displaying used/free space and drive size in text and GUI format
· Display the status of each drive
· Display the Disk type and File System of each drive
· Assist with changing drive letters for connected drives
· Change disk type from Basic to Dynamic
· Delete, Manage, Create partitions
To use the Disk Management snap-in open the Computer Management Console by right clicking My Computer from the Windows Server 2003 Start Menu and selecting Manage.
From here, select the Disk Management snap-in from the left pane of the console, this will display it in the right pane with a list of detected drives in the top portion and a graphical representation of the free space for each in the lower portion of the right pane.
The following information is presented in the initial view:
These options are displayed in the lower portion of the console’s right pane in a graphical format.
What other things can Disk Management do?
Showing information about connected disks is a good starting point, but the Disk Management Snap-in can perform other functions as well. For example, you can change the drive letter of any of the connected disks from this snap-in.
To do so, simply right click the drive (in the list or the GUI) that you wish to change and select Change Drive Letter or Path. This will produce a dialog listing the drive you selected and the following action buttons:
Select the drive letter you wish to change and click the change button. A dialog will appear allowing you to always mount the drive with a letter or to mount the drive as an empty folder.
The currently used drive letter will be selected in the drop down list. Simply select a new letter (or enter a path for the folder mount point) and click OK all the way out to the Computer Management Console.
One of the reasons this can be handy is because Windows doesn’t always follow the next lowest drive letter available policy. If you have a network drive mapped to a certain letter, and attach a USB drive, the USB drive will take the next lowest available letter on the local system, which may be mapped to a network resource. The mapped drive is not updated or changed to reflect this, so the USB device may need to be reassigned to a different letter.
You can also use the snap-in to handle partitions. Creating a partition is as simple as right clicking the free space in the GUI representation for a drive and selecting the action you want to perform on the drive.
New Partition – starts the new partition wizard to create a new partition in available space
New Logical Drive – starts the partition wizard to create a new mountable drive on a partition
Once the partition wizard starts click next on the welcome screen and complete the following steps to create a new primary partition:
Note: While in the new partition wizard you can also choose to create an extended partition or a logical drive, the creation steps are the same for an extended partition and begin with drive letter selection and formatting for a logical drive.
You can also mark partitions as active from the Disk Management Snap-in by right clicking an item in the list that does not have an active status and selecting Mark partition active. This will allow the BIOS of the system to see this as a valid system partition and is only valid on partitions.
Hopefully this look at the Disk Management snap-in has pointed out some of the usefulness of this tool, managing Windows Server 2003 system disks can be quite a challenge, but this tool can provide a great deal of help.
Note: This snap-in is available on all Windows 2000 and later Operating Systems.
Windows Server 2003 brings forward many of the features first introduced in Windows 2000 one of those applications is the Removable Storage snap-in available in the Computer Management Console.
This tip will look at this snap-in and how it can make maintaining a Windows Server 2003 system a little easier.
The snap-in can be accessed by right clicking My Computer (on the Windows Server 2003 Start Menu) and selecting Manage. This will start the Computer Management Console. In the left pane you will find both the Removable Storage Object. Selecting it with a single left click will put its contents in the larger right pane of the console.
Removable Storage
The removable storage snap-in allows administrators to manage tape backup libraries and media sets within Windows Server 2003, the snap-in also contains CD-Rom drives. The categories of devices listed within the removable storage snap-in are as follows:
A media pool is a collection of media units that can be managed together. The existing media pools available in Windows Server 2003 are:
· Unrecognized – This pool contains media that removable storage does not recognize or that has not been written to as of yet.
· Free – Media contained in this media pool are available for use and do not contain data
· Import – Media contained in this pool has been used before by removable storage, perhaps with another server
· Application – User created media pools associated with and managed by specific applications, for example Windows Backup
Automated and non-automated libraries require different techniques to mount and begin using media. When using a non-automated library, you will insert a tape manually, if removable storage recognizes the media it will mount it and place it in the correct media pool. If the media is not mounted you can mount it by right clicking on the media within the media group in Removable Storage and select Mount.
Disabling media and devices
Within Removable Storage you can disable both individual tapes and tape drives. You might disable a specific tape to prevent use temporarily or to remove bad tapes from rotation.
To disable a piece of media, complete the following steps:
Disabling a drive follows a similar process detailed below:
As you can see the Removable Storage snap-in allows simple maintenance of removable media for backup and other uses within Windows Server 2003. In future tips I will explore each aspect of the snap-in in greater detail.
Occasionally file system fragmentation can cause the system administrator tons of frustration. Slow running systems, non functioning applications or processes, and a host of other issues.
Windows Server 2003 includes the Windows Disk Defragmenter to help combat these fragmentation problems. The GUI version of this utility is included in the Computer Management Console and will be the focus of this tip.
Previous mention: In a tip at TechRepublic, I looked at the disk defragmenter as a scheduled task. http://blogs.techrepublic.com.com/datacenter/?p=169
Note: Before beginning with the Disk Defragmentation utility, make sure to disable the screen saver on the Windows Server 2003 system. A running screensaver can cause the Windows Defrag utility to stop when the screensaver activates and restart when it turns off.
What is defragmentation?
When Windows computers are used the day to day use of files on the system can cause files to be spread out across disks, known as fragmentation. Stated simply, this is the noncontiguous placement of files on a disk. Using the Defragmentation utility Windows can reorganize files to put like files together on disk and free space near the end.
This will reduce disk movement and overall wear and tear on the hard disk.
Other Utilities
I will take this opportunity to mention that there are commercially available utilities that will also defragment your system(s). These can be helpful in constantly preventing defragmentation, or providing central administration for the process, which is not available with the utility shipped with Windows. In most cases, a commercial utility is not necessary to accomplish the task of defragmentation.
So where do I start?
To get started with the Windows Disk Defragmenter, open the Computer Management Console on your Windows Server 2003 system by right clicking My Computer on the Start Menu and selecting Manage from the context menu.
Within this console, you can select Disk Defragmenter from the left pane. This will load the snap-in into the console’s right pane.
From there you can select the disk to defragment, provided the Windows Server 2003 you are working on has multiple disks.
To defragment your system, complete the following steps:
1. Highlight the drive letter you wish to defragment
2. Click the Defragment button to begin analysis and defragmentation of the selected drive
Note: When you select Defragment, Windows will first analyze the drive to see if it needs to run a defragmentation, and then proceed with defragmenting the drive. If you select the Analyze button, Windows will check for the need to defragment the drive and display its findings.
How do I know if defragging is needed?
The best way to know if your system needs to defrag is to run an analysis of your computer and let Windows tell you one is needed. More practically, you might notice things are very slow, read/write becomes slow all the time, and some applications will be painfully slow or fail to open at all.
It is unlikely that fragmentation will pop up frequently, but proactive measures can certainly keep things moving in the right direction. It is a good idea to include fragmentation analysis in your monthly routine, that way you are likely to catch the problem before it becomes serious.
In a post at http://www.techrepublic.com I previously provided an overview of the Performance Logs and Alerts Snap-in within Windows Server 2003. The goal here is to look at the Performance Logs exclusively and create logs for counters and traces.
What is the difference which method I use?
The system monitor is a live look at counter activity. It is active until you close it, once closed it will need counters added again.
Performance logs work a little differently, recording events to log files or databases for later review. This will allow you to configure a log and review it on a weekly basis.
Logging types
Performance logs differ from the system monitor in another way as well. They can be configured to work with counters (covered in another tip) which will show specific continual data about a system object, but they can also be created for traces.
Traces are instances of an event that happens to an object. For example, if you wanted to create a trace log to monitor processor activity, as activity occurred it would be recorded.
Another nice thing about trace logs is that they can be started and stopped; when a trace is stopped its settings are still saved.
Counters are snapshots of a given object at set points in time. A counter log will work nicely, however if no activity happens when the object is sampled, there will be very little recorded.
Creating performance counter logs
To create a performance log for counters monitoring, for example, the CPU complete the following steps:
Note: You will need to choose to add all counters for the Processor object or to add only select counters.
If the counter you have added has multiple instances you will need to decide if you want to use all instances of the counter or to use selected instances.
The sample interval specifies how often a sample for this log will be taken.
On the schedule tab you can choose to start and stop the log at a given time or manually using the shortcut menu. For reviewing purposes you might choose to set a start and stop time for the log to make things a bit easier.
Creating performance trace logs
Creating trace logs for events is very similar to creating logs for counters. A trace log can be created by completing the following steps:
Doing this will open a dialog box allowing you to configure the settings for your new trace
If you want to monitor other non-system provided objects, select the Non-system Providers option button and click Add to add new providers that can be traced.
Note: These options are the same as the log file options discussed above with two exceptions:
Sequential trace file – writes entries in the log file sequentially up to the maximum file size, if specified
Circular trace file – Overwrites old data with new data when the file reaches a specified size limit
Counter and Trace logs can be very helpful in monitoring your Windows Server 2003 systems at consistent intervals. When used with the System Monitor these logs can aide in finding long term system issues and determining if they have been happening consistently.