Thomas Maurer (tm) » Windows Server 2008 R2

List of Hyper-V and Cluster Hotfixes for Windows Server 2008 R2

Thomas Maurer — Wed, 08 Feb 2012 17:41:29 +0000

Recently I posted about a page in the TechNet Wiki which lists a lot of Hyper-V tools. Yesterday on Hyper-V workshop, Michel Lüscher mentioned two lists in the TechNet Wiki where you can find Hyper-V and Cluster Hotfixes for Windows Server 2008 R2.

List of Hyper-V Hotfixes for Windows Server 2008 R2 (TechNet Wiki):

http://social.technet.microsoft.com/wiki/contents/articles/1349.hyper-v-update-list-for-windows-server-2008-r2.aspx

List of Cluster Hotfixes for Windows Server 2008 R2 (TechNet Wiki):

http://social.technet.microsoft.com/wiki/contents/articles/2008.list-of-cluster-hotfixes-for-windows-server-2008-r2.aspx

TechNet Wiki: Hyper-V Tool Collection

Thomas Maurer — Mon, 06 Feb 2012 19:10:45 +0000

Microsoft and the community are really starting to work with the TechNet Wiki platform. Now thanks to James van den Berg I found a great wiki page with a collection of Hyper-V tools.

The collection includes a list of the following content:

Supported Microsoft Tools (Solution Accelerators, Product Downloads, etc.)
Microsoft Products and Solutions that are Built upon Hyper-V Technology
Remote Management from Client Versions of Windows
Unsupported Microsoft Tools (Sysinternals, MSDN/ScriptCenter Code Galleries, TechNet/MSDN Blogs)
Community Tools (CodePlex and blogs)
Third-party Free Tools
Hardware-Specific Tools from OEMs and Vendors
Partner Solutions (Commercially Available)
Application-specific Performance Planning/Testing/Analysis tools

You can find also a lot of other interessting content on the TechNet Wiki. For example for Exchange, PowerShell and SQL.

Enable RSAT on Windows Server 2008 R2 for Hyper-V

Thomas Maurer — Mon, 19 Dec 2011 15:32:38 +0000

With the Remote Server Administration Tools (RSAT) you can administrate the Server with remote consoles. Now you can download the Remote Server Administration Tools for Windows 7, but if you are on Windows Server 2008 R2 you can just enable the tools per ServerManagerCmd.exe.


ServerManagerCmd -install RSAT-Hyper-V
ServerManagerCmd -install RSAT-Clustering

Automated Active Directory Deployment with PowerShell

Thomas Maurer — Mon, 12 Dec 2011 19:06:08 +0000

For a small presentation at KTSI I created a PowerShell script will automatically will deploys Active Directory Servers, adds other member servers, creates Organization Units and adds users via Powershell Remoting. As source there is a XML configuration file and CSV files for User Data.

This script is just for Lab deployments not for production, and it is not perfect, but I think maybe some people will enhance this script with their own code.

I do not support this script. it is just something I need to deploy my test environments and nothing more. More it shows diffrent

You can find more information about it works in this document.

XML Config file:

The PowerShell Script:


 

# ---------------------------------------------------------------------------------------------- #

# Powershell AD Creator $Rev: 748 $

# (c) 2011 Thomas Maurer. All rights reserved.

# created by Thomas Maurer

# last Update by $Author: tmaurer $ on $Date: 2010-11-22 14:07:36 +0100 (Mo, 04 Nov 2011) $

# ---------------------------------------------------------------------------------------------- #

 

 

# Set Debug Mode (true/false)

$DebugOn = $false

 

 

 

#region [INFO BLOCK]

# INFO

Write-Host " " -BackgroundColor Black -ForegroundColor White

Write-Host "PowerShell AD Deplyoment" -BackgroundColor Black -ForegroundColor White

Write-Host " " -BackgroundColor Black -ForegroundColor White

Write-Host "Enter Credentials for Remote System:" -BackgroundColor Black -ForegroundColor White

#endregion

 

 

#region [VERBOSE BLOCK]

# Verbose Loop

 

if ($DebugOn -eq $true){

#Debug

Clear-Host

Write-Host "Debug mode on" -BackgroundColor Red -ForegroundColor White

$VerbosePreference = "Continue"

}

