myITforum.com Community Forum myITforum.com Community Forum

Home  Forums  Blogs  Live Support chat  Search Articles  Wiki  FAQ  Email Lists  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Photo Gallery  Member List  Search  Calendars  FAQ  Ticket List  Log Out

All Forums RSS Feed Subscription:


  


Disabled DCOM causes Client Push failures, need enterprise-wide fix

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
  Printable Version
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Disabled DCOM causes Client Push failures, need enterprise-wide fix Page: [1]
Login
Message << Older Topic   Newer Topic >>
Disabled DCOM causes Client Push failures, need enterpr... - 4/15/2008 7:59:20 PM   
jmm

 

Posts: 2
Score: 0
Joined: 4/15/2008
Status: offline
Issue:
Client Push yields the following error in ccm.log for ~20% of the targeted machines:

Unable to connect to WMI on remote machine "computername", error=0x80070005 (80070005 = access denied)
 
Root cause identified. 
Need assistance to identify enterprise-wide solution, such as using SCCM to create a report of all workstations that failed to install the SCCM client due to the above error.
 
Objective:
SCCM2007 in Mixed Mode.
No Network Access Account specified, but SCCM Primary Site Server computer account is a local administrator on all workstations.
Cannot use Group Policy Client Deployment Method due to conflicting WSUS GPO for unmanaged workstations.

 
Assessment:
Root cause of the error above is the Component Services option "Enable Distributed COM on this computer" is disabled.

 
This issue can be resolved by remotely running "reg add \HKLM\Software\Microsoft\OLE">\\<hostname>\HKLM\Software\Microsoft\OLE /v EnableDCOM /t REG_SZ /d N /f" and rebooting, or editing the option through the GUI, as per http://support.microsoft.com/kb/825750 
 
There are hundreds of machines that need to have DCOM enabled to allow a successful Client Push.
 
Does anyone know how to leverage SCCM collections, queries or reports to generate an exportable list of machines affected by this issue?
That would allow me to generate a script to enable DCOM on all the affected machines.

 
Thanks in advance to any efforts in solving this issue!
 
jmm
Post #: 1
RE: Disabled DCOM causes Client Push failures, need ent... - 4/16/2008 11:13:19 AM   
mserafine

 

Posts: 1660
Score: 157
Joined: 4/7/2003
Status: offline
I needed to reword this a little.

First, without the SCCM client installed on the computers, you pretty much won't be able to leverage SCCM to determine what machines have the registry value that you mentioned, nor will you be able to do much of anything else because the agents within the client software are required for most of the actions that can be peformed.

Can you not use any of the typical installation methods to get the client on the computers?

Manual installation is obviously out of the question, but if you can't use any of the other methods outlined here, http://technet.microsoft.com/en-us/library/bb694166.aspx, then you'll find things rather difficult. And in that case, the only other option that I can think of is running a script (under an admin's credentials), but if you're going to go that route, you might as well code it to install the client for you (in addition to adding that registry entry). 

The script would need to locate the systems by querying AD or the SMS database, and would need logic to determine things like 1) is the computer on the network and accessible, 2) is the client already installed, 3) does the registry entry that you mentioned already exist...you get the idea.

< Message edited by mserafine -- 4/16/2008 12:58:47 PM >


_____________________________

Mark Serafine, MCSE, MCTS | Senior Premier Field Engineer - Manageability (SMS, MOM, System Center) | Microsoft Corporation

(in reply to jmm)
Post #: 2
RE: Disabled DCOM causes Client Push failures, need ent... - 4/16/2008 1:05:15 PM   
mserafine

 

Posts: 1660
Score: 157
Joined: 4/7/2003
Status: offline
Oh, I forgot to mention that since none of the machines in question are clients and you won't be able to use use SCCM's traditional methods for obtaining the information you need, I suggest you write a script that reads the CCM.log file and parses each line that contains the error message to extract the name of the affected computer. Dump the names to comma-delimited file or something, and then you'll have your list.

_____________________________

Mark Serafine, MCSE, MCTS | Senior Premier Field Engineer - Manageability (SMS, MOM, System Center) | Microsoft Corporation

(in reply to mserafine)
Post #: 3
Page:   [1]
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Disabled DCOM causes Client Push failures, need enterprise-wide fix Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts



  
Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.438