Topic: MS Exchange vs SME Calendaring

[hainsnet]

Hi.

I have a client with a reasonable server (HP ML350) that constantly crashes with Windows SBS2003 despite rebuilds, MS patches, firmware updates etc etc. I am looking to move them across to SME as a more stable environment as I believe that its SBS 2003 causing the issue.
Whilst I can easily move data and email etc across, is anybody able to advise me about migrating shared calendars across from SBS 2003 to SME? This is the most heavily used feature on their Windows server and cannot afford to lose it's functionality.

Greg

[byte]

Moving this topic to the SME Server 7.x  contribs forum, it is more appropriate there. Thanks!

[dmay]

Greg,

For what it's worth, here is my sagely advice...

You state have a client that already has SBS2003 and is having problems. So...fix it. You imply that you feel it is not hardware (are you sure?) and that you have done everything you feel you can. If this is the case then seek external assistance. I'd recommend you go direct to Microsoft:

http://support.microsoft.com/common/international.aspx?rdpath=1&gprid=3208

One pay per incidient support call should solve your/their problems.

Bottom line. I support many Microsoft and SME installs. When installed and configured correctly, Microsoft products are just fine.

Darrell

[hainsnet]

Hi Darrell,

Thankyou for your response. I hear you re the MS issue, but I have been working on this daily for months now - problem is getting worse. I have already worked with Microsoft who have offered numerous patches and ideas none of which have unfortunately resolved the issue - they have pushed it back to HP saying its a hardware/firmware issue. HP have also tried for roughly the same period with no luck either.

The local HP engineer (through 6 HP logged jobs) has replaced the CPU, tested RAM thoroughly, replaced the mainboard, and run extensive hardware diagnostics on the box and found not a single hiccup. As a result I am pretty sure (under these circumstances nobody can guarantee anything...) Having said this, HP came back to me yesteray and said that the engineers "overseas" have identified a fault in this area, but can provide no more information - re problem, nor resolution.
Anyway, I wont fill up the SME forum with this history.

Thats the background anyway for my situ. So you cant advise on the compatibility of moving shared calendars from Exchange to SME? I just feel this is my next option to resolve this for the client is to swap out the less "proven' product (hardware vs software).

Cheers,
Greg

[dmay]

Less proven? I expect there are a couple of thousand SME installs and a couple of million Microsoft installs.

Swapping hardware sounds cheaper then 'working on this daily for months'.

Bottom line is nothing matches the full feature set of Exchange/Outlook on SME. Why give your client less features then what they have already bought and purchased?

Darrell

[hainsnet]

Darrell,

I should have made myself clearer. I didnt mean that SBS 2003 wasn't proven in terms of it's operating coverage around the world, but more about what we can definitely prove here and now on the spot as the problem with this setup. It's not my first choice to swap out the OS like this with a Linux product, but after months of havoc and an increasingly disgruntled client, it may be one of my best options. As I recommended the setup in the first place I am absorbing all the costs myself as I feel responsible for this mess.
After dumping many logs and running diagnostic tools for both companies, both Microsoft and HP say they don't know what the problem is. Time to start with a clean(er) slate.

Anyway. Thanks for your input on this matter.

Cheers,
Greg

[p-jones]

hainsnet

I faced your exact same situation and dilemma 18 months but for different reasons. Even after considering Groupoffice, which is in my view, the best of the groupwares to put on SME, we went back to SBS2003. Stability hasnt been an issue, nor was it ever part of the original equation. The SBS runs month in and  month out without faltering, 10 users connecting 6 days a week.

To cut to the chase, In my humble opinion, I would have to agree 110% with the advice dmay has given you. (and I am not a serious microsoft fan)

If you do need to migrate it to a new box, a task which is not for the feint hearted, Google for Jeff ??? Swing-It migration Kit. It has a cost but it is worth every cent of what he charges for it.

[frederikbay]

Have to agree with p-jones, GET the Swing-it migration kit worth every cent!

And exellent support if you have a problem.

Frederik

[girkers]

Just another thought, is load SME and load SBS2003 in a Virtual Machine on the SME server. Just a different tacted.