DHCP settings for K2000 over WAN to image laptops
Hello,
I use to have this working a while back from our regional offices, but it no longer works. We have updated K2000 recently, but it's been many months since we've tried to image a laptop over the WAN. Imaging works fine in out HQ where k2000.
I use to have this working a while back from our regional offices, but it no longer works. We have updated K2000 recently, but it's been many months since we've tried to image a laptop over the WAN. Imaging works fine in out HQ where k2000.
There is no firewall between our remote office and the K2000 and it seems to get to the screen to select the image to use then the screen goes black with many dots and after quite some time fails.
DHCP settings are:
bootfile kbox2000.0
next-server 172.29.206.15
option 66 ip 172.29.206.15
option 244 ip 172.29.206.15
Any ideas?
Thanks
1 Comment
[ + ] Show comment
Answers (3)
Please log in to answer
Posted by:
G0nz0
6 years ago
These sites have no IT support and we need to keep costs down so would like to image their laptops should they get issues.
The version is actually v.5.1.84 (my mistake), what is SDA?
Thanks
Comments:
-
System Deployments Appliance, SDA, formerly known as K2000.
RSA, Remote Site Appliance, a Replication Appliance for a main SDA, this is to avoid having computers looking for Images across cities,states or countries, the goal is to maintain Imaging inside a LAN.
Another option for you, will be to create Offline USB installers. - Channeler 6 years ago
Posted by:
rollerinvinh
6 years ago
We have also no IT support on some site but we have push some RSA (remote site appliance) on their sites
then on our central console (SDA) you can deploy with "automated deployments" -> just need MAC address of the computers you need to deploy
next boot of the computer -> the deployment will begin
Posted by:
Nico_K
6 years ago
If a RSA is not possible, you need to route DHCP, TFTP etc, which needs to be done with your routers/switches.
All nessesary ports can be found here:
https://support.quest.com/kb/129799/
But still the better idea is to setup a RSA even if you don't have local staff, because you manage it from the main SDA.
This means: You decide which machine needs to be reinstalled and it will be reinstalled but simply from the remote location.
In the boot actions of the main SDA you have the option to choose from which device (SDA or any of the RSA) the deployment needs to be done.
The RSA is a stripped down SDA which is included in the SDA license (so you can use as many RSA as you like as long the nodes together have licenses). You simply need to verify that the RSA(s) have access to the SDA
All nessesary ports can be found here:
https://support.quest.com/kb/129799/
But still the better idea is to setup a RSA even if you don't have local staff, because you manage it from the main SDA.
This means: You decide which machine needs to be reinstalled and it will be reinstalled but simply from the remote location.
In the boot actions of the main SDA you have the option to choose from which device (SDA or any of the RSA) the deployment needs to be done.
The RSA is a stripped down SDA which is included in the SDA license (so you can use as many RSA as you like as long the nodes together have licenses). You simply need to verify that the RSA(s) have access to the SDA
Also Kbox.2000.0 is deprecated since version 4.0
https://support.quest.com/kace-systems-deployment-appliance/kb/217556/dhcp-configuration-for-bios-and-uefi-pxe - Channeler 6 years ago