Hello,
We are preparing some deploy of Windows 8.1 tablets to use the native Metro (Modern) email Client using EAS to connect to a Lotus Domino Email Server.
Initially we can configure the email server connection, via Exchange Active Sync, without any issue and everything is working and syncing good.
At this time OS version was 6.3.9600 16384.
After Windows Updates the OS version is now 6.3.9600 17415 and the focused email client stop working and don't sync.
Looking for the account definitions when OS was on the previous version
(6.3.9600 16384) it was possible to define if the connection will use SSL or not. With the new OS version (6.3.9600 17415) the same account settings show now a "ghosted" option to activate or deactivate SSL. This could mean the newer version are forcing the SSL use...
From the server side the SSL is up and running and I already setup the same account, that have trouble with the Windows 8 Client, in a Android Tablet and with Windows 10, both using SSL, and it work without clues on both.
If I decided to make the Windows Updates before setting up the email Client using EAS even knowing the settings required for the account config are absolutelly correct, the email config routine insist saying "to check the parameters" and apparently the account is not added ...
The fields required in both versions to configure a EAS connection are:
- Account Email address
- Email Server address
- Domain
- User ID
- Password
So no reference or field relative to SSL...
So it seems some buggy way how the Metro Email Client make the setup for the account using EAS.
Any of you found the same issue or have some suggestions to solve this?
Where are saved the account settings for the native Windows Metro Email Client ? WindowsApp folde ? If so where ?
Thanks a Lot for you patience!
Cheers
We are preparing some deploy of Windows 8.1 tablets to use the native Metro (Modern) email Client using EAS to connect to a Lotus Domino Email Server.
Initially we can configure the email server connection, via Exchange Active Sync, without any issue and everything is working and syncing good.
At this time OS version was 6.3.9600 16384.
After Windows Updates the OS version is now 6.3.9600 17415 and the focused email client stop working and don't sync.
Looking for the account definitions when OS was on the previous version
(6.3.9600 16384) it was possible to define if the connection will use SSL or not. With the new OS version (6.3.9600 17415) the same account settings show now a "ghosted" option to activate or deactivate SSL. This could mean the newer version are forcing the SSL use...
From the server side the SSL is up and running and I already setup the same account, that have trouble with the Windows 8 Client, in a Android Tablet and with Windows 10, both using SSL, and it work without clues on both.
If I decided to make the Windows Updates before setting up the email Client using EAS even knowing the settings required for the account config are absolutelly correct, the email config routine insist saying "to check the parameters" and apparently the account is not added ...
The fields required in both versions to configure a EAS connection are:
- Account Email address
- Email Server address
- Domain
- User ID
- Password
So no reference or field relative to SSL...
So it seems some buggy way how the Metro Email Client make the setup for the account using EAS.
Any of you found the same issue or have some suggestions to solve this?
Where are saved the account settings for the native Windows Metro Email Client ? WindowsApp folde ? If so where ?
Thanks a Lot for you patience!
Cheers
Last edited by a moderator:
My Computer
System One
-
- OS
- win8.1
- Computer type
- Tablet
- System Manufacturer/Model
- ASUS T100