install ASA 6.0 on latest Windows 10 release 1

[bfordz]

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 settings.

Can someone point me in the right direction to get this to work?

I just completely uninstalled the ASA 6.0 from Win 10 to start over, Is there something different I need to do when installing in Windows 10?

 

[kyle555]

you mean voicemail?

When you connect to AAM or MM or CMM (and make sure you make the right choice in ASA!), you connect either over unencrypted port 389 or encrypted 636.

Also, when you go in CMM/MM/AAM, you go into the "Trusted Servers" - that's the account you need to use. In that trusted server page you'll see if you're allowed encrypted/unencrypted/both. It's also very important to note your name and password.

A Trusted Server has an IP address and a Trusted Server Name and Password. if you happened to put in 10.10.10.10 and kyle and Password! then that means a PC running ASA with IP address 10.10.10.10 can connect to CMM with username kyle and password Password! All 3 have to match - ip, trusted server name and password.

 

[bfordz]

Yes, the voicemail side.

"When you connect to AAM or MM or CMM (and make sure you make the right choice in ASA!), you connect either over unencrypted port 389 or encrypted 636."
- is this new for Windows 10? My current Windows 7 ASA is using SSH port 22.

"A Trusted Server has an IP address and a Trusted Server Name and Password. if you happened to put in 10.10.10.10 and kyle and Password! then that means a PC running ASA with IP address 10.10.10.10 can connect to CMM with username kyle and password Password! All 3 have to match - ip, trusted server name and password."
- When I go into the "Trusted Server", should I be able to see the current 'password'?
- All the information that is in the "Trusted Server" for asa is incorrect or information I'm not using currently in my ASA on Windows 7.
* The Trusted Server Name = ASA, I don't use that UserID and the IP address is for another Pc that has never used ASA.

Where can I go to reset the password for the login I'm using for voicemail access in ASA?
** CM > Security > Administrator Accounts > Change Login ??

 

[kyle555]

No, it's always that way to connect to a voicemail system. Not new in Win10
No, you can't see the Trusted Server password, feel free to change it and enter it in ASA

Voicemail uses LDAP login, not Linux level logins like CM. So, if your trusted server name is ASA, then that's the user account you'd use for your trusted server. If you were using voicemail on ssh port 22, then that's some older stuff i don't remember from when IA770 had a web page with a CLI terminal in it.

Are you doing like 'change subscriber' in a terminal in ASA when you had it working?

 

[bfordz]

yes, I would use 'ch sub' in an ASA window for our Audix voicemail.

After doing a complete un-install and re-install; I unchecked some boxes (changes you can't make once installed) and I got closer to the settings I have in my Win7 ASA.

While looking into the settings you suggested I also looked at the "Administrator Accounts" and I looked at my VM login and it was 'locked'. After unlocking it and not being successful I changed the password and now I'm getting in.

So, I think it was my installation choices and wrong password that caused my problems; mainly the installation choices because they were giving me the default ports that you had mentioned (389 or 636) no choice for SSH 22, which is what I was trying to duplicate from my Win7 ASA installation.

I will have to look closer to the installation next time and the setting you pointed out.
** I have to re-install Windows 7 so I'll be re-installing ASA again there.

Thank you for your help and suggestions.