/build/static/layout/Breadcrumb_cap_w.png

Warning about upgrading to KACE SDA version 9.0.144

Warning: The size of the driver feed in KACE SDA version 9.0.144 has increased dramatically over the previous version. Upgrading may crush both your system and your network!

We just upgraded to KACE SDA 9.0.144 on 1 SDA and 12 RSA's dispersed all across the US with a few in Canada. One of the features touted in the new version was an expanded Driver Feed which included support for HP and Lenovo. We don’t have any devices of either brand in our fleet. We started using KACE when it was still a Dell product and it’s worked well for us. I upgraded the SDA and all RSA’s over about a 4 hour period on a Saturday. As soon as all the upgrades were complete I saw that the system was recaching drivers. On Monday morning when I first tried to test the upgraded system I found that my existing image (Win10 21H2 captured on SDA 8.2) was failing on the Copy Drivers task, which was the twelfth step in the process. While investigating this issue I found that the driver recache was still ongoing and that the RSA’s were attempting to sync over 70 GB of data. I looked at the new Driver Feed and found that with the Lenovo and HP drivers included it had swelled from 8 pages of drivers to 39, nearly a five-fold increase in size! This huge increase has absolutely crushed the system. I can’t even get a new KBE to upload to the SDA because of all the data it’s trying to move 5 days later!

Why didn’t Quest split the Driver Feed up into three different ones, Dell, HP, and Lenovo? That way we could take what we need and expand to other vendors as needed. As things stand now I have a gigantic mess on my hands as the SDA is crippled and anything I do only makes things worse as it adds to the backlog of work the system needs to get through. Quest support suggested I unlink the problem RSA’s (like there are any RSA’s that aren’t a problem) and link them up again and sync. Won’t that just make more work for an already overloaded system? If I can’t even get a KBE to upload how will an RSA be able to link to the SDA?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 1 month ago
Red Belt
0

I am not sure what happened, but this is not the normal experience.
My SDA has still less than 40GB in size (incl the backend OS), esp since only the diver feeds are downloaded which are needed.
And after the update the SDA always replicates the updated tasks, images and SI.

Can you give the case number please?

Posted by: Crossover 1 month ago
Senior White Belt
0

The case number is 01831036. I have unlinked and relinked one of the RSA's and it had no effect on the issue. Most recent round of syncs are moving 47GB of data across the WAN. The driver recache that began on Saturday the 20th finally completed on Thursday the 25th. One of the KBEs that we tried to upload appeared on the SDA right after that, so I guess there has been some progress.

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