By default remote management on Windows Server 2012 Core can be blocked by firewall.
In order to enable this functionality, issue following command from Command Prompt window:
Netsh.exe firewall set service remoteadmin enable ALL
Once it’s done you should be able to manage server remotely.
Handful list of parameters possible to use in CMD scripts:
%~I - expands %I removing any surrounding quotes ("")
%~fI - expands %I to a fully qualified path name
%~dI - expands %I to a drive letter only
%~pI - expands %I to a path only
%~nI - expands %I to a file name only
%~xI - expands %I to a file extension only
%~sI - expanded path contains short names only
%~aI - expands %I to file attributes of file
%~tI - expands %I to date/time of file
%~zI - expands %I to size of file
%~$PATH:I - searches the directories listed in the PATH
environment variable and expands %I to the
fully qualified name of the first one found.
If the environment variable name is not
defined or the file is not found by the
search, then this modifier expands to the
empty string
%~1 - expands %1 removing any surrounding quotes (")
%~f1 - expands %1 to a fully qualified path name
%~d1 - expands %1 to a drive letter only
%~p1 - expands %1 to a path only
%~n1 - expands %1 to a file name only
%~x1 - expands %1 to a file extension only
%~s1 - expanded path contains short names only
%~a1 - expands %1 to file attributes
%~t1 - expands %1 to date/time of file
%~z1 - expands %1 to size of file
%~$PATH:1 - searches the directories listed in the PATH
environment variable and expands %1 to the fully
qualified name of the first one found. If the
environment variable name is not defined or the
file is not found by the search, then this
modifier expands to the empty string
%~dp1 - expands %1 to a drive letter and path only
%~nx1 - expands %1 to a file name and extension only
%~dp$PATH:1 - searches the directories listed in the PATH
environment variable for %1 and expands to the
drive letter and path of the first one found.
%~ftza1 - expands %1 to a DIR like output line
Very useful for automated software installations for example.
If you need to identify your public IP and have no possibility to run web browser of any kind you can use telnet.
In order to identify public IPv4:
telnet v4address.com
In order to identify public IPv6:
telnet v6address.com
Once connection is established autoresponder will show your public IP address:
This is the telnet autoresponder at v6address.com. You have connected over IPv4. Your IP address is 5.10.15.20
This might be helpful when using console on some *NIX systems or on the routers.
Quick reference with screenshots and requirements for System Center 2012 SP1 Service Manager installation.
After installing Windows Hyper-V 2012 sometimes there might be some issues with remote management (even if enabled via sconfig).
In that case few firewall rules might have to be enabled on Hyper-V machine using PowerShell:
Quick steps which should be done as pre-migration steps when you want to migrate System Center Configuration Manager 2007 R2 to System Center 2012 SP1 Configuration Manager.
Diagram below shows schematics of the lab environment prepared for migration testing.
