To you knuckleheads that jumped on board right when a new release came out
In other words, try to find a way to improve the situation instead of just bitching and doing nothing about it.
boudjOK... this is my rant (I've been with K for 3 years and have earned the right to do this):
Towards K - Guys, when will you get a major upgrade deployed without all of this grief happening? This will mark my 3rd one, and frankly they all have sucked. You need to do a better job on your product upgrades so they minimize the impact on us and our systems. In the end I was happy with K5 (my company is running well under it) so I did not need to immediately jump to the new version. But you guys officially released K2 to the public (staggered of course) so I assumed it was safe to move up to it. And yet as you can see many users are running afowl of bugs and design changes (like LC remote control not allow end users to open separate remote control windows so as to see full screen or multiple screens like you can do in K5). I mean, how many times can you shoot yourselves in the foot before you start to bleed out too much??? This test/deploy process you are using is broken, and you need to get it fixed. I can see you've done a better job of it this release, but it wasn't good enough!
To you knuckleheads that jumped on board right when a new release came out -> Hasn't Microsoft and K tought you guys anything??? Come on, how many times will it take for you guys to catch on that being an early adopter starts out being fun (look at all of the cool things I can do with the new version!), but in the end the bad out weighs the good for several weeks to several months. After going through this a few times I finally learned to setup a new server and install K2 to it and run things in parallel for a while (especially since K now allows the install of 2 agents to a machine). Once K finally gets all of my issues fixed, I'll move on over to the K2 server and decomission the K5 server. So while you're crying (boo hoo, boo hoo) remember to make sure to kick yourself in the ass for being a knucklehead and not learning from past experiences!
To all of you first timers (those of you going through this for the first time): This sucks. I'm sorry you're going through what we veterans have been through (a difficult and brusing time). However, based on my previous experience, I have justifiable faith that K will plow ahead and resolve these issues and get the product running as it needs to be. Please learn from it, and the next time K releases a major upgrade, have some patience and wait (let the knuckleheads and newbies debug it for us!). Or make sure to do a parallel install where it reduces your stress levels. In the end I feel the K product is an excellent choice to run your business with.
To you people looking to jump ship -> That is your perogative. But instead of crying wolf by "threatening" to dump K for someone else, just do it. I'm sure if enough of you had the balls to leave it would make a good impact on K, and then maybe they'd learn that they need to do a much better job on the upgrade process! However, if you do not leave, them how about you get with others who are also having issues and forming a peer/support group that helps each other out, as well as tries to use its cumulative strength to influence K in the right direction? In other words, try to find a way to improve the situation instead of just bitching and doing nothing about it.
I'm sorry you're going through what we veterans have been through (a difficult and brusing time).
No problem. Just direct me to any location where Kaseya actually allows us to interact with them. Show me where I can go to recommend that they not release hotfixes at 8:30am that cause BUDR backups to execute at the start of the work day, or how I may hint to them that allowing KES to reboot a server in the middle of the day might not be a great idea. That place doesn't exist, so all I can do is ***
boudjTo you knuckleheads that jumped on board right when a new release came out [...] remember to make sure to kick yourself in the ass for being a knucklehead and not learning from past experiences!
email@example.comSomeone mentioned a blog on migrating from K2 to Labtech. I found this blog that you may be interested in-