Deploying windows printserver printers to windows machines | installing drivers via powershell

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 […]

Windows | strange DNS resolve problem

Situation: Your machine lives in a corporate environment and uses your corporates own DNS resolver who’s located in your own LAN/IPsubnet. You didn’t define a default gateway in your IPv4 settings for security reasons. Resolving names via nslookup works fine, but windows himself (i.e ping) and third party software (like datev) run into resolve problems […]

poor quality after jitsi update

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 […]

nginx | redirect https://domain to different https://domain without browser cert errors

Standard nginx redirect: server { listen 80; listen 443 ssl; server_name up-eleven.de http://www.domain-a.tld; return 301 https://www.domain-b.tld; } Produces browser ssl errors (wrong cert) cs before executing the redirecting order the https connection is established between your browser and the orig domain. Solution: Run certbot on the orig domain you redirect from: The bot inserts this […]