Dirk,
We have had lots of discussion about SA here, and overall we love the product. If we could ask for only one feature in future releases it would be this:
The separation of the SA check engine from the interface. This way the engine could be started as a service and never touched while remote connections via Terminal Server, Citrix or whatever could load the interface for adds/changes to the config.
The interface could be compiled or web; based-doesn't matter. But the current remote access issues make running in service mode challenging to work with SA in a "dark" or remote computer room.
Ie: Remote connect to machine. Stop SA Service. Start new desktop copy. Make Changes. Save file. Exit local copy. Start SA service.
Or run it on a Windows 2003 box and term serv to the console.
But, I agree, separating the interface would be ideal. Especially if one option was a web interface since then you could make changes as required from almost anywhere.
-Tom
Powerone Media
Security Tip: When possible, use a passphrase instead of a password.
