Terminal Server idle timeout

-

we have windows server 2008 terminal server.    our sessions time out @ 10 minutes.   have changed idle timeout settings per instructions (domain group policy)  2 hours.  have tried computer settings , user settings.   has never changed timeout idle time - 10 minutes.   system has been rebooted without change 10 minutes.   new installation - 30 days.

hi,

by default users have screen saver timeout of 10 minutes logon prompt.  change can disable screen saver via group policy, extend timeout period via group policy, etc., or have each user change screen saver settings manually.

thanks.

-tp


Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Post a Comment

Popular posts from this blog

Motherboard replacement

-
running windows 10 technical preview, need replace motherboard can run the  sysprep  command restoring pc ? or there easier  or more preferred way ? thanks if replace motherboard within same family of chipsets (i.e. intel > intel or amd > amd), should okay restarting pc twice. carey frisch Windows 10 Insider Preview  >  Windows 10 Insider Preview General
Read more

Remote Desktop App - Error 0x207 or 0x607

-
hi all, i manage windows 2012 r2 network, including connection broker, session hosts , remote apps virtual servers.  i've used remote desktop app on own android phone, no issues @ - connects published gateway url , can login , access network. we looking move business onto nokia handsets ms operating system (currently on blackberry), not able connect via remote desktop app on nokia lumia handset. setup, per android config , brings remote apps , remote desktop screen, know can connect.  when select remote desktop, shows following process: initiating remote connection securing remote connection certificate can't verified - choose connect it digitally signed cert (digicert sha2), pc name different physical connection broker name (inherited domain name old gov project - can't publish publicly) initiating establishing securing connection error have been 0x207 getting 0x607 a bit baffled, work on android (and ipad @ home using app). assume ms use d...
Read more

AD Replication Failure Between Server 2008 R2 and Server 2003 - LDAP bind failed with error 8341

-
Image
hello, i adopted rather messy network previous engineer.  have 2008 r2 domain controller cannot replicate 2003 domain controller.  2003 pdce,  holding fsmo roles. both servers dns servers. as can see below, replication has not occurred in 3 months.  has become large issue workstations on network, exchange server. please note believe have done job of making sure there not duplicate dns entries either dc2003 or dc2008r2 on either server. thank can give. issues encountered while running commands from dc2008r2 : - when browse \\dc2003 dc2008r2 receive error: logon failure: account name incorrect. - when run dcdiag /test:dns i receive following initial error: performing initial setup:    trying find home server...    home server = dc2008r2    * identified ad forest.    [dc2003] ldap bind failed error 8341,    directory service error has occurred..    got error while checking...
Read more