Deploying XP SP3 on user machines

We have recently purchased the KBOX 1100 and Im currently using it to deploy XP SP3 to user machines. In the main the upgrades have worked but Ive hit a few machines where the user has been asked to reboot and it looks like the upgrade has worked ok but on close inspection i see the error "error in patch deploy script" ..FAIL (80) in the Deploy status. Im looking for suggestions/ideas why this might be happening as I have a lot more machines to patch.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: GillySpy 12 years ago
7th Degree Black Belt
You could follow this to get some clues, but I would open a ticket http://www.kace.com/support/kb/index.php?action=artikel&cat=6&id=1045&artlang=en
Posted by: cblake 12 years ago
Red Belt
If you're just trying to upgrade all machines to SP3, you might consider making it a managed install. Then there's no need to subscribe to the SP2 feed, That takes up a lot less space on the K1000, and it's less stuff for you to manage. Just download the installer from Microsoft & treat it like a normal software installer. This also gives you the flexibility to notify users before install and define things like only running while logged off. Food for thought.
Posted by: Llee 12 years ago
Senior Yellow Belt
I seen this before and one thing to check out is that permission on writing to the registry, here is an FAQ to check out: that is for Xp Service Pack 2 and maybe related.

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