'Incident Commander Pro - Version 8'

Hard-Wired Hub
Network Selection & SetupWireless Network

  Selecting a Network Configuration

Three network configurations are recommended for optimum program performance:

  or_ball.gif (967 bytes)Environment 1:      Windows 2008 Server with a Remote Desktop Connection from the client to the server.

or_ball.gif (967 bytes)Environment 2:      Windows 2000, 2003 or 2008 Server in a client / server configuration.

or_ball.gif (967 bytes)Environment 3:      Windows XP Professional, Win 7 or Win 8, in a peer-to-peer configuration.

Summary

Environment 1:      Windows 2008 Server with a Remote Desktop Connection from the client to the server provides very fast connectivity between the client computers and the host server and is especially efficient when 'Incident Commander Pro's GIS mapping module is being run from the client to the host server. This configuration utilizes the inherent high speed of the host server and  is not slowed down by the usually slower processing speeds of the client desktop computers. This is the recommended system for the fastest processing speed, especially when the mapping module is being run from a client computer.

Environment 2:     A Windows 2000, 2003 or 2008 Server Configuration, is far more stable, and generally faster than the peer-to-peer file sharing employed by Windows XP Pro. The server platformís ability to manage cache memory and record locking seem to provide a more stable environment for deployment in a networking situation. However Environment 3, the XP Pro platform, has a distinct cost saving over the server platform.

Environment 2, utilizing a Windows 2000, 2003 or 2008 Server, a SCSI hard drive, and 10 / 100 Ethernet, produced the fastest raw network performance for clients running the network version of the Incident Commander Pro software. It should be noted that the hard drive specifications and interface, is a definite factor in the high performance of the system. This configuration was tested on a desktop server, as SCSI versions of hard drives on laptops do not seem to be an available option.
This desktop configuration did not exhibit any noticeable issues surrounding Incident Commander Pro and itís use on a true server platform. This configuration was also tested with Windows 2003 Server installed on a laptop with some measurable performance increases, especially with some of the new features inherent in this latest release of the server operating system.
The Windows 2003 Server server-based network configuration provided higher speed and is more stable than a peer to peer network environment.  


 

 

 

 

 

 

 

 

 

 

 

 

 




Environment 3:     Utilizing Windows XP Pro in a Peer-to-Peer Network Configuration, provided basic functionality for a small number of clients. It is strongly recommended that the only XP Pro be used as the host and not the Home version. The primary benefit of the Windows XP Pro configuration is reasonable network stability and moderate cost.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Prepared by:  Glen Kulak

Recommended System Requirements

Setting up a Network System
For all three network environments follow Step 1, Step 2 and Step 3 below to install the 'Incident Commander Pro' system files on each client computer:

or_ball.gif (967 bytes)Step 1. Install Incident Commander Pro on the Host or Server computer, then register the program with the required number of Network Licenses.

or_ball.gif (967 bytes)Step 2. Run the IC_ClientSetup program, on each Client computer, to install all of the necessary system files onto each Client computer to be networked to the Host.

or_ball.gif (967 bytes) Step 3. Follow the step-by-step instructions described in Configuring Incident Commander For Network Use PDF document, to configure Windows XP to run Incident Commander over the network.

Note: Microsoft's website provides more detailed information on how to configure a file sharing network for Windows XP.

Conclusions

The server software is designed to provide optimized network use and as a result performs far better than the peer to peer configuration in the network environment. There are, however, two issues to consider when choosing the server option.

   or_ball.gif (967 bytes)The cost for the Windows server software is substantial.

  or_ball.gif (967 bytes)The server software, potentially on a laptop, requires substantial computing power, and therefore the hardware specifications are of importance. Typical areas to watch for are ram speed and quantity, hard drive access speed and network bandwidth capabilities. It should be noted that current laptops are not certified for the server version of the Windows software, however no detectable anomalies were encountered when the software was installed and tested on a laptop.

The use of the server software in large network deployments would probably justify the additional cost.

For small network environments, Windows XP Pro in a peer-to-peer configuration, will provide adequate basic file and print services for a few clients. It should be noted the other applications installed on the client and host machines should be carefully monitored and minimized, as they can affect the stability.

 

Networking 'Incident Commander Pro'

For more information please contact:
SAR Technology Inc.
Phone: (604) 921-2488    Fax (604) 921-2484      sartechnology@telus.net

<-- Go Back to SAR Technollogy Home PageSAR Technology Home