Installing Server 2008 R2 with Hyper-V as LAB and UC workstation

Last week I got a new laptop (workstation), it was quite an upgrade from my previous machine sporting

– 16 GB memory
– Intel i7 quadcore
– Builtin HD cam
– 120 GB SSD

Wanting to convert it to the a powerful tool for my UC labs and my UC workshop I thought maybe installing Windows Server 2008 R2 SP1 and use it as my desktop OS. After all Server 2008 R2 share the same basecode as Windows 7. This will enable me taking advantage of all the cool server roles that are available on this platform and at the same time not installing unnecessary features. My main motivation was getting some hands-on Hyper-V and using it as my virtualization platform. Figured that would make it simpler to take advantage of the Lync labs available by Microsoft and some of my own.

Wanting to check if at all feasible I asked an open question on Twitter:

  • StaleHansen: Is there any use of installing Server 2008 on my Laptop workstation? Thinking about utilizing Hyper-V for lab’s #Server2008 #HyperV #mvpbuzz
    • bartsurminski: You can configure server 2008 r2 to act as a fully configured workstation and use Hyper-V  http://t.co/1kPBAD5
    • tomarbuthnot: Server on laptop works fine. Just no hibernation with hyper-v. In the end VMware workstation wins for me
  • StaleHansen: Thanks for the tip, but do you have sleep? Use that a lot today.
    • tomarbuthnot: No sleep with hyper-v. All power stuff disabled. Also VMware wrkstn does all a/v sharing the hardware. Tried both, vmw For me
    • gusfraser: Tried both. Win7 for hibernation & either VMWare or VirtualBox work for me. 2008 tips here http://t.co/9TJ2kml

After this conversation I found out two things

  1. Twitter works!
  2. It is doable, but need to be aware of hibernation limitation when using Hyper-V

I decided I would try, and reinstall if it was a fail. I started searching around the web for how to go about this and found a lot of good resources in addition to the ones from Twitter.

Here is my install path for Installing Server 2008 R2 as my lab and UC workstation

Installing the Hyper-V role

I have run this configuration a couple of days now and are still enjoying it. Especially enjoy dynamic memory management and having Microsoft’s full hypervizor at my fingertips when working and doing lab’s

I am also looking into using PowerShell to start the Hyper-V service and control my VM’s. Found these resources to start me in the right direction

Installing Lync Server 2010 Prerequisites on Windows Server 2008 R2

When installing Lync Server 2010 some roles requires specific Windows Features to be installed. The features are about the same as for OCS 2007 R2.

NOTE: This article will be updated when more information and requirements become available and necessary. Last update 02.12.2010

Part One – Prerequisites required on all server roles

  • Open PowerShell as administrator and run the following commands
  • Import-Module ServerManager
  • Add-WindowsFeature NET-Framework-Core,Telnet-Client
  • Install the prerequisites for the specific role as described in Part Three
  • Run Windows Update untill everything is updated
  • Install the Lync Server 2010 binaries for the role you are installing
  • Do post installation tasks as described in Part Two

Part Two – What to install AFTER Lync Server 2010 is installed

I describe it here so it is more accessible rather than in the end of the post

Part Three – Commands to install prerequisites for Lync Server 2010 on Windows Server 2008 R2

Front End, Director and Group Chat Server Roles on Windows Server 2008 R2

NOTE: To be able to run schema, forest and domain prep from the Front End Server you need to have the Remote Server Administrative Tools [RSAT-ADDS] installed. It is only required on the first Front End server in you organization. For more information on preparing AD see: http://technet.microsoft.com/en-us/library/gg398607.aspx

  • Open PowerShell as administrator and run the following commands
  • Import-Module ServerManager
  • Add-WindowsFeature RSAT-ADDS,Web-Static-Content,Web-Default-Doc,Web-Http-Errors,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Http-Logging,Web-Log-Libraries,Web-Http-Tracing,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Client-Auth,Desktop-Experience

