Something that we installed for a customer who had been burned by Exchange (twice) was Workgroupshare. It will share basic Outlook data without too much trouble, and allows for group folders of Contacts, Calendar, what have you. It's not the tightest software, but will do in a pinch and isn't...
The VPN client took a little while for me to get it to work... After a while, I finally figured out all the settings that needed set and so on, what with Diffie-Hellman values, etc, not to mention computer configurations, etc. As of yet, I haven't had a chance to connect via client to the 200...
I've been working with a client's 200R appliance and haven't had too many troubles (after we got it working, having shifted out the old 200's). The only qualm I have with the thing is the software that Symantec includes for client connections. It won't allow any software firewall to coexist on...
Update: I tried upgrading to Office SP-3, but it didn't address the problem. It's a shame, I was certain it would. Q290669 (http://support.microsoft.com/?kbid=290669) states the problem pretty much exactly. Users are starting to get very unhappy...
I've had this really odd problem with an Exchange 2000 server that I've been dealing with lately. We just moved Exchange from an older server to this new one, which is acting as the DC and everything else.
There is a shared calendar that someone owns, but at least two other users contribute to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.