else {

#NoDebug

Clear-Host

$VerbosePreference = "SilentlyContinue"

}

#endregion

 

#region [CONFIG BLOCK]

# Get XML Information and create some funny objects...

[Xml]$global:xmlData = get-content ".\config.xml"

 

# Get Credentials for Remotesystems

$cred = Get-Credential

 

$global:xmlServer01 = $xmlData.lab.config.servers.server | Where-Object { $_.id -eq "1"}

$global:xmlServer02 = $xmlData.lab.config.servers.server | Where-Object { $_.id -eq "2"}

$global:xmlDomain = $xmlData.lab.config.ad.domain

$global:xmlOUS = $xmlData.lab.config.ous

 

#endregion

 

#region [FUNCTION BLOCK]

 

function ConvertTo-Scriptblock {

<#

Function to Convert a String into a Script Block

#>

Param(

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$string

)

Begin {

Write-Verbose "Starting Begin Section"

}

Process {

Write-Verbose "Starting Process Section"

try {

Write-Verbose "Convert String to Scriptblock"

$sb = [scriptblock]::Create($string)

return $sb

}

catch {

Write-Host "Could not convert String to Scriptblock" $Error[0]

 

}

}

End {

Write-Verbose "Starting End Section"

}

}

 

 

function Enable-ICMP {

<#

Function to enable ICMP

 

Enable-ICMP -hostip $xmlServer01.ip

#>

Param(

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$hostip

)

begin {

# Write Command

$step001 = @"

netsh firewall set icmpsetting 8

"@

}

process {

try {

# Run Scriptblock

Write-Host "Enable ICMP on " $hostip "..." -BackgroundColor Black -ForegroundColor White

 

Invoke-Command -ComputerName $hostip -ScriptBlock (ConvertTo-Scriptblock -String $step001) -Credential $cred

Write-Host "ICMP successfully enabled..." -BackgroundColor Green -ForegroundColor Black

 

 

}

catch {

# Sending status to CP and EventLog

throw "ERROR: Could not enable ICMP"

}

}

end {

# Cleanup

$step001 = $null

}

}

 

 

 

function Create-ADServer {

<#

Function to Create AD on the first Server

#>

begin {

# Prepair for First AD Server

Write-Host "Preparing Script Block for " + $xmlServer01.name + "..." -BackgroundColor Black -ForegroundColor White

$domainName = $xmldomain.name

$domainNetBiosName = $xmldomain.netbiosname

$domainForestLevel = $xmldomain.forestlevel

$domainDomainLevel = $xmldomain.domainlevel

$domainSafemodePW = $xmldomain.safemodepw

$adTempFolder = "temp4"

$adTempPath = "C:\" + $adTempFolder

$adFilePath = $adTempPath + "\adinstall.txt"

}

process {

try {

# Script Block for First AD Server

$step001 = @"

New-Item -ItemType directory $adTempPath

New-Item -ItemType file $adFilePath

Add-Content $adFilePath "[DCINSTALL]"

Add-Content $adFilePath "InstallDNS=yes"

Add-Content $adFilePath "NewDomain=forest"

Add-Content $adFilePath "NewDomainDNSName=$domainName"

Add-Content $adFilePath "DomainNetBiosName=$domainNetBiosName"

Add-Content $adFilePath "ReplicaOrNewDomain=domain"

Add-Content $adFilePath "ForestLevel=$domainForestLevel"

Add-Content $adFilePath "DomainLevel=$domainDomainLevel"

Add-Content $adFilePath "RebootOnCompletion=yes"

Add-Content $adFilePath "SafeModeAdminPassword=$domainSafemodePW"

Write-Host "Unattend File created successfully..." - -BackgroundColor Green

dcpromo /unattend:$adFilePath

"@

# Run Scriptblock

Write-Host "Configure " $xmlServer01 "..." -BackgroundColor Black -ForegroundColor White

Invoke-Command -ComputerName $xmlServer01.ip -ScriptBlock (ConvertTo-Scriptblock -String $step001) -Credential $cred

Write-Host "Configuration for " $xmlServer01.name " successfully..." -BackgroundColor Green -ForegroundColor Black

}

catch {

# Sending status to CP and EventLog

throw "ERROR: Could not Create AD"

}

}

end {

# Cleanup

$step001 = $null

}

}

 

