/build/static/layout/Breadcrumb_cap_w.png

SMA Version 12 to 14 upgrade

Hello, 

I just upgrade my SMA to 13.0. Can I proceed with the 13.1, 13.2, 14.0 upgrades? My devices have the version 12 Agent. Or should I distribute the 13 agent first to all my devices then proceed with the 14.0 upgrade and 14.0 agent distribution? I see the min requirement for the 14.0 agent is 12.0 so I think it'll be safe but just thought I'd ask :)

Thank you


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: Hobbsy 4 months ago
Red Belt
-1

Top Answer

I’m sure there is someone from Quest who will step in here, but I’d say do not keep updating after update on your SMA.  Allow v13 to settle, leave it over night, take a full back up and then proceed with 13.1 and 13.2.

Allow to settle again probably overnight, get a full backup and then apply v14.

With regards to the agent, v12 agent should talk to v14 so when you are on SMA v14, apply the agent update to v14 and avoid, I mean, skip v13.

That’s what I would recommend and do for any of my customers.


Comments:
  • Great advice! I did the 13.0.284 to 13.0.384 hotfix. I'm now doing the 13.1 upgrade so hopefully that is successful. If so, I'll get a backup and let it settle like you said and do the 13.2 tomorrow. - Babaganoosh 4 months ago
  • The 13.2 upgrade was a success! The 14.0 upgrade aborts due to "K1000 Server Update 14.0.334 ABORTED - Renew MySQL CA certificate - expires within 90 days". I presume I need to complete the "Post-update tasks" as per the 13.2 release notes, specifically step 3. "Enable Database Access"? Currently "Enable database access" is unchecked in my Settings > Control Panel > Security Settings. - Babaganoosh 4 months ago
    • You need to enable DB access and regen the certs from that page. - AmberSDNB 4 months ago
    • Hi, there is a KB for that.

      https://support.quest.com/kace-systems-management-appliance/kb/4248309

      and

      https://support.quest.com/kace-systems-management-appliance/kb/4371414/

      Also, you can just disable the DB access. - RandomITdude24 4 months ago
      • Everything worked swimmingly. Thank you all. - Babaganoosh 3 months ago

Don't be a Stranger!

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

Sign up! or login

Share

 
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