Question

Laserfiche - Outlook - Groupwise

Updated November 12, 2014

asked on November 7, 2014

We upgraded our backend to 9.1 a few weeks ago. Only a select few in the county have 9.1 client. We currently use Groupwise as our email server. Had no issues emailing Laserfiche documents until now. .

Today they started pushing out the Office 365. They instructed folks how to activate it and how to configure Outlook but not make it the 'default' email program. Now the fun has started, when folks go into LF to send a document, it is wanting to default to Outlook and not Groupwise. How do I change a users' default email inside of Laserfiche? I thought it uses the default windows email choice... but it is not.

On November 17th we go live with Outlook. Will I need to change all there settings back to Outlook then? We did not know installing Office 365 changed default functions within Laserfiche

Or am I looking at this in the wrong way? Please help. Stuck in limbo.

0 0

Replies

replied on November 7, 2014

How did you check the default email for the workstation?

If you open windows explorer, select any file, right click and send to mail recipient, what email client comes up?

0 0

replied on November 12, 2014

What we have found is that it is an IE setting and not windows. The machines showed GW as it's default... but when you use IE it wanted to default to Outlook. Changing the IE email default made everything work.

Thanks,

Bonnie

0 0

replied on November 12, 2014

Right, the behavior you would get when using windows explorer is dictated by the IE/windows settings which are the same. If the default application that opens when you go through the process above is not the one you want, those are the default settings to check. That process described above is basically the same thing that LF done you when you email a document from client and it opens the Email application

Glad it works for you.

0 0

You are not allowed to follow up in this post.

Question

Question

Laserfiche - Outlook - Groupwise

Replies

Sign in to reply to this post.