Ir al contenido

Remote Administration Configuration in Workgroup Environments

Establishing WinRM connection policies, CredSSP authentication, and bypassing local UAC policies for managing Server Core in a Workgroup.

0views

Managing a headless server (without a graphical interface) such as Windows Server Core requires enabling secure remote communication channels. In corporate environments where the client is integrated into Microsoft Entra ID (Azure AD) and the server resides in an isolated Workgroup, it is necessary to circumvent the lack of Kerberos authentication through strict trust and identity delegation policies.


1. Hardening and Opening on the SERVER (w-server-2022)

Sección titulada «1. Endurecimiento y Apertura en el SERVIDOR (w-server-2022)»

The following commands must be executed remotely via the virtual machine's physical console or through local SSH as Administrator:

By default, Windows Server usually maps network cards in “Public” mode, forcing the local firewall to immediately block any traffic from DCOM, RPC, or WinRM. It is mandatory to redefine the interface as “Private”:

Ventana de terminal
# 1. Comprobar el perfil activo y tomar nota del InterfaceIndex
Get-NetConnectionProfile
# 2. Modificar la categoría de red (Reemplaza el valor de X por tu InterfaceIndex)
Set-NetConnectionProfile -InterfaceIndex X -NetworkCategory Private

B. Initialize and Configure WinRM (Windows Remote Management)

Sección titulada «B. Inicializar y Configurar WinRM (Windows Remote Management)»

Starts the native PowerShell remote management service and automatically creates listeners in the firewall:

Ventana de terminal
Enable-PSRemoting -Force

Allows the server to accept advanced delegated credentials from the administration client, which are indispensable for installing drivers or interacting with low-level printing APIs:

Ventana de terminal
Enable-WSManCredSSP -Role Server

In local networks without a local corporate domain, Windows blocks elevated administrator tokens for connections coming from external local SAM accounts over the network. Disable this restriction by modifying the local registry:

Ventana de terminal
New-ItemProperty -Name LocalAccountTokenFilterPolicy -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Value 1 -PropertyType DWord -Force

Run the following commands by opening Windows PowerShell as Administrator on your local machine:

Since we do not have a local domain controller to audit the remote server's identity via Kerberos, the client must explicitly trust the target host to establish the encrypted channel:

Ventana de terminal
winrm set winrm/config/client '@{TrustedHosts="w-server-2022,192.168.10.10,w-server-2022.local"}'

Enable secure delegation of the local identity token to allow it to be injected into the remote server during the installation process:

Ventana de terminal
Enable-WSManCredSSP -Role Client -DelegateComputer "w-server-2022.local"

Method 1: Remote Connection via PowerShell (Command Line)

Sección titulada «Método 1: Conexión Remota en PowerShell (Línea de Comandos)»

It is the most direct, agile, and clean way to manage the operating system:

Ventana de terminal
# Iniciar sesión remota ingresando credenciales seguras interactivos
Enter-PSSession -ComputerName 192.168.10.10 -Credential (Get-Credential)
# Sintaxis de credenciales a usar en el diálogo emergente:
# Usuario: w-server-2022\usuario.demo

If you attempt to connect the classic “Print Management” GUI from your Azure AD-integrated workstation, the system will attempt to authenticate with your Microsoft 365 token, immediately throwing an Access denied error.

To force the GUI to communicate using the local SAM credentials of the print server, run the following command in your PC's CMD console:

Ventana de terminal
runas /netonly /user:w-server-2022\usuario.demo "mmc printmanagement.msc"

This command will launch the GUI by loading the local server administrator token directly into the network stack, allowing you to manage printers with complete ease.