FAQ
1. What problem does Ignition solve?
Currently, remote control and remote management products assume the remote system is functioning properly. When something goes wrong on the remote system, the user wonders what is happening and can become frustrated. Ignition can many times allow administrators to recover control without the need to reboot.
back to top
2. How does Ignition work?
Ignition stops and restarts services on remote machines. Ignition can also force a reboot of remote systems.
back to top
3. How does Ignition connect to the remote machine?
Ignition uses a TCP/IP connection typically over a LAN or the Internet.
back to top
4. Why not just use a product such as Windows XP remote desktop to fix problems on remote machines?
Windows XP Remote Desktop is similar to other remote control products on the market today. These tools provide a great way to manage remote systems when they are operating normally. When an application on a remote system completely utilizes the CPU, these products appear to stop working. Ignition uses such a small amount of system resources; it can many times operate when every other means of accessing the system fails
back to top
5. Why not just tell people to reboot?
That is great if someone is at the remote location. However, that is not always the case. When critical servers (with potentially multiple services per server) are involved, a quick intervention is preferred over a complete reboot.
back to top
6. Who are your competitors?
Since we are in a new market space, we do not know of any direct competitors. We have countless indirect competitors and a huge education problem. Remote management tools such Windows XP remote Desktop is fine for everyday use with systems that are working properly. Ignition is only needed on the rare occasions when something goes terribly wrong. When it is needed, it is absolutely needed.
back to top
7. Can Ignition terminate existing sessions between two remote systems?
Yes, many times system administrators leave a remote control session running between their desktop system and a remote server. As system administrators perform their duties away from their desks, they can regret leaving that session open. They find they need access to the remote system from where they are currently working and are unable to do so. Ignition provides a means for system administrators to terminate and restart the remote control service on the remote system terminating the existing session to their desk.
back to top
8. Can Ignition reboot a remote system?
Yes, Ignition can many times force a remote system to reboot when it can no longer be rebooted using many other remote application products.
back to top
9. What operating systems does Ignition support?
Ignition currently supports Windows NT 4.0, Windows 2000, Windows XP, and Linux
systems.
back to top
10. Does Ignition support legacy operating systems such as Windows 95 and Windows 98?
Sage Alliances is willing to develop an interface to legacy operating systems such as Windows 95 and 98 should there be sufficient customer interest. However, there is currently no release date available.
back to top
11. Can you do custom development for us to help differentiate us in the market?
We believe that custom development is an important part of what we offer. We understand the need to differentiate your product in the market.
back to top
12. Ignition is an OEM product. When do you plan to release an end-user product?
We have not yet finalized product plans for our end-user product. Focus groups have told us that we have a great product for the OEM market but we have to make a substantial investment before releasing it as a general product.
back to top
13. How is Ignition integrated into other applications?
Incorporating Ignition is simple. Typically Ignition can be implemented with approximately 12 lines of code. The code allows you to put an Ignition icon on the main application window. During operation, hitting the icon launches Ignition and Ignition runs as an adjunct program.
back to top
|
