{"id":69,"date":"2010-05-04T21:40:36","date_gmt":"2010-05-05T01:40:36","guid":{"rendered":"http:\/\/enterpriseadmins.org\/blog\/?p=69"},"modified":"2010-05-04T21:40:36","modified_gmt":"2010-05-05T01:40:36","slug":"p2v-post-migration-cleanup","status":"publish","type":"post","link":"https:\/\/enterpriseadmins.org\/blog\/scripting\/p2v-post-migration-cleanup\/","title":{"rendered":"P2V Post Migration Cleanup"},"content":{"rendered":"<p>I&#8217;ve been doing a lot of P2V migrations over the last few months and wanted to share a couple of lessons learned.  Our environment uses McAfee ePO to centrally manage our desktops and servers.  We noticed that after a P2V migration the agent would no longer be able to communicate with the ePO server.  After doing some searching we located several registry keys that contain Agent keys unique to a specific piece of hardware.  If we delete these keys and restart the framework service clients are again able to communicate.  Additionally, I look through the device manager and remove old devices &#8212; such as network cards that are no longer installed.  Since these steps are repetitive, and I have a large quantity of P2V&#8217;s, I created this simple batch file to help me out:<\/p>\n<pre><code class=\"language-dos\">\r\n@echo off\r\necho This tool fixes keys after a major hardware change - such as a P2V migration\r\n\r\nif %PROCESSOR_ARCHITECTURE% == x86 reg delete \"HKLM\\SOFTWARE\\Network Associates\\ePolicy Orchestrator\\Agent\\Keys\" \/v binap \/f\r\nif %PROCESSOR_ARCHITECTURE% == x86 reg delete \"HKLM\\SOFTWARE\\Network Associates\\ePolicy Orchestrator\\Agent\\Keys\" \/v binas \/f\r\nif %PROCESSOR_ARCHITECTURE% == x86 reg delete \"HKLM\\SOFTWARE\\Network Associates\\ePolicy Orchestrator\\Agent\\Keys\" \/v binrs \/f\r\nif %PROCESSOR_ARCHITECTURE% == x86 reg delete \"HKLM\\SOFTWARE\\Network Associates\\ePolicy Orchestrator\\Agent\\Keys\" \/v binsp \/f\r\n\r\nif %PROCESSOR_ARCHITECTURE% == AMD64 reg delete \"HKLM\\SOFTWARE\\Wow6432Node\\Network Associates\\ePolicy Orchestrator\\Agent\\Keys\" \/v binap \/f\r\nif %PROCESSOR_ARCHITECTURE% == AMD64 reg delete \"HKLM\\SOFTWARE\\Wow6432Node\\Network Associates\\ePolicy Orchestrator\\Agent\\Keys\" \/v binas \/f\r\nif %PROCESSOR_ARCHITECTURE% == AMD64 reg delete \"HKLM\\SOFTWARE\\Wow6432Node\\Network Associates\\ePolicy Orchestrator\\Agent\\Keys\" \/v binrs \/f\r\nif %PROCESSOR_ARCHITECTURE% == AMD64 reg delete \"HKLM\\SOFTWARE\\Wow6432Node\\Network Associates\\ePolicy Orchestrator\\Agent\\Keys\" \/v binsp \/f\r\n\r\nnet stop McAfeeFramework\r\nnet start McAfeeFramework\r\n\r\nif %PROCESSOR_ARCHITECTURE% == x86 \"%ProgramFiles%\\McAfee\\Common Framework\\CmdAgent.exe\" -s -p\r\nif %PROCESSOR_ARCHITECTURE% == AMD64 \"%ProgramFiles(x86)%\\McAfee\\Common Framework\\CmdAgent.exe\" -s -p\r\n\r\nreg delete \"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run\" \/v CPQTEAM \/f\r\n\r\nset devmgr_show_nonpresent_devices=1\r\nstart devmgmt.msc\r\n<\/code><\/pre>\n<p>To make things even easier, I have placed this script in an ISO image on my desktop.  I can easily connect this ISO to the VM and access utilities even if my network connection is not connected.<\/p>\n<p>Other utilities I keep in this ISO image are:<\/p>\n<ul>\n<li>HP Proliant Support Pack Cleaner &#8211; <a href=\"http:\/\/ctxadmtools.musumeci.com.ar\/HPPSPCleaner\/HPPSPCleaner11.html\">http:\/\/ctxadmtools.musumeci.com.ar\/HPPSPCleaner\/HPPSPCleaner11.html<\/a><\/li>\n<li>IBM Director Cleanup &#8211; <a href=\"http:\/\/www-947.ibm.com\/systems\/support\/supportsite.wss\/docdisplay?lndocid=MIGR-5071462&amp;brandind=5000016\">http:\/\/www-947.ibm.com\/systems\/support\/supportsite.wss\/docdisplay?lndocid=MIGR-5071462&amp;brandind=5000016<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve been doing a lot of P2V migrations over the last few months and wanted to share a couple of lessons learned. Our environment uses McAfee ePO to centrally manage our desktops and servers. We noticed that after a P2V &hellip; <a href=\"https:\/\/enterpriseadmins.org\/blog\/scripting\/p2v-post-migration-cleanup\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[3,4],"tags":[],"class_list":["post-69","post","type-post","status-publish","format-standard","hentry","category-scripting","category-virtualization"],"_links":{"self":[{"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/posts\/69","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/comments?post=69"}],"version-history":[{"count":11,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/posts\/69\/revisions"}],"predecessor-version":[{"id":80,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/posts\/69\/revisions\/80"}],"wp:attachment":[{"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/media?parent=69"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/categories?post=69"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/tags?post=69"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}