http://www.windowsitpro.com/authors/author/author/5015169/rsscomment/5015169en-USSun, 27 May 2012 03:28:27 GMTSun, 27 May 2012 03:28:27 GMThttp://www.windowsitpro.com/article/windows-server-20082/bill-hilf-discusses-trends-in-microsoft-s-server-platform-strategy#commentsAnchorFri, 08 Apr 2011 05:30:47 GMT
That’s a really red shirt]]>will hicksFri, 08 Apr 2011 05:30:47 GMThttp://www.windowsitpro.com/article/windows-server-20082/bill-hilf-discusses-trends-in-microsoft-s-server-platform-strategy#commentsAnchorhttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorWed, 21 Oct 2009 09:54:02 GMT
Hi James, Here’s a thought: If you’re doing a P2V for NT4, Win2k or WinXP from a single (ie. UNI) core processor to a multi-core processor (ie. MP), you may need to replace the virtual machine’s HALs (and a couple other files) if you virtual machine has multiprocessor support. Here are some links: NT: http://support.microsoft.com/kb/142660 XP: http://incore.net/winxp-multicpu/ From what I understand, Vista and Win7 can auto detect the number of processor cores and manual intervention is not required. Regards, Bret]]>BretWed, 21 Oct 2009 09:54:02 GMThttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorhttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorSun, 19 Jul 2009 14:28:21 GMT
Jared & James, There is a missing step in the above How-to. After you are done with the steps that are on Page 1 of this article you need to also complete this command: copy c:\winpe-x86\winpe.wim c:\winpe-x86\iso\sources\boot.wim, Then Y This needs to be executed prior to the oscdimg command for the changes that you did to the winpe.wim to be copied to the ISO file. I found this when attempting to add defrag.exe to a WinPE file and it was also useful when doing my P2V migration with Ghost. Post back if you have any questions.]]>JoshuaSun, 19 Jul 2009 14:28:21 GMThttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorhttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorTue, 14 Jul 2009 11:05:14 GMT
James, The only way I know of checking the contents of the WIM file is by mounting it to a temp directory. If I do that then the answer is "Yes" the Ghost32.exe file IS listed under \Windows\System32. I installed daemon tools however when I mount the ISO I see only the CDROM files/folders: BOOT, EFI, SOURCES, BOOTMGR.]]>jaredTue, 14 Jul 2009 11:05:14 GMThttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorhttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorMon, 13 Jul 2009 17:48:05 GMT
jaredt - the oscdimg command just makes use of whatever is contained within the WIM file. Can you double-check that the ghost32.exe is definitely being written to the WIM file using the /commit command? Another thing to check is to mount the created ISO with Daemon Tools to see whether the file was written to the ISO - let me know how you go.]]>JamesMon, 13 Jul 2009 17:48:05 GMThttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorhttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorFri, 10 Jul 2009 15:43:17 GMT
You guide was fairly straight forward and simple however when the WinPE iso boots ghost32.exe is not loaded. If I "dir" the X:\windows\system32 folder its not listed but if I mount the c:\win_pe folder back on my pc I can see the file is in the directory. Why would it should in the directory but not get copied over when I call the oscdimg command?]]>jaredFri, 10 Jul 2009 15:43:17 GMThttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorhttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchorWed, 08 Jul 2009 23:34:51 GMT
Looks rather complicated. I too wanted to perform a P2V from a workstation and found a method from this site: http://easterndigitalsoftware.com/p2v/p2v.htm that performed perfectly using Ghost. There is the extra step of copying it to MS Virtual server 2005, but it is only momentarily done and can be copied to HyperV and configured.]]>JamesWed, 08 Jul 2009 23:34:51 GMThttp://www.windowsitpro.com/article/migration/crash-course-in-p2v-migration#commentsAnchor