Home

 
 
 

Search Knowledge Base


Knowledge Base Web View
Total Records: 103
ID Title Type Of Article
1155 
Change your Microsoft 365 for business password to keep your account secure How To
1158 
Enable IE Compatibility Mode in Windows Edge Browser How To
1171 
Check Junk Folder and Quarantine Email on Office 365 to find missing emails How To
1317 
Reenabling Home Page or Web Page Views for Outlook Folders How To
1381 
Work Order Task Details Updates to Main Work Order How To
1404 
Setup Engage BMS Launch Batch File for Engage Startup How To
1439 
Engage SQL Errors and find a stuck user session means RDP Server needs to be rebooted How To
273 
Offboarding Checklist New Client
222 
Onboarding VMS check List New Client
993 
5 things customers want from their salesperson Sales and Marketing
1312 
Case Studies and Success Stories Sales Collateral
1323 
Sophos MDR Managed Detection and Response Sales Collateral
1228 
Customer Care Vendor Management & Billing Protocol SOP
223 
Marketing Monthly Reporting Information Support
687 
Fix for Error Call to GetCustomUI() for RibbonID "Microsoft.Excel.Workbook in Engage OLE" Support
712 
Windows 10 multiple display - windows are moved and resized on display power cycle or sleep Support
557 
DT Easy Button working with Remote Desktop or Parallels Support
517 
500 colours by colour name, Hex value, RGB value and Microsoft Access code number Support
490 
Excel Opens File Very Slowly in Remote Desktop Session RDS Support
221 
New Customer: Billing, Collecting, Memorized Transaction Support
217 
Deploy Kaseya Script to Install Symantec Antivirus in Server Support
204 
Outlook Connection Status Window Support
195 
3CX Adding BLF Settings across multiple extensions in the Management Console Support
161 
Distribution Group Mail Flow Support
132 
MS Access System Resources Exceeded Error Support
Add New  Records per page  3 of 5   
Engage Knowledge Base Web View         Support          Print
Title Active Directory Domain Naming Considerations      
Resolution Symptoms:
Cannot register new SSL requests or renwals for an exchange server that is part of a .local or .internal domain.
Possible Cause:
The reason that is given for the change is that the internal server names are not unique and therefore easy to falsify. With common names like server01 or webmail, the end user is never sure if it is actually dealing with the right party or with a malicious. The changing legislation for SSL Certificates shall start on 1 November 2015. This means, from that date, the invalid Fully-Qualified Domain Names (hereafter called FQDN) will no longer be accepted at the standard of the CA/Browser Forum and after that date such certificates may no longer be issued. All certificates issued after 1 November 2015 and meet this qualification will be revoked upon discovery. Users who are requesting a certificate on an invalid FQDN with an expiration date after 1 November 2015 should remember that their certificates will be revoked after 1 November 2015. After this date, no SAN SSL Certificate with a reserved IP address or internal server name will be issued either.
Resolution:
Data-Tech Resolution: For new rollouts or migrations from 2003 to server 2012; Setup the domain using a subdomain of the customers registered public domain. Example, datatech owns datatechitp.com. For the domain name we would set it up as CORP.DATATECHITP.COM this would be the FQDN. With this setup we will be able to register SSL certificates without running into a split DNS issue if we were to use just DATATECHITP.COM for the FQDN. For customers not looking to Migrate you can make adjustments to the internal domain name of the exchange server so that it reports your public domain. Information on how to do that is below. Microsoft Exchange Many people use a SAN SSL Certificate for Microsoft Exchange 2007 or 2010. It is recommended that these certificates will be modified from an internal server name to an external server name as soon as possible. A manual how to modify this on Exchange 2007 can be found here: https://www.networking4all.com/en/support/ssl+certificates/manuals/microsoft/exchange+2007/modify+.local/ The Exchange 2010 manual can be found here: https://www.networking4all.com/en/support/ssl+certificates/manuals/microsoft/exchange+2010/modify+.local/ Additional Alternatives Another alternative would be to use an additional external name. This can be done by using a .net domain name (.net = network) like DC1.DATATECHITP.NET. This would require the ownership of the .NET public domain name along with your .COM. Many companies purchase .COM, .NET, & .ORG when registering their domain however there may be instances where the customer does not own the .NET domain in which case you'll want to use a subdomain of their .COM.
Vendor Microsoft
Web Link http://social.technet.microsoft.com/wiki/contents/articles/17974.active-directory-domain-naming-considerations.aspx
Date Entered 5/1/2018
You Tube Link
Type Of Article Support
Article ID 109


  Copyright   Lietz Development, Inc. 1996. All Rights Reserved.