Installation and Setup - Recent Threads

Installation Problem

mark — Fri, 17 May 2013 23:50:46 GMT

I went through the upgrade process which reported successful. However I cant login to any part of Kaseya now, getting ODBC errors on the login page, and a number of Kaseya services wont start. Have opened a ticket, so hope its fixed today! I can roll back to a server image from yesterday if required but trying to avoid that path. Phoned NZ main number but its going straight to voicemail.

Microsoft OLE DB Provider for ODBC Drivers (0x-7ffbf1c9)

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'systemAppsParam'.

C:\KASEYA\WEBPAGES\ACCESS\../inc/spRead.inc

C:\KASEYA\WEBPAGES\ACCESS\../inc/spRead.inc, line 169

6.3 upgrade and your broken portal

Dan — Thu, 28 Feb 2013 16:54:08 GMT

I tried to enter a ticket for this, but after I typed out all my information the ticket portal would not "Save and close" or "save and new" - so I'm sort of pissed about that to start with.

The reason I wanted to enter a ticket is because we requested 6.3 upgrade over a month ago on Jan 25. It's now Feb 28 and we have had absolutely no communication from Kaseya about our request at ALL. Is it really a MONTH turn around time?? This is getting absolutely ridiculous.

Here's the reply email we received that shows Kaseya did receive our request:

From: Kaseya Product Team [mailto:kaseyanews@kaseya.com]
Sent: Friday, January 25, 2013 6:48 PM
Subject: Kaseya 6.3 Upgrade Request

Thank you for your Kaseya 6.3 Upgrade Request!

In order to provide optimum support during your upgrade process, we are managing the 6.3 download flow based on our current call volumes. As a result, current requests for the download link are being handled by Customer Service within 1-3 business days from your request. If this is an urgent request, please contact Kaseya Customer Service at (415) 694-5700 directly. If your need to upgrade is not urgent, we encourage you to set up an account on our 6.3 Preview server http://www.kaseya.com/preview (promo code: try63) and take 6.3 for a test drive to help you better prepare for your upgrade.

Thank You,

The Kaseya Product Team

The simple question is: Why has it taken a MONTH (so far) to get this upgrade, and who's ear do I need to scream into in order to get the 6.3 upgrade like.. yesterday?

System Check - SQL Service account Check Warning

John Bussey — Wed, 13 Feb 2013 19:39:32 GMT

In our upgrade of Kaseya from 6.2 to 6.3 the System Check test "SQL Service Account Check" keeps resulting in a warning.

I have looked over the help feature and have made sure all SQL services are running with the appropriate logon credentials.

I was hoping that someone could shed some more light on what might also cause this warning as I am at a bit of a loss why it continues to be there.

Linux agent install issue on CentOS6

Thewalt — Tue, 18 Dec 2012 22:26:38 GMT

I have been attempting to roll out a linux client for Cent OS. At first, I was having it complain about the /j option. I created a new installer without using /j and it ran immediately. However using -V -D and it seems to run through and not actually install anything. Here is the output:

$ sudo ./KcsSetupLinux2.sh --tmpdir=/home/Thewalt/tmp -V -D
[KcsSetup.sh][13100]: Start time: 2012/12/18 17:15:39
[KcsSetup.sh][13100]: Debug:         Using "/home/Thewalt/tmp" for storage of temporary files.
[KcsSetup.sh][13100]: Informational: KcsSetupLinux2.sh launched from: /home/Thewalt.
[KcsSetup.sh][13100]: Debug:         Using TMPDIR set to "/home/Thewalt/tmp".
$

I don't see anything that is giving me an indication what I need to look at from here.. Any ideas?

Thanks.

System Requirements - 1000-1500 agents

jesse.smith — Wed, 20 Jun 2012 20:36:16 GMT

Hello all,

We're looking at purchasing a new on-premises Kaseya server and I'm just looking for some input. The Kaseya system requirements are very poorly laid out in my opinion (3x74GB raid 5? That's soooo five years ago :P).

Questions:

1) At what point do people recommend splitting the front/back end? It seems that with the ridiculous server specs available now, this shouldn't be necessary for all but the largest deployments.

