Posts on Robert Rumpf /posts/ Recent content in Posts on Robert Rumpf Hugo -- gohugo.io en-us Wed, 23 Jun 2021 21:21:00 +0200 escalate UAC in Powershell with sudo /posts/2021/06/escalate-uac-in-powershell-with-sudo/ Wed, 23 Jun 2021 21:21:00 +0200 /posts/2021/06/escalate-uac-in-powershell-with-sudo/ For a while now, I have been working professionally with Intune software deployment. I often have to test various scripts for customers. These often require admin rights. Since I’m tired of starting the Powershell as admin every time, I started looking for a way around the problem. I found something on Github. https://github.com/gerardog/gsudo (G)sudo …is probably known from the Linux universe and that’s exactly how it works. Just type sudo or gsudo in front of the command that needs extended privileges and an admin prompt appears without having to open a new shell. For a while now, I have been working professionally with Intune software deployment. I often have to test various scripts for customers. These often require admin rights. Since I’m tired of starting the Powershell as admin every time, I started looking for a way around the problem. I found something on Github.

https://github.com/gerardog/gsudo

(G)sudo

…is probably known from the Linux universe and that’s exactly how it works. Just type sudo or gsudo in front of the command that needs extended privileges and an admin prompt appears without having to open a new shell.

The whole thing can be installed with Powershell (as admin ;-))

PowerShell -Command "Set-ExecutionPolicy RemoteSigned -scope Process; iwr -useb https://raw.githubusercontent.com/gerardog/gsudo/master/installgsudo.ps1 | iex"
]]> Improve WSL2 ressource management for windows /posts/2021/06/improve-wsl2-ressource-management-for-windows/ Wed, 23 Jun 2021 19:22:47 +0200 /posts/2021/06/improve-wsl2-ressource-management-for-windows/ Shutdown your running wsl. wsl --shutdown Going to c:\users*your your profile name* and creating a .wslconfig file or do it via powershell ;-) notepad "$env:USERPROFILE/.wslconfig" [wsl2] memory=4GB # Limits VM memory in WSL 2 to 4 GB processors=5 # Makes the WSL 2 VM use two virtual processors swap=0 localhostForwarding=true After that start Powershell with admin permissions, restart WSL2 by typing: Restart-Service LxssManager Drop Cache variable for WSL create this alias at the end of your ~/. Shutdown your running wsl.

wsl --shutdown

Going to c:\users*your your profile name* and creating a .wslconfig file or do it via powershell ;-)

notepad "$env:USERPROFILE/.wslconfig"

[wsl2]
memory=4GB # Limits VM memory in WSL 2 to 4 GB
processors=5 # Makes the WSL 2 VM use two virtual processors
swap=0
localhostForwarding=true

After that start Powershell with admin permissions, restart WSL2 by typing:

Restart-Service LxssManager

Drop Cache variable for WSL

create this alias at the end of your ~/.bashrc file

alias drop_cache="sudo sh -c \"echo 3 >'/proc/sys/vm/drop_caches' && swapoff -a && swapon -a && printf '\n%s\n' 'Ram-cache and Swap Cleared'\""

and run the following in your shell to setup the alias

source ~/.bashrc

then you can run the drop_cache command when you need it.

You can run it manually when you notice high memory usage or you can try to create a crontab job.

]]>