Restructuring DNS Infrastructure
Posted by sainath in Active Directory on April 14, 2013
Solution Description:
HYDRA DNS infrastructure has potential security issues which provide external entities to gain control over the infrastructure and access the application data or the servers. AVA performed critical analysis of HYDRA infrastructure and produced the report which requires infrastructure should be redesigned.
HYDRA organization hosts their infrastructure in New South Wales. There are 2 major sites connected with high speed networks, the infrastructure is hosted on Microsoft infrastructure servers. The Headquarters is in Sydney followed by Secondary site in Melbourne.
HYDRA existing Microsoft infrastructure is operational on Windows Server 2008 R2 with single Active Directory Forest and having multiple domain controllers configured across the physical sites. HYDRA existing environment has critical Security issues with respect to their Domain Naming System and require redesigning their Domain Naming System and ensure HYDRA security policies are met. HYDRA is engaging AVA, a Microsoft Premier Consulting firm to perform the DNS restructuring which involves placing the DNS servers in DMZ zone and route the internal DNZ server requests to DMZ DNS server instead of public ISP servers.
Detailed design can be found from the below link
Download Document:
Restructuring DNS Infrastructure
Domain Restructuring – Designing RODC
Posted by sainath in Active Directory on April 10, 2013
Introduction:
This document will describe design decision to implement Read Only Domain Controller in the existing Active Directory Forest. The infrastructure is assumed to have the fully operational Active Directory forest which is hosted on Microsoft Hybrid cloud infrastructure.
For complete solution , please download the file below
Download File:
Domain Restructuring – Server 2008 R2
Posted by sainath in Active Directory on April 8, 2013
Introduction:
This document will describe design decision to add Additional Domain Controller in the existing Active Directory Forest. The infrastructure is assumed to have the fully operational infrastructure which is hosted on Microsoft Hybrid cloud infrastructure
Document Link:
Installing Stand Alone Root CA – Server 2012
Posted by sainath in Uncategorized, Windows Security on April 3, 2013
Introduction:
Depending on the CA hierarchy to be designed, this article focus on the steps required to install offline root CA on Windows Server 2012. Following are the assumptions
a) Server will not be joined to the Active Directory domain
b) Root CA is configured as Offline
c) CAPolicy.inf is created under C:\windows and configured as per the CA hierarchy
d) Networking and Storage considerations are considered
e) Provision of User accounts are done ( local administrator permissions are configured accordingly )
Download File
Cannot Rename Computer Name or Unjoin Computer – Certificate Services 2012
Posted by sainath in Windows Security on April 3, 2013
Introduction:
Careful consideration should be made before installing Certificate Services on the Windows Server 2012. A proper CA hierarchy should be design along with Naming standards, CA names cannot be more than 64 characters in length. Naming convention rules which applied to Server 2008 R2 still holds good for Server 2012 such as
Considerations:
a) Names cannot contain special characters
b) Chinese / Arabic … supports 37 character long
c) Server Name becomes the Common Name for CA .
d) CN of the certificate should not be configured with FQDN
e) After installation of Certificate Services on Server 2012, Administrators cannot change the Server name or Unjoin the computer from domain. the only way to change the server name / unjoin from domain is to uninstall the Certificate Services.

To Unjoin / Change Computer Name:
1) On CA Server Navigate to Server Manager
2) Click Manage option located at top right corner of Server Manager , select Remove Roles and Features
3) Select CA Server from Server Pool and on Server Roles window, Uncheck Active Directory Certificate Service and click Remove Features
4) Restart the CA Server and administrators now will be able to Rename and Unjoin activities.
PrincipalContext ContextType – Extended
Posted by sainath in Active Directory on January 30, 2013
The ContextType acts as a store for PrincipalContext and they can be in any of the 3 forms
a) Domain
b) Machine
c) ApplicationDirectory
ContextType has 7 Methods to be used
-Compared To
-Equals
-GetHashCode
-GetType
-GetTypeCode
-HasFlag
-ToString
Each of the Method description can be find in Visual Studio.