SMS: How to Use System Policies with Program Group ControlLast reviewed: October 27, 1997Article ID: Q173793 |
The information in this article applies to:
SYMPTOMSWhen using system policies with client computers running Windows 95 or Windows NT 4.0, defining a "Custom Programs Folder" may keep Program Group Control (PGC) from successfully configuring a user's desktop with the program group(s) and shared application(s) that they would normally receive. The information in this article may also be useful to anyone that is implementing features associated with the Zero Administration for Windows (ZAW) Initiative.
CAUSEWhen the System Policy Editor is used to define a common Programs folder for multiple users, those users will often not have the necessary permissions to modify this directory structure. Because PGC runs under the context of the user, it may fail to configure the program groups. Given the proper permissions, PGC will successfully configure the Programs folder even if it is located on a server.
WORKAROUNDTo deliver a custom desktop through system policies and also use PGC, use the Custom Start Menu option instead of the Custom Programs Folder. NOTE: When using the Custom Start Menu, the Hide Start Menu Subfolders option must be disabled. Otherwise, the custom group under the Start button will not appear. To use the Custom Start Menu option, perform the following steps:
This configuration allows an administrator to use system policies to deliver custom desktop applications to their users while maintaining a local Programs folder that PGC can modify successfully.
|
Additional query words: prodsms appctl32 appctl95 win95 winnt zak
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |