Jump to content


MaceUK

Established Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MaceUK

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    United Kingdom
  1. The next step i wil ltry is to remove the client upgrade MSP's from the TS and let SCCM automatically upgrade the client via the scheduled task.
  2. Changing th MP to SMSMP hasbt helped at all. Clients are still reinstalling.
  3. ccmsetup-ccmeval.log contents... ==========[ ccmsetup started in process 1656 ]========== ccmsetup 10/06/2015 08:58:02 2144 (0x0860) Running on platform X64 ccmsetup 10/06/2015 08:58:02 2144 (0x0860) Updated security on object C:\WINDOWS\ccmsetup\cache\. ccmsetup 10/06/2015 08:58:02 2144 (0x0860) Launch from folder C:\WINDOWS\ccmsetup\cache\ ccmsetup 10/06/2015 08:58:02 2144 (0x0860) CcmSetup version: 5.0.7958.1401 ccmsetup 10/06/2015 08:58:02 2144 (0x0860) Running on 'Microsoft Windows 8.1 Enterprise' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 10/06/2015 08:58:02 2144 (0x0860) Ccmsetup command line: C:\WINDOWS\ccmsetup\cache\ccmsetup.exe /evaluate:prereqs ccmsetup 10/06/2015 08:58:02 2144 (0x0860) Loaded command line: "C:\WINDOWS\ccmsetup\cache\ccmsetup.exe" "/useronly" "/source:C:\_SMSTaskSequence\OSD\SHA00201" "/config:C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf" ccmsetup 10/06/2015 08:58:02 2144 (0x0860) Source folder C:\_SMSTaskSequence\OSD\SHA00201 is invalid. Skip it. ccmsetup 10/06/2015 08:58:02 2144 (0x0860) SslState value: 224 ccmsetup 10/06/2015 08:58:03 2144 (0x0860) Invalid argument 'MP:****************' in the config file. Ignore it. ccmsetup 10/06/2015 08:58:03 2144 (0x0860) CCMHTTPPORT: 80 ccmsetup 10/06/2015 08:58:03 2144 (0x0860) CCMHTTPSPORT: 443 ccmsetup 10/06/2015 08:58:03 2144 (0x0860) CCMHTTPSSTATE: 0 ccmsetup 10/06/2015 08:58:03 2144 (0x0860) CCMHTTPSCERTNAME: ccmsetup 10/06/2015 08:58:03 2144 (0x0860) FSP: ccmsetup 10/06/2015 08:58:03 2144 (0x0860) CCMFIRSTCERT: 1 ccmsetup 10/06/2015 08:58:03 2144 (0x0860) Client is set to use HTTPS when available. The current state is 224. ccmsetup 10/06/2015 08:58:03 2144 (0x0860) CCMCERTID: SMS;F95C448ABE4F92506FB2BF838EEA04DEC47DA9AF ccmsetup 10/06/2015 08:58:03 2144 (0x0860) Config file: C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 10/06/2015 08:58:03 2144 (0x0860) Retry time: 10 minute(s) ccmsetup 10/06/2015 08:58:03 2144 (0x0860) MSI log file: C:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 10/06/2015 08:58:03 2144 (0x0860) MSI properties: INSTALL="ALL" SMSCACHESIZE="10240" PATCH="C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2905002-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2938441-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2994331-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="SHA" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="1" CCMCERTID="SMS;F95C448ABE4F92506FB2BF838EEA04DEC47DA9AF" ccmsetup 10/06/2015 08:58:03 2144 (0x0860) Source List: ccmsetup 10/06/2015 08:58:03 2144 (0x0860) MPs: ccmsetup 10/06/2015 08:58:03 2144 (0x0860) None ccmsetup 10/06/2015 08:58:03 2144 (0x0860) Ccmsetup will run as an evaluation. ccmsetup 10/06/2015 08:58:03 2144 (0x0860) Found a local ccmsetup.cab. A new one will not be downloaded. ccmsetup 10/06/2015 08:58:03 2144 (0x0860) C:\WINDOWS\ccmsetup\cache\ccmsetup.cab is Microsoft trusted. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Successfully extracted manifest file C:\WINDOWS\ccmsetup\ccmsetup.xml from file C:\WINDOWS\ccmsetup\cache\ccmsetup.cab. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Loading manifest file: C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Successfully loaded ccmsetup manifest file. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/vcredist_x86.exe' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/vcredist_x64.exe' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/vc50727_x86.exe' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/vc50727_x64.exe' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/WindowsUpdateAgent30-x86.exe' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/WindowsUpdateAgent30-x64.exe' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/msxml6.msi' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/msxml6_x64.msi' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/msrdcoob_x86.exe' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/msrdcoob_amd64.exe' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'pkgmgr.exe' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'dism.exe' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'wimgapi.msi' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/MicrosoftPolicyPlatformSetup.msi' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/WindowsFirewallConfigurationProvider.msi' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/Silverlight.exe' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/wic_x86_enu.exe' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/wic_x64_enu.exe' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/dotNetFx40_Client_x86_x64.exe' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'SCEPInstall.exe' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'i386/client.msi' is not applicable. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Item 'x64/client.msi' is applicable. Add to the list. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Default CSP Type is 24 ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'i386/vcredist_x86.exe' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'i386/vcredist_x86.exe' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'x64/vcredist_x64.exe' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'x64/vcredist_x64.exe' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'x64/vc50727_x64.exe' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Upgrade code '{A8D19029-8E5C-4E22-8011-48070F9E796E}': product = '{ad8a2fa1-06e7-4b0d-927d-6e54b3d31028}', installed = 1, version = 8.0.61000 ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Checking '{A8D19029-8E5C-4E22-8011-48070F9E796E}' version '8.0.61000' expecting >= '8.0.61000'. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'x64/vc50727_x64.exe' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'x64/WindowsUpdateAgent30-x64.exe' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Checking file 'C:\WINDOWS\system32\wuapi.dll' version '7.9.9600.17415' expecting >= '7.4.7600.226'. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'x64/WindowsUpdateAgent30-x64.exe' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'x64/msxml6_x64.msi' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Checking file 'C:\WINDOWS\system32\msxml6.dll' version '6.30.9600.17415' expecting >= '6.10.1129.0'. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'x64/msxml6_x64.msi' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'dism.exe' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) File 'C:\WINDOWS\system32\msrdc.dll' exists. Discovery passed ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'dism.exe' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'x64/MicrosoftPolicyPlatformSetup.msi' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Upgrade code '{19B9818B-7432-49E9-BC02-B126025EE235}': product = '{90D295B8-BA08-487E-B904-0E624209A410}', installed = 1, version = 1.2.3602.0 ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Checking '{19B9818B-7432-49E9-BC02-B126025EE235}' version '1.2.3602.0' expecting >= '1.2.3602.0'. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'x64/MicrosoftPolicyPlatformSetup.msi' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'x64/WindowsFirewallConfigurationProvider.msi' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Validated file 'C:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi' hash '3BF0651FD4A01170925CEF694468D4EF6F64D76FD3413DEBD14CB8DE019AA10E' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) File 'C:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi' exists. Discovery passed ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'x64/WindowsFirewallConfigurationProvider.msi' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'i386/Silverlight.exe' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) 32-bit Hive selected ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'i386/Silverlight.exe' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'i386/dotNetFx40_Client_x86_x64.exe' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Detected item 'i386/dotNetFx40_Client_x86_x64.exe' ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Discovering whether item 'SCEPInstall.exe' exists. ccmsetup 10/06/2015 08:58:18 2144 (0x0860) Validated file 'C:\WINDOWS\ccmsetup\SCEPInstall.exe' hash '8B76E87A25DFAE06CC36245FCDC269D94A99CE2F1374C105A1F41B3470C2CFD7' ccmsetup 10/06/2015 08:58:19 2144 (0x0860) Checking file 'C:\WINDOWS\ccmsetup\SCEPInstall.exe' version '4.5.0216.0000' expecting >= '4.5.216.0'. ccmsetup 10/06/2015 08:58:19 2144 (0x0860) Detected item 'SCEPInstall.exe' ccmsetup 10/06/2015 08:58:19 2144 (0x0860) Discovering whether item 'x64/client.msi' exists. ccmsetup 10/06/2015 08:58:19 2144 (0x0860) Item x64/client.msi has not been installed yet. Put to pending install list. ccmsetup 10/06/2015 08:58:19 2144 (0x0860) CcmSetup is exiting with return code 0 ccmsetup 10/06/2015 08:58:19 2144 (0x0860) ==========[ ccmsetup started in process 4632 ]========== ccmsetup 10/06/2015 08:58:19 568 (0x0238) Running on platform X64 ccmsetup 10/06/2015 08:58:19 568 (0x0238) Updated security on object C:\WINDOWS\ccmsetup\cache\. ccmsetup 10/06/2015 08:58:19 568 (0x0238) Launch from folder C:\WINDOWS\ccmsetup\cache\ ccmsetup 10/06/2015 08:58:19 568 (0x0238) CcmSetup version: 5.0.7958.1401 ccmsetup 10/06/2015 08:58:19 568 (0x0238) Running on 'Microsoft Windows 8.1 Enterprise' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 10/06/2015 08:58:19 568 (0x0238) Ccmsetup command line: C:\WINDOWS\ccmsetup\cache\ccmsetup.exe /evaluate:client ccmsetup 10/06/2015 08:58:19 568 (0x0238) Loaded command line: "C:\WINDOWS\ccmsetup\cache\ccmsetup.exe" "/useronly" "/source:C:\_SMSTaskSequence\OSD\SHA00201" "/config:C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf" ccmsetup 10/06/2015 08:58:19 568 (0x0238) Source folder C:\_SMSTaskSequence\OSD\SHA00201 is invalid. Skip it. ccmsetup 10/06/2015 08:58:19 568 (0x0238) SslState value: 224 ccmsetup 10/06/2015 08:58:19 568 (0x0238) Invalid argument 'MP:*********************' in the config file. Ignore it. ccmsetup 10/06/2015 08:58:19 568 (0x0238) CCMHTTPPORT: 80 ccmsetup 10/06/2015 08:58:19 568 (0x0238) CCMHTTPSPORT: 443 ccmsetup 10/06/2015 08:58:19 568 (0x0238) CCMHTTPSSTATE: 0 ccmsetup 10/06/2015 08:58:19 568 (0x0238) CCMHTTPSCERTNAME: ccmsetup 10/06/2015 08:58:19 568 (0x0238) FSP: ccmsetup 10/06/2015 08:58:19 568 (0x0238) CCMFIRSTCERT: 1 ccmsetup 10/06/2015 08:58:19 568 (0x0238) Client is set to use HTTPS when available. The current state is 224. ccmsetup 10/06/2015 08:58:19 568 (0x0238) CCMCERTID: SMS;F95C448ABE4F92506FB2BF838EEA04DEC47DA9AF ccmsetup 10/06/2015 08:58:19 568 (0x0238) Config file: C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 10/06/2015 08:58:19 568 (0x0238) Retry time: 10 minute(s) ccmsetup 10/06/2015 08:58:19 568 (0x0238) MSI log file: C:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 10/06/2015 08:58:19 568 (0x0238) MSI properties: INSTALL="ALL" SMSCACHESIZE="10240" PATCH="C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2905002-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2938441-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2994331-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="SHA" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="1" CCMCERTID="SMS;F95C448ABE4F92506FB2BF838EEA04DEC47DA9AF" ccmsetup 10/06/2015 08:58:19 568 (0x0238) Source List: ccmsetup 10/06/2015 08:58:19 568 (0x0238) MPs: ccmsetup 10/06/2015 08:58:19 568 (0x0238) None ccmsetup 10/06/2015 08:58:19 568 (0x0238) Ccmsetup will run as an evaluation. ccmsetup 10/06/2015 08:58:19 568 (0x0238) CcmSetup is exiting with return code 0 ccmsetup 10/06/2015 08:58:19 568 (0x0238) ==========[ ccmsetup started in process 4192 ]========== ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Running on platform X64 ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Updated security on object C:\WINDOWS\ccmsetup\cache\. ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Launch from folder C:\WINDOWS\ccmsetup\cache\ ccmsetup 10/06/2015 09:15:04 5892 (0x1704) CcmSetup version: 5.0.7958.1401 ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Running on 'Microsoft Windows 8.1 Enterprise' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Ccmsetup command line: C:\WINDOWS\ccmsetup\cache\ccmsetup.exe /evaluate:prereqs ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Loaded command line: "C:\WINDOWS\ccmsetup\cache\ccmsetup.exe" "/useronly" "/source:C:\_SMSTaskSequence\OSD\SHA00201" "/config:C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf" ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Source folder C:\_SMSTaskSequence\OSD\SHA00201 is invalid. Skip it. ccmsetup 10/06/2015 09:15:04 5892 (0x1704) SslState value: 224 ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Invalid argument 'MP:SCCMDP-SC1.***********' in the config file. Ignore it. ccmsetup 10/06/2015 09:15:04 5892 (0x1704) CCMHTTPPORT: 80 ccmsetup 10/06/2015 09:15:04 5892 (0x1704) CCMHTTPSPORT: 443 ccmsetup 10/06/2015 09:15:04 5892 (0x1704) CCMHTTPSSTATE: 0 ccmsetup 10/06/2015 09:15:04 5892 (0x1704) CCMHTTPSCERTNAME: ccmsetup 10/06/2015 09:15:04 5892 (0x1704) FSP: ccmsetup 10/06/2015 09:15:04 5892 (0x1704) CCMFIRSTCERT: 1 ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Client is set to use HTTPS when available. The current state is 224. ccmsetup 10/06/2015 09:15:04 5892 (0x1704) CCMCERTID: SMS;F95C448ABE4F92506FB2BF838EEA04DEC47DA9AF ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Config file: C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Retry time: 10 minute(s) ccmsetup 10/06/2015 09:15:04 5892 (0x1704) MSI log file: C:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 10/06/2015 09:15:04 5892 (0x1704) MSI properties: INSTALL="ALL" SMSCACHESIZE="10240" PATCH="C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2905002-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2938441-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP;C:\WINDOWS\CCMHOTFIXES\CONFIGMGR2012AC-R2-KB2994331-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="SHA" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="1" CCMCERTID="SMS;F95C448ABE4F92506FB2BF838EEA04DEC47DA9AF" ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Source List: ccmsetup 10/06/2015 09:15:04 5892 (0x1704) MPs: ccmsetup 10/06/2015 09:15:04 5892 (0x1704) None ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Ccmsetup will run as an evaluation. ccmsetup 10/06/2015 09:15:04 5892 (0x1704) Found a local ccmsetup.cab. A new one will not be downloaded. ccmsetup 10/06/2015 09:15:04 5892 (0x1704) C:\WINDOWS\ccmsetup\cache\ccmsetup.cab is Microsoft trusted. ccmsetup 10/06/2015 09:15:19 5892 (0x1704) Successfully extracted manifest file C:\WINDOWS\ccmsetup\ccmsetup.xml from file C:\WINDOWS\ccmsetup\cache\ccmsetup.cab. ccmsetup 10/06/2015 09:15:19 5892 (0x1704) Loading manifest file: C:\WINDOWS\cc The only error i see is that highlighted in Red. I have made the change in the TS to not use MP but SMSMP instead. Hopefully this will clear that message and cure my problem.
  4. Thanks for the reply Peter, When i deploy the client in the TS i am patching that client with the following... configmgr2012ac-r2-kb2905002-x64.msp configmgr2012ac-r2-kb2938441-x64.msp configmgr2012ac-r2-kb2970177-x64.msp configmgr2012ac-r2-kb2994331-x64.msp Are you saying this shouldn't be done? Lee
  5. Im experiencing an issue with our OSD newly deployed SCCM clients and although it appears all ok, after a day the user will contact the Service Desk and complain that the Software Centre shortcut has disappeared. When investigating it appears the client is stuck in a loop reinstalling the client and then failing. Has anyone else expereinces this at all? The SCCM Site server is currently on SCCM 2012 R2 CU4. Any existing clients out there are ok, it appears just with the newly deployed clients. Any help would be greatly appreciated... Im just testing if i include the following it may help in the Client install step... MP:SCCMDP****.----------.org.uk SMSCACHESIZE=10240 PATCH="C:\windows\CCMHotfixes\configmgr2012ac-r2-kb2905002-x64.msp";"C:\windows\CCMHotfixes\configmgr2012ac-r2-kb2938441-x64.msp";"C:\windows\CCMHotfixes\configmgr2012ac-r2-kb2970177-x64.msp";"C:\windows\CCMHotfixes\configmgr2012ac-r2-kb2994331-x64.msp" There is a step before hand copying across the relevant msp's to C:\windows\CCMHotfixes. Ill feed back if this helps...
  6. Hi Wondering is anyone can help. I have SCCM 2012 R2 running on Windows Server 2008 R2, and my WSUS server is running on Windows Server 2012 R2. My wsus has been integrated and was working fine. However in the last week i can now see this message appearing in my WCM log ... PublishApplication(8427071A-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match. Agreed they don't match but this was working previously and the servers were syncing successfully. Has anyone else had this issue or knows of a fix. Would be really appreciated. Here is my full WCM log File... Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40) Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40) Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40) Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40) Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40) Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40) Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40) No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40) WSUS Server configuration has been updated. Updating Group Info. SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40) Updating Group Info for WSUS. SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40) Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40) Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40) Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40) Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:46 6720 (0x1A40) Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:51 6720 (0x1A40) Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:51 6720 (0x1A40) Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:52 6720 (0x1A40) Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:52 6720 (0x1A40) Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40) Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40) PublishApplication(8427071A-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.~~ at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String sdpFile)~~ at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40) ERROR: Failed to publish sms client to WSUS, error = 0x80131509 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40) STATMSG: ID=6613 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCMSVR.sovereign.org.uk SITE=SHA PID=4304 TID=6720 GMTDATE=Wed Jan 07 09:23:53.245 2015 ISTR0="8427071A-DA80-48C3-97DE-C9C528F73A2D" ISTR1="5.00.7958.1000" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40) Failed to publish client with error = 0x80131509 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40) completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40) HandleSMSClientPublication failed. SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40) Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
  7. Really not one person can assist? Bugger!
  8. Hi We are currently running through a WIndows 7 deployment and we want all the new Windows 7 clients to use a new 2012 WSUS server. Currently all our existing clients are pointing to the old WSUS server, the new WSUS server has been setup and partnered with SCCM. SCCM sees this WSUS server and is happily pulling down updates from MS. As i move people to Windows 7 i want them to use the new WSUS server so as far as i can remember from the SCCM 2012 Course, there are 3 fundamental requirements for this to work. 1, SCCM Client set to enable software Updates. 2. Software Update-Based Client Installation enabled for the site. 3. A GP is in place pointing to the new WSUS server None of these settings are currently enabled so they are all updating from the current GP setting of the old WSUS server. If i wish to approach this is a phased approach and only allow the new Windows 7 boxes to see the new WSUS server I would need to apply a new updated GP to the new Machines, enable the customised SCCM client profile setting to accept software updates and link it to the correct collection. If i enable Software Update-Based Client Installation enabled for the site, this is going to enable this on all clients and an update will be installed on all clients to enable this funtion. When i do this is this going to mess up our current patching solution which is only through WSUS (NO SCCM)? Am i right in thinking as long as the old GP setting is still there they will continue to get patched via WSUS and not SCCM. With the Windows 7 machines, a new GP would be targeted at them, as well as a customised SCCM Client profile to enable updates so they should then start getting patched via SCCM. Has anyone gone through a similar problem? Many tahnsk for your time
  9. Hi Im having a few issues with changing the name of an existing machine of SCCM during the OS deployment. Our current OS deployment is fully automated and setup quite intelligently. Any unknown devices are prompted via the OSDComputerName variable. Any existing machine known to SCCM we want to change the Computer name from the old to the new convention... Old: SHG-ASSET-LOCATION New: LOCATION-ASSET-HARDWARE At present we run the MDT gather step, this can then query the default gateway (DefaultGateway001) for its location and also utilise the IsLaptop/IsDesktop variable for hardware (LA/PC). The problem we are having is trying to pull the numerical part of the old name in to the new. Every old name has a numerical part for the asset tag. If you review the OSDComputerName variable in the BDD.log or the SMSTS.log it shows correctly the SCCM Client Name. If you run a VB script after the gather step while in support mode (F8) and echo the OSDComputerName variable it appears as blank. However if you echo another variable such as HostName it appears correctly. Am i missing something? Any help would be greatly appreciated especially as this is the last step to make our TS a fully automated process for old and new machines. The end result is to get everyone on to Windows 7 with the omputer name changed, and the computer account moved in to a new OU structure. I have completed all the other necessary tasks to make this possible but struggling on this last step. HELP!
×
×
  • Create New...