FAQs

Q. Does it work on DSL?

A. Yes. Any avenue of connection that allows TCP/IP can be used. The type of media being used in communicating with RemoteScope's Clients is not limited. It is the performance of certain RemoteScope functions that is proportionally affected by the speed of the connection.

Q: Can I use it over a WAN?

A: Yes. It's TCP/IP–based and can be used over a LAN, WAN, dial-up or any other way you can access a Client system with TCP/IP.

Q: Will it work with wireless?

A: Yes (see previous answer).

Q: Will it work through a firewall (or VPN)?

A: Yes. A port needs to be opened through the firewall of course, and that can be specified in the Client configuration.

Q: Can the Client modules be installed remotely?

A: Yes, there is a wizard that can be used to remotely install the Client to systems running Windows XP or 2000.  For security reasons Windows 95 and 98 systems must have the Client installed locally, but it's a simple one-click install that your users can do for you after you've made the Client Set-up file available to them by e-mail or sharing it over the network.

Q: Can the user at the Client end turn it off (or uninstall it)?

A: No. It runs in the background on the Client end and can't be closed or uninstalled from there without the administrator's password.

Q: How can it work with dynamic addressing?

A: The Client can be addressed by computer name rather than a static IP address, and the DHCP server on the remote end will resolve it to the Client's current IP address.

Q: How is it licensed?

A: By the number of seats (Client PCs). The price starts at $xx per seat in small volume and comes down as the size of the network goes up.

Q: How about updates?

A: Our Micro-Scope product has been around for many years, and is continually updated for a nominal fee to existing users. We expect that RemoteScope will be managed the same way.

Q: How large a network can it manage?

A: RemoteScope is being used in installations with many thousands of PCs, and the upper limit, if there is one, has not been reached.  As a practical matter, it is generally easier to manage the network in groups of no more than a few hundred sytems, with a Console for each group.

Q: I've heard the inventory isn't collected in real-time. Is this true?

A: The inventory database is maintained on the Console, but can be refreshed at any time. This provides instant access to the data and also cuts down on network traffic because all of the inventory data doesn't have to be sent every time you want to look at it. Another benefit of this approach is that if the Client has a hardware failure that prevents it from communicating over the network, you don't have to make one trip to find out what was on it and a second trip with the right part. And if the Client has a hard drive crash or an application gets accidentally deleted, you still have a complete record of the software including version numbers.

Q: Can the user install hardware or software without me knowing it?

A: The inventory information is collected right from the registry on their machine, so if their operating system knows it's there, so will you.

Q: Can I use it on Linux (MAC, Novell, etc.)?

A: Currently it is only for Windows systems: 95 or NT and above. It can be used in a mixed environment, but only the Windows machines can be remotely controlled.

Q: Does the Console module have to go on the server?

A: No. You can put it on the desktop in your office, or wherever it is most convenient for you to manage the network.

 Request more info