Parallels Forums
> Desktop Virtualization Products Discussion > Parallels Virtual Tools > Parallels Transporter  
Parallels Transporter Build 1038 is available for download  
  

Parallels Transporter Build 1038 is available for download

Dec 1, 2006, 10:23 AM
#1  
STim's Avatar

STim
Parallels Team


Join: Mar 2006
Posts: 831
Parallels Transporter Build 1038 is available for download
Hello all!

Now you can migrate your Windows PC, VMware or Virtual PC Virtual Machines to Parallels Virtual Machines.

You will need Parallels Transporter Beta for this. The Mac version is bundled into Parallels Desktop for Mac Beta Build 3036. The Windows version containing both Parallels Transporter and Parallels Transporter Agent can be downloaded from here.

1. Usage models.

* Migrate remote Windows PC over network directly to VM on your Mac/PC
1) Install Parallels Transporter Agent on your Windows PC you would like to migrate
2) Run Parallels Transporter on your Mac/PC
3) Migrate using few easy steps of Wizard

* Migrate Windows PC locally or to any removable media and move the resulted VM to Mac/PC
1) Install both Parallels Transporter and Parallels Transporter Agent on your Windows PC you would like to migrate
2) Run Parallels Transporter on that Windows PC
3) Migrate using few easy steps of Wizard
4) Deliver the resulting virtual machine to Mac/PC using any removable media

* Converting VMware Workstation/Server or Microsoft Virtual PC VMs to Parallels Desktop/Workstation-compatible format and move resulting Virtual Machine to Mac/PC
1) Install Parallels Transporter on your Windows PC
2) Run Parallels Transporter
3) Convert VM using few easy steps of Wizard
4) Deliver the resulting virtual machine to Mac/PC using any removable media

2. Supported OSes.

Parallels Transporter Agent is the provider which allows online migration of Windows PC:

* Windows 2000
* Windows XP
* Windows 2003

Parallels Transporter is the application which finally creates Parallels virtual machines:

* Windows 2000
* Windows XP
* Windows 2003
* Windows Vista (experimental support)
* Mac OS X

We are extremely interested in your feedback - please share your thoughts or technical issues to beta@parallels.com mailbox.

Best regards,
Tim and all the Parallels Team

----------------
Download links:
Parallels Transporter for Windows Beta and Parallels Transporter Agent for Windows Beta - http://download.parallels.com/beta/P...0.1038-Win.exe

Parallels Transporter for Mac Beta (bundled with Parallels Desktop for Mac Beta Build 3036) - http://download.parallels.com/beta/P...0.1038-Win.exe
Reply 
Dec 1, 2006, 05:03 PM
#2  

innerfire
Junior Member


Join: Dec 2006
Posts: 5
Ok, downloading the agent to my legacy virtual pc was a long process. I hate even loging in there. But, I got it downloaded, turned on the agent, and then tried to find the computer via my new computer. I am migrating from a g4 powerbook to a new imac. They are networked. Getting the pc to show up, I don't know how to do. Any suggestions?
Reply 
Dec 1, 2006, 05:11 PM
#3  

palter
Senior Member


Join: Apr 2006
Posts: 245
Quote:
Originally Posted by innerfire
Ok, downloading the agent to my legacy virtual pc was a long process. I hate even loging in there. But, I got it downloaded, turned on the agent, and then tried to find the computer via my new computer. I am migrating from a g4 powerbook to a new imac. They are networked. Getting the pc to show up, I don't know how to do. Any suggestions?
What style of networking is your VPC configured to use? I don't remember the VPC terminology off hand but in Parallels-speak, you'd probably need to configure it in Bridged mode so it'll have its own IP address. Otherwise, it'll be hiding behind the Mac and you won't be able to see it.

__________________
MacBook Pro (Core 2 Duo) 15", 3GB RAM, 160GB HD, 10.4.9
VMWare VMs: Win XP (x64, 512MB), Win Vista (x64, 1GB), Win 98 (128MB), Fedora Core (x64, 1GB)
Parallels VMs: None
Reply 
Dec 1, 2006, 11:30 PM
#4  

GeezerGeek
Junior Member


