We use Prism Deploy to create pwc packages which we in turn create msi packages for deployment via Active Directory and Group Policy.

We are using Windows 2000 server and workstations.

When I assign one of these msi packages as a "computer based policy" the software installs correctly but it is not advertised - it is completely installed for the client. This is in most cases perfectly okay. This is what we want.

However, when I assign one of these msi packages as a "user-based policy" - note I am not publishing I am using "advanced assignment" in Active Directory and Group Policy, the software is not assigned. I do not see it appearing on the Programs menu after the user signs on. They have to go to the Add / Remove Programs applet and click on the Add New Programs button to see software waiting to install - much like I would if I told the system to use "publish" the msi.

My question, can Prism Deploy msi packages be "advertised". If so, what steps am I missing to make it happen.

I want our user based policy msi packages to deploy for the client without them having to go to the Add / Remove Programs applet. This is an extra step that want to avoid.

Thanks for any insight into this one!

John Falloon

We've done some testing with both a Prism-created MSI and one directly from Microsoft (orca.msi). Both of them behave the same way: on Windows XP, a user-based policy assignment that is configured to run at logon installs successfully without having to go to Add/Remove Programs.

On Windows 2000, however, it does not – the user has to go to Add/Remove Programs to install the software.

Given the differing results between the two operating systems, and given that non-Prism MSIs behave this way, we'd have to conclude this is either as designed by Microsoft for the Windows 2000 platform, or else it’s a Microsoft bug.

Do any MSI gurus out there have additional insights?

This script solves this problem. It however runs for every logon.

http://www.moskowitz-inc.com/grouppolicy/scriptingdownloads.html

John Falloon