Exchange Server 2016 SPLA SAL Comparison

The following feature list is applicable to Exchange Server 2016 Hosted Exchange SALs. Plus SALs include the use of Microsoft Office Outlook desktop application.

The Exchange Server 2016 Hosted Exchange Basic, Exchange Server 2016 Hosted Exchange Standard, Exchange Server 2016 Hosted Exchange Standard Plus, Exchange Server 2016 Hosted Exchange Enterprise, Exchange Server 2016 Hosted Exchange Enterprise Plus and Productivity Suite SALs include the use of Outlook Web Access. You must obtain a SAL for each user.

Exchange 2016 Basic SAL

Each user for whom you obtain an Exchange Server 2016 Hosted Exchange Basic SAL may use the following features of the server software:

  • Outlook Web Access features that enable the features described in this SAL;
  • E-Discovery;
  • Exchange 2016 anti-spam;
  • Multi-Mailbox Search;
  • Messaging and personal folder access through the protocols described in this SAL;
  • Internet mail protocol (Simple Mail Transfer Protocol (SMTP), Post Office Protocol (POP), Internet Message Access Protocol (IMAP)) and Web browser access via any client;
  • Personal Mail Folders (not shared with other users);
  • Personal Address List (not shared with other users);
  • Personal Calendar (not shared with other users);
  • Personal Tasks (not shared with other users);
  • Support for a single, second level domain for a single user or user organization (user obtains the right to use ‘joe@smith.com’ or ‘joesmith@company1.com’ instead of ‘joe@servicesprovider.com’). Multiple suffixes (“.com”, “.net”, “.org”, etc.) are allowed (e.g., ‘joe@smith.com’, ‘joe@smith.net’, ‘joe@smith.de’, etc.); and
  • Global Address List: address list of all users within personalized domain or within the service provider’s entire domain.

Exchange 2016 Standard SAL, Standard Plus SAL and Productivity Suite SAL

Each user for whom you obtain an Exchange Server 2016 Hosted Exchange Standard SAL, Exchange Server 2016 Hosted Exchange Standard Plus SAL or Productivity Suite SAL may use the following features of the server software:

  • The features of the Exchange Server 2016 Hosted Exchange Basic SAL as described above;
  • Support for a multiple, second level domains for a single user or user organization;
  • Outlook Web Access features that enable the features described in this SAL;
  • Messaging Application Programming Interface (MAPI) network protocol;
  • Shared Folders;
  • Public Folders;
  • Shared Address List;
  • Shared Contacts;
  • Shared Tasks;
  • Shared Calendar;
  • Group scheduling, including viewing free/busy times of others;
  • Mobile Notification: Receive notification of events in the server software via mobile devices;
  • Mobile Browse: Access the server software inbox, calendar, address book, Global Address Book and tasks via mobile devices; and
  • Mobile Synchronization: Synchronize mobile devices over wireless networks with the server software inbox, calendar, address book and tasks.
  • Unified Messaging

Exchange 2016 Enterprise SAL, Enterprise Plus SAL

Each user for whom you obtain an Exchange Server 2016 Hosted Exchange Enterprise SAL and Exchange Server 2016 Hosted Exchange Enterprise Plus SAL may use the following features of the server software:

  • The features of the Exchange Server 2016 Hosted Exchange Standard SAL as described above;
  • Compliance Management;
  • Data Loss Prevention; and
  • In-Place Holds (Indefinite, Query-based, and Time-based)
  • In-Place Archive

Reference:  https://sur.microsoft.com/

AutoDesk License Manager / FLEXNet Licensing

I’m not really a fan of this FLEXNet licensing stuff. Mainly because I’m certain I don’t have a complete understanding of it, however, it shouldn’t be so seemingly overly complicated. Why is software working against me?!?

Had a server crash (power + UPS failure) that runs a Network License Manager for AutoDesk 2014. Upon getting the server back up, I had one particular user unable to load AutoCAD 2014 due to error -4.132.0.

Looking closer at this error and doing some initial debugging in the log file for LMTools, I see that a license was issued for a user on 7/7/2014, which is not this user in question.

Long story short, after an hour of going back and forth in documentation, trying things, testing, reading, testing, and finally Googling I came across a nice post that simply said to backup the adskflexborrow file from C:Documents and SettingsAll UsersApplication DataFNPFLEXlm and start the FLEXNet License Server again.

Voila. User can run AutoCAD now without error.

Another note from a commenter that may be helpful; He notes:

We had a case where the client end of FlexLM thought it had borrowed a license when the server had lost that “borrow”. So we could not return it. Less of a problem but still wrong.

If you need to clear this case you can delete FlexLM’s record of the borrow on the client by deleting the keys in registry: HKEY_LOCAL_MACHINESOFTWAREFLEXlm License ManagerBorrow