Client Push CU4

When you use the automatic site wide push or the client push wizard is it pushing the client from the SMS_Sitecode\Client directory? This is also the package source path for the "Configuration Manager Client Package" package. Reason I ask is
if this is correct than the ccmsetup and other files in this directory would be either RTM, SP1, or R2. We have SP1 so the version it would install would be 5.0.7804.1000. When I right click on ccmsetup and look at the details tab it says the file version
is 5.0.7804.1500 which is CU4. I did install the CU4 hotfix so maybe it is reading this from the msp? What does happen is when we do the client push it installs the original SP1 version (5.0.7804.1000). Is this what is supposed to happen?

More info:
Description of Cumulative Update 4 for System Center 2012 Configuration Manager Service Pack 1
http://support.microsoft.com/kb/2922875/en-us
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • 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!

  • Client Push Not Working SCCM 2012

    I am new to SCCM and have a test rig SCCM 2012 for testing, problem is the client push fails every time and I am at a loss to explain why. I have tried removing and reading the DP, FSP and MP roles (Both these are on the SCCM core server) I have run IIS
    reset, removed all AD configured Boundaries and Groups in favor of IP range but I keep getting the same errors. Any advice here would be greatly appreciated... Below is this mornings logs highlighting the failure.
    <![LOG[==========[ ccmsetup started in process 5764 ]==========]LOG]!><time="11:31:48.304-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="7628" file="ccmsetup.cpp:9437">
    <![LOG[Running on platform X64]LOG]!><time="11:31:48.305-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="7628" file="util.cpp:1837">
    <![LOG[Updated security on object C:\Windows\ccmsetup\cache\.]LOG]!><time="11:31:48.305-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="7628" file="ccmsetup.cpp:9281">
    <![LOG[Launch from folder C:\Windows\ccmsetup\]LOG]!><time="11:31:48.306-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="7628" file="ccmsetup.cpp:721">
    <![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="11:31:48.306-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="7628" file="ccmsetup.cpp:727">
    <![LOG[In ServiceMain]LOG]!><time="11:31:48.308-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:3365">
    <![LOG[Running on 'Microsoft Windows Server 2012 Standard' (6.2.9200). Service Pack (0.0). SuiteMask = 272. Product Type = 18]LOG]!><time="11:31:48.366-120" date="01-12-2014" component="ccmsetup" context="" type="1"
    thread="6436" file="util.cpp:1919">
    <![LOG[Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="11:31:48.366-120" date="01-12-2014" component="ccmsetup" context="" type="1"
    thread="6436" file="ccmsetup.cpp:3590">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="11:31:48.366-120" date="01-12-2014" component="ccmsetup" context=""
    type="1" thread="6436" file="ccmsetup.cpp:3775">
    <![LOG[Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="11:31:48.366-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
    file="ccmsetup.cpp:3776">
    <![LOG[SslState value: 224]LOG]!><time="11:31:48.368-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:4425">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8617">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8632">
    <![LOG[CCMHTTPSSTATE:    224]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8650">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8668">
    <![LOG[FSP:    VKYV-HV01]LOG]!><time="11:31:48.369-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8720">
    <![LOG[CCMFIRSTCERT:    1]LOG]!><time="11:31:48.370-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:8778">
    <![LOG[Config file:      C:\Windows\ccmsetup\MobileClientUnicode.tcf]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
    file="ccmsetup.cpp:4539">
    <![LOG[Retry time:       10 minute(s)]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4540">
    <![LOG[MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4541">
    <![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="VSI" FSP="VKYV-HV01" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"]LOG]!><time="11:31:48.371-120"
    date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4542">
    <![LOG[Source List:]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4550">
    <![LOG[                  \\VKYV-HV01.VKYV.LAN\SMSClient]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
    file="ccmsetup.cpp:4557">
    <![LOG[                  \\VKYV-HV01.VKYV.LAN\SMSClient]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
    file="ccmsetup.cpp:4566">
    <![LOG[MPs:]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:4569">
    <![LOG[                  VKYV-HV01.VKYV.LAN]LOG]!><time="11:31:48.371-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
    file="ccmsetup.cpp:4584">
    <![LOG[No version of the client is currently detected.]LOG]!><time="11:31:48.374-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:2748">
    <![LOG[Updated security on object C:\Windows\ccmsetup\.]LOG]!><time="11:31:48.750-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:9281">
    <![LOG[Sending Fallback Status Point message to 'VKYV-HV01', STATEID='100'.]LOG]!><time="11:31:48.750-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:9756">
    <![LOG[Failed to get client version for sending messages to FSP. Error 0x8004100e]LOG]!><time="11:31:48.752-120" date="01-12-2014" component="ccmsetup" context="" type="2" thread="6436" file="ccmsetup.cpp:9838">
    <![LOG[Params to send FSP message '5.0.7958.1000 Deployment ']LOG]!><time="11:31:48.752-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:9887">
    <![LOG[State message with TopicType 800 and TopicId {037AE2A1-3C8B-482A-A180-04392D0312BA} has been sent to the FSP]LOG]!><time="11:31:49.020-120" date="01-12-2014" component="FSPStateMessage" context="" type="1"
    thread="6436" file="fsputillib.cpp:752">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="11:31:49.058-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:1995">
    <![LOG[Detected 44815 MB free disk space on system drive.]LOG]!><time="11:31:49.059-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="util.cpp:628">
    <![LOG[Checking Write Filter Status.]LOG]!><time="11:31:49.059-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:2024">
    <![LOG[This is not a supported write filter device. We are not in a write filter maintenance mode.]LOG]!><time="11:31:49.059-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436"
    file="ccmsetup.cpp:2051">
    <![LOG[Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=VSI))']LOG]!><time="11:31:49.179-120" date="01-12-2014" component="ccmsetup" context="" type="0"
    thread="6436" file="lsad.cpp:656">
    <![LOG[OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202EF308201D7A0030201020210518E5B64E54890884666F9411DA2CCB3300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133313032393130343732365A180F32313133313030363130343732365A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100B999635F3FFE2F0E7DB66B36407C0ED4FB7DC23A8CD42078325E08E7E553EC2AD1D35A5758268CA497A8023B9F056089BA068ADD84ABDDF74E00B1C402308F287387A8FFA3DBCBFDAC81F8A7F32C959B7CCDCBF5FC0D87434A2907C074675CAA4EA6963D2956EAD43957A831B746E4E5D00C66AAC1F2FE5F71D26D54909EEA0883D780EF46111B124C9C77E3F9D767D36972B9420FEFE291A2A377D958A27C1B24F72E3A870498CF44D8C854214C38F1A50C5CBB3924215F037B0256ACD78B5E32FDFD9BF9760329F523777C16234B560C808F201605774B77B54833D0EA918C44106FF72409876A6D1D4FE75EC9F3A349578577B96BAC62E39D102ACBB401230203010001A3373035301D0603551D11041630148212564B59562D485630312E564B59562E4C414E30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100B6B5CDA1A6AA6F712365113F0A81829B596081DB9AF07D5F10DEB0103F158460E9C17B3E1A201A81B9890741F7E2BF5B564058FED25FC724DD4AC948BC9462B1B6A7991AFD159C673B01CE019ABE0A0E0DDD9881AAC751427751C22A43754295DF3F4514EE1BDAD5EF06EE1010E294113B4BB00EB2DF555EE790224E40905E5183E77FF0D87D5EBD98A819DAAE265BA4CD81BA444C226B8B04EF4E80E62ECBF5F3DEDFD2F91822919DBDE529DB043FFAF424A84A0F85A8D0A45F4451F9F5DA48DCADE6603BF106128A36C20F2C52AD69A562BA7834497792D819EAD45DF18BFC6AF1AC60111AC34CF0BF48D9B037064BF41E90E910F36AEAB50C1697C18E800D</SiteSigningCert></SecurityConfiguration><RootSiteCode>VSI</RootSiteCode><CCM>
    <CommandLine>SMSSITECODE=VSI FSP=VKYV-HV01</CommandLine> </CCM><FSP> <FSPServer>VKYV-HV01.VKYV.LAN</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0"
    /></Capabilities><Domain Value="VKYV.LAN" /><Forest Value="VKYV.LAN" /></ClientOperationalSettings>']LOG]!><time="11:31:49.228-120" date="01-12-2014" component="ccmsetup" context=""
    type="0" thread="6436" file="lsadcache.cpp:236">
    <![LOG[Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.]LOG]!><time="11:31:49.229-120" date="01-12-2014" component="ccmsetup" context="" type="1"
    thread="6436" file="ccmutillib.cpp:373">
    <![LOG[The MP name retrieved is 'VKYV-HV01.VKYV.LAN' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>']LOG]!><time="11:31:49.229-120"
    date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="lsadcache.cpp:334">
    <![LOG[MP 'VKYV-HV01.VKYV.LAN' is compatible]LOG]!><time="11:31:49.229-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="lsadcache.cpp:339">
    <![LOG[Retrieved 1 MP records from AD for site 'VSI']LOG]!><time="11:31:49.229-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="lsadcache.cpp:287">
    <![LOG[Retrived site version '5.00.7958.1000' from AD for site 'VSI']LOG]!><time="11:31:49.231-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="siteinfo.cpp:575">
    <![LOG[SiteCode:         VSI]LOG]!><time="11:31:49.231-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:2076">
    <![LOG[SiteVersion:      5.00.7958.1000]LOG]!><time="11:31:49.231-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:2077">
    <![LOG[Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.]LOG]!><time="11:31:49.231-120" date="01-12-2014" component="ccmsetup" context="" type="1"
    thread="6436" file="ccmsetup.cpp:2111">
    <![LOG[Only one MP VKYV-HV01.VKYV.LAN is specified. Use it.]LOG]!><time="11:31:49.232-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:10080">
    <![LOG[Searching for DP locations from MP(s)...]LOG]!><time="11:31:49.232-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:11018">
    <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="11:31:49.232-120" date="01-12-2014" component="LocationServices" context="" type="1" thread="6436" file="lsad.cpp:770">
    <![LOG[Local Machine is joined to an AD domain]LOG]!><time="11:31:49.232-120" date="01-12-2014" component="LocationServices" context="" type="0" thread="6436" file="lsad.cpp:714">
    <![LOG[Current AD forest name is VKYV.LAN, domain name is VKYV.LAN]LOG]!><time="11:31:49.235-120" date="01-12-2014" component="LocationServices" context="" type="1" thread="6436" file="lsad.cpp:842">
    <![LOG[DhcpGetOriginalSubnetMask entry point is supported.]LOG]!><time="11:31:49.237-120" date="01-12-2014" component="LocationServices" context="" type="0" thread="6436" file="ccmiputil.cpp:117">
    <![LOG[Begin checking Alternate Network Configuration]LOG]!><time="11:31:49.237-120" date="01-12-2014" component="LocationServices" context="" type="0" thread="6436" file="ccmiputil.cpp:1095">
    <![LOG[Finished checking Alternate Network Configuration]LOG]!><time="11:31:49.239-120" date="01-12-2014" component="LocationServices" context="" type="0" thread="6436" file="ccmiputil.cpp:1172">
    <![LOG[Sending message body '<ContentLocationRequest SchemaVersion="1.00">
      <AssignedSite SiteCode="VSI"/>
      <ClientPackage/>
      <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0"
    UseInternetDP="0">
        <ADSite Name="Default-First-Site-Name"/>
        <Forest Name="VKYV.LAN"/>
        <Domain Name="VKYV.LAN"/>
        <IPAddresses>
    <IPAddress SubnetAddress="10.6.2.0" Address="10.6.2.2"/>
        </IPAddresses>
      </ClientLocationInfo>
    </ContentLocationRequest>
    ']LOG]!><time="11:31:49.256-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="siteinfo.cpp:96">
    <![LOG[Sending message header '<Msg SchemaVersion="1.1"><ID>{CC48E819-7755-4650-83AC-8BC823C06C8C}</ID><SourceHost>VKYV-HV01</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:VKYV-HV01:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>VKYV-HV01.VKYV.LAN</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-01-12T09:31:49Z</SentTime><Body
    Type="ByteRange" Offset="0" Length="1096"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>']LOG]!><time="11:31:49.256-120" date="01-12-2014"
    component="ccmsetup" context="" type="0" thread="6436" file="siteinfo.cpp:177">
    <![LOG[CCM_POST 'HTTP://VKYV-HV01.VKYV.LAN/ccm_system/request']LOG]!><time="11:31:49.257-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="httphelper.cpp:807">
    <![LOG[Failed to receive ccm message response. Status code = 403]LOG]!><time="11:31:49.434-120" date="01-12-2014" component="ccmsetup" context="" type="2" thread="6436" file="httphelper.cpp:1694">
    <![LOG[GetDPLocations failed with error 0x80004005]LOG]!><time="11:31:49.435-120" date="01-12-2014" component="ccmsetup" context="" type="3" thread="6436" file="siteinfo.cpp:532">
    <![LOG[Failed to get DP locations as the expected version from MP 'VKYV-HV01.VKYV.LAN'. Error 0x80004005]LOG]!><time="11:31:49.435-120" date="01-12-2014" component="ccmsetup" context="" type="2" thread="6436"
    file="ccmsetup.cpp:11261">
    <![LOG[Sending Fallback Status Point message to 'VKYV-HV01', STATEID='101'.]LOG]!><time="11:31:49.435-120" date="01-12-2014" component="ccmsetup" context="" type="1" thread="6436" file="ccmsetup.cpp:9756">
    <![LOG[Failed to get client version for sending messages to FSP. Error 0x8004100e]LOG]!><time="11:31:49.437-120" date="01-12-2014" component="ccmsetup" context="" type="2" thread="6436" file="ccmsetup.cpp:9838">
    <![LOG[Params to send FSP message '5.0.7958.1000 Deployment ']LOG]!><time="11:31:49.437-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:9887">
    <![LOG[State message with TopicType 800 and TopicId {1D445639-95B1-4EC5-A65F-FC7A721F8061} has been sent to the FSP]LOG]!><time="11:31:49.455-120" date="01-12-2014" component="FSPStateMessage" context="" type="1"
    thread="6436" file="fsputillib.cpp:752">
    <![LOG[Next retry in 10 minute(s)...]LOG]!><time="11:31:49.455-120" date="01-12-2014" component="ccmsetup" context="" type="0" thread="6436" file="ccmsetup.cpp:8835">

    Does you MP/DP use HTTP or HTTPS? I recommend to start with HTTP and when you have successfully installed a few clients, you can switch to HTTPS if desired. HTTPS based communication requires more steps e.g. client certificates.
    Have you extended AD schema and do you see objects in \System\System Management container in AD?
    Also, you might have DNS name resolution problem or the firewall is blocking the traffic from the client to MP.
    The client is having troubles to successfully talk with MP:
    Failed to get DP locations as the expected version from MP 'VKYV-HV01.VKYV.LAN'. Error 0x80004005
    Panu

  • SCCM Client push or manual installation does not complete

    Hi All,
    I have deployed SCCM 2012 R2 in my lab environment. It has been deployed successfully. I have a issue in which the clients are not getting installed both manually and by pushing the agents via the console. 
    My servers are as follows:
    SCCMSVR.labtest.com  - Is the SCCM server and Fail back status point.
    Server.labtest.com - Is the Domain controller, SQL server
    SCCMTEST.labtest.com - A testing machine to push the client and to deploy patches in it.
    Site code is LAB
    I ran the setup using the following command.
    I have shared the ccmsetup in a share so the command is as follows:
    \\sccmsvr\Client\ccmsetup.exe /MP:SCCMSVR /Logon SMSSITECODE=LAB FSP=SCCMSVR
    But when i check the task manager the process of ccmsetup.exe but it does not change to CCMEXEC.exe
    I waited for an hour but still the same issue. (This was done in the DC Server.labtest.com)
    Screen shot of the DC  Machine:
    When i do a client push installation in a testing machine (SCCMTEST.labtest.com)  i still the same issue. I pushed the client still the same issue
    In the task manager the process of ccmsetup.exe but it does not change to CCMEXEC.exe.
    Screen shot of the second machine:
    Also checked the control panel. Dint find the config manager options there on both machines.
    Also turned off firewall on all 3 machines  but still the same issue.
    Analysed the event logs on all the servers. The client machines did not have any relevant events.
    The SCCM server had this event. Not sure if this is causing the issue.
    Event id 2344
    On 9/28/2014 3:26:48 PM, component SMS_DISTRIBUTION_MANAGER on computer SCCMSVR.LABTEST.COM reported:  Failed to create virtual directory on the defined share or volume on distribution point "["Display=\\SCCMSVR.LABTEST.COM\"]MSWNET:["SMS_SITE=LAB"]\\SCCMSVR.LABTEST.COM\".
    Possible cause: Distribution Manager requires that IIS base components be installed on the local Configuration Manager Site Server in order to create the virtual directory.  Distribution Manager also requires that IIS Web Services be installed on the Distribution
    Point Server that needs to support Background Intelligent Transfer Service (BITS).
    Solution: Verify that IIS base components are installed on the local Configuration Manager Site Server, and IIS Web Services are installed on the Distribution Point Server.
    Can any one please help.
    Gautam.75801

    Hi Kashif,
    Thank you for your valuable help. As you mentioned the IIS 6 WMI compatibility Feature was not installed. Once i installed and rebooted the SCCM server and pushed
     both the agents manually and by Pushing it via console and it succeed. How ever i got some errors on both the systems The trace log tool during the installation but it succeed.
    What i would like to know is that is it common to get errors like the below while pushing a agent automatically or manually ?
    1. MSI: Action 1:25:44: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents.
    (Got this multiple times)
    2. MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent.
    3. Failed to load mdmregistration.dll. Continue deployment.
    4. Failed to load mdmregistration.dll with error 0x8007007e
    5. File 'C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed.
    6. File 'C:\Windows\system32\msrdc.dll' does not exist. Discovery failed.
    7. Enumerated all 1 local DP locations but none of them is good. Fallback to MP.
    8. Failed to check url http://SCCMSVR.LABTEST.COM/SMS_DP_SMSPKG$/LAB00002. Error 0x80004005
    9. Failed to correctly receive a WEBDAV HTTP request.. (StatusCode at WinHttpQueryHeaders: 401)
    10. As per the screen shot.
    Gautam.75801

  • SCCM Client Push Installation Wizard does not install the client. CCMSetup folder - not created

    Hello,
    I have tried running the Client Push wizard for a single computer or a pilot collection of 8 computers, the result is always
    the same - no SCCM client is installed on any computer.
    The computers are running 32-bit Windows XP SP2.
    The Windows firewall is disabled.
    The client push installation account is setup and have domain admin and local admin privileges. Client Push automatic method
    is not enabled.
    The domain is AD WIndows 2000.
    The SCCM server is running Windows 2003 R2 SP2 64bit Standard.
    The AD schema has been extended.
    MP, and SLP are installed and published. (MP is published in DNS as well.)
    FSP is installed.
    MP, SLP and FSP are running on the same server.
    SQL 2005 server is running locally.
    System management container is created and all rights and permissions delegated.
    With the Push installation account I can access C$ share on the client computer from the SCCM server.
    RPC, Remote registry, WMI services are running on the client machines.
    All prerequisites are installed from the client folder on SCCM server- latest BITS 2.5, Windows installer 3.1 and MSXML6.
    All computers are in the same IP subnet which is listed in the boundaries.
    Yet, the client is not being installed.
    No CCMSetup folder is created on the client machines in Windows\System32 folder, so it is really difficult to troubleshoot
    what the is the issue. I do not see anything helpful in the ccm.log on the server.
    I have tried running the CCMSetup.exe manually on one of the workstations and that was successful and reported back to the
    SCCM server / console.
    What else I should check / try? I really want to push agents via the wizard.
    Thank you,
    Peter

    Hi Wally,
    I have changed 2 things:
    1. Enabed automatic push installation (so I am not usign the wizard any more)
    2. Changed the IP subnet to IP ranges in the site boundairies.
    After runnignt the discovery, I was able to see some activities in the ccm.log. A ccmsetup folder is now created but the agent is still not instaleld. Here is the ccmsetup.log
    ==================================
    <![LOG[==========[ ccmsetup started in process 3140 ]==========]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:8853">
    <![LOG[Version: 4.0.5931.0000]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:1913">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3937">
    <![LOG[Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3946">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7851">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7866">
    <![LOG[CCMHTTPSSTATE:    0]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7884">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7912">
    <![LOG[FSP:    HFXDBSSOM.CORP.EASTLINK.CA]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7927">
    <![LOG[CCMFIRSTCERT:    0]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7969">
    <![LOG[Config file:      C:\WINDOWS\system32\ccmsetup\MobileClient.tcf]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4341">
    <![LOG[Retry time:       10 minute(s)]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4342">
    <![LOG[MSI log file:     ]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4343">
    <![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="PHX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="HFXDBSSOM.CORP.EASTLINK.CA" CCMFIRSTCERT="0"]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4344">
    <![LOG[Source List:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4352">
    <![LOG[                  \\HFXDBSSOM.corp.eastlink.ca\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4359">
    <![LOG[                  \\HFXDBSSOM\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4368">
    <![LOG[MPs:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4371">
    <![LOG[                  HFXDBSSOM.corp.eastlink.ca]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4386">
    <![LOG[Updated security on object C:\WINDOWS\system32\ccmsetup\.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="0" thread="3108" file="ccmsetup.cpp:8692">
    <![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:9169">
    <![LOG[State message with TopicType 800 and TopicId {A450B407-619B-4777-B77E-C3352753B58A} has been sent to the FSP]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="3108" file="fsputillib.cpp:730">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:2534">
    <![LOG[Detected 24292 MB free disk space on system drive.]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:465">
    <![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:511">
    <![LOG[Client OS is not Windows XP Embedded]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:548">
    <![LOG[Successfully ran BITS check.]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:6948">
    <![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="3" thread="2600" file="ccmsetup.cpp:5813">
    <![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="09:45:08.760+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:9169">
    <![LOG[State message with TopicType 800 and TopicId {3BFABF82-FB74-43FB-8A4A-6DFDEAEAC25C} has been sent to the FSP]LOG]!><time="09:45:08.776+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="2600" file="fsputillib.cpp:730">
    ==============================================================
    There are two red errors I am concerned about:
    "Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)
    and
    "Failed to download 'WindwosXP-KB923845-x86-ENU.exe' from http://HFXDBSSOM.corp.eastlink.ca/CCM_Client/i386/BITS25 with error code 0x80004005).
    What should I do to resolve these errors?
    Thanks,
    Peter

  • Best practise for installing patches for SCCM Client 2012 (Both x86 and x64)) - OSD and Client Push Installation

    Hi All,
    What is best practice for automatic installing of SCCM 2012 client Patches
    (using Patch switch) during installation of SCCM 2012 clients? The challenge is that now there are two versions of clients and updates (x86 and x64).
    I need information for:
    OSD
    Client Push Installation
    Thank you in advance.
    Regards,

    Not everything that can be or is supported or not supported is documented (or ever can be):
    http://technet.microsoft.com/en-us/magazine/jj643252.aspx
    Your expectation here needs to be adjusted. No one recommended contacting support. William just mentioned that *if* you have an issue and needed to contact support, they may decline to help you because you've done something explicitly unsupported.
    For clientpatch, here's the specific documentation noting it as unsupported:
    http://blogs.technet.com/b/configmgrteam/archive/2009/04/08/automatically-applying-hotfixes-to-the-configuration-manager-2007-client-during-installation.aspx
    Additionally, I've also been in contact with the sustained engineering folks responsible for the CUs and they've reinforced the statement.
    What can happen? Who knows? Microsoft does not test against unsupported configurations and features -- that's the definition of unsupported. It's not tested so no one really knows. They did find a couple of explicit issues (outlined in that post above) so
    know that at least those exist and probably more since it is, as mentioned, abandoned code.
    Why does it matter what can happen though? If the folks who write and support the code tell you shouldn't do it, you are simply asking for problems by doing it. Ultimately, you're asking a question that has no defined answer (except "bad"/unsupported things)
    that really doesn't matter if you follow the explicit guidance. If you don't, as William points out, that's a risk for you take and an answer for you to discover.
    Jason | http://blog.configmgrftw.com

  • Client push in foreign forests without AD integration

    I am working through a scenario where an SCCM installation is not making use of AD integration and there will be clients in several foreign, untrusted forests. I am looking at how to use the Client Push function to install the client on endpoints. As I will
    have MP+DP site systems living in these foreign forests, I need to find a way to tell the client (during install) to use its local MP.
    Looking at the Client Push Installation Properties dialog I see that I can configure installation properties such as "SMSMP". Granted, this is a global setting and not one I would apply to every endpoint I want to push the client to. I noticed
    the actual Client Push Wizard only allows me to select a Site during the installation. So there is no way for me to configure the MP for a client during a manual push.
    Knowing this, and that clients will use the MP residing in their forest by default, I am a little confused on how MP specification goes down during a Client Push in this scenario. Can someone help me wrap my head around this?

    Clients will always prefer to use the MP in their own forest/domain and DP is entirely dependent upon your boundaries and their membership in boundary groups. The SMSP property simply defines an initial bootstrap MP that will be queried by the client initially
    to find other, possibly better MPs. In this way, the client will find the MP in its own forest. In you scenario, it will initially be unavoidable for the client to not use some central MP if you use the SMSMP property and client push.
    Have you considered using a client start up script instead of client push?
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • WebDAV error when doing a client push ConfigMgr 2012 R2

    Hi everyone, I am getting an error message when doing a client push, only on some DPs.
    Here is the setup:
    ConfigMgr 2012 R2 on Server 2012 R2.
    DP are on Server 2008 R2 (for the most part).
    DP are installed using the exact same way, adding the Primary Site Server to the local Admins group, then using the console to install the role, selecting BranchCache and Configure IIS.
    No PXE.
    Boundary groups are configured as appropriate.
    When initiating a client push the following errors are displayed in the CCMSetup.log:
    Failed to correctly receive a WEBDAV HTTP request.. (StatusCode at WinHttpQueryHeaders: 401)
    Failed to check url http://DPServerName.com/SMS_DP_SMSPKG$/S0100003. Error 0x80004005
    Enumerated all 1 local DP locations but none of them is good. Fallback to MP.
    GET 'HTTP://MPServerName.com/CCM_Client/ccmsetup.cab'
    The installation is done but yet again, no local DP are used.
    The same scenario is actually working on other DP that was configured using the same exact way.
    Servers where not new installation and where used for other things:
    MDT Deployment Share with PXE.
    Other share.
    As far as I can tell, IIS is well configured as I am able to deploy any other software on clients and they are using the local DP. Only the client installation is causing problem.
    Anyone have any idea?
    There is a lot of post about a similar problem on ConfigMgr 2007 but all solution are to configure WebDAV, which is not configured in ConfigMgr 2012.
    Thank you guys for any tip and/or help!
    Mathieu

    You are right about the log, here is a longer snippet of it:
    ==========[ ccmsetup started in process 5980 ]========== ccmsetup 2015-03-25 23:12:12 1020 (0x03FC)
    Running on platform X86 ccmsetup 2015-03-25 23:12:12 1020 (0x03FC)
    Launch from folder C:\Windows\ccmsetup\ ccmsetup 2015-03-25 23:12:12 1020 (0x03FC)
    CcmSetup version: 5.0.7958.1501 ccmsetup 2015-03-25 23:12:12 1020 (0x03FC)
    In ServiceMain ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Running on 'Microsoft Windows 7 Professionnel ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    SslState value: 224 ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    CCMHTTPPORT: 80 ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    CCMHTTPSPORT: 443 ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    CCMHTTPSSTATE: 224 ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    CCMHTTPSCERTNAME: ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    FSP: ServerSCCMPSS.Test.com ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    CCMFIRSTCERT: 1 ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Config file: C:\Windows\ccmsetup\MobileClientUnicode.tcf ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Retry time: 10 minute(s) ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    MSI properties: INSTALL="ALL" SMSSITECODE="S01" FSP="ServerSCCMPSS.Test.com" SMSCACHEFLAGS="PERCENTFREEDISKSPACE" SMSCACHESIZE="20" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Source List: ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    \\Serversccmmp.Test.com\SMSClient ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    \\Serversccmpss.Test.com\SMSClient ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    \\dcsspsccmmpdff.test.com\SMSClient ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    \\ServerSCCMMP.Test.com\SMSClient ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    \\ServerSCCMPSS.Test.com\SMSClient ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    \\DCSSPSCCMMPDFF.test.com\SMSClient ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    MPs: ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Serversccmmp.Test.com ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Serversccmpss.Test.com ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    dcsspsccmmpdff.test.com ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    No version of the client is currently detected. ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Updated security on object C:\Windows\ccmsetup\. ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Sending Fallback Status Point message to 'ServerSCCMPSS.Test.com', STATEID='100'. ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Params to send FSP message '5.0.7958.1501 Deployment ' ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    State message with TopicType 800 and TopicId {40FD8A62-3E9A-41FB-8698-E9A6658A4A91} has been sent to the FSP FSPStateMessage 2015-03-25 23:12:12 4536 (0x11B8)
    Running as user "Système" ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Detected 206206 MB free disk space on system drive. ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Checking Write Filter Status. ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 2015-03-25 23:12:12 4536 (0x11B8)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=S01))' ccmsetup 2015-03-25 23:12:13 4536 (0x11B8)
    OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F5308201DDA00302010202103FC715B41292C689495889DC28401ED8300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3134313231383136353532335A180F32313134313132353136353532335A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100A78659B1C2B8160DD0CF4E10AE142E067F8D9ABD23F931443DD15ED20479E0BF70A8C2322DE863FD41B5429DB5D3CB0AA71D189C8C61E4155A59CD16DC961B75302AF7B75DF31A19E8AB6E163B622A80A5B24FD6B37B54379B74911D6B9771B3120CF72ECFAA36747861896FA99FAF79AF528E8BC2860D3F022C761363C69BBD0969E75AD83ECB60BB06F503195AC2DAAF90FA874A1F45C32111A4B55F638573942C4EAE597A8E02024E8AFFFFDEE746160D45A41615EF97A15500AE99305CE6E980CB0E0F139EAC6D368D72AEE1104C9BAB2CEA4CCAB4490F44B33047A512C4F1EB0DBF38BE66ED0DC875D09DB4C06DA44ED011556D4DEA070D45E0C80502C10203010001A33D303B30230603551D11041C301A821864637073707363636D7073732E6167726F7075722E636F6D30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B050003820101002A2B4C225ACB02DB1389B315F12FAE33B6B0B3FD232243FAC81DDD624722908BDBF7B6CAE87351320DE47BF13A01F93A4C8C62CABB273ED5C696F42926A323E61C9477E7FD71DB693AAB3BC80CBBC0FED501292F702B7223D9AAC334631EE5AA6048028D7C26BAC2A9DB997C73E9B473CDAFDF55834C6DD5C88D5FBED4096EE739EE8C5B9238B8A4C9352C7DF9A98D0011BD8D5FE4B881F5B6B68004355147A2C264C62F1BC99B3B0D26787185863EAC426860411FF329129D270A7D38B1733A12F1EEDE246F5F24D3492A7A53B380576CE20B5F77952EC2F93240784C6ECE8D25B80494129EF3EDC7150EA9BDFA0F80E7E5E7F53673FAD6A922EA7ADE2092D3</SiteSigningCert></SecurityConfiguration><RootSiteCode>S01</RootSiteCode><CCM> <CommandLine>SMSSITECODE=S01 FSP=Serversccmpss.Test.com SMSCACHEFLAGS=PERCENTFREEDISKSPACE SMSCACHESIZE=20</CommandLine> </CCM><FSP> <FSPServer>Serversccmpss.Test.com</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="Test.com" /><Forest Value="Test.com" /></ClientOperationalSettings>' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    The MP name retrieved is 'Serversccmpss.Test.com' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    MP 'Serversccmpss.Test.com' is compatible ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    The MP name retrieved is 'Serversccmmp.Test.com' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    MP 'Serversccmmp.Test.com' is compatible ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    The MP name retrieved is 'dcsspsccmmpdff.test.com' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    MP 'dcsspsccmmpdff.test.com' is compatible ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Retrieved 3 MP records from AD for site 'S01' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Retrived site version '5.00.7958.1000' from AD for site 'S01' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    SiteCode: S01 ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    SiteVersion: 5.00.7958.1000 ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Searching for a valid online MP... ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Checking the URL 'HTTP://Serversccmpss.Test.com:80/CCM_Client/ccmsetup.cab' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    PROPFIND 'HTTP://Serversccmpss.Test.com:80/CCM_Client' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Found a valid online MP 'Serversccmpss.Test.com'. ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Searching for DP locations from MP(s)... ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Current AD site of machine is CDL LocationServices 2015-03-25 23:12:14 4536 (0x11B8)
    Local Machine is joined to an AD domain LocationServices 2015-03-25 23:12:14 4536 (0x11B8)
    Current AD forest name is Test.com, domain name is Test.com LocationServices 2015-03-25 23:12:14 4536 (0x11B8)
    DhcpGetOriginalSubnetMask entry point is supported. LocationServices 2015-03-25 23:12:14 4536 (0x11B8)
    Begin checking Alternate Network Configuration LocationServices 2015-03-25 23:12:14 4536 (0x11B8)
    Finished checking Alternate Network Configuration LocationServices 2015-03-25 23:12:14 4536 (0x11B8)
    Adapter {72FC011A-9993-4CBD-B7B2-D1D56FD38711} is DHCP enabled. Checking quarantine status. LocationServices 2015-03-25 23:12:14 4536 (0x11B8)
    Sending message body '<ContentLocationRequest SchemaVersion="1.00">
    <AssignedSite SiteCode="S01"/>
    <ClientPackage/>
    <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0">
    <ADSite Name="CDL"/>
    <Forest Name="Test.com"/>
    <Domain Name="Test.com"/>
    <IPAddresses>
    <IPAddress SubnetAddress="172.16.64.0" Address="172.16.65.9"/>
    </IPAddresses>
    </ClientLocationInfo>
    </ContentLocationRequest>
    ' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Sending message header '<Msg SchemaVersion="1.1"><ID>{B9F091E1-649D-47C4-A0AD-19508435F962}</ID><SourceHost>C006235</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:C006235:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>Serversccmpss.Test.com</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-03-26T03:12:14Z</SentTime><Body Type="ByteRange" Offset="0" Length="1080"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    CCM_POST 'HTTP://Serversccmpss.Test.com/ccm_system/request' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Content boundary is '--aAbBcCdDv1234567890VxXyYzZ' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Received header '<Msg SchemaVersion="1.1">
    <ID>{336667CB-2AF5-4B7D-9B1B-3B9A39777034}</ID>
    <SourceID>GUID:8BB44537-8D62-4751-9114-1F5527EE800F</SourceID>
    <SourceHost>ServerSCCMPSS</SourceHost>
    <TargetAddress>direct:C006235:LS_ReplyLocations</TargetAddress>
    <ReplyTo>MP_LocationManager</ReplyTo>
    <CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
    <Priority>3</Priority>
    <Timeout>600</Timeout>
    <ReplyCapabilities><AllowRegistrationReset>direct:ServerSCCMPSS:ClientRegistration</AllowRegistrationReset></ReplyCapabilities><TargetHost>C006235</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-03-26T03:12:14Z</SentTime><Body Type="ByteRange" Offset="0" Length="2574"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019406092A864886F70D010702A082018530820181020101310B300906052B0E03021A0500300B06092A864886F70D010701318201603082015C02010130393025311530130603550403130C44435053505343434D505353310C300A06035504031303534D5302104369DD60F91848B94FFD72538BAD96B8300906052B0E03021A0500300D06092A864886F70D010101050004820100B563F71CC4F86BEA28550E4EC51727E4F45F9681BABD9A085EAF4B3CC667B7BF7D212329195A13DF562A46205E22EDA829D0B06EA3C9C0C96248AD58DEECA457241EB4F4CBE581D49C0D657B3485444E06A9ED67D9854B551AADED7E1E3E519CC7D25B473A98BAC3826BE8BDB68BC4799C652168351C6796AE84505B5B703B3AABA3AD71113B133C1410EEB4CA167010AAA4AF2D3BE209E037641CA0293271242FF254C16F8A0997B5A335FB00EDCE445B2CFB21AF5923B14D9BEE3FA940B4B513D230607678ABD6A6211E36418EC2D8CFCEF5370999E6678CD79099B2D9FE29E8F3E1C5FFEA31E2D17C977288E03027D887B1D09E9049EE2FA5B76C32214BD9</Property><Property Name="AuthSenderMachine">ServerSCCMPSS;Serversccmpss.Test.com;</Property><Property Name="MPSiteCode">S01</Property></Hook></Hooks><Payload Type="inline"/></Msg>' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="S01" MasterSiteCode="S01" SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://CDLGHOST.Test.com/SMS_DP_SMSPKG$/S0100003" Signature="http://CDLGHOST.Test.com/SMS_DP_SMSSIG$/S0100003"/><ADSite Name="CDL"/><IPSubnets><IPSubnet Address="172.16.64.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>CDLGHOST.Test.com</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site><Site><MPSite SiteCode="S01" MasterSiteCode="S01" SiteLocality="LOCAL"/><LocationRecords/></Site></Sites><ClientPackage FullPackageID="S0100003" FullPackageVersion="7" FullPackageHash="CE8C259380667F5687A01FA5365B2D2D1236BA9FC1AD4696A54D914B919D294D" MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="7" ProgramEnabled="false" LastModifiedTime="30416572;2153570688" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Found local location 'http://CDLGHOST.Test.com/SMS_DP_SMSPKG$/S0100003' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Discovered 1 local DP locations. ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    PROPFIND 'http://CDLGHOST.Test.com/SMS_DP_SMSPKG$/S0100003' ccmsetup 2015-03-25 23:12:14 4536 (0x11B8)
    Got 401 challenge Retrying with Windows Auth... ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    PROPFIND 'http://CDLGHOST.Test.com/SMS_DP_SMSPKG$/S0100003' ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Failed to correctly receive a WEBDAV HTTP request.. (StatusCode at WinHttpQueryHeaders: 401) ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Failed to check url http://CDLGHOST.Test.com/SMS_DP_SMSPKG$/S0100003. Error 0x80004005 ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Enumerated all 1 local DP locations but none of them is good. Fallback to MP. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    GET 'HTTP://Serversccmpss.Test.com/CCM_Client/ccmsetup.cab' ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Successfully loaded ccmsetup manifest file. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Checking if manifest version '5.00.7958.1000' is newer than the ccmsetup version '5.0.7958.1501' ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Running from temp downloaded folder or manifest is not newer than ccmsetup. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Item 'i386/vcredist_x86.exe' is applicable. Add to the list. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Item 'x64/vcredist_x64.exe' is not applicable. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Item 'i386/vc50727_x86.exe' is applicable. Add to the list. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Item 'x64/vc50727_x64.exe' is not applicable. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Item 'i386/WindowsUpdateAgent30-x86.exe' is applicable. Add to the list. ccmsetup 2015-03-25 23:12:15 4536 (0x11B8)
    Item
    I did double checked with a friend about my configuration and everything, just to make sure, and everything seems to be right.
    As for the use of account used to get the client, a domain join computer will not need to us the network access account if the DP is in the same domain and the same exact config on other servers is working like a charm deploying the client, same
    security and configuration.
    All default IIS security and share permission.
    Thank you guys for your suggestion and help. 
    Mat

  • Client Push on Windows 7 x86 with IE9 open.

    I everyone, I need to validate something.
    I am currently deploying SCCM 2012 R2 for a client of mine.
    They are using mainly Windows 7 with SP1 x86 with IE9 installed.
    When doing  client push from the console or installing any SCCM agent update, we are getting an error message stating the IE just crashed and the error is talking about IEFrame.dl:
    Doing the same thing on a Windows 7 with SP1 x64 is not getting an error message.
    Anyone can reproduce the error on is side? Or anyone know a workaround for this issue?
    We are talking about SCCM 2012 R2 CU3 doing a client push on a Windows 7 with SP1.
    There is no update done on Windows (I was using the default install.wim at first then applied all updates) and IE9 is installed (installation file downloaded at
    http://techdows.com/2011/03/download-ie9-final-offlinestandalone-installer.html).
    I will try the same thing with a all the updates installed on Windows 7 x86.
    Thank you for your help.
    Mathieu

    After some troubleshooting and a bit of luck, the problem is the following:
    The December update KB3008923 (Cumulative Update for IE December 2014) was causing the problem on IE9.
    The update released on January 2015 KB3025945 is fixing the issue.
    This is not an update available through WSUS so you have to look for it at
    http://catalog.update.microsoft.com.
    There is a bit more information, the problem is recurring but I did not found which task was causing the error so it was not only the installation that was causing the problem. After installing the KB3008923, the problem was present on any x86 Windows 7
    computer running any version of configMgr agent (tested on 2012 SP1 and 2012 R2).
    After installing the January update, the problem is gone.
    Mathieu

  • Enable Automatic site-wide client push installation

    Hi,
    We are configuring sccm 2012 next to sccm 2007. We want to push SCCM 2007 clients automatically to pc's in a certain OU. Can this be done via "Enable Automatic site-wide client push installation".
    So will it deploy to only the discovered devices in this OU we configured to discover or really install site wide (probably not but need to be sure)?
    J.
    Jan Hoedt

    Automatic client push will initiate a push to all devices that are discovered (where client = 0) and that are assigned to the site (-> boundaries).
    Torsten Meringer | http://www.mssccmfaq.de

  • Client push deployment and CU / hotfix install

    I'm trying to figure out a way to do a push install of the 2012 client, CU update, and hotfixes all in one go.  I know using the ClientPatch folder method is not supported, but I'm wondering if another way would work.
    1) When you do a client push install from the console, does it use BITS?
    2) Does it directly use the files in Program Files\Microsoft Configuration Manager\Client on the site server, or the SCCM client package?
    3) Could you create a Hotfixes folder under the Client folder, put the CU / hotfixes in there, then use the PATCHES property to point to C:\Windows\ccmsetup\hotfixes\%PROCESSOR_ARCHITECHTURE%\hotfixname.msp?
    I know you can use SCUP or packages to do the updates, but it would be much easier to do it all at once.  Hence the reason why so many people still use the ClientPatch folder, I guess.  I really wish they'd make that a supported option.

    1. No, the initial push portion is a straight SMB copy to the target client. However, that only copies a bootstrapper, ccmsetup, which in turn kicks off on the client to download the rest of the necessary files. The download by ccmsetup does use BITS though.
    2. ccmsetup downloads the necessary files from the package on the proper distribution point (although it will fallback to the MP where it would be ultimately pulling from the client folder location.
    3. Yes, you could create the folder but that would not cause it to be copied to target client. The files it downloads are a fixed list.
    The most you could do is add it to the client push properties but that is problematic because the patches are architecture specific. Thus, there really is no good way to do this using client push.
    A client startup script however offers many advantages including being able to do this.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCCM Client Push Installtion

    Hello I am trying to test SCCM client push installation. I used active directory system group discovery as discovery method. All clients(windows 2008 r2) that were on the same subnet reported fine on collection and installed client through client push
    installation. However two clients that are on two different subnets are not reporting nor clients are install through push installation. I have boundaries setup correctly for these two non reporting client. I have all components of SCCM running on same server.
    What firewall ports are needed for active directory system group discovery and client push installation. Between SCCM and SCCM Client ?ad

    In order to successfully use client push to install the Configuration Manager client, you must add the following as exceptions to the Windows Firewall:
    File and Printer Sharing
    Windows Management Instrumentation (WMI)
    TCP Port 135
    TCP Port 445
    Hossam Wael Elmosallamy (IT Support Engineer-ECC Solutions) MCSE - CCNA [email protected] Mobile:(011)-49464671 www.eccsolutions.net "Experience Reliability&quot

  • HTTP 403.13 during SCCM client push

    We have multiple forest connected to a shared SCCM 2012 R2 site.
    The site is in SSL only mode
    With one forest we have problems pushing clients from SCCM.
    Install works fine but soon as the client connects to the MP we get HTTP 403.13 failures.
    RootCA certs have been added to SCCM
    RootCA certs of the remote forest are added both sided to trusted root CA
    CRL can be checked both sides using IE.
    Still IIS logs on the MP show
    2014-08-07 08:14:57 managementpointip CCM_POST /ccm_system_windowsauth/request - 443 - hostip ccmhttp - 403 13 2148081683 34
    ccm messaging logs show
    Post to https://MPFQDN/ccm_system_windowsauth/request failed with 0x87d00231
    The following registry keys have been set to
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL
    ClientauthTrustmode REG_DWORD 2
    sendtrustedissuerlist REG_DWORD 0
    The strange thing is that one forest works and one not. Both are identical configured.
    Firewall ports are open.

    Hi Torsten,
    I have seen that article and yes it is CRL related. The thing is the MP is configured not to check the CRL.
    Now the client push seems to ignore that value. A local install can be configured with /nocrlcheck
    Still it worries me that the CRL can be accessed by the MP using a browser on the MP.
    SSL Certificate bindings:
        IP:port                      : 0.0.0.0:443
        Certificate Hash             : 0317e07bab17b3f16502c1623778c1abeadbfd19
        Application ID               : {4dc3e181-e14b-4a21-b022-59fc669b0914}
        Certificate Store Name       : My
        Verify Client Certificate Revocation : Disabled
        Verify Revocation Using Cached Client Certificate Only : Disabled
        Usage Check                  : Enabled
        Revocation Freshness Time    : 0
        URL Retrieval Timeout        : 0
        Ctl Identifier               : (null)
        Ctl Store Name               : (null)
        DS Mapper Usage              : Disabled
        Negotiate Client Certificate : Disabled
        IP:port                      : 0.0.0.0:8531
        Certificate Hash             : 0317e07bab17b3f16502c1623778c1abeadbfd19
        Application ID               : {4dc3e181-e14b-4a21-b022-59fc669b0914}
        Certificate Store Name       : My
        Verify Client Certificate Revocation : Enabled
        Verify Revocation Using Cached Client Certificate Only : Disabled
        Usage Check                  : Enabled
        Revocation Freshness Time    : 0
        URL Retrieval Timeout        : 0
        Ctl Identifier               : (null)
        Ctl Store Name               : (null)
        DS Mapper Usage              : Disabled
        Negotiate Client Certificate : Disabled

  • SCCM Client Push

    Hi,
    I have run into a strange issue when setting up SCCM 2012 R2.  I configured the system discovery rule to get machines in the database from AD which was fine but it then did a client push to around half the machines.  I checked the Client Push Installation
    properties and this is not enabled so I am a bit confused to how this happened.   If you could point me to any logs that would help me work out what happened it would be greatly appreciated (only thing I can think is someone did the client push
    but no one is owning up to it)
    Thanks

    You might also want to check out the Status Message Query for All audit messages on your site to see if someone did the change. More on this here:
    http://blog.vdx.com/auditing-events-in-configuration-manager-2012/

  • SCCM Client Push Ports

    Dears,
    I need to understand more on SCCM 2012 Client push ports. I am pushing the client from primary site server.
    As per MS, it’s recommended to have SMB open between site server and client systems.
    My client is accepted to open SMB port (one way) between site servers to client. They are not accepting to open SMB between Clients to Site server.
    I need your suggestion to have below network firewall ports are ok to work on client push.
    Site Server -- > Client
    Description
    UDP
    TCP
    Service Message Blok
    445
    RCP Dynamic
    DYNAMIC
    Hypertext Transfer Protocol (HTTP)
    80
    Client -- > Site Server
    Description
    UDP
    TCP
    Hypertext Transfer Protocol (HTTP)
    80
    Or still we need to open SMB between clients to site server, if yes, please provide the justification.
    Regards,
    Kannan.CS
    Regards, kanna

    https://technet.microsoft.com/en-us/library/hh427328.aspx. SMB from client to server is not needed. 
    Torsten Meringer | http://www.mssccmfaq.de

Maybe you are looking for

  • Part payment against Downpayment Request

    Dear Friends, Even a part payment received against Downpayment Request (Vendor) clears the Request with the entire amount. In other words, it does not keep the Request open though no full payment is received against this Request. Pl. suggest suitable

  • Getting List of Figures, List of Tables titles into main TOC

    I have a book (all in one file) with three TOCs: List of Tables, List of Figures, main Table of Contents. I want the TOC titles from List of Tables and List of Figures to show up in the main TOC. They don't. Does anyone know why? Do TOCs not pick up

  • Long term planning material not displayed in MS04

    Hi, May I request your assistance on my issue? When I run the MS04 one of the component material is not displaying. I have change the planning period and run again the MS03 for a specific material which is the finished material. My component is now d

  • XML Gateway for Oracle Applications to 3rd Party Application System

    Hi, I am having one unique requirement for sending/receving an xml file from Oracle Applications to 3rd Party Application system (which supports XML). Has anyone worked on the XML Gateway for sending/receiving the PO/ASN or Pick Release/Ship Confirm

  • Linking Report Designer pdf to iview

    Hi, I have created several pdf reports using the bex report designer in BI Bex tools. I now wish to link these reports to iview in the portal side. I have succesfully linked queries using this string infocube=ZMFITVC01&query=Z_TRIP_MILEAGE_REPORT I h