2) What kind of disk IOPS (both read/write) should we expect with 1500 or so agents? I'd like to use 10K SAS/Raid 10. Recommended spindle count?

3) What about ram?

Thanks in advance,

Jesse

Linux install problems: unable to parse embedded options

rodkey — Tue, 08 May 2012 22:15:05 GMT

Platform: openSUSE 12.1 (x86_64)

Have generated a KcsSetup.sh as per http://help.kaseya.com/WebHelp/EN/VSA/6020000/index.htm?toc.htm?6908.htm

When I run the shell script, I encounter the following output:

# bash KcsSetup.sh

Loading repository data...

Reading installed packages...

'glibc-32bit' is already installed.

No update candidate for 'glibc-32bit-2.14.1-14.27.1.x86_64'. The highest available version is already installed.

'zlib-32bit' is already installed.

No update candidate for 'zlib-32bit-1.2.5_git201105272030-20.3.1.x86_64'. The highest available version is already installed.

'glib2-32bit' not found in package names. Trying capabilities.

'libglib-2_0-0-32bit' providing 'glib2-32bit' is already installed.

Resolving package dependencies...

Nothing to do.

Fatal: Unable to parse embedded options. Unexpected argument [p "c:\Program Files\Anchor Point\Agent" /s /g=sb.westmont /c /n=1 /a=ANCPNT98017564474928

]

The options were autogenerated when creating the KcsSetup.sh. The entire options line looks like this:

/e /r /p "c:\Program Files\Anchor Point\Agent" /s /g=sb.westmont /c /n=1 /a=ANCPNT98017564474928

Changing the path to a unix-like path (e.g. /usr/share/AnchorPoint/Agent) doesn't help, although I suspect it should be done anyway.

Changing the argument flag from / to - doesn't help, e.g. "-e -r -p "/usr/share/AnchorPoint/Agent" -s -g=sb.westmont -c -n=1 -a=ANCPNT98017564474928 is also unhelpful, apparently.

Ideas?

John

Integrated Windows Authentication

Jack Dekker — Fri, 10 Feb 2012 10:22:17 GMT

Morning guys.....

I am trying to enable windows authentication in IIS 7 on our Kaseya 6.2. When i enable this and disable anonymous authentication than i get the following error/message:

Localhost access to this IIS server failed.
Several VSA services depend on localhost access. Typically localhost access can be enabled by:

1. open the IIS Enterprise manager
2. Right click the default website and select properties
3. Click the website tab
4. Verify the IP address field is set to (All Unassigned)

When i enable anonymous authentication than the message disappears. Also when windows authentication is enabled and anonymous is disabled it wont login automaticly.

Server 2008 R2 with IIS 7, and running a V5.x version > upgrade to K2 6.2

Best Practices - New PC setup

Elliot Tabush — Thu, 27 Oct 2011 14:48:52 GMT

We setup a lot of new computers for clients and i'm looking to make the process more efficient.

I would like to automate as many steps as possible. I was thinking of maybe creating the idea new computer then migrating that profile to every new computer we setup. What do you recommend?

Is it safe to restore a Kaseya 5.1 archive to an existing Kaseya 6.1 instance, prior to a 6.2 upgrade?

markchicobaby — Sat, 15 Oct 2011 06:46:53 GMT

Hi, we are upgrading our hardware and also upgrading Kaseya from 5.1 to 6.2 at the same time.

My target hardware has a working 6.1 instance on it, it has a few agents checking in, but I don't care if this database is completely deleted as the production database is on the 5.1 machine. I set up the the working 6.1 instance mainly to test the hardware and software.

There is a section in the upgrade PDF titled "Updating the Kaseya Server while Moving to New Hardware" that discusses how to upgrade from 5.1 to 6.2 when also moving to new hardware. However the document assumes that the target hardware does not already have kaseya installed. The steps are basically:

- copy some files from the old machine

- import the 5.1 database

