{"id":4714,"date":"2012-11-07T00:01:00","date_gmt":"2012-11-07T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2012\/11\/07\/post-windows-server-2012-migration-powershell-cleanup-work\/"},"modified":"2012-11-07T00:01:00","modified_gmt":"2012-11-07T00:01:00","slug":"post-windows-server-2012-migration-powershell-cleanup-work","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/post-windows-server-2012-migration-powershell-cleanup-work\/","title":{"rendered":"Post Windows Server 2012 Migration PowerShell Cleanup Work"},"content":{"rendered":"

Summary:<\/strong> Microsoft Scripting Guy, Ed Wilson, talks about Windows PowerShell cleanup work to do following a migration to Windows Server 2012.<\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. Well, following any migration, there is always a bit of cleanup work. Luckily, Windows Server 2012 enables Windows PowerShell remoting by default. This means that the cleanup is not too bad.<\/p>\n

Note<\/strong>   Read about my experience upgrading my group of servers to Windows Server 2012 in yesterday’s Hey, Scripting Guy! blog post: The 32-hour Upgrade to Windows Server 2012<\/a>.<\/em><\/p>\n

First Windows PowerShell task—ensure you update Help<\/h2>\n

One of the cool new features of Windows PowerShell 3.0 is the updatable Help. The great thing about this is that it makes it easy to always have the latest Help files. Once I complete my upgrade to Windows Server 2012 (or, for that matter, to Windows 8, or any computer to Windows PowerShell 3.0) I need to run the Update-Help<\/strong> cmdlet.<\/p>\n

I could simply run Update-Help<\/strong> on each computer, and then tell it to go off to the Internet and grab the latest Help files. But that is inefficient, and Windows PowerShell 3.0 has provisions for offline updates.<\/p>\n

So, from my laptop computer (which, incidentally, has the Windows 8 RSAT tools and, therefore, all the modules installed on it), I run the Save-Help<\/strong> cmdlet. I point it to a shared folder on my network. The following image shows the command and the associated output.<\/p>\n

 \"\"<\/a><\/p>\n

OK, so that was less than impressive. The reason? Well, the destination folder must exist. I was hoping that it would be smart enough to create my poshhelp directory. Oh, well. No problem. I revise the command as appears here.<\/p>\n

PS C:\\> New-Item -ItemType directory -Path \\\\dc1\\share\\poshhelp<\/p>\n

    Directory: \\\\dc1\\share<\/p>\n

Mode                LastWriteTime     Length Name<\/p>\n

—-                ————-     —— —-<\/p>\n

d—-         11\/5\/2012   2:12 PM            poshhelp<\/p>\n

PS C:\\> Save-Help -Module * -DestinationPath \\\\dc1\\share\\poshHelp<\/p>\n

A couple of errors still appear, but that is due to the fact that Help is trying to update Help for some modules that do not have updated Help. Cool. Now, I need to update the Help by using the share for all my new Windows Server 2012 servers. This is easier than it appears. Remember, I have the RSAT tools on my laptop, therefore, I have access to the Get-ADComputer<\/strong> cmdlet. I use the following command to obtain all of the servers that run Windows Server 2012 on my network.<\/p>\n

PS C:\\> Get-ADComputer -Filter * -properties operatingsystem | where operatingsystem<\/p>\n

-match 2012 | select name<\/p>\n

name<\/p>\n

—-<\/p>\n

DC3<\/p>\n

DC4<\/p>\n

W8SERVER8<\/p>\n

W8S504<\/p>\n

HYPERV3<\/p>\n

SQL1<\/p>\n

WDS1<\/p>\n

HYPERV2<\/p>\n

DC2<\/p>\n

WEB1<\/p>\n

 I store the results of the command (not by using Select-Object<\/strong>) into a variable I call cn<\/strong>. <\/em>This is shown here.<\/p>\n

 $cn = Get-ADComputer -Filter * -properties operatingsystem | where operatingsystem -match 2012<\/p>\n

 By using an automatic expansion (a cool Windows PowerShell 3.0 feature), it is easy to get the computer names. I just pick out the property. I will include it in my command to create the Windows PowerShell session. I know some of these computers are offline, and so I expect some errors. Here is the command I use to create the sessions.<\/p>\n

$session = New-PSSession -cn $cn.name -Credential iammred\\administrator<\/p>\n

I query the $session variable to see that at least some computers worked. This appears here.<\/p>\n

PS C:\\> $session<\/p>\n

 Id Name            ComputerName    State         ConfigurationName     Availability<\/p>\n

 — —-            ————    —–         —————–     ————<\/p>\n

  4 Session4        DC3             Opened        Microsoft.PowerShell     Available<\/p>\n

  5 Session5        DC4             Opened        Microsoft.PowerShell     Available<\/p>\n

  8 Session8        HYPERV3         Opened        Microsoft.PowerShell     Available<\/p>\n

 11 Session11       HYPERV2         Opened        Microsoft.PowerShell     Available<\/p>\n

  9 Session9        SQL1            Opened        Microsoft.PowerShell     Available<\/p>\n

 10 Session10       WDS1            Opened        Microsoft.PowerShell     Available<\/p>\n

 13 Session13       WEB1            Opened        Microsoft.PowerShell     Available<\/p>\n

 12 Session12       DC2             Opened        Microsoft.PowerShell     Available<\/p>\n

The commands and associated output appear here.<\/p>\n

 \"\"<\/a> <\/p>\n

I now use Invoke-Command<\/strong> to update Help on all of my servers. This appears here.<\/p>\n

Invoke-Command -Session $session -ScriptBlock {Update-Help -PSPath \\\\dc1\\Share\\poshhelp -Force}<\/p>\n

If I do not want to fool with downloading Help, I can use the following command to update Help on all of my servers.<\/p>\n

Invoke-Command -Session $session -ScriptBlock {Update-Help -force}<\/p>\n

Of course, a few more errors about missing modules and stuff appear, but, in the end, I have updated all the Help on my servers.<\/p>\n

Enable script support<\/h2>\n

Now, I want to enable scripting on the servers. This is also a single cmdlet—Set-ExecutionPolicy<\/strong>. Here is the command I use:<\/p>\n

Invoke-Command -Session $session -ScriptBlock {Set-ExecutionPolicy remotesigned -force}<\/p>\n

I can easily check the results by using Get-ExecutionPolicy<\/strong>. This is shown here.<\/p>\n

PS C:\\> Invoke-Command -Session $session -ScriptBlock {Get-ExecutionPolicy}<\/p>\n

PSComputerName               RunspaceId                  Value<\/p>\n

————–               ———-                  —–<\/p>\n

DC4                          571a049f-c671-46e7-b72a-… RemoteSigned<\/p>\n

DC3                          8cc8e20d-2426-44fd-9ae5-… RemoteSigned<\/p>\n

HYPERV3                      b3f5afae-1f1b-43ca-918f-… RemoteSigned<\/p>\n

SQL1                         9609e293-26ff-4866-9734-… RemoteSigned<\/p>\n

WEB1                         d5dfcde8-2de1-4b8f-9a21-… RemoteSigned<\/p>\n

WDS1                         75124ffd-5f4b-4e27-91f4-… RemoteSigned<\/p>\n

DC2                          ea287978-f21f-4f27-85e1-… RemoteSigned<\/p>\n

HYPERV2                      a4e5f5ab-add7-4fe3-a7a7-… RemoteSigned<\/p>\n

That is all there is to updating Help and configuring script support on my remote servers running Windows Server 2012. Join me tomorrow, when I will do remote updates.  <\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about Windows PowerShell cleanup work to do following a migration to Windows Server 2012. Microsoft Scripting Guy, Ed Wilson, is here. Well, following any migration, there is always a bit of cleanup work. Luckily, Windows Server 2012 enables Windows PowerShell remoting by default. This means that the cleanup is not […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[31,362,3,4,45],"class_list":["post-4714","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-operating-system","tag-powershell-3","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about Windows PowerShell cleanup work to do following a migration to Windows Server 2012. Microsoft Scripting Guy, Ed Wilson, is here. Well, following any migration, there is always a bit of cleanup work. Luckily, Windows Server 2012 enables Windows PowerShell remoting by default. This means that the cleanup is not […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4714","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=4714"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4714\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=4714"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=4714"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=4714"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}