Re: 6.3 release date

Comforting to hear there is some testing & retesting before things go into production. Unlike the old says of "We'll fix it later". Better to wait for the release than helter skelter.

We have an Alpha copy for testing our module on.

6.3 does look good so far. there a a few things that need to get sorted but it's an Alpha so thats ok. Im actually looking forward to it's release

Can anyone give a status on 6.3?

When it's ready, it will be released. Three weeks ago (per Mike earlier in this thread) it went out to the first round of controlled release, which means it will probably be another month or more before it's ready for general availability.

I don't understand what folks hope to accomplish by posting the same question to the forums, day after day (not implying that it's all you, @etabush.) Do you think it will make the testing go faster? ... "Are we there yet? Are we there yet?"

Would you rather have potentially unstable software? Get in the test pilot program. (Which specifically restricts people from posting info about unreleased software to these forums.)

The 3 GOLDEN RULEs - TEST , TEST, and RETEST before release. Otherwise, the forums fill up with complaints, tech support gets bombed, and no one is happy. If you ever coded, you understand, its not not fixing the fan belt. Takes time and a pair of blinders to focus on code & logic, let alone the typos.

TEST TEST AND RETEST IS THE BEST !!!

Kaseya, How far we are away from 6.3?

Is it being sent to Test Pilots? I didn't get it yet, please send if already being sent. I would like to deploy it.

The Pre-Release Announcement is showing a release date in Q1 2013:

As a Test Pilot, I haven't yet gotten my hands on it, but even if I had managed to load 6.3, the Test Pilot NDA prohibits me from talking about it 

Seriously? Q1 2013? What happened to end of June release date that was talked about at Kaseya Connect?

We have put months of delevopment 'on hold' because 6.3 was going to be released soon, but month after month it is just being pushed back?

One hour ago at the Achab Open Forum (italy) Matthé Smit (Technical Director from Kaseya) said the relase date is january 2013

If reporting is once again functional as well as KES integration with KPM, I will be happy.

Wow - Q1 2013!  K6.4 was suspossed to be released in Q4 2012, so I can't imagine how long it will be till we get that!  While the reporting stuff is nice in 6.3, what I really want is a decent remote control package because VNC is horrible and slow, which is both frustrating and costs us money.  6.4 is supposed to have the new remote control.  

Eddy - That's precisely my concern. I've been dying for the "new remote control" that's been talked about for a couple of years now. Just when I thought we were getting close (it being on display at Kaseya Connect) and them talking about end of year for 6.4 and end of summer for 6.3 I guess I just started getting excited.

If 6.3 is released in January, with Kaseya Connect 2012 being just a few months off I imagine they'll use that to promote all the cool new stuff, say end of summer (again) and maybe we'll get it Jan 14!

I received an e-mail today (in Dutch) where it says 6.3 is expected early Q1 2013.

I didn't want to translate to Enlish myself, so here's Google translate for you (which seems to make sense for once).

Kaseya version 6.3 (expected in early Q1 2013) represents a leap forward in terms of performance, ease of use, and functionality. It also shows the Kaseya's commitment to developing advanced IT management products for everyone.

...2013? Seriously?

We've put many projects on hold based on the expectation from the announcements at Kaseya Connect (back in, what, Q2 2012?) that it would be out Any Time Now. At this rate it'll be coming out just in time for the NEXT Connect conference.

Gah. Well, I guess we'll just keep putting those projects on hold, won't we.

@GreyDuck

That's why you need those projects in service desk. You can then have an SD procedure.

IF $pigs$ Does not Contain "Flying"  Set ProjectStatus to "Hold" ELSE Set ProjectStatus to "Ohwedidntthinkthiswouldeverhappen".

6.3 .. maybe just a decent remote control. Every time I have to use LMI I am reminded of the crap I was fed 3 or so years ago. Slow remote = lost $$ by every tech every day

We are in the same boat. We had expectations set that 6.3 would be released at least by the end of fall. It would be one thing if there were serious flaws with these releases hence why they are set back however the past couple releases that came out had some serious bugs that were eventually fixed by patches. Kaseya needs to get on the ball. Don't set client expectations if you cannot hold true to them.

anyone else think discovery looks alot like spiceworks :O0

Realistically we can't really wait for copy and paste functionality and the ability to use tab in my remote control solutions until 2014, we are back to considering our options. I can't put into words how frustrated I feel. At the end of the day I understand Kaseya want this product right, but should it really take this long to get it "right"? Was it so bad in the first place, and if so, why the premium price...

