محدود کردن لاگان همزمان با یک یوزر در محیط دامین

[SIZE=3][FONT=Arial]سلام به اعضای انجمن[/FONT][/SIZE]
[SIZE=3][FONT=Arial]من از اعضای جدید انمن هستم یه سوال استادمون مطرح کرده که هر جا گشتم جوابش نبود.[/FONT][/SIZE]
[SIZE=3][FONT=Arial]سوال اینه که :[/FONT][/SIZE]
[SIZE=3][FONT=Arial]میخواهیم در محیط دامین یک یوزر نتونه به صورت همزمان لاگان کنه.[/FONT][/SIZE]
[SIZE=3][FONT=Arial]برای مثال در محیط دامین دو کامپیوتر به نام های PC1 و PC2 موجود هست علی با یوزر خودش روی PC1 لاگان کرده اگر خواست روی PC2 نیز لاگان کنه باید حتما یوزر خودش رو در PC1 لاگاف کنه که بتونه به کامپیوتر بعدی دسترسی داشته باشه..[/FONT][/SIZE]
[SIZE=3][FONT=Arial]لطفا در صورتی که جواب رو میدونید کمک کنید تا این سوال حل بشه :([/FONT][/SIZE]
[FONT=Arial][SIZE=3] [/SIZE][/FONT]
[SIZE=3][FONT=Arial]Mer 30[/FONT][/SIZE]

[LEFT][SIZE=3][B]Limiting a user's concurrent connections in Windows Server 2003, Windows 2000, and Windows NT 4.0

[/B][/SIZE][CODE]http://support.microsoft.com/kb/237282[/CODE][SIZE=3][/SIZE] This article describes how to limit concurrent connections for all users in a Microsoft Windows Server 2003, a Microsoft Windows 2000, or a Microsoft Windows NT 4.0 environment. [URL="http://support.microsoft.com/kb/237282#top"][IMG]http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gif[/IMG]Back to the top[/URL]

[B][URL="javascript:void(0);"]MORE INFORMATION[/URL]Install the Windows 2000 Resource Kit tool named CConnect.exe on each client co...
[/B]

Install the Windows 2000 Resource Kit tool named CConnect.exe on each client computer. This tool, together with an .adm file that is supplied by the tool, can perform the following functions:
[LIST][*]Limit concurrent connections for each user.[*]Log off remote computers when concurrent connections are reached.[*]List all computers that a user is logged on to.[*]List logon servers for each user.[*]Show how many users are logged on to a domain controller (DC).[*]Force a logoff when concurrent connections are reached.[*]Enable debugging of the CConnect tool.[*]Write events to the event log of a specified server about the status of the CConnect tool.[*]Save all lists to a file for further examination.[*] Track the last user of the computer and only limit that user from logging on to the computer if the computer was shut down incorrectly.[/LIST]
This tool is included with the Windows 2000 Resource Kit and works with both Windows NT 4.0 and Windows 2000. For Windows 2000, there are no system requirements. For Windows NT 4.0, the following requirements exist:
[LIST][*]Windows NT 4.0 Service Pack 3 or later must be installed.[*]Microsoft Data Access Components (MDAC) 2.0 must be installed.[*]Windows Scripting Host must be installed.[*]Web Based Enterprise Management (WBEM) must be installed.[/LIST]
[URL="http://support.microsoft.com/kb/237282#top"][IMG]http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gif[/IMG]Back to the top[/URL]
[B]Version 2.0[/B]

Version 2.0 supports Terminal Server restrictions. [B]Requirements[/B]

Windows NT 4.0 Terminal Server: Service Pack 4 or later
Windows 2000: No requirements
Version 2 will be available for public use on the next Windows 2000 Resource Kit. Version 1.3 is on the first Windows 2000 Resource Kit. [URL="http://support.microsoft.com/kb/237282#top"][IMG]http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gif[/IMG]Back to the top[/URL]

[B]LimitLogin utility[/B]

You can also use the LimitLogin utility to limit concurrent user logins in an Active Directory domain in a Windows Server 2003, a Windows 2000, or a Windows NT 4.0 environment. The LimitLogin utility keeps track of all logon information in Active Directory domains.

The LimitLogin utility has the following capabilities:
[LIST][*]It can limit the number of logins for each user from any computer in the domain. This includes terminal server sessions.[*]It can display the logon information about any user in the domain according to specific criteria. For example, you can use the LimitLogin utility to display all logon sessions to a specific client computer or to a specific domain controller. Additionally, you can use the utility to display all computers to which a certain user is currently logged on.[*]It is easy to manage and to configure because it can integrate into the Active Directory Microsoft Management Console (MMC) snap-ins.[*]It can remotely delete and log off user sessions from the Active Directory Users and Computers MMC snap-in.[*]It can generate logon information reports in either a comma-separated values (CSV) format or an XML format.[/LIST]
To download the LimitLogin utility, visit the following Microsoft Web site:[URL]http://download.microsoft.com/download/f/d/0/fd05def7-68a1-4f71-8546-25c359cc0842/limitlogin.exe[/URL] ([url]http://download.microsoft.com/download/f/d/0/fd05def7-68a1-4f71-8546-25c359cc0842/limitlogin.exe[/url])
To submit questions or to provide customer feedback about the LimitLogin utility, e-mail the following alias:llogin@microsoft.com
[URL="http://support.microsoft.com/kb/237282#top"][IMG]http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gif[/IMG]Back to the top[/URL]

[B]APPLIES TO[/B]


[LIST][*]Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)[*]Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)[*]Microsoft Windows Server 2003, Standard Edition (32-bit x86)[*]Microsoft Windows Server 2003, Web Edition[*]Microsoft Windows 2000 Server[*]Microsoft Windows 2000 Advanced Server[*]Microsoft Windows 2000 Professional Edition[*]Microsoft Windows 2000 Datacenter Server[*]Microsoft Windows NT Server 4.0 Enterprise Edition[*]Microsoft Windows NT Workstation 4.0 Developer Edition[*]Microsoft Windows NT Server 4.0 Standard Edition[/LIST]


