Discussion Forums/AA Console/Questions

Answered

WMIprvse.exe is hogging lots of CPU resources on a VIRTUAL W2008 server

Tom C. Doan
asked this on December 09, 2009 10:46

Ever since we have installed Admin Arsenal as an eval, WMIprvse.exe is hogging a lot of CPU on another server... When we stop the Admin arsenal services, the problem goes away on this W2008 server.

Is there a way to exclude this server from being queried by Admin Arsenal?

 

Comments

User photo
Shane Corellian
Admin Arsenal

There are two methods that I can think of to accomplish this task. I think adding a specific feature to exclude specific computers would actually be beneficial so I will bring it up with the team.

In the mean time, here are the two options you have:

1) Move the Windows 2008 server to an Active Directory Organizational Unit (OU) above your "Root AD Container" defined in Admin Arsenal. This would effectively make the computer invisible to Admin Arsenal.

2) Deny Distributed COM rights for the account that runs Admin Arsenal.

For example: You run Admin Arsenal from the domain account called Tom.Waits. You do not want Admin Arsenal to perform WMI queries against the server "MyServer". You decide to run the command DCOMACLS.EXE (in your Admin Arsenal directory) to deny the account Tom.Waits WMI access to the system. From your Command window (CMD.EXE) go to your Admin Arsenal directory.

cd %programfiles%\brisworks\Admin Arsenal

dcomacls -deny *.R*:Domain\Tom.Waits -computer MyServer

You can verify that this took affect by running:

dcomacls -view -computer MyServer

You should see a minus sign (-) for Domain\Tom.Waits for the AL.R, LL.RA and LL.RL rights.

You can view the usage for DCOMACLS.exe here:

http://www.adminarsenal.com/documentation/index.html?dcomacls.htm

 

December 09, 2009 10:47
User photo
David Cockrell

I have a similar problem.  I want to exclude all servers in certain OUs though.  I have a few servers running Citrix and get complaints when scanning kicks off.  Is there a way to exclude an entire OU?

 

Thanks,

David

December 01, 2010 09:26
User photo
Shane Corellian
Admin Arsenal

The best way to exclude machines from management is to have these systems reside in OU's located above the OU that you choose as your root for AA. Any machine that exists in an OU below your root AA OU (the OU that you choose to synch within AA) will be seen and inventory will be attempted.

We don't have a way to exclude certain machines otherwise.

December 01, 2010 09:42
User photo
David Cockrell

I'm not thinking co-workers would like me rearranging AD just because of me using AA!  Is the heartbeat and inventory the only things going on that would bother machines?  I just unchecked Inventory in the preferences and assume that will stop the problem I'm having.

A different way to solve my problem may be to ensure the scans happen after hours.  Is there a way to tell AA when to do the inventory scan?

Thanks again,

David

December 01, 2010 10:43