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

Similar Messages

  • Cross-forest SCCM 2012 client push

    Hi all,
    Hoping that you might be able to send me in the right direction either by pointing me at some existing documentation or sharing your insights.
    First, we’ve got an SCCM 2012 installation running fairly well in a domain (let’s call it A), doing things like Forefront and Software Updates.  Second, I’ve got another domain (B).  There is a two-way trust between these domains.
    We’re able to run a discovery on domain B, and show clients in SCCM, but we are not able to push the client to machines in Domain B.
    We’ve added and have succeeded in publishing domain A’s SCCM management points into domain B’s AD.
    So far… so good, but… now there are two scenarios:
    1)  When the SCCM site is configured to use PKI client certificate authentication, domain B clients cannot access resources on the domain A management point.
    We’ve tried trusting Domain B’s certificate authority by importing in the CA root certificate into the Domain A management point server (local machine) certificate store for Trusted Certificate Authorities, but that doesn’t seem to work.
    The following error is seen in the ccmsetup log:
    Failed to get DP loations as the expected version from MP “HTTPS://servername.domain.local’. Error 0x80072f8f (I’ve the machine name)
    2)  When SCCM is *not* configured to use client certs, it looks like the clients try to hit the MP using a UNC path that does not exist on the MP.  The error shows:
    Source \\servername.domain.local\SMSClient is inaccessible (67)
    The client *can* connect to the server using the UNC, however, the correct path to this server would be,
    \\servername.domain.local\SMS_Site1\Client …
    In the absence—or inability to find—documentation on this subject, we are pretty much guessing here on how to do this stuff.
    The preference would be to get scenario 1 working so that domain B clients can access the MP, using client certs; however, if that’s not possible, we’d like to get scenario B working.
    Thanks in advance for your help.
    Thanks,
    Kim

    Hi there,
    A short note on this:
    In fiddling around more, I came up with a workaround.  In short, I turned of the certificate authentication requirement, which (as stated above) changes the client behavior to use a UNC install path that did not exist.  So I created a share with
    the client files in it and granted everyone read access to it on the share and NTFS levels.
    I am near sure that this is not the best way to do things, but I did get client push to work.
    The problem now is that these clients are not showing up as having clients in the SCCM Management console.
    Any further direction or advice on the proper way to get push install working in the environment described would be most appreciated.
    Best,
    Kim

  • 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

  • How/ where to change a weekly off to working day, working day to weekly off by maintaining IT0007 is 7-time evaluation without payroll integration

    Dear Experts
    We are doing Negative Time Management where we record only deviations
    But customer has third party time machine which required to be integrated with SAP system
    As I know, from the time recording terminal, i should map SAP number to all employees and then get a text mail the  details with employee attendance for the  respective dates and times. Then, have to create a ABAP report which will read the text file and update clock in/out with date into SAP system. After this we can check employee attendance infotype 2011.
    But, Before going for above, time administrator wants to set IT0007 as 7- time evaluation without payroll integration, then maintain data in IT0050 & IT2011
    Then run Time Evaluation then the out put will be according to the data maintained in IT 2011. Now the  requirement is, time administrator wants to change eg. the  day is suppose to be working day for any employee but based on adjustments that day became weekly off, another employee suppose to work but again due to some adjustments that day became weekly off, so how this time administrator can change this and where. This is like, time administrator  need to see the total work schedule for an employee and needs to change whichever data and whenever or after time evaluation, he could see the total work schedule as desired.
    And also, time administrator wants to change schedule manually for any of the employee during that particular period and view the same.
    Please note that, ESS/MSS haven't implemented yet.
    Appreciated all your prompt responses to this.
    Thanks
    SS

    No
    I have created a workschedule on wednesday In a year there can be weekly off 5 or 6 times on Saturday or Sunday So  in that case there is no need to create three workschedules we can create one workschedule and change the days Again we need to regenerate the workschedules inorder to take 'off's" in to account. that is what iam thinkinng at the moment. Yes there is no need to do anything in IT 007 If there is any change in Shift in that Case User has to change workschedule in IT 007.
    If there is weekly off he can select the dates on which day it is falling and generate the workschedule.
    for changing shifts he should change work schedule in IT 007
    Is this is right approach please throw some light on this
    My client requirement was Sometimes there can be weekly off in the company It can be either wednesday off or saturday off or
    unday off or it can be any day.
    Edited by: My SAP Cronies on Feb 2, 2012 5:17 AM
    Edited by: My SAP Cronies on Feb 2, 2012 5:22 AM

  • Time Management Status 7 without Payroll Integration.

    Dear All,
    when do we go about Time Management Status - 7 - without Payroll Integration.
    In this case how the process goes on SAP. what do we do in this status. do we record employees attendances in 2002 IT
    actually what happens.
    Regards
    kvn

    Hi KVN,
    You are using time management status 7 which means that no integration to payroll.Now as far as ur Quotas are considered then please use RPTQTA00 which is just a program and RPTIME00 or PT60 which will run time evaluation and if u want your Quotas to generate in time evaluation then just change V_556A_B in this table to increase so with time evaluation and no generation for Quotas to be with time evaluation.
    The client may ask sometimes for few Quotas to be prorated on a daily basis and so on in that case go with TE Quota generation
    else RPTQTA00 is ok.So see ur business and use either of it
    Let me know if u have any further Questions.
    Thanks
    Swati

  • Problem installing SCCM client in remote untrusted forest

    Hi,
    My configuration is :
    My network is in two parts : intranet and a DMZ. In the DMZ there is another forest and domain. There is no trust between the forest in the DMZ and the internal network. I configured the remote forest in SCCM with a user account that has Domain Admin acces
    in the DMZ forest/domain.
    The primary site server is located in the internal part of my network. SQL is installed on a remote server. Management point, distribution point, Fallback Status Point roles are installed on the primary site server. SMS Provider is installed on the primary
    site server.
    In the DMZ part, I have a management point, distribution point installed on one server.
    The forest discovery works fine. I can query AD in the remote forest (DMZ).
    I have a problem installing the SCCM client on computers located in the remote forest with client push or with the command line.
    CCMSETUP.EXE /MP:DMZ site server /DP:DMZ site server /FSP: primary site server SMSSITECODE:SIT
    In CCMSetup.log I can see that the client try to communicate with my DMZ site server but it reverts to the management point and distribution point located in the internal part of the network. The installation fails and will try in 10 minutes.
    Do anyone has seen this problem before? Am I missing something? Could it be a configuration issue?
    Could you help me whit this please?
    Thanks in advance for your time!
    Jacques

    Does the client installation work when you install the client manually on the untrusted domain client? What does the CCM.log say on the site server?
    Have you double checked the firewall ports for the client push installation? The ports needed for the client push to work are as follows (from the site server to the client):
    SMB - TCP 445
    RPC Endpoint Mapper - TCP 135 / UDP 135
    RPC Dynamic Ports
    And to Management Point:
    HTTP - TCP 80 (When using HTTP)
    HTTPS - TCP 443 (When using HTTPS)
    Also a quote from
    TechNet: "In addition to the ports listed in the following table, client push installation also uses Internet Control Message Protocol (ICMP) echo request messages from the site server to the client computer to confirm whether the client
    computer is available on the network. ICMP is sometimes referred to as TCP/IP ping commands. ICMP does not have a UDP or TCP protocol number, and so it is not listed in the following table. However, any intervening network devices, such as firewalls, must
    permit ICMP traffic for client push installation to succeed."

  • 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

  • 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

  • Automatic Client Push not working - Site System Servers

    Having an issue getting automatic site-wise client push to work when only
    having "Configuration Manager site system servers" selected.  This was turned on after discovery was enabled and fully executed.
    SCCM 2012 R2 CU1, Single Primary Site Server, 2 Management Points (one on primary and second is standalone), with 5 DP's (currently), SQL is standalone.
    The site systems are within the IP range boundaries and show as assigned (i.e. site code showing in console of object).  The boundaries are in a boundary group with site assignment selected, and a DP added.  When I view the object properties I
    see its returning the correct IP that does fall withing the IP range boundary.
    Nothing in the ccm.log indicating its ever trying to install the client and the ccr and ccrretry folders are empty.  I can do a manual client push without issue to a site server object or a discovered desktop/laptop object.
    Is there something I may be missing here?  And does anyone know the interval in which SCCM should be creating ccr records for discovered objects that don't have a client?

    Thanks or the quick replies everyone.  To answer Idan's questions, no errors in log or component status and SQL is not clustered.
    John, I hope this isn't the case.  If it were wouldn't that effectively mean you would not be able to enabled discovery until you are ready to turn on auto client push?  And if you did that you would have no way to control the client roll out.
     Maybe I am missing something in that equation.  I'll test that theory regardless but if that ends up being the case that is alarming!  :-)
    Jason, thanks for the tip on the potential bug.  Was really more so hoping to validate automatic client push rather than actually needing it for my site system servers.  So if it is the issue you reference above hopefully its just contained to
    the site system servers.  Would be nice to be able to select automatic client push to just a collection of devices prior to turning it on for site wide deployment.  
    I guess I could always just turn off discovery temporarily and delete all but some test clients, enable client push for workstations, then once validated, turn it back off and re-enable discovery.  (wouldn't turn push back on until most clients are
    deployed on the roll out schedule)

  • Automatic Client Push

    We recently migrated from SCCM 2007 to SCCM 2012 R2.  I did the migration by manually pushing out clients, and now that a majority are migrated, I enabled Automatic Client Push.  However, resources that were already discovered without the client
    installed aren't receiving the client.  Checking CCM.log on the primary site server, I don't see SCCM even attempting to push the client.
    Any ideas?

    Can you post a portion of the ccm.log?
    I apparently can't post much of it.  The workstations that are failing are ones I pushed to manually the day prior.  This is from the point of enabling automatic client push, and a bit afterwards:
    Waking up for site control file directory change notification  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.896+360><thread=17076 (0x42B4)>
    The Site Control File has changed, parameters will be reread.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.965+360><thread=17076 (0x42B4)>
    Updating Site Parameters  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.984+360><thread=17076 (0x42B4)>
    ~MP Ports: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.998+360><thread=17076 (0x42B4)>
    ~IISPreferedPort: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.012+360><thread=17076 (0x42B4)>
    ~MP SSL Ports: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.025+360><thread=17076 (0x42B4)>
    ~IISSSLPreferedPort: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.040+360><thread=17076 (0x42B4)>
    ~Default MP: SCCM.Domain.com  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.053+360><thread=17076 (0x42B4)>
    ~Default MP Type: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.067+360><thread=17076 (0x42B4)>
    ~Default MP: [None]  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.081+360><thread=17076 (0x42B4)>
    ~Certificate Selection Criteria:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.094+360><thread=17076 (0x42B4)>
    ~Certificate Store:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.107+360><thread=17076 (0x42B4)>
    ~SSL State: 224  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.120+360><thread=17076 (0x42B4)>
    ~Select First Certificate: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.134+360><thread=17076 (0x42B4)>
    ~Certificate Issuers:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.159+360><thread=17076 (0x42B4)>
    Checking configuration information for server: SCCM.Domain.COM.~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.174+360><thread=17076 (0x42B4)>
    ~No Fallback Status Point installed on the Site  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.187+360><thread=17076 (0x42B4)>
    ~Install on DC: True  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.200+360><thread=17076 (0x42B4)>
    ~Option for installing using IP address: 0  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.214+360><thread=17076 (0x42B4)>
    Retrieving properties from the site control file.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.226+360><thread=17076 (0x42B4)>
    ~Advanced Client Command Line: SMSSITECODE=STE  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.239+360><thread=17076 (0x42B4)>
      Ignoring unrecognized property "Advanced Client Command Line Default"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.253+360><thread=17076 (0x42B4)>
    ~Security Mode Option - CCR buffering disabled.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.266+360><thread=17076 (0x42B4)>
    ~Default Client Type: -1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.279+360><thread=17076 (0x42B4)>
    Sleeping for 981 seconds...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.300+360><thread=17076 (0x42B4)>
    CCM Shutting down (12)~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.799+360><thread=10212 (0x27E4)>
    No request returned from queue  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.836+360><thread=10212 (0x27E4)>
    CCM Shutting down... (4)~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.850+360><thread=17076 (0x42B4)>
    CCM Main thread is exiting...~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.908+360><thread=17076 (0x42B4)>
    SMS_EXECUTIVE started SMS_CLIENT_CONFIG_MANAGER as thread ID 2664 (0xA68).  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.269+360><thread=16000 (0x3E80)>
    ************** Client Config Manager main thread starting **************  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.294+360><thread=2664 (0xA68)>
    This site: "STE".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.308+360><thread=2664 (0xA68)>
    This site type: "1".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.324+360><thread=2664 (0xA68)>
    This machine: "SCCM.Domain.com".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.338+360><thread=2664 (0xA68)>
    The Site Control File has changed, parameters will be reread.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.498+360><thread=2664 (0xA68)>
    Updating Site Parameters  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.570+360><thread=2664 (0xA68)>
    ~MP Ports: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.615+360><thread=2664 (0xA68)>
    ~IISPreferedPort: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.630+360><thread=2664 (0xA68)>
    ~MP SSL Ports: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.644+360><thread=2664 (0xA68)>
    ~IISSSLPreferedPort: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.658+360><thread=2664 (0xA68)>
    ~Default MP: SCCM.Domain.com  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.680+360><thread=2664 (0xA68)>
    ~Default MP Type: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.693+360><thread=2664 (0xA68)>
    ~Default MP: [None]  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.705+360><thread=2664 (0xA68)>
    ~Certificate Selection Criteria:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.718+360><thread=2664 (0xA68)>
    ~Certificate Store:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.732+360><thread=2664 (0xA68)>
    ~SSL State: 224  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.745+360><thread=2664 (0xA68)>
    ~Select First Certificate: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.758+360><thread=2664 (0xA68)>
    ~Certificate Issuers:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.774+360><thread=2664 (0xA68)>
    Checking configuration information for server: SCCM.Domain.COM.~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.788+360><thread=2664 (0xA68)>
    ~No Fallback Status Point installed on the Site  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.801+360><thread=2664 (0xA68)>
    ~Install on DC: True  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.819+360><thread=2664 (0xA68)>
    ~Option for installing using IP address: 0  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.845+360><thread=2664 (0xA68)>
    Retrieving properties from the site control file.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.864+360><thread=2664 (0xA68)>
    ~Advanced Client Command Line: SMSSITECODE=STE  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.878+360><thread=2664 (0xA68)>
      Ignoring unrecognized property "Advanced Client Command Line Default"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.893+360><thread=2664 (0xA68)>
    ~Security Mode Option - CCR buffering disabled.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.914+360><thread=2664 (0xA68)>
    ~Default Client Type: -1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.927+360><thread=2664 (0xA68)>
    Confirming all required files are available on the site server~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.942+360><thread=2664 (0xA68)>
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.965+360><thread=2664 (0xA68)>
      Site Server Name             "\\SCCM.Domain.com"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.980+360><thread=2664 (0xA68)>
      Site Code                    "STE"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.020+360><thread=2664 (0xA68)>
      CCM Account 1                "Domain\clientdeploy"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.054+360><thread=2664 (0xA68)>
      CCM Account 2                "Domain2\clientdeploy"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.067+360><thread=2664 (0xA68)>
      CCM Account 3                "<end of list>"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.081+360><thread=2664 (0xA68)>
      Max CCR Processing Threads    10     $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.095+360><thread=2664 (0xA68)>
      CCR Processing Thread Timeout 600000 ms  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.108+360><thread=2664 (0xA68)>
      Sitewide Travel Mode Switch   USE CLIENT SETTING  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.131+360><thread=2664 (0xA68)>
      Days Between Account Cleanups 30  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.143+360><thread=2664 (0xA68)>
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.156+360><thread=2664 (0xA68)>
    Parameters for queue: "Incoming"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.168+360><thread=2664 (0xA68)>
      Inbox Path                   "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.181+360><thread=2664
    (0xA68)>
      Read Queue Every             DIR CHANGE NOTIFICATION    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.193+360><thread=2664 (0xA68)>
      Retry CCR For                168 Hours    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.206+360><thread=2664 (0xA68)>
      Report Error After           ERROR REPORTING OFF    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.219+360><thread=2664 (0xA68)>
      Warn when Queue Exceeds      100  CCRs    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.246+360><thread=2664 (0xA68)>
      Delay Between CCRs           100 Millisec    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.259+360><thread=2664 (0xA68)>
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.271+360><thread=2664 (0xA68)>
    Parameters for queue: "Retry"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.284+360><thread=2664 (0xA68)>
      Inbox Path                   "E:\Program Files\Microsoft Configuration Manager\inboxes\ccrretry.box"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.297+360><thread=2664
    (0xA68)>
      Read Queue Every             60 Minutes    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.310+360><thread=2664 (0xA68)>
      Retry CCR For                168 Hours    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.323+360><thread=2664 (0xA68)>
      Report Error After           24 Hours    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.336+360><thread=2664 (0xA68)>
      Warn when Queue Exceeds      150  CCRs    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.349+360><thread=2664 (0xA68)>
      Delay Between CCRs           100 Millisec    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.361+360><thread=2664 (0xA68)>
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.374+360><thread=2664 (0xA68)>
    Parameters for queue: "Processing"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.387+360><thread=2664 (0xA68)>
      Inbox Path                   "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box\InProc"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.389+360><thread=2664
    (0xA68)>
      Read Queue Every             DIR CHANGE NOTIFICATION    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.415+360><thread=2664 (0xA68)>
      Retry CCR For                CCR DOESN'T EXPIRE    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.428+360><thread=2664 (0xA68)>
      Report Error After           ERROR REPORTING OFF    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.440+360><thread=2664 (0xA68)>
      Warn when Queue Exceeds      150  CCRs    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.453+360><thread=2664 (0xA68)>
      Delay Between CCRs           0 Millisec    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.466+360><thread=2664 (0xA68)>
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.478+360><thread=2664 (0xA68)>
    Moving CCRs from processing queue to incoming queue~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.491+360><thread=2664 (0xA68)>
    Started Incoming Queue Thread, ThreadId = 2488  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.505+360><thread=2664 (0xA68)>
    Started Retry Queue Thread, ThreadId = 1548  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.518+360><thread=2664 (0xA68)>
    Sleeping for 300 seconds...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.531+360><thread=2664 (0xA68)>
    THREAD_ProcessQ starting, Input Queue ID is 0.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.551+360><thread=9352 (0x2488)>
      Queue Name is "Incoming".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.632+360><thread=9352 (0x2488)>
      Queue Directory is "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.697+360><thread=9352 (0x2488)>
    Sleeping for 300 seconds before processing requests on queue Incoming...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.711+360><thread=9352 (0x2488)>
    THREAD_ProcessQ starting, Input Queue ID is 1.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.531+360><thread=5448 (0x1548)>
      Queue Name is "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.773+360><thread=5448 (0x1548)>
      Queue Directory is "E:\Program Files\Microsoft Configuration Manager\inboxes\ccrretry.box".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.785+360><thread=5448 (0x1548)>
    Sleeping for 480 seconds before processing requests on queue Retry...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.804+360><thread=5448 (0x1548)>
    ~Waking up for site control file directory change notification  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.148+360><thread=2664 (0xA68)>
    The Site Control File has not changed since the last parameter update.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.170+360><thread=2664 (0xA68)>
    Updating Site Parameters  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.183+360><thread=2664 (0xA68)>
    ~MP Ports: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.200+360><thread=2664 (0xA68)>
    ~IISPreferedPort: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.247+360><thread=2664 (0xA68)>
    ~MP SSL Ports: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.260+360><thread=2664 (0xA68)>
    ~IISSSLPreferedPort: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.279+360><thread=2664 (0xA68)>
    ~Default MP: SCCM.Domain.com  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.298+360><thread=2664 (0xA68)>
    ~Default MP Type: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.311+360><thread=2664 (0xA68)>
    ~Default MP: [None]  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.324+360><thread=2664 (0xA68)>
    ~Certificate Selection Criteria:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.337+360><thread=2664 (0xA68)>
    ~Certificate Store:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.351+360><thread=2664 (0xA68)>
    ~SSL State: 224  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.364+360><thread=2664 (0xA68)>
    ~Select First Certificate: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.379+360><thread=2664 (0xA68)>
    ~Certificate Issuers:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.392+360><thread=2664 (0xA68)>
    Checking configuration information for server: SCCM.Domain.COM.~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.411+360><thread=2664 (0xA68)>
    ~No Fallback Status Point installed on the Site  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.494+360><thread=2664 (0xA68)>
    ~Install on DC: True  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.520+360><thread=2664 (0xA68)>
    ~Option for installing using IP address: 0  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.535+360><thread=2664 (0xA68)>
    Sleeping for 282 seconds...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.557+360><thread=2664 (0xA68)>
    CCR count in queue "Incoming" is 0.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.577+360><thread=2664 (0xA68)>
    CCR count in queue "Processing" is 0.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.590+360><thread=2664 (0xA68)>
    Sleeping for 300 seconds...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.603+360><thread=2664 (0xA68)>
    Getting a new request from queue "Incoming" after 100 millisecond delay.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.733+360><thread=9352 (0x2488)>
    Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.746+360><thread=9352
    (0x2488)>
    Getting a new request from queue "Retry" after 100 millisecond delay.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.827+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_GetPushRequestMachine] 2097152351~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.944+360><thread=5448 (0x1548)>
    Successfully retrieved information for machine workstation2 from DB  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.957+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_GetPushRequestMachineIP] 2097152351~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.969+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097152351~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.983+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_GetPushMachineName] 2097152351~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.996+360><thread=5448 (0x1548)>
    Received request: "2097152351" for machine name: "workstation2" on queue: "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.008+360><thread=5448 (0x1548)>
    Stored request "2097152351", machine name "workstation2", in queue "Processing".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.021+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152351, 1~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.036+360><thread=5448 (0x1548)>
    ----- Started a new CCR processing thread. Thread ID is 0x335c. There are now 1 processing threads  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.061+360><thread=5448 (0x1548)>
    Submitted request successfully  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.074+360><thread=5448 (0x1548)>
    Getting a new request from queue "Retry" after 100 millisecond delay.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.087+360><thread=5448 (0x1548)>
    Found CCR "2097152396.ccr" in queue "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.099+360><thread=5448 (0x1548)>
    ======>Begin Processing request: "2097152351", machine name: "workstation2"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.074+360><thread=13148 (0x335C)>
    Execute query exec [sp_IsMPAvailable] N'STE'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.129+360><thread=13148 (0x335C)>
    ---> Trying each entry in the SMS Client Remote Installation account list~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.142+360><thread=13148 (0x335C)>
    ---> Attempting to connect to administrative share '\\workstation2\admin$' using account 'Domain\sccmclientdeploy'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.155+360><thread=13148 (0x335C)>
    Execute query exec [sp_CP_GetPushRequestMachine] 2097152396~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.211+360><thread=5448 (0x1548)>
    Successfully retrieved information for machine workstation1 from DB  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.230+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_GetPushRequestMachineIP] 2097152396~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.243+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097152396~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.256+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_GetPushMachineName] 2097152396~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.269+360><thread=5448 (0x1548)>
    Received request: "2097152396" for machine name: "workstation1" on queue: "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.283+360><thread=5448 (0x1548)>
    Stored request "2097152396", machine name "workstation1", in queue "Processing".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.296+360><thread=5448 (0x1548)>
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152396, 1~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.312+360><thread=5448 (0x1548)>
    ---> Connected to administrative share on machine workstation2 using account 'Domain\sccmclientdeploy'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.213+360><thread=13148 (0x335C)>
    ---> Attempting to make IPC connection to share <\\workstation2\IPC$> ~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.351+360><thread=13148 (0x335C)>
    ---> Searching for SMSClientInstall.* under '\\workstation2\admin$\'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.368+360><thread=13148 (0x335C)>
    ---> Unable to connect to WMI on remote machine "workstation2", error = 0x80041002.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.457+360><thread=13148 (0x335C)>
    ---> Deleting SMS Client Install Lock File '\\workstation2\admin$\SMSClientInstall.STE'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.470+360><thread=13148 (0x335C)>
    Execute query exec [sp_CP_SetLastErrorCode] 2097152351, -2147217406~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.491+360><thread=13148 (0x335C)>
    Stored request "2097152351", machine name "workstation2", in queue "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.505+360><thread=13148 (0x335C)>

  • Client Push install, deploying slower then expected.

    I am in the process of standing up my SCCM 2012 R2 enviroment, I have a CAS, and 1 primary site(adding more later), and from the Primary site, I have several Distribution sites.  Boundaries have been detected and I have configured them into appropriate
    Boundary Groups (Only using IP based Boundaries), and I have pointed the group to the Site server for the distribution point.  These sites are only running the Site System, and Distribution Point, the only Management point is on my Primary server.  In
    the beginning I was manually kicking of the Client install base on collections, but now that I have all my DP set up.  I enabled the Client Push Installation, selecting only Workstations, the account is the same account I was using to deploy the clients
    manually, and the only Installation Properties is the SMSSiteCode.  I enable the Client Push 24 hours ago, and it has only installed on an additional 300 computers, out of about 3000 that had not yet received the client.
    I have viewed the CCM.log and I see it rolling through at a slow rate, I expected to get a large influx of clients do to the number without it.  Is this a generally slow method?  I have clients reporting, in all boundaries, except for 1, and the
    DP points are showing they have the SCCM client.  I have spot checked the IP Boundaries from SCCM with what I have in our DHCP servers in those locations, and they are correct.  I have verified, the service account can ping and has access to the
    admin share.
    Is there something I missed? 

    I concur, if you are just now installing clients agents, stop, format your drives and start over, there is no reason for having a CAS and it *will* cause you issues having one.
    As for the CCM, process, there are a lot of caveats. First you mentioned having 6,000 clients? Where is this number from? Is this the number of clients discovered by ConfigMgr?
    Next, ConfigMgr will *not* generate a CCR for clients not assigned to the site (unless it is forced to during manual client install). No, if are viewing the All Systems collection, any resource without a site code will *not* have a CCR generated for it.
    CCM, as Torsten mention, throttles itself to 10 CCRs at a time. Any CCRs that get placed in the ccrrety box get retried every hour. So, if you have 3,000 assigned resources without client agents, it will take a while for it churn through those. The next
    time full discovery runs, CCRs will again be created for any assigned resources that do not have the client agent installed.
    Jason | http://blog.configmgrftw.com
    +1
    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

  • Automatic client push installation not working

    I created one secondary server and replication with CAS is active. Boundary also configured and enabled automatic client push installation. 
    Daily i am checking some machines, but agents are not getting installing automatically . But manual client installation is working fine without any issue. Anyone can help on this to find outwhy automatic clients push installation is not running on client
    machines

    Which site code is showing, for your secondary or for your primary?
    If secondary, then as Joyce pointed out, you need to check ccm.log on the secondary site server needs to be checked because that's where the client will be pushed from.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCCM Client Push installation comms/ports

    Hi all,
    I've done a bit of reading of articles/resources and I'm not quite clear on communication requirements. I read that ICMP ping is required in addition to various TCP ports for client push installation. Our setup is a hub and spoke design with firewalls which
    we don't administer between premises (convenient how 'site' is a key word in SCCM grrr) :)
    I thought we would be able to have Distribution Points/Management Points on remote premises and have the clients on those premises do all necessary communication with the local server in their same subnet in order to deploy the SCCM client and report status.
    Do I require ping etc through to the main server before it will use the local Distribution Point to deploy and report via the local Management Point?
    We have a few clients manually installed at a couple of remote premises which are reporting but can't push the client and we have many clients at our central premises which have had client push installation and reported back successfully - presumably because
    they are in the same subnet with no firewalls between.
    I also have a couple of manually installed clients at remote premises which are not reporting client activity but I'll look into that further once the main client push feature is working.
    Thanks for any clarification, I'm building my SCCM knowledge!
    R

    Hi Gerry,
    Thanks for your response and the resources on your blog.
    I have looked at the link but I'm still not clear on instances (if any) where direct communication is required between the client and the primary site server.
    Should clients be expected to be able to communicate only with their local distribution point/management point which is in the same subnet if they are firewalled from the primary site server as I have? How does SCCM know to have a remote distribution point
    do the communication to a client that is local to it without knowing the IP address? My servers have exceptions setup between them but the clients are fairly restricted to their own premises.
    My boundaries are configured per AD Site but unless SCCM checks DNS for IP address would it be able to determine the AD Site to have the nearest DP/MP handle all the client interaction?
    My query about ICMP was based on this link https://technet.microsoft.com/en-us/library/gg682180.aspx which says:
    "In addition to the ports listed in the following table, client push installation also uses Internet Control Message Protocol (ICMP) echo request messages from the site server to the client computer to confirm whether the client computer is available on
    the network."
    Edit: I see Jason has partly answered my question above - I spent too long typing this post :)
    Thanks

  • Account assignment error even without controlling integration

    We have set up a service order without controlling integration nor billing. After releasing the service order and saving, CRM throws out an error as if it is trying to create an internal order in ECC. See error log below.
    We do not intend to replicate CRM customers to ECC which should not be a problem for our requirements.
    The error log is pointing to missing customers in ECC as "Customer" is a controlling characteristic when one want to create an internal order. In our case, we don't want this to happen and have done the necessary configuration. The relevant item category in the service order has been set as not relevant for costing.
    Can anybody see a reason why we are having this behaviour? How can we get around it?
    Note: The solution consisting of preventing document distribution to ECC via status profile would not work for us as we also intend to use Logistics integration to create Purchase orders in ECC.
    Cheers
    Diagnosis
    Errors occurred when assigning an account assignment object to a business transaction. To view the error message, see the accompanying log file.
    Transfer Log
    No customer is assigned to business partner 005056822FA61EE3B094CD9026046ADD (Notification E XR 004)
    No customer is assigned to business partner 005056822FA61EE3B094CD9026046ADD (Notification E XR 004)
    Characteristics for Controlling object have errors (Notification E IAOM 034)
    Characteristic "Sold-to party" for business scenario "CRM Service" is missing (Notification E IAOM 007)
    Characteristics for Controlling object have errors (Notification E IAOM 034)
    Characteristic "Sold-to party" for business scenario "CRM Service" is missing (Notification E IAOM 007)
    Characteristics for Controlling object have errors (Notification E IAOM 034)

    Hello Thierry,
    Are you sure that you use items that are non-relevant for billing?
    Regards,
    Nicolas.

  • Crystal Developer XI without Sap integration kits cant see released Queries

    Hi All!
    When I'm used MS Excel, I can see released SAP BW Queries via SAP OLE DB access. But when I'm used Crystal Developer XI (without Sap integration kits), I can’t see released SAP BW Queries via SAP OLE DB access.
    What's a problem here?
    WBR Artem

    Hi,
    you missing the SAP integration Kit. To conenct to SAP BW you need the SAP Integration Kit installed.
    ingo

Maybe you are looking for

  • Brand new Ipod Touch, tried to update, stuck in recovery for hours

    I just received an iPod Touch today. I hooked it up to itunes, played around with it for a bit, with no problems, and several hours later downloaded the upgrade 2.02 from the itunes store. I followed the directions. In the process of downloading, I n

  • Emac monitor goes black – slap brings it back to life

    Last couple of days my emac monitor will just shut down and go black, just like an old TV tube packing up used to. It won't return on restart, but did return a couple of times after I took out mains lead from side of computer, let it rest, then tried

  • Trying to video chat

    i have a logitech webcam connected to my powerbook, yet when i goto try and video chat with someone it says that no camera is connected. what to do? im thinking maybe i have to have an apple webcam? like hte isight? or what?

  • HT5167 hi there i hate this new windo  how can i put my system back  to lion

    hi there i hate this new  window i want to out my suystem back to lion . How can i do that

  • Sending Media Product Master via ALE

    Hello, I have setup ALE for generic FI master data (i.e. GL accounts) and it is working correctly. My client also wants to sync MPM data using ALE but I am not able to see a way to do that. I do not see a message type for MPM family, product, or issu