New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Windows Update Sensor - Access denied creating an instance of the COM component

Votes:

0

Your Vote:

Up

Down

I am having trouble getting the windows update sensor to work with a non-administrator account - I get the following error: Creating an instance of the COM component with CLSID {4CB43D7F-7EEE-4906-8698-60DA1C38F2FE} from the IClassFactory failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).

If I add the user account to the Administrators group on the server then the sensor works fine, but for obvious reasons I do not want my account to be a member of the administrators group. I am using Server 2012R2.

My testing so far:

According to the article at https://kb.paessler.com/en/topic/71899-problems-with-windows-update-status-sensor, a key part of the powershell script is 'New-Object -ComObject Microsoft.Update.Session'.

I can run this piece of code successfully in a non-administrator user account when logged on to an desktop session such as my personal user account. However I cannot run this code successfully when running the code in a remote powershell session using the same user account.

The code does run successfully in a remote powershell session for an administrator account.

So, what specific permissions to I need to add to my account to be able to successfully run this in a remote powershell session? Anyone else have this scenario working?

permissions powershell prtg remote-powershell windows-update

Created on Aug 9, 2017 10:02:52 PM by  mpnzhc (0) 1



6 Replies

Votes:

0

Your Vote:

Up

Down

Hi mpnzhc,

Is the user you're trying to use a member of the Distributed DCOM Users group?


Kind regards,
Stephan Linke, Tech Support Team

Created on Aug 11, 2017 8:04:22 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Yes, the account is a member of both Distributed DCOM Users and Performance Monitor Users.

Created on Aug 15, 2017 8:34:39 PM by  mpnzhc (0) 1



Votes:

0

Your Vote:

Up

Down

I have come to the conclusion that the user must be a member of the administrators group. https://msdn.microsoft.com/en-us/library/aa387288?f=255&MSPPError=-2147217396

Created on Aug 17, 2017 1:38:17 AM by  mpnzhc (0) 1



Votes:

0

Your Vote:

Up

Down

And it works now? :)

Created on Aug 17, 2017 8:51:18 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

No, I do not want to elevate my probe account to an administrator. I have implemented an alternative solution to using this sensor, involving running a scheduled task on the target machine and fetching the results using remote powershell.

Created on Aug 17, 2017 9:40:05 AM by  mpnzhc (0) 1



Votes:

0

Your Vote:

Up

Down

That's what the new update sensor will do basically. The workaround is only temporary then :) Please keep an eye on https://www.paessler.com/prtg/history/stable to see when it's released shortly.

Created on Aug 17, 2017 10:08:06 AM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.