When Thunderbird starts it ignores already existing registry entries. That means, if you have had deleted an extension via UI and you did not change the registry entry (deleting or modifying) afterwards TB will not install this extension again. In other words: If you have once installed an extension via registry and you delete it […]
Debug it using the Developers error console. Try using ASCII (PEM) instead of Binary (DER) certs.
Basics: https://bytesandbones.wordpress.com/2019/09/30/thunderbird-gpo-admx Via Registry: HKCU\Software\Policies\Mozilla\Thunderbird\Certificates\Install\1 = “mycert.der” or Software\Policies\Mozilla\Thunderbird\Certificates\Install\2 = “\\MYHOST\Users\username\mycert.pem” or Software\Policies\Mozilla\Thunderbird\Certificates\Install\3 = “C:\CERTS\mycert.pem” as REG_EXPAND_SZ. If you define only a file name without a path Thunderbird searches %USERPROFILE%\AppData\Local\Thunderbird\Certificates%USERPROFILE%\AppData\Roaming\Thunderbird\Certificates for your files. Via GPO: Use the user branch. Define full path file location or file names only. If you specify only a file […]
Get-NetAdapter -Physical | where InterfaceDescription -eq “Intel(R) Ethernet Connection (7) I219-V” | Set-NetAdapterAdvancedProperty -NoRestart -DisplayName “Energieeffizientes Ethernet” -DisplayValue “Aus” Get-NetAdapter -Physical | where InterfaceDescription -eq “Realtek*” | Set-NetAdapterAdvancedProperty -NoRestart -RegistryKeyword “EEE” -RegistryType “REG_SZ” -RegistryValue “0” Get-NetAdapter -Physical | where DriverProvider -eq “Intel” | where DriverVersion -like “12.18.8.*” | Set-NetAdapterAdvancedProperty -NoRestart -DisplayName “Energieeffizientes Ethernet” -DisplayValue “Ein” […]
You have a problem with running WOL properly on Windows 10 in a corporate environment? Distribute a powershell (argghhh) script like this via GPO. All 192.168 NICs are renamed into a standard OFFICEN (OFFICE1..999). $adapter = gwmi win32_networkadapterconfiguration | ? { $_.IPaddress -like “*192.168*”} $i = 1 foreach($element in $adapter){ $adapterindex = $element.index $newname = […]
Your machines can’t connect to your WSUS? Maybe you upgraded your Windows version (ie 1909 > 2004) and your old GPOs don’t fit the new version. Solution: remove your old Update GPOs, add the new admx files from an freshly upgraded windows machine to your DCs PoliciyDefinitions and reconstruct your GPOs.
bytes and bones 