{"id":2740,"date":"2013-10-12T00:01:00","date_gmt":"2013-10-12T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2013\/10\/12\/disconnected-sessions-phenotype-and-genotype-part-2\/"},"modified":"2013-10-12T00:01:00","modified_gmt":"2013-10-12T00:01:00","slug":"disconnected-sessions-phenotype-and-genotype-part-2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/disconnected-sessions-phenotype-and-genotype-part-2\/","title":{"rendered":"Disconnected Sessions: Phenotype and Genotype (Part 2)"},"content":{"rendered":"

Summary<\/strong>: Learn about a revolutionary feature in Windows PowerShell 3.0 that lets you disconnect from and reconnect to PSSessions.\nToday we continue our exciting guest blog series that is written by Paul Higinbotham, a software design engineer for Windows PowerShell and June Blender, a senior programming writer for Windows Azure Active Directory. Here’s June…\nI hope that everyone got a chance to try the scenario that I discussed in Disconnected Sessions: Phenotype and Genotype (Part 1)<\/a>. In this post, I’ll show you how to use the InDisconnectedSessions<\/strong> parameter of Invoke-Command<\/strong> and share a few “gotchas” to keep you out of trouble.<\/span><\/p>\n

Disconnect Immediately<\/h2>\n

Our savvy IT pro is ready to head to a long meeting. So, she starts a command in a disconnected session. The really efficient command that follows creates the remote session, disconnects from the session, and then runs the command in the disconnected session, thereby keeping all of the command results in the disconnected session:<\/p>\n

 PS C:> Invoke-Command -ComputerName Server02 {<commands>} -InDisconnectedSession -SessionName TestWeekly<\/p>\n

 <\/p>\n

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

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

  5 TestWeekly      Server02        Disconnected  Microsoft.PowerShell          None\nWhen she returns from her meeting, the commands are still running. (Must have been a short meeting…)<\/p>\n

PS C:> $s = Get-PSSession -ComputerName Server02 -Name TestWeekly | Connect-PSSession<\/p>\n

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

 <\/p>\n

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

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

  5 TestWeekly      Server02        Opened        Microsoft.PowerShell          Busy<\/p>\n

Gotchas: IdleTimeout<\/h2>\n

I know you’ll want to try this right now. Who wouldn’t? But before you run off, I want to give you some hints to avoid problems.\nThe value of the IdleTimeout<\/strong> property of the PSSession determines how long the PSSession is maintained while it’s idle (including the heartbeat). When the timeout expires, Windows PowerShell removes the PSSession. This is especially important for disconnected PSSessions that might be left idle for long periods by design.<\/p>\n

PS C:> (Get-PSSession -ComputerName Server01 -Name Diag).IdleTimeout<\/p>\n

7200000\nThe default value of the IdleTimeout<\/strong> property of a PSSession is determined by the value of the IdleTimeoutMs<\/strong> property of the session configuration that is used to create the session.\nIn this scenario, the IT pro did not specify a session configuration (New-PSSession -ConfigurationName <name>), so the PSSession used the default session configuration, Microsoft.PowerShell, where the value of the IdleTimeoutMs<\/strong> property is 7200000 milliseconds, or two hours.<\/p>\n

PS C:> (Get-PSSessionConfiguration Microsoft.PowerShell).IdleTimeoutMs<\/p>\n

7200000\nThere are several ways to extend the idle timeout of a PSSession:<\/p>\n