Limit concurrent connections

[Guest]

Good day!

How can I restrict users in our Windows 2000 network to only one concurrent
connection regardless on which PC they are using within their OU? Is it to
implement on our Win2K server, without needing to configure individual
workstations? Is it possible through GPO?
Please provide me the best solution/steps or an article for this one.
This greatly appreciated.

Thanks,
Gomez

 

[Paul Bergson]

There is the option of using a special program unsupported by Microsoft, but
written by a partner program of theirs.

See:

http://www.microsoft.com/technet/technetmag/issues/2005/05/UtilitySpotlight/default.aspx

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Jorge_de_Almeida_Pinto]

Good day!

How can I restrict users in our Windows 2000 network to only
one concurrent
connection regardless on which PC they are using within their
OU? Is it to
implement on our Win2K server, without needing to configure
individual
workstations? Is it possible through GPO?
Please provide me the best solution/steps or an article for
this one.
This greatly appreciated.

Thanks,
Gomez

By default not possible...

However, Microsoft has a tool called LimitLogin that exactly does what
you need. It is free. It needs a schema update, it needs IIS and it
creates an APP partition in AD. To be able to create an APP partition
you at least need to have 1 w2k3 DC and for that you need to update
your AD schema.

See for updating the AD schema and introducing w2k3 DCs:
MS-KBQ325379_How to Upgrade Windows 2000 Domain Controllers to Windows
Server 2003

MS-KBQ555040_Common Mistakes When Upgrade Windows 2000 Domain To
Windows 2003

MS-KBQ314649_W2K3 ADPREP Command Causes Mangled Attributes in W2K
Forests That Contain E2K Servers

For limitlogin see:
http://bink.nu/files/limitlogonfaq.htm

 

[Guest]

Thanks Paul, Thanks Jorge...

Both of your advices really helps....