Building a new Windows 2016 Standard virtual machine to test the x64 "package" from thaiminhan. I will give you any "special advice" if new steps are needed to fully install Mdaemon 17.5.3...
Thank you Thaiminhan. You very good. SecurityPlus v5.5.1 Rebuild by you was very well Thu 2018-04-12 10:33:59.852: Attempting to load 'Outbreak Protection' plug-in Thu 2018-04-12 10:33:59.852: * Outbreak Protection::StartupFuncName @0000000007022310 Thu 2018-04-12 10:33:59.852: * Outbreak Protection::ConfigFuncName @0000000007019D10 Thu 2018-04-12 10:33:59.852: * Outbreak Protection::SMTPMessageFuncName2 @0000000007020380 Thu 2018-04-12 10:33:59.852: * Outbreak Protection::ShutdownFuncName @000000000701D4C0 Thu 2018-04-12 10:33:59.852: * Outbreak Protection plug-in loaded in slot 7 Thu 2018-04-12 10:33:59.852: ---------- Thu 2018-04-12 10:33:59.852: Outbreak Protection plug-in is starting up Thu 2018-04-12 10:33:59.852: * Outbreak Protection engine is starting up... Thu 2018-04-12 10:34:01.369: * Outbreak Protection engine version: 8.00.0125.1 Thu 2018-04-12 10:34:01.376: * Outbreak Protection engine is ready for use. Thu 2018-04-12 10:34:01.376: ----------
Fully Running on a brand new Windows 2016 Standard virtual machine with the "package" of thaiminhan : Using files directly downloaded from http://www.altn.com/Downloads/ md1753_en_x64.exe av551_en_x64.exe oc501_en.exe Installed the same way, with the same steps as any 16.x.x and 17.x.x previous version. Replacing files, and doing the usual license.xml mods. My hosts file only contains: 0.0.0.0 services.altn.com _________________________________________________ Antivirus log: _________________________________________________ 2018-04-12 20:02:43 -- SPUPDATER START -- 2018-04-12 20:02:43 Version 5.5.1 2018-04-12 20:02:43 Subscription active: 1825 days left 2018-04-12 20:02:45 Definition version: 201804121854 2018-04-12 20:02:45 Download file OK http://files.altn.com/antivirus/ctav/updates/antivir-v2-i-201804121854.zip 2018-04-12 20:02:52 Install file OK C:\MDaemon\Queues\Temp\CTAVWORK\20180412200245\antiviri-v2.def 2018-04-12 20:02:53 New definition version: 201804122201 2018-04-12 20:02:53 Virus definitions updated successfully. 2018-04-12 20:02:57 -- SPUPDATER END -- _________________________________________________ Licenses: _________________________________________________ MDaemon Server: License name: Mail Company or distributor: Mail Registration key: 1234567-2357642-7654321 Registered / PRO / Unlimited users 1825 days of software license renewal coverage remaining. Activation has been successfully performed. _________________________________________________ SecurityPlus for MDaemon: License name: Mail Company or distributor: Mail Registration key: 1234567-2357642-7654321 Registered / Unlimited users 1825 days of virus definition updates remaining. Activation has been successfully performed. _________________________________________________ Outlook Connector: License name: Mail Company or distributor: Mail Registration key: 1234567-2357642-7654321 Registered / Unlimited users 1825 days of software license renewal coverage remaining. Activation has been successfully performed. _________________________________________________ ActiveSync: License name: Mail Company or distributor: Mail Registration key: 1234567-2357642-7654321 Registered / Unlimited users 1825 days of software license renewal coverage remaining. Activation has been successfully performed. _________________________________________________ Files versions: _________________________________________________ MDaemon Server (64-bit) SMTP/POP/IMAP server: v17.5.3 WorldClient HTTP server: v17.5.3 WorldClient DLL: v17.5.3 WorldClient Instant Messenger client: v17.5.2 Content filter server: v17.5.3 Content filter DLL: v17.5.3 Content filter GUI: v17.5.3 Calendar API (MDCalendar.dll): v17.5.3 Mailing list API (MDList.dll): v17.5.3 Original "Flat-File" API (MDUser.dll): v17.5.3 COM/DCOM API (MDUserCOM.dll): v17.5.3 LDAP API (MDUserLDAP.dll): v17.5.3 ODBC/SQL API (MDUserODBC.dll): v17.5.3 SyncML (MDSyncML.dll): v17.5.3 MDaemon<->BIS integration plugin (MDBis.dll): 17.5.3 ClamAVPlugin.dll (ClamAVPlugin.dll): 5.5.1 Dynamic Screening (64bit) for MDaemon Messaging Server (DynScrn.dll): 17.5.3.44 ActiveSync Mgmt Module (64bit) for MDaemon Messaging Server (MDASMgmt.dll): 17.5.3.9 AutoDiscovery Service (64bit) for MDaemon Messaging Server (MDAutoDiscover.dll): 17.5.3.2 Management Web Service (64bit) for MDaemon Messaging Server (MDMgmtWS.dll): 17.5.3.4 MDPGP (mdpgp.dll): 16.5.0a MDOP (mdop.dll): 1.3.8 ActiveSync (MDAirSync.dll): v17.5.3.26 NT/2K/XP utility API (NTUtil.dll): v17.5.3 DKIM API (LibDKIM.dll): v1.0.21 AntiSpam server daemon (MDSpamD): v3.41.0 CalDAV/CardDAV (MDWebDAV.dll): v17.5.3 XMPP server (WCXMPPServer.exe): v17.5.3 SecurityPlus for MDaemon: AV overall system: v5.5.1 AV engine source: Alt-N Technologies, Ltd AV known viruses: 201804122201 AV last virus update: Thu 2018-04-12 20:02:53 Outbreak Protection (MDOP.dll): v1.3.8 Outlook Connector for MDaemon: Plug-in: v5.0.1 Remote Administration Server: HTTP server: v17.5.3 _________________________________________________ Thank you again thaiminhan !!!
Plug-ins loaded without errors and running ok : _________________________________________________ Thu 2018-04-12 20:02:22.606: Attempting to load 'DynScrn' plug-in Thu 2018-04-12 20:02:22.606: * DynScrn::ConfigFuncName @00007FF825593A50 Thu 2018-04-12 20:02:22.607: * DynScrn::HrMDPluginServiceQueryState @00007FF825597630 Thu 2018-04-12 20:02:22.607: * DynScrn::HrMDPluginServiceQueryIcons @00007FF8255975E0 Thu 2018-04-12 20:02:22.607: * DynScrn::HrMDPluginServiceControl @00007FF825597A70 Thu 2018-04-12 20:02:22.607: * DynScrn::HrMDPluginServiceContextMenu @00007FF825597F00 Thu 2018-04-12 20:02:22.607: * DynScrn::HrMDPluginServiceDblClk @00007FF825596AC0 Thu 2018-04-12 20:02:22.607: * DynScrn::HrMDPluginGetLogfilePath @00007FF825596990 Thu 2018-04-12 20:02:22.607: * DynScrn::HrMDPluginMTAPreProcess @00007FF8255944A0 Thu 2018-04-12 20:02:22.607: * DynScrn plug-in loaded in slot 2 Thu 2018-04-12 20:02:22.607: ---------- Thu 2018-04-12 20:02:22.627: Attempting to load 'MDASMgmt' plug-in Thu 2018-04-12 20:02:22.628: * MDASMgmt::GetDialogInfoFuncName @00007FF82538A8A0 Thu 2018-04-12 20:02:22.628: * MDASMgmt::HrMDPluginServiceQueryState @00007FF82538D240 Thu 2018-04-12 20:02:22.628: * MDASMgmt::HrMDPluginServiceQueryIcons @00007FF82538DD10 Thu 2018-04-12 20:02:22.628: * MDASMgmt::HrMDPluginServiceControl @00007FF82538D0B0 Thu 2018-04-12 20:02:22.628: * MDASMgmt::HrMDPluginServiceContextMenu @00007FF82538D2E0 Thu 2018-04-12 20:02:22.628: * MDASMgmt::HrMDPluginServiceDblClk @00007FF82538CFF0 Thu 2018-04-12 20:02:22.628: * MDASMgmt::HrMDPluginGetLogfilePath @00007FF82538CB10 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem::&Options/Customize @00007FF82538BEA0 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem::&Service Tuning @00007FF82538BFF0 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem::&Global Client Settings @00007FF82538C770 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem:&rotocol Restrictions @00007FF82538BF50 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem:omain &Management @00007FF82538C280 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem::&Client Management @00007FF82538C210 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem::&Account Management @00007FF82538C320 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem::Co&nnection Monitor @00007FF82538C800 Thu 2018-04-12 20:02:22.628: * MDASMgmt::MenuItem::&Log Viewer/Analyzer @00007FF8253AC5E0 Thu 2018-04-12 20:02:22.628: * MDASMgmt plug-in loaded in slot 3 Thu 2018-04-12 20:02:22.629: ---------- Thu 2018-04-12 20:02:22.644: Attempting to load 'MDAutoDiscover' plug-in Thu 2018-04-12 20:02:22.644: * MDAutoDiscover::HrMDPluginServiceQueryState @000000018003B6E0 Thu 2018-04-12 20:02:22.644: * MDAutoDiscover::HrMDPluginServiceQueryIcons @000000018003BA80 Thu 2018-04-12 20:02:22.644: * MDAutoDiscover::HrMDPluginServiceControl @000000018003B890 Thu 2018-04-12 20:02:22.644: * MDAutoDiscover::HrMDPluginGetLogfilePath @000000018003BA10 Thu 2018-04-12 20:02:22.644: * MDAutoDiscover plug-in loaded in slot 4 Thu 2018-04-12 20:02:22.644: ---------- Thu 2018-04-12 20:02:22.656: Attempting to load 'MdMgmtWS' plug-in Thu 2018-04-12 20:02:22.656: * MdMgmtWS::HrMDPluginServiceQueryState @0000000007F1FBF0 Thu 2018-04-12 20:02:22.656: * MdMgmtWS::HrMDPluginServiceQueryIcons @0000000007F1FFA0 Thu 2018-04-12 20:02:22.656: * MdMgmtWS::HrMDPluginServiceControl @0000000007F1FDB0 Thu 2018-04-12 20:02:22.656: * MdMgmtWS::HrMDPluginServiceContextMenu @0000000007F20630 Thu 2018-04-12 20:02:22.656: * MdMgmtWS::HrMDPluginGetLogfilePath @0000000007F1FF30 Thu 2018-04-12 20:02:22.656: * MdMgmtWS plug-in loaded in slot 5 Thu 2018-04-12 20:02:22.656: ---------- Thu 2018-04-12 20:02:22.685: Attempting to load 'MDPGP' plug-in Thu 2018-04-12 20:02:22.685: * MDPGP::StartupFuncName @00007FF8265A4E60 Thu 2018-04-12 20:02:22.685: * MDPGP::ConfigFuncName @00007FF8265A5B30 Thu 2018-04-12 20:02:22.685: * MDPGP::ReloadFuncName @00007FF8265A5C10 Thu 2018-04-12 20:02:22.685: * MDPGP:reMessageFuncName @00007FF8265A5C60 Thu 2018-04-12 20:02:22.685: * MDPGP:ostMessageFuncName @00007FF8265A60D0 Thu 2018-04-12 20:02:22.685: * MDPGP::ShutdownFuncName @00007FF8265A5A10 Thu 2018-04-12 20:02:22.685: * MDPGP plug-in loaded in slot 6 Thu 2018-04-12 20:02:22.685: ---------- Thu 2018-04-12 20:02:22.685: MDPGP plug-in is starting up Thu 2018-04-12 20:02:22.732: MDPGP - OpenPGP for MDaemon v17.5.3 (64-bit) (RFC 4880) Thu 2018-04-12 20:02:22.732: * Using: Library v14.0.292 Thu 2018-04-12 20:02:22.732: * Using: MDaemon v17.5.3 Thu 2018-04-12 20:02:22.732: * Using: C:\MDaemon\App\Plugins.dat Thu 2018-04-12 20:02:22.733: * Using: C:\MDaemon\App\MDaemon.ini Thu 2018-04-12 20:02:22.733: * Using: C:\MDaemon\App\MDUser.dll Thu 2018-04-12 20:02:22.733: * Key-ring using: C:\MDaemon\pem\_mdpgp\Keyring.public Thu 2018-04-12 20:02:22.733: * Key-ring using: C:\MDaemon\pem\_mdpgp\Keyring.private Thu 2018-04-12 20:02:22.733: * Key-ring: loaded 0 public-keys Thu 2018-04-12 20:02:22.733: * Key-ring: loaded 0 secret keys Thu 2018-04-12 20:02:22.733: Startup successful Thu 2018-04-12 20:02:22.733: ---------- Thu 2018-04-12 20:02:22.740: Attempting to load 'Outbreak Protection' plug-in Thu 2018-04-12 20:02:22.740: * Outbreak Protection::StartupFuncName @00000000076D2310 Thu 2018-04-12 20:02:22.740: * Outbreak Protection::ConfigFuncName @00000000076C9D10 Thu 2018-04-12 20:02:22.740: * Outbreak Protection::SMTPMessageFuncName2 @00000000076D0380 Thu 2018-04-12 20:02:22.740: * Outbreak Protection::ShutdownFuncName @00000000076CD4C0 Thu 2018-04-12 20:02:22.740: * Outbreak Protection plug-in loaded in slot 7 Thu 2018-04-12 20:02:22.740: ---------- Thu 2018-04-12 20:02:22.740: Outbreak Protection plug-in is starting up Thu 2018-04-12 20:02:22.740: * Outbreak Protection engine is starting up... Thu 2018-04-12 20:02:22.879: * Outbreak Protection engine version: 8.00.0125.1 Thu 2018-04-12 20:02:22.880: * Outbreak Protection engine is ready for use. Thu 2018-04-12 20:02:22.880: ---------- _________________________________________________
Mail Server is DDoS by Bootnet ? IP 203.155.200.117 request connection always Fri 2018-04-13 10:22:59.486: Session 027386; child 0001 Fri 2018-04-13 10:22:59.486: Accepting SMTP connection from 203.155.200.117:50596 to xxx.xxx.xxx.xxx:25 Fri 2018-04-13 10:22:59.528: --> 220 mail.abc.com.vn ESMTP Fri, 13 Apr 2018 10:22:59 +0700 Fri 2018-04-13 10:22:59.886: <-- HELO mail.abc.com.vn Fri 2018-04-13 10:22:59.887: Performing SPF lookup (mail.abc.com.vn / 203.155.200.1174) Fri 2018-04-13 10:23:00.034: * Result: none; no SPF record in DNS Fri 2018-04-13 10:23:00.034: ---- End SPF results Fri 2018-04-13 10:23:00.035: --> 250 mail.abc.com.vn Hello mail.abc.com.vn [203.155.200.117], pleased to meet you Fri 2018-04-13 10:23:00.389: <-- AUTH LOGIN Fri 2018-04-13 10:23:00.389: --> 538 5.7.11 An SSL connection is required Fri 2018-04-13 10:23:00.791: <-- QUIT Fri 2018-04-13 10:23:00.791: --> 221 2.0.0 See ya in cyberspace Fri 2018-04-13 10:23:00.791: SMTP session terminated (Bytes in/out: 44/226) Fri 2018-04-13 10:23:00.792: ---------- Fri 2018/04/13 10:12:11.497: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:16:16.825: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:16:16.825: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:20:22.897: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:20:22.898: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:24:35.958: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:24:35.958: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:28:39.843: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:28:39.843: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:32:40.933: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:32:40.933: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:36:41.747: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:36:41.747: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:40:42.753: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:40:42.753: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:44:42.943: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:44:42.943: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:48:41.872: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:48:41.872: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:52:40.024: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117) Fri 2018/04/13 10:52:40.024: Debug, [00000043] 0x41502103 Refusing SMTP access: IP:203.155.200.117 Fri 2018/04/13 10:56:40.168: Debug, [00000043] 0x41502150 Blacklist: found IP:203.155.200.117 (via 203.155.200.117)
MDaemon Server v18.0 Release Notes MDaemon 18.0.0 - April 17, 2018 SPECIAL CONSIDERATIONS [16456] Hosted email options with MDaemon Private Cloud are now available. To learn more, please visit: http://www.altn.com/Products/MDaemon-Private-Cloud/. [20008] Alt-N Technologies has changed its name to MDaemon Technologies. WorldClient is now MDaemon Webmail, WorldClient Instant Messenger is now MDaemon Instant Messenger, SecurityPlus is now MDaemon Antivirus, and Outlook Connector is now MDaemon Connector. [19546] The MDaemon installer now includes MDaemon AntiVirus and MDaemon Connector, which are licensed separately. [19512] The "From Header Modification" feature has changed. It operates as before however the format of the final modified From data has changed from this format: "Email -- Name" <Email> to this format: "Name (Email)" <Email>. This new format is more readable/usable/sortable etc. If you would rather keep the old format (your users may be used to it already) you can check a box at Ctrl+S|Screening|Hijack Detection|From Header Modification. [19577] A past installer reset the option "Ctrl+S|Sender Authentication|SMTP Authentication|Authentication is always required when mail is sent from local IPs" to disabled for upgraders. The installer has been changed to ignore this setting. You must manually check that this option is set to your desire. The default is for it to be checked (enabled) but you should check to be sure it is set how you want. [19703] The following settings have had default values changed. Existing installations should check to be sure the following settings are as desired: Ctrl+S|Security Settings|SSL & TLS|MDaemon: Enable the dedicated SSL ports... and SMTP server requires STARTTLS... options have had defaults changed from disabled to enabled. Ctrl+S|Security Settings|Sender Authentication|DMARC verification|Honor p=reject... has changed from disabled to enabled. Ctrl+S| Security Settings|Sender Authentication|SPF Verification|User local address in SMTP envelope...has changed from disabled to enabled. Ctrl+S|Security Settings| Screening|IP Screen|Apply IP Screen to MSA connections has changed from disabled to enabled. Ctrl+S|Security Settings|Screening|Host Screen|Drop connection after EHLO has changed from disabled to enabled. [19612] Catalog functionality has been deprecated and removed from the UI. [20220] All Virtru related support has been removed from MDaemon Webmail. Old encrypted messages can still be viewed in the Virtru Secure Reader. [20339] Previously when a message was sent to an alias, MDPGP would encrypt it using the key for the actual email address. Now that same message won't be encrypted. To encrypt it now requires a key for the alias. MAJOR NEW FEATURES [19571] DNSSEC Ctrl+S|SSL&TLS|DNSSEC allows you to request DNSSEC service from your DNS server(s). When enabled, MDaemon sets the AD bit when making DNS queries and checks for it in the answers. This may not work with all DNS server(s) (not sure) so you'll have to try with yours. DNSSEC service is only applied to messages that meet your selection criteria. DNSSEC service can be "requested" or "required" on a per-message basis. If "required" and DNS results fail to include authenticated data then the message is bounced back to sender. If "requested" then DNSSEC service is attempted but nothing happens if it fails. Mail session logs will include a line at the top if DNSSEC service was used and "DNSSEC" will appear next to secure data in the logs. IMPORTANT: MDaemon is a non-validating stub-resolver. This means that it will request authenticated data from DNS server(s) but it has no way to independently verify that the data it gets from them is secure. However, if you know/trust your connection to your DNS server(s) (for example, it runs on localhost or within a secure LAN or workplace) then you should use this as it will boost security. DNSSEC lookups take more time and resource and I think less then 7% of domains have currently deployed it. That is why this is not configured to apply to every message delivery by default. However, if you want that, you can force every email sent to use DNSSEC by adding one line like "To *" into the configuration file (see Ctrl+S|SSL&TLS|DNSSEC). [15288] Email Snooze MDaemon Webmail was updated to allow a user to snooze an email. When a message is snoozed it will be hidden from the user for a designated period of time. To snooze a message, right click on it and choose the "Snooze for..." option in the context menu. Then choose how long you wish to snooze the message for. The "Choose a date and time" option is only available for browsers that support the date and time inputs. Hidden messages can be viewed in LookOut theme by clicking the "View Snoozed Messages" icon in the toolbar and WorldClient theme by choosing "view snoozed" from the view drop down menu in the toolbar. This feature is on by default. To turn off the feature, go to Options | Personalize, and find the Inbox Settings. Uncheck the "Enable Message Snooze" box. There are no snooze controls in Lite and Mobile theme, but snoozed messages are still hidden. [1520] Public Calendars In MDaemon Webmail users can publish a calendar to a publicly accessible link. Users have the option to password protect the calendar. To disable this globally, change the value of [Default:Settings] EnablePublicCalendars to No. To disable it on a per user basis, add CanPublishCalendars=No to a user's User.ini file. To publish a calendar, in LookOut or WorldClient theme, go to Options | Folders and click the "Share Folder" button next to the calendar you wish to publish. In the dialog, open the Public Access tab and if desired, fill in the display name or require a password, then click the "Publish Calendar" button. A confirm dialog will show up to tell the user what is about to happen. After clicking OK, an alert will display the new URL where the calendar is available. There will also be a link displayed on the page once the calendar has been published. To unpublish the calendar, click the "Unpublish Calendar" button. To change the password or the display name, click the "Update" button. [10886] Remember Me A "Remember Me" option has been added to the logon page of MDaemon Webmail. This feature is disabled by default. The default expiration is 30 days, and the maximum expiration setting is 365 days. It can be enabled in the MDRA GUI under Main->Webmail Settings->Settings. Users can check the "Remember Me" option on the logon page to be remembered on a specific device. Then if they have a bookmark with any of three View URL variables set (View=Main, View=Logon, or View=List) (or no View URL variable set), the user will be automatically logged in. Two Factor Authentication (2FA) is separate and will still be required when the 2FA remember me token expires. [19865] "Remember Me" was also added to the Remote Administration logon page. This feature is disabled by default. The default expiration is 30 days, and the maximum expiration setting is 365 days. It can be enabled in the MDRA GUI under Main->Remote Admin Settings->Settings. Users can check the "Remember Me" option on the logon page to be remembered on a specific device. Two Factor Authentication (2FA) is separate and will still be required when the 2FA remember me token expires. [19738] Exempt Known ActiveSync Devices from Location Screening An option has been added to allow a previously known ActiveSync device to bypass location screening. Administrators can enable this option to allow users to continue to access their account via ActiveSync from a location that is configured to block authentication attempts. In order to exempt the device it must have connected and authenticated using ActiveSync within the time frame configured to remove inactive clients. To exempt a device go to Setup / Mobile Device Management / Clients, select the client and click Settings, then check the box for Exempt from Location Screening. You can also choose to Whitelist the address the client is connecting from. This can be used to allow other clients that might be connecting from the same IP address to also bypass location screening.
Looks like all Trial Keys for 17.5.3 have been deactivated on Sunday April 15. No more Keys being given out for AV and OC. This is due to New MD 18.00 and integrated OC and AV. Trial key is still available for new MD 1800. Will test to see how the licensing works with the integration of OC and AV.
