none
Instalacion de clientes de SCCM ( Push) en Sitios Secundarios RRS feed

  • Pregunta

  • Hola Buenos dias, voy a tratar de resumir mi pregunta ya que es extenso las pruebas y configuraciones que he realizado:

    1- Mi topologia consta de 3 localidades fisicamente separas , tengo un AD en cada localidad y un dominio ( topologia de replicacion entre sitios) tengo 3 site asociados a cada localidad.

    2- Tengo un site Primario cuyo Site code es SCM y pertenece eal SITE1, en el he instalado todos los roles necesarios y hasta el momento funciona bastante bien, instale los clientes bien ( que corresponden al site1), cree politicas por ejemplo de actualizacion de la huella del antivirus y se hace bien , etc.

    3- Cree un SCCM secundario en este caso para el Site2, el mismo se instalo bien y active los rool de Distribution y Managment, los bounderies estan configurados bien, hay dos bounderies correspondiente a cada site de AD, hay dos bounderiews group correspondiente a cada site.

    4- En la configuracion del client push de secundario me cerciore de activarlo y alli definí el parametro de  SMSSITECODE=CUM, en ves de AUTO puse o force que fuese al site que corresponden esos clientes.

    5- El error es que cuando instalado el cliente la operación se hace bien, es decir, si abres el logs de ccm en el site principal ves que no se levanta ningún proceso de instalación, si abres el mismo logs en el Server secundario ves que levanta el proceso de instalación, eso me hace pensar que  la instalacion esta bien por que la ejecuta el servidor al que pertecece el site del usuario. Sin embargo una ves finaliza la instalacion en el cliente y reviso el cliente apunta al SITECODE SMS que el el site del principal y no al CUM que es el site del Secundario.

    6- He hecho infinidades de pruebas y no e podido lograr que esto cambie

    7- Hay errores en el logs ccmsetup del cleinte que pudieran decir algo pero no logro conseguir algo

    ****************************************************************************************************

    This is not a supported write filter device. We are not in a write filter maintenance mode.
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=CUM))
    OperationalXml '<ClientOperationalSettings><Version>5.00.8498.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>480</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F6308201DEA003020102021021A84897EEF1889949B3959252E52463300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3137303532353134353531395A180F32313137303530323134353531395A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100EFD143457446E440C9156A44A94B4B64616CF57E2C1C91C48F70B720235298DAD1F2E89574DA3B5CA173780E24D3C9DC1B73BE4D1A7FE3C5A7443C908128C7D0797B984FDA2FD86CEBECEB0874788E1ACD1472EAA119D774CC84B6096D9EF3E6FCD8FC40C4019BDDF274DEE40DCC8B7B9592858EFE3D37F823FBF9B8CD1C0D95FD12239E8A7B7EA292BCD68D364680195AADA8E0E5253656D0DDDE35D17B9E378402C401BE4671474B677062CBB5A394A29CDB3221B7A41324C132A84A7235E5CDB2493A093DD6B783FB8449F2883E02C9440BE5ABC594C7DB0DD3CB45B698FC389C4CD51035828791552EF25BEE0E2DBB967CC93099D387F9E486D9D65FBFA90203010001A33E303C30240603551D11041D301B82195444562D385134395753312E546F796F74612E636F6D2E766530140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100B4DD48307CD9826BD258C693E7BB75571D635B90F765BA4B1D9F7CC060898F664B71B36A004119469FFB5158D9D715B9B527B8AE05DB4E96A5ED9463D6D6CAC31B28DAB8DC07AA3A24EFEF8F3BDD8BD7CE8385039640E0EC8032C73EEEFBA60D52B9439492750BD5B397316282378FFA7DCC38D3B834F3ACAE38BA81BCADFA2F06AD479FEB73485FB8F68E5493B08CDCF2B18685EB4ED5637820754A6493AF696FC06909BD2334B6F3668A18B1358B9739F6F0BCBA3037FC47DB30A2A905A5700314F3687E0F450A4C495D4EB6D02C071A6034E9436C038DCE3BA0E99567BFE4FEB694A495A63F0F8299AFA522FA0611360016FD0BA1553C81F45BD2BC98EAE3</SiteSigningCert></SecurityConfiguration><CCM> <CommandLine>SMSSITECODE=CUM</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="Toyota.com.ve" /><Forest Value="Toyota.com.ve" /></ClientOperationalSettings>'
    Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.
    The MP name retrieved is 'TDV-LS460.' with version '8498' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>'
    MP 'TDV-LS460.Toyota.com.ve' is compatible
    Retrieved 1 MP records from AD for site 'CUM'
    Retrived site version '5.00.8498.1000' from AD for site 'CUM'
    SiteCode:         CUM
    SiteVersion:      5.00.8498.1000
    Only one MP TDV-LS460.Toyota.com.ve is specified. Use it.
    Searching for DP locations from MP(s)...
    Current AD site of machine is Site-Cumana
    Local Machine is joined to an AD domain
    Current AD forest name is cccc.com, domain name is cccc.com
    DhcpGetOriginalSubnetMask entry point is supported.
    Begin checking Alternate Network Configuration
    Finished checking Alternate Network Configuration Adapter {E05F602C-E9EB-4D10-9BEA-E87D930B2C76} is DHCP enabled. Checking quarantine status.
    Sending message body '<ContentLocationRequest SchemaVersion="1.00">
      <AssignedSite SiteCode="CUM"/>
      <ClientPackage RequestForLatest="0"/>
      <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0">
        <ADSite Name="Site-Cumana"/>
        <Forest Name="cccc.com"/>
        <Domain Name="cccc.com"/>
        <IPAddresses>
    <IPAddress SubnetAddress="172.17.2.0" Address="172.17.2.180"/>
        </IPAddresses>
      </ClientLocationInfo>
    </ContentLocationRequest>
    Sending message header '<Msg SchemaVersion="1.1"><ID>{99A40096-1983-423C-8922-8B6257E96B85}</ID><SourceID></SourceID><SourceHost>5XB8NH1-1</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:5XB8NH1-1:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>TDV-LS460.Toyota.com.ve</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2017-08-03T12:41:28Z</SentTime><Body Type="ByteRange" Offset="0" Length="1146"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>'
    CCM_POST 'HTTP://TDV-LS460.cccc.com/ccm_system/request'
    Content boundary is '--aAbBcCdDv1234567890VxXyYzZ'
    Received header 'NoReply'
    Received reply body 'NoReply' )
    MP did not find any locations matching with the site version.
    GetDPLocations failed with error 0x87d00203
    Failed to get DP locations as the expected version from MP 'TDV-LS460.cccc.com'. Error 0x87d00203
    Failed to get client version for sending state messages. Error 0x8004100e
    [] Params to send '5.0.8498.1008 Deployment Error: 0x0, '
    A Fallback Status Point has not been specified and no client was installed.  Message with STATEID='101' will not be sent.
    Failed to send status 101. Error (87D00215)
    Next retry in 10 minute(s)...
    Current AD forest name is cccc.com, domain name is cccc.com
    Domain joined client is in Intranet
    Current AD site of machine is Site-Cumana
    DHCP entry points already initialized.
    Begin checking Alternate Network Configuration
    Finished checking Alternate Network Configuration

    *****************************************************************************************************

    Alli coloque en negrilla los errores que pude identificar.

    Saludos y muchas gracias

    jueves, 3 de agosto de 2017 13:27