Section 3.2. Exam 70-290 Suggested Exercises

3.2. Exam 70-290 Suggested Exercises

Exam 70-290 expects you to know how to manage and maintain a Windows Server 2003 environment. You'll need plenty of previous hands-on experience to pass the exam. You'll need to review the study guide closelyespecially any areas with which you are unfamiliar. This section provides a numbered list of exercises that you can follow to gain experience in the exam's subject areas. Performing the exercises will be useful for helping to ensure you have hands-on experience with all areas of the exam.

Although you can study for the exam using Windows Server 2003 on a single computer, I recommend setting up a test network with at least two computers: a server running Windows Server 2003 acting as a domain controller and a workstation running Windows XP Professional from which you perform most administration. Some of the exercises in this section require two computers on a network.

In addition to performing the exercises below, you should also have experience using each of the Windows Server 2003 administrative tools described in the Study Guide.

3.2.1. Using Remote Desktop for Administration

1. Configure a server so that it can be remotely managed using Remote Desktop.

2. Open the Remote Desktop Connection client, and then click Options.

3. Establish a remote session with the computer from a workstation or another server.

3.2.2. Using Remote Assistance

1. Configure a server so that it can send Remote Assistance requests.

2. While logged on to the server, ask for remote assistance.

3. Accept the remote assistance request on another computer.

4. Access the remote server and give assistance.

3.2.3. Examining Hardware Drivers

1. Configure a server so that it displays a warning prompt if someone attempts to install an unsigned driver.

2. Using Device Manager, check the current network adapter driver on the server to ensure it has a signed driver.

3. Print a summary of the server's installed devices .

3.2.4. Troubleshooting Hardware Devices

1. Using Device Manager, check a server's network adapter for possible resource conflicts.

2. Start the Hardware Troubleshooter and proceed as if the network adapter wasn't working properly.

3. Restart the server.

4. During startup, press F8.

5. Review the startup options.

3.2.5. Examining Disks and Volumes

1. Using Computer Management, examine a server's disks and volumes.

2. Determine the disk type, layout, and volume formatting.

3. Determine which volume is the system volume.

4. If a disk on the server has unallocated space, create, and format a new volume using NTFS.

5. Give the new volume a drive letter.

6. Remove the drive letter on the new volume.

7. Mount the new volume to an empty NTFS folder on another volume.

3.2.6. Create a Dynamic Disk

1. Create a dynamic disk or convert a basic disk to a dynamic disk.

2. Create a volume on the dynamic disk. Leave space so that volume can be resized.

3. Resize the dynamic volume.

4. Create a RAID-1 or RAID-5 volume.

3.2.7. Using DiskPart

1. Start DiskPart.

2. List the current disks.

3. Select a disk and list its volumes.

4. Exit DiskPart.

3.2.8. Using Check Disk

1. Check the integrity of all volumes on a server. Be sure to correct any problems found.

2. Ensure the system volume is checked and fixed as necessary.

3. Restart the server. Note the procedure Check Disk uses to examine the system volume.

3.2.9. Change a Server's Name

1. Determine the name of a non-DC server.

2. Change the server's name.

3. If the server is a member of a domain, remove the server from the domain.

4. Rejoin the server to the domain.

3.2.10. Create Security Groups

1. Create a domain local security group.

2. Add users and other groups as members of the security group.

3. Try to change the group scope.

3.2.11. Determining Group Membership

1. Access a group and determine its members.

2. Determine whether the group is a member of any other groups.

3. Determine the members of the same group from the command line.

4. Determine the group scope from the command line.

5. Add a user to the group using the GUI and the command line.

3.2.12. Creating User Accounts

1. Create a user account for a normal user.

2. Make the user a member of the appropriate groups so the user can access network resources.

3. Create a user account for an administrator.

4. Make the user a member of the appropriate groups so the user can perform domain administration.

3.2.13. Exporting User Accounts

1. Export user accounts from Active Directory. Be sure to get all LDAP properties.

