I had the opportunity to attend the Madison Fishing Expo a few weekends ago. It was a great way to stay excited for the upcoming fishing year during these cold winter months. I didn’t get any new information, but I did let my son pick out a few cheap lures to add to his tackle box.
The warm weather has completely melted the ice off our area lakes (nice and early!), but we, along with almost the entire rest of the country, got a round of winter weather this week, so we’re back to almost a foot of snow on the ground. It’ll be at least a few more weeks before I launch the boat for the first time this year.
The company I work for has been in the process of strengthening its security posture for the last few years. Recently, they took the step of creating separate administrator accounts to use when we are doing things that require administrative permissions. Up until now, I only had one account – an administrator-level account. I expected at least a few things to break once they turned off my higher privileges, and those expectations were met. The thing I’m going to touch on today is Powershell privileges.
I use a Powershell script that is run daily to collect various health statistics regarding my SQL databases and servers. This script is run from Windows Task Scheduler, and is run from my laptop using my Windows AD account user. Once that user lost its admin privileges, a few of the collection methods failed. In order to get them to work, I needed to plug in my admin account for that specific method. I found a neat way to do that using Powershell’s Credential object.
First, I stored the account password in a text file. The password is encrypted and placed as a file on the disk by using the following Powershell command:
Opening the new file contains the following:
So you can see that the password is definitely encrypted.
Now I can reference that file whenever I need to enter credentials.
#Create a credential for connecting to the server $user = "Domain\adminuser" $pw = cat "C:\Temp\Password.txt" | convertto-securestring $cred = new-object -typename System.Management.Automation.PSCredential -argumentlist $user, $pw #Access the Disk Info using my new credntial $disks = Get-WmiObject -ComputerName $instance -Class Win32_LogicalDisk -Filter "DriveType = 3" -Credential $cred;
Using this method you can pass credentials to your Powershell script without having to store them in plain text on your computer. The only downside in my case is I will have to update my encrypted password file whenever my admin account has a password change.