For managing migrations on Hyper-V OS you need to do it remotely…

“To manage the tasks with remote management tools, configure constrained delegation and select Kerberos as the authentication protocol.”

https://technet.microsoft.com/en-GB/library/jj134199.aspx#BKMK_Prereqs

$SourceGroup = "Terminal Service Users"
$TargetGroup = "RDG Users"

$Sgroupmem = Get-ADGroupmember -Identity $SourceGroup
Add-ADGroupmember -Identity $TargetGroup -Member $Sgroupmem

Script to produce a nice HTML report of the Hyper-V resources…

.\Get-HyperVReport.ps1 -VMHost Host1,Host2,Host3

https://gallery.technet.microsoft.com/scriptcenter/Hyper-V-Reporting-Script-4adaf5d0

This assumes that you are removing the LAST Exchange 2010 Server in a domain after moving to Office 365…

DISABLE the Mailboxes, be careful the other option bins the AD user object as well!!

Delete all User Public folders:
$ExchangeServer = "ServerName"
Get-PublicFolder -Server $ExchangeServer "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server $ExchangeServer -Recurse -ErrorAction:SilentlyContinue

Delete all System Public folders:
Get-PublicFolder -Server $ExchangeServer "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server $ExchangeServer -Recurse -ErrorAction:SilentlyContinue

Delete the Default Offline Address Book.

Delete the Mailbox Databases

Check if a specific mailbox database that you cannot remove through EMC contains a mailbox and what type they are:
get-mailbox -database "Mailbox Database"
get-mailbox -database "Mailbox Database" -archive
get-mailbox -database "Mailbox Database" -arbitration

Assuming that there are arbitration mailboxes, this is how you remove them:
get-mailbox -database "Mailbox Database" -arbitration | disable-mailbox -arbitration -disablelastarbitrationmailboxallowed

Remove any Send Connectors (Organisation Configuration > Hub Transport > Send Connectors)

Uninstall Exchange from Programs and Features.

Posting this as I always bloody forget it!

import-module ActiveDirectory
Get-ADUser -SearchBase 'ou=users,dc=company,dc=local' -Filter * | Foreach-Object{
$firstname = $_.givenname
$lastname = $_.surname
$domain = "@company.co.uk"
$emailaddress = $firstname + "." + $lastname + $domain
Set-ADUser -Identity $_ -Email $emailaddress
}

A good article on NSLookUp…

http://www.rackspace.com/knowledge_center/article/nslookup-checking-dns-records-on-windows

https://technet.microsoft.com/en-us/library/hh848454.aspx

Example to convert from a dynamic to a fixed VHDx file:

Convert-VHD -path "C:\Hyper-V\server-1.VHD" -destinationpath "C:\Hyper-V\server-2.VHD" -vhdtype fixed

Once the VHDx has been altered the new file will not contain the correct permissions. If you rename the new VHDx to the same as the old file (after renaming the old one) then the Virtual Machine will not boot. If you examin the permissions of the two files you will see the differences. The simplest way to correct the permissions is to add the new VHDx through Hyper-V manager (or if you have renamed the VHDxs simply remove and re-add the Hard Drive in Hyper-V manager).

http://blogs.technet.com/b/messaging_with_communications/archive/2011/04/22/how-to-manage-exchange-2010-message-queues.aspx

Queues
Get-Queue
Resume-Queue
Retry-Queue
Suspend-Queue

Messages
Get-Message
Remove-Message
Resume-Message
Suspend-Message
Export-Messages

Ohhhhh lots of lovely scripts….
http://blogs.technet.com/b/dblanch/archive/2013/12/03/managing-exchange-public-folder-permissions.aspx