Windows Server Essay -- Computers Software Essays

Windows Server There are some key differences between Windows DNS Services servers and non-Windows DNS server appliances in the areas of AD integration and security. For example, some non-Windows DNS server appliances lack complete AD integration features. Conversely, Windows DNS Service servers don't support encrypted zone transfer and update features like some non-Windows DNS server appliances do. (ref: DNS server appliances) One cant use any DNS service. Active Directory requires that the DNS support dynamic updates via RFC 2136; Windows 2000 has the advantage of being the only one that does it out of the box Those environments that already have Internet domains and DNS servers on their networks have two options.Either replace their existing DNS servers with Windows 2000 boxes or create a new internal domain to host the AD. For example, if your company is called WidgetCo, and all your internal servers are TCP/IP hosts on widgetco.com, you either need to create a sub-domain called ad.widgetco.com or you need to create something like widgetco.net, as one of my associates had to do at a large Manhattan-based international law firm. It's possible to make Unix DNS servers like BIND (Berkeley Internet Name Daemon) support Windows 2000 dynamic DNS, but it's a little tricky. Microsoft TechNet's white paper on Windows 2000 DNS provides information on getting your non-MS DNS to comply with RFC 2136. Chances are you'll need to upgrade your Unix server to the latest version of BIND, version 8.2, to make it work. Creating an entirely new domain may be less of a headache. (ref: How Microsoft went wrong with Active Directory) When Microsoft started to talk about AD and AD's DNS integration, the company said AD would operate with any DNS implementation that is compatible with the standards for dynamic DNS. DDNS is a key piece of the AD model. As the development of AD progressed, Microsoft downplayed the support for non-Win2K DNS servers. At press time, Microsoft claimed that Win2K will be compatible with UNIX's Berkeley Internet Name Domain (BIND) 8.2, but to fully utilize AD's features, you will need to use Win2K's DNS. UNIX advocates believe that NT isn't stable enough to provide the 24 X 7 service that DNS services require and that the Microsoft DNS implementations aren't sufficiently compatible with the open-source UNIX standards. Win2K and NT advo... ... Native Mode? When a domain is first installed, it is in mixed mode. The mode of operation can be changed from mixed mode to native, but this is not reversible. In native mode, Windows NT 4.0 Domain Controllers cannot participate in the domain. (ref :Step by step guide) Changing the Domain Mode Windows 2000 domains operate in one of two modes: ï‚ §Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Mixed Mode. Allows domain controllers running both Windows 2000 and earlier versions of Windows NT ® Server to co-exist in the domain. In mixed mode, the domain features from previous versions of Windows NT Server are still enabled, while some Windows 2000 features are disabled. You can change to native mode after making sure all domain controllers in your domain are running Windows 2000 Server. 4.Your organisation contains four geographic locations connected via slow links. Currently all locations belong to the one Domain with a number of domain controllers all located at one site. Users are complaining of slow authentication and access to AD information. Describe 2 different options you could consider to improve the performance of the Domain. Recommend one of the options providing reasons for your choice.