Join: Oct 2006
Posts: 6
I downloaded and installed the beta with no problems. Then I imported a Winddows 98 image from Virtual PC. The import went fine, and it booted. As expected, it wanted the Windows CD for drivers. Oops - no CD drive. I tried giving it a real CD, as well as an image, on both IDE channels. Windows simply does not show a CD in the system. I suppose this could be due to the need for a new driver for IDE devices, but it's pretty much a show stopper. I'm going to try going back to Virtual PC and copy the CD to a virtual hard drive, which I'll then convert with Transporter, and finally use to get the necessary drivers.
Reply 
Dec 2, 2006, 09:03 AM
#5  

pjb
Junior Member


Join: Dec 2006
Posts: 4
success?
Quote:
Originally Posted by GeezerGeek
... I imported a Winddows 98 image from Virtual PC. ...
GeezerGeek, would you mind detailing your process so those of us who were not successful can see what did work? (at least for the import step)

Thanks.
Reply 
Dec 2, 2006, 09:08 PM
#6  

James Bond 007
Senior Member


Join: May 2006
Posts: 159
Quote:
Originally Posted by GeezerGeek
I downloaded and installed the beta with no problems. Then I imported a Winddows 98 image from Virtual PC. The import went fine, and it booted. As expected, it wanted the Windows CD for drivers. Oops - no CD drive. I tried giving it a real CD, as well as an image, on both IDE channels. Windows simply does not show a CD in the system. I suppose this could be due to the need for a new driver for IDE devices, but it's pretty much a show stopper. I'm going to try going back to Virtual PC and copy the CD to a virtual hard drive, which I'll then convert with Transporter, and finally use to get the necessary drivers.
Yes, you should go back to Virtual PC and copy the contents of the Win98 folder on the Windows 98 CD onto the Windows 98 VM. Then after you "transported" and Windows 98 ask for drivers just point to that folder and 98 should then load the necessary drivers.

I always copy the Win98 folder to the hard disk and install 98 by running setup from that folder when I need to install Windows 98 on a PC or in a VMware VM on my PC. That way the install process is much faster (compared to running Win98 setup from the CD) and 98 will know where to get drivers from "CD" later. I guess it is just the same in Parallels even though I have not tried it myself yet.



__________________
When there is a will, there is a way.
Hope for the best. Prepare for the worst.
Reply 
Dec 3, 2006, 12:54 AM
#7  

Hugh Watkins
Senior Member


Join: Jul 2006
Posts: 976
my old notebook has no cd burner


could I use a usb hard disk as the medium?

or connect via a lan or a crossover cable?

It sounds like another killer app
it would have saved me buying an OEM windows cd

as long as it preserves the original MAC number ???


Hugh W
Reply 
Dec 2, 2006, 12:31 AM
#8  

largestgasman
Junior Member


Join: Dec 2006
Posts: 1
I am trying to migrate a VPC7 version of XP on a G5 tower to a MBP and failing.
I'm finding the documentation a bit obtuse.

Can you help me understand?

I installed Transporter on the VPC version of XP, selected "Express" mode then "from virtual computer" and directed it to the VHD of my XP installation located in the documents/virtual pc list folder of my macintosh HD. Is this the correct target?

Once I had done this I selected "migrate" then "boot from it" when prompted. At this point, clicking on "next" has no effect in that no migration occurs.

If I click "Use data from it" instead of "Boot from it" at this stage the whole operation is aborted.

Do I have the wrong end of the stick here?
Can anyone explain the process a bit more for me?
Reply 
Dec 2, 2006, 09:01 AM
#9  

pjb
Junior Member


Join: Dec 2006
Posts: 4
same problem
Quote:
Originally Posted by largestgasman
...I installed Transporter on the VPC version of XP, selected "Express" mode then "from virtual computer" and directed it to the VHD of my XP installation located in the documents/virtual pc list folder of my macintosh HD. Is this the correct target?

Once I had done this I selected "migrate" then "boot from it" when prompted. At this point, clicking on "next" has no effect in that no migration occurs.

If I click "Use data from it" instead of "Boot from it" at this stage the whole operation is aborted.
...

I had exactly this problem only 1. I used Win2kPro and 2. I have two (nearly identical) virtual machines and directed the installer to the .vhd file of the one that was not running.

Thoughts?
Reply 
Dec 2, 2006, 04:26 AM
#10  

leonsio
Junior Member


