Configure DCOM

  • On the server to be managed click Start, click Run, type DCOMCNFG, and then click OK.
  • In the Component Services dialog box, expand Component Services, expand Computers, and then right-click My Computer and click Properties.
  • In the My Computer Properties dialog box, click the COM Security tab.
  • Under Launch and Activation Permissions, click Edit Limits.
  • In the Launch Permission dialog box, select ‘Distributed COM Users’. In the Allow column under Permissions for User, select Remote Launch and select Remote Activation, and then click OK.
  • Under Access Permissions, click Edit Limits.
  • In the Access Permission dialog box, select ‘Distributed COM Users’. In the Allow column under Permissions for User, select Remote Access, and then click OK.
  • Add the user account to the Distributed COM Users Group in Computer Management, Local Users and Groups on the Server to be managed.
  • Add the user account to the Performance Log Users Group in Computer Management, Local Users and Groups on the Server to be managed.

Configure WMI

  • On the server to be managed click Start, click Run, type wmimgmt.msc, and then click OK.
  • In the console tree, right-click WMI Control, and then click Properties.
  • Click the Security tab.
  • Select the Root namespace and then click Security.
  • In the Security dialog box, click Add.
  • In the Select Users, Computers, or Groups dialog box, enter the user account. Click the Check Names button to verify your entry and then click OK.
  • In the Security dialog box, under Permissions, select ‘Enable Account’ and ‘Remote Enable’ for the user account.
  • Ensure the permissions propagate to all subnamespaces.

CPU Ready value is cumulative between the number of vCPUs the VM is assigned. For example, a one vCPU VM has the measurement of 1000ms. For a VM with two vCPUs, the same performance drop would rise to 2000ms, or 1000ms per vCPU. For a VM with four vCPUs, it would be 4000ms.

Realtime Monitoring

CPU Ready / (interval * 1000) * 100 = Performance Penalty

Statistics Rollup Intervals

vCenter defines the following default intervals for rollups:

  • Real-Time: 20s interval (20 seconds)
    • CPU Ready / (20 * 1000) * 100
  • Daily: 5m interval (300 seconds)
    • CPU Ready / (300 * 1000) * 100
  • Past Week: 30m interval (1800 seconds)
    • CPU Ready / (1800 * 1000) * 100
  • Past Month: 2h interval
    • CPU Ready / (7200 * 1000) * 100
  • Past Year: 1d interval
    • CPU Ready / (86400 * 1000) * 100

Real World Examples

Here is a Database server real-time graph.  The average CPU Ready is 609.

609 / 22000 * 100 = 2.76% CPU Ready

width=795

Improving Performance

On this particular DB server, it was configured with 8vCPU.

width=795

After reducing the vCPU from 8 to 4, I used the next available day to review performance improvement (or not).

width=793

I can see now that my average is 7420ms, or 2.76% performance degredation.  Performance improvement of almost 45%!

When generating reports in OpManager v11 and exporting as PDF, the footer contains ManageEngine OpManager Page : as the footer.

To change this, on your OpManager install, navigate to the installation path of OpManager and modify confrandProps.properties file.  Add the following line, and customize accordingly.

pdfFooterText=Your Company or Whatever | email@yourdomain.com |  Page:

You do not need quotes surrounding the pdfFooterText variable.

Save the file and go generate a report and export to PDF.  Enjoy!

width=639

When browsing my Downloads folder, or any folder in general, on Windows 10 I have experienced the Working on it… message and it takes a few seconds to load.  This doesn’t matter if I have a lot of files/folders or just a few, it still hangs.

Resolution

Open Folder Options > Set Open File Explorer to This PC. Try WinKey + E now.

If it opens fine, then problem is with Quick access cache, which can be cleared by deleting *.automaticDestinations-ms from the following directory, using Command Prompt.

del %AppData%MicrosoftWindowsRecentAutomaticDestinations*.automaticDestinations-ms

Security vulnerabilities are addressed in WordPress 4.7.2. An XSS and SQL injection vulnerability (wp_query()) were discovered and have been patched.

Update your sites.

s
search
c
compose new post
r
reply
e
edit
t
go to top
j
go to the next post or comment
k
go to the previous post or comment
o
toggle comment visibility
esc
cancel edit post or comment