As a systems guy, I don't like users leaving behind idle connections because
they disconnected instead of logging off. Only creates administrative
overhead.

Is there any way I can scan the servers on our network noting who is logged
in, perhaps with some criteria like "has been idle more than 2 days". Then
we could email those users, or notify someone in IT, etc.

Thanks.

If your talking about idle Remote Desktop sessions there are group policies
that you can configure to logoff idle sessions. Read the whole thread...

http://tinyurl.com/9toc3

Beyond that I suggest you post to one of the server news groups for help
with Windows 2003/2000 Server issues like this...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

"BrianD" <BrianD@discussions.microsoft.com> wrote in message
news:3FB0ADF4-398D-4F5F-A005-9AD16C21C5FA@microsoft.com...
> As a systems guy, I don't like users leaving behind idle connections
> because
> they disconnected instead of logging off. Only creates administrative
> overhead.
>
> Is there any way I can scan the servers on our network noting who is
> logged
> in, perhaps with some criteria like "has been idle more than 2 days".
> Then
> we could email those users, or notify someone in IT, etc.
>
> Thanks.

> As a systems guy, I don't like users leaving behind idle connections
because
> they disconnected instead of logging off. Only creates administrative
> overhead.
>
> Is there any way I can scan the servers on our network noting who is
logged
> in, perhaps with some criteria like "has been idle more than 2 days".
Then
> we could email those users, or notify someone in IT, etc.

NET SESSION

Yes I'm referring to Remote Desktop sessions, this is the Remote Desktop
newsgroup. :-)

I will check that thread... thanks.

"Sooner Al [MVP]" wrote:

> If your talking about idle Remote Desktop sessions there are group policies
> that you can configure to logoff idle sessions. Read the whole thread...
>
> http://tinyurl.com/9toc3
>
> Beyond that I suggest you post to one of the server news groups for help
> with Windows 2003/2000 Server issues like this...
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual
> benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
> "BrianD" <BrianD@discussions.microsoft.com> wrote in message
> news:3FB0ADF4-398D-4F5F-A005-9AD16C21C5FA@microsoft.com...
> > As a systems guy, I don't like users leaving behind idle connections
> > because
> > they disconnected instead of logging off. Only creates administrative
> > overhead.
> >
> > Is there any way I can scan the servers on our network noting who is
> > logged
> > in, perhaps with some criteria like "has been idle more than 2 days".
> > Then
> > we could email those users, or notify someone in IT, etc.
> >
> > Thanks.
>
>
>