Link to home
Start Free TrialLog in
Avatar of Doug Poulin
Doug PoulinFlag for Canada

asked on

remote assistance not working for server 2012

We have two servers 1st one is the primary domain controller.  The second is a backup domain controller as well as our remote desktop server.  The big problem we are having is that server 2012 doesn't support viewing a rds user's console.  This is a big problem for us in being able to provide support.

One of the suggested workarounds is to use remote assistance.  So I've added remote assistance to the first server.  Since that is the machine that we are going to provide remote support from.  I've set up the GPO's to allow this to happen.  I've opened the appropriate firewall settings (also in a gpo).

When I try to run I get the following entry in the event log.

There was a problem interacting with COM object 833E4010-AFF7-4AC3-AAC2-9F24C1457BCE.  An outdated version might be installed, or the component might not be installed at all.

I know this is not a firewall issue since turning off the firewall has the same result.

Do I have to install something on the target host as well?
ASKER CERTIFIED SOLUTION
Avatar of Mahesh
Mahesh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Doug Poulin

ASKER

The following event log entry appears in the first server (owl).

DCOM got error "2147746132" from the computer raven.par... when attempting to activate the server:
{833E4010-AFF7-4AC3-AAC2-9F24C1457BCE}

raven is the target machine for support.  

No error show up on ravens event log.

A quick browser through the net suggests making changes to the COM+ properties on raven.  I've tried adding owl to the default options and setting the remote tick boxes.  So far nothing different has occurred.
The following article says that it should work and how.  It turns out that it's slow to start up (like about a minute on our server with nothing running on it).  But it does work.

http://microsoftplatform.blogspot.ca/2013/06/what-new-in-windows-server-2012-r2.html