MCSA Notes 70-740 P2

Manage Windows Server Core Machine

Server Core IP Address: 192.168.1.101

Server Core Hostname: CORE-NUG

Domain Controller IP Address: 192.168.1.100

Domain Controller Hosename: DC-NUG

#Set DNS Configuration on Windows Server Core Machine

Set-DNSClientServerAddress -InterfaceAlias "Ethernet" -ServerAdresses ("192.168.1.100","8.8.8.8")

#Ping Domain

ping nuggetlab.com

#Join Domain (cmd command)

netdom join %computername% /domain:nuggetlab.com /userd:administrator /passwordd:Pa$$w0rd

#Join Domain (powershell)

Add-Computer -Domainname nuggetlab.com

Start Windows Server Manager on DC and Add CORE-NUG

# Enter a powershell session on a remote machine
Enter-PSSession -ComputerName CORE-NUG

# View all available features
Get-WindowsFeature

# Install web server (iis) role and management service
Install-WindowsFeature -Name Web-Server, Web-Mgmt-Service

On DC-NUG Install the IIS Web Management Console

Install-WindowsFeature web-mgmnt-console

CORE-NUG won’t allow Remote Management by default. To activate it we have to set the following powershell command

# Configure remote management for IIS
Set-ItemProperty -Path "HKLM:\Software\Microsoft\WebManagement\Server" -Name "EnableRemoteManagement" -Value 1

# Configure remote managent service to start automatically
Set-Service WMSVC -StartupType Automatic

# Rename CORE-NUG to WEB-NUG
Rename-Computer -NewName WEB-NUG -DomainCredential "nuggetlab\administrator" -Force -Restart

# Exit remote powershell session
Exit-PSSession

Now let’s go over to DC-NUG and start the IIS Manager Console. Now it’s possible to add web-nug and administer it.

We can also check now if the core services for IIS working on WEB-NUG

# Send a command over to a remote machine (powershell remoting – http)
Invoke-Command -ComputerName WEB-NUG -ScriptBlock { Get-Service W3SVC, WMSVC }

# Use the built in computername parameter (windows – dcom)
Get-Service -ComputerName WEB-NUG

Ersten Kommentar schreiben

Antworten

Deine E-Mail-Adresse wird nicht veröffentlicht.


*