Hey Conrad. We have figured out the issue. It turns out that the program was not getting installed during our imaging process. We have never had any issues with that process and just didn't think about the software not being installed after we imaged. We looked at a machine and found that it was not installed and then fixed the imaging task to make sure it got installed correctly. We are good to go!! Thanks so much for your help!
Hey Conrad, Thanks so much for the help. We looked at the server there is nothing on the idle tab. So I am assuming that these devices on the other networks did not check in correctly with the server. Is there a log or something on the client that we can go to that would help us find where the problem is coming from? We have some devices in hand and are at one of our other schools so we can test. Really appreciate the help, we have been very pleased to have partnered with you guys for over 8 years!
RU Server Verision 220.127.116.11 (2802) Viewer Version 18.104.22.168 Host 22.214.171.124 We are a school system and we are trying to setup the server to be able to remotely administer our machines whether they are on our network or off. We are trying to auto import all of our clients so that we have them in the addresss book with their Internet-ID. We imaged some devices here at our Central Office where the RU Server is located. We were successfully able to get machines that we imaged to import once they rebooted and checked in with the server. However, if our techs image clients on a different subnet, we are not seeing those devices auto import. We do have the server setup as a dns entry and not an IP address. Is there something we are missing in the setup that would keep this auto import from working as we hoped? Thanks so much for any help you can provide.