ASK

Promoting the first Domain Controller that runs Windows Server 2008 R2 is not a new thing. However, there are some pre-requisites that you need to look after before promoting your new Domain Controller. In this test scenario, we already have our  itserveronline.local  domain and forest which consists of only one Windows Server 2003 R2 Domain Controller with the DNS server role in a Windows 2000 Mixed domain. This article entails the different steps needed to successfully add the first and full operational Domain Controller and DNS server that runs Windows Server 2008 R2 in our forest. Prerequisites to the new server. The first step is to  prepare  the Windows Server 2008 R2 server. To start,  we need to ensure proper  Computer Name  of the new server (as per your naming convention). The next thing to check is the  IP address  of the new server. It is to be noted that the server needs to be assigned a  static  IP address. Since the new server will have to be a member server of

Scenario: we have a lot of DFS namespaces shared across on our domain, reachable via \\example.com\namespace1  and  \\example.com\namespace2 .  DFS namespaces has ABE enabled. After a reboot of a domain controller all namespaces are available through that server except for the content of the ABE enabled namespaces. After I import the NTFS rights again with ICACLS or FileACL  the content is available again . If we do another reboot or rest the permission the process starts over again. Cause: This issue occurs because of a logic error in the DFS Namespace service. This issue occurs when the service sets an Access Control List (ACL) to the DFS folders in a DFS version 1 namespace during the service start-up process.   Resolution: Installation of hotfix KB2464365 was carried out and the issue was no longer experienced. Hotfix Download: https://support.microsoft.com/kb/2464365

In Windows 2008 R2, Windows search has Indexing in built or as a part of it with some default file\folders inclusions. Other Indexing role is for Legacy OSs. In Windows Server 2008R2 Search in file content is not enabled by default and can be enabled by installing the File Server >  Windows Search Service role. Once the Windows Search Service is installed file searches on shares hosted on Windows 2008 R2 file servers can be off-loaded to the file server thereby conserving XenApp server resources. Users App data folder, Start Menu and Internet Explorer history will be also indexed….. and this is where the trouble can start: The Search database file C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb may grow very large – a “normal” size seems to be around 40 MB and a large DB can be 4 GB. The SearchIndexer.exe process has high disk I/O We decided to only allow file searches as it seemed the main cause was indexing of above mentioned contents.