Paralels Desktop Transporter as Startup Item - is this normal?

Leopard 10.5.6,
Parallels Desktop 4
There is also a Bootcamp drive although i have not had any need for it since upgrading to Parallels 4).


I noticed that Leopard lists "ParallelsDesktopTransporter" in its system startup items
(Go to Apple menu - > About this Mac -> Software -> StartupItems)

Is this normal, or am I running a service that got "stuck" there for some reason?

Thx!

 

So... 20 people have read this question and no one can tell if they have same item in their configuration?

Fascinating!

 

Have exactly the same issue/concern.

Under Startup Items,

<
ParallelsDesktopTransporter:

Description: Parallels Link-local IPv4 deamon
Location: /Library/StartupItems/ParallelsDesktopTransporter
Provides: ParallelsServerTransporter
Enabled: Yes
Order Preference: Late >

from a default installation of Parallels 4.0.

I personally have no apparent use for Parallels Transporter, would it be safe to delete it? I do of course wish to retain Parallels Desktop for typical use, I just don't like extraneous components remaining on my system. All the better if it would reduce startup times, and it would be nice to be rid of that entry in the Startup list, if it's not needed. A search for "parallels desktop transporter on startup" turns up a similar, but unanswered, question in the forums.


An additional thought:
I don't quite know what each of the components that are included in a standard Parallels installation are for. I'm not sure if they're described in the installer though, it's been quite a while. Looking at the uninstallation menu provided under Terminal, it seems

<
server
Removes Parallels Server.
desktop
Removes Parallels Desktop.
vitools
Removes Parallels Transporter, Parallels Explorer, Parallels ImageTool.
sdk
Removes Parallels Server SDK.
gtools
Removes Parallels Tools for Mac OS X. >

is more or less a list of the components that are installed with Parallels. I assume "desktop" is the basic application; is it safe to delete any or all of the others?

 

After checking the logs to try and figure out why Mac OS X 10.5 Leopard is taking so long to boot on my 13" Unibody MacBook, I also noticed that ParallelsDesktopTransporter was included in the /Library/StartupItems folder. (Note: I did not have any other Parallels related folders in the StartupItems folder.) So, I took a chance and moved the ParallelsDesktopTransporter folder to a temporary directory with the following command in Terminal:

mkdir ~/temp/
sudo mv /Library/StartupItems/ParallelsDesktopTransporter/ ~/temp/

I then rebooted to see if 1) this breaks Parallels Desktop and 2) if it sped up the boot time. The boot time does seem a little faster, but to be fair I have no concrete data. However, I can confirm that Parallels Desktop does work fine for me.

A little info on my Parallels setup:
* Only have one virtual OS, which is WinXP Pro
* I don't use Parallels Transporter
* Using shared networking
* Adaptive hypervisor is enabled; performance optimized for virtual machine; power consumption optimized for better performance
* Share Max OS X home folder with Windows, but I do not share Windows disks with Mac OS X
* Shared profile enabled
* Shared applications disabled

Hope this helps.

 

in troubleshooting Airport issues, I was just advised to temporarily move the "ParallelsDesktopTransporter" and "ParallelsTransporter" out of my StartupItems folder.

I rebooted and I, too, can verify my install of Windows 7 seems to run fine and access the network ok.

Can someone in Parallels Engineering please give us the definitive answer as to what these executables do and under what circumstances they are necessary?

It seems like this question has gone unanswered back in 2008 for quite some time and have reports others are trashing these processes!

 

ok - I could use the help of someone to help set the record straight - I notice my Windows RC7 install starting having intermittent network problems so I put the ParallelsDesktopTransporter and ParallelsDesktop items back in my StartupItems folder and Internet Explorer is able to open up a web page on boot now.

What I'm a bit confused about is why the Network Diagnostic Tool was able to "fix" the problem somehow and on reboot, why it needs to be "fixed" again.

So apparently, these startup items are not necessary per se as Win 7 can access the internet without them but they do seem to be necessary if you want Windows to work on initial boot.

This what I'm observing so far - if anyone could clear the air - this would be great.