0

0

The problem description is roughly the same as the problem in this thread: http://social.technet.microsoft.com/Forums/en/operationsmanagergeneral/thread/d315f7b5-ebc3-4285-b0b8-04aaa75d8b4c Their problem was an incorrect dns suffix setting... I st

0

0

Ok, another shot in the dark then: You said the Agents can find the MS server on FQDN on port 5723. Can the MS server find the Agents on FQDN? (and matching the certificate names, of course)

0

0

We've had similar problems like this with certificates and 32 bit version agents on 64 bit servers. If you have 64 bit servers you MUST use the 64 bit agent or else you won't get a connection. Just my 2c ;-)

2

2

Don't know what you guys did, but it looks to me like the site had a great performance boost. Everything reacts really quick. Good job, guys!!!

0

0

Dear Frank, You can do this with some SQL queries directly against the Operations Manager database: Before you start with these queries: Make backups and try them out in a test environment if possible... Fist, get a list of all computers without

0

0

Hi Andreas, I posted this question a while ago: http://www.systemcentercentral.com/tabid/60/indexId/54722/tag/Forums/Default.aspx#vindex54727 I never got around to post it, but I answered my own question. The problem was that the SDK service account was c