Is installing the PCloud Connector on a Windows hybrid joined (joined to AD and Entra) a supported configuration?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Is installing the PCloud Connector on a Windows hybrid joined (joined to AD and Entra) a supported configuration?

L2 Linker

My client wants to use Windows hybrid joined servers (joined to AD and Entra) rather than traditional AD joined servers due to a non-CyberArk related requirement. I haven't found any clear guidance from CyberArk on the topic, and the only mentions I have found of hybrid joined servers in the community are fairly old, slightly unclear and negative.

 

Does anybody have any experience of installing the Windows Connector on Hybrid joined servers?

1 accepted solution

Accepted Solutions

L7 Applicator

Hi @Rob Seymour​ 

 

You are right, there is no specific mention in the documentation of this requirement.

 

Please note I've not yet configure Connector on Hybrid server. However, I 'think' the connector should work fine and reasons it should work are,

 

The Windows Connector expects a domain-joined machine (to traditional on-prem AD) , connectivity to DCs and the ability to impersonate accounts, access shares, manage services, etc.

 

A hybrid-joined serves should work fine if It’s joined to an on-prem domain, It can resolve and communicate with on-prem DCs, having Kerberos authentication for privileged account operations and its not Azure AD Join only

 

The connector behaves just like any other domain-joined server and hybrid join only impacts Entra ID access and conditional access policies

 

The Kerberos authentication may fail if DNS or domain trust isn’t properly configured and it can also fail if group policy is not applied correctly due to hybrid join conflicts, it may cause permission

 

 

Hope it helps !

View solution in original post

2 REPLIES 2

L7 Applicator

Hi @Rob Seymour​ 

 

You are right, there is no specific mention in the documentation of this requirement.

 

Please note I've not yet configure Connector on Hybrid server. However, I 'think' the connector should work fine and reasons it should work are,

 

The Windows Connector expects a domain-joined machine (to traditional on-prem AD) , connectivity to DCs and the ability to impersonate accounts, access shares, manage services, etc.

 

A hybrid-joined serves should work fine if It’s joined to an on-prem domain, It can resolve and communicate with on-prem DCs, having Kerberos authentication for privileged account operations and its not Azure AD Join only

 

The connector behaves just like any other domain-joined server and hybrid join only impacts Entra ID access and conditional access policies

 

The Kerberos authentication may fail if DNS or domain trust isn’t properly configured and it can also fail if group policy is not applied correctly due to hybrid join conflicts, it may cause permission

 

 

Hope it helps !

L2 Linker

Thank you Malhar, this is helpful!

  • 1 accepted solution
  • 158 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!