Remote Registry Editing in Windows 95

Windows 95 introduced centralized desktop management to enterprise networks, allowing administrators to modify client configurations without visiting individual physical workstations. To enable remote registry editing, Windows 95 required the installation of an optional network service found on the operating system's installation media, the configuration of user-level access control via a domain controller, and the use of the standard Registry Editor tool connecting over remote procedure calls.

The Microsoft Remote Registry Service

Remote registry capability was not enabled by default in Windows 95. Instead, Microsoft provided the Remote Registry service (regserv.exe) as an administrative utility located on the Windows 95 installation CD in the \ADMIN\NETTOOLS\REMOTREG directory.

To enable the functionality on a target computer, administrators had to add the service manually or deploy it via automated network installation scripts (such as batch setups via MSBATCH.INF):

  1. Open the Control Panel and launch Network.
  2. Click Add, select Service, and click Add.
  3. Choose Have Disk and point to the \ADMIN\NETTOOLS\REMOTREG path on the installation media.
  4. Select Microsoft Remote Registry and click OK.

Security Prerequisites: User-Level Access Control

The Remote Registry service could not operate on Windows 95's default "Share-level access control." It strictly required "User-level access control."

Because Windows 95 lacked a local security authority capable of managing individual user accounts, user-level security required authentication pass-through to a centralized authentication server—either a Windows NT Server domain or a Novell NetWare server.

Once user-level access control was configured in the Network Control Panel, only accounts with administrative rights within the authenticating domain could establish an administrative RPC (Remote Procedure Call) connection to the client's registry.

Network and Transport Requirements

For the service to process incoming requests, several networking components had to be operational:

  • File and Printer Sharing: Either File and printer sharing for Microsoft Networks (using VSERVER.VXD) or File and printer sharing for NetWare Networks (using NWSERVER.VXD) was required to bind the RPC endpoints.
  • Network Protocol: A compatible transport protocol had to run on both the host and the target, typically NetBEUI, IPX/SPX, or TCP/IP.
  • System Agent / Background Tasks: The regserv.exe executable loaded alongside the network stack upon boot to listen for incoming registry modification calls.

Connecting via Registry Editor

Once the service was running and permissions were established, administrators edited the remote client's registry directly from their own workstations using the standard Registry Editor (regedit.exe):

  1. Launch REGEDIT.EXE from the Run dialog.
  2. Select Registry from the top menu, then click Connect Network Registry.
  3. Enter the computer name of the target Windows 95 machine.
  4. If authentication succeeded, the remote machine appeared in the folder tree alongside the local registry.

The connection exposed two primary hives: HKEY_LOCAL_MACHINE (hardware, network, and system software configurations) and HKEY_USERS (the profile of the currently logged-on user or default profile settings). Changes committed in the interface were transmitted across the network and applied in real time to the remote machine's SYSTEM.DAT and USER.DAT files.