Microsoft Essential Business Server team is excited to announce the release of Microsoft IT Environment Health Scanner, the new diagnostic tool designed for administrators of small or medium-sized networks who want to assess the overall health of their network infrastructure. When run from a computer with the proper network access, the tool takes a few minutes to scan your IT environment, perform more than 100 separate checks, and collect and analyze information about the following:
ü Configuration of sites and subnets in Active Directory
ü Replication of Active Directory, the file system, and SYSVOL shared folders
ü Name resolution by the Domain Name System (DNS)
ü Configuration of the network adapters of all domain controllers, DNS servers, and e-mail servers running Microsoft Exchange Server
ü Health of the domain controllers
ü Configuration of the Network Time Protocol (NTP) for all domain controllers
This tool is based on the well-known EBS Preparation Wizard, which the EBS team has originally built for customers who were deploying Essential Business Server 2008 (see more on Preparation Wizard here). Very soon, however, the team noticed that Preparation Wizard was widely used, not just by customers who were deploying EBS, but anyone with Active Directory in their network who wanted to verify the health of their environment. That should have come as no surprise – after all, Preparation Wizard ran over 100 different checks which were based on most common issues resolved by Microsoft Customer Support Services over the past 10 years!
Building on the success of the Preparation Wizard, the team is now introducing the Microsoft IT Environment Health Scanner. Just like its predecessor, Microsoft IT Environment Health Scanner scans your network, identifies various networking and provides links to knowledge based articles that explain how to correct these issues. The one main difference is that the new tool is completely EBS-agnostic. That is, if in order to run Preparation Wizard, the administrator had to answer several questions specific to EBS deployment. Microsoft IT Environment Health Scanner, on the other hand, requires no prior EBS knowledge to run. And of course, this new tool is completely free!
Go give it a try!
Julia KuzminovaEBS Program Manager
Just tried it. It crashes a few moments after starting the scan.
Could it have something to do with our DCs running WS08 Core?
Can you please send us zipped Data and Logs folders (under %systemdrive%\Microsoft IT Environment Health Scanner\Wizard) so that we can investigate the crash?
Looks like the network adapter gateway testing is confused. It tells us we need more than one value on a given nic and points to the subnet address x.x.x.0/24 rather than our true gateway.
Error's out after a few minutes and all scan's are skipped with the error: "Error: The value of the serverReferenceBL attribute for ,<servername> was not set."
I got this same error with EBS prep tool. The server it errors on is not even a DC...just a test server. How do I either correct what it is looking for or get passed it?? Thx
The reason for this failure ("Error: The value of the serverReferenceBL attribute for ,<servername> was not set.") is that the tool is detecting the server as a bad DC (that is, that test server was probably once a DC, but was not properly dcpromo-ed down).
If the server is not a DC anymore, clean it up from AD using the instructions here:
I, also, am having issues with the scanner crashing after a few minutes. Would you like me to send you our logs as well?
I have problems runing this tool in my network, The problems are related to conectivity issues with the security server.
The XXXXXXX server could not be accessed using WMI. Actions that you can perform to resolve this issue might include stopping the firewall before you run the wizard, ensuring that the server is available, installing WMI provider on a Windows 2000 server, enabling WMI access on the server, or removing the server object from Active Directory Sites and Services if the server has been decommissioned.
Most likely, your firewall is blocking access to WMI. Are you running the Health Scanner in an EBS environment (or any environment with TMG/ISA)?
If yes, we have to be able to query WMI on the TMG server from the workstation or server you are running the wizards on. If you can sacrifice taking the entire network offline while the wizard runs (this won't work if you have remote sites), running "net stop fweng /y" from the TMG server will allow the tool to run.
The more complete way to do this is to temporarily open up TMG to allow the wizard to run:
1. Create a bi-directional allow-all access rule between the two machines:
Name: Allow all
Protocols: All outbound traffic
From: local host; machine running wizards
To: local host; machine running wizards
Users: All users
Right-click on the rule, choose "Configure RPC Protocol", and de-select "Enforce strict RPC compliance"
2. Edit the 'RPC (all interfaces)' protocol in toolbox and deselect the RPC filter.
3. Right-click on Firewall Policy, Choose 'edit system policy ...', and choose 'Active Directory'. De-select "Enforce strict RPC compliance"
Click apply and ok to save the settings, and refresh Monitoring\Configuration until it shows 'Server configuration matches the Configuration Storage server configuration'
Yes, please feel free to send us the logs.
Can you please make sure you entered the correct internal IP address of your main firewall on the Firewall IP page (note: it may or may not be the same as the gateway)? If so, and you are still having issues, please email us your logs!
I am having problems running this in our environment. We are a pure Windows 2003, Native, Active Directory, with Cisco routers, firewalls and switches. The software installs just fine but when i run it, I put the IP address and Subnet of our main Cisco firewall, and the subnet mask it has, and then i add our other IP ranges, but when i say scan it looks like it is trying to collect data but i get the following message:
The specified domain controller doesn't appear in ServerTable: SERVERNAME (the name of one of my DCs)
and then it skips the rest of the tests. I have tried running this from a local workstation, from a member server, and from one of our DCs, but i get the same type of message (the DC listed usually changes) but the results are always the same. I really would love to get some results.
Please help if possible
Is SERVERNAME still a DC in your environment? Generally, the tool gives that error for the servers it finds in AD that used to be DCs, but were not demoted corretly/successfully (hence, data is left in AD that needs to be removed).
Can you please send us your logs (zip Data and Logs folders under %systemdrive%\Microsoft IT Environment Health Scanner\Wizard)?
They are always active domain controllers in our environment. I have sent a zip of the two logs to the address requested.
thanks for the help
Another crasher here...logs sent to the posted email