2. From Zero to Hero on Hyper-V R2 part 2 - 75 minutesThe second part, allows us to focus on installation and configuration. We will also provide some understanding on the Authorization Manager which governs the heart of authorization and access to Hyper-V.
In production environment, it is recommended to install Server Core. Server Core is a minimal server installation option with limited functionality. Normally in Windows OS, you can see all the nice graphical user interface with all the great icon.But in SC, After you login in you will only see black screen – Dos command prompt.No GUI shell is available and you need to enter command line for the confiiguration.In R2 edition, Microsoft has improved server core by including a menu for you to configure certain configuration. Just type the command sconfig.If you still miss the GUI, you can go to CodePlex (Microsoft Open source community) to download Core Configurator.Don’t worry. In today HOL, we have included with Server core so you can play around with command line, sconfig and Core Configurator. It is part of your lab exercise.Hmm…You may ask yourself “ Why should i use SC?”Here is the benefit.Less patches since you install less stuff into the system.Reduce surface attack as less roles installed.More secure
Available after installed in a supported guest operating system such as Win2k3 and above. Integration Services provides 5 unique integration component1. Time synchronization-Keep time synch between parent and guest operating system.2. HeartbeatProvides a mechanism for the parent partition to detect whether a guest OS becomes unresponsive.Eventually parent will send regular heartbeat. If not response, parent will generate an events.3. ShutdownInitiate shutdown from the console without interact with guest OS4. Key/Value ExchangeConsist of predefined key. Used by the Hyper V user interface and 3rd party management tool in order to know more about Child operating system from the parent OS5. VSSAllow to perform backup on entire Hyper V server including online and offline VM
Reset Check Boxes The final user setting can be used to reset settings to the defaults when the Hyper-V Role was installed.Delete Saved Credentials The fourth user setting allows for deleting any saved user credentials on the Hyper-V Server as User Credentials The third user setting addresses what credentials will be used to connect to a virtual machine. The default is to use the same credentials used to open the Hyper-V Management interface Mouse Release Key The setting for the keystroke sequence used to release the mouse from inside the virtual machine. The default is CTRL+ALT+LEFT ARROW
Export UI:Here is a screen capture of the Export UI you get when you right-click on a virtual machine in the Hyper-V Manager and click “Export…” :It is still rather rudimentary and allows the user to specify the location to export the VM to. The VM will be exported along with its VHD files and saved state files to the specified folder. You might notice that the check-box for doing a configuration-only export is not there. This is by design, but we do support configuration-only export. More on this topic in a subsequent blogpost.Exporting a snapshot:To export a snapshot, right-click on the snapshot you want to export (in the snapshots pane that shows up for a selected virtual machine in Hyper-V) and click on “Export…”. It will bring up the Export UI above.Copy on Import: The R2 Import/Export APIs now allow the user to specify a location to import to and not use the import directory as the VM's execution directory. Thus, the user can now create a "gold VM", export it once to a file share and then import it multiple times from that file share. This capability ends up enabling a number of scenarios as a result:a. Backup-restore: For the users who do not want to use a backup application to backup their VMs, they can use import/Export and can restore the same files multiple times. Additionally, they can now have their backup media as read-only.b. Moving/Cloning VMs: The users do not need to do a separate file copy operation in order to move a VM now. They just have to export to a file share and then import it. Additionally, at import time, the user can now specify where to place the VM on the target machine.Export of a Snapshot: Picture this in the v1 days of Hyper-v: Tester Fred is running a number of tests using virtual machines. During the course of the tests, he takes snapshots at different points in time. Now, after snapshot #5 of 20, he sees a bug. So, he would like the developer to take a look at it. However, he would need to export the entire VM and all its snapshots in order to do that. In R2, he can export snapshot #5 as a separate and independent VM and send it to the developer to debug. Additionally, this functionality has enabled another scenario in the IT arena: IT Admin John has a staging environment where he experiments with a number of versions of software in a VM to determine which works best for his scenario. Using R2 Hyper-V, he can create snapshots for each version of the software being tried out. When he determines a version that would work best in his deployment, all he has to do is to export that snapshot and then import it as an independent VM in the production machines.
Import UI:The import UI is launched from the same spot under the Actions pane in Hyper-V manager:In the import UI, check the highlighted checkbox and you will end up copying the VM on import, leaving files in the import directory good for a second import
1. From Zero to Hero on Hyper-V R2 part 3 - 75 minutesAs for Part 3, the content will cover design and planning aspect for deployment. The aspects would include zooming into CPU, RAM, disk storage, and NICs and networks. Best practices and recommendation would be included.