Trying to add a Windows Print Queue sensor fails in PRTG with the error "Generic Failure". Server has the pre-reqs for .Net 4.7.2 and WMI enabled on target server firewall.

Issue due to the Print Spooler service not running on the Probe server. After the service is started then the sensor works as expected.

If your SQL Server’s Model database file gets corrupt then the SQL Server itself will fail to start. You cannot run the usual database repair tools when the server services will not even start.

Fortunately, the Model database is just a blank database used as a template for newly created databases. It can be fixed by replacing the model.mdf and modellog.ldf files in the Data folder in the file in the SQL Server folder "C:\Program Files\Microsoft SQL Server\MSSQLxxx\ MSSQL\Binn\Templates".

Then the SQL Server service should start.

When configuring SCIM provisioning, in Azure AD/Entra you may want to include the sAMAccountName of the user but it is not available as standard from the field selection but can be added with the following steps:

1. Modify ADConnect configuration to include SamAccountName (under Azure AD Connect app -> Customize synchronization options -> enable Directory extension attribute sync -> Directory Extensions -> add sAMAccountName)
2. Do a full sync
3. Create Enterprise App
4. Under Provisioning -> Mapping change user sync setting
5. Add mapping for new field (should be name extension_xxx_sAMAccountName) to whatever SAS app field you want it to populate

Use Provision on Demand to test.

Teams has started displaying some Microsoft Adverts for What's New in Teams and Conferences. This can be annoying to users who just want to use Teams. The latest version of MicrosoftTeams PowerShell has introduced a methods of disabling those messages from being displayed.

To do so first ensure your MicrosoftTeams PowerShell module is v6.1 or higher:

get-module MicrosoftTeams

To update the PowerShell module use command: Update-Module MicrosoftTeams -RequiredVersion 6.3.0 -Force

If updated then restart PowerShell and run the following:

Get-CsTeamsUpdateManagementPolicy -Identity Global

Check what is returned for DisabledInProductMessages

To set run the folowing:

[array]$DisabledMessages = "edf2633e-9827-44de-b34c-8b8b9717e84c", "91382d07-8b89-444c-bbcb-cfe43133af33"
Set-CsTeamsUpdateManagementPolicy -Identity Global -DisabledInProductMessages $DisabledMessages

That should now apply to all tenant users :-)

Thanks to Tony Redmond's Office 365 for IT Pros site for this information: https://office365itpros.com/2024/07/05/in-product-messages/

Microsoft docs for New-TeamsUpdateManagementPolicy: https://learn.microsoft.com/en-gb/powershell/module/teams/new-csteamsupdatemanagementpolicy?view=teams-ps&WT.mc_id=M365-MVP-9501

When exporting a Kace report to Excel it displays the error below:

Error Running Report

Worksheet!X9999 -> Formula Error: An unexpected error occurred

This occurs if the field it is reporting on contains data which starts with a "=" character. This is interpreted by Excel as a formula and if the following data does not contain a valid formula then the error message is displayed.

This can be prevented by editing the data to change the first character from a "=" to another character.