Network Audit and Documentation, CENTREL Solutions Blog

I've recently bought a pair of Sony WH-1000XM4 headphones at £350 which includes noise cancelling and are excellent for working in café and other busy environments. During Coronavirus lockdown it made sense to use these headphones for exercise whilst trapped in the house. Within 6 months the headphones weren't charging properly and a few weeks later completely failed. I raised a warranty call with Sony and was pretty annoyed such a high value pair of headphones had failed so soon, but since they were only 8 months old and under warranty at least I'd get them repaired. Wrong. Having sent them back to the Sony repair centre SONYUKTEC in Pencoed, Wales I waited a while and was finally told that the unit had failed because of water damage. I was quite surprised as they'd never been outside the house except for a flight and then they were in the case the whole time outdoors. I told them I'd only used them indoors for work and exercise during lockdown. They pointed out th

Microsoft have now released Windows Server 2022, and it looks like they've fixed the weird bug in Windows Server 2019 when you couldn't access the form and the error "Windows cannot access the specified device, path, or file." was displayed. https://david-homer.blogspot.com/2019/06/windows-server-2019-desktop-icons-such.html In Windows Server 2022 you can  Go to Start > Settings (cog) Search for Desktop Icons which will display Themes and related settings . Click  Themes and related settings Scroll down and click  Desktop icon settings This will display the familiar Desktop Icon Settings dialog. Alternatively it's still possible to run the command directly as was required in Windows Server 2019 desk.cpl ,5 - While you're here - Why not check out our Windows Server Documentation and Audit Tool?

When running a command using PowerShell remoting from C# we were receiving the following errors. Processing data for a remote command failed with the following error message: <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="3762504530" Machine=" servername "><f:Message><f:ProviderFault provider="microsoft.powershell" path="C:\Windows\system32\pwrshplugin.dll"></f:ProviderFault></f:Message></f:WSManFault> For more information, see the about_Remote_Troubleshooting Help topic. ...And... Processing data from remote server servername  failed with the following error message: The WSMan provider host process did not return a proper response. It turned out that the first command being run was executing unmanaged C# code through the PowerShell remoting connection. There was an issue with this code (a missing ref statement) which caused the code to crash.  Subsequently this cau