(Paperback - Older Edition)
This pocket-sized resource is your fast-answers, daily operations guide to Microsoft Windows XP-based desktop administration. Get critical details through quick-reference tables, lists, and step-by-step instructions.
More Reviews and RecommendationsWilliam Stanek has taught millions of people about the Internet and networking technologies. His work has appeared in leading magazines such as PC Magazine and Dr.Dobb's. He has written over a dozen computer books, including bestsellers. He is the author of many Micrsoft Press® Pocket Consultants including Microsoft Exchange 2000 Server Administrator's Pocket Consultant and Microsoft SQL Server 2000 Administrator's Pocket Consultant.
Reader Rating:
See Detailed Ratings
November 19, 2002: Where I work we planned a move to Windows XP for some time. It's a major change from where we were (Windows 98 and Windows NT 4.0 Workstation). I knew I would need a great new reference to help with my part of the transition. I bought several books. Two in the pocket series (this one and the Windows 2000 Administrator's Pocket Consultant). William Stanek's, 'Windows Xp Administrator', is a tremendous help for anyone working with Windows XP. The book has 14 chapters. It covers everything you are going to use on a day to day basis. I found the writing style is easy to follow. For the last few months I grabbed for this book every time I needed a fast answer about Windows XP. Everyone using Windows XP needs this book. I had trouble putting a book down and have no complaints at all about it.
Reader Rating:
See Detailed Ratings
November 14, 2002: If you need to learn about Windows XP Pro and related technologies this is the book for you. It is very easy to read and the author has obviously come from working in the real IT world. It is actually enjoyable to read for a text book. I've found concepts are written in a way that is useful. The book focusses on a lot of Group Policy issues. The types of every day questions and issues are answered. All the essential technical are explained clearly. I don't know why anyone would give it low marks unless they were a competing author or they just didn't understand what the book is about. It's not meant to be an all in one reference. Like the description says it focuses on daily tasks and key issues. The things you use. When you pair this book with the Windows 2000 Server Pocket Consultant like the author says on Page 1 you really do have a complete library. It's an excellent day-to-day reference. It also helped me study for the Microsoft exams (but it's not a replacement for actual exam guide). There isn't an administrator I know that doesn't have it or one of the others.
The Barnes & Noble Review
Whether you're upgrading your entire enterprise or simply buying new PCs on an ad hoc basis, Windows XP Professional is coming into your enterprise. If you're responsible for supporting or administering it, this handy pocket guide offers you more useful answers per ounce than any other book we've seen. It's especially strong on XP's new administrative features, and those really important tasks (like setting up desktop VPN connections) that you won't do often enough to memorize on your own.
The book's organized into four sections: essentials, core administration, networking, and optimization/recovery. In 350 pages, it manages to be remarkably complete. Want to use Windows XP's new Remote Assistance feature to resolve users' problems without leaving your computer? Prohibit users from setting up Internet Connection Sharing on your DNS domain? Set a new home page for all your users at once? Place custom content on each user's desktop? Use System Restore across a network? Lock the taskbar, so it can't be moved or lost? William B. Stanek walks you through all these tasks, and more.
We could go on. Setting disk quotas. Managing security zones. Using notebook power schemes. Rolling back troublesome driver versions. Checking the status of a LAN connection. Configuring the synchronization of offline files. If you need to do it as a manager or support professional, there's no faster way to find out how. (Bill Camarda)
Bill Camarda is a consultant, writer, and web/multimedia content developer with nearly 20 years' experience in helping technology companies deploy and market advanced software, computing, and networking products and services. His 15 books include Special Edition Using Word 2000 and Upgrading & Fixing Networks For Dummies®, Second Edition.
The practical, portable guide to Windows® XP Professional!
Whether you support 50 desktops or 5000, this indispensable guide provides fast answers for the day-to-day administration of the Windows® XP Professional operating system. This pocket-sized resource zeroes in on essential desktop support issues and procedures—delivering critical details through quick-reference tables, step-by-step instructions, and lists. It's the precise information you need to solve problems and get the job done—whether you're at your desk or in the field!
Get fast facts to:
Loading...| Acknowledgments | ||
| Introduction | ||
| Pt. I | Microsoft Windows XP Professional Essentials | |
| 1 | Introduction to Microsoft Windows XP Professional Administration | 3 |
| 2 | Configuring the Environment | 23 |
| 3 | Configuring Hardware Devices and Drivers | 59 |
| 4 | Customizing Menus, the Windows Taskbar, and Toolbars | 85 |
| 5 | Optimizing the Desktop and Screen Appearance | 103 |
| Pt. II | Microsoft Windows XP Professional Core Administration | |
| 6 | Managing User Access and Global Settings | 129 |
| 7 | Managing Laptops and Traveling Users | 149 |
| 8 | Configuring User and Computer Policies | 165 |
| 9 | Configuring Folder Options, Offline Files, and Quotas | 191 |
| Pt. III | Microsoft Windows XP Professional Networking | |
| 10 | Managing Internet Options | 223 |
| 11 | Configuring TCP/IP Networking, Security, and Authentication | 247 |
| 12 | Managing Mobile Networking and Remote Access | 267 |
| Pt. IV | Microsoft Windows XP Professional Optimization and Recovery | |
| 13 | Optimizing Microsoft Windows XP Professional | 301 |
| 14 | Troubleshooting Microsoft Windows XP Professional | 323 |
| Index | 339 |
In this chapter, you’ll learn how to manage group policy settings. The chapter examines policies that you might want to configure in the domain and on local computers. These policies are organized by topic area, such as file and data management. Group policies apply only to systems running Microsoft Windows 2000 and Microsoft Windows XP. (In this book, "Windows XP" refers to Windows XP Professional unless otherwise indicated.) They will also apply to systems running the Windows .NET operating system.
When multiple policies are in place, they are applied in the following order:
If there are conflicts among the policy settings, settings applied later take precedence and overwrite previous policy settings. For example, OU policies take precedence over domain group policies. As you might expect, there are exceptions to the precedence rule that allow administrators to block, overview, and disable policies.
The events that take place during startup and logon are as follows:
You access and use local policies on a computer by completing the following steps:
You access and use site, domain, and OU policies by completing the following steps:
Figure 8-1. Group Policy options depend on the type of policy you’re creating and the add-ons installed. (Image Unavailable)
The exact configuration of Computer Configuration and User Configuration depends on the add-ons installed and which type of policy you’re creating. You’ll usually find that both nodes have subnodes for the following:
Figure 8-2. User and computer policies are set through administrative templates. (Image Unavailable)
Any changes you make to policies available through the administrative templates are saved in the registry. Computer configurations are saved in HKEY_LOCAL_MACHINE and user configurations are saved in HKEY_CURRENT_USER. The best way to get to know what administrative template policies are available is to browse the Administrative Templates node in the Group Policy console. As you browse the templates, you’ll find that policies are in one of three states:
You can enable, disable, and configure policies by completing the following steps:
Figure 8-3. Use the Add/Remove Templates dialog box to add more templates or remove existing ones. (Image Unavailable)
Table 8-1. Disk Quota Policies
| Policy Name | Description |
| Enable Disk Quotas | Turns disk quotas on or off for all NT file system (NTFS) volumes of the computer and prevents users from changing the setting. |
| Enforce Disk Quota Limit | Specifies whether quota limits are enforced. If quotas are enforced, users are denied disk space if they exceed the quota. This overrides settings in the Quota tab on the NTFS volume. |
| Default Quota Limit And Warning Level | Sets a default quota limit and warning level for all users. This setting overrides other settings and only affects new users. |
| Log Event When Quota Limit Exceeded | Determines whether an event is logged when users reach their limit and prevents users from changing their logging options. |
| Log Event When Quota Warning Level Exceeded | Determines whether an event is logged when users reach the warning level. |
| Apply Policy To Removable Media | Determines whether quota policies apply to NTFS volumes on removable media. If you do not enable this policy, quota limits only apply to fixed media drives. |
Whenever you work with quota limits, you’ll want to use a standard set of policies on all systems. Typically, you won’t want to enable all of the policies. Instead, selectively enable policies and then use the standard NTFS features to control quotas on various volumes. If you want to enable quota limits, use the following technique:
Group policies simplify administration by giving administrators central control over privileges, permissions, and capabilities of both users and computers. You can think of a group policy as a set of rules that helps you manage users and computers. Group policies can be applied to multiple domains, to individual domains, to subgroups within a domain, or to individual systems. Policies that apply to individual systems are referred to as local group policies and are stored on the local system only. Other group policies are linked as objects in the Active Directory service.
In this chapter, you'll learn how to manage group policy settings. The chapter examines policies that you might want to configure in the domain and on local computers. These policies are organized by topic area, such as file and data management. Group policies apply only to systems running Microsoft Windows 2000 and Microsoft Windows XP. (In this book, "Windows XP" refers to Windows XP Professional unless otherwise indicated.) They will also apply to systems running the Windows .NET operating system.
Group Policy Essentials
Careful management of policies is essential to proper operations. Policy settings are divided into two broad categories: those that apply to computers and those that apply to users. Computer policies are normally applied during system startup, and user policies are normally applied during logon.
Understanding Policy Application
During logon, policies are applied in an exact sequence, which is often important in troubleshooting system behavior.
When multiple policies are in place, they are applied in the following order:
If there are conflicts among the policy settings, settings applied later take precedence and overwrite previous policy settings. For example, OU policies take precedence over domain group policies. As you might expect, there are exceptions to the precedence rule that allow administrators to block, overview, and disable policies.
The events that take place during startup and logon are as follows:
Accessing and Using Local Group Policies
Each computer running Windows XP has one local group policy stored in its %SystemRoot%\System32\GroupPolicy folder. You shouldn't edit these folders and files directly. Instead, you should use the appropriate features of the Group Policy console.
You access and use local policies on a computer by completing the following steps:
Accessing and Using Site, Domain, and Unit Policies
Each site, domain, and OU can have one or more group policies. Group policies higher in the Group Policy list have a higher precedence than policies lower in the list. Group policies set at this level are associated with Active Directory. This ensures that site policies get applied appropriately throughout the related domains and OUs. Site, domain, and OU group policies are stored in the %SystemRoot%\Sysvol\Domain\Policies folder on domain controllers. In this folder you'll find one subfolder for each policy you've defined on the domain controller. You shouldn't edit these folders and files directly. Instead, you should use the appropriate features of the Group Policy console.
You access and use site, domain, and OU policies by completing the following steps:
Using the Group Policy Console
Once you've selected a policy for editing or created a new policy, you use the Group Policy console to work with group policies. As Figure 8-1 shows, the Group Policy console has two main nodes:
Figure 8-1. Group Policy options depend on the type of policy you're creating and the add-ons installed. (Image Unavailable)
The exact configuration of Computer Configuration and User Configuration depends on the add-ons installed and which type of policy you're creating. You'll usually find that both nodes have subnodes for the following:
Configuring Policies
When you want to manage users and computers, you'll want to configure the administrative template policies. These policies provide easy access to registry-based policy settings that control the operating system, Windows components, and programs.
Viewing Policies and Templates
As shown in Figure 8-2, you can view the currently configured templates in the Group Policy console's Administrative Templates node, which contains policies that can be configured for local systems, OUs, domains, and sites. Different sets of templates are found under Computer Configuration and User Configuration. You can add additional templates containing new policies manually in the Group Policy console and when you install new Windows components.
Figure 8-2. User and computer policies are set through administrative templates. (Image Unavailable)
Any changes you make to policies available through the administrative templates are saved in the registry. Computer configurations are saved in HKEY_LOCAL_MACHINE and user configurations are saved in HKEY_CURRENT_USER. The best way to get to know what administrative template policies are available is to browse the Administrative Templates node in the Group Policy console. As you browse the templates, you'll find that policies are in one of three states:
Enabling, Disabling, and Configuring Policies
In the Group Policy console, you'll find administrative templates in two nodes: Computer Configuration and User Configuration. In most cases, the policies in these areas don't overlap or cause conflict. If there is a conflict, however, computer policies have precedence, which means that the computer policy is the one that is enforced. You'll find details on commonly used policies and how you can employ them later in this chapter.
You can enable, disable, and configure policies by completing the following steps:
Adding or Removing Templates
You can add or remove template folders in the Group Policy console. To do this, complete the following steps:
Figure 8-3. Use the Add/Remove Templates dialog box to add more templates or remove existing ones. (Image Unavailable)
Working with File and Data Management Policies
Every system administrator should be familiar with file and data management policies, which affect the amount of data a user can store on systems, how offline files are used, and whether the System Restore feature is enabled.
Configuring Disk Quota Policies
Policies that control disk quotas are applied at the system level. You access these policies through Computer Configuration\Administrative Templates\System\Disk Quotas. The available policies are summarized in Table 8-1.
Table 8-1. Disk Quota Policies
| Policy Name | Description |
| Enable Disk Quotas | Turns disk quotas on or off for all NT file system (NTFS) volumes of the computer and prevents users from changing the setting. |
| Enforce Disk Quota Limit | Specifies whether quota limits are enforced. If quotas are enforced, users are denied disk space if they exceed the quota. This overrides settings in the Quota tab on the NTFS volume. |
| Default Quota Limit And Warning Level | Sets a default quota limit and warning level for all users. This setting overrides other settings and only affects new users. |
| Log Event When Quota Limit Exceeded | Determines whether an event is logged when users reach their limit and prevents users from changing their logging options. |
| Log Event When Quota Warning Level Exceeded | Determines whether an event is logged when users reach the warning level. |
| Apply Policy To Removable Media | Determines whether quota policies apply to NTFS volumes on removable media. If you do not enable this policy, quota limits only apply to fixed media drives. |
Whenever you work with quota limits, you'll want to use a standard set of policies on all systems. Typically, you won't want to enable all of the policies. Instead, selectively enable policies and then use the standard NTFS features to control quotas on various volumes. If you want to enable quota limits, use the following technique:
Figure 8-4. Use the Default Quota Limit And Warning Level Properties dialog box to enforce disk quotas. (Image Unavailable)
Configuring System Restore Policies
System Restore is designed to save the state of system volumes and enable users to restore a system in the event of a problem. It is a helpful feature for the average user, but it can use a tremendous amount of disk space. As you learned in Chapter 2, "Configuring the Environment," you can turn System Restore off for individual drives or for all drives on a computer.
In the Group Policy console, you'll find the System Restore policies under Computer Configuration\Administrative Templates\System\System Restore. Through System Restore policies, you can override and disable management of this feature. The following policies are available:
To configure system restore policies, follow these steps:
Configuring Offline File Policies
Offline file policies are set at both the computer and the user level, and there are identically named policies at each level. If you work with identically named policies at both levels, keep in mind that computer policies override user policies and that these policies may be applied at different times.
The primary policies you'll want to use are summarized in Table 8-2. As the table shows, most offline policies affect access, synchronization, caching, and encryption. You'll find Offline File policies under Computer Configuration\Administrative Templates\Network\Offline Files and User Configuration\Administrative Templates\Network\Offline Files.
Table 8-2. Offline File Policies
| Policy Type | Policy Name | Description |
| Computer | Allow Or Disallow Use Of The Offline Files Feature | Forces enabling or disabling of the Offline Files feature and prevents overriding by users. In this way, you can administratively control Offline File settings for a system. |
| Computer\User | Prohibit User Configuration Of Offline Files | Prevents users from enabling, dis-abling, and configuring Offline Files. This locks down the default settings for Offline Files. |
| Computer\User | Synchronize All Offline Files When Logging On | Forces full synchronization when users log on and prevents them from changing synchronization timing. |
| Computer\User | Synchronize All Offline Files Before Logging Off | Forces full synchronization before users log off and prevents them from changing synchronization timing. |
| Computer\User | Synchronize Offline Files Before Suspend | Forces synchronization before a computer goes into standby or hibernate mode. You can specify quick or full synchronization. |
| Computer | Default Cache Size | Limits size of automatically cached offline files and prevents users from changing related options. If you enable this option you can set a cache size. If you disable this option the limit is 10 percent of drive space. |
| Computer\User | Action On Server Disconnect | Specifies how the system responds when a server becomes unavailable. The Work Offline action ensures offline files are available. |
| Computer\User | Remove "Make Available Offline" | Prevents users from making files available offline. |
| Computer\User | Prevent Use Of Offline Files Folder | Prevents users from accessing the Offline Files folder. Users can't view or open copies of cached files, but they can work offline. |
| Computer | Files Not Cached | Lists types of files that cannot be used offline by file extension. |
| Computer\User | Administratively Assigned Offline Files | Specifies files and folders that are always available offline by Universal Naming Convention (UNC) path. |
| Computer | At Logoff, Delete Local Copy Of User's Offline Files | Cleans up the offline file cache on the local computer at logoff. |
| Computer\User | Event Logging Level | Ensures offline file events are logged in the application log. |
| Computer | Subfolders Always Available Offline | Makes subfolders available offline when a parent folder is available offline. |
| Computer | Encrypt The Offline Files Cache | Determines whether offline files are encrypted to improve security. |
| Computer\User | Prohibit "Make Available Offline" For These Files And Folders | Prohibits users from making specific files and folders available offline. Enter UNC paths to resources. |
Setting Offline File Configuration Policies
Offline file configuration can be easily controlled through policy. You can allow users to specify which files and folders should be available offline, prevent them from configuring offline file features on their own, and allow them to work offline but not access other cached resources. Follow these steps to set offline file configuration policies:
Administratively Controlling Offline Files and Subfolders
You can administratively control which files and folders are available for offline use. Typically, you'll want to do this on file servers or other systems sharing resources on the network. You can use several different techniques to administratively control which resources are available offline.
You can prevent users from making files available offline and assign specific offline resources by following these steps:
Figure 8-5. Use the Show Contents dialog box to specify resources according to their UNC path. (Image Unavailable)
You can make specific files automatically available and prevent others from being used offline by following these steps:
Setting Offline File Synchronization Policies
Offline file synchronization is normally controlled using the Synchronization Manager. However, you can set specific synchronization timing and techniques through policies. Normally resources are either fully synchronized, meaning that all files are checked to ensure they are complete and current, or quickly synchronized, meaning files are checked to ensure they are current, but file contents are not examined for completeness.
Several events can trigger synchronization automatically, such as logon, logoff, standby, and hibernate. Again, the Synchronization Manager normally determines which events are used. Using policies you can override this behavior. In most circumstances, you'll want to synchronize files only when a user logs on. The advantage to synchronizing when users log on is that they'll always have the freshest copies of files. The disadvantage is that the logon process may take longer. The notable exception for synchronizing at logon is for laptop users. Here, you may want to synchronize at logoff to ensure that users have the freshest copy of files when they go home and use their laptop offline.
To configure synchronization policies, follow these steps:
Setting Offline File Cache Policies
Careful configuration of the offline file cache is essential to managing the system and network overhead generated by offline file usage. You can specify a maximum file cache size, whether the cache is encrypted for security, and which file types should never be cached. To configure policies for the offline file cache, follow these steps:
Figure 8-6. Set a default cache size for offline files in the Default Cache Size Properties dialog box. (Image Unavailable)
NOTE:
If you don't configure the Default Cache Size policy or disable it, the cache size limit is 10 percent of the free space on the system drive.
Working with Access and Connectivity Policies
Access and connectivity policies control network connections, dial-up connections, and Remote Assistance configurations. These policies affect a system's connectivity to the network and connectivity to the system.
Configuring Network Policies
Many network policies are available. Network policies that control Internet Connection Sharing, Personal Firewall, and Network Bridge are configured at the computer level. Network policies that control local area network (LAN) connections, Transmission Control Protocol/Internet Protocol (TCP/IP) configuration, and remote access are configured at the user level. The primary policies that you'll want to use are summarized in Table 8-3. You'll find Network policies under Computer Configuration\Administrative Templates\Network\Network Connections and User Configuration\Administrative Templates\Network\Network Connections.
Table 8-3. Network Policies
| Policy Type | Policy Name | Description |
| Computer | Prohibit Use Of Internet Connection Sharing On Your DNS Domain Network | Determines whether administrators can enable and configure connection sharing. This policy only applies to the domain in which it is assigned. |
| Computer | Prohibit Use Of Internet Connection Firewall On Your DNS Domain Network | Determines whether users can enable the personal firewall. This policy only applies to the domain in which it is assigned. |
| Computer | Prohibit Installation And Configuration Of Network Bridge On Your DNS Domain Network | Determines whether users can install and configure network bridges. This policy only applies to the domain in which it is assigned. |
| User | Prohibit Access To Properties Of Components Of A Remote Access Connection | Determines whether users can access and change properties of remote access connections. |
| User | Prohibit TCP/IP Advanced Configuration | Determines whether users can access advanced TCP/IP settings. |
| User | Prohibit Access To Properties Of A LAN Connection | Determines whether users can change the properties of LAN connections. |
| User | Ability To Change Properties Of An All User Remote Access Connection | Determines whether users can access connection available to all users of the computer. |
| User | Prohibit Deletion Of Remote Access Connections | Determines whether users can delete remote access connections. |
| User | Ability To Delete All User Remote Access Connections | Determines whether users can delete remote access connections available to all users of the computer. |
| User | Ability To Enable/Disable A LAN Connection | Determines whether users can enable or disable LAN connections. |
As shown in the table, network policies for computers are designed to restrict actions on the organization's network. When you enforce these restrictions, users are prohibited from using features such as Internet Connection Sharing in the applicable domain. This is designed to protect the integrity of corporate networks but it doesn't prevent users with laptops, for example, from taking their computers home and using these features on their own networks. To enable or disable these restrictions, follow these steps:
User policies for network connections usually prevent access to certain configuration features, such as the advanced TCP/IP property settings. To configure these policies, follow these steps:
Configuring Remote Assistance Policies
Remote Assistance policies can be used to prevent or permit use of remote assistance on computers. Typically, when you set Remote Assistance policies, you'll want to prevent unsolicited offers for remote assistance while allowing requested offers. You can also force a specific expiration time limit for invitations through policy rather than setting this through the System utility. To configure policy in this manner, follow these steps:
Figure 8-7. Set a time expiration limit for Remote Assistance invitations. (Image Unavailable)
To prevent remote assistance and remote control of computers entirely, follow these steps:
Working with Computer and User Script Policies
Script policies control the behavior and assignment of computer and user scripts. Four types of scripts can be configured:
You can write these scripts as command-shell batch or Windows scripts. Batch scripts use the shell command language. Windows scripts use Windows Script Host (WSH) and are written in a scripting language, such as VBScript or JScript.
Controlling Script Behavior Through Policy
Through policy you can control the behavior of startup, shutdown, logon, and logoff scripts. The key policies that you'll use are described in Table 8-4. As you'll see, there are quite a few options for configuring script behavior.
Table 8-4. Computer and User Script Policies
| Policy Type | Policy Name | Description |
| Computer/User | Run Logon Scripts Synchronously | Ensures the system waits for logon scripts to finish before displaying the Windows interface. |
| Computer | Run Startup Scripts Asynchronously | Allows the system to run startup scripts simultaneously rather than one at a time. |
| Computer | Run Startup Scripts Visible | Displays startup scripts and their instructions as they execute. |
| Computer | Run Shutdown Scripts Visible | Displays shutdown scripts and their instructions as they execute. |
| Computer | Maximum Wait Time For Group Policy Scripts | Sets the maximum time to wait for scripts to finish running. The default value is 600 seconds (10 minutes). |
| User | Run Legacy Logon Scripts Hidden | Hides logon scripts configured through System Policy Editor in Windows NT 4. |
| User | Run Logon Scripts Visible | Displays logon scripts and their instructions as they execute. |
| User | Run Logoff Scripts Visible | Displays logoff scripts and their instructions as they execute. |
Although there are many ways to control script behavior and many different combinations, you'll usually want scripts to behave as follows:
To enforce this behavior, follow these steps:
Figure 8-8. Set the maximum wait time for scripts. (Image Unavailable)
Assigning Computer Startup and Shutdown Scripts
Computer startup and shutdown scripts can be assigned as part of a group policy. In this way, a computer and all its users or all computers that are members of the site, domain, or OU execute scripts automatically when they're booted or shut down.
To assign computer scripts, follow these steps:
Figure 8-9. Manage computer startup scripts using the Startup Properties dialog box. (Image Unavailable)
Assigning User Logon and Logoff Scripts
User scripts can be assigned as part of a group policy. In this way, all users who access a computer or are members of the site, domain, or OU execute scripts automatically when they log on or log off.
To assign user scripts, complete the following steps:
Figure 8-10. Manage user logon scripts using the Logon Properties dialog box. (Image Unavailable)
Working with Logon and Startup Policies
Windows XP provides a set of policies to control the logon process, some of which allow you to configure the way programs run at logon. This makes them similar to logon scripts, in that you can execute specific tasks at logon. Other policies change the view in the welcome and logon screens. The main logon and startup policies that you'll use are summarized in Table 8-5.
Table 8-5. Logon and Startup Policies
| Policy Type | Policy Name | Description |
| Computer | Don't Display The Getting Started Welcome Screen At Logon | Hides the welcome screen that is displayed when new users log on. This only applies to Windows XP and not to servers. |
| Computer | Always Use Classic Logon | This overrides the default simple logon screen and uses the logon screen from previous versions of Windows. |
| Computer/User | Run These Programs At User Logon | Sets programs that all users should run at logon. Use the full file path (unless program is in %SystemRoot%). |
| Computer/User | Do Not Process The Run-Once List | Forces the system to ignore customized run-once lists. |
| Computer/User | Do Not Process The Disable Legacy Run List | Disables running startup applications other than those set through System Policy Editor in Windows NT 4. |
Hiding the Welcome Screen
Experienced users often find the welcome screen annoying, particularly because it is displayed automatically every time they log on to a new computer. To hide the welcome screen at logon, follow these steps:
Using Classic Logon vs. Simple Logon
The simple logon window is new in Windows XP. It is the default authentication, and although that view can be useful, some users might prefer to see only the classic logon window. To use classic logon rather than simple logon, follow these steps:
Setting Policy-Based Startup Programs
Although users can configure their startup applications separately, it usually makes more sense to handle this through policy, especially in an enterprise in which the same applications should be started by groups of users. To specify programs that should start at logon, follow these steps:
Disabling Run Lists Through Policy
Using policy, you can disable legacy run lists as well as run-once lists. Legacy run lists are stored in the registry in
HKEY_LOCAL_MACHINE
\Software
\Microsoft
\Windows
\CurrentVersion
\Run
and
HKEY_CURRENT_USER
\Software
\Microsoft
\Windows
\CurrentVersion
\Run
Run-once lists can be created by administrators to specify programs that should run the next time the system starts but not on subsequent restarts. Run-once lists are stored in the registry under
HKEY_LOCAL_MACHINE
\Software
\Microsoft
\Windows
\CurrentVersion
\RunOnce
To disable run lists, follow these steps:
loading...
loading...
loading...
Terms of Use, Copyright, and Privacy Policy
© 1997-2009 Barnesandnoble.com llc