The information in this article applies to:
SYMPTOMSWhen an administrator publishes an upgrade to an existing program, if a user using the upgraded package double-clicks a file associated with a feature not currently installed on the local computer, the feature may be installed from the original program and not from the intended upgraded program. CAUSEThis behavior can occur if the administrator has an existing published program (base program) managed in a Group Policy Object (GPO). A new program is then published that upgrades the base program. A user then installs the upgraded program, but does not install all of the features. When the user double-clicks a document associated with one of the features, the original base program feature is installed rather than the upgraded feature. RESOLUTIONTo avoid this behavior when you publish an upgrade program, click to clear the Auto-Assign check box box for the original program in the GPO. Check to make sure the Auto-Assign check box is selected for the upgrade program. Additional query words: active directory
Keywords : kbenv |
Last Reviewed: December 30, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |