2 - Windows Server 2
2 - Windows Server 2
2 - Windows Server 2
Table of Content
Creating User Accounts Creating Group accounts Creating Computer Accounts Group Policy Disk Space, Sharing and Permissions Disk Management
Group Accounts
Group accounts help to minimize the administrative effort associated with assigning rights and permissions to users with common needs. You have two different types in Windows Server 2003 1) Security Groups q A Security Identifier (SID) that allows groups assigned permissions to resources as well as rights to perform various tasks defines this group. 2) Distribution Groups q Are used when sending an e-mail to a group, which then sends it to all members of that group.
Group Policy
Administrators use Group Policy to define options for managing configurations of servers, desktops, and groups of users. Local policy settings can be applied to all machines, and for those that are part of a domain, an administrator can use Group Policy to set policies that apply across a given site, domain, or range of organizational units (OUs) in the Active Directory
Introduction to Group Policy in Windows Server 2003 Microsoft Corporation Published: April 2003
Group Policies
Group policies deal with account lockouts, passwords and Kerberos etc. Lockout: - Number of times a user can try to login before being locked out. Passwords: - Enforce password history, defines the number of passwords to be unique before a user can reuse an old password. (After how many days should a user change their password.) Kerberos: - Enforce user logon restrictions using Key Distribution Center (KDC. To view group policies: 1. Right Click the Domain object in Active Directory Users and Computers, then click on Properties. 2. Click on the Group Policy tab, and then click on the Edit button to show account policies.
Shared folders
These are data sources that have been made available over the network to authorized users. Centralized network resources through the use of shared folders There are two ways of creating shared folders:
Creating a shared folder using Windows Explorer Creating a shared folder using Computer Management Console
NTFS Permissions
These permissions can only be applied on files and folders that exist in partitions formatted with NTFS file system. NTFS permissions are configured through the Security tab, and its cumulative, that means if a user is member of different groups, his permissions are all permissions put together. It can be set at file or folder level, and child folders and files inherit permissions unless otherwise specified.
1. Under the Sharing and Security of Folder, select the Security tab 2. Click the Add button to add user, computer and groups. 3. Then select permission for different users, either Full Control, Modify, Read & Execute, Read, Write etc. 4. Click the advanced button, to specify inheritable properties. 5. To remove any Groups or Users, click on Remove. 6. Then Click Apply and the OK.
For special permissions, click advanced button and modify Permissions for users and groups. When Shared folder and NTFS permissions are combined: Over a network the most restrictive permission of the two becomes the effective permission. When a file is accessed locally, only NTFS permissions apply.
Disk Management :
Windows 2003 Server supports two data storage types
Basic Disks
Uses traditional Disk management Techniques and contains primary and extended partitions and logical drives, any can be configured with FAT, FAT32 and NTFS. Each partition acts as a separate storage on the disk. If more then one primary partition is configured, only one can be marked as the active partition.
Dynamic Disks
Does not use partitions, but volumes instead, because they provide additional features and capabilities. Provides a new flexibility, as there are basically no restrictions to the number of volumes that can be implemented on the disk. Not restricted to the size initially configured.
Basic Disks
Primary Partitions: There are at least one configured on a drive Usually contain the operating system start-up files at the beginning of the partition. The active primary partition is where the computer looks for the hardware specific files to start the OS. Extended Partitions: Created from space that is not yet partitioned, meaning space that is left after primary partition has been created. Can only be one extended partition on a standard basic Disk. It is not formatted or does not have a drive letter assigned. Once created, it can be further divided into logical drives each getting their drive letter. The disk is described as logical because it does not actually exist as a single physical entity in its own right
3. Then select the Extended Partition radio button and click Next.
4. Specify the size of the partition in MB, and click Next and then Finish
Disk Management:
Fault Tolerant disk Strategies
Allows setup of the system to recover from hardware and software failure. Windows 2003 Server allows this fault tolerance through software RAID (Redundant Array of Independent Disks):- which is a set of standards for lengthening disk life, preventing data loss and enabling relatively uninterrupted access to data. RAID is setup depending on level of fault tolerance. Your Server will include either 2-3 harddrives with RAID controllers. The Harddrives are controlled through these controllers depending on how it has been setup, whether it be for backup, or for speed. Lets look at the different levels of RAID setup.
RAID Levels
1) RAID level 0: - Striping (Striped Volumes) with no other redundancy features, it is just for extending disk life and improve performance. 2) RAID level 1: - Used for simple mirroring, providing a means of duplicating the operating systems files in the event of disk failure. It places the backup on a different controller that is used by main disk. This RAID is much slower as all data has to be written twice.
3) RAID level 2: - Uses an array of disks whereby the data is striped across all disks in the array, and it contains errorcorrecting information on each to reconstruct data from a failed disk.
Raid levels
4) RAID level 3: - Same as level 2, but stores the error correcting info only on one drive, so if that drive fails cannot reconstruct the data. 5) RAID level 4: - Same as level 2, but can perform checksum verification, which is the sum of bits on a file. So when disk fails and data is reconstructed, the reconstructed file size is compared the checksum size, and if the two dont match then files might be corrupted. 6) RAID level 5: - Includes striping, error correction and checksum verification, and all are spread across all of the disks. However this RAID uses more memory then others. Recovery for this RAID provides same guarantee as with disk mirroring (level 1), and has much faster read access then Level 1.
References
MCSE (Exam 70-294) Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure 2nd Edition, Published by Microsoft Press 2006. Jill Spealman, Kurt Hudson, and Melissa Craft with Anthony Steven of Content Master, ISBN: 0-7356-2286-8 Windows Server 2003 Weekend Crash Course Published by Wiley Publishing 2003. Don Jones, ISBN: 0-7645-4925-1 Active Directory Cookbook Published By OReilly 2003. Robbie Allen, ISBN: 0596-00464-8