What should you do for server core so it can be managed from another server 2012 R2?

What should you do for server core so it can be managed from another server 2012 R2?

What should you do for server core so it can be managed from another server 2012 R2?

A.
1

B.
2

C.
3

D.
4

E.
5

F.
6

G.
7

H.
8

I.
9

J.
10
K.
11
L.
12
M.
13
N.
14
O.
15

Explanation:
You should join the server to the domain first. You can add workgroup servers to Server Manager on
a domain joined server, however, you must first add the workgroup computer to the Trusted Hosts
list using “Set-Item wsman:\\localhost\\Client\\TrustedHostsWorkgroupServerName -Concatenate –
Force”



Leave a Reply 5

Your email address will not be published. Required fields are marked *

6 − one =


Dave

Dave

Shouldn’t this be H. 8?

Chuck Testa

Chuck Testa

How are you going to join a server to a domain without a valid ip address?… You can’t just assume that is taken care of. 8 imho is correct here.

Patrick

Patrick

A server does not have to be in the same domain to be managed remotely via Server manager. There are a number of things that have to happen, but the first thing is it must be given an IP so that it can be found. Every server build document I have ever seen shows configuring the Network Settings as one of the very first things you do after installing the OS.

Maurizio

Maurizio

I think that ip it’s already given, but reading Technet documentatio

“To manage servers that are running Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008 by using Server Manager in Windows Server 2012 R2, apply the following updates to the older operating systems.

.NET Framework 4.5

Windows Management Framework 4.0. ”
and for this reason I think reply 5