Is WMI required SCCM client 2007 agent for working

A Quick Qustion
Is WMI required SCCM client agent for working
what is the neccesity for WMI on SCCM client agent 2007
How SCCM CLient affect if WMI corrupt
could any one explaine
Its not only a question I am facing sccm client agent corrupted
shinu

Yes, functional WMI is a requirement for the SCCM client to work. One sign of WMI being corrupt is that the client won't receive any policies from the MP.
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson

Similar Messages

  • SCCM 2012, WMI, and SCCM Clients

    I have SCCM 2012 R2 CU2. I know that WMI has to be working for SCCM to be fully functional. I've done some reading on what I'm about to ask but I'd like to get some clarification on these points as I'm not totally clear on a few things:
    1) If when using wbemtest you discover there is no WMI connectivity between the DCs and siteserver to/from a client, including a non-domain member client, will the SCCM client install on that client machine?
    2) After the SCCM client is installed on a client machine, how essential is WMI connectivity to that SCCM client functioning?
    3) Was parts of SCCM use WMI?
    4) What permissions, including within DCOM, are needed for WMI to work with SCCM?
    Thanks.
    Ben JohnsonWY

    <...>
    I'm now back to getting that 0x80070427 error. That error code is also on another server (and with the same software and main functionality) that's on another domain but for now we'll stick with the server we've been talking about.
    <...>
    So the root question is, what is causing that 0x80070427. There's almost zilch on that error code on the internet.
    cmtrace is your friend :)
    open cmtrace, press CTRL+L and paste in the error/HRESULT:
    Lookup: 0x80070427
    Result:The service process could not connect to the service controller.
    Source: Windows
    Note that ConfigMgr relies heavily on non-ConfigMgr components, i.e. Windows base services/features. If those base services/features are mis-configured / disabled / broken, ConfigMgr *will* be impacted.
    In this case, the "Source: Windows" tells us that a Windows component is throwing the error.
    There should be additional/further detail/information available for this event in the log. Research that.
    The logs on the client will probably need to be examined, including the Windows event logs, to see why the service and service-controller are throwing this error. IF it's happening on two servers, and those servers both have  "the same software
    and main functionality", I'd be immediately suspicious of that software/function - perhaps that software is the cause of the service/controller issue..
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • SCCM Client Installation - Options for "Retry" Setting

    Hey Guys - 
    I've got a fairly straightforward question for you.  When the SCCM Client is installed / deployed to a system, successfully downloads locally, but fails, it retries installation by default every 30 minutes.  When creating an Orchestrator runbook
    for Client Health, I'm needing ccmsetup to try only once.
    So basically, I'm trying to find out how to make ccmsetup.exe not retry installation and simply fail.  There is a "Retry" command line switch for ccmsetup (/retry:<Minutes>) where
    minutes may be specified, however, this does not pertain to the actual installation, but the initial download of the setup files.  It does not have an affect on the client installation, itself.
    Yes, a simple script could be created which could kill the process after X, but prefer a native (or at least better) solution.
    Any ideas?  Thanks!
    Ben K.

    Hey - Thanks for the reply...
    I totally understand what you are saying - but - the only reason I thought I'd ask is because it's being used in an Orchestrator Runbook as mentioned and processes which run after it won't start until it completes.  When it loops, it never completes.
    Basically, yes - I understand what you are saying and have done it 100 times, but in this case was wondering if there was a more "supported" method by chance.
    Thanks - 
    Ben K.

  • Locked SCCM Client Package waiting for prestaged content, Cant use Client Push

    Hi there,
    I am having an issue with client push. When initiated the client is unable to find the client install package on the DP. The CCMSETUP log file on the client  reads "MP xxxxx.xxx.com didnt return DP locations for client package with the expected
    version". This could be caused by a boundry issue but the boundry information is set up correctly, and published into AD.
    The SCCM Client on the site server is not getting replicated properly to the DP's that we have setup and I think that this is causing the issue. The reason why its not gettiog to the DP is due to this error: "Distribution Manager is waiting for Package SG100001
    content to be prestaged on the distribution point" when we look at the content status of the SCCM client Package.
    We are unable to change the prestaged distribution point settings "automatic" as the package is the locked as its the SCCM client installation package and its waiting for us to prestage it on the DP. I have tried prestaging it, but it didnt
    work
    Any ideas as I have been stuck for two days on this now...
    Thanks in advanced.
    George

    Torsten you were right, The solution was as follows for anyone else having the same issue.
    As soon as you create a DP it appears that the client installation package automatically tries to distribute to the DP. If you created the DP as "Enabled for Prestage" while doing the setup then the SCCM client package will just wait for you to
    copy it manually. To reslove this I had to remove the "Enabled for Prestage Content" from the DP then go into the SCCM client Package, content location tab, select the DP and redistribute the package to the DP.
    Checking the Distribution Manager and PkgXferMgr.log assisted me in monitoring the content transfer to the new location.
    Thanks for your assistance.
    George
    George, I too concur that this fixed the issue.
    I had the same problem with my SCCM 2012 R2 CU4, where i updated the distribution point for the Configuration Manager Client Package. Thanks a million!

  • Send state message to SCCM after uninstall of SCCM client

    Hi Everyone,
    I have a batch file to uninstall the client from PC's, how would I could I send a state message back to SCCM to say the uninstall was successful? Asking because the console doesn't come back with success info, just waiting, and accepted on the program.....as
    the client is uninstalled etc.
    Currently running a simple ccmsetup.exe /uninstall as below, thanks for any help in advance.
    I know there's a Vb script to force any existing messages to be sent, but as the CCM WMI will not exist, there would be nothing to send, right?
    And I have to do this for a POF......Is this even possible??I could write to a log file with the name of the computer that just uninstalled, but really wanted to use a report.....or if there's another way to uninstall client and get the info in SCCM then
    please let me know, it's been a very long few days..... cheers :)
    @echo off
    echo Please Wait while the system is uninstalling Microsoft's SMS/SCCM Client.
    REM 'echo Checking for SCCM 2007 client...
    REM 'IF EXIST %windir%\System32\ccmsetup\ccmsetup.exe GOTO DEL07
    REM 'echo No SCCM 2007 client found.
    echo Checking for SCCM 2012 client...
    IF EXIST %windir%\ccmsetup\ccmsetup.exe GOTO DEL12
    echo No SCCM 2012 client found.
    echo Checking for SMSCFG file...
    IF EXIST %windir%\SMSCFG.INI GOTO DELINI
    echo No SMSCFG file found.
    echo All software already removed or no client installed.
    GOTO END
    REM :DEL07
    REM echo Found SCCM Client v2007. Removing...
    REM %windir%\System32\ccmsetup\ccmsetup.exe /uninstall
    REM RD /S /Q %windir%\System32\ccmsetup
    REM RD /S /Q %windir%\System32\ccm
    REM RD /S /Q %windir%\System32\ccmcache
    REM echo SCCM Client 2007 removed.
    REM IF EXIST %windir%\ccmsetup\ccmsetup.exe GOTO DEL12
    REM IF EXIST %windir%\SMSCFG.INI GOTO DELINI
    REM GOTO END
    :DEL12
    echo Found SCCM client v2012. Removing.
    %windir%\ccmsetup\ccmsetup.exe /uninstall
    REM RD /S /Q %windir%\ccmsetup
    REM RD /S /Q %windir%\ccm
    RD /S /Q %windir%\ccmcache
    echo SCCM Client 2012 removed.
    IF EXIST %windir%\SMSCFG.INI GOTO DELINI
    GOTO END
    :DELINI
    echo SMSCFG file found. Removing...
    del /F %windir%\SMSCFG.INI
    echo SMSCFG file removed.
    GOTO END
    :END
    echo Done!
    rem pause
    exit
    many thanks

    Don't you think this is a bit of a silly question? The client is what sends state messages therefore what would you expect to "send" the message that the client was removed? Seems about as effective as putting the address on the inside of an
    envelope and expecting the post office to just know where to send the mail.
    John Marcum | Microsoft MVP - Enterprise Client Management
    My blog: System Center Admin | Twitter:
    @SCCM_Marcum | Linkedin:
    John Marcum

  • Issue with sccm client installation

    hi,
    iam facing issue with sccm client 2007 installation on secondary site.please find the logs below,

    Refer for the above error : http://www.myitforum.com/forums/MSI-SMS-Advanced-Client-does-not-support-peruser-installations-m183336.aspx
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • WMI issues in VMware based Machine Windows 2008 R2 Servers affecting SCCM Clients

    Dear
    Brothers,<o:p></o:p>
    I came to
    an observation particularly in dealing with Windows 2008R2 Servers Vmware Based
    Virtual Machines with SCCM Clients.<o:p></o:p>
    Observation:<o:p></o:p>
    1. Windows
    2008R2 Virtual Machine with Vmware Tools installed (Also depending in the
    entries of WMI, I supposed). <o:p></o:p>
    When the SCCM Server Pushes the client on this Servers, I found out that the SCCM Client
    seems to be installed perfectly but when I tried to perform a remote WMI Query
    and the response is displayed below (The RPC Server is unavailable).<o:p></o:p>
    Now, I know that this kind of issues is something to do about DCOM Configuration
    for Remote Access right?
    Well, sad to say the settings has been checked, trippled checked actually to make sure it is correct with the correct permissions required and proven correct up to the last settings.
    I even compare the settings to those in some Windows Servers with Working WMI Remote Access.
    =========
    What I have observed is that when we make a VMware Systems and install the
    VMware Tools (see picture below) first before installing the
    SCCM Client and the issue regarding WMI Remote access issues happens (The RPC Server is unavailable).
    I proved it by creating a new VM Machine, then conduct installation in this order
    SCCM Client first and then the
    VMware Tools by this way so far the WMI Remote access works perfectly.
    Now the Question:
    Since we have atleast 70 VM Servers in production with this issue, and I proven that the VMware Tools is something to do with this issue, somehow now I need to resolved this in a logical manner.
    For some of us who can guide me to resolved the issue without uninstalling the VMware Tools and fixing the WMI settings and let the SCCM Client work.
    Regards,

    We also have this issue. Nearly all of our terminal servers. I have to run a script to fix the issue and then reboot. It works, but only for a few days and then it starts all over again...
    ::to fix "not found" wmi error
    ::to fix .net calls to wmi repository
    ::to fix "initialization failure" error
    net stop winmgmt
    c:
    cd c:\windows\system32\wbem
    rd /S /Q repository
    regsvr32 /s %systemroot%\system32\scecli.dll
    regsvr32 /s %systemroot%\system32\userenv.dll
    mofcomp cimwin32.mof
    mofcomp cimwin32.mfl
    mofcomp rsop.mof
    mofcomp rsop.mfl
    for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
    for /f %%s in ('dir /b *.mof') do mofcomp %%s
    for /f %%s in ('dir /b *.mfl') do mofcomp %%s
    mofcomp exwmi.mof
    mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
    mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
    mofcomp exmgmt.mof
    For the Update on this case Microsoft didn't find out direct connection of WMI issue to any contributors, however the clients
    from Microsoft and and 3rd party application such as VMware is highly dependent on WMI for its total function.
    Things that we have learned:
    1. Your script is the primary solution as recommended as well by Microsoft, but this is to restore the WMI to its healthy State.
    Is the error gone?
    no definitely not.
       Note: The WMIDiagnostic tool does not help to isolate at all, not even Microsoft is validating the credibility of its generated Logs from this tool.
    2. You need to apply the Hotfixes recommended by Microsoft to eliminate the WMI repository to increase its capacity which contributes to the Service to stall. Deliver the Patches via SCCM or any means of your patch deployment.
    3. Don't forget to reboot the Affected Server every Hotfix installation, this seems fix the issue. For 3 months now the usual system who got the WMI issue most of the time is no longer encountering the WMI errors. So far this is the solution, what causes
    the issue? according to Microsoft the cause is the absence of the patches.

  • SCCM Client Application Installation WMI Classes and Cycles

    Hi,
    I am writing some software to monitor application deployements via SCCM - specifcally required applications. The applications installing OK however
    it takes a bit of time for the SCCM console to realize the application has been installed after the client has actually done it.
    So here are my questions:
    1. What client cycle actually sends the status message back to the SCCM database saying "I have installed this application" - I am guessing the
    "Application Deployment EValuation Cycle"?
    2. Which WMI class can I look at that can tell me "when" the SCCM client installed the application?
    Thanks,
    Ward

    To add to Torsten's answer here, there is no client cycle/action for this as it's automatic (see Torsten's answer). The App Deploy Eval cycle is for re-evaluating global conditions and application requirements on an on-going basis to ensure they are still
    enforced and has nothing to do with reporting back to the site.
    For part 2, CCM_Application should also get you what you are looking for on the client side but that's pretty inefficient for anything thing more than one-of deployments in small environments. Why not use reporting?
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Sccm Agent will not install via push on SCCM 2012 to computers that have sccm 2007 agents

    I can not install the sccm 2012 agent on client computers via the push method or selecting the computers in a collection and clicking on install client nothing happens on the clients. 
    Also another problem is when i install the clients manually on the machines there is no site code and i can not "find site"
    in both cases teh machines did have the sccm 2007 agent and were working fine on that.

    1.make sure you have created the boundary group first. if you cant push the agent via push method, check the log files.
    2. also make sure that in your environment if you have a firewall then there are port need to be open for agent push.
    3. also if you have installed MacAfee agent on your client machine make sure the policies are not blocking file and print sharing.
    4. also the windows firewall need to open for file and print sharing of you are using push method.
    did you try to push the agent via GPO?
    IF not try to run the following script in one of the client machine. use this command in the command prompt.
    in my case smssitecode is BLL 
    MP is the management point.
    ccmsetup.exe SMSSITECODE=BLL /mp:sccmserver.contoso.com /source:\\sccmserver.contoso.com\sms_bll\client
    run the above command in the command prompt of one of the client machine which you cant install the agent and see.

  • List of recommended hotfixes/updates for SCCM 2012 R2 agents?

    Hopefully I ask this correctly.
    Is there a list of recommended hotfixes or updates for SCCM 2012 R2 agents?  Things like .Net or WMI updates.
    I am seeing the occasional agents lose connectivity, and I want to make sure I have a complete or recommended list of non-SCCM hotfixes before I move forward.
    Thanks!
    Andy

    To my knowledge there aren't really any kind of recommended hotfixes to apply before a client installation, except for the prerequisites (that the client installs by itself). But as a best practice, always make sure that a client is up to date when it comes
    to patches.
    Regards,
    Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

  • Best practices for securing communication to internet based SCCM clients ?

    What type of SSL certs does the community think should be used to secure traffic from internet based SCCM clients ?  should 3rd party SSL certs be used ?  When doing an inventory for example of the clients configuration in order to run reports
    later how the  data be protected during transit ?

    From a technical perspective, it doesn't matter where the certs come from as there is no difference whatsoever. A cert is a cert is a cert. The certs are *not* what provide the protection, they simply enable the use of SSL to protect the data in transit
    and also provide an authentication mechanism.
    From a logistics and cost perspective though, there is a huge difference. You may not be aware, but *every* client in IBCM requires its own unique client authentication certificate. This will get very expensive very quickly and is a recurring cost because
    certs expire (most commercial cert vendors rarely offer certs valid for more than 3 years). Also, deploying certs from a 3rd party is not a trivial endeavor -- you more less run into chicken and egg issues here. With an internal Microsoft PKI, if designed
    properly, there is zero recurring cost and deployment to internal systems is trivial. There is still certainly some cost and overhead involved, but it is dwarfed by that that comes with using with a third party CA for IBCM certs.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Sharing Primary Site and Secondary Site's SUP WSUS for non-SCCM client use

    I was wondering if the WSUS deployed for the SCCM's SUP can also be (re)used for non-SCCM clients.
    Our SCCM infrastructure are mainly used to manage Workstations whereas our back-end servers are not deployed with SCCM agents due to overlapping SLAs and responsibilities. However, we would like to take advantage of WSUS's centralized update repository without
    each back-end servers initiating connection to the Internet to get their updates.
    Is this possible?

    No. WSUS servers that are used for SUPs are controlled by ConfigMgr and cannot be used outside ConfigMgr.
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM Client requirements

    How much space is required in order to install the SCCM client via SCCM 2012 Server.

    The defaults are 500Mb for the client installation and 5Gb for the client cache. There is some room for tuning, see for all the information:
    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientSysHardware
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SCCM Client Agent Deployment - Internet based client scenario

    Hi There,
    I need to deploy SCCM 2012 client agent and certificate to the machines not connected to the corporate LAN. I know that SCCM agent and certificate needs to be installed manually on them ( or via Group Policy ).... but here I'm talking about 2000 internet
    based machines.
    Can you please let me know the enterprise level best practice to capture those 2000 internet based machines.
    50% of these machines may not come on corporate network for very long time....so cannot capture them by Group Policy... How to capture those machines.... Has anyone worked on a solution to create some kind of portal etc...whose link we can provide to the
    users via email for them to just click and that installs both SCCM client agent and certificate....just a thought.
    Regards,
    Sam

    There is no best practice as that would imply that every organization is the same and should do it the same way.
    Ultimately, this challenge is unique to your organization -- not the specific ConfigMgr details, but how best to get it done within the resources and security posture of your organization.
    If your users are local admins and you have a VPN solution, then you can potentially just send them batch files to run (that install a cert and install the client agent) when they are connected via VPN. You could potentially expose both via an HTTP download
    and the CA web issuance pages also or using certutil (assuming the user has local admin permissions again). There simply are too many variables that are unique and specific to your environment to be able to describe any sort of complete solution.
    Ultimately, it comes down to two parts, neither of which is overly complicated (or magic):
    1. Request and install client auth certificate.
      - Must be done as local admin
      - Can be automated using certutil and PowerShell
    2. Install ConfigMgr client agent
      - Must be done as local admin
      - Must be initiated by running ccmsetup (with appropriate switches and properties)
      - Must have access to rest of client setup files either locally, via the Internet DP, or Internet MP
      - Must be able to communicate with MP
    I have seen folks publish scripts for this and web pages even so a little web searching may turn one of these up.
    Jason | http://blog.configmgrftw.com

  • SCCM Server 2007 Client=No

    I have a question SCCM Server 2007.
    Displayed on the screen "Client=No"
    I think so deployment security patch status.
    Please tech me for confirmation.
    I want confirmation from SCCM Server 2007.
    I am sorry for the inconvenience but I would appreciate your cooperation.
    Can you send me a reply,please.

    Need to check whether the client is successfully installed or not. This can be confirmed from client machine (ccmsetup.log) and other client logs (CCM folder). 
    Once the client is installed successfully but it's not reporting back the installation status then please refer to the following article http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspx
    Anoop C Nair (My Blog www.AnoopCNair.com)
    - Twitter @anoopmannur -
    FaceBook Forum For SCCM

Maybe you are looking for