I have been using WPKG to force installation of Windows XP updates, and are now switching to a WSUS server. So the question for you all: Is there a way to force remove the package information from the clients without running any remove commands? Solutions I have though of and why they wont work. 1. Solution: Remove the packages from the computer profiles. Problem: I have made "remove" entries for all updates (sometime it is not good to do things the right way). If I just remove the package from the computer profile, the updates will be removed, the users annoyed by the computer beeing slow for too long and I will be hunted down. 2. Solution: Create a new revision of all packages and remove the "remove"-entries. Then after all clients have got the new revision, remove the packages from the computer profile and remove/rename the packages to force removal of the package on the client. Problem: We have a lot of users working on laptops, some are away for months (up to a year in some cases) and I have no idea when all computers have received the updated packages. (this was the first reason why I started to use WPKG to force install updates on the computers when they get back to campus. With WSUS I can force install critical updates by setting a deadline) /David |