function Join-AD {

<#

Function to add second AD Server

 

Join-AD -hostname $xmlServer02.name -hostip $xmlServer02.ip -dnsip $xmlServer01.ip -domainName $xmldomain.name -adminpw $xmlServer01.adminpw

 

#>

Param(

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$hostname,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$hostip,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$dnsip,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$domainName,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$adminpw

)

begin {

# Prepair for Second AD Server

}

process {

try {

# Script Block join AD

$step001 = @"

netsh interface ipv4 add dnsserver name="Local Area Connection" address=$dnsip index=1

netdom join $hostname /domain:"$domainName" /userd:administrator /passwordd:$adminpw /REBoot

"@

 

# Run Scriptblock

Write-Host "Adding " $hostname " to domain..." -BackgroundColor Black -ForegroundColor White

 

Invoke-Command -ComputerName $hostip -ScriptBlock (ConvertTo-Scriptblock -String $step001) -Credential $cred

Write-Host "Domainjoin for " $hostname " successfully..." -BackgroundColor Green -ForegroundColor Black

 

 

}

catch {

# Sending status to CP and EventLog

throw "ERROR: Could not add System to AD"

}

}

end {

# Cleanup

$step001 = $null

}

}

 

function Add-ADServer {

<#

Function to add a second AD to the Domain

#>

begin {

# Prepair for First AD Server

Write-Host "Preparing Script Block for DCPROMO " $xmlServer02.name "..." -BackgroundColor Black -ForegroundColor White

$server01ip = $xmlServer01.ip

$domainName = $xmldomain.name

$server01pw = $xmlServer01.adminpw

$domainSafemodePW = $xmldomain.safemodepw

}

process {

try {

# Script Block for First AD Server

$step001 = @"

Dcpromo /unattend /replicaOrnewDomain:replica /replicaDomainDNSName:$domainName /ConfirmGC:yes /username:administrator /Password:$server01pw /safeModeAdminPassword:$domainSafemodePW

"@

# Run Scriptblock

Write-Host "Running DCPROMO " $xmlServer02.name "..." -BackgroundColor Black -ForegroundColor White

Invoke-Command -ComputerName $xmlServer02.ip -ScriptBlock (ConvertTo-Scriptblock -String $step001) -Credential $cred

Write-Host "DCPROMO " $xmlServer02.name " successfully..." -BackgroundColor Green -ForegroundColor Black

}

catch {

throw "ERROR: Could not add Second Server to AD"

}

}

end {

# Cleanup

$step001 = $null

}

}

 

function Add-ADOU {

<#

Function to add OU to AD

 

Add-ADOU -hostip $xmlServer01.ip -name $namedings -path $pathdings

 

#>

Param(

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$hostip,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$name,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$path

)

begin {

# Prepair for Second AD Server

}

process {

try {

# Script Block join AD

$step001 = @"

Import-Module ActiveDirectory

New-ADOrganizationalUnit -name "$name" -Path "$path"

"@

 

# Run Scriptblock

Write-Host "Adding OU " $name " to " $path "..." -BackgroundColor Black -ForegroundColor White

 

Invoke-Command -ComputerName $hostip -ScriptBlock (ConvertTo-Scriptblock -String $step001) -Credential $cred

Write-Host "OU added " $name " successfully..." -BackgroundColor Green -ForegroundColor Black

}

catch {

# Sending status to CP and EventLog

throw "ERROR: Could not add OU to AD"

}

}

end {

# Cleanup

$step001 = $null

}

}

 

