RPC Endpoint Mapper Client Authentication Policy using Intune

This post will help in understanding and setting the RPC Endpoint Mapper Client Authentication Policy Using Intune. Here we are going to implement this policy using Intune’s Configuration Profiles. This policy’s main aspect is providing hands-on experience configuring the RPC Endpoint Mapper Client Authentication Policy Using Intune.

RPC Endpoint Mapper Client Authentication Policy setting governs whether RPC clients are required to authenticate when their requests include authentication information for the Endpoint Mapper Service. It’s important to note that the Endpoint Mapper Service on computers running Windows NT4 (across all service packs) lacks the capability to process authentication information provided in this manner.

If you choose to disable this policy setting, RPC clients will not go through the authentication process when interacting with the Endpoint Mapper Service. However, this will enable them to establish communication with the Endpoint Mapper Service on Windows NT4 Server.

On the other hand, enabling this policy setting mandates authentication for RPC clients making calls that include authentication information. As a result, clients initiating such calls won’t be able to communicate with the Windows NT4 Server’s Endpoint Mapper Service.

Patch My PC

If you leave this policy setting unconfigured, it effectively remains disabled. In this state, RPC clients won’t undergo authentication when interacting with the Endpoint Mapper Service. However, they can still establish communication with the Windows NT4 Server’s Endpoint Mapper Service.

Note! – This policy’s effects will not take place until the system is rebooted.

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.1
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.1

Windows CSP Details RPCEndpointMapperClientAuthentication

We will see Windows CSP Details for this Policy setting RPCEndpointMapperClientAuthentication. This policy setting allows administrators to manage how RPC client authentication is handled, with a particular focus on compatibility with Windows NT4 and enhancing security in RPC communications. The choice of configuration should be based on your network’s specific needs and security considerations.

CSP URI – ./Device/Vendor/MSFT/Policy/Config/RemoteProcedureCall/RPCEndpointMapperClientAuthentication

Adaptiva
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.2
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.2

RPC Endpoint Mapper Client Authentication Policy using Intune

For RPC Endpoint Mapper Client Authentication Policy Using Intune, follow the steps stated below:

  • Sign in to the Intune Admin Center portal https://intune.microsoft.com/.
  • Select Devices > Windows > Configuration profiles > Create a profile.

In Create Profile, I select Windows 10 and later in Platform, and select Profile Type as Settings catalog. Click on the Create button.

PlatformProfile Type
Windows 10 and laterSettings Catalog
Table 1 – RPC Endpoint Mapper Client Authentication Policy Using Intune
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.3
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.3

On the Basics tab pane, I provide a name for the policy as “RPC Endpoint Mapper Client Authentication Policy.” Optionally, if you want, you can enter a policy description and proceed by selecting “Next.”

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.4
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.4

Now in Configuration Settings, click Add Settings to browse or search the catalog for the settings I want to configure.

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.5
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.5

In the Settings Picker windows, I searched for the keyword RPC, I found the category Administrative Templates\System\Remote Procedure Call and selected this.

When I select that option as stated above, I see the sub-category Enable RPC Endpoint Mapper Client Authentication. After selecting that, click the cross mark at the right-hand corner, as shown below.

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.6
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.6

I kept the Enable RPC Endpoint Mapper Client Authentication as Enabled and clicked on Next to continue.

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.7
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.7

Using Scope tags, you can assign a tag to filter the profile to specific IT groups. One can add scope tags (if required) and click Next to continue. Now in Assignments, in Included Groups, you need to click on Add Groups, choose Select Groups to include one or more groups, and click Next to continue.

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.8
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.8

In the Review + Create tab, I review settings. After clicking on Create, changes are saved, and the profile is assigned.

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.9
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.9

Upon successfully creating the “RPC Endpoint Mapper Client Authentication Policy, notification will appear in the top right-hand corner, confirming the action. You can also verify the policy’s existence by navigating to the Configuration Profiles list, where it will be prominently displayed.

Your groups will receive your profile settings when the devices check in with the Intune service. The Policy applies to the device.

Intune Report for RPC Endpoint Mapper Client Authentication Policy

From the Intune Portal, you can view the Intune settings catalog profile report, which provides an overview of device configuration policies and deployment status.

To track the assignment of the policy, you need to select the relevant policy from the Configuration Profiles list. Reviewing the device and user check-in status lets you determine if the policy has been successfully applied. If you require more detailed information, you can click on “View Report” to access additional insights.

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.10
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.10

Intune MDM Event Log

To verify the successful implementation of String or integer policies on Windows 10 or 11 devices through Intune, you can leverage event IDs 813 and 814. These event IDs provide valuable insights into the application status of the policy as well as the specific value assigned to the policy on those devices. In the case of this particular policy, the value is a String and is linked to the event ID 814.

By analyzing these event IDs, you can gain a clear understanding of the policy’s application status and the corresponding value associated with it on the devices in question.

To confirm this, you can check the Event log path – Applications and Services Logs – Microsoft – Windows – Devicemanagement-Enterprise-Diagnostics-Provider – Admin.

MDM PolicyManager: Set policy string, Policy: (RPCEndpointMapperClientAuthentication), Area: (RemoteProcedureCall), EnrollmentID requesting merge: (5B88AEF1-09E8-43BB-B144-7254ACBBDF3E), Current User: (Device), String: (<Enabled/>), Enrollment Type: (0x6), Scope: (0x0).

RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.11
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.11

When I opened the above Event log, I found that the policy I have applied to the device has been successfully implemented. By reviewing the log entry shown in the above image, the Event Viewer, I came across essential information, including the Area and Enrollment ID. These details play a significant role in identifying the corresponding registry path. To locate the specific information, please consult the table provided below:

AreaPolicyStringScopedEvent ID
RemoteProcedureCallRPCEndpointMapperClientAuthenticationEnabledDevice814
Table 2 – RPC Endpoint Mapper Client Authentication Policy Using Intune

The details presented in the table above for the RPC Endpoint Mapper Client Authentication Policy Using Intune can be employed to access the registry settings that hold the group policy configurations on a specific computer. To accomplish this, you can execute “REGEDIT.exe” on the target computer and navigate to the precise registry path where these settings are stored.

  • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\providers\5B88AEF1-09E8-43BB-B144-7254ACBBDF3E\default\Device\RemoteProcedureCall

When you navigate the above path in the Registry Editor, you will find the registry key named RPCEndpointMapperClientAuthentication. Also, when I navigated to the above path, I saw that the Registry Key was created.

Registry NameValue
RPCEndpointMapperClientAuthenticationEnabled
Table 3 – RPC Endpoint Mapper Client Authentication Policy Using Intune
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.12
RPC Endpoint Mapper Client Authentication Policy Using Intune Fig.12

We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click hereHTMD WhatsApp.

Author

Abhinav Rana is working as an SCCM Admin. He loves to help the community by sharing his knowledge. He is a B.Tech graduate in Information Technology.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.