Skip to main content

How to remove kerberos authentication on network name resource in windows 2003 cluster

How to remove kerberos authentication on network name resource in windows 2003 cluster?

The Microsoft(R) Exchange Server Analyzer Tool reads the following registry entry to determine the version of the Microsoft Windows(R) operating system that is running on the server:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\CurrentVersion
A CurrentVersion value of 4.0 indicates the computer is running Windows NT(R) Server 4.0. A value of 5.0 indicates the computer is running a Windows 2000 Server operating system, and a value of 5.2 indicates the computer is running a Windows Server(tm) 2003 operating system.
The Exchange Server Analyzer also queries the Active Directory(R) directory service to determine the value of the serialNumber attribute for all objects with an object class of msExchExchangeServer. If the string value includes "Version 5.5," the computer is running Exchange Server 5.5. If the string value includes "Version 6.0," the computer is running Exchange 2000 Server. If the string value includes "Version 6.5," the computer is running Exchange Server 2003.
Finally, the Exchange Server Analyzer reads the following registry value to determine whether Exchange is running in a cluster with a Kerberos-enabled Network Name cluster resource:
HKLM\Cluster\Resources\(Resource GUID for Network Name resource)\RequireKerberos
A value of 0 for RequireKerberos indicates that the Network Name resource is not enabled for Kerberos and a value of 1 indicates that the Network Name resource is enabled for Kerberos.
If the Exchange Server Analyzer finds the value for RequireKerberos set to 1 on an Exchange 2000 Server virtual server that is running in a Windows 2000 Server server-based cluster, a warning is displayed.
This warning indicates that a Kerberos-enabled Network Name cluster resource is being used for an Exchange 2000 Server virtual server. This is not a supported configuration, and should be corrected as soon as possible. As stated in the Microsoft Knowledge Base article 235529, "Kerberos support on Windows 2000-based server clusters" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=235529), Kerberos authentication for an Exchange 2000 Server Network Name resource is not supported. Exchange 2000 Server has not been tested to ensure that a clustered Exchange 2000 Server virtual server supports Kerberos authentication.
http://i.technet.microsoft.com/Platform/Controls/CollapsibleArea/resources/minus.gif To correct this warning
1.   Open a command prompt on any node in the cluster.
2.   Run the following command: cluster res "Name of Network Name Resource" /priv requirekerberos=0:dword
http://technet.microsoft.com/en-us/library/Aa997566.note(en-us,EXCHG.80).gifNote:
The resource name should be enclosed in quotation marks.
3.   Take the Network Name resource offline and delete it.
4.   Open Active Directory Users and Computers.
5.   Locate the computer account object for the deleted Network Name resource and delete it from Active Directory.
6.   Create a new Network Name resource for this Exchange Virtual Server (EVS) and do not make it Kerberos-enabled. You can use the same name and configuration as the Network Name resource that you deleted in step 3.
7.   Bring the new Network Name resource online, and then bring the remaining resources in the EVS online.


Comments

Popular posts from this blog

INSTALL CISCO VPN CLIENT ON WINDOWS 10 (32 & 64 BIT). FIX REASON 442

This article shows how correctly install Cisco VPN Client (32 & 64 bit) on Windows 10 (32 & 64 bit) using simple steps, overcome the ‘ This app can’t run on this PC ’ installation error , plus fix the Reason 442: Failed to enable Virtual Adapter error message . The article applies to New Windows 10 installations or Upgrades from earlier Windows versions and all versions before or after Windows 10 build 1511 .  To simplify the article, we’ve broken it into the following two sections: How to Install Cisco VPN client on Windows 10 (clean installation or upgrade from previous Windows), including Windows 10 build prior or after build 1511 . How to Fix Reason 442: Failed to enable Virtual Adapter on Windows 10 Figure 1. The Cisco VPN Client Reason 442: Failed to enable Virtual Adapter error on Windows 10 HOW TO INSTALL CISCO VPN CLIENT ON WINDOWS 10 (NEW INSTALLATIONS OR O/S UPGRADES) The instructions below are for new or clean Windows 10 inst...

Linux File and Directory Permissions

file & directory protection is a essential of any OS and Linux OS is no exception for it! These authorizations allow you to choose exactly who can access your files & directory, providing an overall improved system security. There was one of the major flaws in the older Windows operating-system where, by standard, all users can see each other people's information (Windows 95, 98, Me). For overcoming it, editions of the Windows based computer system such as NT, 2000, XP and 2003 lot more security features added. They fully support file & directory permissions, just as Linux system has since the beginning. Together, we'll now assess a directory listing from our Lab Linux system hosting server, to help us understand the information provided. a simple 'ls' command will give you the file and directory listing within a given directory, including the option  '-l' will display number of new areas that we are going to discuss here:

How to create a Hirens Boot CD 15.2 USB Disk

Hiren’s BootCD (HBCD) is a bootable CD that contains a set of tools that can help users to fix their computer if their system fails to boot. More specifically, HBCD contains hardware diagnostic programs, partition tools, data recovery utilities, antivirus tools and many other tools to fix your computer problems.  I write this article because I use Hiren’s BootCD frequently to troubleshoot computer problems, specially when a computer doesn’t boot anymore due to a virus attack or due to a corrupted file system. In this article you will find instructions on how to put Hiren’s BootCD on a USB flash drive (stick) in order to troubleshoot computer problems in the future.