- Open a command window (select Start > Run > cmd)
- Type netsh
- Type dhcp
- Type server \\<servername> or server <ip_address>
- You then see a command prompt that says: dhcp server>
- Type add optiondef 60 PXEClient STRING 0 comment=option added for PXE support
- Type set optionvalue 60 STRING PXEClient
- To confirm that everything has been set correctly, type show optionvalue all
To remove the configuration from the Microsoft DHCP server:
- To remove type delete optionvalue 60
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 188.8.131.52, rather than the final release of KID 184.108.40.206, 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.