locked
System Center 2012 Configuration Manager upgrade and windows 7 clients RRS feed

  • Question

  • I'm migrating a  config mgr 2012 install to the same sub-net as a 2007 config mgr existing install. I'm having problems,  I think I have overlapping boundaries.  2007 has one boundary , an AD group which has all ip ranges included.  In order to migrate these boundaries to 2012, the preferred procedure is to migrate one sub-net at a time and test, but with one boundary on 2007 its almost impossible to get this going without migrating the whole site at once.

    1. In order to do the migration should i break up 2007 boundaries into similar sub-nets to match 2012 ip sub-nets that were created in discovery? Or just migrate the machines and hope it works! ( i know that is wrong)

    Next  Migrations Questions:

    I have config mgr client (2012) on 6 servers running win server 2008 in the above scenario with sccm 2012 running side by side. These serves found my new config mgr because I disabled the GP policy forcing them to go to sccm 2007 site code however all windows 7 clients can not be installed. 

    I cant push the 2012 client or load the client from the sms_111 share from my sccm 2012 install to any windows 7 clients. The ccmsetup process is running but times out. On some of my win 7 clients, in ctr panel in the configuration manager  there is no site  configured, and it cant fine either site, new site 111 or old site TIC? I used the ccmclean.exe to clean the machines of old entries. I tried disabling UAC, Firewall.

    On the Win 7 machines when I click find mgmt server and put in code 111 ( new site) I get a 666 entry?  I scoured dns and wins and AD for a rouge 666 entry, I found one in dns and deleted the entry.  In ad right now the only site that is showing is TIC ( old site).   Why wont my windows 7 clients work, why cant I push install from sccm 2012 or on the client machine go to the sms_111 share and double click the ccmsetup. When I do the logs are below. 

    I'm new to the world of Configuration manager but been around a long time, Just need a push in the right direction, any help or suggestions is greatly appreciated! I'm in a 2000 enterprise location with 8 remote locations, all on the same domain.

    ==========[ ccmsetup started in process 12136 ]==========    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Running on platform X64    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Updated security on object C:\Windows\ccmsetup\cache\.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Launch from folder C:\Windows\ccmsetup\cache\    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    CcmSetup version: 5.0.7804.1000    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Ccmsetup command line: C:\Windows\ccmsetup\cache\ccmsetup.exe /remediate:all    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Loaded command line: C:\Windows\ccmsetup\cache\ccmsetup.exe     ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    SslState value: 224    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    No sitecode is specified or detected. Assume AUTO sitecode.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    CCMHTTPPORT:    80    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    CCMHTTPSPORT:    443    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    CCMHTTPSSTATE:    224    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    CCMHTTPSCERTNAME:        ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    FSP:        ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    CCMFIRSTCERT:    1    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Ccmsetup run in remediation mode. Adding MPs from the client as backup.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Searching MP from client    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Did not find any MP from the client.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    No MP or source location has been explicitly specified.  Trying to discover a valid content location...    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Looking for MPs from AD...    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Local Machine is joined to an AD domain    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Current AD forest name is ntsupport.tic.toshiba.com, domain name is ntsupport.tic.toshiba.com    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Domain joined client is in Intranet    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    DhcpGetOriginalSubnetMask entry point is supported.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Begin checking Alternate Network Configuration    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Finished checking Alternate Network Configuration    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Adapter {79F03CF8-90B5-41CD-BFD2-BA0103E1EFC6} is DHCP enabled. Checking quarantine status.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Current AD site of machine is TIC    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Attempting to query AD for assigned site code    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=167972891)(MSSMSRangedIPHigh>=167972891))))'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.3.16.0)(mSSMSRoamingBoundaries=TIC)(mSSMSSiteCode=TIC)(mSSMSSiteCode=111)))'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Verifying Site Compatibility for <666>    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Current AD forest name is ntsupport.tic.toshiba.com, domain name is ntsupport.tic.toshiba.com    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Domain joined client is in Intranet    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSGetSiteVersionFromAD : Attempting to query AD for MPs for site '666'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=666))'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7678.0000' for site '666'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Site Version = '5.00.7678.0000' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteVersionCompatible : Site Version '5.00.7678.0000' is not compatible.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Site <666> Version '5.00.7678.0000' is not compatible.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Verifying Site Compatibility for <TIC>    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Current AD forest name is ntsupport.tic.toshiba.com, domain name is ntsupport.tic.toshiba.com    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Domain joined client is in Intranet    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'TIC'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=TIC))'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6487.0000' for site 'TIC'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Site Version = '4.00.6487.0000' Site Capabilities = <Capabilities SchemaVersion="1.0">
    </Capabilities>    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteVersionCompatible : Site Version '4.00.6487.0000' is not compatible.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Site <TIC> Version '4.00.6487.0000' is not compatible.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Verifying Site Compatibility for <111>    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Current AD forest name is ntsupport.tic.toshiba.com, domain name is ntsupport.tic.toshiba.com    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Domain joined client is in Intranet    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSGetSiteVersionFromAD : Attempting to query AD for MPs for site '111'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=111))'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7804.1000' for site '111'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Site Version = '5.00.7804.1000' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteVersionCompatible : Site Version '5.00.7804.1000' is compatible.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSIsSiteCompatible : Site <111> Version '5.00.7804.1000' is compatible.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    This client might be within the boundaries of more than one site - AD SiteCode search matched 3 entries    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    The client will be assigned to the first valid site    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    LSGetAssignedSiteFromAD : Trying to Assign to the Site <111>    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Got site code '111' from AD.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=111))'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    OperationalXml '<ClientOperationalSettings><Version>5.00.7804.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>30820303308201EBA003020102021028AB17C8DB4D9E844445B657317366BB300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303331373139323532335A180F32313133303232323139323532335A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101008867CDCF875031BDA95B6679A8794505DE344A4F85C1D3892B971B56E49C21260A78B0280AEFDA159E512EEFA5690E867A8CAE68A0E2119D8917F8ECFCFD30E3DDF27914A4D00B33A9FEB092347BFB5B746DC1D261900012B53AB2D13AAB87129EA043DDA17B9EF4A259B239A40B3EEFCE7B52C0A1E5ADC0E0CAD144DD355DADA4FB6343C7C657023D9FAB90BD6CD3F16251ACD419319762ECA07D0C0F93F11A65CA6C0250D0E09C29227CA7120686A1F0233BED8FB56F87C9FF8E35AAAD5495AA0662BB1DAFFFCD1C8B6ED95B4CCB61671CC891C4078A1803DA1D4EFC89D1E20D83F4233E0D833F7DE3150EBF2B32BCB67301867563A4470AADC3D973A96F390203010001A34B304930310603551D11042A30288226436F6E66674D6772323031322E6E74737570706F72742E7469632E746F73686962612E636F6D30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100029EC234E40DDA6C7D42E963B62D09FF7E0F94FAAD6F2AB784E959B0D0C1B29ADB8E91797105EA3A08C6D9156B45F5ADF9B15BB67EC1BB23696E60088C2493762E87CA943605BFE281AF4629A755ADC73E2F09798AD9912EF2C3F350184692FF1A4E7CAF9610A75BFAC6AB7366B3E5B52F8C086BEC2C7E3E78A3C150D523C6D7156AE8F768B22DA8F7EA1B43E57EA8B6E8ECF503A05B1EBD8CBE57CB4E2C86D9E4F19131F12DC840DAB4A5DE391CA74B2484FD75EF9B1E6968F2AD02874DED8CCDEE7ED0A18992D60B53241028369A477D60E9401BA3DB4950B0B39CE393141246DA87AE8076A567D2C116A345CCEE10CC1D6A017798A6E3502382B75F6FD79C</SiteSigningCert></SecurityConfiguration><RootSiteCode>111</RootSiteCode><CCM> <CommandLine>SMSSITECODE=111 SMSMP=CONFGMGR2011 SMSLP=CONFGMGR2012 FSP=CONFGMGR2011 DNSSUFFIX=NTSUPPORT.COM</CommandLine> </CCM><FSP> <FSPServer>ConfgMgr2012.ntsupport.tic.toshiba.com</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="ntsupport.tic.toshiba.com" /><Forest Value="ntsupport.tic.toshiba.com" /></ClientOperationalSettings>'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    SSL State is invalid: 0x80000000.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Registry Value HttpsState is not valid. Selecting HTTP for Client.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    The MP name retrieved is 'ConfgMgr2012.ntsupport.tic.toshiba.com' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    MP 'ConfgMgr2012.ntsupport.tic.toshiba.com' is compatible    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Retrieved 1 MP records from AD for site '111'    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    FromAD: FSP = ConfgMgr2012.ntsupport.tic.toshiba.com    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    FromAD: command line = SMSSITECODE=111 SMSMP=CONFGMGR2011 SMSLP=CONFGMGR2012 FSP=CONFGMGR2011 DNSSUFFIX=NTSUPPORT.COM    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Current AD forest name is ntsupport.tic.toshiba.com, domain name is ntsupport.tic.toshiba.com    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Domain joined client is in Intranet    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    CMPInfoFromADCache requests are throttled for 01:07:09    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Found MP http://ConfgMgr2012.ntsupport.tic.toshiba.com from AD    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Config file:          ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Retry time:       10 minute(s)    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    MSI properties:    SMSSITECODE="AUTO" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" SMSMP="CONFGMGR2011" SMSLP="CONFGMGR2012" FSP="CONFGMGR2011" DNSSUFFIX="NTSUPPORT.COM"    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Source List:    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    MPs:    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
                      http://ConfgMgr2012.ntsupport.tic.toshiba.com    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    No version of the client is currently detected.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Updated security on object C:\Windows\ccmsetup\.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Sending Fallback Status Point message to 'ConfgMgr2012.ntsupport.tic.toshiba.com', STATEID='100'.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Failed to get client version for sending messages to FSP. Error 0x80041010    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Params to send FSP message '5.0.7804.1000 Remediation '    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    State message with TopicType 800 and TopicId {815D959B-9EA7-4005-946C-9ACADAF8C28E} has been sent to the FSP    FSPStateMessage    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Another instance of ccmsetup is already running.    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    Failed to delete file C:\Windows\ccmsetup\ccmsetup.log. Error 32    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    CcmSetup is exiting with return code 3    ccmsetup    3/22/2013 12:11:36 AM    10836 (0x2A54)
    ==========[ ccmsetup started in process 11248 ]==========    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Running on platform X64    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Updated security on object C:\Windows\ccmsetup\cache\.    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Launch from folder C:\Windows\ccmsetup\cache\    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    CcmSetup version: 5.0.7804.1000    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Ccmsetup command line: C:\Windows\ccmsetup\cache\ccmsetup.exe /evaluate:prereqs    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Loaded command line: C:\Windows\ccmsetup\cache\ccmsetup.exe     ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    SslState value: 224    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service.    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    No sitecode is specified or detected. Assume AUTO sitecode.    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    CCMHTTPPORT:    80    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    CCMHTTPSPORT:    443    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    CCMHTTPSSTATE:    224    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    CCMHTTPSCERTNAME:        ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    FSP:        ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    CCMFIRSTCERT:    1    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Config file:          ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Retry time:       10 minute(s)    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    MSI properties:    SMSSITECODE="AUTO" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Source List:    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    MPs:    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
                      None    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Ccmsetup will run as an evaluation.    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    Found a local ccmsetup.cab. A new one will not be downloaded.    ccmsetup    3/22/2013 12:11:36 AM    11492 (0x2CE4)
    C:\Windows\ccmsetup\cache\ccmsetup.cab is Microsoft trusted.    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\cache\ccmsetup.cab.    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Successfully loaded ccmsetup manifest file.    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Item 'i386/vcredist_x86.exe' is applicable. Add to the list.    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Item 'x64/vcredist_x64.exe' is applicable. Add to the list.    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Item 'i386/vc50727_x86.exe' is not applicable.    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Item 'x64/vc50727_x64.exe' is applicable. Add to the list.    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Item 'i386/WindowsUpdateAgent30-x86.exe' is not applicable.    ccmsetup    3/22/2013 12:11:37 AM    11492 (0x2CE4)
    Item 'x64/WindowsUpdateAgent30-x64.exe' is applicable. Add to the list.    ccmsetup    3/22/2013 12:11:

    Friday, March 22, 2013 5:59 PM

