Emails are sent to Quarantine even the sender’s email address has been added to allow list

Situation: Emails sent by an internal email address have been moved to quarantine even the sender’s email address has been added to allow list in Anti-Spam.

Troubleshooting: Use the Microsoft Message Header Analyzer, we find the emails have been moved to quarantine because Anti-Phish policy. Please refer to this post:

The resolution is to add the sender’s server IP address to PHISH policy by following these steps:

  1. After login Microsoft 365, go to Microsoft 365 admin center > Security > Policy & rules.

2. Click on Threat policies

3. Click on Anti-Spam policies.

4. Click on Connection filter policy (Default). Then add the IP address which is the sender’s IP address.

 

Using Microsoft Message Header Analyzer to troubleshoot email issues

Situation:  The client uses office 365 for their email. They would like to know if Microsoft offer any tool for them to troubleshoot email issues such as quarantine, not deliverable.

Resolution: Yes, one tools is Microsoft Message Header Analyzer. this post shows how to use it based on a quarantined email.

  1. Login Office 365.
  2. Go to Microsoft 365 admin center.
  3. Click on Security.
  4. Click on Review.
  5. Double click on Quarantine to open it.

6. Open the quarantined and click on 3 dots. Then click on View message headers.

7. Copy message header.

8. Click on Microsoft Message Header Analyzer.

9. Read the report carefully. in our example, the problem is Protection policy: PHISH.

 

 

 

PDF file opens in Microsoft Edge when saving or convert a PDF file

Situation: Whenever the user exports or print word document to PDF, the PDF open Microsoft Edge.

Cause: In the most cases, the PDF Properties is setup Microsoft Edge as default app.

Resolution 1: Right click on a PDF file -> Propertied -> Open with > Choose another app -> Select adobe.

Resolution 2: Settings -> Apps -> Default Apps -> Choose default apps by file type -> select .pdf -> select Adobe.

Resolution 3: If above 2 resolutions don’t fix the problem, switch default Internet browser to other browser such as Chrome or Firefox.

QNAP doesn’t delete Recycled files automatically

Situation: The client a QNAP TVS-871 as backup storage. It is out of the spaces because the QNAOP doesn’t delete Recycled files automatically.

Resolution 1: Making sure that the Control Panel is configured correctly

  1. Log in to your QNAP device using an internet browser.
  2. Go to Control Panel.

3. Click on Network Recycle Bin in Network & File Service

4. Make sure File retention time is set to meet your requirement, 4 days in our example.

Resolution 2: This issue may be caused by interactions between the File retention time setting and the Antivirus utility. To resolve this issue, use the following steps to exclude the @Recycle folder from antivirus scans.

  1. Log in to your QNAP device.
  2. Go to Control Panel > Applications > Antivirus.

3. Go to the Scan Jobs tab.

4. Identify an antivirus scan job.

5. Under Action, click the Edit Scan Job icon.

6. The Details window opens.

7. Go to the Filter tab.

8. Select Exclude files or folders.

9. Enter /*/@Recycle

Veeam Backup: Agent failed to process method

Situation: The client has Veeam backup to back up all their VMs on Microsoft Hyper-V. The backup failed with this error: Agent failed to process method.

Troubleshooting: That could be hardware or services’ issues. Please refer to these posts:

Veeam backup: Failed to upload disk

Situation: The client has Veeam backup to back up all their VMs on Microsoft Hyper-V. The backup failed with this error: Failed to upload disk.

Troubleshooting 1: It could be physical server low RAM. Please refer to this article for RAM requirement.

Troubleshooting 2: It could be the hard disk issue. Please run chkdsk: /f /x /r to check and fix it.

Troubleshooting 3: Modify SkipBadBlocks settings on Registry.

1. Open up regedit.
2. Locate the Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup
3. Add the following new DWORD: SkipBadBlocks and change the value to 1.
4. Close regedit, open up the services.msc console, and then restart the Veeam Agent for Microsoft Windows service.

Troubleshooting 4: It could be system time issue. Quoted from Veeam website:

Cause

The Veeam Backup Service uses a system of timed leases to monitor the many processes it manages. Usually, this error involves a five minute lease for the VeeamAgent processes (Data Movers). When the Veeam Backup Service is operating normally, this lease is continually renewed. If the lease expires, the associated process is shut down.

Typically the lease will expire either because the system time has changed by several minutes, or because a problem communicating with the Veeam Backup Configuration Database has prevented the Veeam Backup Service from renewing the lease.

Solution

On VMware virtual machines, the VMware Tools will periodically synchronize the system time with the ESXi host. If the time on the host differs from the NTP server used by the Guest OS, the system time will repeatedly shift between the two different times. The best solution is to synchronize the time between the ESXi host, the Veeam Backup & Replication server and/or the domain controllers with the same source. If this is not possible, you could disable VMware Tools time synchronization on the Veeam Backup & Replication server.

Troubleshooting 5: Restarting Veeam services may fix the problem.

 

Veeam Backup: Shared memory connection was closed

Situation: Some users has Veeam backup to back up all their VMs on Microsoft Hyper-V. The backup failed with this error: Shared memory connection was closed.

Troubleshooting 1: It could be physical server low RAM. Please refer to this article for RAM requirement.

Troubleshooting 2: It could be the Hard Disk issue. Please double check it or run chkdsk /f /r command to check and fix it.

Troubleshooting 3: In another case, the user uses a USN external drive to be the backup storage. We don’t recommend using external USB as a backup storage. However, if this is workstation and you have to use USB drive, you may try to upgrade the USB driver. Also, if the USB is FAT32 or exFAT format, it is not a good choice for a backup target. Perhaps, you can format as NTFS.

Troubleshooting 4: Run VSSadmin to check any errors? Please refer to this article:

Troubleshooting VSS Writers timeout or failed error

Troubleshooting 5: To fix it, follow these steps :
1) Open Backup & Replication
2) Open your properties (top left corner)
3) Network Traffic
4) Check the number near “Use multiple upload streams per job”. Endpoint need at least 3 streams to work.

If the RAM is not the issue, restarting Veeam services may fix the problem.

 

Veeam Backup: Unable to allocate memory for storage metadata bank

Situation: The client has Veeam backup to back up all their VMs on Microsoft Hyper-V. The backup failed with this error: Unable to allocate memory for storage metadata bank.

Resolution 1: It could be physical server low RAM. Please refer to this article for RAM requirement.

Resolution 2: If the RAM is not the issue, restarting Veeam services may fix the problem.

Resolution 3: Check the status of Windows update. If there is any windows update installed or pending for restart, please do so.