Packt+ | Advance your knowledge in tech

You're reading from Windows Server 2016 Hyper-V Cookbook Save time and resources by getting to know the best practices and intelligence from industry experts

Product type Paperback

Published in Jan 2017

Publisher Packt

ISBN-13 9781785884313

Length 524 pages

Edition 2nd Edition

Languages

PowerShell

Tools

Hyper-V

Concepts

Servers

Authors (4):

Nemnom

Leandro Eduardo S Carvalho

Lownds

Leandro Carvalho

View More author details

Table of Contents (19) Chapters

Windows Server 2016 Hyper-V Cookbook - Second Edition

Credits

About the Authors

Acknowledgments

www.PacktPub.com

Customer Feedback

Preface

1. Installing and Managing Hyper-V in Full, Server Core, and Nano Server FREE CHAPTER

2. Migrating and Upgrading Physical and Virtual Servers

3. Managing Disk and Network Settings

4. Saving Time and Cost with Hyper-V Automation

5. Hyper-V Best Practices, Tips, and Tricks

6. Security and Delegation of Control

7. Configuring High Availability in Hyper-V

8. Disaster Recovery for Hyper-V

9. Azure Site Recovery and Azure Backup for Hyper-V

10. Monitoring, Tuning, and Troubleshooting Hyper-V

Hyper-V Architecture and Components

Index

Converting physical computers to virtual machines

Every day we can see companies implementing virtual servers to explore virtualization benefits such as cost reduction, flexibility, automation, and so on. That's why physical to virtual migration is still very common and it's important to make sure that the existing servers running under old and unnecessary hardware can be converted into virtual machines. In this recipe, you will see how to convert a physical server into a virtual machine using the tool Disk2vhd.

Getting ready

Disk2vhd is not a default Windows tool and it has to be downloaded from the following link: http://technet.microsoft.com/en-us/sysinternals/ee656415. The minimal operating system for client conversions is Windows Vista and for server versions is Windows Server 2008. Also, you need to pay attention to the implications caused by licensed software applications such as OEM operating systems.