2. Export user accounts from Active Directory getting only the following LDAP properties: DN, objectClass, sAMAccoutName, sn, givenName, and userPrincipalName.

3.2.14. Configuring User Profiles

1. Create a default user profile for users.

2. Create a new user account.

3. Log on as the user and ensure that the user has the default user profile.

4. Log off the user.

5. Configure the user with a roaming profile.

6. Log on as the user.

7. Confirm the roaming profile is being used.

3.2.15. Resolving Account Disabled and Locked Out Accounts

1. Determine whether any user accounts are locked out using the GUI and the command line.

2. If an account is locked out, clear the lockout so the user can log on.

3. Disable a user account.

4. Using the command line, confirm the account is disabled.

5. Enable the account using the command line.

3.2.16. Configuring Access to Shared Folders

1. Determine all the shared folders on a server.

2. Create a new share.

3. Configure permissions on the share so only Domain Users and Administrators have access.

4. Allow Domain Users to have Change access.

5. Allow Administrators to have Full Control.

6. Change the NTFS permissions on the folder so no one has access.

7. Try to access the shared folder over the network.

8. Take ownership of the folder.

9. Assign NTFS permissions on the folder so that Domain Users and Administrators have appropriate access.

10. Stop sharing the folder.

11. Try to access the shared folder over the network.

3.2.17. Allowing a User to Use Terminal Services

1. Determine which users currently have Terminal Services permissions.

2. Allow a user to access Terminal Services.

3. Remove a user's Terminal Services access.

3.2.18. Accessing the Event Logs

1. Access the event logs on a remote server.

2. Filter the application event log so that only critical and warning events are displayed.

3. Grant a user permission to access the security logs.

3.2.19. Using Task Manager

1. Determine the current CPU and memory usage on a server.

2. Using the System utility, configure the server so that it has two times as much virtual memory as physical memory.

3. Determine the amount of used and unused virtual memory.

3.2.20. Using Performance Monitoring

1. Configure performance monitoring on a server as you would for a database server.

2. Configure performance monitoring on a server as you would for a web server.

3. Configure performance logging to monitor a server according to a schedule.

4. Configure a server with performance alerts for 95 percent or higher CPU utilization and less than 10 percent free space on all essential disks.

5. Determine if a server has any performance bottlenecks.

3.2.21. Configuring Disk Quotas

1. Enable disk quotas on a volume.

2. Configure a quota warning of 900 MB and a quota limit of 1 GB.

3. Determine how much space each user is using on the volume.

4. Allow a user to have a quota warning of 2 GB and a quota limit of 3 GB.

3.2.22. Managing Print Queues

1. Create a shared printer.

2. Check the security permissions on the print queue.

3. Change the location of the printer's spool folder.

4. Check the NTFS permissions on the spool folder to ensure that they are configured properly.

5. Set the print queue priority to 50.

3.2.23. Managing Internet Information Services

1. Configure a server for use as a web server.

2. Allow only anonymous access to the server.

3. Configure all directories so that users can read files and run scripts and applications. Log visits but do not allow writing or directory browsing.

4. Reset the IIS services in the GUI and from the command line.

3.2.24. Configuring Software Update Infrastructure

1. Install an update server.

2. Configure policy so that updates are installed automatically.

3. Configure policy so that the update server is used.

3.2.25. Managing Software Site Licensing

1. Determine the site license server for a domain.

2. Determine whether a server uses per-server or per-user/per-device licensing.

3. Determine the current licensing for each server in a domain.

3.2.26. Managing and Implementing Disaster Recovery

1. Create a disaster recovery plan for a server.

2. Create an ASR disk.

3. Schedule full backups of the server on a weekly basis.

4. Schedule daily incremental backups on the server.

5. Perform a test restore to original, alternate, and single locations.

3.2.27. Restoring Data from Shadow Copy Volumes

1. Enable shadow copies on a volume.

2. Create shadow copies of the volume's shares.

3. Install the shadow copy client.

4. Access the shadow copy of a share.

5. Restore a corrupted or deleted file from previous version.