- Avaya Secure Access Administration Overview 8 Avaya Integrated Management Release 5.2 Secure Access Administration Opening the Help to a Topic of Interest To open the help directly to a topic of interest: 1. Or Select Help Help On. The cursor changes to the shape of an arrow with a question mark.
- Since Windows 7 has been widely available to the business community for a few months now. Has anyone used Windows 7 in a production environment for ASA, CMS, IP Agent, IP Softphone, VAL Manager or any other apps? Can you enlighten us on successes or failures? Thanks, gblucas CM 5.2 CMS R14 Intuity Audix 5.1.
- Avaya site administration windows 7 in Description. IIS Admin allowed for multiple site definitions to be created under Windows XP (with only a single site started at a time).It can create a separate site for each project, all the configuration changes would be saved with that site, and to switch you just start a different site.
ASA 5.2 Windows 7 Crashing. November 21, 2014, 1:18 am. Had a customer wanting to run reports on an older voice-mail system so had to install ASA 5.2 (Avaya Site Administrator) but found it repeatedly crashed in Win 7, fortunately came across this useful snippet of information on a support forum. Delete the uxtheme.dll from C:Program. CM/CMM 5.2 on S8800 Windows 10 pro 64bit ver.1803 ASA 6.0 New Pc with Windows 10 pro 64 bit; Installing ASA 6.0 and I can't get connected to our VM server. I got the Voice services setup, duplicating our ASA Windows 7 settings, but I can't get our VM services to connect using our ASA Windows 7.
The Microsoft® ODBC Data Source Administrator manages database drivers and data sources. This application is located in the Windows Control Panel under Administrative Tools. Beginning in Windows 8, the icon is named ODBC Data Sources, and on 64-bit operating systems there is a 32-bit and 64-bit version.
For information about detailed ODBC Administrator procedures, open the ODBC Data Source Administrator dialog box and click Help.
You can use PowerShell commands to manage drivers and data sources. For more information about these PowerShell commands, see Windows Data Access Components PowerShell commands.
This section contains the following topics.
This is not an official guide! Past performance is no guarantee of future results!
Avaya Site Administration 5.2 Windows 7 32-bit
I've been lucky enough to be testing Windows 10 for some time, and have spoken to lots of Avaya engineers who were worried about using Windows 10 because of compatability with Avaya products. I thought I'd compile an unofficial list of what works and doesn't. Engineers like to tinker with new toys, so wanted to pass on my experience in case you brick your laptop just before walking on site...
Please bear in mind, this list is based on the Preview build (10162 and earlier), and may not be representative of the final version when it's released on July 29th. My testing comprises of using Windows 10 on three machines, two of which are installed on the primary partition, the third is on VirtualBox on Mac OS X Yosemite (10.10.3). The results are from all three instances unless noted.
- Provision (2014.3) - no issues found connecting to CM, MM and AAM.
- ASA (6.0.07 SP11) - no issues including Announcement backup/restore (SP12 is coming soon to support CM7, but this has not been seen/tested)
- One-X Communicator 6.2.4.07 - worked fine in H.323 and SIP mode, have not tried any presence or video, just voice
- One-X Agent 2.5.5 (not tested through VirtualBox) - registered to a CM with no issues - recommend more thorough testing
- CMS Supervisor R17 (not tested through VirtualBox) - limited testing here but worked fine
Other third party apps that have been used and found to be working:
- PuTTY 0.63
- WinSCP 5.7.3/5.7.4
- SecureCRT 7.3.4
- VMWare vSphere client 5.5 and 6.0
Firefox remains the browser of choice connecting to Avaya products. Microsoft Edge (the IE replacement) did not fare well, but truthfully I gave it 5 minutes before I realized it sucked and moved back to something tried and tested. Edge doesn't seem to have a decent PDF viewer built in...so no wonder I changed back. Will get better over time I am sure.
So far so good...now for the bad stuff:
On a number of these builds, I found the upgrade process from build to build bricked my network adapters and/or prevented VPN clients (Cisco & SonicWall) from functioning at all. At this current time, 10162 has bricked both my VPN clients and even a fresh ISO install of 10162 doesn't solve the problem. This will probably go away when Windows 10 goes live, but it's been a nagging problem for a few months. Worth testing first if you rely on VPN clients for day-day or customer connectivity.
Avaya Site Administration Guide
Hope this helps :) and please add your experiences in the comments.
Product names and trademarks used in this post are owned by their respective corporations.