Service Management Automation (SMA) is the next gen IT Automation tool. SMA has some certain advantage over Orchestrator but also some limitations and vise versa. Nevertheless I am taking in consideration that you are aware of these advantages and limitations and you’ve decided to move fully or partially from SCO to SMA. Continue reading “From Orchestrator to Service Management Automation: Migration Scenarios”
Tag: migration
Steps to Migrate Virtual Machines with Shared VDHX from One Cluster to Another
Imagine the following situation: You have two Windows Server 2012 R2 Hyper-V clusters – Cluster1 and Cluster2. Every cluster has two or more nodes. On Cluster1 you have two virtual machines VM1 and VM2. The virtual machines are in guest cluster and are using one or more Shared VHDX files. As you probably know virtual machines with shared vhdx files cannot be migrated with shared nothing live migration. Than how to move VM1 and VM2 from Cluster1 to Cluster 2? Here is a solution for you:
- Logon to VM2. Start Failover Cluster Console. Pause VM2 as node in the cluster and drain all roles.
- Shut down VM2.
- Logon to VM1. Shut down VM1.
- Remove cluster resources for VM1 and VM2 from Cluster1.
- Open Hyper-V console on the node of Cluster 1 where VM1 and VM2 are.
- From the VM settings of VM2 remove all shared VHDX disks. Apply.
- From the VM settings of VM1 remove the checkbox for shared VHDX on all drives where is checked. Apply
- From Hyper-V console move VM1 to one of the nodes of Cluster2.
- From Hyper-V console move VM2 to one of the nodes of Cluster2.
- Now VM1 and VM2 are on Cluster2.
- Open the Hyper-V console on the node of Cluster2 where VM2 is.
- Open VM settings for VM2. Attach all shared vhdx files as disks that you’ve removed in step 6 in the same order as before. Check the checkbox for shared VHDX on all of them. Apply
- Open VM settings for VM 1. Check the checkbox for shared VHDX for all disk that you’ve removed in step 7. Apply.
- Add VM1 and VM2 as cluster resources in Cluster2.
- Start VM1. Check if VM1 is healthy and all resources/roles are up in the Failover Cluster Console.
- Start VM2. Resume VM2 as node of the guest cluster. Migrate all roles and resources to make sure everything is ok.
These are all the steps you need. I hope they will help you.
Microsoft Virtual Academy: Migration to Windows Server 2012
If you are in the path to Windows Server 2012 migration MVA just published videos for you. The course is still not available on MVA site but you can watch the videos:
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 1 – Upgrading to Windows Server 2012
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 2 – Introduction to Tools Part 1
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 2 – Introduction to Tools Part 2
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 2 – Introduction to Tools Part 3
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 3 – Upgrading to Active Directory
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 4 – Migrating WSUS
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 5 – Printing & Document Services
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 6 – Migrating IP Config
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 7 – Cluster Migration
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 8 – Migrating Windows Server 2003 Part 1
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 8 – Migrating Windows Server 2003 Part 2
- Microsoft Virtual Academy: Migration to Windows Server 2012: Module 8 – Migrating Windows Server 2003 Part 3
Upgrade Assessment Tool (UAT) 2012 beta for SCCM 2012 formerly known as Configuration Manager 2007 Application Compatibility Toolkit Connector
Taken directly from MS Connect site:
Microsoft System Center 2012 Configuration Manager Upgrade Assessment Tool is a feature pack download that provides administrative users with information that they can use to determine if the operating system on computers that are managed by System Center 2012 Configuration Manager can be upgraded to Windows 7 or Windows 8. The previous version of this tool was the Configuration Manager 2007 Application Compatibility Toolkit Connector (ACT Connector).
Features:
· Retrieves device driver compatibility for installed peripheral devices and creates reports that you can use to determine which device drivers need to be upgraded to support the Windows operating system.
· Allows you to see which computers meet the recommended system requirements for Windows operating systems and to customize these requirements for your environments.
· Creates summary reports that you can use to see an enterprise wide view of operating system upgrade readiness.
· Allows you to create dynamic collections for an operating system deployment. The collection query rules can be based on system requirements, application compatibility status, and device driver status.
Pre-requisites:
Please note that the Beta version of the Upgrade Assessment Tool requires the ConfigMgr SP1 Beta and the Application Compatibility Toolkit (ACT) 6.0 which is available in the Windows Assessment and Deployment Kit (ADK) for Windows 8.
More information and download link for the tool can be find on Connect site.
Migrating from SCOM R2 CU#5 to OM12. Part III: Pre Upgrade Tasks for Operations Manager by Marnix Wolf
Read the full article here.