Nel terminal server 2003 mi bastava mappare la lettera di unità e il percorso di rete nella terminal service home folder del terminal service profile ed il gioco era fatto. Purtroppo su XP non è possibile gestire dallo snap in di gestione utenti locali, eventuali settaggi relativi alle sessioni remote…

Mi spiego meglio; ho xp patchato ma non riesco a far si che l’applicazione remota (sul file/application server, vero) vada in esecuzione poichè non some come far si che la sessione terminal su XP possa creare l’unità di rete mappata G: dalla quale mandare in esecuzione l’applicazione.

Qualcuno sa dove posso recuperarla?

Grazie e ciao

Diego

Response:
The beta 2055 release of XP PRO SP2 let you run two sessions (one local console and one remote desktop) concurrently. This functionality was removed in the Final release. You can obtain copies of the termsrv.dll from version 2055 that lets you renable concurrent sessions. You must use a different user for each session. To enable concurrent sessions, perform the following steps:
1. Start a registry editor (e.g., regedit.exe).
2. Navigate to the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Licensing Core registry subkey.
3. From the Edit menu, select New, DWORD Value.
4. Enter the name “EnableConcurrentSessions,” then press Enter.
5. Double-click the new value, then set it to 1.
Here are some more detailed instructions and a link to get the termsrv.dll file from 2055.
Install the recovery console onto the hard drive (to use in the process, plus its good to have anyway in case of emergency http://support.microsoft.com/default.aspx?scid=kb;EN-US;307654
Copy this DLL file
http://members.lycos.nl/nessyh/files/term/termsrv.dll
into your system32 directory as TERMSRV.2055 make the appropriate registry changes listed above
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Licensing Core\
DWORD: EnableConcurrentSessions=1
Make the policy changes:
Local Computer Policy – Computer Configuration – Administrative Templates – Windows Components – Terminal Services | Allow users to connect remotely using Terminal Services=enabled
Local Computer Policy – Computer Configuration – Administrative Templates – Windows Components – Terminal Services | Sets rules for remote control of Terminal Services user sessions=enabled+Full Control without user`s permission
Computer config./admin. templates/windows components/terminal services and enabling the setting:
Limit number of connections, then entering values in there.
Make sure you have multiple accounts with a PASSWORD (that are in the remote users group or are administrators), you have FAST USER SWITCHING enabled, and are NOT in a domain.
Reboot, and enter the recovery console
cd /d c:\windows\system32
ren termsrv.dll termsrv.sp2
ren termsrv.2055 termsrv.dll
cd /d c:\windows\system32\dllcache
ren termsrv.dll termsrv.sp2
Reboot into windows- you should be able now to terminal in from another computer
AND use the console, as long as you do it from DIFFERENT accounts.