Quantcast
Channel: Forums - Recent Threads
Viewing all 30534 articles
Browse latest View live

RE: Kaseya\Connectwise Integration broke from 9.5.0.19 installer

$
0
0

Hi Jonathan,

Thanks for the reply. In ours, after doing the entire setup (a few times no less) we are only getting the following. Also, when we try the: http://localhost/KaseyaCWWebService/ManagedIT.asmx it gives us the same "Oops" message but as you said, it's not designed to actually show anything anymore.

03:12:50: ManagedItSync - Company Name: twc

03:12:51: ManagedItSync - Attempting to determine version of Kaseya installed at: https://<MyVSA>/KaseyaCWWebService/ManagedIT.asmx

03:12:51: ManagedItSync - Could not determine version of Kaseya or server error:

System.Net.WebException: The request failed with the error message:

--

<html><head><title>Object moved</title></head><body>

<h2>Object moved to <a href="/Errors/error.html?aspxerrorpath=/KaseyaCWWebService/ManagedIT.asmx">here</a>.</h2>

</body></html>

--.

  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

  at ManagedITSync.MSPKaseyaWebService.ManagedIT.IsKaseya2008()

  at ManagedITSync.ManagementItSetupConnector.getKaseyaConnector(MgmtItSetup setup, IKaseyaWebService ws, IMspApiProxy api, ISimpleLog log)

03:12:51: ManagedItSync - It is possible that the update scheduled task on your kaseya server stopped working.


RE: Is Software Management Dead?

$
0
0

Yeah and those of us who are old to VSA were told that same thing about two years ago.

RE: Is Software Management Dead?

$
0
0

Hmm,

I have also noticed quite a few legacy modules floating about like Video Chat.

There is an annoucement webinar on the 18th April which will cover some product updates.

Fingers crossed some good news will follow.

RE: Alternative Multi-Factor Authentication for VSA access

$
0
0

Just as a heads up, I am currently using Kaseya VSA integrated with our AzureAD tenant which includes MFA. There are a couple of tricks to it, basically you have to put in some dummy data into VSA to make it think it has AuthAnvil. The same applies to BMS as well, that ultimately you have to tell it you have AuthAnvil so that it breaks authentication directly, and you must always auth to AzureAD first then you can pass through to VSA/BMS. But once you add the shortcuts to your 365 tenant, it just works. I login to my Office 365 portal, go through my 2FA/MFA check, click VSA or BMS and am passed through. If I use try accessing either BMS or VSA directly it will refuse to log me in.

So it is possible to do, and in theory should be compatible with just about any 3rd party authentication system using SAML. BUT the problem is that their support, and their documentation are heavily geared towards AuthAnvil. Which is a shame, because there are so many people out there using Office 365 or other SAML style platforms, why not document it clearly about what settings you accept? I had tickets open with their support team and they would constantly point me back to Microsoft, oh it's a Microsoft problem go talk to them. No it's a Kaseya issue, because your documentation is incomplete. I've heard rumors that there was once upon a time better documentation, but it has been removed because of AuthAnvil and the push to sell that. But who knows.

Ultimately, it's possible to do, at some point I was thinking about putting together a blog post on how to exactly get it working but just haven't had the time. If there is interest I could knock something out from my personal blog.

RE: Alternative Multi-Factor Authentication for VSA access

$
0
0

We're currently in the middle of a project rolling out an OKTA integration for SSO and MFA to all of our primary internal applications including Kaseya. Options are there.

RE: Kaseya\Connectwise Integration broke from 9.5.0.19 installer

$
0
0

Are your VSA and your Manage server on the same network?

From the perspective of the Manage server, what does the hostname that you are using in the "Management IT Solution" setup table in Manage for the VSA server? (In the "Override Webservice location box").

In my case at least I'm not using the same hostname as what we "normally" use to access the VSA in this box.  I'm also *not* using https.   Assuming they are on the same network I would try changing it to http rather than http, and try plugging in the internal IP rather than a hostname.  I'm thinking two things here.

My thoughts here are two-fold.  

1.) Like I say on ours I don't have it using https, and it works.

2.) If you are using the same hostname as your "normal" access to the VSA, and it resolves to the public IP, then the access rules only allowing access from your internal IP of your manage server may actually be blocking you.  

RE: HP Battery Recall

$
0
0

Hey Jonathan, Thanks so much for sharing your procedure! Did get a chance to update it to include the additional statement about emailing the admin?

RE: Agent GUID Sequential Numbers

$
0
0

I guess I'm curious to know why they care what the Agent GUID is?  The agent GUID is literally a unique identifier in the database for the agent, and I've never really seen a time when I would *care* what it is.


RE: Alternative Multi-Factor Authentication for VSA access

