Jump to content

Recommended Posts

Posted

We've been upgrading our DCs to 2025 and have stopped carrying out the upgrade on the rest because of GCDS. We have been running GCDS in LDAP mode on port 389. I did have a thread back in 2020 about setting up GCDS with LDAPS and it might be worth a re-visit but I'm asking, those that run GCDS with Server 2025 DCs and given that MS have bow dropped support for LDAP on Server 2025, what are plans / thoughts about moving forward?

 

I thought maybe LDAP Signing might help but as soon as i set

- Domain: LDAP signing to Require

- Network: LDAP client to Require

GCDS no longer works on port 389 or 3268 and it seems that we have to set up a CA server and import thr certificate into GCDS.

Posted

A few options spring to mind.

 

  • Setup LDAPS
  • Make a script to export the data from AD via Powershell and make the changes to Google via GAM. Might be quite a bit of work though.
Posted

Another option might be to migrate to Google’s cloud Directory Sync (under Directory in Google Admin). It is in Beta but we have it working well after a few initial issues in setup, and have now decommissioned GCDS.

It can sync from AzureAD or local AD using a VPN (although haven’t tried the latter).


 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...