Throw away your timestamp calculation snippets for testing script performance in favor of the native PowerShell cmdlet Measure-Command.
Learn how to discover all of a PowerShell object’s properties and see their values.
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.
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?