How to convert Hyper-V dynamic disk to fixed disk

Problem

Using fixed disk is one of best practices of Hyper-V deployment. It leads to 1) Less likely to fragment and better space management 2) Better performance by roughly 10% to 15%.

Step by Step Guide

1) Open Windows Hyper-V Manager

2) Turn off the Virtual Machine whose disk file you want to concert

Right click Virtual Machine name and select "Turn Off".

3) Right-click the Virtual Machine and select 'Settings...'

4) Select the Virtual Machine's hard drive and click 'Edit'

5) Select 'Convert' and click 'Next'

6) Input the path to which you want output fixed disk file, and click 'Next'.

7) Click 'Finish' to start conversion

If the host server installed IDE SATA disk, it takes about 1 hour to convert a 40G disk file. The time will increase proportionally, if the disk file is larger

Step by Step Guide to Install Windows Hyper-V Guest Operating System

Requirements

Install Windows Server 2008/2003 or Linux as guest operating system into the Windows Hyper-V server.

Step by Step Guide

1) Create Windows Hyper-V Virtual Machine

Make sure to create Windows Hyper-V virtual machine first. Please refer to Step by Step Guide to Create Windows Hyper-V Virtual Machine.

2) Open Windows Hyper-V Manager

Windows Server 2008 Start > Programs > Administrative Tools > Hyper-V Manager.

3) Start Virtual Machine

If the virtual machine is not running, You should start it first by right click virtual machine and select start.

4) Connect to Virtual Machine and Start to install guest operating system

Right click Virtual Machine name and select Connect. The Virtual Machine Connection tool window pops up.

5) Choose install media

Select Media > DVD Driver > Insert Disk... menu item if you want to install guest operating system from .iso file.

6) Select Windows Server 2003 install ISO file

Browse the hard driver and find the .iso file.

7) Install Windows Server 2003

Just click "Enter" key after step 6. Follow the screen to install window Server 2003.

8) Install Windows Server 2003 CD 2

Change the install media from CD1 to CD2 by choosing Media > DVD Driver > Insert Disk... menu item. Browse the hard driver and find the correct ISO file.

Click the "Ok" button to install the second CD.

9) Install Integration Services and Virtual Machine Drivers

This action will install hardware driver for the virtual machine.

10) Configure Network for Guest OS

Specify a dedicated IP for the virtual machine. So you can access the server from outside with the IP.

11) Enable Remote Desktop Protocol (RDP)

So you can login to the Hyper-V server with RDP.

12) Finish

Now your Hyper-V server should be ready for you to use.

Step by Step Guide to Create Windows Hyper-V Virtual Machine

Requirements

We will install all Windows Hyper-V servers at "C:\HyperV" folder. Each virtual machine will have its separated sub folder. The sub folder name will be the virtual machine's host name. Here is an example "C:\HyperV\TestVM". All information about this virtual machine will be under this folder (Disk file "C:\HyperV\TestVM\TestVM.vhd", virtual machine configuration "C:\HyperV\TestVM\Virtual Machines" and snapshots "C:\HyperV\TestVM\SnapShots").

Step by Step Guide

1) Change the default Hyper-V folders

Please see How To Change Windows Hyper-V Default Folders to Store Hard Disk File and Virtual Machine Configuration File?.

2) Create Physical Folder Manually

You need to create a physical folder to store the hard disk file and configuration files first. It is "C:\HyperV\TestVM" or what ever you want.

3) Open Windows Hyper-V Manager

Windows Server 2008 Start > Programs > Administrative Tools > Hyper-V Manager.

4) New Virtual Machine

Click "New > Virtual Machine" in the right side "Actions" panel.

5) Specify Name and Location

Put "TestVM" as name and check on "Store the virtual machine in a different location" but leave "C:\HyperV" as it is. Then click "Next >".

6) Assign Memory

Specify the amount of memory to allocate to this virtual machine. You can specify an amount from 8MB through the maximum physical memory. Then click "Next >".

7) Configure Networking

Choose "External Virtual Network" from the dropdown list. If it is not in the list, you need to create the virtual network first. Then click "Next >".

8) Create Virtual Hard Disk

Leave the name and location as default. Specify the hard disk size (25GB) based on your requirement. Then click "Next >".

9) Install Operating Sysem Optionst

Choose the default "Install an operating system later". Then click "Next >".

10) Review and Confirm

Review the configuration information. Click "Finish" button if everything looks ok.

11) Check the file structure

The file structure should be similar with below. Now you are ready to load operating system to your Hyper-V server. Please see Step by Step Guide to Install Windows Hyper-V Guest Operating System.

Step by Step Guide to Install Windows Server Hyper-V Role

1. Requirements

Please make sure you meet the following hardware and software requirements before you install Windows Server Hyper-V.

• The physical server must be a 64-bit environment
• The physical server must support hardware-assisted virtualization (Intel VT or AMD-V) technology. Make sure it is enabled in the server BIOS.
• Operating system must be Windows Server 2008 Standard, Enterprise or Datacenter Edition x64

2. Open Server Manager

Windows Server 2008 Start > Programs > Administrative Tools > Server Manager.

3. Add new Role

4. Click Next at Before You Begin Window

5. Select "Hyper-V" at Select Server Roles Window

6. Click Next at Hyper-V Windows

7. Select correct Ethernet Cards at "Create Virtual Network" Window

8. Click Install to start to install

9. Hyper V role installed

10. Upgrade Windows 2008 server and restart it

Step by Step Guide to Configure Windows Hyper-V Virtual Network

1. Install Windows Server Hyper-V Role

2. Network Settings Before Install Hyper-V Virtual Network

1) Open Network Connections

Windows Server 2008 Start > Settings > Network Connections.
There is a 'Local Area Connection' network. It is a physical network adapter for Hyper-V Virtual Network.

2) Open Properties of Local Area Connection

Right click 'Local Area Connection' and select 'Properties'.

2) Open Properties of 'Internet Protocol Version 4TCP/IPv4)'

Click 'Internet Protocol Version 4(TCP/IPv4)' and select 'Properties'.

3. Configure Windows Hyper-V Virtual Network

1) Open Windows Hyper-V Manager

Windows Server 2008 Start > Programs > Administrative Tools > Hyper-V Manager.

2) Open Virtual Network Manager

Click "Virtual Network Manager..." in the right side "Actions" panel.

3) Add a New Virtual Network

Select 'External' and click 'Add'.

4) Set Virtual Network

1. Input the New Virtual Network
2. Select correct physical network adapter for Hyper-V Virtual Network
3. Click OK

5) Apply Networking Changes

There will have a new warning window. Click 'Yes' to apply the changes

Note:
The network may be disconnected if you use a static IP. Please re-config the 'Local Area Connection 4' as the old Local Area Connection.

4. Network Settings After Install Hyper-V Virtual Network

1) Open Network Connections

Windows Server 2008 Start > Settings > Network Connections.
There is a new 'Local Area Connection 4' network. It is the External Virtual Network that has been created.

2) Open Properties of 'Local Area Connection'

Right click 'Local Area Connection' and select 'Properties'.
There is only 'Microsoft Virtual Network Switch Protocol' enabled after installed External Virtual Network.

3) Open Properties of 'Local Area Connection 4'

Right click 'Local Area Connection4' and select 'Properties'.
It will have the same settings to the Local Area Connection's old settings

4) Open Properties of 'Internet Protocol Version 4TCP/IPv4)'

Click 'Internet Protocol Version 4(TCP/IPv4)' and select 'Properties'.

Upgrading to Exchange Server 2013

 

Upgrading to Exchange Server 2013

   

With the news that Exchange Server 2013 has reached RTM a lot of customers are now asking for guidance on upgrading their existing organizations to Exchange 2013.
Although all of the upgrade guidance is not publicly available yet, here is what we know so far.

Supported Co-Existence Scenarios for Exchange 2013

Exchange Server 2013 will support co-existence with the following versions:

• Exchange Server 2010 SP3
• Exchange Server 2007 SP3 + an update rollup

Neither Exchange 2010 Service Pack 3 nor the required update rollup for Exchange 2007 SP3 have been released yet, so as it stands right now there is no co-existence possible.
Microsoft has announced that Exchange 2010 SP3 will be released some time in the first half of 2013. This leaves open the possibility that Exchange 2013 will reach general availability (announced for Q1 2013 and rumoured to be in February) before the Exchange 2010 SP3 release. Personally I hope they arrive at the same time.
No word yet on the next update rollup for Exchange 2007 SP3, which it has been suggested will be the one to meet the requirements for  co-existence with Exchange 2013. However based on typical release cadence we may see this in January/February 2013 as well.
There will be no co-existence support for Exchange Server 2003. If you’re still running Exchange 2003 and are looking to upgrade to Exchange 2013 you’ll need to do an interim upgrade to Exchange 2010 (or 2007) first.

Client Support for Exchange Server 2013

During a TechEd Australia session on Exchange 2013 deployment and co-existence, Scott Schnoll showed us the following list of compatible clients for Exchange Server 2013.

• Outlook 2013, Outlook 2010, and Outlook 2007
• Entourage 2008 for Mac, Web Services Edition
• Outlook 2011 for Mac

Outlook 2013 will support Exchange 2013 as-is, but an update will be required for Outlook 2010 and 2007.
There will be no support for Outlook 2003. If you’re still running Office 2003 in your environment and intend to upgrade to Exchange 2013 then now would be a good time to begin looking at upgrading your Office installations.

Active Directory Requirements for Exchange Server 2013

In what may be a relief for some customers, Exchange 2013 will support a Windows Server 2003 Forest/Domain functional level, and Windows Server 2003 SP2 domain controllers, according to the information presented at TechEd.
A schema update will be required as usual, and this is expected to be delivered in the same service pack/update rollup that will provide co-existence support.

The Upgrade Process for Exchange Server 2013

The documentation and general guidance for Exchange 2013 upgrades has not been published yet, though we can expect to see the guidance appearing in the Exchange Deployment Assistant in due course.
In the meantime if you want to see an overview of the deployment and co-existence scenarios I do recommend watching Scott’s session from TechEd Australia 2012.
My personal view is that an upgrade project for Exchange 2013 is going to be very similar to that for Exchange Server 2010. Many of the challenges in these upgrades come not from Exchange itself, but more from the integration points such as third party software.
In that respect you will need to watch for announcements from the vendors for products such as your backup software now that the RTM and GA timelines are becoming a reality.
My free planning guides for the Exchange 2010 upgrade scenarios can be used even now to begin identifying these integration points and other key elements of your environment that will need consideration during an Exchange 2013 upgrade project.

How to Install Exchange Server 2013

   

Deployment of an Exchange Server 2013 server goes through three main stages.

1. Preparing Active Directory (if you are installing Exchange Server 2013 for the first time)
2. Installing the Exchange Server 2013 pre-requisites on the server
3. Running Exchange Server 2013 setup

Preparing Active Directory for Exchange Server 2013

When you are installing Exchange Server 2013 for the first time the Active Directory needs to be prepared.
There are a series of requirements for Active Directory preparation to be successful:

• Schema master running Windows Server 2003 with SP2, or a later version of Windows Server
• At least one Global catalog server per site that Exchange will be installed in that is running Windows Server 2008 or later
• At least one Domain controller per site that Exchange will be installed in that is running Windows Server 2008 or later
• Forest functional mode of Windows Server 2003 or higher
• An account with Schema Admins, Domain Admins, and Enterprise Admins permissions to run Exchange setup

Although Active Directory preparation can occur as part of the installation of the first Exchange Server 2013 server, you can also run the Active Directory preparation as a separate task beforehand on a 64-bit server running Windows Server 2008 or higher.
Because the Active Directory preparation requires the RSAT-ADDS tools I am running it on the domain controller in my test lab.
Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.
For Windows Server 2008 R2 (SP1 or later), in PowerShell run:

Import-Module ServerManager

Add-WindowsFeature RSAT-ADDS

For Windows Server 2012, in PowerShell run:

Install-WindowsFeature RSAT-ADDS

If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory:

setup /PrepareAD /OrganizationName: "your organization name" /IAcceptExchangeServerLicenseTerms

Note: if your organization name contains spaces then it must be enclosed in quotes as shown above.
If an Exchange organization already exists you can omit the /OrganizationName parameter.

setup /PrepareAD /IAcceptExchangeServerLicenseTerms

For other Active Directory preparation scenarios, such as multiple forests or multiple domains, refer to this article on TechNet.

Installing the Exchange Server 2013 Pre-Requisites

Exchange Server 2013 can be installed on either Windows Server 2008 R2 (SP1 or later) or Windows Server 2012. Depending on the server roles you are installing the pre-requisites vary.

• Installing Exchange Server 2013 Pre-Requisites on Windows Server 2008 R2
• Installing Exchange Server 2013 Pre-Requisites on Windows Server 2012

Installing Exchange Server 2013 Using the Setup Wizard

After installing the pre-requisites a restart of the server may be required. If you proceed without restarting then setup may be unable to proceed when it detects the pending restart.
From the location where you have stored your Exchange 2013 files run Setup.exe.
The first dialog gives you the opportunity to check for updates to the setup files before you proceed.

 

Check for updates to Exchange 2013 setup files

After the setup files have updated click Next to continue.
Click Next to continue past the Introduction message.

 

 

Exchange 2013 setup introduction

  
Accept the license agreement and click Next to continue.

Exchange 2013 license agreement

Choose whether or not to enable Error Reporting and click Next to continue.

Configure Exchange 2013 error reporting

After a check that all the pre-requisites are installed the setup wizard will move on to the next step automatically (if the check was successful).
Now we can choose the server roles to install. If this is the first server you’re installing Microsoft recommends you install the Mailbox server role first (this can be either a Mailbox-only server or a combined Mailbox/Client Access server).

Choose the Exchange 2013 server roles to install

Verify that you have enough disk space for the installation, or choose a path that does have enough disk space, and click Nextto continue.

Choose the location to install Exchange 2013

If there is no existing Exchange organization in Active Directory, and you haven’t already prepared Active Directory for Exchange, you will be prompted to enter an Exchange organization name.
When installing the Mailbox server role you are given the option to disable malware protection. If you disable it now you can enable it again later.

Configure anti-malware protection for the Mailbox server

Some readiness checks are performed. If this is the not the first server you’re installing and there is no Send Connector defined for outbound email then you may see a warning, but you can still proceed with the server installation.

Setup can’t detect a Send connector with an address space of ‘*’. Mail flow to the Internet may not work properly.

Exchange 2013 setup pre-requisite warning

 

When you are ready to proceed you can click Install to begin.

Begin the installation of Exchange 2013

The install is a fairly lengthy process, so you may want to go and do something else while you wait. When setup has finished click Finish.

Exchange 2013 setup is finished