none
Cliente sccm não instala remotamente RRS feed

  • Pergunta

  • Estou com três micros windows xp e não consigo mandar a instalação do agente remotamente. Me parece problema de wmi, porém não consigo resolver. Ja parei o servico de wmi e renomei a pasta c:\windows\system32\wbem\repository e reiniciei o servico wmi; ele recria  a pasta, mas também não adiantou. Tambén não é problema de permissão e nem firewall.

    Segue o log do ccm.log:

    Received request: "COSF015404_COS_CELG_GO" for machine name: "COSF015404" on queue: "Retry". SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:33 2564 (0x0A04)
    Stored request "COSF015404_COS_CELG_GO", machine name "COSF015404", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:33 2564 (0x0A04)
    ----- Started a new CCR processing thread. Thread ID is 0x910. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:35 2564 (0x0A04)
    ======>Begin Processing request: "COSF015404_COS_CELG_GO", machine name: "COSF015404" SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:35 2320 (0x0910)
    ---> Trying the account stored in the CCR (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:35 2320 (0x0910)
    ---> Attempting to connect to administrative share '\\cosf015404.cos.celg.go\admin$' using account 'cos\sccm' SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:35 2320 (0x0910)
    Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:35 2564 (0x0A04)
    Getting a new request from queue "Retry" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:35 2564 (0x0A04)
    Sleeping for 60 minutes for queue "Retry". SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:35 2564 (0x0A04)
    ---> Connected to administrative share on machine cosf015404.cos.celg.go using account 'cos\sccm' SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:36 2320 (0x0910)
    ---> Attempting to make IPC connection to share <\\cosf015404.cos.celg.go\IPC$> SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:36 2320 (0x0910)
    ---> Searching for SMSClientInstall.* under '\\cosf015404.cos.celg.go\admin$\' SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:09:36 2320 (0x0910)
    CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:10:18 2320 (0x0910)
    ---> Unable to connect to WMI on remote machine "COSF015404", error = 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:10:18 2320 (0x0910)
    ---> Deleting SMS Client Install Lock File '\\cosf015404.cos.celg.go\admin$\SMSClientInstall.COS' SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:10:18 2320 (0x0910)
    Stored request "COSF015404_COS_CELG_GO", machine name "COSF015404", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:10:18 2320 (0x0910)
    <======End request: "COSF015404_COS_CELG_GO", machine name: "COSF015404". SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:10:18 2320 (0x0910)
    CCR count in queue "Retry" is 1. SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:11:01 3704 (0x0E78)
    Sleeping for 628 seconds... SMS_CLIENT_CONFIG_MANAGER 19/5/2010 15:11:01 3704 (0x0E78)

    quarta-feira, 19 de maio de 2010 18:12

Respostas

  • ola,

    o firewall do windows esta habilitado na estação?

    o erro é muito parecido quando o firewall esta habilitado, o compartilhamento de arquivos esta habilitador mas o WMI remoto esta sendo bloqueado...

    se for isso, vc tem 2 formas:
    1- na estação com problema: netsh firewall set service remoteadmin enable
    2- via gpo
    - Crie ou edite uma GPO existente
    - Expanda Computer Settings, Administrative Templates, Network, Network Connections, Windows Firewall e Domain Profile
    - Edite Windows Firewall: Do not allow exceptions e selecione Disabled
    - Edite Windows Firewall: Allow remote administration exception, selecione Enabled e em Allow unsolicited incomming messages from coloque o endereço IP do servidor SCCM e do Management Point
    - Edite Windows Firewall: Allow file and printer sharing exceptions, selecione Enabled e em Allow unsolicited incomming messages from coloque o endereço IP do servidor SCCM e do Management Point
    - Aguarde os clientes atualizarem as políticas ou atualize manualmente usando o comando gpupdate /force

    espero ter ajudado,


    Raphael - MCP/MCSA Security/MCSE Security/MCTS/MCITP/MCT/MVP - http://www.dotnetwork.com.br
    • Marcado como Resposta SmartnetINFO quinta-feira, 20 de maio de 2010 20:06
    quinta-feira, 20 de maio de 2010 09:34
    Moderador
  • Descobri o problema. Liberação de portas no firewall linux que temos entre as redes.

    • Marcado como Resposta SmartnetINFO quinta-feira, 20 de maio de 2010 20:06
    quinta-feira, 20 de maio de 2010 20:06

Todas as Respostas

  • Oi Gislaine, verifica se as portas que fazem comunicação com o escritorio remoto estao liberadas, as do sccm tenta para o serviço sms se tiver e o ccmsetup para tambem, ai remove a pastas ccmstup e ccm da estação, ai tenta instalar de novo. mas verifica as portas http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/953295c2-bca2-406f-85a2-f114bae19af8 espero ter ajudado
    MCTS - SCCM
    quarta-feira, 19 de maio de 2010 20:47
  • Sim, está tudo liberado. Me parece erro no WMI. Estou executando wmidiag.vbs e aparece alguns erros. vou postar a seguir.

    quarta-feira, 19 de maio de 2010 20:58
  • recriando o repositorio eu nunca vi uma estação que desse falha, da uma olhada nos logs do windows, as vezes pode ser problema com o windows installer tbm Att
    MCTS - SCCM
    quarta-feira, 19 de maio de 2010 21:18
  • ola,

    o firewall do windows esta habilitado na estação?

    o erro é muito parecido quando o firewall esta habilitado, o compartilhamento de arquivos esta habilitador mas o WMI remoto esta sendo bloqueado...

    se for isso, vc tem 2 formas:
    1- na estação com problema: netsh firewall set service remoteadmin enable
    2- via gpo
    - Crie ou edite uma GPO existente
    - Expanda Computer Settings, Administrative Templates, Network, Network Connections, Windows Firewall e Domain Profile
    - Edite Windows Firewall: Do not allow exceptions e selecione Disabled
    - Edite Windows Firewall: Allow remote administration exception, selecione Enabled e em Allow unsolicited incomming messages from coloque o endereço IP do servidor SCCM e do Management Point
    - Edite Windows Firewall: Allow file and printer sharing exceptions, selecione Enabled e em Allow unsolicited incomming messages from coloque o endereço IP do servidor SCCM e do Management Point
    - Aguarde os clientes atualizarem as políticas ou atualize manualmente usando o comando gpupdate /force

    espero ter ajudado,


    Raphael - MCP/MCSA Security/MCSE Security/MCTS/MCITP/MCT/MVP - http://www.dotnetwork.com.br
    • Marcado como Resposta SmartnetINFO quinta-feira, 20 de maio de 2010 20:06
    quinta-feira, 20 de maio de 2010 09:34
    Moderador
  • O firewall fica desabilitado por gpo.  Vou postar o resultado do wmidiag.vbs.
    quinta-feira, 20 de maio de 2010 18:36
  • o resultado é do report.txt é:

    19051 15:36:47 (0) ** WMIDiag v2.0 started on quinta-feira, 20 de maio de 2010 at 15:32.
    19052 15:36:47 (0) **
    19053 15:36:47 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
    19054 15:36:47 (0) **
    19055 15:36:47 (0) ** This script is not supported under any Microsoft standard support program or service.
    19056 15:36:47 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    19057 15:36:47 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    19058 15:36:47 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    19059 15:36:47 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    19060 15:36:47 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    19061 15:36:47 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    19062 15:36:47 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    19063 15:36:47 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    19064 15:36:47 (0) ** of the possibility of such damages.
    19065 15:36:47 (0) **
    19066 15:36:47 (0) **
    19067 15:36:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19068 15:36:47 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    19069 15:36:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19070 15:36:47 (0) **
    19071 15:36:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19072 15:36:47 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'COS\P90106' on computer 'COSF015404'.
    19073 15:36:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19074 15:36:47 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
    19075 15:36:47 (0) ** INFO: => 3 incorrect shutdown(s) detected on:
    19076 15:36:47 (0) **          - Shutdown on 12 March 2010 20:44:40 (GMT+3).
    19077 15:36:47 (0) **          - Shutdown on 25 March 2010 07:10:54 (GMT+3).
    19078 15:36:47 (0) **          - Shutdown on 29 April 2010 08:28:40 (GMT+3).
    19079 15:36:47 (0) **
    19080 15:36:47 (0) ** System drive: ....................................................................................................... C: (Disco 0 partição 0).
    19081 15:36:47 (0) ** Drive type: ......................................................................................................... IDE (SAMSUNG HD161HJ).
    19082 15:36:47 (0) ** There are no missing WMI system files: .............................................................................. OK.
    19083 15:36:47 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    19084 15:36:47 (0) ** WMI repository state: ............................................................................................... N/A.
    19085 15:36:47 (0) ** BEFORE running WMIDiag:
    19086 15:36:47 (0) ** The WMI repository has a size of: ................................................................................... 24 MB.
    19087 15:36:47 (0) ** - Disk free space on 'C:': .......................................................................................... 41433 MB.
    19088 15:36:47 (0) **   - INDEX.BTR,                     1507328 bytes,      20/5/2010 15:32:40
    19089 15:36:47 (0) **   - INDEX.MAP,                     760 bytes,          20/5/2010 15:32:40
    19090 15:36:47 (0) **   - OBJECTS.DATA,                  23281664 bytes,     20/5/2010 15:32:40
    19091 15:36:47 (0) **   - OBJECTS.MAP,                   11392 bytes,        20/5/2010 15:32:40
    19092 15:36:47 (0) ** AFTER running WMIDiag:
    19093 15:36:47 (0) ** The WMI repository has a size of: ................................................................................... 24 MB.
    19094 15:36:47 (0) ** - Disk free space on 'C:': .......................................................................................... 41431 MB.
    19095 15:36:47 (0) **   - INDEX.BTR,                     1507328 bytes,      20/5/2010 15:32:40
    19096 15:36:47 (0) **   - INDEX.MAP,                     760 bytes,          20/5/2010 15:32:40
    19097 15:36:47 (0) **   - OBJECTS.DATA,                  23281664 bytes,     20/5/2010 15:32:40
    19098 15:36:47 (0) **   - OBJECTS.MAP,                   11392 bytes,        20/5/2010 15:32:40
    19099 15:36:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19100 15:36:47 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
    19101 15:36:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19102 15:36:47 (0) ** DCOM Status: ........................................................................................................ OK.
    19103 15:36:47 (0) ** WMI registry setup: ................................................................................................. OK.
    19104 15:36:47 (0) ** WMI Service has no dependents: ...................................................................................... OK.
    19105 15:36:47 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    19106 15:36:47 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    19107 15:36:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19108 15:36:47 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    19109 15:36:47 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
    19110 15:36:47 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
    19111 15:36:47 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
    19112 15:36:47 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
    19113 15:36:47 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
    19114 15:36:47 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
    19115 15:36:47 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
    19116 15:36:47 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
    19117 15:36:47 (0) **    fail depending on the operation requested.
    19118 15:36:47 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
    19119 15:36:47 (0) **
    19120 15:36:47 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    19121 15:36:47 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    19122 15:36:47 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    19123 15:36:47 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    19124 15:36:47 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    19125 15:36:47 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19126 15:36:48 (0) ** Overall DCOM security status: ....................................................................................... OK.
    19127 15:36:48 (0) ** Overall WMI security status: ........................................................................................ OK.
    19128 15:36:48 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    19129 15:36:48 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
    19130 15:36:48 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
    19131 15:36:48 (0) **   'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
    19132 15:36:48 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    19133 15:36:48 (0) **   'select * from MSFT_SCMEventLogEvent'
    19134 15:36:48 (0) **
    19135 15:36:48 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    19136 15:36:48 (0) ** WMI ADAP status: .................................................................................................... OK.
    19137 15:36:48 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
    19138 15:36:48 (0) ** - ROOT/SERVICEMODEL.
    19139 15:36:48 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    19140 15:36:48 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    19141 15:36:48 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    19142 15:36:48 (0) **    i.e. 'WMIC.EXE /NODE:"COSF015404" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    19143 15:36:48 (0) **
    19144 15:36:48 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    19145 15:36:48 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    19146 15:36:48 (0) ** WMI GET operations: ................................................................................................. OK.
    19147 15:36:48 (0) ** WMI MOF representations: ............................................................................................ OK.
    19148 15:36:48 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    19149 15:36:48 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    19150 15:36:48 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    19151 15:36:48 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    19152 15:36:48 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    19153 15:36:48 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    19154 15:36:48 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    19155 15:36:48 (0) ** WMI static instances retrieved: ..................................................................................... 984.
    19156 15:36:48 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    19157 15:36:48 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
    19158 15:36:48 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19159 15:36:48 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    19160 15:36:48 (0) **   DCOM: ............................................................................................................. 0.
    19161 15:36:48 (0) **   WINMGMT: .......................................................................................................... 45.
    19162 15:36:48 (0) **   WMIADAPTER: ....................................................................................................... 0.
    19163 15:36:48 (0) ** => Verify the WMIDiag LOG at line #18607 for more details.
    19164 15:36:48 (0) **
    19165 15:36:48 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    19166 15:36:48 (0) **   DCOM: ............................................................................................................. 0.
    19167 15:36:48 (0) **   WINMGMT: .......................................................................................................... 0.
    19168 15:36:48 (0) **   WMIADAPTER: ....................................................................................................... 0.
    19169 15:36:48 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19170 15:36:48 (0) ** WMI Registry key setup: ............................................................................................. OK.
    19171 15:36:48 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19172 15:36:48 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19173 15:36:48 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19174 15:36:48 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19175 15:36:48 (0) **
    19176 15:36:48 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19177 15:36:48 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    19178 15:36:48 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    19179 15:36:48 (0) **
    19180 15:36:48 (0) ** WARNING: WMIDiag determined that WMI works CORRECTLY.  HOWEVER, some issues were detected.  Check 'C:\DOCUMENTS AND SETTINGS\P90106\CONFIGURAÇÕES LOCAIS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_COSF015404_2010.05.20_15.32.50.LOG' for details.
    19181 15:36:48 (0) **
    19182 15:36:48 (0) ** WMIDiag v2.0 ended on quinta-feira, 20 de maio de 2010 at 15:36 (W:78 E:12 S:2).

    Sendo que as dlls acima que falam pra registrar eu já registrei, porém parece q não adiantou.

     

    quinta-feira, 20 de maio de 2010 18:42
  • Descobri o problema. Liberação de portas no firewall linux que temos entre as redes.

    • Marcado como Resposta SmartnetINFO quinta-feira, 20 de maio de 2010 20:06
    quinta-feira, 20 de maio de 2010 20:06
  • Eu avisei hehehehe mas que bom que voce resolveu
    MCTS - SCCM
    quinta-feira, 20 de maio de 2010 20:25
  • hehehehe. Thanks.
    quinta-feira, 20 de maio de 2010 20:26
  • Ola Gislaine

     

    Quais portas você liberou no firewall ? Desculpe minha ignorancia.....

    segunda-feira, 14 de junho de 2010 19:30
  • ola,

    se vc esta falando do cliente, vc tem que liberar a porta RCP TCP 135, ao compartilhamento de arquivos e wmi remoto. O wmi remoto vc pode fazer tanto via gpo quando via netsh

    mais info
    http://blog.dotnetwork.com.br/?p=158

    para uma lista completa das portas usadas pelo sccm da 1 olhada
    http://technet.microsoft.com/en-us/library/bb632618.aspx

    espero ter ajudado,
    Raphael - MCP/MCSA Security/MCSE Security/MCTS/MCITP/MCT/MVP - http://www.dotnetwork.com.br
    segunda-feira, 14 de junho de 2010 19:34
    Moderador