- install a NEW kaseya 6.2 instance on the target server

What modifications to the process do I need to make, given I have a working kaseya 6.1 instance on the target hardware already?

Thank you

DMZ install or behind proxy

peteb — Wed, 12 Oct 2011 20:31:09 GMT

Are the system requirements for a 5000 agent deployment wacky?

firstcall — Thu, 15 Sep 2011 16:42:51 GMT

http://help.kaseya.com/WebHelp/EN/VSA/6020000/K2-System-Requirements62.htm

We have 3500 agents at the moment and 5000 agent licenses we would certainly like to use. We are on Kaseya 2008 at the moment and planning our K2 upgrade to new hardware. However, the system requirements below seem wacky.

The web server part makes sense to me as well as seperating the roles to 2 servers.

However, the disk side of the SQL server is throwing us when it talks about the SAN or external storage. Is it saying we need a SAN or external storage or is that in case we happen to be using that for the server storage it needs to have 1500 IOPS performance? An then on the 1500 IOPS thing, that is a lot! In a simplistic model we would need 18 15K SAS drives in RAID 0+1 to get that level of performance. For grins I got a quote from rackspace.com to host the servers and they think we need 22 15K disks to get 1500 IOPS.

Don't get me started on the T3 for bandwidth part... that is just over the top crazy. Is the person writing these requirements unaware that there are in fact modern internet connections with speeds in between a T1 and a T3?

Those of you in the same size range as us, what are you doing for disks and RAID arrays in K2?

Suggested Kaseya Server Configuration for Managing up to 5,000 Machines

Database Server

