Mar 31 2021 07:50 AM
Mar 31 2021 07:50 AM
2 days ago I installed WAC on my desktop Win 10 (1909). I was using Edge and added just a couple servers to monitor while I test this product. This morning I fired it up in Edge and right after I see the short list of Servers followed with the following error:
Apr 01 2021 09:20 AM
Apr 05 2021 07:11 AM
Apr 06 2021 06:06 AM
Exact same thing here. Incredibly frustrating to actually see it starting correctly, then after a second or two it changes its mind and says Access denied. Now I am left with nothing working, old version can't be installed either after uninstalling this new version. Well done MS. @ImNotBob
Apr 06 2021 07:08 AM
Apr 06 2021 08:34 AM
So I managed to solve it with some trickery! My setup is btw a Windows 10 computer, joined to domain. What I did was make my useraccount a member of the local admin group, restarted my computer, and then installed with my normal useraccount, not the domain admin account I also have. Now I could start WAC by simply doubleclicking the shortcut on the desktop, select the correct certificate and then it works. MS has made a mess of this installation, seems they seem to think we are all local admins on our computers. Elevating with another account screws everything up. Still have not tried removing my local admin membership on the computer, it might break again when I do. I'm going to use the storage migration tool so I can live with adding my account to local admins when I use that in a couple of days, but it is not pretty. Hope anyone from MS reads this thread.....Fix an installer that isn't broken please! @ImNotBob
Apr 06 2021 08:50 AM
Apr 06 2021 11:05 AM
Greetings, then you will be happy to hear that I have now verified that after installing like I described in my previous post, removing your non-admin account from local admins on the pc and rebooting will not break the WAC. It works like it is supposed to without being admin. Just required during installation.@--BF--
Apr 12 2021 02:06 PM
Same issues here. When I login as my admin user account it works fine but as a non admin on the WAC server (2016 Server Core) I get the permission denied error and it asks for credentials to Localhost.
Apr 15 2021 06:03 PM - edited Apr 15 2021 07:13 PM
@ImNotBob @Deargubel @NebulousBurrito @AndreasM1976 @--BF-- @Antonio_Filho @TinklemyFinkle Thanks for reporting folks! The Windows Admin Center team is aware of this issue and are investigating right now! Will update this thread and Twitter (@servermgmt) as soon as we have a workaround or a new update available.
Apr 19 2021 04:02 AM
It looks like when running with a standard user account it does not have rights to make updates to the admin center as there seems to be some extensions that need to be updated.
To fix this problem, open up the console from a location that you can log in with an account that either has domain admin rights or admin rights on the server that is hosting the admin center. It will then do all the updates to the extensions needed. Once done, and it has reloaded, you can then open up the console on your normal desktop and should all start working again.
Apr 19 2021 11:47 AM
Did as you suggested and it seems to be ok now.
Very odd behavior. One would think that launching WAC with a prv account that has local admins would solve this like any other product.
Thanks everyone for feedback and workaround.
Apr 21 2021 09:30 AM - edited Apr 21 2021 11:44 AM
Well today is a new day and after firing up WAC, I'm greeting with the same issue again.
Perhaps I'm not looking at this correctly. Having to add my non-prv account to the admin group, log in, run WAC, remove my non-prv account from admin, log out, log back might be a feature?