Hyper-V 3.0 --- Copied VM is working in another Hyper-V 3.0 Server (part 3)

In Hyper-V 2.0, we have to export VM so that we can re-create the VM and attach the VHD when disaster happens in the future. Before do the export VM, we also have to shutdown this VM so that the related Service in this VM will be stopped then. This mechanism is not smart and the function is less than VMWare Product.

Since Hyper-V 3.0 release, we just only point to the path with the associated VM files so that VM can be live after power on.
How to do it?
Copy the backup VM files to the default folder that store VM configuration files in Hyper-V 3.0 Server. (# 1)
Open Hyper-V Manager and click one Hyper-V Server that will locate his VM next to click Import Virtual Machine linkIn Before You Begin page, click Next > buttonIn Locate Folder page, click Browse… button
Select the specify path that with xml file next to click Select Folder buttonClick Next > button to go ahead next step if the folder containing the VM is rightIn Select Virtual Machine page, select the VM that will be imported next to click Next > buttonDue to the VM and its files have already been in the right place, we will choose Register option that just want to register VM’s unique ID with Hyper-V. After choosing the import type, click Next > button to go ahead the next step.So do that we will complete the Import Wizard.Now the imported VM will exist in this Hyper-V Server.
Start this VM by click Start link in Actions panelNext to click Connect … linkThe imported VM will be live and normal now.
Reference :(# 1) How to know the default path to store VM configuration files?
          In Hyper-V Settings, click Virtual Machine in Server item so that can see where it is.

<<<   Hyper-V 3.0 --- Create NIC Teaming after Hyper-V online (part 2)

 Hyper-V 3.0 --- One-Way Replication between Non-Cluster Hosts on the same AD domain (part 4) >>>

Microsoft Access Database Engine 2010 Redistributable --- No 64 bit ODBC Drivers in Windows 7 x64

In Windows 7 x64, the default Data Source(ODBC) will point to 64 bit DLL in “C:\Windows\System32”. If we want to run 32 bit Apps on 64 bit Windows 7, we need to use 32 bit ODBC Administrator Tool by launching “C:\Windows\SysWOW64\odbcad32.exe”. (# 1)

When we launch ODBC Data Source Administrator and want to configure Excel Files in User DSN tab,
we get an error message “Cannot find Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb) ODBC driver”.
Although I know use the different ODBC administrator to configure 32bit or 64 bit DSN setting (#  1), I don’t when 64 bit ODBC driver for Office 2010 miss. In my intuition, the solution is very simple that reinstall ODBC driver!
So I download AccessDatabaseEngine_x64.exe from Microsoft Download Center(# 2) and double-click this file for installing it. But the warming message show up “Cannot install it besides remove the 32 bit installation of Office products firstly”.I don’t want to follow its suggestion because it will spend more time to remove and reinstall Office.
I search Web information by Google and find out it can be resolve by adding passive switch. The full command line is AccessDatabaseEngine_X64.exe /passiveAfter finish the above command and redo the ODBC configuration, its function is normal now.

Reference :
(# 1) Unable to create DSN for Microsoft Office System Driver on 64-bit versions of Windows
(# 2) Microsoft Access Database Engine 2010 Redistributable