user sessions remain in disconnect state forever...

[Guest Brad Pears]

We are using a windows 2003 (sp1) terminal server. Our domain controller is

a Windows 2000 small bus server.

 

I have configured user session time limits etc... using the "sessions" tab

in each users AD user profile to "end a disconnected session" after 1 hour.

I have not configured anything on the actual terminal server using the

"Terminal Server Configuration" app because I wanted to do it user

specifically.

 

For some reason when a users session becomes disconnected, it never gets

logged off when the 1 hour expiration limit I set is reached. This has not

been a big problem in the past (I used to log them off manually) but just

recently we have had a few issues and I would like to ensure that I get this

problem resolved.

 

Does anyone have any ideas why this may be happening? It appears the "idle

session limit" I set of 30 minutes is working because after 30 min, they are

being disconnected properly...

 

Strange...

 

Any ideas would be most helpful!

 

Thanks, Brad

[Guest Vera Noest [MVP]]

Re: user sessions remain in disconnect state forever...

 

Do the sessions actually get the status "Disconnected", in Terminal

Services Manager?

If not, check this:

 

216783 - You cannot completely disconnect a Terminal Server

connection

http://support.microsoft.com/?kbid=216783

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Brad Pears" <bradp@truenorthloghomes.com> wrote on 13 aug 2007 in

microsoft.public.windows.terminal_services:

> We are using a windows 2003 (sp1) terminal server. Our domain

> controller is a Windows 2000 small bus server.

>

> I have configured user session time limits etc... using the

> "sessions" tab in each users AD user profile to "end a

> disconnected session" after 1 hour. I have not configured

> anything on the actual terminal server using the "Terminal

> Server Configuration" app because I wanted to do it user

> specifically.

>

> For some reason when a users session becomes disconnected, it

> never gets logged off when the 1 hour expiration limit I set is

> reached. This has not been a big problem in the past (I used to

> log them off manually) but just recently we have had a few

> issues and I would like to ensure that I get this problem

> resolved.

>

> Does anyone have any ideas why this may be happening? It appears

> the "idle session limit" I set of 30 minutes is working because

> after 30 min, they are being disconnected properly...

>

> Strange...

>

> Any ideas would be most helpful!

>

> Thanks, Brad

[Guest Brad Pears]

Re: user sessions remain in disconnect state forever...

 

Yes, they show as disconnected... I think I may have been able to get

around this by using a "computer" Administrative->Terminal Server group

policy on our backup win2K3 domain controller. I noticed that on win2K3

there are User and Computer Terminal Server policy settings available for

use - which are not present on our Windows 2000 Small Bus server. I set them

on the backup Win2K3 server for logging off disconnected sessions after 1

hour and it appears to work. Hopefully making settings changes on the Win2K3

backup DC that are not present on our Win2K SBS will not cause problems.

Ultimately I would like to have those Terminal Server policy settings on the

Win2K server as well. Any chance you might know how to do that??

 

Thanks, Brad

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns998BEA9B4678Bveranoesthemutforsse@207.46.248.16...

> Do the sessions actually get the status "Disconnected", in Terminal

> Services Manager?

> If not, check this:

>

> 216783 - You cannot completely disconnect a Terminal Server

> connection

> http://support.microsoft.com/?kbid=216783

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "Brad Pears" <bradp@truenorthloghomes.com> wrote on 13 aug 2007 in

> microsoft.public.windows.terminal_services:

>

>> We are using a windows 2003 (sp1) terminal server. Our domain

>> controller is a Windows 2000 small bus server.

>>

>> I have configured user session time limits etc... using the

>> "sessions" tab in each users AD user profile to "end a

>> disconnected session" after 1 hour. I have not configured

>> anything on the actual terminal server using the "Terminal

>> Server Configuration" app because I wanted to do it user

>> specifically.

>>

>> For some reason when a users session becomes disconnected, it

>> never gets logged off when the 1 hour expiration limit I set is

>> reached. This has not been a big problem in the past (I used to

>> log them off manually) but just recently we have had a few

>> issues and I would like to ensure that I get this problem

>> resolved.

>>

>> Does anyone have any ideas why this may be happening? It appears

>> the "idle session limit" I set of 30 minutes is working because

>> after 30 min, they are being disconnected properly...

>>

>> Strange...

>>

>> Any ideas would be most helpful!

>>

>> Thanks, Brad

[Guest Vera Noest [MVP]]

Re: user sessions remain in disconnect state forever...

 

I'm not an expert on SBS, you might want to check in the SBS

