Jesus Shelby's questions

I can not get Licensing issue resolved on Essentials server for Remote access. While I'm familiar with Windows server, I"m less familiar with the Essentials SKU.

The user has deployed Windows 2016 Essentials and completed the Access Anywhere wizard.

It appears to deploy all the RDS roles, it configures it for per-user licensing and the essentials server is listed as the licensing server. There are no errors around the deployment other than the licensing notice. licensing mode remains "Remote Desktop for Administration". I've noticed in the Technet forums where this was present on 2012 servers, but it seemed related to users who manually deployed the RDS role. In this case, everything was configured thru the Essentials wizard, so I assume here - all the roles should be deployed including the session host server.

If this were a standard deployment we would load up the CALs and call it a day - but there should be no additional license configuration needed for an Essentials server.

I've re-run the wizard and repaired the anywhere access - but nothing has changed. Curious if anyone has hit this with 2016 and what they did to resolve it.

I'm running into an issue with the latest version, 4.1.1.180, that I can't resolve.

After installation, the AD Connector is now failing and throwing errors. They fail on the import and export run profiles.

They sync fails with the no-start-ma status

The event log then registers two events

Event: 6005

The management agent "Domain.INT" failed on run profile "Export" because of an unspecified management agent error.
 Additional Information

 %3

Event 6401

 "ERR_: MMS(2276): ..\libutils.cpp(10143): Failed to start run because of undiagnosed MA error
Azure AD Sync 1.1.180.0"

I've installed the latest updates for .NET 4.5 and then installed .NET 4.6.1 but with same results (so it's currently running now with .NET 4.6.1).

Additionally, if you open the connector itself and try to refresh the schema or view the containers (OU"s) it throws an error

I've re-ran the configuration wizard - and this completes without error.
If I save the Import profile output it doesn't show me anything - it is connecting successfully to the-the domain controller.

   <ma-connection>
    <connection-log><incident><connection-result>success</connection-result><date>2016-05-13 18:04:35.121</date><server>DC.Domain.int:389</server></incident></connection-log>
   </ma-connection>

There are no errors logged from the profile. I also enabled the AD Sync event logs - but nothing is getting logged there either. As far as I can tell there are no other application logs we can check in the Azure AD directories. One other thing of note is that password sync continues to work - but new objects or changes to objects are not synced.

I'm in the process of upgrading Exchange from 2010 to 2013. The 2010 server is used with Lync 2013 as a unified messaging server. Co-existence is configured and proxy and redirects for normal exchange operations are working as expected, but not UM requests. When it hits the server Exchange 2013 appears to receive the request but doesn't pass it along to the 2010 server where the users mailbox resides.

When Exchange 2013 Servers are added to Dial Plans, users with mailboxes on the 2010 UM server can't receive voice mail, but migrated users on 2013 work as expected. When Exchange 2013 servers are not part of the dial plan than 2010 users work fine (but of course 2013 users will not).

Unfortunately a straight cut over of all users to 2013 is not possible, and I would like to ensure continued functionality for all users during the migration (otherwise I would prefer that and not worry about T/S this).

Nothing else is changing other than the Exchange server upgrade. I've validated the Dial plans, gateways, and hunt groups are all available on the 2013 server. I've followed the MS checklist here to double check my steps: https://technet.microsoft.com/en-us/library/dn169226%28v=exchg.150%29.aspx

I'm currently waiting on a MS support rep to schedule an outage and work thru it but I'm open to any ideas.