<div>
Aside from the loopback policies you need to configure The Terminal Server Configuration Connections as this overrides ALL settings, including GPOs.<br />
<br />
-open your run command line<br />
-type in tscc.msc and press enter<br />
-Go to the Sessions tab and you can override the settings here if they are enabled.
</div>


Aside from the loopback policies you need to configure The Terminal Server Configuration Connections as this overrides ALL settings, including GPOs.

-open your run command line
-type in tscc.msc and press enter
-Go to the Sessions tab and you can override the settings here if they are enabled.

<div>
<div class="content wysiwyg-content">
I have 2 screensaver policies applied to 2 different User Groups. &nbsp;The first policy is a 15min/No lock and second is 5min/Lock. &nbsp;The problem is that I have users from each group logging into a Win2003 Terminal Server and users that should not have the lock are having the lock applied. &nbsp;Example - Time Clock terminal session via Remote Desktop should have 15min/No Lock, but the session is locking after 5 minutes. &nbsp;Is there a way to put in an exception for our Terminal Server to ignore the Screensaver policies using the GPMC? &nbsp;I was also curious if Terminal Server screensaver policies are not session specific but truly computer based so only 1 screensaver policy will affect all users with active sessions?
</div>
</div>


I have 2 screensaver policies applied to 2 different User Groups.  The first policy is a 15min/No lock and second is 5min/Lock.  The problem is that I have users from each group logging into a Win2003 Terminal Server and users that should not have the lock are having the lock applied.  Example - Time Clock terminal session via Remote Desktop should have 15min/No Lock, but the session is locking after 5 minutes.  Is there a way to put in an exception for our Terminal Server to ignore the Screensaver policies using the GPMC?  I was also curious if Terminal Server screensaver policies are not session specific but truly computer based so only 1 screensaver policy will affect all users with active sessions?

Terminal Server Screensaver Group Policy Exception

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

IT Administration is the processes and best practices for programming and development, and incorporates methodologies for managing activities and projects. Common methodologies include waterfall, prototyping, iterative and incremental development, spiral development, rapid application development, extreme programming and various types of agile methodology. The life-cycle "model" is a more general term for a category of methodologies, and a software development "process" a more specific term to refer to a specific process chosen by a specific organization.