[/LEFT]

از بابت کمکتون ممنون
اما من دنبال دستور کامندی این کار می گردم.این طور که خودم در موردش اطلاعات گرفتم این کار یک دستور هم داره و می شه این کار رو بدون استفاده از نرم افزار هم انجام داد.
اگر در موردش اطلاعات جدیدی بدست آوردید من رو هم بی اطلاع نزارید ممنونم
باز هم از کمکتون تا به همین جا هم ممنون

[LEFT][CODE]http://www.amset.info/windows/limit-logins.asp[/CODE]
[B][SIZE=5]Limit the Number of Network Logins a User Can Make[/SIZE][/B]
In many environments you may want to limit the number of times people can login to the network. This can be for many reasons such as ensuring people don't share login information and to ensure that their profile and files don't get our of sync.
You can use the login script along with an option in Windows to accomplish this task.
[B][SIZE=4]Setup Limited User Access Directory[/SIZE][/B]
To do this, your environment will need to be set up in the correct way. However you may find that you have already many of the components in place and just need to adjust the settings.

[LIST=1][*]On the file server, create a folder for each user that matches their username. For example, if their username is "[I]jsmith[/I]" then create a folder called "[I]jsmith[/I]".[*]Share this folder out, either as "[I]jsmith[/I]" If you would like to hide it from the browse list - which might be the case if there are lots of users on the machine as well as some generic shares, share it as "[I]jsmith$[/I]".[*]While you are sharing, adjust the "User Limit" from "Maximum Allowed" to the number that you desire. This would be "[I]1[/I]" if you want to limit the user to just one connection.[*]Press Apply/OK to close the dialogue.[/LIST]
[B][SIZE=4]Adjust the Login Script[/SIZE][/B]
Once you have restricted the user directory, you need to adjust your login script.
First map the drive to their user directory.
[I]net use U: \\fileserver\%username%$[/I]
Then you need to check if the mapping was successful. Add the following line immediately below the net use:
[I]iferrorlevel 1 goto logoff[/I]
Then add a section called logoff. In the example below a message is also sent to the user to tell them why they have been kicked out. Then follow a command to logoff the user:
[I]:logoff
net send localhost "You are logged in elsewhere. Please log off a the other terminal before trying again."
logoff[/I]
Finally if you are going to use the user directory as their home directory, then add the following commands immediately afterwards to set the environment variables correctly:
[I]setx homedrive "U:"
setx homepath "\"[/I]
[B]The complete sample ready for copying and pasting in to your own script can be found at the bottom of the page.[/B]
[B][SIZE=4]Uses for the User Directory[/SIZE][/B]
The most common use for the user directory is to redirect the "My Documents" folder. This would allow it to be backed up centrally.
You could also use it for the home to roaming profiles.
With the addition of a registry file applied by the login script, you could also redirect the user's "Favorites", allowing them access where ever they might be.
[B][SIZE=4]Questions[/SIZE][/B]
[B]Q: Logoff Doesn't Work
[/B]A: This seems to only work on servers. For workstations you need the "[I]logoff.exe[/I]" file from the [I]"NT4.0 Resource Kit"[/I] which you can download from here: [URL="http://www.microsoft.com/downloads/details.aspx?FamilyID=3E972E9A-E08A-49A2-9D3A-C0519479E85A&displaylang=en"]Download details: Windows NT 4.0 Resource Kit Support Tools[/URL]
[B]Q: I need other users to be able to see the contents of the home directories.
[/B]A: There may be instances where this is required. In that case, share the folder twice.
For example, share it once as "jsmith$" which is used in the login script as all the other shares are by this name and has the user connection limit applied. Then share it again as "jsmith" or even a different name such as "J Smith Documents" as this name isn't being used in a login script or has a user limit.
[B]Q: I am a network admin and need to see in to all the home directories but don't want to share each twice.
[/B]A: In many cases network admins will create the user directories in a main folder called "users". This master folder is shared out (usually hidden: "[I]users$[/I]") with restrictions on the share permissions (not the file permissions) to allow only admins access.
[B]Q: Where can I find more information about login scripts?[/B]
A: We have a dedicated web site for login scripts at [URL="http://loginscripts.info/"]Creating and Using Login Scripts | loginscripts.info from Sembee Ltd.[/URL]
[B][SIZE=4]Complete Sample - Ready to Copy and Paste. [/SIZE][/B]
Remember to turn off word wrap when working in notepad


