Author: Bob Lin

Situation: After upgrading to Windows 11 or made change on user account on Windows 11, Surface Touch Keyboard doesn’t show up.

Resolution: enabling touch keyboard and Virtual touchpad. Please follow this post:

• How to enable Touch keyboard and Virtual touchpad in Surface running Windows 11

Situation: After enabling Microsoft MFA or Microsoft Authenticator on Office 365, the user unable to stay signed in to my work account on Teams, Outlook, Office365 for more than 5 minutes.

Troubleshooting 1: Clear the cached password

1. Sign out from Office application and close all the Office applications opened on your system. To sign out, open any Office application, let’s say Word, click File>Account>Sign out.

2) Open Control Panel>User Account>Credentials Manager>Windows Credentials>Delete all MicrosoftOffice16 and MicrosoftOffice15 credentials.

3) After deleting the cached password, open Word and click File>Account>Sign in and enter your Office 365 log in credentials. Try to sign in to Skype for business as well, see if this is resolved.

Troubleshooting 2: Reset MFA

1. Login Microsoft 365 admin center.
2. Navigate to Users>Active users. Highlight on the user who has the problem.
3. Click on the multi-factor authentication.
4. Click on Manage user settings.

5. Check Delete all existing app passwords and generated by the selected users.

Situation: After creating a default email group, we can’t edit with This requested group is invalided.

Troubleshooting: Login Microsoft 365 admin center. Go to Health>Service Health>. Check the issues.

Situation: The client keeps getting a “Custom Dictionary Not Available” message when adding words to Outlook Dictionary.

Troubleshooting: Please follow these steps:

1. Open Outlook and select File and choose Options.
2. Select Mail in the left pane of the window.
3. Choose Spelling and Auto correct button.
4. Select Proofing and Custom Dictionaries.
5. Set CUSTOM.DIC as the default.

Get back to us with the result.

Situation: the client is internal company and has migrated their multiple domains into a Microsoft Tenant. Now, they have an issue to send emails between domains. For example, A.com and B.com are under the same Tenant with default domain name C.com. Email sent from A to B was blocked.

Cause: They encountered this issue during the migration of A.com and B.com to C.me. Although I am not entirely certain about the reason, I have a theory. Both A.com and B.com are under the Microsoft Tenant. When A.com sends an email to B.com, Microsoft Intelligent Assistant (which is not as intelligent as a human) mistakenly identifies the email as spam and blocks it.

Resolution: Add A.com, and C.com to whitelist. Please refer to these posts:

What’s allows and blocks in the Tenant Allow/Block List

How to add email address to Whitelist in Office 365

Troubleshooting:

1. The user/group may not have access to LAN subnets. In our case, the client adds All Interface IP instead of LAN Subnets. We fix the problem by replacing All Interface IP with LAN Subnets.

2. The SSLVPN IP Pool is in the same subnet as X0.

If your computer display has these issues:

• A blank or black screen.
• Color fade.
• Fuzzy, blurry, distorted, stretched image.
• Geometric distortion.
• Light leakage or bleeding.
• Flickering.
• Horizontal or vertical lines.
• Light or dark patches.

Try these suggestions:

1. If you have two or more displays, compare them settings.
2. Check Display Settings by going to Advanced display and check the refresh rate.

Situation: The client try to access their SonicWALL Global VPN, but it shows Connecting forever.

Troubleshooting: It seems like Peer IP or name issue.

Go to Properties>Peers>, click on Edit.

Uncheck “Use the default gateway as the peer IP address”. Then enter the peer’s IP address, which should be the SonicWALL WAN IP address.

Situation: When running PowerShell command:

Connect-MicrosoftTeams

you may get this error:

Connect-MicrosoftTeams : The term ‘Connect-MicrosoftTeams’ is not recognized as the name of a cmdlet, function, script

file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct

and try again.

At line:1 char:1

+ Connect-MicrosoftTeams

+ ~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : ObjectNotFound: (Connect-MicrosoftTeams:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

Resolution: Uninstall and re-install early teams PowerShell Module:

Uninstall-Module MicrosoftTeams

Install-Module -Name MicrosoftTeams -RequiredVersion 1.0.0

Situation: When running Import-Module MicrosoftTeams PowerShell command, you may receive this error:

Import-Module : File C:\Program Files\WindowsPowerShell\Modules\MicrosoftTeams\5.8.0\MicrosoftTeams.psm1 cannot be
loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ Import-Module MicrosoftTeams
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [Import-Module], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess,Microsoft.PowerShell.Commands.ImportModuleCommand

Resolution:

Your PowerShell Execution Policy might be preventing Import-Module from running successfully. Try running:

Set-ExecutionPolicy -ExecutionPolicy AllSigned -Scope Process

This will allow all signed scripts to run in the current PowerShell process. When you close the PowerShell session, you will revert to your previous Execution Policy.

If the module is still not successfully importing, you might try:

 Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process

Be cautious about this setting, since it will allow any unsigned scripts to run, including potentially malicious code. Ensure that you trust the script/modules you’re installing if you choose ExecutionPolicy Bypass.