This has been discussed before but with no response, official or not, from Microsoft: http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/8a9705a6-3aff-40f5-b144-7356d9ccbe95/ Note: my version of EXBPA is 12.12 (Exchange 2007 SP2). EXBPA reports that the DHCP Client is not running. Yet, if I look in services.msc, DHCP Client is "Started" {or "Running" I dare assume) and it is also set to "Automatic". Is this a bug? If so, it has not been fixed since it was first discussed in the link above.

I ran this in my ENV which has Exchange 2007 SP3 and not able to reproduce issue. Its looking issue with SP2, Do you have plan for upgrade of SP3. Anil

In my Exchange 2007 SP2, I dont see this warning in the BPA Health check -unless I stop actually stop the service- From the definition of the warrning: The Microsoft® Exchange Server Analyzer Tool queries the Win32_Service Windows® Management Instrumentation (WMI) class to determine the value of the Started key for the Dynamic Host Configuration Protocol (DHCP) Client service. If the Exchange Server Analyzer finds that the value of the Started key for the DHCP Client service on an Exchange server is set to False, the Exchange Server Analyzer displays a warning. So I will suggest: - Make sure that the server you are checking the service status in, is the same server listed in the warrning "The DHCP Client service is not running on server SERVERNAME .ABC.LOCAL. " - Open Exchange Managment shell, and run this command: Get-WmiObject win32_service | Where {$_.DisplayName -eq "DHCP Client"} | fl DisplayName,Started and confirm the result is: DisplayName : DHCP Client Started : True Ibrahim Al Masry http://www.ibra.me/

SP3 upgrade? No, not immediately. Perhaps in a month or so.

Hello Ibrahim, Thank you for the suggestion. This is the result (directly copied and pasted from the EMS): [PS] C:\>Get-WmiObject win32_service | Where {$_.DisplayName -eq "DHCP Client"} | fl DisplayName,Started DisplayName : DHCP Client Started : True I tried this too (confirms above result): [PS] C:\>Get-service | Where {$_.DisplayName -eq "DHCP Client"} Status Name DisplayName ------ ---- ----------- Running Dhcp DHCP Client I'll try running the EXBPA again and check again. EDIT - well, it's OK this time. Not sure why it alerted me the other time.

Hello Ibrahim, Thank you for the suggestion. This is the result (directly copied and pasted from the EMS): [PS] C:\>Get-WmiObject win32_service | Where {$_.DisplayName -eq "DHCP Client"} | fl DisplayName,Started DisplayName : DHCP Client Started : True I tried this too (confirms above result): [PS] C:\>Get-service | Where {$_.DisplayName -eq "DHCP Client"} Status Name DisplayName ------ ---- ----------- Running Dhcp DHCP Client I'll try running the EXBPA again and check again.

Hi Le, I think you can safely ingore the warning since you should always assign a static IP to the Exchange server.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

yes and assuming that exchange server has been assigned static ip address we can remove this check from EXPBADhruv

Hello, Actually, I think you can ignore that warning only if the service is actually started and working, but if the service is stopped, you should worry as per this article even if -and you are- configured Exchange server with static IP: This warning indicates that the DHCP Client service is not running. The DHCP Client service performs dynamic Domain Name System (DNS) updates. If the DHCP Client service is not running, dynamic update failures will occur. If an Exchange server is not running this service, the most common problem will be mail flow problems. Note: The DHCP Client service must be running, even if the server is configured to use static IP addresses rather than DHCP. Ibrahim Al Masry http://www.ibra.me/