| Frequently Asked
Questions |
Q: I have a small office
with only a few computers. Do you offer anything for a small business?
Q. Does it work on DSL?
Q: Can I use it over a WAN?
Q: Will it work with wireless?
Q: Will it work through a firewall (or VPN)?
Q: Can the Client modules be installed remotely?
Q: Can the user at the Client end turn it off (or uninstall it)?
Q: How can it work with dynamic addressing?
Q: How is it licensed?
Q: How about updates?
Q: How large a network can it manage?
Q: I've heard the inventory isn't collected in real-time. Is this
true?
Q: Can the user install hardware or software without me knowing it?
Q: Can I use it on Linux (MAC, Novell, etc.)?
Q: Does the Console module have to go on the server?
Q: I have installed Firewall software on my clients, which ports
should I open for RemoteScope console to communicate with the clients?
Q: What are RemoteScope's background running processes on the console
computer and client computer?
Q: How can I remotely uninstall client programs?
Q: How can I customize the client program installation? For example,
I want to set my client programs to have different default usernames and
passwords during the client auto deployment.
Q: How can I backup and restore my configuration in RemoteScope? (I
know the current version can backup Access database. How about the SQL
database?)
Q: What is the connection limit of the screen broadcast? How many
clients can a console broadcast without problem?
Q: What is the maximum file size that RemoteScope can backup?
Q: I opened the necessary port in Windows Firewall but still cannot
connect with the clients I deployed. What can block the connection
between my console and clients?
Q: How do I change the default ports used by RemoteScope?
Remote-Scope common questions
Q: I have a small office with only a few computers. Do you offer
anything for a small business?
A: Yes. We have an affordable package that is designed just for a
small business or even a home office application. Please see our
SOHO (Small Office
Home Office) edition
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).
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 systems, 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.
Q: I have installed Firewall software on my clients, which ports
should I open for RemoteScope console to communicate with the clients?
A:
The ports used by RemoteScope client are:
TCP: 8169, the service port for searching client
TCP: The default port is 15168, which can also be configured by user.
Q: What are RemoteScope's background running processes on the console
computer and client computer?
A:
The background processes are:
Console:
Console.exe (Console program)
EAMngr.exe (Program of Enterprise Asset Manager)
ProductEdit.exe (Configuring tool for software distribution)
OSI.exe (OSI program)
RSDB.EXE (Database maintenance utility program)
ActivationWizard.exe (Activation program)
Client:
Client.exe (Client program)
RSPumper.exe (Service to startup Client)
RSWallpaper.exe (Wallpaper program)
RunProcess.exe (Program used to completely uninstall the drive)
UninstallClient.exe (Client uninstall program)
VCREDIST.EXE (The program used to pack the system when installing the
Client)
DDIHOOKA.EXE (The program used in Win98
Q: How can I remotely uninstall client programs?
A:
You may use the uninstall script to remotely uninstall the clients.
a: Defining the uninstall script:
Right click on any part of script list to view and select 'New Script'
from the context menu, the Script Editor window will appear.
Double-click “UninstallAs,” and then edit the function by entering the
username and password of the client machine in the right view
Click 'save' button after editing and then type in the saving path
and the name to complete the definition.
b: Run the uninstall script:
Right click the uninstall script you defined in the list view and select
'Run' from the context menu, the Run script window will pop up. Please
select the clients you want from the list and then click 'OK' to run the
script on them.
The uninstall process will complete after the reboot of the client
machine.
Q: How can I customize the client program installation? For example,
I want to set my client programs to have different default usernames and
passwords during the client auto deployment.
A:
The current version does not support the customization of the client
install package, and there is no item setting the Client password in the
install package. Please set the client password in the Console.
Q: How can I backup and restore my configuration in RemoteScope? (I
know the current version can backup Access database. How about the SQL
database?)
A:
You can use RSDB to backup the RS Console configuration, as the
screenshot shown below:
Application Data: Backup RS Console database.
Software Distribution Package: Backup the information of software
distribution under “productinfo” folder.
Scripts: Backup all the syntax script files under the Scripts
folder.
Network Profiles: Backup the network configuration file
netsegment.cfg.
System Configuration: Backup system configuration file
rsconsole.ini.
System Logs: Backup system log file Console.log.
Activation Configuration: Backup activation configuration info
files UserInfo.ini and Proxy.ini.
In the restore interface, each item is the same as that of this backup
interface. But only the items have backed up are available in the
restore interface.
Q: What is the connection limit of the screen broadcast? How many
clients can a console broadcast without problem?
A:
There is no connection limit to the screen broadcast. The number of
clients will not influent the performance.
Q: What is the maximum file size that RemoteScope can backup?
A:
RemoteScope provides quick and simple backup solutions even though it is
meant to be management software. The maximum file size that you can
backup using RemoteScope is 3Gb.
Q: I opened the necessary port in Windows Firewall but still cannot
connect with the clients I deployed. What can block the connection
between my console and clients?
A:
Verify the following:
Enable the ICMP response in Windows Firewall
Check "file and printer sharing" in the exception list, also in Windows
Firewall
Change Local Security Settings. Please make sure that the Policy
"Network access: Sharing and security model for local accounts" is set
to "Classic" instead of "Guest Only"
If you have Antispyware software installed, please make sure it does not
block client communication with the console.
Q: How do I change the default ports used by RemoteScope?
A:
You have two options for changing the default ports.
At the time of deployment, you may click the "Set the selected host
parameter" in the Deploy Client Wizard Configure window, and set the
port that you want to use. The client will use the port you configured
to connect to the console.
If the client has been already deployed; select the client that you want
to change the port in the client and group window and right click,
select Remote Configure and change the port number. Then, right click on
the selected clients again and select Properties. You may change the
port number that is next to IP address in the General Tab. Your console
may connect to the clients by using the new port number afterwards.
For information on your specific needs, please
contact us
or see our SOHO
edition (Small Office /Home Office) for small business applications
Back to top of page
