![[PowerShell] Reclaim Windows 10](http://35.204.150.161/content/images/wordpress/2016/07/reclaimWindows10_ps1.png)
I came across a nice script called “Reclaim Windows 10” by Ali Robertson. It turns off a bunch of unnecessary Windows 10 telemetery, removes bloatware, and privacy invasions. Review and tweak before running. Scripts for reversing are included and commented. The script below is from GitHub, it’s forked from http://pastebin.com/gQxCUkLP. ########## # Tweaked Win10 Initial Setup Script # Primary Author: Disassembler <[email protected]> # Original Version: 1.4, 2016-01-16 # Tweaked based on personal preferences for @alirobe 2016-03-23 - v1.4.1 # NOTE: MAKE SURE YOU READ THIS SCRIPT CAREFULLY BEFORE RUNNING IT + ADJUST COMMENTING…
All posts in Powershell
wrote a script for a customers network administrator to enable and disable access to removable storage. In the example below I used the registry keys for the Removable Disks: Deny write access and Removable Disks: Deny read access Group Policy Objects. It is easier to fix this with Group Policy if the computers are domain joined, you can set the policy in Computer Configuration > Administrative Templates > System > Removable Storage Access. Note: The script below is only tested on Windows 10, version 1511. Use it as reference for your own environment. <# .SYNOPSIS Enable or Disable access to…
I was looking for a PowerShell replacement of the script provided in MS KB “How to open the firewall port for SQL Server on Windows Server 2008” which uses the netsh command to open the Windows firewall ports for SQL Server. Because in future versions of Windows, Microsoft might remove the Netsh functionality for Windows Firewall with Advanced Security. Microsoft also recommends that you transition to Windows PowerShell if you currently use netsh to configure and manage Windows Firewall with Advanced Security. And I found the answer it on the TechNet Forums. For reference I have posted the…
In most cases, you won’t need to specify a static internal IP address (DIP) for your virtual machine. VMs in a virtual network will automatically receive an internal IP address from a range that you specify. But in certain cases, specifying a static IP address for a particular VM makes sense. For example, if your VM is going to run DNS or will be a domain controller. Or, if you have a VM that you plan to stop/deprovision at some point, but want retain the DIP for the VM when you provision it again. A static DIP stays…