I made some additional tests as well with MobileMe.
I reset Mobile Me synching (unregister all Mac, delete all server data,
re-register first Mac, sync, re-register second Mac deleting all
computer data and replacing with MobileMe data, sync).
It was hell!!! I got notifications of hundreds of modifications at the
second sync, lost some keychain entries...
The problem with all that is that synching remains buggy on both sides
of the aisle. I suspect MS still has some issues (and your problem
illustrates it) and Apple still does too :-@
Corentin
--
--- Mac:MS MVP
http://www.cortig.net/wordpress/---
http://www.mvps.org -
http://mvp.support..microsoft.com
MVPs are not MS employees - Les MVP ne travaillent pas pour MS
Remove "NoSpam" to e-mail me - Retirez "NoSpam" pourm'écrire
Right on. I don't might much working in one module at a time. It’s
just a hassle. Why I got those dups of all day events might have had
something to do with testing two or more modules at the same time.
When I do this, but I really don't unless there might be some
possibility its still working, oddly enough all day events in the
calendar about 3 months back to the beginning of calendar dup.
Fortunately, since I categorize everything I just find non categorized
items, delete Entourage calendar in iCal and let the combine method in
Entourage rebuild the Entourage cal in iCal. Generally, everything
works flawlessly as long as I don't enable too modules at the same
time. Over on the Markspace forum, numerous people are doing this now.
One guy wrote me the other day to thank me for this tip as he was
spending hours, like I was in the beginning, trying to make it work.
I'd go nuts with what you described happened to me but I don't use
mobileme. I really was never getting my value out of .Mac as I just
wasn't using enough of their services and the backup program had a
terrible time restoring the Entourage DB. So after 4 years of having
it, I've gone to other services and I'm way happier.
I just don't understand how Microsoft can't deal with this issue. I
was corresponding, finally, with a manager who went directly to BU and
they said they knew of the problem but weren't sure when it will be
fixed. Its been 8 months now and I don't see any progress. I always
check in with tech support on my original Jan 24 08 case # and they
have no answers. The scary thing is many of them often say if it will
ever be fixed. My understanding from Markspace is it has something to
do with Entourage's data architecture and when you enable more than
one module it causes conflicts and thus the mess. They identified it
to Microsoft way back when but have still heard nothing. They though
it was fixable but were concerned, as they have a good working
relationship with MS, as to why they were hearing nothing and still
have heard nothing.
Anyway, they kept telling me to work the with the workaround I
accidentally discovered as they discovered this at about the same time
in their labs. So that's about as much as we know. All vague.