Dual processor (Intel Xeon 3 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
16 GB RAM ⁽²⁾
Database RAID: 5x73Gig 15k SAS (hardware RAID 5)
Tempdb/OS RAID: 2x73Gig 15k SAS (hardware RAID 1)
Microsoft Windows Server 2003 or 2008 EE 64 Bit
Microsoft SQL Server 2005 or 2008 Standard Edition 64 Bit, with latest service pack ⁽³⁾
1 Gbps Network Interface Card (NIC)
High IO External Storage Device or SAN recommended able to support 1500 IOPS

Application Server

Single processor (Intel Xeon 2 Ghz Quad Core, 1066 Mhz front side bus,4 MB cache)
8 GB RAM ⁽²⁾
OS: 2x146Gig 10k SAS (hardware RAID 1)
Microsoft Windows Server 2003 or 2008
1 Gbps connection between the Kaseya Server and SQL Server
1 Gbps Network Interface Card for UI and Agents
T3 connection

Change Default Website Install to seperate IIS Site

russell.lum — Mon, 12 Sep 2011 18:54:52 GMT

I am migrating to a new virtual server environment and want to have Kaseya web running in it's own IIS site outside of the default. I searched the around and could not find anything about doing this - has anyone accomplished this and are their resources you can point out so I ensure I am not missing anything?

This is Windows 2008 R2 Enterprise server.

NOT installing any form of VNC or RDP access configuration on machines -> Possible?

Justin Tison — Tue, 23 Aug 2011 21:16:38 GMT

I wanted to know if there is any configuration to NOT have VNC/KVNC install when the agent installs. I have had issues where clients have mentioned seeing the icon, and I do have a procedure to remove it, but I just wondered if there was anyway to completely skip that install when installing the agent on a target machine. I have tried using RDP/terminal services as the default selection for my agent templates, but VNC still installs. Anyone have a solution for this? Thanks in advance!

K2 will not install on a domain controller

MB_TCrank — Thu, 18 Aug 2011 15:43:33 GMT

If you get the following message during install, it's because you're running on a DC. DCPromo your server out, and you're good to go.

"ERROR: Could get name from IIS7 Users Group."

The install tries to use the SID S-1-5-32-568, which is the security group IIS_IUSRS, which doesn't exist on DCs.

Search:
Kaseya
ERROR: Could get name from IIS7 Users Group
S-1-5-32-568

Kaseya on RedHat and backup options

Matt — Sun, 26 Jun 2011 10:30:08 GMT

Hi All

2 quick questions

1. Installing Kaseya agent on redhat - I've had one of my tech's try to get a kaseya working on a redhat machine but he's been having problems. Any tips or areas he might be going wrong? See his notes below.

2. Assuming we can get kaseya working on redhat (as I believe it is listed as being supported), then what would everyone recommend to use for backups which would report back to kaseya for alerting etc, seeing that BUDR doesn't support linux?

Thanks all.

"RHEL4 x64 test server - I have spent the last 2 days working on this

I can honesty say I have been trying nearly everything under the sun to get Kaseya onto it and working

The problem is that the kaseya shell script installer for the agent needs the following

ia32libs specifically

YUM or APT if you are using a debian based distro

PERL – Easy and works fine

The script is written for versions of RHEL5 / CentOS4.x which both support the YUM package management system. Currently the system in use is the up2date system which queries RH for all install critical and non-critical security updates as well as binary packages and requires a subscription to access them.

So I thought I would attack it sideways and install yum on rhel4 which is certainly possible…. BUT

It nearly broke all the repo's for RH – I highly doubt clients would go for this

Ok so I thought what about the following

Migrate to Centos4 – Yeap this works but rebrands the entire system and causes major headaches to get RH updates and half broke up2date and some of yum stuff kept getting corrupt headers. It was pretty bad and I would not want implement this. It didn’t attempt to install the agent since it was 50/50 working

So what I have not tried

Migrate them to RHEL5/6 which would require a new subscription both of these are supported by Kaseya, RHEL4 is getting pretty long in the tooth too

Entirely possible though

I would not recommend them going over to centos5.x

Try something else besides kaseya to monitor the server?

uninstall of a module

JCR — Fri, 03 Jun 2011 20:00:49 GMT

Migrating from Labtech to Kaseya

Rizwan Shaikh — Thu, 19 May 2011 07:48:19 GMT

I have a labtech RMM environment and am moving over to Kaseya. Are there ways where the scripts can be migrated over to Kaseya or migration steps for moving from Labtech to Kaseya?

I know Labtech gives steps to move from Kaseya to Labtech.

Thanks

IIS Errors when upgrading K5 to 6.1

Boon Tee — Tue, 17 May 2011 21:53:48 GMT

I've been following the guide to upgrading K5 to 6.1. I have a Server 2003 virtual K5 with SQL 2005. I have a new Server 2008 R2 x64 Virtual Server running SQL 2008 R2 x64 to run 6.1.

The installation gets to the point of Applying VSA hotfixes, and then it crashes. The message says "An error occurred on the server when processing the URL. Please contact the system administrator. If you are the system administrator please click here to find out more about this error.

The here link doesn't give any further useful information.

Kaseya Support offered the following help:

The error that you are seeing about the URL, is a little misleading. IIS7 by default will not show full errors, so we display this default message.

There is a way to enable full errors in IIS7, this article gives details - http://blogs.iis.net/bills/archive/2006/10/19/Improving-Custom-Errors-for-IIS7-Server.aspx

With this enabled, we should be able to see exactly what is causing the error.

I had a look at this blog, but it refers to IIS7 RC1. I'd like some more detailed step by step help on how to enable this in IIS7. Thanks.

Kaseya Upgrade SQL issues

Boon Tee — Sat, 14 May 2011 04:56:27 GMT

I am running an upgrade right now from K5 to K2 6.1.

Everything appears to be workable EXCEPT this one item. On page 12 of the EN_KserverInstall61.pdf (http://help.kaseya.com/WebHelp/en/KServer-Install-Guide.asp), there is a mention of setting the database collation to SQL_Latin1_General_CP1_CI_AS. I did that in my installation of SQL Server 2008 R2 and this is what the master databases are set to.

I followed the instructions on page 38 (I am moving the installation to a new server) and restored the backup I made to the new server. The database collation for ksubscribers is set to SQL_Latin1_General_CI_AS and I cannot change it to SQL_Latin1_General_CP1_CI_AS.

I tried running the following SQL Query

ALTER DATABASE ksubscribers
COLLATE SQL_Latin1_General_CP1_CI_AS ;

And got this:
Msg 5075, Level 16, State 1, Line 1
The object 'getMultiMembership' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
Msg 5075, Level 16, State 1, Line 1
The object 'fnOSCounts' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
Msg 5075, Level 16, State 1, Line 1
The object 'fnMissingPatchCounts_NoPolicy' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
Msg 5075, Level 16, State 1, Line 1
The object 'fnMissingPatchCounts_UsePolicy' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
Msg 5075, Level 16, State 1, Line 1
The column 'machNameTab.displayName' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
Msg 5075, Level 16, State 1, Line 1
The column 'machNameTab.agentGuidStr' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
Msg 5072, Level 16, State 1, Line 1
ALTER DATABASE failed. The default collation of database 'ksubscribers' cannot be set to SQL_Latin1_General_CP1_CI_AS.

How significant is this if I carried on at this stage and installed K2 6.1 as instructed? Can it be fixed later?

Installing Kaseya on Windows 2008 Server Core

zackherman — Thu, 12 May 2011 18:39:32 GMT

We are hoping to install Kaseya on Win Server 2008 Core and I don't see any documentation on it.

We are hoping to be able to run updates on the server through Kaseya as well.

Double groups after Kaseya 2 upgrade problem

groffnetworks — Mon, 25 Apr 2011 16:20:40 GMT

We just completed our upgrade to full SQL server and cut over to Kaseya 2 at the same time. All changes took place on the same virtual server.
We noticed that each of our groups now has a duplicate with the word "root" in the machine names.
I'm assuming "machine.root.group" is the new naming convention rather than "machine.group". Only the new names containing "root" are sending alerts so I'm thinking we should remove all groups with the old naming convention. Can anyone else confirm this choice?

Could this be a sign of something more serious? Everything seems to be working as normal.
I'm just concerned that this may be causing unnecessary strain on our KServer and the database.

Thanks!

Install of Windows Agent with SystemDrive NOT C fails

Kai Osthoff — Thu, 24 Feb 2011 12:22:51 GMT

Hi!

Where can i found a installation logfile of a AGENT-Installation that fails on a client computer?

Computers aren't showing up in the console

Brandon Taylor — Thu, 24 Feb 2011 00:35:00 GMT

We've been deploying Kaseya to some of our customers, but we've run into a problem. Many of our machine aren't showing up in the management console. When we hover over the Agent on the machines, it shows that it is connected, and it shows the correct name and group. Any ideas?

Improperly installed, Can't uninstall

Brandon Taylor — Wed, 23 Feb 2011 02:48:44 GMT

When we first started deploying Kaseya it was done with an improperly built installer, as a result we have several machines that show a grey K icon in the task bar. I tried to install Kaseya again but nothing happens, it dosen't show up in Add/remove programs, and it doesn't have the files that are pointed to in the manual uninstall KB. Any ideas?

Unable to login to VSA after 6.1 upgrade

Coldfirex — Sat, 19 Feb 2011 04:12:01 GMT

Howdy,

We just upgraded from 6.0.1 to 6.1. The upgrade supposedly went fine, the VSA login page reports the new version but we are unable to login. I have already rebooted, verified the Default website is started, reapplied the schema/hotfixes, and reinstalled the db schema. I entered a support ticket but I suppose I will be waiting a while on them. Agents are checking in at least.

The page cannot be displayed

There is a problem with the page you are trying to reach and it cannot be displayed.

HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x-7ffbf1c9)
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'fvFilterView49051033'.
/home.asp, line 1476
Browser Type:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; MS-RTC LM 8)
Time:
Friday, February 18, 2011 10:11:14 PM