Installs the following components:

  • [RSAT-ADDS] – Remote Server Administrative Tools
  • [Web-Static-Content] – Static Content
  • [Web-Default-Doc] – Default Document
  • [Web-Http-Errors] – HTTP Errors
  • [Web-Asp-Net] – ASP.NET
  • [Web-Net-Ext] – .NET Extensibility
  • [Web-ISAPI-Ext] – Internet Server API (ISAPI) Extensions
  • [Web-ISAPI-Filter] – ISAPI Filters
  • [Web-Http-Logging] – HTTP Logging
  • [Web-Log-Libraries] – Logging Tools
  • [Web-Http-Tracing] – Tracing
  • [Web-Windows-Auth] – Windows Authentication
  • [Web-Filtering] – Request Filtering
  • [Web-Stat-Compression] – Static Content Compression
  • [Web-Mgmt-Console] – IIS Management Console
  • [Web-Scripting-Tools] – IIS Management Scripts and Tools
  • [Web-Client-Auth] – Client Certificate Mapping Authentication
  • Anonymous Authentication (This is installed by default when IIS is installed)
  • [Desktop-Experience] – Desktop Experience

NOTE: Installing on Server 2008 R2 SP1, you need to do this step manually. All Front End Servers and Standard Edition servers where conferencing will be deployed must have the Windows Media Format Runtime installed. The Windows Media Format Runtime is required to run the Windows Media Audio (.wma) files that the Call Park, Announcement, and Response Group applications play for announcements and music. Thats why Desktop Experience is installed. If you only want to install the correct runtime run the command below:

  • Run using Command Prompt as administrator
  • Requires reboot
  • %systemroot%\system32\dism.exe /online /add-package
    /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
    /ignorecheck

Mediation Server Role on Windows Server 2008 R2

  • No additional features required for mediation

EDGE Server Role on Windows Server 2008 R2

  • Need one aditional hotfix for Lync EDGE Server Role.
    • Note: This hotfix is included in SP1 for Server 2008 R2
    • Windows Server 2008 R2 update available from Microsoft Knowledge Base article 2028827, “The applications that use the TDI driver for network traffic may stop responding in Windows Server 2008 R2 or in Windows 7,” at http://go.microsoft.com/fwlink/?LinkId=205459

Monitoring and Archiving Server Roles on Windows Server 2008 R2

NOTE: If Monitoring og Archiving is deployed in the topology, all server roles must install the below features, including the Monitoring and Archiving Servers

  • Open PowerShell as administrator and run the following commands
  • Import-Module ServerManager
  • Add-WindowsFeature msmq-server,msmq-directory

Installs the following components:

  • [MSMQ-Server] – Message Queuing Server
  • [MSMQ-Directory] – Directory Service Integration

Software Automatically Installed by Lync Server Setup

When you install Lync Server 2010 on a server, some software that is required by Lync Server is installed automatically (that is, if the required software is not already installed on the server). This includes the following:

  • Microsoft Visual C++ 2008 Redistributable
  • Microsoft Visual J# version 2.0 Redistributable
  • URL Rewrite Module version 2.0 Redistributable
  • SQL Server 2008 Express SP1
  • SQL Server 2008 Native Client

References:
For more information see TechNet documentation: http://technet.microsoft.com/en-us/library/gg398686.aspx

Installing OCS 2007 R2 Prerequisites on Windows Server 2008 R2

[tweetmeme source=”stalehansen” only_single=false]Server 2008 R2 is now supported by OCS 2007 R2. As a follow-up to my post on Installing OCS 2007 R2 Prerequisites on Windows Server 2008 I will in this post describe how you can install OCS 2007 R2 prerequisites on Server 2008 R2. While you need to install the same prerequisites on both OS’ there is a change in what commands you use and you also need to prepare the server in a different way when you are installing on Server 2008 R2

