Windows and PowerShell have built-in security features and default configurations intended to prevent end-users from accidentally launching scripts in the course of their daily activities. However, if your daily activities routinely involve writing and running your own PowerShell scripts, this can be more of a nuisance than a benefit. Here, we’ll show you how to work around these features without completely compromising on security.
For several reasons, mostly security-related, PowerShell scripts aren’t as easily portable and usable as batch scripts can be. However, we can bundle a batch script with our PowerShell scripts to work around these issues. Here, we’ll show you a few of those problem areas, and how to build a batch script to get around them.
In batch scripts, changes to environment variables have a global impact to the current session by default. For PowerShell, the exact opposite is true because scopes are used to isolate a script’s modifications. Here, we’ll explore how scopes affect PowerShell scripts and how to work in and around them.
When you need a data set for testing or demonstration, and that set needs to represent Personally Identifiable Information (PII), you generally don’t want to use real data that represents actual people. Here, we’ll walk you through how you can use PowerShell to generate a list of random names and phone numbers for just such an occasion.
There are plenty of third-party programs and other widgets that may help you keep information close at hand. Here’s a neat trick to keep short notes or other small pieces of information accessible from the taskbar without any extra software.
With news of the NSA, GCHQ, big corporations, and anyone else with an Internet connection snooping through your online data these days, you can’t be too careful when it comes to protecting the stuff you put in the cloud. This guide will tell you what you need to do so that TrueCrypt can keep your synced files guarded from prying eyes.