I passed the test. First I went to my system: marked as the tomato garden.
As we all know, XP by default does not support simultaneous login by multiple users. That is to say, when we remotely Access XP, a local user is kicked out and can only be used by one user. Find the perfect solution on the east side of the network:
1. Create a new user (identity administrator) and set the password.
2. Replace the following files with the same name in safe mode (Please back up the files ):
C: \ windows \ system32 \ termsrv. dll, c: \ windows \ system32 \ dllcache \ termsrv. dll.
As attachments cannot be uploaded, you can search for this file online. There are many!
2. log on to Windows XP normally. If the file protection function of the system prompts that the termsrv. dll file has been modified, ask whether to restore the file and select No.
3. Run enableconcurrentsessions. bat,
Create a TXT file with the following content:
@ Echo off
Setlocal
Set regkey = "HKLM \ System \ CurrentControlSet \ Control \ Terminal Server \ licensing core"
Reg add % regkey %/V enableconcurrentsessions/T REG_DWORD/D 1/F
Endlocal
Modify the file nameEnableconcurrentsessions. Bat. Double-click it.
Or modify the key values of the registry:
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ licensing core, create a DWORD Value named "enableconcurrentsessions" under this key, and set the data of this value to 1.
4. In Windows x Settings> Control Panel> user account management, find the newly created user and enable the "Welcome screen" and "quick User Switch" functions.
5. Restart the instance and open the task manager to check if it is a dual-user? Can be connected, consistent with remote operations