With the limited numbers of users that we have (70 in total) and
being in Australia we couldn't justify putting in our own Notify
server so we had to go with the hosted method.
This created several problems:
1. all mail had to go to their server and the delay was a problem
with syncing
2. the cost from our mobile carrier ended up being quite high due to
the amount of downloads for each Treo user
3. You had to sync wired users using NotifyLink Desktop Connector
which really sucked. In essence all wired users had to go their
server in another country to sync their own data from our mm server
which belonged in the same office. A bit ludicrous.
4. Registering devices was a hit and miss affair, more miss than hit.
5. If you didn't want email you still got it no matter what you set
on the hosted server.
The list goes on.........
NotifyLink, I think is a great product to enhance your users
experience and I see the benefits of it, but it should have always
been an option and not forced on us as the only way.
When we moved to 8.6 NotifyLink didn't even have the software for Mac
and PC to sync the devices. We had to wait several weeks until the
software was released well after 8.6 was available.
NotifyLink also hadn't tested the software properly so they weren't
able to offer much support initally. After several weeks they were
fine, but initially MM and NL were crap with supporting a product
that they forced onto us.
Subsequently, many users vented their spleen at MM. Some have spoken
openly on the list about going elsewhere and using alternatives,
others have persisted and borne the flack from their own users on
behalf of MM, like I have.
It will be interesting to see what eventuates when Leopard server is
released later this year as to what happens with MM going forward. If
Apple can come up with wireless option for iCal Server then watch out.
Post by Mathew ShemberI am really surprised.
NotifyLink has been great for us. We have had no problems and
their support has been excellent. We have all types of cells......
It allowed us to abolish the Outlook connector which was a real pain for us.
We haven't had the need for palm conduits and probably won't
install them.
Post by Andrew FisherWe had all sorts of problems with NotifyLink as I believe so many
others did.
So when the Palm Conduits were brought back we jumped right in, as
we had already moved over to 8.6. The conduits work so much better
than NotifyLink for syncing as you can sync how you want whether
via USB or Bluetooth and there is not the cost.
NotifyLink will be a great advantage for those users that want to
use it as a future solution but the push from MM and forcing us to
use it was wrong. They have obviously learnt from our thundering
complaints that taking away the conduits was not a good move for
there ongoing viability.
We have now redeployed the Palm Conduits to all Palm users,
(Treos, T|X's, T3's, etc.) and we have not had one problem.
Thankfully, I can now erase the last 4 months from my memory about
the syncing problems that plagued all of us who had to upgrade to 8.6.
Please, MM do not do anything like that again!!!!!
Post by Thomas BetzAs the time-zone issues weren't an issue for us, and as we are
not using the HTML client here, making the use of On Notify
problematic, we chose to stay with 8.53 instead of upgrading to
8.6. Now that the Palm Conduits for 8.6 have been released, and
seeing that some users are wanting to move to Windows-based PDA
phones, I'm considering the upgrade. But I'd need wired Palm
syncing to work from day one.
Is anyone here using the new conduits? Are they as reliable as
8.53's conduits?
Thanks.
--
Tom Betz, System Administrator
Greyston Foundation
Phone 914-376-3903 ext 230
Processing the finest bytes since 1982...
* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/
MMXP-TALK.HTML
* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
TALK.HTML
* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
TALK.HTML
* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML