Exchange Support

[sudogreg]

Re: Exchange Support

i would like to turn off autosync for all users, and leave on the autosync for other users on the server where my account is used to login with, i dont want it popping up on mine too. my computer keeps trying to sync for all users basically

[Support Team]

Re: Exchange Support

As you'll be using the same user on the server on your PC they will share the same settings.
While you cannot block it you can manually disable auto-sync for all users while logging into their RangerMSP user accounts and asking them not to enable it. In regards to your account, you can disable auto-syncing too and when logging into the server manually activate the auto-sync for this session.

[sudogreg]

Re: Exchange Support

is this the best way to achieve real-time (or close to it) syncing of tech calendars? i guess it may be best to create a new user dedicated to syncing, but that would again cost us 1 additional CommitCRM license since there would be a dedicated user to sync...

[Support Team]

Re: Exchange Support

Yes, this is the closest option to real-time.
Thanks.

[racassel]

Re: Exchange Support

I have been looking at CommitCRM CRM on and off for three years, waiting to move to Exchange and another CRM from Goldmine. Every time I read up on the Outlook / Exchange integration with CommitCRM I end up deciding to wait another six months. CommitCRM I hope you get it together, the other PSA's are way way too expensive. I like the pricing model, but this one most basic function seems to be lacking, maybe because it drives your web licence sales you hold back? Anyhow, I pass again for now and will take another look in six months, hopefully you will have done something with Exchange, with Office365 now everyone can afford it and CommitCRM needs to catch up. Whats the big deal with 'run as a service'?

[Support Team]

Re: Exchange Support

racassel, thank you for your post. I believe that RangerMSP has so much more to offer... Even if you prefer to have a direct back-end server side Exchange sync instead of syncing with Exchange trough Outlook I still believe that you can really benefit from all of the other options. Anyway, thanks for your feedback.

[lpopejoy]

Re: Exchange Support

also, just to add to the discussion... I'm not sure there would be a way to make direct exchange integration work with hosted Exchange unless you can modify the permissions on mailboxes with your hosted exchange provider. Right?

[raymond]

Re: Exchange Support

the whole CommitCRM exchange sync process would need to be re-written in a way to account for this (hosted exchange). We have not implemented certain features in CommitCRM because of the sync issues... in other words, we only use the contacts sync. Basically what we do is have certain workstations (that are usually on all day with CommitCRM running) sync the contacts to a (contacts) public folder. This public folder is mountable as an address book directly in Outlook (and usable in OWA). We then have implemented a 3rd party application (add2exchange or epicenter) to sync the public folder contacts to a special user mailbox which is then mountable as a secondary address in Windows 7 phones (or iphons or android...). This is ONLY a one way sync as I firmly beleive doing bi-directional sync has the potential for corruption and data lost... (!) We do the sync this way simply because it's the easiest way to get the contacts shared everywhere we need without serverly hacking outlook and exchange...

//ray

[northwestmsp]

Re: Exchange Support

CommitCRM Dev Team: Why not just go with Active-Sync as your Exchange connection? Then it doesn't matter where the Exchange server it hosted, requires no special Exchange configuration and no plug-in or extension to Exchange itself. Native, fast and secure. It works for our mobile phones, it works for many other CRM products, it even works for your competition (ConnectWise & AutoTask). Exchange Active-Sync connection is the ONLY way CommitCRM should even CONSIDER implementing Exchange into it's product line.

[aaspeer]

Re: Exchange Support

+10,000 from me!

[sctelcom]

Re: Exchange Support

We concur: direct sync between CommitCRM and Exchange is needed. We cannot use the CommitCRM calendar because most of our users are laptop, mobile & remote users who need to be in/out in short timeframe. Short of keeping an Outlook instance online constantly for each and every user, CommitCRM currently offers no good way of syncing CommitCRM Calendar with users' Exchange calendars.

We would like to see CommitCRM put development efforts toward this (as would many other CommitCRM exchange users).

Thank you for all you do - please seriously consider this.

[hayden]

Re: Exchange Support

We don't use dispatch for this reason.

[racassel]

Re: Exchange Support

To understand this correctly, CommitCRM would need to be logged in, and running on the server? It won't work with SBS, because you cannot (should not) run Outlook on the same server as Exchange due to Mapi issues. Keeping the application open and running in the server is also an additional security concern. Any possibility of using the tool instsrv.exe and srvany.exe to get around this: http://www.msfn.org/board/topic/8327...-as-a-service?

[Support Team]

Re: Exchange Support

Good question. Though we haven't tried that it seems like it will not work because RangerMSP client requires the user to manually log in - in other words a user interface is involved and services by nature are not designed for GUI apps (though there are some exceptions).

[sctelcom]

Re: Exchange Support

+1 from us again on a true Exchange sync withCommitCRM.

CommitCRM team: What is the development status / road map for Exchange sync feature?

The current work-around is troublesome. I will echo many others here: we use Exchange. CommitCRM needs to make a real sync service.