Error message when you try to connect to a Windows XP SP2-based computer by using the Remote.exe tool together with the /SMS:NoSQL switch: ''Security rights to run Remote Tools on this client have been denied" (922357)

WORKAROUND

To work around this issue, use one of the following methods.

Method 1

If you know the site code name or the database server name, use the Remote.exe command without the /SMS:NoSQL switch. You will be prompted to manually enter the site code or the database server name.

Method 2

If you must use the /SMS:NoSQL switch, create an authenticated session to the client computer before you run the Remote.exe tool.

To create an authenticated session, type net use \\client computer name\IPC$ at a command prompt, and then press ENTER. This command generates a connection to the client computer by using the logged-on user's credentials.

Note You can use another set of credentials in this command. The Remote.exe tool will use the authenticated session to connect to the named pipe. You can also map a drive to a network share before you start the Remote.exe tool. Or, you can locate a shared resource on the client computer before you run the Remote.exe tool. These approaches generate the same outcome as when you connect to the IPC$ share on the SMS Advanced Client.

Method 3

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Enable named pipes that connect to the Server service by using null nessions. To do this, use one of the following methods.

Method A: Modify the registry on the client computer

1. On the client computer, start Registry Editor.
2. Locate and then click the following registry subkey:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver

3. Click parameters, and then double-click NullSessionPipes.
4. In the Edit Multi-String dialog box, add the SrvSvc entry by typing SrvSvc on a new line.
5. Click OK, and then exit Registry Editor.

Method B: Modify the local security policy

1. On the client computer, click Start, click Run, type secpol.msc, and then click OK.
2. In the Local Security Settings window, expand Local Policies, and then click Security Options.
3. In the results pane, double-click Network Access: Shares that can be accessed anonymously.
4. In the Local Policies Settings dialog box, add the SrvSvc entry to the list by typing SrvSvc on a new line.
5. Click OK, and then close the Local Security Settings window.
6. Click Start, click Run, type gpupdate.exe, and then click OK.
   
   Note When you remove the SrvSvc entry from the policy, you do not remove the registry entry if it has been added.

Notes

• Method 3 does not work if the RestrictAnonymous registry entry is enabled on the client computer or if the RestrictAnonymous policy has been implemented.
• You do not have to restart the client computer to apply these changes. These changes will be applied as long as the registry change or the local security policy is applied.