Hi,
I would like to have .sap files to be automatically opened instead of download by MS Edge.
I created GPOs:
- AutoOpenAllowedForURLs and entered particular URLs;
- AutoOpenFileTypes and entered: sap
Despite MS Edge policies are applied successfully when I click on the link with with it is asking me to to download it or open.
Is there anything else I can do or I am doing it wrong?
You right click on the file and choose which default program you want to use to open this type of file.
For AutoOpenFileTypes policy, your computer must meet the following conditions:
This policy is available only on Windows instances that are joined to a Microsoft Active Directory domain, Windows 10 Pro or Enterprise instances that enrolled for device management, or macOS instances that are that are managed via MDM or joined to a domain via MCX.
If your computer doesn't meet the above conditions, this policy can't be applied. You can also go to edge://policy/ in Edge to see if the policies are applied successfully.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Regards,
Yu Zhou
Hi Yu Zhou,
for clarification - there is not a problem if GPO is applied because as you mentioned computer is domain joined and I can see on edge policy is applied successfully:
The problem is - despite it is applied it is downloading .sap files automatically and asking to open it instead of automatically open them
.sap file needs specific program to open it. Do you install any program to open .sap file? If not, you need to install one and set it as the default program to open .sap files. After that, you can test again to see if it can achieve your demands.
Hi,
yes, it is installed and .sap extension is associated with it and it opens manually when I click open on Edge - but not automatically open.
Hi,
found the cause - it was in the form of url I typed - there was particular port and some subfolders which shouldn't be included in the policy.
Amended with FQDN only and it works fine now.
Thanks for help Yu Zhou!
13 people are following this question.