newsgroup as well, but here's how you do it on a plain W2K server:

 

307900 - Upgrading Windows 2000 Group Policy for Windows XP

(applies to 2003 as well)

http://support.microsoft.com/?kbid=307900

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Brad Pears" <bradp@truenorthloghomes.com> wrote on 14 aug 2007 in

microsoft.public.windows.terminal_services:

> Yes, they show as disconnected... I think I may have been able

> to get around this by using a "computer"

> Administrative->Terminal Server group policy on our backup

> win2K3 domain controller. I noticed that on win2K3 there are

> User and Computer Terminal Server policy settings available for

> use - which are not present on our Windows 2000 Small Bus

> server. I set them on the backup Win2K3 server for logging off

> disconnected sessions after 1 hour and it appears to work.

> Hopefully making settings changes on the Win2K3 backup DC that

> are not present on our Win2K SBS will not cause problems.

> Ultimately I would like to have those Terminal Server policy

> settings on the Win2K server as well. Any chance you might know

> how to do that??

>

> Thanks, Brad

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns998BEA9B4678Bveranoesthemutforsse@207.46.248.16...

>> Do the sessions actually get the status "Disconnected", in

>> Terminal Services Manager?

>> If not, check this:

>>

>> 216783 - You cannot completely disconnect a Terminal Server

>> connection

>> http://support.microsoft.com/?kbid=216783

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Brad Pears" <bradp@truenorthloghomes.com> wrote on 13 aug 2007

>> in microsoft.public.windows.terminal_services:

>>

>>> We are using a windows 2003 (sp1) terminal server. Our domain

>>> controller is a Windows 2000 small bus server.

>>>

>>> I have configured user session time limits etc... using the

>>> "sessions" tab in each users AD user profile to "end a

>>> disconnected session" after 1 hour. I have not configured

>>> anything on the actual terminal server using the "Terminal

>>> Server Configuration" app because I wanted to do it user

>>> specifically.

>>>

>>> For some reason when a users session becomes disconnected, it

>>> never gets logged off when the 1 hour expiration limit I set

>>> is reached. This has not been a big problem in the past (I

>>> used to log them off manually) but just recently we have had a

>>> few issues and I would like to ensure that I get this problem

>>> resolved.

>>>

>>> Does anyone have any ideas why this may be happening? It

>>> appears the "idle session limit" I set of 30 minutes is

>>> working because after 30 min, they are being disconnected

>>> properly...

>>>

>>> Strange...

>>>

>>> Any ideas would be most helpful!

>>>

>>> Thanks, Brad

[Guest Brad Pears]

Re: user sessions remain in disconnect state forever...

 

Thanks Vera.

That worked.

 

Brad

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns998CDBFB05251veranoesthemutforsse@207.46.248.16...

> I'm not an expert on SBS, you might want to check in the SBS

> newsgroup as well, but here's how you do it on a plain W2K server:

>

> 307900 - Upgrading Windows 2000 Group Policy for Windows XP

> (applies to 2003 as well)

> http://support.microsoft.com/?kbid=307900

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "Brad Pears" <bradp@truenorthloghomes.com> wrote on 14 aug 2007 in

> microsoft.public.windows.terminal_services:

>

>> Yes, they show as disconnected... I think I may have been able

>> to get around this by using a "computer"

>> Administrative->Terminal Server group policy on our backup

>> win2K3 domain controller. I noticed that on win2K3 there are

>> User and Computer Terminal Server policy settings available for

>> use - which are not present on our Windows 2000 Small Bus

>> server. I set them on the backup Win2K3 server for logging off

>> disconnected sessions after 1 hour and it appears to work.

>> Hopefully making settings changes on the Win2K3 backup DC that

>> are not present on our Win2K SBS will not cause problems.

>> Ultimately I would like to have those Terminal Server policy

>> settings on the Win2K server as well. Any chance you might know

>> how to do that??

>>

>> Thanks, Brad

>>

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns998BEA9B4678Bveranoesthemutforsse@207.46.248.16...

>>> Do the sessions actually get the status "Disconnected", in

>>> Terminal Services Manager?

>>> If not, check this:

>>>

>>> 216783 - You cannot completely disconnect a Terminal Server

>>> connection

>>> http://support.microsoft.com/?kbid=216783

>>>

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>> TS troubleshooting: http://ts.veranoest.net

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "Brad Pears" <bradp@truenorthloghomes.com> wrote on 13 aug 2007

>>> in microsoft.public.windows.terminal_services:

>>>

>>>> We are using a windows 2003 (sp1) terminal server. Our domain