installing on windows 2008 Core OS

c0rs0 — Thu, 03 Feb 2011 21:44:26 GMT

We are looking at redeploying our Kaseya Server and splitting it up into a Front End / Back End setup

we are looking at using 2008 core for the front end if possable

I dont see any documentation that says "This does not work"

has anyone tired this?

How to successfully install the MAC agent ?

Omar Urena — Fri, 28 Jan 2011 04:28:16 GMT

I've been trying to install the mac agent for a few days now with no results. I have a mac OSX 10.5 with all updates. Our Kaseya and agent are both up to date.

Every time I try the installation nothing happens. I run the setup on the terminal, the process starts and finishes up without installing anything. I check the processes and nothing is running the agent never installs or comes online.

Is there any trick to successfully install the agent ?, Is this a know issue ?

Please let me know and if you need any info I will provide it.

Thanks,

Linux agent not in list of packages on KServer.

varidan — Tue, 25 Jan 2011 00:54:16 GMT

Hi,

We have recently begun managing a site with Linux servers, and we are unable to deploy the linux agent as the option is not present in the packager.

I Understand that 6.0.0.1 includes the Linux agent (correct me if I'm wrong). The KServer version we have is 6.0.9.0, although at the top of the System->Configuration page it shows 6.0.0.0 and clicking "Check for Updates" states the system is up to date.

What version are we actually running here? If it's 6.0.0.0, then how can we update it?

Thanks in advance.

Trevor.

New to the K2 playground, questions about setting up K2

John M. — Thu, 20 Jan 2011 19:42:20 GMT

We are currently running Kaseya and plan to upgrade to K2 with anew server. I want to find out how I should go forth and setting up a new server that will be running as a VM setup. I will be purchasing a server that will be speced well enough for 2500 clients. Server will be dual 2.8 Xeons with 12mb cache, 6- 600GB SAS drives, 48 GB of memory. I need suggestions on how I should setup this server with room of expanding it to have 2 more servers (VM'ed) Thank you for your input.

HTTPS and Certificates with Kaseya Server

Anonymous — Tue, 04 Dec 2007 03:56:21 GMT

Kaseya sits on top of IIS.

If you change the IIS configuration, either the port that the default website runs on or enable SSL, Kaseya will detect the change at thenext logonanda background processmake any necessary changes to Kaseya.

The agents can be told to check in to DNS name, NetBIOS name or IP address, as long as the name in the 'server address' box can be reolved by the client to the server all is well. DNS is the nicest solution as any changes to the servers IP address only result in you having to update your DNS rather than give the new address to all the agents.

The agent connects directly to the Kaseya service on the server, so changes to IIS will not affect this.

IIS is only used for us humans to access the admin console, not by the agents.

For information regarding the configuration of IIS and SSL please see http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/56bdf977-14f8-4867-9c51-34c346d48b04.mspxas a good starting point.

Microsoft has a great deal of information regarding the procedure of enabling SSL on IIS.

Kaseya does not send usernames and passwords in clear text. Encyrption of the data is performed at the client end, and the encrypted data is sent to the server, even without SSL enabled.

Legacy Forum Name: HTTPS and Certificates with Kaseya Server,
Legacy Posted By Username: jimalves

Unable to connect to database on Windows x64

Anonymous — Tue, 16 Oct 2007 05:15:00 GMT

Problem :-

After installing Kaseya server on 64 bit Windows, get message:

"Connection to the database failed.

SQL 2000 prohibits remote access to the database with Service Pack 3 installed.
Verify you have SP3 for SQL2000 installed on your server"

Cause :-

Kaseya requires IIS to be running in 32 bit mode

Solution: -

Below are the instructions to set IIS to run in 32 bit mode:

1.Click Start, click Run, type cmd, and then click OK.

2. Type the following command to enable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

3. Type the following command to install the version of ASP.NET 1.1 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

4. Make sure that the status of ASP.NET version 1.1.4322 is set to Allowed in the Web service extension list in Internet Information Services Manager.

http://support.microsoft.com/default.aspx/kb/894435

Legacy Forum Name: Unable to connect to database on Windows x64,
Legacy Posted By Username: dwalsh

Quick Start Guide

Anonymous — Fri, 06 Jul 2007 05:21:00 GMT

This document covers the initial installation and setup of your Kaseya server and how to install your first Agent.

Legacy Forum Name: Quick Start Guide,
Legacy Posted By Username: raybarber

WkzJnmygAclwZrKO

Anonymous — Tue, 30 Jan 2007 06:26:00 GMT

comment5, Http: www.google.com gwt x client ms-hms-tmobile-wow-us&source m&u http: www.dogpile.com c, 936, Internal rhyme poems examples, 0359, Senoras nalgonas cojiendo, dwrq, Finger foods black, uxrjrj, All games rpg, 96604, Cold metformin feeling, %-DD, Teenren hair games, %-), Republic occidental grand punta cana, 0880, Royal societies in uk, kihe, Baby items that start with a k, 8-(, How to type picture symbols, 8(((,

Registry keys for manual uninstall

Anonymous — Tue, 01 Aug 2006 23:32:00 GMT

If you are having trouble installing Kaseya, follow these steps to completely uninstall Kaseya, and then you can start afresh without carrying any of the last instlal setting through.

1) Open Add/Remote Programs

2) If the "Kaseya Virtual System Administrator" is present, remove it

3) If "Microsoft SQL Server Desktop Engine (KVSAMSDE)" is present, remove it

4) Verify the Kaseya directory (default is c:\Kaseya) is completely gone.

If not, delete it.

5) Verify that C: \program Files\Microsoft\ SQL Server is completely gone. If not, delete it.

