• Status: Solved
  • Priority: Low
  • Security: Public
  • Views: 251
  • Last Modified:

Microsoft Edge GPO on Windows Server 2016

I feel really stupid for not being able to figure this out but I can't seem to get Microsoft Edge GPO configuration as an option on my Windows Server 2016 Domain Controller. Essentially, I want to be able to set the home-page for Microsoft Edge from the Domain Controller, much like I currently do for Internet Explorer, which works without issue.

The problem is I can't seem to get Microsoft Edge as an option in Group Policy on the server at all. Every knowledge base and website I go to tells me to look in Policies -> Admin Templates -> Windows Components and there should be an option for Microsoft Edge. I can find this option on my local Windows 10 machine but it doesn't show up on Windows Server 2016. Am I missing something simple here? It's great that I can set a computer locally to set the Edge homepage but why can't I do it from the server?

Things I've tried:

1) Updated every and all ADMX libraries for Windows Server 2016. Made sure they are current (ADMX files on the server show they are from October of last year.
2) Tried copying the ADMX file for Edge from my computer to the Server. I was afraid this might break something but it didn't do anything.
3) Checked both c:\windows\policydefinitions and c:\program files (x86)\Microsoft Group Policy that to make sure they are updated. The latter shows the folder of Windows 10 Fall Creatures Update 1709.

Attached are two files showing the problem. One is labeled computer is one is labeled server. The computer shows the group policy folder I'm looking for, the server image shows where the GP should be but doesn't show up at all.

The closest I see is Edge UI but those aren't the same items.

Any help would be greatly appreciated.
Computer_example.jpg
Server_example.jpg
0
Tarkisal
Asked:
Tarkisal
1 Solution
 
McKnifeCommented:
Install RSAT on win 10 and use win 10 to manage that gpo.
0
 
TarkisalAuthor Commented:
Thank you, McKnife. I'm assuming it doesn't have Edge because Server 2016 doesn't have Edge. It still seems strange, though. In any case, I will try your suggestion and update the ticket shortly.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: McKnife (https:#a42492795)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now