<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx</link><description>Hello everyone, We are pleased to announce that the Beta release of Windows server 2008 R2 supports managing Remote Desktop services using PowerShell. You can now configure and manage all RDS role services and components using PowerShell. For example,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9302863</link><pubDate>Sat, 10 Jan 2009 01:47:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9302863</guid><dc:creator>Rod Trent at myITforum.com</dc:creator><description>&lt;p&gt;Managing Remote Desktop services (aka Terminal services) using Windows PowerShell Feed: Windows PowerShell&lt;/p&gt;
</description></item><item><title>re: Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9303245</link><pubDate>Sat, 10 Jan 2009 05:19:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9303245</guid><dc:creator>Jason Stangroome</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I've been trying to find a way to query a list of servers for their current Terminal Services sessions and then force a logoff for any sessions that have been inactive for a threshold time.&lt;/p&gt;
&lt;p&gt;Is this a supported scenario with PowerShell?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Jason&lt;/p&gt;</description></item><item><title>re: Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9303980</link><pubDate>Sat, 10 Jan 2009 15:18:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9303980</guid><dc:creator>Rajesh B R</dc:creator><description>&lt;p&gt;Hi Jason,&lt;/p&gt;
&lt;p&gt;The session time limits for connection RDP-Tcp can be found at path : 'RDS:\RDSConfiguration\Connections\RDP-Tcp\SessionTimeLimitSettings'&lt;/p&gt;
&lt;p&gt;Change directory to above location.&lt;/p&gt;
&lt;p&gt;Say you have to set the IdleSessionLimit of 1 hour (3600000 millisecs).&lt;/p&gt;
&lt;p&gt;The following snippet should do it for you :&lt;/p&gt;
&lt;p&gt;# if 'TimeLimitPolicy' is 0(Server Override), Just set the IdleSessionLimit&lt;/p&gt;
&lt;p&gt;Set-Item IdleSessionLimit 3600000&lt;/p&gt;
&lt;p&gt;# if 'TimeLimitPolicy' is 1(User setting), Set policy to Server override and provide timelimit values&lt;/p&gt;
&lt;p&gt;Set-Item TimeLimitPolicy 0 -IdleSessionLimit 3600000 -ActiveSessionLimit 0 -DisconnectedSessionLimit 0&lt;/p&gt;
&lt;p&gt;For more information on these items check their description.&lt;/p&gt;
&lt;p&gt;Example: Get-Item TimeLimitPolicy | Format-List&lt;/p&gt;</description></item><item><title>re: Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9307016</link><pubDate>Mon, 12 Jan 2009 09:08:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9307016</guid><dc:creator>Rajesh B R</dc:creator><description>&lt;p&gt;@ Jason:&lt;/p&gt;
&lt;p&gt;If the threshold idle time is fixed, above snippet would do. Otherwise we donot currently support the following:&lt;/p&gt;
&lt;p&gt; &amp;nbsp;1. Listing the current TS sessions&lt;/p&gt;
&lt;p&gt; &amp;nbsp;2. Log-off sessions on need basis or with variable threshold idle time&lt;/p&gt;</description></item><item><title>re: Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9307632</link><pubDate>Mon, 12 Jan 2009 14:37:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9307632</guid><dc:creator>Rajesh B R</dc:creator><description>&lt;p&gt;Terminal services tools can be used with PowerShell to accomplish the above mentioned tasks.&lt;/p&gt;
&lt;p&gt;For more details on these tools visit : &lt;a rel="nofollow" target="_new" href="http://technet.microsoft.com/en-us/library/cc776289.aspx"&gt;http://technet.microsoft.com/en-us/library/cc776289.aspx&lt;/a&gt;&lt;/p&gt;</description></item><item><title>PowerShell Provider for Remote Desktop Services (Terminal Services)</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9342245</link><pubDate>Tue, 20 Jan 2009 07:00:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9342245</guid><dc:creator>Ying Li(MVP) at myITforum.com</dc:creator><description>&lt;p&gt;In case you haven&amp;amp;#39;t noticed, Microsoft renamed Terminal Services as Remote Desktop Services from&lt;/p&gt;
</description></item><item><title>re: Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9392175</link><pubDate>Tue, 03 Feb 2009 03:47:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9392175</guid><dc:creator>Harrison</dc:creator><description>&lt;p&gt;On Windows Server 2008 R2, if I just install the Remote Desktop Virtualization role, I don't get the &amp;quot;Remote Desktop Services PowerShell&amp;quot;. Is it by design?&lt;/p&gt;</description></item><item><title>re: Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9902027</link><pubDate>Thu, 01 Oct 2009 23:32:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9902027</guid><dc:creator>Michal Talaga</dc:creator><description>&lt;p&gt;Same problem here, No powershell where it should be thought I see the provider is installed when i run powershell modules from start menu-&amp;gt;somewhere&lt;/p&gt;</description></item><item><title>re: Managing Remote Desktop services (aka Terminal services) using Windows PowerShell</title><link>http://blogs.msdn.com/powershell/archive/2009/01/09/managing-remote-desktop-services-aka-terminal-services-using-windows-powershell.aspx#9902029</link><pubDate>Thu, 01 Oct 2009 23:37:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9902029</guid><dc:creator>Michal Talaga</dc:creator><description>&lt;p&gt;OK figured out i can just launch the powershell as mentioned before and do cd RDS:&lt;/p&gt;</description></item></channel></rss>