6) Remove the following keys

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\KServer.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\AgentMon.Exe
HKEY_LOCAL_MACHINE\SOFTWARE\Kaseya

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\KAPFA
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\KaseyaAgent
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Kserver.exe
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\KWebExec

HKEY_CLASSES_ROOT\CLSID\{49BD2FA9-B3E2-4169-AAD7-A8326A5987E0}
HKEY_CLASSES_ROOT\CLSID\{CE5ADB7B-A671-11D5-A23A-00000ED22400}
HKEY_CLASSES_ROOT\CLSID\{D5BD4E11-C316-4009-9E52-4EAC8F3A92F3}

HKEY_CLASSES_ROOT\TypeLib\{51719146-2FFF-447E-8BF7-48B5CAE3FA4F}
HKEY_CLASSES_ROOT\TypeLib\{915735B1-E8BA-438E-B332-13FD3BA609BB}
HKEY_CLASSES_ROOT\TypeLib\{CE5ADB6C-A671-11D5-A23A-00000ED22400}

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{49BD2FA9-B3E2-4169-AAD7-A8326A5987E0}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{CE5ADB7B-A671-11D5-A23A-00000ED22400}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{D5BD4E11-C316-4009-9E52-4EAC8F3A92F3}

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{51719146-2FFF-447E-8BF7-48B5CAE3FA4F}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{915735B1-E8BA-438E-B332-13FD3BA609BB}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{CE5ADB6C-A671-11D5-A23A-00000ED22400}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5725691C-819A-4CB1-8759-547DD5AE55AE}

Legacy Forum Name: Registry keys for manual uninstall,
Legacy Posted By Username: jnuttall

Configuring Default SMTP Virtual Server with authenticated Smart host account

Anonymous — Fri, 03 Feb 2006 17:49:00 GMT

As more and more ISPs and mail service providers reject unauthenticated mail connections or unregistered mail servers, you may find that alert and ticketing emails from your Kaseya server are undelivered. These undelivered emails collect in your c:\inetpub\mailroot\badmail directory, and the most recent emails that cannot be sent are found in the c:\inetpub\mailroot\queue directory.

If you have an external email server with an account from your ISP for POP3 and SMTP, then you can use that email server as a Smart host for the Default SMTP Virtual Server. The Smarthost can be configured to use authentication, which more mail servers require now to prevent spam via anonymous mail relay.

See the attached PDF document for instructions on configuring the authentication to an email account on an external mail server which will serve as the Smart host for all outbound emails sent from your Kaseya Server.

Legacy Forum Name: Configuring Default SMTP Virtual Server with authenticated Smart host account,
Legacy Posted By Username: PWong