Part one – Before you install OCS 2007 R2 binaries

  • Open powershell as administrator and run the following commands
    • Import-Module ServerManager
    • Add-WindowsFeature as-net-framework,desktop-experience,telnet-client
      • This installs the following features
        • [As-Net-Framework] – .Net Framework 3.5 SP1
        • [Desktop-Experience] – Desktop Experience
        • [Telnet-Client] – Telnet Client (recommended not required)
  • Request the Hotfix that is described in KB975858 for Windows Server 2008 R2
    • You need to request it, then you recieve a link by email, from there you can download and install it
  • Install the prerequisites for the specific role as described in part three
  • Run Windows Update untill everything is updated
  • Install the OCS 2007 binaries for the role you are installing

Part two – After you install OCS 2007 R2 binaries

  • When you try to activate OCS 2007 R2 Standard Edition, Enterprise Edition or Edge Server role when all windows updates are installed it fails
    • Download and install OCSASNFix.exe
    • Re-run the activation wizard
  • Download and install the latest cumulative updates for OCS 2007 R2
  • If you have XP or Vista clients in your enterprise change the default NTLM security settings from 128-bit encryption to “no minimum”
    • Start secpol.msc on a Windows Server 2008 R2 operating system server.
    • Click to select Local Policies and then click Security Options node.
    • Make sure that the following values of the policies are set to “No Minimum.”

Part three – Commands to install the necessary prerequisites for OCS 2007 R2 on Windows Server 2008 R2

Front End on Windows Server 2008 R2

  • Import-Module ServerManager
  • Add-WindowsFeature web-windows-auth,web-mgmt-compat,web-mgmt-console,web-http-logging,msmq-server,msmq-directory,was-process-model,was-config-apis, web-static-content,rsat-adds

Installs the following components:

  • [Web-Windows-Auth] – Windows Authentication
  • [Web-Mgmt-Compat] – IIS 6 Management Compatibility
  • [MSMQ-Server] – Message Queuing Server
  • [MSMQ-Directory] – Directory Service Integration
  • [RSAT-ADDS] – Active Directory Domain Services Tools
  • [WAS-Process-Model] – Process Model
  • [WAS-Config-APIs] – Configuration APIs
  • [Web-Mgmt-Console] – IIS Management Console
  • [Web-Http-Logging] – HTTP Logging
  • [Web-Static-Content] – Static Content

NOTE: If you are to run the create pool wizard from the Front End server against SQL 2008, you also need the MS SQL Native Client: X64 Package (sqlncli.msi) – 7963 KB
Also check out this post of mine whether to run create pool on OCS Front End or Back End SQL server: https://msunified.net/2009/08/11/create-pool-%e2%80%93-run-on-ocs-or-sql-server/

Office Communicator Phone Edition deployment on Windows Server 2008

  • Import-Module ServerManager
  • Add-WindowsFeature Web-Static-Content

Installs the following components in addition to Front End prerequisites:

[Web-Static-Content] – Static Content

NOTE: It exists default MIME types for both the .xml and the .cat extensions that is used by the updater. There is however no default for the .nbt extension and you need to configure it manually. See this post on how to do it http://www.codesalot.com/2010/communicator-phone-edition-update-issues/

Monitoring Server on Windows Server 2008

  • Import-Module ServerManager
  • Add-WindowsFeature msmq-server,msmq-directory

Installs the following components:

  • [MSMQ-Server] – Message Queuing Server
  • [MSMQ-Directory] – Directory Service Integration

CWA Server on Windows Server 2008

  • Import-Module ServerManager
  • Add-WindowsFeature web-windows-auth,web-digest-auth,web-basic-auth,web-mgmt-compat,web-mgmt-console,web-common-http,web-ISAPI-ext,web-ISAPI-filter,web-request-monitor,web-http-redirect,web-http-logging

Installs the following components:

  • [Web-Windows-Auth] – Windows Authentication
  • [Web-Digest-Auth] – Digest Authentication
  • [Web-Basic-Auth] – Basic Authentication
  • [Web-Mgmt-Compat] – IIS 6 Management Compatibility
  • [Web-Mgmt-Console] – IIS Management Console
  • [Web-Common-Http] – Common-http-features
  • [Web-ISAPI-Ext] – ISAPI Extensions
  • [Web-ISAPI-Filter] – ISAPI Filters
  • [Web-Request-Monitor] – Request Monitor
  • [Web-Http-Redirect] – HTTP Redirection
  • [Web-Http-Logging] – HTTP Logging

