[zenkinz]

one of the problem that I get after migrating to Vista is getting Activesync to work using bluetooth. For some reason, Windows Mobile Device Center (WMDC) that's installed separately from Vista, doesn't allow bluetooth synchronisation to work especially if either your desktop or mobile device is running on widcomm bluetooth stack. Selecting 'Bluetooth' in the WMDC's connection setting doesn't work, at least for me. This is because while my mobile device detects my desktop via bluetooth, it cannot determine there's an activesync service (i.e. WMDC) running in the background in the desktop. In the good old days of Activesync, all I need to tell activesync to 'listen' to a bluetooth com port. There's no such ability in WMDC.

This registry hack, to be applied to your desktop pc/laptop, enables WMDC to bind to a bluetooth virtual com port (as you set this com port as the incoming port). Go to \HKLM\Software\Microsoft\Windows CE Services, modify the value name "SerialPort" from "Bluetooth or Infrared" to "COM4", where COM4 is the virtual com port associated to your bluetooth incoming com port. The number varies from desktop to desktop, so choose the right com port for your specific use.

[nostromos]

lets take a look on the problem:
1.-my ppc (qtek 2020, windows mobile 2003, windows bt stack)) connects with my pc (vista ultimate,widcomm 5 bt stack). that means no problem on both bt stacks
2.-no connection on wmdc via bt, even configuring it to accept bluetooth connections, but no problem via usb cradle. that means no problem with vista firewall.
so, lets think about: when i connect ppc bt, some services appears on pc bt: activesync, obex, voice gateway... But wmdc works over serial port. Resuming: wmdc needs SERIAL PORT. ppc offers ACTIVESYNC. More problems: activesync software allows to choice com port to connect bt to. wmdc not.
SOLUTIONS:
1.-as i ve read on the net: modify registry values , so we can tell wmdc which com port must be used to connect bt. this com port must be the same one assigned to activesync service when ppc is connected to pc bt stack. in my case: COM5. So, a bit of regedit, look for HKLM\software\microsoft\windows ce services\serial port, and change value, which is usually bluetooth, writting COM5 instead (or whatever com port you have assigned to your activesync service).
then save, close regedit and reboot pc. reconnect ppc and let bt stack add new bt devices so we can reconfigure bt ppc services in order to:
2.-this is my finding: once ppc found, go to select which services we want to use on bt, select activesync and click over configuration. in the new window, you can change the name of the service, that obviously is activesync and put a new name: Serial Port. click accept and finalize and voila!!!. open wmdc on pc, open activesync on ppc, click on connect using bluetooth and youll see how wonderfully wmdc connect with your ppc.

[zard]

Iive been looking over the net and looking for this answer and now I've finally found it here.

I've tried it out and only thing I find I cannot do was the part was the renaming of service from activesync to Serial Port. Anyway, after a few tries on my WM5 ppc, I was able to connect through BT.

With WMDC 6.1 out now, I've not tried it yet. Will update later.