If you are trying to view web pages that contain flash content on Windows Server 2012 r2 then you may find that it does not work. You are then led to a page on the Adobe website tells you that Flash player is already installed on Windows 8 and that you do not need to install it. This post explains how to enable Flash Player on Windows Server 2012.
The page then goes on to provide instructions as to how to enable Flash, this basically consists of:
- Ensuring that the flash player add-on is enabled.
- Checking that Active-X filtering is disabled.
You will probably find that these instructions do not work for you as flash player is not listed in the Internet Explorer Add-ons.
How to install Flash Player on Windows Server 2012 r2
In order to install Flash Player on Windows Server 2012 you need to install the Desktop Experience Feature. To do this, do the following:
- Go into server manager.
- Click add roles and features:
- Press next until you reach the “Features” page.
- Tick the box “Desktop Experience” which is hidden under the “User Interfaces and Infrastructure” feature:
- You will then have to accept the installation of some other features to support the installation of desktop experience
- The features are installed and the server is rebooted:
Or if you prefer, you can install with the simple but so effective Windows Powershell command:
The reason I wanted to have access to Flash Player on this particular server was so that I could access the vSphere Web client, which uses flash. Hope this helps someone.
A recent change in Exchange online seems to have caused a problem with mail enabled public folders receiving messages from people outside of the organisation. It has never been necessary with Office 365/Exchange Online to give create permissions to the anonymous or default users , you could instead set the mail flow settings of the public folder to allow anonymous access.
You may see the following bounce message when sending to a mail enabled public folder:
Delivery has failed to these recipients or groups:
Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery. For more tips to resolve this issue see DSN code 5.7.1 in Exchange Online. If the problem continues contact your help desk.
5.7.1 RESOLVER.RST.AuthRequired; authentication required [Stage: CreateMessage]>’
Of course it is possible and easy to set permissions for the public folder from Outlook to solve this problem, but doing this does not seem to be working for everyone. Some people are reporting success with it, but others not.
Setting the public folder permissions with PowerShell fixes the problem, but I cannot understand why there is a difference.
Setting Offiec 365 Public Folder Permissions with Powershell
In order to fix this problem you have to grant create permissions to anonymous and the default user. The Powershell cmdlet to do this is Add-PublicFolderClientPermission.
After connecting to Office 365 Remote Powershell as described here, you can run the following commands:
Add-PublicFolderClientPermission -identity "\test public folder" -User Anonymous -AccessRights CreateItems
Add-PublicFolderClientPermission -identity "\test public folder" -User Default -AccessRights CreateItems
Once you have added the permission it’s probably best to give it a quick check with:
Get-PublicFolderClientPermission -identity "\test public folder"
Hope this helps.