Resources for IT Professionals > Página Inicial dos Fóruns > Configuration Manager General > How to handle computer where the client is not installing?
Fazer uma PerguntaFazer uma Pergunta
 

RespondidoHow to handle computer where the client is not installing?

  • domingo, 22 de novembro de 2009 1:29Shrek46 Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    We have about 1700 workstations and servers. The report shows about 400 non-clients with failed installation. Randomly looking at ccmsetup.log, reasons vary from missing SP4 on 2000, to all kinds of issues like permissions issues, MSI installer version etc.
    Short of writing a script to collect the logs, mine and analyze the failure reason, what other option do we have?
    BTW, we deployed Office 2007 this weekend to 500 computers with installed clients, and had close to  98% success rate. Life is good!
    Once again, thanks for all the tremendous help provided here, this forum rocks!

Respostas

  • quarta-feira, 25 de novembro de 2009 2:26John MarcumMVP, ModeradorMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     Respondido
    I think saying that the FSP is mostly for native mode misleading. It's quite helpful for mixed mode too. I use it all the time. Between the fsp and ccm.log you should be able to find why those clients are not installed.




    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    • Marcado como RespostaShrek46 quarta-feira, 25 de novembro de 2009 15:07
    •  

Todas as Respostas

  • domingo, 22 de novembro de 2009 2:25Matt Tinney Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    Do you have an FSP installed and configured in your environment? The FSP should be able to help you identify the installation and communication (mostly for native mode) issues for failed clients.

    Where are you having the MSI Installer version issues? Windows 2000 SP4?

    Matthew Tinney mtinney@windowsmanagementexperts.com www.windowsmanagementexperts.com (206) 778 4432 http://www.linkedin.com/pub/3/b81/371
  • domingo, 22 de novembro de 2009 7:42Shrek46 Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    We run in mixed more. Yes we have some servers running 2000 SP3 which we know that are incompatible, but also see other problems on the clients.
  • quarta-feira, 25 de novembro de 2009 2:26John MarcumMVP, ModeradorMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     Respondido
    I think saying that the FSP is mostly for native mode misleading. It's quite helpful for mixed mode too. I use it all the time. Between the fsp and ccm.log you should be able to find why those clients are not installed.




    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    • Marcado como RespostaShrek46 quarta-feira, 25 de novembro de 2009 15:07
    •  
  • quarta-feira, 25 de novembro de 2009 19:39Matt Tinney Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     

    Hi John,
    Ok. I got what you have to say.   

    To clarify my statement "mostly for native mode". The FSP is relevant for both native and mixed mode sites. However, what I was stating is that the FSP provides state messages for native mode communication issuses specifically (as does mixed mode) in terms of identifying problems with client to MP communication issues relating to client certificates (valid), certificate selection if more then one client cert is located in the certificate store, expiration of server certificate, etc. 

    Thanks for posting.
    -Matt


    Matthew Tinney mtinney@windowsmanagementexperts.com www.windowsmanagementexperts.com (206) 778 4432