Situation: When attempting to reset your office 365 password, you may receive this message: You can’t reset your own password because password reset isn’t turned on for your account. You must contact your administrator to turn on password reset for your account.

Resolution: Have your administrator to enabling self-service in Office 365. Please refer to this post:

How to enable office 365 self-service password reset?

Situation: The client attempts to join a remote computer to their domain over GlobalProtect. They can join the computer to the domain. However, they can’t login using domain account after restarting the domain computer because the GlobalProtect VPN is off.

Troubleshooting and cases.

Case 1: If you lock the PC, instead of the switch user option, it does not disconnect GP and will allow you to log into the domain account.

Case 2: Cache the domain account by Run different user.

• Keep GP conncted.

• Run an application, for example PanGPA.exe > shift+right clicked > Run as different user.

• Now, try to login the domain account without VPN.

3. Cache the by mapping a domain network drive.

4. Add Windows Credentials manually.

Run Credentials Manager>Windows Credentials>Add a Windows credentials.

If you’re experiencing issues with AutoCorrect in Outlook, here are some troubleshooting steps you can try:

1. Check your AutoCorrect settings: Go to File > Options > Mail > Spelling and Autocorrect for spelling issue.

Go to Editor Options for editor issue.

Make sure that the “Typing replace selected text” option is selected and that the correct language is chosen. You can also review and edit the list of AutoCorrect entries in the “AutoCorrect Options” section.

Go to File>Options > Mail and select Editor Options. Select Proofing> AutoCorrect Options. On the AutoCorrecttab, select or clear Replace text as you type.

2. Disable third-party add-ins: Sometimes third-party add-ins can interfere with AutoCorrect. To disable them, go to File > Options > Add-Ins. In the “Manage” dropdown, select “COM Add-ins” and click “Go”. Clear the checkboxes next to any third-party add-ins and click “OK”.

3. Repair your Office installation: If the issue persists, try repairing your Office installation. Go to Control Panel > Programs and Features, select Microsoft Office, and click “Change”. Choose the “Repair” option and follow the prompts.

4. Disable Exchange cache by going to File>Account Settings>Change.

5. Run Outlook.exe /safe for a test.

6. Repair the PST File.

• First, open your Outlook folder in File Explorer.
• That folder path could be this one on 64-bit Windows:Program Files(x86)/Microsoft/OfficerootOffice
• Or this one on 32-bit platforms:Program Files/Microsoft/OfficerootOffice
• Then click the scanpst.exe to open the Outlook Inbox Repair Tool window.
• Press the Browsebutton to select your PST file.
• Enter Outlook.pst in the Windows search bar if you’re not sure what folder the PST file is in.
• Click the Startbutton on the Outlook Inbox Repair Tool window to fix the PST file.

6. Reset your Outlook settings: As a last resort, you can try resetting your Outlook settings. Note that this will reset all Outlook options to their default values. To do this, close Outlook and navigate to %LOCALAPPDATA%\Microsoft\Outlook. Rename the Outlook.xml file to Outlook.xml.old and restart Outlook.

The error message “Failed to send notification using server/device Resolution state: Closed” suggests that the System Center was unable to send a notification to a server or device due to a closed resolution state.

There are a few steps you can take to troubleshoot and resolve this issue:

1. Check the notification settings: Ensure that the notification settings are configured correctly in the System Center. Check if the notification channel is set up properly and if the server/device is correctly identified.
2. Verify server/device connectivity: Verify if the server/device is reachable from the System Center. Check if there are any network or firewall issues preventing the System Center from connecting to the server/device.
3. Check the resolution state: The error message indicates that the resolution state is closed. Check if the issue that triggered the notification has been resolved. If the resolution state is closed, the System Center will not send any further notifications.
4. Restart the System Center services: Try restarting the System Center services to see if it resolves the issue. This can sometimes clear any temporary issues that might be causing the notification failure.
5. Review logs: Review the System Center logs for any errors or warnings that might be related to the notification failure. This can help identify the root cause of the issue.

If these steps do not resolve the issue, you may need to contact Microsoft support for further assistance.

Situation: One of our users can’t login GloablProtect and gets DUO Authentication failed error.

Troubleshooting: When we check the user logs, we see Location Unknown and No Response.

Case 1: It sounds to me like you may have changed some device settings with your Android phone that caused the Duo Mobile app to deactivate, and you should be able to authenticate again once you follow the steps to reactivate the app.

Case 2: I have the same problem after disabling the account of DUO-PROTECTED  on the DUO app.

This could be the cache issue. To clear Auto-Complete list, please follow these steps:

1. Go to the File tab and choose Options.
2. In the Outlook Options dialog box, select the Mail tab.
3. To turn off autocomplete, go to the Send messages section. …
4. If you want to clear the auto-complete cache without disabling the feature, select Empty Auto-Complete List.

Alternatively, we can disable Exchange cache and re-enable later,

 

Case 1: login DUo.com and check the report. In our case, the phone is no response because of location unknown.

 

Other possible resolutions:

1. Check your internet connection: Make sure you have a stable internet connection and that your device is connected to it. A weak or unstable internet connection can cause authentication failures.
2. Check your Duo account status: Make sure that your Duo account is active and that you have not reached your authentication limit. If you’re unsure, contact your organization’s Duo administrator.
3. Check your device settings: Make sure that your device’s clock is set correctly, as an incorrect time can cause authentication failures. Also, check that your device is not in airplane mode or in a location with poor reception.
4. Try a different authentication method: If you’re using a specific authentication method, try a different one, such as using a passcode instead of a push notification.
5. Clear your cache and cookies: Clearing your cache and cookies can help fix any issues related to data corruption. Try clearing your browser’s cache and cookies and then attempt to log in again.
6. If your smartphone does not seem to be getting the DUO Push after Two(2) tries, select OTHER OPTIONS, and choose another authentication option such as DUO Mobile Passcode or Text message passcode.  This will prevent your account from being locked after Three(3) failures.
7. Contact support: If none of the above steps work, contact Duo support for further assistance. They can help diagnose the issue and provide a solution.

I hope this helps, and good luck!