Just to add to that. Tab functionality use to work then one day it just stopped. I contacted support they they told me it will be added as a feature request. What!!! We just had that feature and they can't figure out how to put it back.

Yep we have had instances of this just recently too with another KLC issue. Previously you could connect to a terminal server with KLC if the RDP port was other than 3389, now you can't and it's an enhancement request. Means we now remote control with two tools, which sucks

Wow. We left Kaseya about a year ago and moved to n-able. The only reason I am back here was to try and download the mac uninstall script, but Kaseya have password protected it!

So glad we left. I was running 6.2 about a year ago (awful bloated software it was)! I seriously thought 6.4 or 6.5 would be out. Since moving to n-able we've had a major release every couple of months, ESXi monitoring is awesome and the web interface is nice and consistent.

I don't regret leaving!

2013 Q1 is getting close.

Anyone from Kaseya want to comment if your still on track for 6.3 release.

Just our 2 cents ... we are a small shop and tied to Kaseya, we just struggle to make monthly maintenance payments lately and Kaseya is really getting to be out of our reach as well, and then they put off all the stuff further and further until it's no longer viable ... Kaseya used to be cutting edge and we'd deal with issues, why? because that's what we do everyday as techs, we fix problems so we're used to finding workarounds, etc ... as much as we want to b*tch that something is done right when it comes out, we still want it to come out ... even if it has bugs ... if it came out and it didn;t have bugs for us to find, we'd go nuts looking for them anyways .... just realease the damn thing before everyone jumps ship and goes to inferior products because they can release products on time with promised features ... and yes the NEW remote control was promised way back when 4.5 was still around, and since then all we've gotten is newer versions of VNC wrapped into the systemn ....

Tom, I hate to say this... But there are other options to Kaseya. Like N-able.

Kaseya isn't the best - but it works.

We used to call N-Able...disable..

Must have changed alot in the last few years...

N-Able was a nightmare, for the record.  Not only did they install the latest .NET binaries, but they also installed IIS Express, telnet server -and- UltraVNC on every single test machine with their Agent, at which point (when we were good an angry about this) their crack sales team stopped returning e-mails and phone calls FOR THREE MONTHS!

Their uninstaller didn't clean up after itself either... I had to build a supplemental Kaseya script that went back in to remove IIS express and UltraVNC, disable the telnet server, and nuke the corresponding %PROGRAMFILES% folders and registry entries.  In short, the N-Able experience was absolutely infuriating.  Only after I'd removed every last stinking piece of their software and powered down their server VM did they (again, THREE MONTHS later) fire back a cheerfully-worded e-mail saying, "I wanted to find out if we can arrange a meeting with everyone to see if we can get things back up and running..."

They had the gall to call our Engineering Director last month and say, "Your CEO, _____________, asked us to ask you to re-evaluate our product now that we've released N-Central ____."  Our CEO said no such thing.

Different strokes for different folks, but I'd seriously caution anyone looking to go the N-Disable route.

Any Idea how i can get on the test pilot program for 6.3, we have multiple Windows 8 machines and need to be able to use Kaseya from these machines as well as administrate them.

I would have to agree.

We recently checked it out .. IIS and the other junk installed is a no go.

Labtech on the other hand looks and works great. Not having to deal with Web browser interface and the benefits of a "real" interface are a major plus

I would agree, that heavy of an agent is a no go....

For me, I think 6.3 is goning to determine if I stay or go...our maintenance levels next year are gonig to be pretty hefty so its worth the look around....

Having a standalone application would be great. Feel like i'm dealing with browser plugin issues/complaints every day.

FYI - I have been in the controlled release program for K6.3 and using it for the past month or so and find it a good upgrade. It seems to be working fine for me. My first direct comment will be it seems to be a mojor tweak of K6.2... In other words, it seems to fix all of the little quirks in K6.2. Also, I do like the new Discovery module.  

@Dsinton - If you would like to be on 6.3 we can help you upgrade. Just submit a support ticket with the following subject: CRK263 - Win8/server2012 support

Yep, we have had enough on many levels and are looking at all other options .

We have been with kasaya since 2008 .. wont be  in 2013.

Realyl wish I could submit a support Ticket by email like we do with all OUR clients.

Imagine the feedback we'd get if we had to require our clients to login to a portal to actual submit a ticket...I'd find myself without clients pretty quick (or else my helpdesk guys turning into receptionists).