يا ليتني كوري شمالي

@ PanArab @lemmy.ml

Posts

174
Comments

1071
Joined

4 yr. ago

“If there were an Oscar for best theatrical performance by a country, Israel would win every year. It's a country based on theater. It's a lunatic state - completely insane”.
Norman Finkelstein

Moderating

Israeli Crimes lemmy.ml

3d ago

Hmmmmm. Libs: NoRtH KoReA BaDdD
Jump
يا ليتني كوري شمالي @lemmy.ml 3d ago
I wish I was North Korean

6d ago

How to get into linux and stay with linux?

I use FOSS even when I used to use Windows. So the programs I use and format I use were ready for me to switch. If for some reason you rely on a proprietary or Windows-only software you may have to make the effort to migrate, readjust and learn a new set of software to to do your work.

Many Windows administrative, automation, and remote management tasks require Command Prompt or PowerShell because they cannot be efficiently or practically executed via the GUI.

Tasks that involve repetitive or bulk operations often require CMD or PowerShell. For example: Renaming thousands of files simultaneously is impractical through File Explorer but can be done easily with Rename-Item in PowerShell
Batch file automation using .bat scripts allows automated workflows like clearing temporary files, launching multiple apps, backing up directories, and switching system settings like dark/light mode
Scheduled tasks and automatic scripts are better created with command-line scripts, providing repeatable precision versus manual GUI actions
Accessing and manipulating Windows services: Use Get-Service and Stop-Service in PowerShell to check or stop services on local or remote machines
Managing user accounts and permissions: Commands like net user or whoami /groups provide instant information on users or their groups, which may otherwise require multiple GUI interactions
Registry, Group Policy, and WMI tasks: Most registry edits, group policy refreshes (gpupdate /force), and WMI queries are accessible through PowerShell but lack straightforward GUI counterparts
System auditing and repair: Commands like sfc /scannow and DISM /RestoreHealth repair system files or images without needing GUI-based troubleshooting tools
Managing remote computers: Tools like shutdown /m computername or PowerShell cmdlets enable shutdowns, restarts, or status checks remotely where GUI Remote Desktop may be impractical or unavailable
Collecting diagnostics across multiple endpoints: CMD and PowerShell allow executing scripts across multiple machines unlike GUI tools, which must be operated individually
Searching, filtering, and processing files: Commands like Get-ChildItem, Where-Object, and Select-Object enable precise filtering, data extraction, and file management far beyond what the GUI allows
Clipboard automation: Using Get-Clipboard and Set-Clipboard for large or structured data transfer without manual selection
Reading log data: Extracting and analyzing system or application logs is faster via wevtutil than navigating Event Viewer
DNS, IP configuration, and connectivity tests: Commands like ipconfig /all, ping, tracert, Test-NetConnection, and netstat provide immediate network diagnostics that either lack GUI equivalents or are slower to perform