Standard stuff: On Server install your printer and printer driver. Then run printmanagament.msc and do Deploy with Group Policy. Have an eye on the drivers section. Know the exact name of your driver, thats important for deploying drivers to local machines. Your brandnew Group Policy should consist of (i) computer >> policies >> windows settings […]
check places.sqlite, maybe it’s corrupt
check the js console in chromes developer tools for something like this: BridgeChannel.js:88 WebSocket connection to ‘wss://jitsi.yourmachine.com/colibri-ws/default-id/6e93e6f16131917e//a6a42650?pwd=6iiknuitk9epkkh65n8q2ak1m3’ failed It seems your update process switches you poorly (incompletely) from multiplexing to bridge websockets. Check this: https://jitsi.github.io/handbook/docs/devops-guide/faq Additional hints: In /etc/turnserver.conf you can remove listening-port= Check the external-ip btw. In /etc/prosody/conf.avail/jitsi.yourmachine.com.cfg.lua you can remove the stun and […]
The -k switch won’t work. Intsatll the nmap package and use ncat instead.
Select the Application Pool Name and then click ‘Advanced Settings’.Do some changes: Private Memory Limit (KB): 1843200 to 4194304 Queue Length: 1000 to 25000 Limit Interval (minutes): 5 to 15 ‘Service Unavailable’ Response: HttpLevel to TcpLevel Then stop the IIS (IIS-Manager or ‘net stop w3srv’), edit the web.config ( C:\Program Files\Update Services\WebServices\ClientWebService\web.config ) for WSUS:Replace […]
Open the management console, Filter for ‘Approved’, Status: ‘All’. Then add the column ‘File Status’. Maybe disapprove the baddies.
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 