Recently we have seen issues with VMware Vcenter and Host Update not working as expected. Error like the one below may be displayed when attempting to update hosts:

Cannot download VIB: ''. This might be because of network issues or the specified VIB does NOT exist or does NOT have a proper 'read' privilege set. Please make sure the specified VIB exists and is accessible from vCenter Server.

VMware have recently changed their update processes to require the download URLs for Vcenter and Host updates to be changed to include a unique download token.

This token can be generated by accessing the Broadcom Support portal. You will need product administrator role to be able to generate the token.

Once generated it can be applied to various VMware products using the knowledge article below:

VCF authenticated downloads configuration update instructions - https://knowledge.broadcom.com/external/article/390098

Finally, a group policy to remove Windows default store apps!

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.