General

Use PowerShell to Set Up a Hyper-V Lab

Aaron Rothstein · October 11, 2016 · 2 Comments

A Hyper-V lab for your PowerShell sandbox

When learning and playing with new technology like PowerShell, a lab environment is extremely beneficial. Some of the benefits are:

A lab environment can be torn down and and rebuilt as needed.
Components can be added to or removed from a lab as needed.
Actions that are considered risky to perform in a production environment can be performed safely in a contained lab.

Windows 10 Pro, Enterprise, and Education (as well as Windows 8 Pro and Enterprise) come with the same Hyper-V technology that runs in the datacenter, just waiting to be enabled. Here is how to get it installed and configured using PowerShell.

Try PowerShell “-Verbose” to Troubleshoot Errors

Aaron Rothstein · October 5, 2016 · 2 Comments

A real-world example of where using PowerShell “-Verbose” parameter is more efficient than a Google search.

“Couldn’t connect to the source mailbox.”

Recently I needed to export an Exchange 2010 mailbox to a PST file. I opened my Exchange Management Shell and ran New-MailboxExportRequest, only to get the following error:

[PS] C:\Windows\system32>New-MailboxExportRequest -Mailbox jdoe -FilePath \\FileServer1\Exports\jdoe.pst
Couldn't connect to the source mailbox.
    + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
    + FullyQualifiedErrorId : C7D44FB7,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

Why couldn’t it connect to the source mailbox?

Get Process Name and Owner User Name

Aaron Rothstein · September 20, 2016 · 2 Comments

Two ways of returning the owner User Name of a running process using PowerShell.

PowerShell Script to Empty Recycle Bin at Logoff

Aaron Rothstein · July 6, 2016 · 3 Comments

Automate the emptying of the Windows Recycle Bin with this simple PowerShell script and Group Policy.

Redirected Folders = Recycle Bin Storage on File Server

In a lot of business environments, we redirect user folders like Documents, Desktops, Favorites, and more to a home directory on a network share, often mapped to its own drive letter. The folders are then synced to the user’s workstation to be available offline. This gives the user the ability to work on the files when disconnected, but still allows IT to have the files stored on the file servers and backed up.

PowerShell Replacement for ‘nslookup’

Aaron Rothstein · March 2, 2016 · 9 Comments

The fourth post in my PowerShell Beginner series, “Daily Tasks, The PowerShell Way“. Use PowerShell’s Resolve-DnsName cmdlet as a more powerful successor to ‘nslookup’.

What’s in a name?

Any seasoned IT Pro knows that the names we see for servers or in web URLs ultimately need to “resolve” or translate to a numerical IP address. Computers perform this resolution using a worldwide network of Domain Name System (DNS) servers. When your browser attempts to go to https://thinkpowershell.com, your computer will send a query to a DNS server with the hostname “thinkpowershell.com”, and the DNS server will return the IP address of the server hosting the website. Your DNS server will likely have to forward a query to other DNS servers to get the correct IP address.

nslookup (name server lookup) is a command line tool that has been around for years for performing this lookup activity on demand. You can specify the hostname or website domain name for which you want to “lookup” the IP address. Additionally, with the second positional parameter you can specify the IP address of a specific DNS server you want to query. It is a helpful tool, but it only returns CNAME , A, and AAAA record information, and not as a script-usable object.