Visual Studio Analyzer ships with security open. You can increase the security settings to reflect your site's needs. To increase the security settings, you need to complete the following steps:
These steps are described in the following procedures.
Note: You need to configure security on a per-machine basis for any machine on which you are running the Visual Studio Analyzer server or client.
The procedures for restricting access all use DCOMCNFG, a configuration utility intended for configuring DCOM-specific settings in the registry. DCOMCNFG is shipped with the Windows 95 DCOM Refresh but is not added to the Start menu or to any groups. You must start DCOMCNFG using the Run command on the Start menu.
For more information on using DCOMCNFG to configure access and launch permissions, search for "DCOMCNFG" in MSDN Library Visual Studio 6.0.
To restrict access to the Visual Studio Analyzer server to specific users
The Access Permissions dialog box appears. This dialog box lists the known users who currently have (or are denied) access to the machine. Click Add to add users to the list; click Remove to remove users.
The Add Access Permissions dialog box appears.
To restrict access to the Visual Studio Analyzer client
You need to perform this procedure on any machine where you are running the Visual Studio Analyzer client. This procedure ensures that the machine will connect to legitimate Visual Studio Analyzer servers only.
To edit the registry to enable security checking on the Visual Studio Analyzer server
To edit the registry to enable security checking on the Visual Studio Analyzer client
If you want to connect to a remote Microsoft® Windows® 95 machine running Visual Studio Analyzer, you must run DCOMCNFG on the remote machine to change your DCOM settings to allow remote connections. Before you can run DCOMCNFG on any machine, you must set the machine's access control to user level (DCOMCNFG requires user-level access control in order to run). You should need to run DCOMCNFG one time only to change these settings.
Important Changing access control to user level on a Windows 95 machine can have far-reaching consequences. For example, it will reset all of your current share permissions and you will need to restore those permissions manually. However, you cannot run Visual Studio Analyzer on a remote Windows 95 machine without changing access control to user level. Make sure you check with your system administrator before you change access control.
To set access control to user level
To allow remote connections
To allow access to your Windows 95 machine, you must also run the Visual Studio Analyzer Server each time you want to allow remote connections. See Starting the Visual Studio Analyzer Server on Windows 95 for steps on how to start the Visual Studio Analyzer Server.
Visual Studio Analyzer ships with security open. In this way, you can adjust the security settings to reflect your site's needs.
On Windows 95, you might find a situation where no components that generate Visual Studio Analyzer events are listed for the machine to which you are connected, even though those components exist and are registered. To work around this problem, you need to install the Remote Registry Service on that machine. To use the Remote Registry Service, you must be using user-level security and you must have the Remote Administration option enabled.
To enable the Remote Administration option
Note If you are using user-level security, you do not receive a password dialog box. Instead, add users to the list by clicking Add.
To install the Remote Registry Service