Discussion Locked

Clients not updating

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Recently I applied some post-SR1 patches to two Office 2000 administrative installation points. Each of the install points is located at a different site. For one of the sites, when I performed a "recache and reinstall" using MS Installer, everything went well. However, at the other site, the version numbers stayed the same.

The sites each contain one domain, and two way trusts have been established. Each domain runs a couple of NT 4 server machines. The clients are a mix of Win 9x and NT.
Previously, the full SR-1 patch was applied to each installation point and all of the clients successfully updated. These new patches do seem to have applied correctly as the file dates and sizes that should update have been updated. I have tried running just a "plain" install (with no transforms etc) at the non-working site but still get the same result - the file versions are still the old versions.

6 replies

by blitzer

OK, if you have two seperate domains, and two install points, one on each domain, trust relationship between domains shouldn't be the issue, but you may want to verify these.
Assuming that the installer updage is being done when the client logsin, running off a script, compare policies on both domains, and check user rights on the domain in question, perhaps they do not have sufficient machine rights to update those files, or registry.
Also, start with a clean machine, perform a registry dump, attempt the update, then dump the registry again and compare, see if anything related to the update has been added, this could shed some light on the issue.
Wild one but its worth a try...where was the Installer package created? in the working domain or the problem domain? how did you transfer the package from one install point to the other? Try re-creating the package in the problem domain and deploy.
I always create a check registry key, or check file when deploying patches, it could be as easy as creating a file called SR-XX.TXT someplace, script it so that it checks for that file, if it exists it will ignore the update, if it doesn't it installs the update. If you need to re-apply the update, all you have to do is delete one file, re-log back in (running the script) and you've got an updated machine, something you can get the user to do over the phone.

Hope this helps in any way.

Cheers...
Daniel.

by blitzer

OK, if you have two seperate domains, and two install points, one on each domain, trust relationship between domains shouldn't be the issue, but you may want to verify these.
Assuming that the installer updage is being done when the client logsin, running off a script, compare policies on both domains, and check user rights on the domain in question, perhaps they do not have sufficient machine rights to update those files, or registry.
Also, start with a clean machine, perform a registry dump, attempt the update, then dump the registry again and compare, see if anything related to the update has been added, this could shed some light on the issue.
Wild one but its worth a try...where was the Installer package created? in the working domain or the problem domain? how did you transfer the package from one install point to the other? Try re-creating the package in the problem domain and deploy.
I always create a check registry key, or check file when deploying patches, it could be as easy as creating a file called SR-XX.TXT someplace, script it so that it checks for that file, if it exists it will ignore the update, if it doesn't it installs the update. If you need to re-apply the update, all you have to do is delete one file, re-log back in (running the script) and you've got an updated machine, something you can get the user to do over the phone.

Hope this helps in any way.

Cheers...
Daniel.

This discussion is closed to new replies.