User Profile
Bruce_McDonald
Copper Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Change local account password and WAC stops working?
Have had WAC (latest release) working perfectly for the last 3 weeks on a newly built Windows 10 ENT 20H2 desktop. I am using WAC to manage a small business workgroup environment. Today - I updated my local account password on this machine - and suddenly WAC can no longer fire up at all. When I click the WAC icon on the start menu - I do get the prompt to select an existing Windows Admin Center client certificate followed by this message in MS Edge (91.0.864.37) " You are not authorized to view this page. If you recently updated Windows Admin Center, you may need to restart your browser, and then refresh the page" No amount of restarting the browser, clearing cache or refreshing the page does anything. I checked the certificate - it appears to be valid with no issues. While I have no idea what my local account password has to do with this - clearly something is bent out of shape. Anyone have any idea what is going on or where I might start to look to adjust my credentials for WAC? EDIT: As much as I did not want to - I see that 2103.2 became available and I had to do a reinstall - looks like that did the trick. But JEEZ - what is the deal here? The reinstall wiped all my machines and I need to redo the whole layout. As an "enterprise" tool - I do not see the point to this tool if you cannot easily export and reimport a machine list - it sure would have come in handy in this case. Cheers BDo the Group Policy templates actually work for stopping/controlling Microsoft Edge Updates?
Hello I am current testing MS Edge for Business with the specific goal of controlling the update cadence for the Stable channel. I want complete control on when these updates are applied and ONLY deploy them in a small business environment via WSUS or ManageEngine Desktop Central. I have downloaded the current policy files for Edge Businessand studied the update attributes and items found here: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-update-policies#updatedefault But I have some serious concerns about the validity of these group policy templates. I have been unable to determine the exact policy combination to get the updates to stop while continuing to allow Edge's default payloads to be enabled (3 Services and 2 scheduled tasks that appear in Task Scheduler) after a standard install OR an update? I have been testing this a lot for weeks now and in a stock install of Edge for Business - either a new install OR an update to an existing install - the installeradds (AND reactivates if disabled)the following services: It also adds (and re-enables if disabled) the following tasks into Task Scheduler as well: MicrosoftEdgeUpdateTaskMachineCore MicrosoftEdgeUpdateTaskMachineUA These 5 items – if present and enabled – would seem to allow Edge to update itself like it would in a consumer environment - by itself - every hour on the hour regardless of any GP that may be enabled., The only way I have found to exert any control over the updates is to set these policies (Via GPEDIT) And then run a standalone PS script that actually DELETES the scheduled tasks and disables two of the three services. But I should not have to do this much work. Q: Does the group policy (Update policy override setting) actually override/stop the activity of these 3 services and 2 tasks? While I always believed that GP should be the law - I am skeptical if these services and tasks are actually taken out of the equation with the GP (Update Policy Override) enabled. And even with all this extra work - if a user goes and opens the "..." menu in the upper right and then choose Settings->Help and Feedback->About Edge - Edge will then attempt update itself here as well - which I also do not want my users to be able to do. Ideally what I really want is this to display if a user attempts to select "About Edge": Appreciate any update on how to completely control the Edge Update cycle and have the system ignore these tasks and services that it places on the machine during each update. Cheers Bruce
