Situation: When upgrading Veeam v9.5 to V11, the client has an issue with SQL 2016 database. They re-installed it by changing the SQL instant name from VeeamBackup to VeeamBackup2. The installation was successful.
However, they can’t create a backup with The wait operation timed out.
Troubleshooting: Changed the database name back to VeeamBackup instead of VeeamBackup2. To do that, open Veeam Backup and Replication Database Connection Settings.
Situation: Since WFH, more users WFH. However, VPN users can’t call each other using Softphone.
Resolution 1: Make sure VPN client can ping each other. If not, make sure GloablProect has VPN route setup correctly. Go to Network>GloablProtect>Gateways>Agent>Client Settings. in our example, 10.144.0.0/16 is VPN Client IP Pool.
Resolution 2: Make sure you have VPN Inbound and Outbound policy under Policy>Security. For example
Situation: When installing Windows update, you may receive this error: Error 0X800F0982.
Resolution 1: Running the Windows Update Troubleshooter
tart by opening up a Run dialog box by pressing Windows key + R. Next, inside the text box, type “ms-settings-troubleshoot” and press Enter to open up the Troubleshooting tab of the Settings app.
2. Resetting the Windows Update component and Clear the SoftwareDistribution Folder
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver
If ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old
commands don’t work, you can delete them from C:\Windows
3. Force the installation of the update via Powershell
Run this command:
‘wuauclt.exe /UPDATENOW‘
4. Start the Windows Modules Installer Service
Start the Windows Modules Installer Service by running this command:
‘SC config trustedinstaller start=auto’
Then restart the computer and try to install the update again
Situation: When the user login Office 365, he receive this message: “Your organization doesn’t allow you to update your password on this site. Please update it according to the method recommended by your organization, or ask your admin if you need help”.
Troubleshooting: You may need to dismiss user risk. To do that, login Azure. Search Dismiss user risk. Or go to Security>Risky users.
Highlight the user and click on Dismiss user(s) risk.
Situation: The client can’t login Microsoft 365 with this message: your sign in was successful but does not meet the criteria to access this resource
Troubleshooting: You may need to dismiss user risk. To do that, login Azure. Search Dismiss user risk. Or go to Security>Risky users.
Highlight the user and click on Dismiss user(s) risk.
Situation: The client uses Office 365 to send Mitel voicemail, Scanned documents to email, and setup some applications to send email notifications. They don’t work anymore. All venders refer to Microsoft article: How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 – https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365 . Following the instruction, they can’t make it work.
Troubleshooting: They need to follow this article:
to enable Basic Authentication on organization level.
If that doesn’t fix the problem, check this article:
to make sure the account they use also enable SMTP authentication.
Situation: When installing or uninstall Relius Administration, you may receive this message: Relius Administration key exists in registry, but could not determine the version.
Resolution: Delete Relius registry key by go to regedit.
Situation: You just take over the ownership of a folder, you can’t access some files under the folder.
Troubleshooting: when you take the ownership of the folder, some files are using which don’t allow you take the ownership. So that you need to do it again when no one use them.
Situation: The client finds some of their users can’t see other users’ profile pictures. For example, Outlook shows the profile picture but not Teams. Or Teams at home PC can see the picture but not in the office PC.
Resolution: This is cache issue. Quoted:
After user attributes are updated in Microsoft Teams, users continue to see the old information in the Teams client. User attributes include information such as display name, telephone number, manager, and profile photo.
This behavior is by design.
Teams has a caching scheme that is designed for capacity and performance optimization. The Teams service caches general user information for up to three days. The Teams client also caches general user information locally. Some data, such as display name and telephone number, can be cached up to 28 days in the client. Profile photos can be cached up to 60 days.
Relaunching Microsoft Teams may fix the problem.
2. Click on Sign Out.
3. Re-login Teams.
Situation: The client has a problem to install Windows Update KB5015811 with Updates failed and retry. .
Troubleshooting: If this is a new Windows Update, you could wait for a while.
“Windows Updates usually eventually sorts them out, but it has to scan 1.5 billion PC’s every few days so it can get behind and may take awhile to sort them out as to priority, or process the telemetrics to adjust the update to avoid failure.. So you can ignore it and not micro-manage updates if they are not bothering you”
Or refer to this post: