NOTE: There is no Client Access role with Exchange Server 2016. All roles, with the exception of the Edge Transport server role, have been combined to align with Microsoft’s long recommended guidance for multi-role servers.
2. Restart the server (required). Alternately, “-Restart” (quotes excluded) can be appended to the command above to automatically restart the server upon completing the install of the required roles and features.
NOTE: There are many hardware configurations that can be recommended, however, the items above are fairly consistent with all of projects I manage. Your suggestions are welcomed as I am always seeking to improve.
When integrating your Windows 10 devices into Microsoft Endpoint Manager, you may encounter policy conflicts where the same setting is configured both on-premises via GPO and Intune. When this happens it can be a complete nightmare, so in this post I will show you how to identify GPOS not supported by MDM.
If you are a regular visitor to my blog you will know of my passion of leverage Power Automate to notify me of the latest happenings within the Microsoft technology space and today post is no different.
Today, I am going to publish Microsoft events into Microsoft Teams and because we are using Power Automate. You are not just limited to publishing into Teams but you could even send an email, update a SharePoint list etc..
So first of all I have created a new Channel within my Organisation Wide Announcements Team as shown below.
We will open Power Automate and configure the required flow to publish the below into Microsoft Teams.
Launch Power Automate Click Create –> Automated Cloud Flow
Provide a Flow Name i.e (Microsoft Event RSS Push) Select “When a feed item is published”
Enter the RSS feed url “https://events.microsoft.com/eventrss.xml”
Select PublishDate Click New Step
Search for Microsoft Teams Connector Select Post a message (V3)
Specify your Team and Channel Populate your Subject with the Feed title Populate your Message with Primary feed link and Feed Summary.
When the first run happens it will flood the channel with all current active events but after this point you will receive a steady flow of events.
When integrating your Windows 10 devices into Microsoft Endpoint Manager, you may encounter policy conflicts where the same setting is configured both on-premises via GPO and Intune. When this happens it can be a complete nightmare, so in this post I will show you how to configure Microsoft Endpoint Manager so that your MDM policies rein over GPO.
Lets get to it and launch Microsoft Endpoint Manager dashboard –> Go to Devices –> Configuration Profile –> Create Profile
Platform – Windows 10 and later Profile – Custom
Click Add and enter the below
Name: ConflictPolicyConflict Description: Enter value if required OMA-URI: ./Device/Vendor/MSFT/Policy/Config/ControlPolicyConflict/MDMWinsOverGP Data type: Integer Value: 1
Click Save –> Press Next
If you are using Scope Tags – Define your tags and Press Next
Define your selected groups of machines for the profile and Press Next
Define applicability rules if in use and Press Next
This will now force MDM Policies to win over Group Policies assigned to a Windows 10 device.