$
0
0
We currently use SAASPASS but it sounds like there are “tricks” to get this working with any 3rd party. Official documentation from Kaseya would be great so it can encourage EVERYONE to enable 2fa for everyone’s security. Alas, at this point. I’d welcome any suggestions to getting MFA setup via unofficial methods.

RE: Kaseya\Connectwise Integration broke from 9.5.0.19 installer

$
0
0

We are on the same internal network. I have it setup with the external domain name, which resolves internally due to the DNS Zone we have.

I've tried disabling HTTPS, having the URL be HTTPS / HTTP with the host name, with the IP address to the same result. On a PC that isn't allowed to access it, I do get an Access Denied instead of the "oops" page so I know at least the restrictions are working properly.

I've had ConnectWise on the system multiple times and they are scratching their heads at it as well. I sort of dislike that you can't browse to the URL any longer as it creates an issue with testing to verify the website is actually working.

Thanks for the assistance, I'll see what ConnectWise comes back with.

RE: HP Battery Recall

$
0
0

I've updated the download in the Automation exchange this morning, so as soon as it gets approved and "relisted" it should be there.   It also has the small change I made to my powershell call where I found that it was failing on about 1% of the machines I ran it on because powershell.exe was not in the "path" for the system user.   So far on it's successfully run on 187 laptops in our client-base and found 1 that actually is subject to the recall.  It still has a number of machines to run on that just haven't been online since I scheduled it.

RE: Kaseya\Connectwise Integration broke from 9.5.0.19 installer

$
0
0

The fact that your log shows it getting redirected to the error page pretty well indicates it's still getting *some* kind of error in their code the same as it does when you try to browse to it in a browser.

Out of curiosity... Where is your key.json file... In c:\program files\Connectwise, or in c:\program files\Connectwise\KaseyaCWWebService?

Also if you are "ok" with SQL.  Take a quick look at the CW manage database.  In the cwwebapp_<yourcompanyname> database, in the Mgmt_It_Setup table, there will be a record that you should relatively easily be able to identify as the one for your Kaseya server.  One of the columns will be a column named Kaseya_Key.   Check that value against the  "Key" value in the key.json file on the VSA server.  They *should* match.  You can't really do much to verify the RSA keys at this point, but that's the only other thing I can think of off the top of my head.

RE: Is Software Management Dead?

$
0
0

Do you have a link to the webinar info?

RE: Agent GUID Sequential Numbers

$
0
0
I understand, the client wants to use it as an Asset Tag

RE: Kaseya\Connectwise Integration broke from 9.5.0.19 installer

$
0
0

Also one other thing you can do to try and help debug it yourself....  In IIS on the VSA server, Browse specifically to the KaseyaCWWebService Application directory in the listing.  Click on it and then in the "Features" pane double click on .Net Error Pages in the top section.

Then Click Edit Feature Settings in the action pane (or right click and select Edit Feature settings if the action pane is turned off for some reason.)

This will bring up the Edit Error Pages Settings.  From there you can change the mode to "Off", and check the checkbox for "Allow Nested Errors".  Then try browsing to the page in your browser.  Now you'll see the *actual* underlying ASP.net errors rather than being redirected to the generic page.

Make sure to set that back to "On" once you are done with your testing.  Generally speaking when you try from a browser, you'll end up seeing something about "unauthorized" due to the fact that you aren't sending the correct auth info from the keys.  There's another way you can simulate that info as well, but we'll save that for another discussion (maybe offline).


RE: Agent GUID Sequential Numbers

$
0
0

The agent GUID on a device could change if the agent ever needs to be reinstalled either to "fix" the agent's functionality or in the event the machine is reset and programs have to be reinstalled. I would not recommend they try to use it as a static asset tag number. The would be better off using the device serial number.

RE: Agent GUID Sequential Numbers

$
0
0
The serial wouldn't be a right fit as it wouldn't be sequential. Is there any other way that I can achieve the asset tag to be automatically generated in VSA and sequentially

RE: Agent GUID Sequential Numbers

$
0
0

A lot of systems have something equivelant to an asset tag in the bios.  We have one client that uses physical Asset Tags, and we put the number of off their physical asset tag into that field in the BIOS when we load them.  Then when the system info audit runs in Kaseya it pulls that into the Chassis Asset Tag field.  Works pretty well for that purpose.

RE: HP Battery Recall

$
0
0

New version has been approved and is available on the automation exchange now.

RE: Agent GUID Sequential Numbers

$
0
0

You could always create a procedure that creates the sequential numbers for you and stores the numbers into a variable in the VSA specific to each machine .... not sure the algorithm to do this however ...

Viewing all 30534 articles
Browse latest View live


Latest Images