Follow

How do I white label the Kaseya software so that my customers are not aware that I am using Kaseya to provide services to them?

KB#:  KKB000625

QUESTION

How do I white label the Kaseya software so that my customers are not aware that I am using Kaseya to provide services to them?

ANSWER

· The following steps are required to completely white label the Kaseya software:

1. Under the System tab > ServerManagement > Customize, modify CSS styling of the Kaseya interface, and the agent icon for both Windows and Mac deployment packages

2. Change the installation location byuse the /p switch to specify a different install path when you create a package

3. Customize the web interface logo

4. Schedule the remaining actions against one or more template accounts, which you specify to copy agent settings from when you create a package. These actions will be applied against the agent when the agent first checks in. The actions are:
a. Remove the Kaseya menu from the Start menu, Programs folder.
b. Rename the Kaseya Agent service and change the description.
c.Configure the Agent Menu for the template to use your own website details.

MORE INFORMATION

It is not possible to completely white label all parts of the product, but the above steps provide for all components where white labeling is currently supported. The exceptions are:

1. Although a standard user will never see this, any admin user will see 'Poweredby Kaseya-Copyright ?? 2000-2008Kaseya. All rights reserved.' at the bottom of each web page on the VSA web console. This notice is required for copyright purposes and will not be removed.

2. The Kaseya Security Service also does not support white labeling at this stage.

3. The look and feel of the product cannot be completely hidden through CSS styling, and anyone familiar with the Kaseya product may recognize another Kaseya web console, or output such as reporting.

4. The agent and server configuration files and executables will include the string Kaseya, and should not be modified to try to eliminate this, as this will cause system instability and crashes.

5. If an agent fails to check in when it is first deployed, the configuration changes that require an agent check in will not be successfully copied down, and therefore part of the white labeling will fail.

APPLIES TO

System tab
Agent tab
Script tab
Sample Scripts

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.