The PowerShell execution policy is a good feature from a security perspective, but in most cases it is just plain annoying, especially when running scripts from Group Policy, Task Scheduler, or some other sort of remote mechanism. This article shows you how to bypass the PowerShell execution policy on a machine so that you can run your script on a system irrespective of what execution policy is set.
If you have Windows Firewall enabled then chances are that eventually you are going to find that it will be blocking one or more ports required by your applications. Checking Windows Firewall for blocked ports will help you troubleshoot your issues.
To check if Windows Firewall is blocking a port(s) that your machine is trying to communicate, follow the steps below…
So Windows 10 is a pretty awesome operating system and generally (so far at least) well received by the majority of users. There is one thing that might not be so awesome… by default Windows 10 is stealing your internet bandwidth.
Why? Because Windows Update are now peer-to-peer shared. In other words, the updates you download are automatically “seeded” so that others can download them directly from you, instead of the Microsoft web servers. It works in the same as torrents do; you download and at the same time seed the file for others to download.
You maybe thinking, who cares? But the problem is that it is using your internet bandwidth without you knowing, and therefore slowing your internet speeds. Also, if your uploads are counted towards your download limit (like in Australia) then they are eating away at your download limit as well!!
So how do you stop Windows 10 from stealing your internet? Easy… follow the steps in the article below.
Have your tried to ping your computer or server and it fails even though you know that it is online and connected to the network? One of the reasons why this fails could be because ping is disabled in the Windows Firewall. This article discusses how to resolve this and allow ping through the Windows Firewall.
Here is a quick fix to a problem that I had the other day, which I thought my be useful to a few people.
You logging into the vSphere 5.1 Web Client with the local vSphere Single Sign-On (SSO) user of admin@System-Domain and it fails with the error message of
associated users password is expired.
Below is the solution to this error message…
About a year ago I had a requirement to securely store a few passwords that would then be used to run a PowerShell script. At the time, I thought it would be a good idea to create another one of my PowerShell Function Libraries, such as my PowerShell Logging Function Library.
This article documents my solution and the end product: PowerShell Encryption Function Library….