Answers

  • from the looks of the log file it looks to me like the installation is running ok. You need to look at the clientidstartupmanager.log file and the clientlocation.log file (both on the client) to find the answer to why the clients are not getting assigned to the correct site. I can see that you are using the SMSSLP commandline, no need for that as CM12 do not have a server locator point.

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    • Proposed as answer by NPherson Wednesday, May 15, 2013 12:51 AM
    • Marked as answer by John W. Kirshy Thursday, May 16, 2013 1:58 PM
    Monday, March 25, 2013 7:17 AM

All replies

  • from the looks of the log file it looks to me like the installation is running ok. You need to look at the clientidstartupmanager.log file and the clientlocation.log file (both on the client) to find the answer to why the clients are not getting assigned to the correct site. I can see that you are using the SMSSLP commandline, no need for that as CM12 do not have a server locator point.

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    • Proposed as answer by NPherson Wednesday, May 15, 2013 12:51 AM
    • Marked as answer by John W. Kirshy Thursday, May 16, 2013 1:58 PM
    Monday, March 25, 2013 7:17 AM
  • Thanks Kent, I ended up migrating over all ad boundaries from Sccm 2007 and tweaked those boundaries to use in Sccm 2012. Thank you very much!

    I found some other issues that Sccm new admins might find helpful. 

    The ccmclean.exe that everyone uses does not always clean up the sccm2012 client. I actually had a windows error on the ccmsetup log on a few clients that said the program was already installed. I think it was error 1638 on the client ccmsetup.log.  It was baffling, the client install did not show up in control panel or in the add-remove programs,  and I could not find a trace of the client in windows or the registry?

    After much searching I found a dos command that lists all the programs installed on your PC and it showed the sccm 2012 client still installed? It was there from previous attempts to install the client with wrong settings or other issues like not having the proper permission on System Container in AD.   I fixed this ccm client install issue buy running Microsoft Windows Install Cleanup Tool, it found the sccm 2012 client and uninstalled it. It also cleaned the registry of the offending msi reference  that my installer was looking for and telling me it was already installed. A reboot and then I could manually  install the new sccm 2012 client!  So much time on this issue, but it alerted me to the pitfalls of pushing the client from sccm console.  One particular headache discovery was on a failed push of the client the ccminstaller runs as a service for the next 12 hours, so if you want to push again with corrected entries you have to manually stop the service on the client machine and then push, this answers many question as to why does it take so long for clients to show up in the console. I need to invoke the not run as a service option on the ccmsetup.exe, that is published to the sms_sitecode folder.

    I also found firewall errors on many client PCs, we have a domain group policy that disables the domain firewall only.  However  on some machines, I still had to poke holes through the domain policy even though it was disabled.  This presented another very important non documented issue that two important services are blocked by default in windows 7, WMI and File sharing ports. No wmi  access and no communication from sccm clients to sccm server. To fix this issue, I had to open the ports on various clients manually, and then disable the firewalls again and it worked? Maybe since the public and home\work firewall are still enabled?  I'm not sure how to fix that error yet. 

    If you push the client from your Sccm server, the local firewalls are an issue, even disabled! Enable firewall, allow ports, then disable firewall.

    In my environment I was thrown into the software install with no training, I  read books and researched very much. The most important web site I found was the   SCCM 2012 Microsoft Team site http://blogs.technet.com/b/configmgrteam/. It will alert you to changes and new CU's and other issues, especially with SP1.

    A major mistakes I did was not understanding that keeping two Sccm servers a 2007 and 2012 actually on the same network with same ad boundaries does cause major issues! You Push the client, or run it from the sccm network share and you get all kinds of  issues.  Don't make the same mistake, migrate the Boundaries from 2007 and then Turn off the sccm 2007 services that run SCCM. Stop the ad broadcast to the system container and remove all entries that point to the old 2007 server. Although the 2012 client install will look for the newest sccm server 2012 all the time this issue still was a pain.

    I learned that by trial and error, some say a great way the to learn.  With research I did see warnings about dual version of servers running on one domain, but I did not fully understand that two servers were broadcasting to Ad system container with two sms server entries , all it does it confuse the clients depending on how often the clients call the mother ship and check in.

    This is my continuing journey into a environment with 3k users and 7 remote sites with one sccm 2012 server, 2 domains.  My manager keeps asking when it will be ready, im on my 4th Virtual machine running this software and am getting better at it. Performance wise the vm's work great of course I have a massive NetApp drive system and a Very healthy Vm-Ware environment with 10 gig fiber connections. You have to be a well rounded tech to install this software and I keep telling him it will be soon.  I Hope as of writing this ill be configuring my production server. If Anyone has any comments please post as im an not a guru yet!

    Thursday, May 16, 2013 4:34 PM