[CODE]
net use U: \\fileserver\%username%$
if errorlevel 1 goto logoff
goto continue
:logoff
net send localhost "You are logged in elsewhere. Please log off a the other terminal before trying again."
logoff
:continue
setx homedrive "U:"
setx homepath "\"
(rest of the script)

[/CODE][/LEFT]

این هم جالب بود
ولی خوب map کردن یک درایو و ...

[SIZE=3][FONT=Times New Roman]من می خوام که این کار رو روی Virtual PC 2007 انجام بدم ولی دچار مشکل شدم.[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]من تو ویندوز SERVER یک فلدر رو به اسم یوزر ساختمو و اون رو share کردم و اون فایل رو توی کامپیوتر های دیگه که XP هستند MAP کردم ولی وقتی کامند رو توی SERVER اجرا می کنم اجرا نمیشه.[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]اسم کامپیوتر SERVER هست YAHOO[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]کامپیوتر های دیگه PC1 و PC2 هستن[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]و یوزر هم اسمش ALI هست.[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]حالا می خوام بدونم من چه طور و در کدوم محیط باید دستورات رو اجرا کنم تا جواب بگیرم من دستورات رو داخل محیط CMD اجرا میکنم.[/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman]و شکل درست نوشتن دستور به چه شکل هست من دستور رو به این شکل می نویسم و پیغام خطا میگیرم[/FONT][/SIZE]
[FONT=Times New Roman][SIZE=3]net use U: \\fileserver\%username%$[/SIZE][/FONT]
[FONT=Times New Roman][SIZE=3] [/SIZE][/FONT]
[FONT=Times New Roman][SIZE=3]net use U: \\yahoo\%ali%$[/SIZE][/FONT]