Managing workstations over the internet
Hello,
We have several machines that are in remote locations, we'd like to have KACE inventory these PCs but aren't really that concerned with patching, deployment or anything else. If possible I'd like to do this without creating a VPN from each site. I'm pretty sure all I need to do is set the K1000 web server name to our external web address and the domain name to the same domain. Then setup port forwarding in the router.
The problem is the internal network has a different domain name than the external site. IE. the internal domain is set to something like domain.ad.local while the external site is domain.com. According to this article all I have to do is change the internal DNS to allow both names, but I've never had to do anything like that before and I'm not sure where to start. Nor am I even sure what to search for, so far my attempts at scouring Google have been fruitless.
Thanks!
Matt
Edit: After thinking it over for a bit I'm pretty sure I figured it out. It's not allowing for multiple names like the article said but setting up a CNAME or alias in the DNS server for the KBOX that points the URL to the its FQDN. We'll find out soon enough. [:)]
We have several machines that are in remote locations, we'd like to have KACE inventory these PCs but aren't really that concerned with patching, deployment or anything else. If possible I'd like to do this without creating a VPN from each site. I'm pretty sure all I need to do is set the K1000 web server name to our external web address and the domain name to the same domain. Then setup port forwarding in the router.
The problem is the internal network has a different domain name than the external site. IE. the internal domain is set to something like domain.ad.local while the external site is domain.com. According to this article all I have to do is change the internal DNS to allow both names, but I've never had to do anything like that before and I'm not sure where to start. Nor am I even sure what to search for, so far my attempts at scouring Google have been fruitless.
Thanks!
Matt
Edit: After thinking it over for a bit I'm pretty sure I figured it out. It's not allowing for multiple names like the article said but setting up a CNAME or alias in the DNS server for the KBOX that points the URL to the its FQDN. We'll find out soon enough. [:)]
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
ahayz
12 years ago
I am having the same issue however I do have vpn to my sites. The agent just will not install.
Not sure what I am doing wrong, it stops on phase 3
Not sure what I am doing wrong, it stops on phase 3
Posted by:
nshah
12 years ago
People that we work with have set up their KBOX in two ways to address remote users.
1. Put the KBOX in the DMZ and everyone in the company resolves to a public name or IP address of the KBOX
2. Keep the KBOX internal and install the agent either manually or via script with a public name or IP address and then route it through the firewall to the KBOX internally.
Once the agent is out there with either a public DNS or IP, it's a matter of networking. As long as it resolves and routes (80 and 52230 Ports) the agents should communicate. As far as I now there isn't any FAQ or documents on the setup.
1. Put the KBOX in the DMZ and everyone in the company resolves to a public name or IP address of the KBOX
2. Keep the KBOX internal and install the agent either manually or via script with a public name or IP address and then route it through the firewall to the KBOX internally.
Once the agent is out there with either a public DNS or IP, it's a matter of networking. As long as it resolves and routes (80 and 52230 Ports) the agents should communicate. As far as I now there isn't any FAQ or documents on the setup.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
