Quantcast
Channel: Symantec Connect: Deployment and Imaging
Viewing all articles
Browse latest Browse all 622

Deployment Package Server not upgrading after 7.5 SP1 HF2 application

$
0
0
Oui, j'ai besoin d'une solution

I set up a validation environment for CMS and AMS 7.5 SP1; our production environment is 7.1 SP2 MP1. I inherited the produciton environment at a lower install base, and with very little knowledge, was assisted in upgrading to the current install a little over a year ago, by a consultant we hired. The purpose of the validation environment is for me to learn how everything works without disrupting our production, then migrate everyone over; so call it half test-lab, half validation. I also ran into some licensing issues that I finally resolved yesterday and am now running fully licensed. Unfortunatly, when I saw HF2 pop up, I installed it without reading anything. To pour more salt in the wounds, I just started turning on upgrade policies, also without reading anything, and this occurred while my CMS suite was unlicensed. Books? Reading? Order of Operations? Who needs it? Me, that's who. No, I won't do that again, but it's too late and now I need some help.

 

By the time I realized I messed up, I had several agents not upgrading correctly. On my NS Server, I had:

Deployment Package Server 7.5.3219 instead of 7.5.3251
Package Server  7.5.3153 instead of 7.5.3183

On my Site server, I had:

Altiris Client Task Server Agent 7.5.3153 instead of 7.5.3183
Deployment Package Server   7.5.3219 instead of 7.5.3251
Package Server    7.5.3153 instead of 7.5.3183

 

Once I was licensed properly, I was able to get both servers' Package Server agents and the site server Altiris Client Task Server Agent upgraded by policy. Unfortuntaly, I still seem to be stuck with the Deployment Package Server agents at their old version. For several days, the targets for "Deployment Package Server Components - Upgrade" weren't even showing any servers needing the upgrade. After I ran a repair on the install, in the SIM, the targets seem to be updating properly now. I turned the policy on/off and saved it with the new count, but it still didn't deploy, as far as I could tell. I then created a Clone of the policy and instead of running once only, I set it to run every 10 minutes; I don't have any maintenance windows configured at this time. I was able to see the policy activate and see the Software Delivery Task on both Servers for the Cloned policy, but it never seemed to update the agent. If I look in the Agent and Package Server tab, the Package is still showing a timestamp from a couple weeks ago. I also have 3 packages continually "Retrying download" so I don't know if that'e related.

 

Oh, and one final reason to hate me, my 2 servers are virtual and I didn't snapshot before the hotfix adding even more pain to my brain every time I try to fix this. I am the poster child for stupidity, please have mercy. Thanks for any help!


Viewing all articles
Browse latest Browse all 622

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>