Join: Sep 2006
Posts: 3
does it posible to migrate VmWare (Fusion) Images to Parallals format running it on MacOSX
its a nice feature but useles on macintosh, because i need allways a windows PC zu install transporter on it :(
Reply 
Dec 2, 2006, 11:06 AM
#11  

pjb
Junior Member


Join: Dec 2006
Posts: 4
unable to initialize
This also did not work:

connect the mac to the virtual PC Win2Kpro (running with it's own IP) at a shared folder, run PT Agent on the virtualPC, run PT on the mac and use the VPC IP address as the source. This ends with the message "Unable to initialize data on the source computer" and the VPC OS reports a program error. Where would I find that log file?

Update: got as far as seeing the VPC in the list of options but then received the error "We have no active OS which can be reconfigured as default. Select disk and partition for capturing data without reconfiguring" but in the next pane the list of volumes is empty.
Reply 
Dec 2, 2006, 11:55 AM
#12  

don montalvo
Senior Member


Join: May 2006
Posts: 111
can parallels transporter be used to convert a parallels windows image over to my new bootcamp partition?

don

__________________
don montalvo, nyc
curmudgeon at large
Reply 
Dec 2, 2006, 06:02 PM
#13  

morwen
Junior Member


Join: Jul 2006
Posts: 22
upgrade from build 1970?
I've been having trouble upgrading for several builds now, the only way I could get them to work was to uninstall Parallels and reinstall the new version. It always found my old Parallels vm of XP.

This new beta I tried to upgrade to, it failed as has been usual for me. I uninstalled build 1970 and then installed the new beta, but it doesn't seem to see my Parallels vm of XP. Its still in Library/Parallels...how can I get this to work?
Reply 
Dec 2, 2006, 06:44 PM
#14  

innerfire
Junior Member


Join: Dec 2006
Posts: 5
Transporter Error
OK, I logged into Virtual PC, and used the transporter locally to create the parallels files. I then copied them to my new computer, and tried to fire them up. The version of XP boots from the get go, but my mouse is now not able to controll anything within the window, so I can't log in. I can have parallels capture my mouse, but then I can't move within the xp world. I've tried installing a USB controller and re-booting via the back end. Help!
Reply 
Dec 3, 2006, 06:37 PM
#15  

innerfire
Junior Member


Join: Dec 2006
Posts: 5
Quote:
Originally Posted by innerfire
OK, I logged into Virtual PC, and used the transporter locally to create the parallels files. I then copied them to my new computer, and tried to fire them up. The version of XP boots from the get go, but my mouse is now not able to controll anything within the window, so I can't log in. I can have parallels capture my mouse, but then I can't move within the xp world. I've tried installing a USB controller and re-booting via the back end. Help!
As an update, I was able to get the mouse to work together, when I switched to full screen mode. I then logged in, had roughly 20 minutes of good working time, installed the parallels scrips, and then restarted the computer. It was amazing, the mouse worked perfectly after I installed the scripts, however, I ran into a major problem. Now the keyboard can't be recognized. I've since tried makeing the system work in several ways, but the keyboard is not interacting with the PC. Help. Ideas?
Reply 
Dec 4, 2006, 12:40 AM
#16  

antblog701
Junior Member


Join: Nov 2006
Posts: 13
I successfully imported the Virtual PC disk image (Windows 2000) to Parallels. Let me add a few detail...
It's Windows 2000 Pro under Virtual PC 7 for Mac, and migrated to Parallels Desktop for Mac.

Just to provide some basic steps on what I did...
  • Install Parallels Transporter and Parallels Transporter Agent on your source PC (under Virtual PC for Mac).
  • Uninstall Virtual PC Additions, then reboot. (this is very important, otherwise you won't be able to boot up the imported virtual machine.)
  • I also changed the Network Setting to "Virtual Switch" (I am not 100% certain if this is necessary, but it works better in a number of situations with this setting.)
  • In your Windows PC, launch Parallels Transporter Agent, make sure the Virtual PC is connected to the local network.
  • In your Intel-based Mac, launch Parallels Transpoter, and follow the on-screen instruction.

Hope this helps.

__________________
AntBlog701: http://ant.sillydog.org/
Reply 
Dec 4, 2006, 01:06 AM
#17  

constant
Senior Member


Join: Mar 2006
Posts: 1,043
.
antblog701,

That would be a good post for the how to forum.
.
Reply 
Dec 18, 2006, 03:50 AM
#18  

gmankono
Junior Member


Join: Dec 2006
Posts: 1
Follow-up: success - VPC to Parallels XP image
I'll post to the how-to board as well, but I wanted to quote antblog, since the specifics mentioned here were the keys to my success, both in using the Windows Transfer tool, as well as to getting the Mac Transfer tool and Windows Transfer Agent combo to work.

Initially, I just used the Windows Parallels Transporter to create a Parallels disk image that I then coped to the target Intel iMac, and I was able to boot the virtual machine, though Mouse Synchronization was clearly not working. I was able to log in to the XP environment, though networking was not working, and drivers could not be installed (the only discs available in this installation case are the original Virtual PC install discs, which do NOT include a standard XP installation disc, which leaves a re-installation near impossible, without transfer tools). I was able to run the Parallels Tools installation, but once complete, the mouse and keyboard input to the virtual environment did not work at all.

The key, in reviewing the post quoted here, is the section that details that the "Virtual PC Additions" need to be uninstalled. If they are not uninstalled, there are clearly conflicts between the Virtual PC additions, and the "Parallels Tools" that offer similar benefits and the actual drivers for the virtualization environment. After restarting the Virtual PC machine after the uninstallation, the mouse synchronization in the VPC environment was off, but I was still able to run the Windows Parallels Transporter to create a new Transporter1.hdd and accompanying winxp.pvs file set, which I copied to the Intel iMac, and was able to successfully boot, run the "Install Parallels Tools..." installer, and get working keyboard & mouse input, working video drivers, and working networking.

HUZZAH!!! Success, especially in this case, before the actual deadline, is very sweet.

The other important detail in the original post is that to get the Mac Parallels Transporter to recognize a Virtual PC "machine" running the Parallels Transfer Agent (Windows) is to make sure that the VPC machine is set to use Virtual Switch networking instead of Shared networking. Once I shut down the VPC VM, set the networking to Virtual Switch, started the VPC VM, and started the Parallels Transfer Agent, the Intel iMac running the Mac Parallels Transfer app was able to "see" and start an import of the VPC VM.

I made a backup of the original, working, bootable file set I got from the Windows Parallels Transfer app, but hopefully the Mac Transfer app will be smart about asking where to save the file it creates, rather than overwriting the "working" VM I have in place.

Currently, I'm very happy I can get this machine in place without having to find or purchase a new XP install disc, since the original license with Virtual PC is valid.

Happy Transferring,

G

:cool:

Quote:
Originally Posted by antblog701
I successfully imported the Virtual PC disk image (Windows 2000) to Parallels. Let me add a few detail...
It's Windows 2000 Pro under Virtual PC 7 for Mac, and migrated to Parallels Desktop for Mac.

Just to provide some basic steps on what I did...
  • Install Parallels Transporter and Parallels Transporter Agent on your source PC (under Virtual PC for Mac).
  • Uninstall Virtual PC Additions, then reboot. (this is very important, otherwise you won't be able to boot up the imported virtual machine.)
  • I also changed the Network Setting to "Virtual Switch" (I am not 100% certain if this is necessary, but it works better in a number of situations with this setting.)
  • In your Windows PC, launch Parallels Transporter Agent, make sure the Virtual PC is connected to the local network.
  • In your Intel-based Mac, launch Parallels Transpoter, and follow the on-screen instruction.

Hope this helps.
Reply 
Dec 16, 2006, 11:15 AM
#19  

mcsenerd
Junior Member


Join: Nov 2006
Posts: 20
I started a seperate thread about the mouse and keyboard issues in converted VPC machines. I think there are still issues with fully removing the MS Virtual Machine Additions from the VPC Machine prior to converting...because I followed that routine exactly and yet there still remain conflicts between the mouse and keyboard drivers when running in Parallels.
Reply 
Dec 17, 2006, 05:48 PM
#20  

Geesu
Member


Join: Dec 2006
Posts: 52
So whenever I try to run this on my windows xp machine (I want to create an image of that computer to transfer to my mac) it builds a pretty large file - sometimes about 70% completion - then it errors with:

"The operation of migration has been aborted. To migrate later run Parallels transporter once again. Click Finish to exit."

I've ran it about 6 times and still nothing. Is there a way to get a more detailed error report?

Thanks,
Josh
Reply 


12>

Thread tools Display modes
Hybrid Mode