Author: Bob Lin

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!

The error message “Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off” usually indicates a problem with a roaming user profile on a Windows system. Here are some steps you can follow to troubleshoot and fix this issue:

1. Check the network connectivity: Make sure the computer is properly connected to the network and that there are no network issues that might prevent the user’s roaming profile from being loaded.
2. Check the permissions on the user’s profile folder: Verify that the user has full permissions to their roaming profile folder on the server. If the user does not have the correct permissions, Windows may not be able to load the profile.
3. Delete the user’s temporary profile: Sometimes, Windows may create a temporary profile for the user, which can cause the issue. To fix this, log in as a different user with administrator privileges, navigate to C:\Users, and delete the temporary profile folder for the affected user. Then, log in as the affected user again and see if the issue is resolved.
4. Check the user’s registry entries: Check the registry entries for the user’s roaming profile to make sure they are correct. To do this, log in as a different user with administrator privileges, open the Registry Editor, and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Find the registry entry for the affected user’s profile and check that the value for the “ProfileImagePath” key is correct.
5. Re-create the user’s profile: If none of the above steps work, you may need to re-create the user’s roaming profile. To do this, log in as a different user with administrator privileges, delete the user’s profile folder on the server, and then have the user log in again to create a new profile.

By following these steps, you should be able to resolve the issue of Windows not being able to find the user’s local profile and logging them on with a temporary profile.

A “554 Message Not Allowed” error typically occurs when an email server rejects an incoming message. This error message indicates that the recipient’s mail server or email account has blocked the email, usually due to spam or other security concerns. Here are some steps you can take to troubleshoot this error:

1. Verify that the email address you are sending to is correct and active. Ensure that there are no typos or other errors in the email address.
2. Check the content of your email message. Make sure that your message is not spam or contains any suspicious content that may trigger the recipient’s spam filter.
3. Check your IP address reputation. If your IP address has a poor reputation due to past spam or security issues, it may be blocked by the recipient’s mail server. You can use online reputation tools like SenderScore or MXToolbox to check your IP address reputation.
4. Contact the recipient to check if their mail server is experiencing any issues. It’s possible that the recipient’s mail server is down or experiencing other issues that prevent it from accepting incoming messages.
5. Try sending the message from a different email account or service. If the issue persists, you may need to contact your email provider or IT department for further assistance.

Situation: We received many New detection such as Action taken: Endpoint detection, process would have been blocked if related prevention policy setting was enabled. Sensor hostname: ANDREW02 Endpoint detection URL: https://falcon.us-2.crowdstrike.com/activity/detections/detail/6fa1575720ae43248d15e104d0e69a80/738776163848 Endpoint detection status: New File path: \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\ig-1.exe Last behavior timestamp: 2023-02-03T14:26:18Z Sensor platform: Windows OS version: Windows 11 Behavior objective: Falcon Detection Method Local IP address: 192.168.1.149 Severity: Informational User ID: S-1-5-21-876873567-1263676363-868425949-5726 User name: Andrew Behavior timestamp: 2023-02-03T14:26:18Z See in Falcon. Do we need to do anything to stop this alert?

Resolutioin 1: The detection is for an Informational detection which is the lowest confidence event as to being malicious. You are seeing these because your settings for Sensor Anti-malware in your prevention policy is set to the following:

Detect is set to Extra Aggressive which triggers the detection and the Alert Prevention is set to Aggressive which does not act on Informational detections

You can either lower your detect to Aggressive to not detect informational events or you can increase your Prevention to Extra Aggressive to act on the informational detections.

Resolution 2: We have identified the reason for the email alerts on Informational detections. These are being generated due to the Fusion Workflows you currently have configured. https://falcon.us-2.crowdstrike.com/workflow/fusion Please disable or modify these workflows to stop the emails being generated on your account.

Situation: A recipient doesn’t receive an email. When the Exchange admi checks the status using Microsoft 365 message trace, it shows Expanded.

Troubleshooting:

Expanded status in the Microsoft 365 Message Trace result means the email was rejected by a recipient’s mail server due to a spam filter or Exchange rule or policy.

Note: When a message trace is performed, the results will typically show a summary of the delivery status, such as “Delivered,” “Failed,” or “Pending.” However, by expanding the result, administrators can view more detailed information about the delivery, including any error codes that were generated and the specific steps taken by the email delivery system to attempt delivery.

Situation: the client can’t turn his laptop on. When turn it on, we can see the hard disk light on and power light on. however, we can’t see the screen.

Resolution 1: Disconnect the battery or power and press the power button for 30 seconds. Try it again.

Resolution 2: Check the display connection.

Resolution 3: Reset hardware.