Mediation Server on Windows Server 2008

  • Import-Module ServerManager
  • Add-WindowsFeature rsat-adds

Installs the following components:

  • [RSAT-ADDS] – Active Directory Domain Services Tools

References:
For base OS prerequisites: http://support.microsoft.com/kb/982021
For supporting OCS 2007 R2 after raising the domain functional level: http://support.microsoft.com/kb/982020

Installing Exchange 2010 Prerequisites on Server 2008 R2

Commands to install the necessary prerequisites for Exchange 2010 on Windows Server 2008 R2

Update 08.12.11: Exchange Server 2010 SP2 was released and require an additional prerequisite which is IIS 6 WMI Compatibility feature (Web-WMI).  This article and PowerShell Script was updated accordingly in all options containing the CAS role.

Before you begin, prepare your environment

  • Make sure that the functional level of your forest is at least Windows Server 2003
  • Also make sure that the Schema Master is running Windows Server 2003 with Service Pack 1 or later
  • If Database Availability Groups (DAG) is going to be used install Server 2008 R2 Enterprise Edition
    • Exchange 2010 Standard Edition supports DAG with up to 5 databases
    • Exchange 2010 Enterprise Edition supports up to 100 databases per server
    • You can install all server roles on the same server when using DAG
    • But then you need a hardware load balancer  for redundant CAS and HUB due to a Windows limitation preventing you from using Windows NLB and Clustering Services on the same Windows box
    • Two node DAG requires a witness that is not on a server within the DAG
      • Exchange 2010 automatically takes care of FSW creation; though you do have to specify the location of the FSW
      • It is recommended to specify the FSW to be created on a Hub Transport Server
      • Alternatively, you can put the witness on a non-Exchange Server after some prerequisites have been completed
      • You can follow these steps to get your member server to act as FSW
        • add the “Exchange Trusted Subsystem” group to our Local Administrators Group on that member server
      • On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For details, see 2007 Office System Converter: Microsoft Filter Pack (this allows office attachments content to be searched and indexed)
  • Set Pagefile size, RAM + 10MB (for systems with 8 GB of RAM or less, set pagefile to RAM * 1,5)
  • Disable IPv6 by using this guide: http://support.microsoft.com/kb/929852
  • Run Windows Update untill all updates are installed

Install the Windows Server 2008 R2 operating system prerequisites

  • Open powershell and run the following command
    • Import-Module ServerManager
  • For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox roles:
    • Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy,Web-WMI -Restart
  • For a server that will host the Client Access and Hub Transport server roles:
    • Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy,Web-WMI -Restart
  • For a server that will host only the Mailbox role:
    • Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server -Restart
  • For a server that will host only the Unified Messaging role:
    • Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Desktop-Experience -Restart
  • For a server that will host the Edge Transport role:
    • Add-WindowsFeature NET-Framework,RSAT-ADDS,ADLDS -Restart
  • After the system has restarted, configure the Net.Tcp Port Sharing Service for Automatic startup by running the following command:
    • Set-Service NetTcpPortSharing -StartupType Automatic

PowerShell Script: MVP Pat Richard has created a script to automate the process of installing the prerequisites: http://www.ehloworld.com/152

NOTE: You can also install the above features using xml scripts found in a scripts catalogue on the Exchange media. You still need to manually configure Net.Tcp Port Sharing Service for Automatic startup though. There is one script for every role. Thanks goes to Alex Lewis for the tip: http://www.networkworld.com/community/node/46829

For more information see Technet article http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx
Also check out Chris and Robin’s Technology blog http://chrislehr.com/2009/10/installing-exchange-2010-quickly-using.htm
You should also check out MVP Elan Shudnows blog for how to install Exchange 2010 with DAG: http://www.shudnow.net/2009/10/29/exchange-2010-rtm-dag-using-server-2008-r2-%E2%80%93-part-1/