>>>> controller is a Windows 2000 small bus server.

>>>>

>>>> I have configured user session time limits etc... using the

>>>> "sessions" tab in each users AD user profile to "end a

>>>> disconnected session" after 1 hour. I have not configured

>>>> anything on the actual terminal server using the "Terminal

>>>> Server Configuration" app because I wanted to do it user

>>>> specifically.

>>>>

>>>> For some reason when a users session becomes disconnected, it

>>>> never gets logged off when the 1 hour expiration limit I set

>>>> is reached. This has not been a big problem in the past (I

>>>> used to log them off manually) but just recently we have had a

>>>> few issues and I would like to ensure that I get this problem

>>>> resolved.

>>>>

>>>> Does anyone have any ideas why this may be happening? It

>>>> appears the "idle session limit" I set of 30 minutes is

>>>> working because after 30 min, they are being disconnected

>>>> properly...

>>>>

>>>> Strange...

>>>>

>>>> Any ideas would be most helpful!

>>>>

>>>> Thanks, Brad

[Guest Vera Noest [MVP]]

Re: user sessions remain in disconnect state forever...

 

Great! I'm glad that it worked, and thanks for your feedback, Brad.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Brad Pears" <bradp@truenorthloghomes.com> wrote on 24 aug 2007 in

microsoft.public.windows.terminal_services:

> Thanks Vera.

> That worked.

>

> Brad

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns998CDBFB05251veranoesthemutforsse@207.46.248.16...

>> I'm not an expert on SBS, you might want to check in the SBS

>> newsgroup as well, but here's how you do it on a plain W2K

>> server:

>>

>> 307900 - Upgrading Windows 2000 Group Policy for Windows XP

>> (applies to 2003 as well)

>> http://support.microsoft.com/?kbid=307900

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Brad Pears" <bradp@truenorthloghomes.com> wrote on 14 aug 2007

>> in microsoft.public.windows.terminal_services:

>>

>>> Yes, they show as disconnected... I think I may have been

>>> able to get around this by using a "computer"

>>> Administrative->Terminal Server group policy on our backup

>>> win2K3 domain controller. I noticed that on win2K3 there are

>>> User and Computer Terminal Server policy settings available

>>> for use - which are not present on our Windows 2000 Small Bus

>>> server. I set them on the backup Win2K3 server for logging off

>>> disconnected sessions after 1 hour and it appears to work.

>>> Hopefully making settings changes on the Win2K3 backup DC that

>>> are not present on our Win2K SBS will not cause problems.

>>> Ultimately I would like to have those Terminal Server policy

>>> settings on the Win2K server as well. Any chance you might

>>> know how to do that??

>>>

>>> Thanks, Brad

>>>

>>>

>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>> wrote in message

>>> news:Xns998BEA9B4678Bveranoesthemutforsse@207.46.248.16...

>>>> Do the sessions actually get the status "Disconnected", in

>>>> Terminal Services Manager?

>>>> If not, check this:

>>>>

>>>> 216783 - You cannot completely disconnect a Terminal Server

>>>> connection

>>>> http://support.microsoft.com/?kbid=216783

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>> TS troubleshooting: http://ts.veranoest.net

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> "Brad Pears" <bradp@truenorthloghomes.com> wrote on 13 aug

>>>> 2007 in microsoft.public.windows.terminal_services:

>>>>

>>>>> We are using a windows 2003 (sp1) terminal server. Our

>>>>> domain controller is a Windows 2000 small bus server.

>>>>>

>>>>> I have configured user session time limits etc... using the

>>>>> "sessions" tab in each users AD user profile to "end a

>>>>> disconnected session" after 1 hour. I have not configured

>>>>> anything on the actual terminal server using the "Terminal

>>>>> Server Configuration" app because I wanted to do it user

>>>>> specifically.

>>>>>

>>>>> For some reason when a users session becomes disconnected,

>>>>> it never gets logged off when the 1 hour expiration limit I

>>>>> set is reached. This has not been a big problem in the past

>>>>> (I used to log them off manually) but just recently we have

>>>>> had a few issues and I would like to ensure that I get this

>>>>> problem resolved.

>>>>>

>>>>> Does anyone have any ideas why this may be happening? It

>>>>> appears the "idle session limit" I set of 30 minutes is

>>>>> working because after 30 min, they are being disconnected

>>>>> properly...

>>>>>

>>>>> Strange...

>>>>>

>>>>> Any ideas would be most helpful!

>>>>>

>>>>> Thanks, Brad