/build/static/layout/Breadcrumb_cap_w.png

Am I the only one with patching issues?

After upgrading to vs 13 I just ran a test patch of some servers.  4 out of 7 showed  "reboot pending" in the morning.  This patch is a detect and deploy.  In my experience it is the only way to get all patches done where there is a dependency which is almost every month.   

KONEA service is either not starting or starting very delayed which is causing this.. if it eventually starts on its own the status turns to "suspended". This is because I set a time limit on the patch.  If I didnt do that and the konea service finally started on its own the servers would be restarting during critical business hours.  

I should note: ampwatchdog service seems to be starting.


Ive opened a ticket for this before and was told I needed to rebuild all of our servers.  After the 13 upgrade it is now worse so I opened a ticket.

Is no one else seeing this madness?  Do I really need to rebuild 80+ servers so kace will work?  In which "kace" will will likely move to another product.  




0 Comments   [ + ] Show comments

Answers (1)

Posted by: Hobbsy 1 year ago
Red Belt
0

See what support say, I'm not convinced that v13 isn't living up to it's name, if you catch my drift ;o)



Comments:
  • We went from 12 to 13... normally means a major update.. Im not seeing it. All that aside, I will let you know. - barchetta 1 year ago
 
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