MS Teams Notifications Missing (macOS)

Teams Notifications KB ID 0001803

Problem

I’ve put up with this for a while, my business pretty much runs on Teams now, so when theres no notification badges on the Teams icon (in the Dock), my response times can be ‘not great‘. In fact, usually I get my head down into a job, and check Teams just to see a ‘ton‘ of messages that need my input. (Some might think that’s a good way to work,) but when you check it at quarter to five, and find an hours worth of extra work, it’s annoying.

Teams Notifications Solution

Within teams > Click the three dots (ellipses) near your user image > Settings > Notifications > Ensure the style is set to ‘Mac’.

Ventua OSX

Click the Apple Icon at the top of your screen >  System Settings > Notifications > Scroll down to Microsoft Teams > Click it.

Make sure ‘Allow Notifications‘ is turned on.

Older Versions od OSX

Click the Apple Icon at the top of your screen >  Preferences > Notifications & Focus > Scroll down to Microsoft Teams > Make sure ‘Allow Notifications‘ is turned on > Make sure ‘Badge app icon‘ is enabled.

Restart MS Teams, problem sorted.

Related Articles, References, Credits, or External Links

Microsoft Teams: Suppress Annoying Message Pop-ups

Microsoft Teams: Custom Background Images

macOS: FaceTime HD Camera Not Working In Microsoft Teams?

Completely Remove Teams From macOS

FirePOWER – ‘DataPlaneInterface0’ is not receiving and packets

KB ID 0001344 

Problem

While replacing a FirePOWER Management console, I got this error;

Interface Status
Interface ‘DataPlaneInterface0’ is not receiving any packets

 

Solution

A look a the health monitor showed me the same thing;

Firstly, common sense dictates, that this is a live firewall and traffic is actually flowing though it? In my case the traffic simply needed to be ‘sent though’ the module. Execute the following, (or check for the presence of matching configuration);

[box]

access-list ACL-FirePOWER extended permit ip any any
class-map CM-SFR
 match access-list ACL-FirePOWER
 exit
policy-map global_policy 
 class CM-SFR
  sfr fail-open
exit
exit
write mem

[/box]

Note: Here I’m assuming you want to ‘fail-open’ i.e. not block traffic if the FirePOWER module fails, and you are inspecting ‘inline’ (not passively).

Then apply the cup of coffee rule, and ensure some traffic is sent via the firewall.

Failover (Active / Standby) Firewalls and FirePOWER

As pointed out (below, thanks Marvin) If you have an active/standby failover firewall pair, you will also see this error from the SFR module in the standby firewall. Which makes sense because this firewall is not passing any traffic!

Related Articles, References, Credits, or External Links

NA

SBS – Alert – ‘The following disk has low idle time’

KB ID 0000583 

Problem

I got this alert forwarded to me, from a client that I’d put in new hard drives for a few week ago.

Alert:

The following disk has low idle time, which may cause slow response time when reading or writing files to the disk. Disk: {Number} {Drive Letter}: Review the Disk Transfers/sec and % Idle Time counters for the PhysicalDisk performance object. If the Disk Transfers/sec counter is consistently below 150 while the % Idle Time counter remains very low (close to 0), there may be a problem with the disk driver or hardware. If the review shows that the disk is functioning properly, use Task Manager to determine which processes are causing the majority of the disk activity. You can attempt to correct the problem by stopping and then restarting those processes. You can disable this alert or change its threshold by using the Change Alert Notifications task in the Server Management Monitoring and Reporting tasked.

Solution

1. It’s telling me review some counters (Start > Run >Perfmon {Enter}). I added in the counters that it asked me to, and sure enough this disk was getting thrashed with a very high disk latency.

2. While discussing it in the office, a colleague suggested I check the BBWC on the RAID card. Sure enough a quick look at the System Management Homepage shows;

4. The battery has failed on the internal E200i RAID card. The server in question was an HP ML350 (G5). So my first thought was to update the firmware for the RAID card, (If for no other reason than it’s the first thing HP would ask me to do, if I logged a call). This did not resolve the problem, so I logged the call for a replacement (The server is under care pack).

5. After fitting, I left it 24 hours for the battery to charge, and checked it again.

Note: Latency has dropped from 1100 to 70).

Related Articles, References, Credits, or External Links

NA