Storage migration of VMs can be performed as one step easily using either the Failover Cluster Manager in Windows 2012 R2 or VMM . However, migrating a VDI deployment that consist of a collection of virtual desktops is far more complex and there is no direct way to do the migration yet !
when you try to edit the deployment properties to change the storage location, you will be able to change certain configuration but not all of them, for example you can change the location of the users profiles but not the location of the parent disk of the image/template used to create the collection,
so to do the migration, you will need to create a new collection.
so here what I needed to do to migrate my VDI deployment :
1- Copy the master VM/Image used to create the collection to the new storage
2- Copy the users profiles vhd files (if your deployment use them) in a temp folder
3- Drop the existing collection
4- Create the new collection based on the Image you copied
5- Move the users profiles vhd files to the new storage location
Note: it is important to use the same template, otherwise users might have problems loading their profiles .
when you try to edit the deployment properties to change the storage location, you will be able to change certain configuration but not all of them, for example you can change the location of the users profiles but not the location of the parent disk of the image/template used to create the collection,
so to do the migration, you will need to create a new collection.
so here what I needed to do to migrate my VDI deployment :
1- Copy the master VM/Image used to create the collection to the new storage
2- Copy the users profiles vhd files (if your deployment use them) in a temp folder
3- Drop the existing collection
4- Create the new collection based on the Image you copied
5- Move the users profiles vhd files to the new storage location
Note: it is important to use the same template, otherwise users might have problems loading their profiles .
