|
Posted by cseilern@collins-stewart.com on October 3, 2006, 10:54 am
Please log in for more thread options Hi Chris
I see your point. But as with the castrating of WiFi syncing, I suspect
that MSFT just ticked off more users (who ended using workarounds)
instead of figuring out how to make it open AND secure (how about some
policies?).
Chris De Herrera wrote:
> Hi,
> The reasoning for this limitation is that most companies do not want their
> data copied to another company.
>
> --
> Chris De Herrera
> http://www.pocketpcfaq.com
> http://www.tabletpctalk.com
> http://www.pocketpctalk.com
> http://www.mobilitytalk.com
>
> ActiveSync 4.x Troubleshooting Guide -
> http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm
>
> > As of Activesync 4.x, for some unfathomable reason, MSFT has removed
> > the possibility to sync one device with two exchange servers, or two
> > PC's connected to excahnge servers. This drive me insane when I bought
> > my first WM5 device. But after much googleing, I found a workaround.
> >
> > So, to sync two exchange servers, put this in the device's registry:
> >
> >
[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\EnableNonLocalCrossPollination]
> > = (DWORD) 1
> >
> > This key will most probably be there already, but if it is, its value
> > will be 0. If so, change it to 1.
> >
> > Soft reset, then, setup activesync ON THE DEVICE (If you try setting up
> > on the PC, it will still fail).
> >
> > I'm now syncing an Exchange connected PC with with another Exchange
> > Server directly - work like a CHARM.
> >
> > (thanks to Chris de Herrera for the registry key hint)
> >
| 
XML Sitemap