SCCM R3 Clients not installing.
Hi there...Can you please help me in this post. I am trying to install SCCM R3 client to client systems. SCCM R3 is in the Server 10.x.2.x network and client systems (in which I am trying install SCCM R3 client) is in 10.x.7.x network. After checking the Technet KB, I opened the following ports(from this website - http://technet.microsoft.com/en-us/library/bb694088.aspx) Port Numbers are - 1. File and Printer Sharing - 445, 2. Windows Management Instrumentation (WMI), 3. TCP port 2701, 4. TCP port 2702, 5. TCP port 135 6. TCP port 3389 except - statview.exe. Do I need to open anyother port numbers apart from those mentioned above & do I have to unblock statview.exe (in the Firewall))-if so whats the port number I can use for that or I can just unblock as application. Can you pls let me know regarding this or an other ways to find why SCCM R3 clients are not installing.VT
February 13th, 2012 5:40pm

Are you positive that blocked ports are preventing the clients from installing? The first log you should be checking is CCM.log, located in your ConfigMgr install location, in a directory called logs. It will detail the attempts to push out clients. There can be many causes for clients not installing.. how are the clients appearing in the Collection view? Is a Site Code listed? Cheers.LinkedIn
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2012 5:45pm

Hi Adrian...thanks for your response....Yes I can see the site code in the SCCM console & under the COmputer Management --> All Desktop and Servers (the site code that one that I have set up). Here are the logs I got for that system...pls let me know whats causing that not to install. Received request: "STK0033068_DOMAIN_COM" for machine name: "STK0033068" on queue: "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.386 2012 Canada Central Standard Time><thread=5560 (0x15B8)> Stored request "STK0033068_DOMAIN_COM", machine name "STK0033068", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.386 2012 Canada Central Standard Time><thread=5560 (0x15B8)> WARNING: A request for machine 'STK0033068' is already being processed. This CCR will be saved back to the retry queue $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.386 2012 Canada Central Standard Time><thread=5560 (0x15B8)> Failed to submit request for processing (1003) $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.386 2012 Canada Central Standard Time><thread=5560 (0x15B8)> Stored request "STK0033068_DOMAIN_COM", machine name "STK0033068", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.386 2012 Canada Central Standard Time><thread=5560 (0x15B8)> Getting a new request from queue "Retry" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.386 2012 Canada Central Standard Time><thread=5560 (0x15B8)> Found CCR "STK0033068_DOMAIN_com.DOMAIN.CCR" in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.386 2012 Canada Central Standard Time><thread=5560 (0x15B8)> Received request: "STK0033068_DOMAIN_COM.DOMAIN" for machine name: "STK0033068" on queue: "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.511 2012 Canada Central Standard Time><thread=5560 (0x15B8)> Stored request "FPZQUDRV", machine name "STK0033068", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.511 2012 Canada Central Standard Time><thread=5560 (0x15B8)> WARNING: A request for machine 'STK0033068' is already being processed. This CCR will be saved back to the retry queue $$<SMS_CLIENT_CONFIG_MANAGER><Mon Feb 13 16:53:06.511 2012 Canada Central Standard Time><thread=5560 (0x15B8)> VT
February 13th, 2012 6:15pm

So that log file looks as if CCR's are being processed. On the PC you are targetting, can you show me some of the ccmsetup.log located in root:\windows\system32\ccmsetup Cheers.LinkedIn
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2012 8:01pm

I couldnt find the ccmsetup.log in the target computer. And also searched for it in the C: drive...any solutions, pls let me know. Also couldnt find any client PC log files mentioned in the link - http://technet.microsoft.com/en-us/library/bb892800.aspx But in the SCCM Server, I found this log (ccmsetup)...let me know if that helps, but I couldnt find any entry after 02-05-2012. <![LOG[MSI: Action 0:02:10: InstallServices. Installing new services]LOG]!><time="00:02:10.176+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:10: WriteEnvironmentStrings. Updating environment strings]LOG]!><time="00:02:10.192+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:10: CcmSetServiceConfig. Configuring service]LOG]!><time="00:02:10.192+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:10: SmsMigrateInventory. Migrating SMS Legacy Client inventory settings]LOG]!><time="00:02:10.254+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:10: CcmConfigDCOM. Configuring service]LOG]!><time="00:02:10.316+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:10: SmsShellNotify. Setting SMS configuration]LOG]!><time="00:02:10.379+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:10: CcmInitializePolicy. Initializing policy]LOG]!><time="00:02:10.441+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:11: SmsSetClientConfig. Setting SMS configuration]LOG]!><time="00:02:11.876+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:11: CcmMigrateDownloadSchema. ]LOG]!><time="00:02:11.954+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:12: CcmRegisterProduct. Registering product]LOG]!><time="00:02:12.017+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:12: CcmRegisterProductRollback. Registering product]LOG]!><time="00:02:12.079+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:12: SmsInstallPrepDrvr. Installing Software Metering PREP Driver]LOG]!><time="00:02:12.095+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:12: StartServices. Starting services]LOG]!><time="00:02:12.157+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:13: CcmStartService. ]LOG]!><time="00:02:13.202+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:13: SmsCleanupDesktopMigrationInfo. Deinstalling the SMS Legacy Client or SMS 2.0 Client]LOG]!><time="00:02:13.249+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:44: SmsClientInstallSucceeded. Sending status message]LOG]!><time="00:02:44.746+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:44: RollbackCleanup. Removing backup files]LOG]!><time="00:02:44.964+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[MSI: Action 0:02:45: RemoveExistingProducts. Removing applications]LOG]!><time="00:02:45.167+000" date="02-05-2012" component="ccmsetup" context="" type="0" thread="8376" file="msiutil.cpp:374"> <![LOG[Installation succeeded.]LOG]!><time="00:02:45.260+000" date="02-05-2012" component="ccmsetup" context="" type="1" thread="8376" file="msiutil.cpp:890"> <![LOG[Successfully deleted the ccmsetup service]LOG]!><time="00:02:50.268+000" date="02-05-2012" component="ccmsetup" context="" type="1" thread="8376" file="ccmsetup.cpp:3592"> <![LOG[A Fallback Status Point has not been specified. Message with STATEID='400' will not be sent.]LOG]!><time="00:02:50.268+000" date="02-05-2012" component="ccmsetup" context="" type="1" thread="8376" file="ccmsetup.cpp:9330"> <![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.cab]LOG]!><time="00:02:50.268+000" date="02-05-2012" component="ccmsetup" context="" type="1" thread="5580" file="ccmsetup.cpp:9069"> <![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.xml]LOG]!><time="00:02:50.268+000" date="02-05-2012" component="ccmsetup" context="" type="1" thread="5580" file="ccmsetup.cpp:9069"> <![LOG[Deleted file C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe]LOG]!><time="00:02:50.268+000" date="02-05-2012" component="ccmsetup" context="" type="1" thread="5580" file="ccmsetup.cpp:9069"> <![LOG[Deleted file C:\Windows\ccmsetup\client.msi]LOG]!><time="00:02:50.268+000" date="02-05-2012" component="ccmsetup" context="" type="1" thread="5580" file="ccmsetup.cpp:9069"> VT
February 13th, 2012 8:38pm

That log seems to indicate a successful client installation. Have you checked that client for a ccmexec.exe process running? LinkedIn
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2012 8:55pm

Yes I can see CCMEXE.EXE*32 is running in the server and not in the client PC....VT
February 13th, 2012 10:32pm

Right. How are you installing the client? LinkedIn
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2012 11:15pm

The client is installing just fine, the problem is the assignment process. Look at the clientidstartupmanager.log and the clientlocation.log (both on the client). If you find any errors, please post them in your reply.Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund
February 14th, 2012 12:58am

@ Adrian - I am installing client from the SCCM console --> Computer Mgmt --> Collections --> System # --> Install Client Thanks Kent...I could not find clientstartupmanager.log & clientlocation.log in the client systems (on the PC in which I am trying to install SCCM client). But in the SCCM Server I can find clientlocation.log and didnt find any errors...got few entries from the SCCM Server (clientlocation.log)....Pls let me know.... <![LOG[GetCurrentManagementPointEx]LOG]!><time="07:11:17.244+000" date="02-14-2012" component="ClientLocation" context="" type="1" thread="13932" file="smsclientclass.cpp:1039"> <![LOG[Current Management Point is SCCMServer.DOMAIN.COM with version 6487 and capabilities: <Capabilities SchemaVersion="1.0"> </Capabilities>.]LOG]!><time="07:11:17.260+000" date="02-14-2012" component="ClientLocation" context="" type="1" thread="13932" file="smsclientclass.cpp:1094"> <![LOG[GetCurrentManagementPointEx]LOG]!><time="08:03:21.472+000" date="02-14-2012" component="ClientLocation" context="" type="1" thread="12608" file="smsclientclass.cpp:1039"> <![LOG[Current Management Point is SCCMServer.DOMAIN.COM with version 6487 and capabilities: <Capabilities SchemaVersion="1.0"> </Capabilities>.]LOG]!><time="08:03:21.488+000" date="02-14-2012" component="ClientLocation" context="" type="1" thread="12608" file="smsclientclass.cpp:1094"> VT
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 9:18am

See ccm.log on the server if the push installation succeeded at all.Torsten Meringer | http://www.mssccmfaq.de
February 14th, 2012 9:24am

Thanks Torsten...I think this log might help... ---> Unable to connect to WMI on remote machine "STK0033068", error = 0x800706ba. $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 14 08:03:15.513 2012 Canada Central Standard Time><thread=10496 (0x2900)> ---> Deleting SMS Client Install Lock File '\\10.x.7.x\admin$\SMSClientInstall.STK'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 14 08:03:15.513 2012 Canada Central Standard Time><thread=10496 (0x2900)> Retry request id for "6KL0R1EK" set to "10_225_7_240.DOMAIN" $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 14 08:03:15.513 2012 Canada Central Standard Time><thread=10496 (0x2900)> Stored request "10_x_7_x.DOMAIN", machine name "STK0033068", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 14 08:03:15.513 2012 Canada Central Standard Time><thread=10496 (0x2900)> <======End request: "10_x_7_x.DOMAIN", machine name: "STK0033068". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 14 08:03:15.528 2012 Canada Central Standard Time><thread=10496 (0x2900)> Pls let me know if this realted to port issue or any other issue. But as I have mentioned in the post above...I am able to install SCCM client on the client or server in the same subnet.... VT
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 9:55am

That errors translates to RPC_S_SERVER_UNAVAILABLE. Double check if there are any firewalls between the server and the clients.Torsten Meringer | http://www.mssccmfaq.de
February 14th, 2012 10:31am

Yes there is a firewall between client PC and SCCM server. Do I have open any ports?? pls let me knwVT
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 10:54am

I was trying to follow this link - http://sms-hints-tricks.blogspot.com/2007/04/fixing-wmi-errors-in-your-repository.html after running WMIDIAG script file in the client PC, got this report below - DCOM Status: ................................ OK. WMI registry setup: ............................ OK. WMI Service has dependents: ................. 2 Services. 38497 10:30:54 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)! 38498 10:30:54 (0) ** - Security Center (WSCSVC, StartMode='Automatic') 38499 10:30:54 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled') 38500 10:30:54 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well. 38501 10:30:54 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but 38502 10:30:54 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped, 38503 10:30:54 (0) ** this can prevent the service/application to work as expected. RPCSS service: ................................. OK (Already started). WINMGMT service: ............................... OK (Already started). -------------------------- WMI service DCOM setup: ........................ OK. WMI components DCOM registrations: ............. OK. WMI ProgID registrations: ...................... OK. WMI provider DCOM registrations: ............... OK. WMI provider CIM registrations missing for the following provider (s): ................1 WARNING (S)! 38512 10:30:54 (2) !! WARNING: WMI provider CIM registrations missing for the following provider(s): ...................................... 1 WARNING(S)! 38513 10:30:54 (0) ** - ROOT/WMI, Provider_BIOSInterface (i.e. WMI Class 'HPBIOS_BIOSEvent') 38514 10:30:54 (0) ** MOF Registration: '' 38515 10:30:54 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers 38516 10:30:54 (0) ** while the CIM registration is wrong or missing. This can be due to: 38517 10:30:54 (0) ** - a de-installation of the software. 38518 10:30:54 (0) ** - a deletion of some CIM registration information. 38519 10:30:54 (0) ** => You can correct the CIM configuration by: 38520 10:30:54 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command. 38521 10:30:54 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag. 38522 10:30:54 (0) ** (This list can be built on a similar and working WMI Windows installation) 38523 10:30:54 (0) ** The following command line must be used: 38524 10:30:54 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider' 38525 10:30:54 (0) ** - Re-installing the software. 38526 10:30:54 (0) ** => If the software has been de-installed intentionally, then this information must be 38527 10:30:54 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove the provider 38528 10:30:54 (0) ** registration data and its set of associated classes. 38529 10:30:54 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\WMI path __Win32Provider Where Name='Provider_BIOSInterface' DELETE' 38530 10:30:54 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\WMI Class HPBIOS_BIOSEvent DELETE' 38531 10:30:54 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software, 38532 10:30:54 (0) ** the namespace and ALL its content can be ENTIRELY deleted. 38533 10:30:54 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='WMI' DELETE' WMI provider CLSIDs: ........................... OK. WMI providers EXE/DLL availability: ............ OK. Any Clue...pls let me know..VT
February 14th, 2012 12:07pm

To me, it looks like a firewall is preventing the ConfigMgr server from connecting to the WMI service on the client. Is it a Windows 7 Client? Are you using the inbuilt Firewall? Or is it something else entirely? Cheers.LinkedIn
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 5:04pm

Yes its Windows 7 OS. Built in Firewall is been disabled. But there is a firewall in between the 10.x.7.x and 10.x.2.x network.VT
February 14th, 2012 5:19pm

Are the following ports open bidirectionally on that firewall? 80 (TCP) 8530 (TCP) 2701-2704 (UDP-TCP) 3389 (TCP) 9 (UDP) 139 (UPD - TCP) 135 (UDP-TCP) 445 (TCP) 137 (UDP) Cheers.LinkedIn
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 5:49pm

I followed this article in http://technet.microsoft.com/en-us/library/bb694088.aspx)& opened the following ports mentioned below... I am sure I am missing few of them from what you have mentioned above...will do that and will try....Do you have any idea if I need to allow stateview.exe as program right ? Port Numbers are - 1. File and Printer Sharing - 445, 2. Windows Management Instrumentation (WMI), 3. TCP port 2701, 4. TCP port 2702, 5. TCP port 135 6. TCP port 3389 except - statview.exe. VT
February 14th, 2012 5:53pm

Try and see how you go. I dont think you will need to allow statview.exe It's definitely the firewall between networks giving you these issues. Cheers.LinkedIn
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 6:02pm

Thanks Adrian...will keep you all posted...VT
February 14th, 2012 6:03pm

Thanks Torsten and Adrian its a Firewall issue, opened necessary ports that Adrian gave and few others as well worked fine.VT
Free Windows Admin Tool Kit Click here and download it now
February 20th, 2012 2:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics