VIEWS: 6 PAGES: 9 POSTED ON: 9/6/2012
Setting up the Host Machine for the SharePoint and Office 2010 Virtual Machines V4.1 "The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, places, or events is intended or should be inferred." System Requirements Requirement Item Operating System Microsoft Windows® Server 2008 R2 with the Hyper-V role enabled (Service Pack 1 highly recommended) Drive Formatting NTFS Processor Intel VT or AMD-V capable RAM 4 GB or more (16 GB or more recommended) Hard disk space required for install 100 GB (plus space for VHD growth) Virtual Machine Software and Pre-Configuration Virtual machine “a” contains the following pre-configured software: 1. Windows Server 2008 R2 SP1 Standard Evaluation Edition, running as an Active Directory Domain Controller for the “CONTOSO.COM” domain with DNS and WINS 2. Microsoft SQL Server 2008 R2 Enterprise Edition with Analysis, Notification, and Reporting Services 3. Visual Studio 2010 SP1 4. Microsoft SharePoint Server 2010 SP1 Enterprise Edition 5. Microsoft Office Web Applications SP1 6. FAST Search for SharePoint 2010 SP1 7. Microsoft Project Server 2010 SP1 8. Microsoft Office Professional Plus 2010 SP1 9. Microsoft Visio 2010 SP1 10. Microsoft Project 2010 SP1 11. Microsoft Lync 2010 Virtual machine “b” contains the following pre-configured software: 1. Windows Server 2008 R2 SP1 Standard Evaluation Edition, joined to the “CONTOSO.COM” domain 2. Microsoft Exchange Server 2010 SP1 Virtual machine “c” contains the following pre-configured software: 1. Windows Server 2008 R2 SP1 Standard Evaluation Edition, joined to the “CONTOSO.COM” domain 2. Microsoft Lync Server 2010 Active directory has been preconfigured over 200 “demo” users with metadata in an organizational structure. All of these user profiles have been imported and indexed for search within SharePoint Server 2010, with “contoso\administrator” granted Domain Admin permissions. SharePoint Server 2010 has been configured in a “Complete” farm using Kerberos authentication and the default SQL Server 2008 R2 instance for data, and has a site collection created using the Team Site template at http://intranet.contoso.com/ and a FAST Search Center at http://intranet.contoso.com/search/. Virtual machine “a” is required for all scenarios, image “b” for email functionality and image “c” for instant messaging. Performance Considerations 1. If possible, unpack and run the VM image(s) on a separate, fast hard drive (7200 RPM or better) from the operating system of the host machine. If this is being done on a laptop, a second internal drive or external eSATA drive works best, though USB 2.0/3.0 (1.1 is too slow) or Firewire is acceptable. For best performance use a second internal SSD drive. Host Configuration This section lists the tasks that you must perform on the machine being used as the virtual machine host. Tasks Detailed steps 1. Install the Hyper-V role on your a. Install the Hyper-V role on your Windows Server Windows Server 2008 R2 host 2008 R2 or R2 SP1 host It is essential that you use Windows Server 2008 R2 or R2 SP1. Older versions of Hyper-V will not be able to import the VM package, will likely trigger activation of the software included in the image, and will have reduced performance. If you are running a host with a Core I7 processor, be sure to disable power saving for both CPU and PCI in the host BIOS. 2. Extract VM Image(s) a. Copy the archive files for the VM to local disk. Do not attempt to unpack from a network share. b. Extract the VM image by running the self- extracting executable c. Set the extraction location, see the note in Performance Considerations above for more information Configure Hyper-V for the Virtual Machine This section lists the tasks that you must perform in Hyper-V Tasks Detailed steps 1. Configure the Hyper-V Manager a. Start Hyper-V Manager from Control Panel -> Administrative Tools Do not use an External network for the b. Confirm that the local host machine appears in the VMs in this set. The VMs do not contain Hyper-V Manager list and select it if not already any antivirus software and can conflict done (MAC addresses, IP addresses, c. Under Actions, click Virtual Network Manager… hostnames, etc.) with other running d. Confirm that you have created an Internal virtual instances of the VM or potentially network named “Internal”. Internal networks limit unrelated physical machines. The connectivity to only VMs and the host. If a suitable Internal virtual network configuration in not, create one now using the following steps: these steps will allow the host to use i. Click on Virtual Network Manager in the remote desktop to access the VM. Actions pane ii. Choose New virtual network in the Virtual If you must run this VM set with external Networks pane access, please setup a second NIC in the iii. Choose Internal from the type list and click Hyper-V configuration for this purpose. Add The primary NIC inside the VM is setup to use a static IP address and changing iv. Enter a name of Internal and click OK this setting will have a wide range of v. On the host machine, choose Start menu -> undesirable side effects. right-click Network -> Properties vi. Click Change adapter settings vii. Find the adapter with a description of Internal, right-click and choose Properties viii. Double-click on Internet Protocol Version 4 and enter the following values: 1. IP address: 192.168.150.6 2. Subnet mask: 255.255.255.0 3. Default gateway: (leave blank) 4. Preferred DNS server: 192.168.150.1 ix. Click OK e. Close the Virtual Network Manager dialog. 2. Import and Configure the Virtual a. Under Actions, click Import Virtual Machine… Machine b. Use the Browse button to select the folder where the virtual machine package was extracted. Due to the activation and expiration Choose the option to copy the configuration models in Windows Server 2008 R2, it’s c. Click Import and wait for the Import to complete – highly recommended that you do one of the import status will appear in the Operations the following: column Retain a copy of the unaltered d. Select the newly imported virtual machine and click VM Settings in the right pane of the Hyper-V Manager Create and retain a snapshot e. Confirm (and correct if necessary) that the from before first run of the VMs Network Adapter is connected to the Internal network from step 1d. Do not add a new Network Adapter. For more information see the “Activation f. (Optional – for non-SP1 Hosts Only) Update the and Expiration” section below. VMs to use additional RAM if available. Use the following settings for the VMs for best performance: i. “a”: 10240MB ii. “b”: 4096MB iii. “c”: 3072MB g. (Optional – for SP1 Hosts Only) Update the VMs to use Dynamic memory. Use the following settings for the VMs for best performance: i. “a” A. Startup: 4096MB B. Maximum: 10240MB ii. “b” A. Startup: 1024MB B. Maximum: 4096MB iii. “c” A. Startup: 1024MB B. Maximum: 3072MB h. Close the virtual machine Settings dialog Post-setup Performance Tweaks This section lists actions and settings for the host machine which will help you get best performance. Tasks Detailed steps 1. Defragment all host drives a. Open Windows Explorer, right-click on the C: drive icon, and choose “Properties” b. Choose the Tools tab and click on the “Defragment Now” button c. Confirm that the C: drive is the chosen volume, and click on the “Defragment” button d. Wait for the defragmentation to complete. This may take anywhere from a few seconds to a few hours depending on the size of the drive and how fragmented it is. You may need to run this multiple times for full effect. e. Repeat for all other host hard drives 2. Set the host video resolution a. Right-click on the desktop Properties Settings b. Confirm that the resolution is at least 1024x768 (1280x1024 or higher if recommended) and the color depth is at least 16 bit 3. Confirm that the system date and a. Open the Control Panel Date and Time time are correct b. Confirm that the date and time are accurate, if not correct them 4. Disable Virus Scanning a. Follow the procedures for your antivirus software to disable any “real-time” scanning of the Hyper-V processes and the folder where you unpacked the VM files. See http://support.microsoft.com/kb/961804 for more details. 5. Convert the dynamic VHD included a. Open the Hyper-V Manager on the host in the VM into a static VHD b. Select the VM in the Virtual Machines pane c. Click Settings in the Actions pane If drive space allows, consider doing d. Choose the Hard Drive under IDE Controller 0 in this conversion. The fixed VHD is the Hardware pane considerably larger (135GB for each e. Click the Edit button directly below the path of VM) but will give better performance. the VHD file f. Choose the Convert radio button and click Next g. Supply a file path and name for the new fixed disk h. Click Finish and wait for the Edit operation to complete i. Click Browse for the VHD file and choose the fixed VHD just created j. Click OK to apply the change and close the settings window k. Defragment the host drive containing the new fixed VHD Start the Virtual Machine Before each demo session the following steps are necessary to setup the environment. Tasks Detailed steps 1. Start the “a” Virtual Machine a. Return to or start the Hyper-V Manager b. Select the “a” Virtual Machine c. Click Start d. Click Connect – a Virtual Machine Connection window should appear e. Wait for the VM to boot up and reach the login screen. 2. Start the “b” Virtual Machine a. Return to or start the Hyper-V Manager (optional) b. Select the “b” Virtual Machine c. Click Start d. Click Connect – a Virtual Machine Connection window should appear e. Wait for the VM to boot up and reach the login screen. f. Close the Virtual Machine Connection window 3. Start the “c” Virtual Machine a. Return to or start the Hyper-V Manager (optional) b. Select the “c” Virtual Machine c. Click Start d. Click Connect – a Virtual Machine Connection window should appear e. Wait for the VM to boot up and reach the login screen. f. Close the Virtual Machine Connection window 3. Log in to the VMs a. Login to the “a” Virtual Machine using the Virtual Machine Console as the following user: Note: The Virtual Machine Connection User: administrator uses Ctrl-Alt-Home instead of the Password: pass@word1 normal Ctrl-Alt-Del sequence for login. Domain: CONTOSO b. Double-click the “Start Services” desktop shortcut and close when complete. c. Repeat for the “b” and “c” VMs if running. Stop the Virtual Machine Image After each demo, the following steps are necessary to reset the environment for the next use. Tasks Detailed steps 1. Stop the VM Image a. Click Shut Down from either the Virtual Machine Connection or the Hyper-V Manager for the “a”, “b” and “c” images. Snapshots and Saved State Hyper-V introduces the concept of “snapshots” which can be used to revert a virtual machine to a previous configuration state. As delivered, this virtual machine does not include any snapshots. Tasks Detailed steps 1. Create a Snapshot a. Prepare the VM(s) in the state you wish to capture. It is very important that snapshots in b. Open or return to the Hyper-V Manager multiple VM environments are “in sync”. c. Select the “c” VM (if running) and click Snapshot If you capture a snapshot of one VM in under Actions. a set, make sure you capture a d. Select the “b” VM (if running) and click Snapshot corresponding snapshot in all other under Actions. VMs as well. e. Select the “a” VM and click Snapshot under Actions. f. Wait for the snapshot captures to complete g. (optional) Select each VM and rename the snapshots you have just created. 2. Apply a Snapshot a. Open or return to the Hyper-V Manager b. Select the “a” VM, right-click on the snapshot It is very important that snapshots in you wish to use, and choose Apply. You will be multiple VM environments are “in sync”. prompted to save the current state as a If you apply a snapshot of one VM in a snapshot. Doing so will retain your current set, make sure you apply a state, skipping will discard it. corresponding snapshot in all other c. Select the “b” VM, right-click on the snapshot VMs as well. you wish to use, and choose Apply. You will be prompted to save the current state as a snapshot. Doing so will retain your current state, skipping will discard it. d. Select the “c” VM, right-click on the snapshot you wish to use, and choose Apply. You will be prompted to save the current state as a snapshot. Doing so will retain your current state, skipping will discard it. Activation and Expiration NOTE – Activation of the operating system in the virtual machine is OPTIONAL. Please do NOT perform the following steps unless your initial 10 day evaluation period expires. The Windows Server 2008 R2 instances used in these virtual machines are distributed without activation using a trial key. You will receive activation notifications a few days after your first use, and expiration notifications after 180 days. In Windows Server 2008 R2 Virtual Machines the notifications will followed by forced shutdowns after approximately two hours of use. To reset the activation and/or expiration clocks, you may use the steps in this section. Tasks Detailed steps 1. “Rearm” the Virtual Machine a. Startup and login to the Virtual Machine b. Run “Rearm Windows” from the “rearm” group in “Rearm” may only be done a limited the Start Menu number of times. It is highly c. Wait for the popup confirmation that the recommended that you use one of the configuration changes are complete options in the “Configure Hyper-V for d. Reboot the Virtual Machine the Virtual Machine” section to avoid e. Repeat for all VMs in the set being left without a functioning Virtual Machine unexpectedly. Mobile Device Demos The demo sets are created to be run as standalone environments and should not be directly connected to external networks. However, it is possible to demonstrate mobile device integration with the demo environment using the following steps. To complete this configuration you will need a mobile device capable of Wifi connectivity -OR- multiple physical machines and a mobile device capable of “tethering” via the Zune software. To connect via Wifi, use the following steps. Tasks Detailed steps 1. Startup the VMs a. Confirm that the Hyper-V host is not connected to any external networks, either wired or wireless Note: Do not start the DHCP scope if the “a” VM is connected to a b. Startup all VMs using the instructions above network of any kind as this can c. Login to the “a” Virtual Machine as disrupt network communication for contoso\administrator others on that network. d. Open DHCP from Administrator Tools in the Start Menu e. Expand the tree and enable the “Mobile Device” scope 2. Setup wireless connections a. Connect all VMs to a Hyper-V virtual network bound to a wireless device. There are multiple possible configurations, but the most common Note: Ad-hoc networks have a very are: limited range and are not support on Windows Phone 7 devices. i. An internal Hyper-V virtual network bridged to the Hyper-V host’s physical wireless adapter. Within the settings for the host wireless adapter, create and connect an ad- hoc wireless connection. ii. An internal Hyper-V virtual network using Routing and Remote Access (RRAS) to share the Hyper-V host’s physical wireless adapter. Within the settings for the host wireless adapter, create and connect an ad- hoc wireless connection. iii. An external Hyper-V network bound to the Hyper-V host’s physical wired adapter, with a wireless access point (or router in access point mode) connected via Ethernet. b. Connect your mobile device to the wifi network (either ad-hoc or from the access point) 3. Setup mobile device a. On the mobile device browse to http://demo2010a.contoso.com/certsrv/ and download (then install) the CA cert chain Note: You will not be able to setup an EAS mailbox for the b. Use the web browser, Office Hub and/or setup email@example.com an Exchange mailbox on the device as needed. account. Please use one or more of If email autoconfiguration does not find the the other demo user accounts for server the first time, wait a moment and try this portion. again. To connect via Zune software, use the following steps. Tasks Detailed steps 1. Startup the VMs a. Confirm that the Hyper-V host is not connected to any external networks, either wired or wireless b. Startup all VMs using the instructions above c. Login to the “a” Virtual Machine as contoso\administrator d. Open DHCP from Administrator Tools in the Start Menu e. Expand the tree and enable the “Mobile Device” scope 2. Setup connections a. Connect all VMs to a Hyper-V virtual network bound to the Hyper-V host’s physical wired adapter b. Connect a second physical machine running Windows 7 to the wired network. c. Join the Windows 7 machine to the Contoso domain. d. Install and run the Zune software on the Windows 7 machine e. Connect your mobile device to the Windows 7 machine via USB and confirm it is detected by the Zune software 3. Setup mobile device a. On the mobile device browse to http://demo2010a.contoso.com/certsrv/ and download (then install) the CA cert chain Note: You will not be able to setup an EAS mailbox for the b. Use the mobile device browser, Office Hub firstname.lastname@example.org and/or setup an Exchange mailbox on the account. Please use any of the device as needed. If email autoconfiguration other demo user accounts for this does not find the server the first time, wait a portion. moment and try again.
"Virtual Machine Setup Guide _1_"