windows server 2012 remote management from windows 8

Forums › Microsoft Windows › windows server 2012 remote management from windows 8

hamish225

1418 posts

Uber Geek

ID Verified

#129345 11-Sep-2013 22:19

Hi, so i'd like to remotely manage my server from my desktop, i can do this via remote desktop connection but i would like to see it working via the remote server administration tools app on windows 8.

I've installed it and managed to get it running, but now when i add the server to the list of servers i want to manage it comes up with an error that looks like this

i found some pages on google that suggest i run this command "Set-Item wsman:\localhost\Client\TrustedHosts [COMPUTERNAME] -Concatenate -Force"

I tried that and it made no difference, just to be sure i ran it on both the server and my desktop, still not working. haaaalp

just to note the server has a GUI since i've got no idea how a command prompt works beyond doing pings and tracerts

*Insert big spe*dtest result here*

nathan

5695 posts

Uber Geek
Inactive user

#894508 11-Sep-2013 22:32

Are you on the same network and domain etc?

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Note that to use Quic Broadband you must be comfortable with configuring your own router.

hamish225

1418 posts

Uber Geek

ID Verified

#894511 11-Sep-2013 22:41

nathan: Are you on the same network and domain etc?

there is no domain, just workgroup. all the computers on my network are on 'workgroup' all on the same ip range (192.168.1.xxx)

*Insert big spe*dtest result here*

nathan

5695 posts

Uber Geek
Inactive user

#894515 11-Sep-2013 22:47

To add remote workgroup servers to Server Manager

1.On the computer that is running Server Manager, add the workgroup server name to the TrustedHosts list. This is a requirement of NTLM authentication. To add a computer name to an existing list of trusted hosts, add the Concatenate parameter to the command. For example, to add the Server01 computer to an existing list of trusted hosts, use the following command.

Copy

Set-Item wsman:\localhost\Client\TrustedHosts Server01 -Concatenate -Force

2.Determine whether the workgroup server that you want to manage is in the same subnet as the computer on which you are running Server Manager.

If the two computers are in the same subnet, or if the workgroup server’s network profile is set to Private in the Network and Sharing Center, go on to the next step.

If they are not in the same subnet, or if the workgroup server’s network profile is not set to Private, on the workgroup server, change the inbound Windows Remote Management (HTTP-In) setting in Windows Firewall to explicitly allow connections from remote computers by adding the computer names on the Computers tab of the setting’s Properties dialog box.

3.

securitySecurity Note

Running the cmdlet in this step overrides User Account Control (UAC) measures that prevent elevated processes from running on workgroup computers unless the built-in Administrator or the System account is running the processes. The cmdlet lets members of the Administrators group manage the workgroup server without logging on as the built-in Administrator. Allowing additional users to manage the workgroup server can reduce its security; however, this is more secure than providing built-in Administrator account credentials to what might be multiple people who are managing the workgroup server.

To override UAC restrictions on running elevated processes on workgroup computers, create a registry entry called LocalAccountTokenFilterPolicy on the workgroup server by running the following cmdlet.

Copy

New-ItemProperty -Name LocalAccountTokenFilterPolicy -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -propertyType DWord -value 1

4.On the computer on which you are running Server Manager, open the All Servers page.

5.If the computer that is running Server Manager and the target workgroup server are in the same workgroup, skip to the last step. If the two computers are not in the same workgroup, right-click the target workgroup server in the Servers tile, and then click Manage as.

6.Log on to the workgroup server by using the built-in Administrator account for the workgroup server.

7.Verify that Server Manager is able to connect to and collect data from the workgroup server by refreshing the All Servers page, and then viewing the manageability status for the workgroup server.

To add remote servers when Server Manager is running on a workgroup computer

1.On the computer that is running Server Manager, add remote servers to the local computer’s TrustedHosts list in a Windows PowerShell session. To add a computer name to an existing list of trusted hosts, add the Concatenate parameter to the command. For example, to add the Server01 computer to an existing list of trusted hosts, use the following command.

Copy

Set-Item wsman:\localhost\Client\TrustedHosts Server01 -Concatenate -Force

2.Determine whether the server that you want to manage is in the same subnet as the workgroup computer on which you are running Server Manager.

If the two computers are in the same subnet, or if the workgroup computer’s network profile is set to

Private in the Network and Sharing Center, go on to the next step.

If they are not in the same subnet, or if the workgroup computer’s network profile is not set to Private, on the workgroup computer that is running Server Manager, change the inbound Windows Remote Management (HTTP-In) setting in Windows Firewall to explicitly allow connections from remote computers by adding the computer names on the Computers tab of the setting’s Properties dialog box.

3.On the computer on which you are running Server Manager, open the All Servers page.

4.Verify that Server Manager is able to connect to and collect data from the remote server by refreshing the All Servers page, and then viewing the manageability status for the remote server. If the Servers tile still displays a manageability error for the remote server, go on to the next step.

5.Log off of the computer on which you are running Server Manager, and then log on again by using the built-in Administrator account. Repeat the preceding step, to verify that Server Manager is able to connect to and collect data from the remote server.

If you have followed the procedures in this section, and you continue to have problems managing workgroup computers, or managing other computers from workgroup computers, see about_Remote_Troubleshooting on the Microsoft website

nathan

5695 posts

Uber Geek
Inactive user

#894516 11-Sep-2013 22:49

hamish225: Hi, so i'd like to remotely manage my server from my desktop, i can do this via remote desktop connection but i would like to see it working via the remote server administration tools app on windows 8.

I've installed it and managed to get it running, but now when i add the server to the list of servers i want to manage it comes up with an error that looks like this
i found some pages on google that suggest i run this command "Set-Item wsman:\localhost\Client\TrustedHosts [COMPUTERNAME] -Concatenate -Force"

I tried that and it made no difference, just to be sure i ran it on both the server and my desktop, still not working. haaaalp

just to note the server has a GUI since i've got no idea how a command prompt works beyond doing pings and tracerts

also, can you ping the name and it resolves OK? Did you try the IP address instead of [COMPUTERNAME] above?

hamish225

1418 posts

Uber Geek

ID Verified

#894520 11-Sep-2013 23:08

nathan:
hamish225: Hi, so i'd like to remotely manage my server from my desktop, i can do this via remote desktop connection but i would like to see it working via the remote server administration tools app on windows 8.

I've installed it and managed to get it running, but now when i add the server to the list of servers i want to manage it comes up with an error that looks like this
i found some pages on google that suggest i run this command "Set-Item wsman:\localhost\Client\TrustedHosts [COMPUTERNAME] -Concatenate -Force"

I tried that and it made no difference, just to be sure i ran it on both the server and my desktop, still not working. haaaalp

just to note the server has a GUI since i've got no idea how a command prompt works beyond doing pings and tracerts

also, can you ping the name and it resolves OK? Did you try the IP address instead of [COMPUTERNAME] above?

followed those instructions again and for some reason it worked this time, i have no clue what i did wrong last time maybe i entered the computer name wrong but it works now!

*Insert big spe*dtest result here*