Office 365 and FMS

[dapaulio]

Watching with interest, I have a school who uses fms and no reports as of yet, however this maybe they haven’t done a run of orders or what ever they call it Edited December 5, 2022 by dapaulio

[Lebowski]

Another with this issue checking in

[Strawdog]

Lancashire have an existing mail relay they are offering schools use of - you have to send them a list of IPs for the machines you want to use it but all our core admin desktops have static IPs already from using Sun Global Desktop over lockdown.

 

That being said I've just left it with staff printing to PDF and manually emailing them

[Mark182]

Our finance team have just logged this issue too

[simonw]

watching with interest.

[geosharp]

Hey,

Short while ago I had a reply from our councils finance helpdesk forwarded to me:

 

"I’ve just received an update from ESS about the case I raised re the BACS e-mailremittance problem.

It looks as though there has been a patch released on SOLUS for you to download.

We are pleased to advise that FMS Autumn 2022Workstation Patch 1 is being made available on SOLUS to resolve the issuesbeing experienced when sending email using Microsoft365 (Office365).

This is being released now and should be available onSOLUS by the end of 07/12/2022. Please run a 'Check for Updates' to pull thisdown.

Once installed to affected workstations this will allowthe sending of emails from within FMS without the errors previouslyexperienced.

Could you ask your technician to try it when he gets the chance and let me know if itsolves the problem."

 

Whilst it not shown up on our SOLUS yet, keep an eye out! Hopefully it does indeed fix it.

Cheers :-)

[Strawdog]

Lancashire (EDS) are testing the patch inhouse before releasing it to schools - I'm pleasantly surprised that ESS patched it that quick.

[geosharp]

Lancashire (EDS) are testing the patch inhouse before releasing it to schools - I'm pleasantly surprised that ESS patched it that quick.

 

Aha, good to know that - i'd always wondered if the local council SIMS teams did any patch testing, good to know they do. Presumably ours is as well and it'll show up eventually.

Cheers :-)

[Michael]

I can confirm this is now working connecting to smtp.office365.com

[DEllinor]

Had an email about the Patch that was released today and we can confirm that it works!

[Lebowski]

Applied the patch last night, all working today

[password1234]

We having this issue with multiple schools, what is the name of this patch exactly? we checked on our solus and there is no patch showing up

called

"FMS Autumn 2022Workstation Patch 1"

unless its called something else?

[simonw]

Is the patch not included in the FMS Autumn 2022 Full Release update

[Chenderit]

We having this issue with multiple schools, what is the name of this patch exactly? we checked on our solus and there is no patch showing up

 

unless it's called something else?

The patch is called "FMS Autumn 2022 Workstation Patch 1 - Remittance slips not sending using Office 365".

[simonw]

It turns out my LA were only releasing the patch to Solus3 on demand, nice of them to mention it.

[chazzy2501]

I had to ask for the patch, I also had to enable "Legacy TLS" in office 365

 

edit:

 

The account being used to email needs to have Authenticated SMTP enabled.

Find the user and open their properties.

Click Mail

Click Manage email apps.

On the list select Authenticated SMTP and save the changes

 

 

Turn on use of legacy TLS Clients needs to be enabled

Go to the Exchange Admin Centre

Click Settings

Click Mail Flow

Click check box next to "Turn on use of legacy TLS Clients needs to be enabled"

Click Save

Edited February 2, 2023 by chazzy2501

[Bankesy]

Joining this thread a bit late and not strictly the same issue but I'm currently migrating from Exchange to O365 and wondering if anybody has FMS working with a genuine shared mailbox rather than a user mailbox that's shared if that makes sense?

 

I thought it best to convert "shared mailboxes" to actual shared mailboxes prior to migration but I don't think this will work with FMS because there won't be a username\password to enter into the FMS setup?

[Michael]

Joining this thread a bit late and not strictly the same issue but I'm currently migrating from Exchange to O365 and wondering if anybody has FMS working with a genuine shared mailbox rather than a user mailbox that's shared if that makes sense?

 

I thought it best to convert "shared mailboxes" to actual shared mailboxes prior to migration but I don't think this will work with FMS because there won't be a username\password to enter into the FMS setup?

 

You can manually specify a password for a Shared Mailbox in O365 Admin - it will work. The username is of course the email address itself.

[Jarv]

We have just started to receive this error despite the workstation fix being applied and Legacy TLS Clients being enabled in Exchange Admin Centre

[Bankesy]

I'm revisiting this and following some of the advice from @chazzy2501 above but I wonder how the Authenticated SMTP part would work in a scenario like mine where the mailbox is shared so doesn't have a license but seemingly a license is needed to enable that setting

[Bankesy]

@Michael

 

In your bodge screenshot, what is the format of the mail server please? I can't figure out what should be there in place of the green highlighting.

 

Is it nameofschool.co.uk.mail.....?

[Michael]

@Michael

 

In your bodge screenshot, what is the format of the mail server please? I can't figure out what should be there in place of the green highlighting.

 

Is it nameofschool.co.uk.mail.....?

 

It's your O365 MX record, but this issue's now resolved with the patch.

[Bankesy]

@Michael

 

I fixed it, the account needed adding as an exclusion to a conditional access policy that blocks legacy authentication.

 

As I had already enabled MFA on the account at the request of ESS I then had to enforce MFA in order to setup an app password, now it works in FMS using the e-mail and app password instead of the Office 365 password.