Extra configuration is required in only one scenario, and that is if you are using SMB
storage for the target of a storage migration and are initiating the migration remotely,
either through Hyper-V Manager or PowerShell; that is, you are not running the tools
on the actual Hyper-V host, which is the preferred management approach for
Windows Server 2012 because all management should be done remotely using
PowerShell or from a Windows 8/8/1 machine. When you configure SMB storage for
use with Hyper-V, you set numerous specific permissions, including giving the
administrators full control as the person creating a VM on SMB or moving to SMB as
part of a storage migration as their credentials are used. To enable the credential to be
used on a remote SMB file server, constrained delegation must be used, which I
mentioned earlier related to Live Migrations in nonclustered environments. I cover
constrained delegation in detail later.
Storage migrations can be triggered through Hyper-V Manager or through PowerShell,
and there are two options when performing a storage migration. You can move
everything to a single location or select different locations for each item stored as part
of a virtual machine; that is, one location for the configuration file, one for the
snapshots, one for smart paging, one for virtual hard disk 1, one for virtual hard disk 2,
and so on, as shown in Figure 7.36.
Figure 7.36 The different storage objects for a virtual machine
Start with performing the move using Hyper-V Manager, which will help you
understand the options that are possible:
1 . Launch Hyper-V Manager.
2 . Select the virtual machine whose storage needs to be moved, and select the Move