Questions we think may be frequently asked for KID 1.1.
How to run KID BootSvc PXE on a DHCP server (running Microsoft DHCP)
You need to set a registry key on the repository machine in order to ignore the DHCP server check during repository creation.
\\HKLM\SOFTWARE\Kaseya\Agent\AllowPXEServer DWORD 1
BootSvc.exe acts as a PXE server (aka DHCP proxy) to boot PCs.  It uses port 67 on each IP address for this.  If port 67 is already being used by a DHCP server on the machine, then it is possible for PXE requests to be handled by port 4011, but the DHCP server needs to be configured with the VendorClassId (option #60) set to PXEClient.
The Microsoft DHCP server requires the following extra configuration in order for BootSvc to be installed alongside it on the same server.
To configure the Microsoft DHCP server:
  1. Open a command window (select Start > Run > cmd)
  2. Type netsh
  3. Type dhcp
  4. Type server \\<servername> or server <ip_address>
  5. You then see a command prompt that says: dhcp server>
  6. Type add optiondef 60 PXEClient STRING 0 comment=option added for PXE support
  7. Type set optionvalue 60 STRING PXEClient
  8. To confirm that everything has been set correctly, type show optionvalue all
Note that when a DHCP server is configured like this with the PXE server along side, no other (repository) PXE server can work in the same subnet.

To remove the configuration from the Microsoft DHCP server:
  1. To remove type delete optionvalue 60
How to clone machines with static IP addresses?
KID 1.1does not support cloning machines with static IP addresses.
Does KID provide hardware independent imaging?
Kaseya Imaging & Deployment does not currently provide a hardware independent restore.  The machines which you restore your image to, need to have similar hardware to the master machine that you take the image from.  Sysprep is run on the master machine, so the image is "generalized" but all the drivers needed for networking and mass-storage needed for the client machines need to be already installed on the master machine.  You cannot inject drivers on the repository.  (It does help though that Windows 7 is more tolerant of hardware changes than Windows XP.)  KID creates a disk clone image of the system boot disk drive using Clonezilla and Partclone to create images in a Clonezilla format.
One feature of KID is that it preserves the "identity" of clients which have been reimaged.  After they have been cloned with the image from the master machine their old computer name is restored to them and their Kaseya Agent is restored to its old identity.  This means that they can still be individually managed using Kaseya after they have been reimaged.
Repository cannot be installed on a Domain Controller (including Microsoft Small Business Server).
The KID Repository creates a user KaseyaSSPUser as a share owner, if it is hosted on a Domain Controller policies may prevent the user from being created or if it is created it will be a domain user which may then clash with the user created by a different repository. Please use a different system, ideally not a server which hosts other critical services.  Note: KID 1.1 can be hosted on a virtual machine.
How to get extra logging out of the Kaseya Boot Service.
Set the environment variable KidLogLevel to the string 'info' (or for very verbose output 'debug') and then restart the service.
To add an enviroment variable in Windows, right click on Computer, choose properties | Advanced system settings | Environment Variables | System variables New.
A very long computer name (>40 letters) or agent name causes a Boot Menu job to hang.
When the KID Boot Menu is enabled and a computer is booted and an image is selected you will be prompted for a new computer name (and optionally a new agent name).  Do not enter a name longer than 40 characters, even though this is accepted it will cause the job to hang. 
Also it is worth noting that Windows limits computer names to 15 characters, so even though you can enter a name between 15 and 40 characters, if it is a Windows computer, the name will be truncated to 15 characters. 
Customizing the CD Boot
The CD will prompt the user for the address of a repository and will then download the Boot Menu and display that.  This can be customized by editing the kid11.iso image using a ISO image editor.
1. To set the settings to the repository server
Copy the init.ini file from a repository.  You will find it in Program Files (x86)\Kaseya\<instance id>\ExtDlls\ImageDeploy\services\tftp.
Add to the end of the init.ini file:  kid_srv=<ip address of the repository>
Edit kid11.iso and save init.ini in the root of the filesystem
2. To set a custom Boot Menu
Copy the menuentries.cfg file from Program Files (x86)\Kaseya\<instance id>\ExtDlls\ImageDeploy\services\tftp\grubmenu
Edit this file (for example removing all the entries, except for the one you want.
Edit kid11.iso and save init.ini in the root of the filesystem
3. Burn your modified iso to a CD
Deploying an image of a computer with multiple agents
If you take an image of a computer with multiple agents (connected to different VSAs) and then deploy that image to a destination computer, then:
all the agents will be renamed to the name of the agent on the destination computer used for the deployment, but will connect back to the different VSAs as they did on the source computer.
This may mean that new agents will be created on the other (secondary) VSAs.

CIFS VFS: cifs_mount failed with return code = -12
mount error(12): Cannot allocate memory


You probably just need to increase the amount of memory your workstation allocates to SMB/CIFS.

Set the following registry key to ’1':

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

and set the following registry key to ’3':


Restart the “KaseyaBootService” service and its dependencies


This problem we occasionally see when the repository is running a non-server version of Windows.


Using Boot Menu gives the error "Agent could not contact server"

One possibility is that the client machine does not have a valid IP address.  KID 1.1 requires that clients can obtain IP addresses from DHCP.  If you are cloning new machines you must make sure there are enough addresses available for the new machines being added.

Object reference error when scheduling a new image

We're you part of the controlled release of 6.3? This problem can occur when you are running the final controlled release of KID, rather than the final release of KID, which confusingly has the same version number. If this is the cause, you can resolve the problem by re-running kinstall, and installing just the KID module again (even though it will say it doesn't need an update).

If you weren't part of the controlled release, just open a ticket, and we'll take a look at your server and sort out the problem.

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


Article is closed for comments.