The only thing holding me back from administering CM that way was that I didn’t have any way to use SAT’s required function keys from within PuTTY.Įnter TuTTY. For those things that used SSH, mRemoteNG launched a PuTTY session behind-the-scenes, and presented its UI in a tab. I had long been mRemoteNG (previously mRemote) for connection/session management of the various things I needed to be able to administer, regardless of whether each thing used RDP or SSH. I tried SecureCRT, but decided that it didn’t provide any appreciable benefit over ASA. The responses I got were entirely negative toward ASA everyone preferred VanDyke SecureCRT, and many people used it exclusively. WindowsĮarly-on in my CM administration experience, I asked some employees at Avaya and our Avaya Business Partner what tools they recommended that I use for administering CM via SAT. SAT is the term Avaya uses for the functionality that permits CM to be administered via a command-line curses-like interface, generally via telnet, SSH, or serial. So I found other ways to give me access to the System Administration Terminal (SAT).
#SSH EMULATOR MAC WINDOWS#
I fairly quickly tired of using RDP (to connect to a Windows machine that had ASA installed) or a VM (to run a Windows VM that had ASA installed on a desktop without either Windows or ASA).
That was fine, when I used only Windows, and only ever needed to administer CM from stations where ASA was installed. On Windows, I mostly used Avaya Site Admin (ASA), in either interface mode (GEDI or Emulation).
#SSH EMULATOR MAC MAC OS X#
In the time I’ve been administering CM, I’ve used Windows, Linux, and Mac OS X – all as my primary desktop operating system.
0 kommentar(er)
