Edit

DCOMSCMRemoteCallFlags

  • Article

Controls the behavior of calls from the local DCOM Service Control Manager (DCOMSCM) to a remote DCOMSCM.

Registry Entry

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole
   DCOMSCMRemoteCallFlags = value

Remarks

This is a REG_DWORD value.

Value Description
0x1 DCOMSCM_ACTIVATION_USE_ALL_AUTHNSERVICES
0x2 DCOMSCM_ACTIVATION_DISALLOW_UNSECURE_CALL
0x4 DCOMSCM_RESOLVE_USE_ALL_AUTHNSERVICES
0x8 DCOMSCM_RESOLVE_DISALLOW_UNSECURE_CALL
0x10 DCOMSCM_PING_USE_MID_AUTHNSERVICE

 

DCOMSCM_ACTIVATION_USE_ALL_AUTHNSERVICES Description

When the client issues an activation request that uses the default security settings, the local DCOMSCM uses the Negotiate authentication service when making the activation RPC call to the remote DCOMSCM. If the call fails, the local DCOMSCM makes the activation RPC call using no security.

Windows Server 2003 and Windows XP/2000: If the activation RPC call that uses the Negotiate authentication service fails, the local DCOMSCM makes the activation RPC call using Kerberos, NTLM, or other configured security providers. If no security providers work, the local DCOMSCM makes the activation RPC call using no security.

By setting this flag, the local DCOMSCM on Windows Vista or higher can be made to behave like pre-Vista systems. It is not recommended to set this flag unless required for compatibility reasons.

DCOMSCM_ACTIVATION_DISALLOW_UNSECURE_CALL Description

If the DCOMSCM_ACTIVATION_DISALLOW_UNSECURE_CALL flag is set, the local DCOMSCM does not make an unsecure activation RPC call. To enable clients to make activation requests with non-default security settings, specify the COAUTHINFO structure when making the activation request. In this case, the DCOMSCM_ACTIVATION_USE_ALL_AUTHNSERVICES and DCOMSCM_ACTIVATION_DISALLOW_UNSECURE_CALL flags are ignored.

It is not recommended to set this flag unless all the clients and servers in the network are fully authenticated.

DCOMSCM_RESOLVE_USE_ALL_AUTHNSERVICES Description

When the client unmarshals an object reference, the local DCOMSCM uses the Negotiate authentication service when making the OXID Resolution RPC call to the remote DCOMSCM. If the call fails, the local DCOMSCM makes the OXID Resolution RPC call using no security.

Windows Server 2003 and Windows XP/2000: If the OXID Resolution RPC call using the Negotiate authentication service fails, the local DCOMSCM makes the OXID Resolution RPC call by using Kerberos, NTLM, or other configured security providers. If no security providers work, then the local DCOMSCM makes the OXID Resolution RPC call using no security.

By setting this flag, the local DCOMSCM on Windows Vista or higher can be made to behave like pre-Vista systems. It is not recommended to set this flag unless required for compatibility reasons.

DCOMSCM_RESOLVE_DISALLOW_UNSECURE_CALL Description

If the DCOMSCM_RESOLVE_DISALLOW_UNSECURE_CALL flag is set, the local DCOMSCM does not make an unsecure OXID Resolution RPC call. In addition, the local DCOMSCM does not make an unsecure garbage collection Ping RPC call. It is not recommended to set this flag unless all the clients and servers in the network are fully authenticated.

DCOMSCM_PING_USE_MID_AUTHNSERVICE Description

The local DCOMSCM uses the Negotiate authentication service when making the garbage-collection Ping RPC call to the remote DCOMSCM. If the call fails, the local DCOMSCM makes the garbage-collection Ping RPC call using no security.

Windows Server 2003 and Windows XP/2000: If the garbage-collection Ping RPC call using the Negotiate authentication service fails, the local DCOMSCM makes the garbage collection Ping RPC call by using Kerberos, NTLM, and other configured security providers. If no security providers work, then the local DCOMSCM makes the garbage collection Ping RPC call using no security.

By setting this flag, the local DCOMSCM on Windows Vista or above can be made to behave like pre-Vista systems. It is not recommended to set the DCOMSCM_PING_USE_MID_AUTHNSERVICE flag unless required for compatibility reasons.

Authentication for Remote Connections

EnableDCOM

Registering COM Servers

Security in COM