2000 computers do not install packages at logon

[Guest]

We're migrating from SMS to GP for our software deployments. We have things
working pretty well (thanks to help from folks in this forum) and our XP
computers are receiving and installing all the updates.

Our 2000 computers, though, do not install our software packages during the
logon process. I activated the appmgmt.log and find no errors, but entries
like the following:

The following 5 managed applications are currently applied to this user.
...
Universal Tool from policy Package Deployment Policy with state 509 and
assign count 1.
...
Found assigned application Universal Tool from policy Package Deployment
Policy in the registry.
Found 5 applications locally that are not included in the set of
applications from the Active Directory.
...
Assigning application Universal Tool from policy Package Deployment Policy.
Calling the Windows Installer to advertise application Universal Tool from
script
C:\WINNT\System32\appmgmt\S-1-5-21-329068152-308236825-725345543-4114\{3c6f431b-f734-4b9e-80c7-076a4902c2bf}.aas with flags 24.
The assignment of application Universal Tool from policy Package Deployment
Policy succeeded.

I can't find anything that tells me what "state 509" means. Also, all these
packages are upgrades of software previously installed via SMS, but even if I
delete the old versions it still doesn't do the install. The security rights
appear to be okay as well.

Any thoughts? TIA.

Kevin

 

[Guest]

Figured it out, thought I'd share.

The trouble I was seeing is by design: 2000 puts settings into the registry
and adds Start menu links at logon, but the software actually installs at
first use.

Since all the packages I was deploying were upgrades to pre-existing
software, all of which had the same program IDs as their predecessors, every
time we ran a program Windows checked for its existence, found the old
version, and ran it.

By adding two packages to GP, one of the old version and another with the
new (set to Upgrade the old), 2000 understood the pre-existence of the
software and removed the old versions. This allowed the new version to
install at first run.

Once everyone is upgraded, we'll remove the older packages, and further
upgrades will work as expected.