AutoDiscovery not working on Windows/SQL2008R2 but OK for 2003/SQL2005
Hi I cannot get R2 to Autodiscover on a Windows 2008R2/SQL2008R2 server. Just keeps going on and on for ~45 mins, then fails. Manual discovery works fine. The 2008R2 server was even re-built and still no joy with Autodiscovery. On the same domain a 2003 Server with 2005 SQL was also built. this has no problems doing Autodiscovery. What could be the problem with the 2008R2 server? There are no errors in the Event logs when the discovery fails (All recent patches have been applied, CU3 etc). Thx, John Bradshaw
January 15th, 2011 1:34am

Hi John, At the first look it looks like disabled SQL Service Broker. Check it: SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager'. Then you want to check a firewall settings on SQL box. You can find all ports you need in Supported Configurations document. If you can - just turn off the firewall and see if that works. http://OpsMgr.ru/
Free Windows Admin Tool Kit Click here and download it now
January 15th, 2011 1:56am

Hi Alexey, I can discover manually OK, so I don't think it's the broker or firewall. I'm wondering if there is a known problem between 2008R2 client (OpsMgr) and Domain controllers which are all 2003?? JB
January 16th, 2011 2:23pm

Update.....In working with MS we seem to have identified a problem when discovering more than a certain number of devices/servers. It is with MS at the moment and they have gone away to engineer a hotfix. Shall let you know the progress. Thx, JB
Free Windows Admin Tool Kit Click here and download it now
January 16th, 2011 11:44pm

Still with MS support JB
January 21st, 2011 2:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics