The subject behavior occurs because administrator permissions is required to set up RDS.
To resolve this problem, an administrator must delete the private key that was created during the failed set up and then set up RDS.
1. Log on as a member of the local Administrators group.
2. Run the following DPKRDS.BAT file, which uses REG.EXE, installed from the Support Tools on the Windows 2000 CD_ROM:
@echo off setlocal set key=HKLM\SOFTWARE\Microsoft\SystemCertificates\_NMSTR\Certificates set OK=N for /f "Tokens=*" %%a in ('reg query %key%^|FIND /i "\Certificates\"') do ( set OK=Y ) if "%OK%" EQU "Y" endlocal&goto :EOF set file="%ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys\511a0f3f9e960fa97de3d0b74adfc574_*.*" call :quiet>nul 2>&1 endlocal goto :EOF :quiet set OK=N for /f "Tokens=*" %%a in ('dir /b /s /a %file%') do ( set OK=Y ) if "%OK%" EQU "Y" del /q /AS %file%3. Start NetMeeting.
4. Press Tools / Options / OK.
5. Set up RDS.
If you wish to grant Power Users the right to complete the RDS Wizard, even though they still won't be able to start RDS:
1. Open a CMD.EXE window.
2. Type the following cammand and press Enter:
subinacl /keyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates" /grant="Power Users"=F