Kace SMA 7.2 experience?
Can you please share your experience with K1000 ver 7.2? I am running a stable 6.4 SP3 and did not upgrade due to all the issues folks have had with both 7.0 and 7.1.
Support will be forcing everyone to upgrade in November due to the name changes, they will not support any appliance with Dell logo.
3 Comments
[ + ] Show comments
-
Can you elaborate more on forcing users to upgrade in November? I, like you, am on 6.4 and not going anywhere until Quest proves the 7.x platform is stable. - rockhead44 7 years ago
-
Per support, come November if your Kace appliance has a Dell logo they will not be able to support it. I guess we can stay on 6.4 as long as we do not need to call support. - bozadmin 7 years ago
-
I was hoping we would get some feedback on your question. I will pose the same question later this week if you don't get anything so that it cycles back to the top of the page. - rockhead44 7 years ago
Answers (6)
Please log in to answer
Posted by:
Ted S
7 years ago
I would love to know this answer as well, I am in the EXACT same boat as you. Still running 6.4 and have to upgrade to 7.2 and am terrified of wrecking my scripts, inventory and everything else.
Posted by:
Ted S
7 years ago
I would love to know this answer as well, I am in the EXACT same boat as you. Still running 6.4 and have to upgrade to 7.2 and am terrified of wrecking my scripts, inventory and everything else.
Posted by:
rockhead44
7 years ago
Not a good report here. 8.0 coming soon
http://www.itninja.com/question/kace-agent-causing-machine-reboot
Posted by:
krk310
7 years ago
We were on 6.4 and I upgraded to 7.2.101 (including the agents to 7.2.10) a few weeks ago. We previously had an issue with servers suddenly rebooted when we upgraded to 6.4. I temporarily disabled all my patching schedules until the updates were complete. Once I re-enabled the patch schedules, they went off without a hitch. I had no server reboots. Not saying you have to do this. i did it as a precaution because of a previous experience. Since the upgrade, I've only had the issue of detections and deployments taking some extra time more so than they did before the upgrade. All scripts seem to be intact, as well as reports. I haven't implemented the Service Desk yet. It's on my 'todo' list. So no comments on that one. On the whole, it's doing OK, so far.
Comments:
-
Did you have to manually upgrade the agents on machines? - sam240 6 years ago
Posted by:
LHYardi
7 years ago
We were on 6.4 and upgraded to 7.0 and then 7.1 (with agents) over a weekend. Things seemed to be OK but then a few days after the upgrade, the agents would stop updating inventory every once in a while. While they were not updating inventory, they were also not completing 'run now' scripts - sometimes they would stop updating for over an hour before coming back to life. Very frustrating for us as we push a lot of run now scripts. Quest support couldn't tell me why they would stop updating. They told me to upgrade to 7.2 (with agents) but it still took a couple of weeks for this pattern to stop. I actually let them close the ticket this morning because it seems things are back to normal.
Going from 6.4 to 7.0 broke a few of my Access queries because they changed the 'Location' field in the User record (I had been using LDAP to populate this field) to a pointer to a Location field in the Asset record.
Comments:
-
Did you have to manually upgrade the agents on machines or did this happen automatically once you updated the agent version on the server? - sam240 6 years ago
Posted by:
scarpent
7 years ago
Had to upgrade some reports due to field changes but nothing else major other than an asset table error which they were quick to fix.
Our agents seem to be communicating a lot better and not dropping off as much as they were in the past so patching especially laptops has been a better experience also.
I have offered to me a Beta for 8.0 so we will see how this goes. Did a Beta in the past and when there was a problem it was looked into as soon as it was reported.
Hoping that they start looking at user voice requests and doing more upgrades or changes in the future instead of just one a year.
