MS-RPC Services to UUID Mappings

Question

MS-RPC Services to UUID Mappings

Anonymous

Hi, I am trying to gain some insights on MS-RPC services mapping to a UUID. I gained some context about MS-RPC here: https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/rpc-over-it-pro/ba-p/399898

I am looking for a reference table that includes all MS-RPC services available with corresponding UUID(s) but I could not locate any.

The closest thing I was able to find was the table from this link: https://supportportal.juniper.net/s/article/MS-RPC-UUID-Mappings?language=en_US

However, the table in the link above does not have all the MS-RPC services. I also read into GUID structure and how UUIDs are generated:

https://learn.microsoft.com/en-us/windows/win32/api/guiddef/ns-guiddef-guid#syntax

https://learn.microsoft.com/en-us/windows/win32/rpc/generating-the-uuid

I’m still seeking for answers on the following questions.

Is there a publicly available table that includes all the MS-RPC services with corresponding UUID(s)?
I see that one service can map to more than one UUIDs. I want to confirm that there’s no instance where two different services map to a same UUID.
Is it possible to have a combination of two or more services map to a single UUID which is different from each service’s UUID? If so, is the UUID (for the combination of two or more services) randomly generated or is there a pattern with regards to any of the service’s UUID (i.e. reusing the same final 12 hexadecimal digits)?
Is there a different UUID assigned for the same service with a different version?

Thank you.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

Accepted answer

0 additional answers

Answer 1

Hello,

Regarding the issue of MS-RPC mapping UUID, here are some references:

Through inquiries, Microsoft currently does not provide a complete table of mapping between MS-RPC services and their corresponding UUIDs. The generation and management of UUIDs involves a series of complex processes. Usually, if you work in a specific environment or framework, you can handle the mapping and generation logic of multiple service UUIDs by writing custom code.
The server registers its interface by calling the RpcServerRegisterIf function. In addition, the server can support multiple versions of the same interface, each with its own interface function implementation. Therefore, a service may have multiple UUIDs, but each UUID is unique, and no two different services are mapped to the same UUID.
UUID is a string containing a set of hexadecimal digits, and each interface has a different UUID. The generation is usually done by a computer to ensure its uniqueness. Therefore, the UUID of each service is unique, and there will be no situation where a combination of two or more services is mapped to a single UUID that is different from the UUID of each service.
For standard interfaces with the same GUID and different version numbers, connection is possible only when the major version is the same and the client is not higher than the minor version of the server. Therefore, there may be different UUIDs for the same service with different versions.

Hope this information can help you.

References:

Registering Interfaces - Win32 apps | Microsoft Learn

Generating Interface UUIDs - Win32 apps | Microsoft Learn

uuid attribute - Win32 apps | Microsoft Learn

We value your feedback, click Yes or No to help us improve the support experience.

Best regards,

Jacen Wang

Share via

MS-RPC Services to UUID Mappings

0 additional answers