Share via

Error installing Windows Admin Center 1809

Question

Friday, September 21, 2018 6:10 PM

When trying to install Windows Admin Center 1809, the install process fails with the following error message. Windows 10 Pro is up to date and running 'Import-Module Microsoft.PowerShell.LocalAccounts' does not help.

Unhandled Exception:

System.Management.Automation.CommandNotFoundException The Module 'Microsoft.PowerShell.LocalAccounts' could not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.LocalAccounts'.

All replies (19)

Friday, September 21, 2018 6:17 PM

Hi,

What is your current build of Windows 10?

Best regards,
Leon

Blog: https://thesystemcenterblog.com LinkedIn:

Friday, September 21, 2018 7:36 PM

Microsoft Windows [Version 10.0.17134.286]

Friday, September 21, 2018 8:35 PM

Tested in my lab on Windows 10 Professional (10.0.17134.286) and Windows 10 Enterprise (10.0.17134.286) and the installation was successful.

How did you try to install it? Did you try "Run as administrator"?

Also try disabling the firewall or antivirus (if installed)?

Blog: https://thesystemcenterblog.com LinkedIn:

Friday, September 21, 2018 8:54 PM | 1 vote

Running as admin and through an elevated cmd window failed.

Same results when turning all antivirus & firewalls off.

Still getting the same error.

Saturday, September 22, 2018 8:14 PM

Same here, but on 18242. Since you're on 17134, there goes my theory that it's the Windows build.

If you can scare up the previous release of WAC, it would be interesting to see if it also bombs out.

Monday, September 24, 2018 2:47 AM

Please refer check this Microsoft doc for some information about Windows Admin Center Known Issues

/en-us/windows-server/manage/windows-admin-center/use/known-issues#installer

When you install Windows Admin Center on Windows 10, it uses port 6516 by default, but you have the option to specify a different port. You can also create a desktop shortcut and let Windows Admin Center manage your TrustedHosts.

Note:

Modifying TrustedHosts is required in a workgroup environment, or when using local administrator credentials in a domain. If you choose to forego this setting, you must configure TrustedHosts manually.

Regards

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Monday, September 24, 2018 2:51 AM

I was referring to the Windows builds, not the ports...ports have nothing to do with this.

Sunday, September 30, 2018 3:15 AM | 1 vote

Hi There,

I had the same problem installing Windows Admin Center version 1809 but no problems at all with version 1804.25. 

The only way I was able to install version 1809 was running the following command: 

msiexec /i <WindowsAdminCenterInstallerName>.msi /qn /L*v log.txt SME_PORT=<port> SME_THUMBPRINT=<thumbprint> SSL_CERTIFICATE_OPTION=installed

The installation completed without rolling back and now I am able to launch version 1809.

The command was taken from the following link (in the "Install on Server Core" section)

https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/deploy/install

I hope this work for those of you having the same problem.

Sunday, September 30, 2018 3:51 AM

Good idea. Not sure you intended to reference the one ending in =installed rather than =generate though.

Anything else you had to do to get the site to actually work post install?  I've accounted for port (6516), WinRM service being started, and TrustedHosts allowing the PC. But https://localhost:6516 behaves as if the site isn't there, which it might not be, because it's unclear what to check to know if it's actually started.

Wednesday, October 3, 2018 1:45 PM | 4 votes

+ the fastest solution would be to edit the PSModulePath under 'Environment Variable' -> 'User Variable' 

  • add the path 'C:\Windows\System32\WindowsPowerShell\v1.0\Modules' and move it to the top
  • a logoff/login might be required  OR open a new CMD with elevated rights and run the installer from there

Wednesday, October 3, 2018 9:05 PM

Yes, that worked to allow the install of Admin Center. What was there previously, and there was just one line, pertained to the SharePoint PNP PowerShell module. It's now secondary (and still works).

The line you mentioned is apparently some new dependency for the Admin Center installer.

As for actually getting the Admin Center to open, still ERR_CONNECTION_REFUSED despite seemingly everything being accounted for, but that's for a different thread if I can't figure it out.

Wednesday, October 3, 2018 9:09 PM

Does this issue also occur on the newest Windows 10 1809 (Build 17763.1) ?

Blog: https://thesystemcenterblog.com LinkedIn:

Wednesday, October 3, 2018 9:13 PM

I think I was still on that build when first encountering the problem, but I'm currently on the 18xxx builds.

There's probably a good chance that it happens on any build if you don't happen to have the line ioan.c mentioned in place, but I haven't tested that theory. I don't think it's an issue with Windows per se, just interference from other PS modules.

Wednesday, October 3, 2018 9:22 PM

Most likely some interference with other PS modules yeah, I haven't been able to replicate this problem on any Windows 10 build so far.

This issue should be reported here:

https://windowsserver.uservoice.com/forums/295071-management-tools

Blog: https://thesystemcenterblog.com LinkedIn:

Wednesday, October 3, 2018 9:26 PM

Even when you remove the line ioan.c mentioned (and then either log off/on, reboot, or run from a new admin CMD)?  If so, that's VERY puzzling, since that alone seems to make the difference here.

Wednesday, October 3, 2018 9:39 PM

Removing the "C:\Windows\System32\WindowsPowerShell\v1.0\Modules" path didn't make any difference, the installation is still successful without any issues.

Blog: https://thesystemcenterblog.com LinkedIn:

Wednesday, October 3, 2018 10:00 PM

OK, it's not the absence of the line but the presence of another. In my case:

%localappdata%\Apps\SharePointPnPPowerShellOnline

That directory doesn't have to exist to trigger the problem. I just tested that in a fresh 1809 by setting it and then opening a new admin CMD and trying the install.

Wednesday, December 26, 2018 1:46 PM

+ the fastest solution would be to edit the PSModulePath under 'Environment Variable' -> 'User Variable' 

  • add the path 'C:\Windows\System32\WindowsPowerShell\v1.0\Modules' and move it to the top
  • a logoff/login might be required  OR open a new CMD with elevated rights and run the installer from there

Worked like a charm, thank you. 

Wednesday, December 26, 2018 5:41 PM

+ the fastest solution would be to edit the PSModulePath under 'Environment Variable' -> 'User Variable' 

  • add the path 'C:\Windows\System32\WindowsPowerShell\v1.0\Modules' and move it to the top
  • a logoff/login might be required  OR open a new CMD with elevated rights and run the installer from there

This one worked for me (latest version of both Windows and WAC). Thanks!