norweg

We are currently setting up the Finance Module in SIMS. As part of the process, we need to configure email using OAuth authentication with Microsoft 365. One of the required steps is to register an application in Microsoft Entra ID (formerly Azure AD). The documentation provided by ESS (SIMS) is not particularly helpful, but after a number of attempts we managed to complete the setup. Authentication is successful; however, when we click "Test Email", we receive the following error: 535 5.7.3 Authentication unsuccessful I raised a ticket with ESS and spent over an hour on a remote support session with them. Their conclusion was that I need to log a support ticket with Microsoft. I have done so, although I am not convinced this is a Microsoft issue, as we have several other app registrations used for email workflows that are working perfectly well. Microsoft's documentation links error 535 5.7.3 to the following possible causes: SMTP authentication not enabled MFA-related authentication issues Azure/Entra security or Conditional Access policies I have ruled out all of the above. Has anyone using the SIMS Finance Module with OAuth authentication come across a similar issue? Changes made: Improved grammar, punctuation, sentence structure, and flow while keeping the technical details and meaning unchanged. The tone is now clearer and more professional for posting on a support forum or sending to ESS.

Hi Paul, You might need to setup profile for your users (on the Mac server) or MDM server (like Jamf Casper). In the "Scope" settings you can narrow it to AD group(s), then in Login Item you add smb://server/share

Actually I use Jamf Casper to deploy package containing script (script to be copied to /Library/LoginHooks), then policy triggers another script to execute "sudo defaults write com.apple.loginwindow LoginHook /Library/LoginHooks/loginhook.sh" once per computer.

We had same problem. We used initially "recommended" mcx redirector for "Caches" folder (redirecting it to /tmp/%username%/Caches. Unfortunately how Apple created this feature - does not work well for many processes - as they require access to Caches folder (read/write). We decided to use loginhook - which creates dynamic link from network "Caches" folder to /Library/Caches/%username% That seems improved performance and stability...

Install Workgroup Manager on a computer where yo've installed those application. Open it (WGM), connect to your server, and then apply restriction on those applications for selected group.

You can try the following link too: iPad cases PIEL FRAMA

Did you think about creating new profile (login) and transfering data including Microsoft User Data (Entourage) to new account. Do you use a parental control to limit what programs can be run (as constant popups asking for permissons are common when parental controll / Only allow selected applications is active). You can also try to run repair disk permissions in diskutility...

Quit Safari. Go to user's /Library folder find subfolder called Keychains and delete file login.keychain

Many OSX applications placed in /Applications folder relay on access to /Library/Application Support folder - therefore allowing /Applications/Aplication name to be run might not be enough if user doesn't have access to /Library/Application support folder. Try to give your users permissions to access /Library/Application Supports/Adobe folder. Hopefully it should help.

Try to follow instruction below. It did work for us: 1. When user who experiences those problems is logged in, quit any "Office" applications 2. Go to that user Library/Preferences folder 3. Delete Microsoft folder 4. delete all com.microsoft.* files 5. Open office application again. Hopefully it should work now without quitting.

In our case – as all classrooms computers are Macs – we: 1. Exported each subject – pupil group to “csv” file (including information about division – set) 2. Imported file to application called “Passenger” – which allows to convert csv file (and add additional information) to format you can import to WGM on OSX server 3. Earlier we prepared groups for each subject as quite subject teachers requested access to specific applications 4. For each group we prepared different default settings (ex. Disabling spell checker, changing look of dock etc.) 5. Every teacher reports at the beginning and the end of session to allow us unlock/lock group account.