Log in

View Full Version : ActiveSync — Multiple User Accounts in WinXP

Scott Heine
01-15-2005, 04:07 PM
I sync my Pocket PC with my office machine throughout the week. My wife syncs her Pocket PC with our home computer. So far, so good.

However...

We have multiple User Accounts in Windows XP on our home machine — mine, my wife's, and our 3 kids.

When my wife's Pocket PC is in the cradle and I log in, I'm presented with an opportunity to create a partnership with her Pocket PC in my User Account. Obviously I don't want this; I don't want my home desktop to sync with her Pocket PC.

In an ideal world, this is what would happen:

My wife logs in; her User Account syncs with her Pocket PC.

I log in; if my wife's Pocket PC is in the cradle, nothing happens. But if I want to put my Pocket PC in the cradle, I can sync my home PC with the info on my Pocket PC.

My kids log in; nothing happens with either of our Pocket PCs.

So... How in the world do I set this up? Is it possible? I could really appreciate some help here; I can't find any obvious settings in either ActiveSync or the User Account control panel.

Thanks!
Glohamar
01-15-2005, 04:25 PM
AFAIK, there is no way to do this. I have the same set up at my house. I just make sure my ppc is not in the cradle before my wife logs in.


Hey its my 100th post :D
Sc00teR
01-15-2005, 06:04 PM
Hmmm. That stinks. Definitely a feature needed for future versions... :wink:

Well, I wonder if there is a way to disable ActiveSync in every User Profile other than my wife's. That way, she can log in and sync up her Pocket PC, but ActiveSync won't automatically start (and give us the blurb about setting up a guest partnership) everytime someone else logs in on their account.
Vincent M Ferrari
01-15-2005, 07:29 PM
There are a lot of improvements necessary in the Activesync world, and I have to tell you that one is one of the first that should be done. Activesync should be smart enough to know the partnership is already assigned to another user on the same system.

Then again, Activesync should be smart enough to know a lot of things that it doesn't, so I guess we can just add this to the list.