function Add-UsersfromFile {

<#

Function to add OU to AD

 

Add-UsersfromFile -hostip $xmlServer01.ip -filename $xmlData.lab.config.users.file.name -path $xmlData.lab.config.users.file.path

 

#>

Param(

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$hostip,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$SamAccountName,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$UserPrincipalName,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$name,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$DisplayName,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$GivenName,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$SurName,

[Parameter(

Mandatory = $false,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$Manager,

[Parameter(

Mandatory = $false,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$Department,

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$path

)

begin {

 

}

process {

try {

# Script Block join AD

$step001 = @"

Import-Module ActiveDirectory

New-ADUser -SamAccountName $SamAccountName -UserPrincipalName $userprinicpalname -DisplayName $displayname -GivenName $GivenName -SurName $SurName -Path "$path" -AccountPassword (ConvertTo-SecureString "test41;" -AsPlainText -force)

"@

 

# Run Scriptblock

Write-Host "Adding Users " $userprinicpalname " to " $path "..." -BackgroundColor Black -ForegroundColor White

 

Invoke-Command -ComputerName $hostip -ScriptBlock (ConvertTo-Scriptblock -String $step001) -Credential $cred

Write-Host "Users " $userprinicpalname " added successfully..." -BackgroundColor Green -ForegroundColor Black

}

catch {

# Sending status to CP and EventLog

throw "ERROR: Could not add Users to AD"

}

}

end {

# Cleanup

$step001 = $null

}

}

 

 

function WaitFor-Host {

<#

Function to wait for Host after Reboot

 

WaitFor-Host -hostip $xmlServer01.ip -service servicename

 

#>

Param(

[Parameter(

Mandatory = $true,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$hostip,

[Parameter(

Mandatory = $false,

ParameterSetName = '',

ValueFromPipeline = $true)]

[string]$service

)

begin {

#

}

process {

try {

# Wait until Server is offline

Write-Host "Waiting for Reboot " $hostip "..." -BackgroundColor Black -ForegroundColor White

Start-Sleep -Seconds 10

 

# Wait for Server Reboot

Write-Host "Waiting for Host " $hostip "..." -BackgroundColor Black -ForegroundColor White

while (!(Test-Connection $hostip -quiet)) {

Write-Host 'Unreachable!'

}

Write-Host "Server up..." -BackgroundColor Green -ForegroundColor Black

Start-Sleep -Seconds 30

}

catch {

# Sending status to CP and EventLog

throw "ERROR: Waiting for reboot failed"

}

}

end {

}

}

 

 

 

 

#endregion

 

 

 

 

#region [MAIN BLOCK]

 

# Enable ICMP

Enable-ICMP -hostip $xmlServer01.ip

Enable-ICMP -hostip $xmlServer02.ip

 

# Create first AD Server

Create-ADServer

Start-Sleep -Seconds 30

WaitFor-Host -hostip $xmlServer01.ip

 

# Add Second AD Server to Domain

Join-AD -hostname $xmlServer02.name -hostip $xmlServer02.ip -dnsip $xmlServer01.ip -domainName $xmldomain.name -adminpw $xmlServer01.adminpw

Start-Sleep -Seconds 30

WaitFor-Host -hostip $xmlServer02.ip

 

# Run DCPROMO on Second AD Server

Add-ADServer

 

# Add OUs to Domain

foreach ($ou in $xmlOUS.ou){

Add-ADOU -hostip $xmlServer01.ip -name $ou.name -path $ou.path

}

 

 

# Add Users to Domain

foreach ($file in $xmlData.lab.config.users.file){

$tempfile = ".\" + $file.name

Import-Csv $tempfile | Foreach-Object {

$userprinicpalname = $_.SamAccountName + "@" + $xmlDomain.name

Add-UsersfromFile -hostip $xmlServer01.ip -SamAccountName $_.SamAccountName -UserPrincipalName $userprinicpalname -Name $_.name -DisplayName $_.name -GivenName $_.GivenName -SurName $_.SurName -Manager $_.Manager -Department $_.Department -Path $file.path

}

}

 

 

 

# Add Members to Domain

foreach ($member in $xmlData.lab.config.members.member){

Join-AD -hostname $member.name -hostip $member.ip -dnsip $xmlServer01.ip -domainName $xmldomain.name -adminpw $xmlServer01.adminpw

}

 

#endregion

Slipstream SQL Server 2008 SP2 for SCCM 2012

Thomas Maurer — Fri, 02 Dec 2011 22:23:57 +0000

The Release Candidate version of System Center Configuration Manager 2012 requires MS SQL Server 2008 SP2 with Cumulative update package 6. Now this can be a little annoying and will hopefully change to SQL Server 2008 R2 in the RTM version.

Now if you want to install MS SQL Server 2008 on a Windows Server 2008 R2 you need at least a install media with SP1. Now this post shows you how you can integrate Service Pack 2 into the install media of SQL Server 2008.

Copy the SQL Server 2008 install media to C:\SQLServer2008withSP2
Download and copy the SQL Server 2008 Service Pack 2 files to C:\temp

Now you can run the following commands:

SQLServer2008SP2-KB2285068-IA64-ENU.exe /x:c:\SQLServer2008withSP2\PCU
SQLServer2008SP2-KB2285068-x64-ENU.exe /x:c:\SQLServer2008withSP2\PCU
SQLServer2008SP2-KB2285068-x86-ENU.exe /x:c:\SQLServer2008withSP2\PCUrobocopy C:\SQLServer2008withSP2\PCU c:\SQLServer2008withSP2 Setup.exe
robocopy C:\SQLServer2008withSP2\PCU c:\SQLServer2008withSP2 Setup.rll
robocopy C:\SQLServer2008withSP2\pcu\x86 C:\SQLServer2008withSP2\x86 /XF Microsoft.SQL.Chainer.PackageData.dll
robocopy C:\SQLServer2008withSP2\pcu\x64 C:\SQLServer2008withSP2\x64 /XF Microsoft.SQL.Chainer.PackageData.dll
robocopy C:\SQLServer2008withSP2\pcu\ia64 C:\SQLServer2008withSP2\ia64 /XF Microsoft.SQL.Chainer.PackageData.dllecho PCUSOURCE="C:\SQLServer2008withSP2\PCU" >> C:\SQLServer2008withSP2\x86\DefaultSetup.ini
echo PCUSOURCE="C:\SQLServer2008withSP2\PCU" >> C:\SQLServer2008withSP2\x64\DefaultSetup.ini
echo PCUSOURCE="C:\SQLServer2008withSP2\PCU" >> C:\SQLServer2008withSP2\ia64\DefaultSetup.ini

After you have done this you can install the MS SQL Server
After you have installed it, you still need to download and install the Cumulative update package 6 for SQL Server 2008 Service Pack 2

More about SQL Slipstreaming on Peter Saddow’s MSDN blog post.

Cisco UCS C200 M2 – Cisco Integrated Management Controller (CIMC)

Thomas Maurer — Wed, 30 Nov 2011 17:24:18 +0000

The first things I tried with the new Cisco UCS C200 M2 servers was the CIMC (Cisco Integrated Management Controller). CIMC is the remote out-of-band management solution (IPMI) provided with Cisco servers, it’s basically the same like HP iLO or Dell DRAC.

One of the biggest advantages is that CIMC is included for free, so there is no extra license you need for extra features like KVM or stuff like that.

After working some hours with the CIMC I was really happy, no problems at all everything worked as expected. From the design it’s like the Cisco UCS Manager but better . I think it is much easier to use and much faster (it’s not Java).

Keyfeatures

Web based front-end
KVM and Virtual media
Change BIOS Settings
Active Directory connector
SNMP
IPMI (Very interesting with the Bare-metal deployment in SCVMM 2012)
SSH
Health Monitoring

Building a new Hyper-V Private Cloud Lab

Thomas Maurer — Mon, 28 Nov 2011 19:08:20 +0000

Two years ago I created my first real IT Lab with some HP ProLiant ML110 G5. I used this in the past years to test new products and projects. The Lab at this time was very limited, no storage, no cluster, not much RAM and weak CPU performance. Not much help if you work a lot with Hyper-V Clusters and System Center products.

I was looking around for some time now to find a cheap offer for new servers. In the last week I found a offer from Cisco with c200 M2 servers and I couldn’t resist to buy two of the for my Hyper-V Cluster nodes. The offer was a special deal which was even cheaper than building the servers by my own, at this point thanks to my former employer Atlantis Informatik AG.

Now what I will do is creating a new Hyper-V Cluster friendly environment with two Cisco C200 M2 Hyper-V nodes, one HP ML110 G5 as Storage Server and one of my old HP ML110 G5 servers as Hyper-V Server which all my Management servers and Active Directory will run on.

If you want to know more about Hardware you can use for a Hyper-V Lab I recommend the posts of Carsten Rachfahl on hyper-v-server.de (german).

Hardware Configuration

Hyper-V nodes:

2x Cisco C200 M2 - Intel Xeon 5620 2.4GHz Quad Core, 16GB RAM, Remote Management, IPMI, 6 Networkports

Storage Server:

1x HP ProLiant ML110 G5 – Intel Xeon E3110 3.0 GHz Dual Core, 8GB RAM, 4x 500GB Raid 10, 3 Networkports

Management Hyper-V node:

1x HP ProLiant ML110 G5 – Intel Xeon E3110 3.0 GHz Dual Core, 8GB RAM

Commands for Windows Server Core & Hyper-V Core Server

Thomas Maurer — Mon, 31 Oct 2011 14:45:15 +0000

For some KTSI projects I have been working a lot with Windows Server Core or Hyper-V Server. Now I had to do a lot of automation, so I made this little connection of commands. If you configure the server manually you can do the most important things with the sconfig utility.

Networking

Set Hostname

netdom renamecomputer %COMPUTERNAME% /NewName:

Join Domain

netdom join %COMPUTERNAME% /domain: /userd: /passwordd:*

Remove Domain

netdom remove

Rename Network Interface

netsh interface set interface name=”old name” newname=”new name”

Configure IP Address

netsh interface ipv4 set address name=”” source=static address= mask= gateway=

Configure DNS Servers

netsh interface ipv4 add dnsserver name=”” address= index=1

Disable Firewall (not recommended)

netsh advfirewall set allprofiles state off

Remoting

Enable PowerShell Remoting

Enable-PSRemoting

Enable Remotedesktop

netsh advfirewall firewall set rule group=”remote desktop” new enable=yes

Enable Remote Administration

advfirewall firewall set rule group=”Remote Administration” new enable=yes

Enable Remote Firewall Administration

netsh advfirewall firewall set rule group=”Windows Firewall Remote Management” new enable=yes

Enable ICMP (Ping)

netsh firewall set icmpsetting 8

Enable Remote Disk Management

netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes

Licensing

Enter License key

slmgr.vbs -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Activate Windows

slmgr.vbs -ato

Windows Update

Enable automatic updates

cscript C:'Windows'System32'Scregedit.wsf /au 4

Disable automatic updates

cscript C:'Windows'System32'Scregedit.wsf /au 1

Roles & Features

Get availibale features & roles

Dism /online /get-features /format:table

Enable feature & roles

Dism /online /enable-feature /featurename:

Basics

Change Administrator password

net user administrator *

Restart Computer

shutdown /r /t 0

Logoff

logoff

More information about Server Core: TechNet

How to add Disk Cleanup tool in Windows Server 2008 R2

Thomas Maurer — Mon, 17 Oct 2011 15:08:50 +0000

Disk Cleanup option on drive’s general properties and cleanmgr.exe is not present in Windows Server 2008 or Windows Server 2008 R2 by default.So in order to use cleanmgr.exe you’ll need to copy two files that are already present on the server, cleanmgr.exe and cleanmgr.exe.mui.

Copy “C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe” to “%systemroot%\System32″
Copy “C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui” to “%systemroot%\System32\en-US”

Now you can launch the Disk cleanup tool (cleanmgr.exe) from the command prompt.

You could also install the “Desktop Experience” feature this would also work, but why install something if you don’t need it, specially on a server.

Install SNMP on Hyper-V R2 Core Server

Thomas Maurer — Wed, 12 Oct 2011 15:21:42 +0000

If your running Microsoft Hyper-V R2 or any Windows Server 2008 R2 Core Server you can install the SNMP Feature on the command line with the command line tool dism.

First you can list all Windows Features

Dism /online /get-features /format:table

Now you can install for the SNMP Service:

Dism /online /enable-feature /featurename:SNMP-SC

After you have done this you and you have enabled Remote Management you can mange and configure smtp via remote MMC.

Important: If you need to configure the SNMP Service on a remote machine you have to install the SNMP feature on the local administrative computer. Otherwise you will not see the SNMP specific tabs.

More Information on installing Windows Features on a server running a Server Core installation of Windows Server 2008 R2: http://technet.microsoft.com/en-us/library/ee441253(WS.10).aspx