Do you have an internal Windows CA? With new products all now making use of
certs (E2K7, OCS, SCOM, et al) it makes sense IMO to implement your own CA
internally for such certs, using purchased certs at the ISA level of course.
This way, you can create and re-create your internal certs as often as
If you point the clients to the NLB FQDN and set the autodiscovery stuff etc to
the NLB address, then all you really need is that and the autodiscovery FQDN as
well(dont forget autodiscovery!)
No need to add the .local and actual host names of the servers unless you
really want to.
__
Admin Issues
Subject: RE: NLB CAS SSL Certs
If you point the clients to the NLB FQDN and set the autodiscovery stuff
etc to the NLB address, then all you really need is that and the
autodiscovery FQDN as well(dont forget autodiscovery!)
No need to add the .local and actual host names of the servers
25, 2008 6:24 AM
To: MS-Exchange Admin Issues
Subject: RE: NLB CAS SSL Certs
Just make you set the avail and autodiscovery stuff
(AutoDiscoverServiceInternalUri), etc.. via powershell to point to the
FQDN of the NLB.
-Original Message-
From: Matt Bullock [mailto:[EMAIL PROTECTED]
Sent
To: MS-Exchange Admin Issues
Subject: RE: NLB CAS SSL Certs
If you point the clients to the NLB FQDN and set the autodiscovery stuff
etc to the NLB address, then all you really need is that and the
autodiscovery FQDN as well(dont forget autodiscovery!)
No need to add the .local and actual host
