Jump to content

Recommended Posts

Posted

Hi all,

 

I'm looking to configure and enable LDAPS on my domain controllers, purely to save me the constant phone calls during holiday times by allowing self-service password resets via Foldr.

 

I'm looking to enable it within an existing domain which has been running for around 2/3 years without LDAPS being enabled. Is there anything I should do before hand/ be prepared for?

 

As you can probably tell this is something I haven't enabled previously, so I'm treading carefully!

Posted

It isn’t difficult.

 

Ideally you should get publicly trusted SSL certificates, especially if the service that’s using it is an external one but you might be able to get away with certificates issued by an internal CA if your only going to use internal services and if that service trusts your root CA.

 

Once you’ve got your cert, it’s recommended to put it into the DC’s NTDS personal certificate store. You can put it into the computers if you prefer but it’s better in the NTDS one.

 

One thing, if you’re going to use a public cert, you will needs domain name that uses a routable domain name as most public CAs won’t issue cert’s to .internal, .local and the like any more.

  • Thanks 1
  • 1 month later...
Posted
Hi all,

 

I'm looking to configure and enable LDAPS on my domain controllers, purely to save me the constant phone calls during holiday times by allowing self-service password resets via Foldr.

 

I'm looking to enable it within an existing domain which has been running for around 2/3 years without LDAPS being enabled. Is there anything I should do before hand/ be prepared for?

 

As you can probably tell this is something I haven't enabled previously, so I'm treading carefully!

 

 

Hi @Techie2000, is there any particular guide you followed to enable LDAPS?

Posted
I didn't do it in the end! I thought I'd try and opt to setup password sets via O365 dirsync instead and that didn't work either. Was just really a case to save me getting emails to manually reset passwords but so far no luck, sorry :(
  • 1 month later...
Posted

Install AD Certificate services, set up as enterprise, done. (Unless you have loads of Windows Servers and want to not put it on a DC, then read the instructions)

 

Make sure you use sha256 not sha1, it's 255 better.

 

Test with ldp.exe, connect using domain name, not ip

Posted
Install AD Certificate services, set up as enterprise, done. (Unless you have loads of Windows Servers and want to not put it on a DC, then read the instructions)

 

Make sure you use sha256 not sha1, it's 255 better.

 

Test with ldp.exe, connect using domain name, not ip

 

That's only of use if you are internal services. If you are using an external service to connect via LDAPS, they will expect a publicly signed certificate and it's not always possible or reasonable to ask them to ignore untrusted certs. And to preempt your usual response to things like this, yes, I know, everything should use OAUTH but that's not always an option and switching over to a service that supports it isn't always an option either.

Posted

Generally you need both, you need internal CA for internal devices, and if you want external connections that can't use your CA, a signed cert.

 

If you just want to run the CA on your DC it's almost too simple, install it, done. The CA root cert is sent to the domain joined computers automatically too.

Posted
If you just want to run the CA on your DC it's almost too simple, install it, done. The CA root cert is sent to the domain joined computers automatically too.

 

Does it have to be on a DC? My understanding it could be a member server.

 

I'm playing with my test setup first, small little Domain on an old server, I've got a Domain all setup and installed the CA on a member server but the Enterprise CA is greyed out. Am I missing something?

 

Pete

Posted

If you install a CA on a DC and you ever need to demote it to replace it etc. you have made the job more complicated as you will need to move the CA first.

 

Virtualisation allows for separation of roles - it's best practice for a reason. :)

  • Thanks 2
Posted
Isn't best practise containers now? Either way, requires more licences than I have.

 

Why would you need to replace it, it's virtual.

 

Windows Server Roles aren't suitable for containerization...and you'll need to replace it when the OS is out of support.

 

Member servers rather than DCs will save you pain later - if you want to do it *properly* you'd also have an offline CA with online subordinate signing server.

 

This vastly reduces the pain of redeployment if Root Keys are ever compromised.

Posted

Im in the same boat at the moment and starting to get a bit too deep - i hate certs the best of times.

 

Originally a CA role was installed on a DC. I was told that if i didnt use the CA it could be removed so i did. About 10 years later i re-setup 2 servers which are currently turned off for CAs.

Posted

If people cared enough to set up pki properly they wouldn't be in this thread.

 

So, install DC, install ADCS on DC, wait 10 years, install it again on a new server OS version.

 

Or: Install DC, install MS, install ADCS on MS, wait 10 years, install it again on a new server OS version.

 

Can't see the difference, except another £250 for another copy of Windows server

Posted

Can't see the difference, except another £250 for another copy of Windows server

 

Sure, if you're installing it on another physical host. Otherwise, if you've got any sense, you've got a Windows Datacenter license which gives you unlimited VM guests on your host. Which I suspect you know, I'd be surprised if you didn't. Even if you're using Standard licenses, you can install two VMs on top of the host on the same license.

  • Thanks 1
Posted
Sure, if you're installing it on another physical host. Otherwise, if you've got any sense, you've got a Windows Datacenter license which gives you unlimited VM guests on your host. Which I suspect you know, I'd be surprised if you didn't. Even if you're using Standard licenses, you can install two VMs on top of the host on the same license.

 

That's £1500, no way I'd be getting that, nor could I see the point of running over 12 Windows VMs on one host.

Posted
You wouldn't be expected to run the same version for nine years though - normally it's three. Don't be obtuse for the sake of a poorly made point. It is a very cheap way to run multiple VMs.
  • Thanks 1
Posted

Yeah, no one's running Windows 2008 R2 still, that's not a thread.

 

My aim is always to give the least amount of money possible to Microsoft

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...