My Windows Updates recently couldn’t update the Azure File Sync Agent v14.1 to any newer version of it (running on the lab-Domain-Controller). Important to know: I did a Inplace upgrade from Windows Server 2019 to Windows Server 2022 on this machine, where File Sync Agent was installed. The 2019 OSBuildInfo was still on 2019 on the Agent Registry Values, so the updater „StorageSyncAgent_WS2022 v16.msi“ needed to say „not correct OS“, even the real OS was right. So, I tried several (10?) methods: Update Installation (wrong version) Repair Installation (fatal error) Patch Installation via cab/msp (wrong version) What finally solved my can’t update issue (before doing the same, check the maybe…

Exceptions

Problem: Guest didn’t got network packets via Hyper-V Switch. Solution: Removed switch, added new switch with the same settings. Voila, works.

Problem: Windows 11 20Hx Solution: Download Insider ISO File and update with ISO to the new Windows 10 Version (22H2).

I had the issue, after backing up files from Android to Windows file shares with Cx Explorer, some files could not be renamed, deleted or moved via Windows Explorer, any UI tool and even PowerShell and cmd. This where the symptoms:   Solution: „Since short filenames are an optional feature of NTFS it’s possible that these files don’t have short names. In which case, you might be able to do it by using the extended length path form of the files‘ paths. You do this by prepending \\?\ to the full path of the file, enclosing it with quotes:“ C:\>ren „\\?\C:\Example\images\receipt. “ receipt.pdf   That finally solved my issue.   Thanks to…

Symptom: 0x800b0109 iis client certificate RetrieveTokenFromStsServerImpl failed with error 0x87d0027e [CCMHTTP] ERROR INFO: StatusCode=401 StatusText=PreAuth token validation failed Invoke-WebRequest : Server Error 403 – Forbidden: Access is denied. You do not have permission to view this directory or page using the credentials that you supplied. In Zeile:3 Zeichen:1 + Invoke-WebRequest -Uri „https://   Cause: This error happens in the end because of an non-root authority deployed/installed as into trusted root CA on the MP/SCCM Primary Server. Solution See 2nd Root Cause at first as your solution. It was mine. Otherwise 1st Root Cause could also help you out.     Details Troubleshooting-Steps:     Check SSL authentication with the machines…

Question #1 – Are the security baselines backward compatible? E.g. is the 20H2 Baseline also usable for 20H1 or 1903? Answer #1 – I did not found anything that documents this backward compatibility. In my point of view, mostly they are backward compatible and Microsoft adds mostly new settings of new major versions to the baselines. Consider, that in rare cases, also existing security settings could be changed. Conclusion: So if you plan to use the latest Baselines for all your Windows 10 / Windows Server versions, you can but You could get old settings changed resulting in productivity loss Divide your Windows Clients and Servers into multiple groups –…

Symptoms:   Fehler bei der Verarbeitung der Gruppenrichtlinie. Es konnte nicht bestimmt werden, ob sich Benutzer- und Computerkonto in der gleichen Gesamtstruktur befinden. Stellen Sie sicher, dass der Benutzerdomänenname mit dem Namen einer vertrauenswürdigen Domäne übereinstimmt, die sich in der gleichen Gesamtstruktur wie das Computerkonto befindet. Resolution: The netlogon service had manual as start type and was also not started. Once it was started, it was working again and added to GPO as automatic.  

Hier schreiben wir über Geschenke des Lebens, IT-Themen und Sonstiges.