ConfigMgr SCCM 2012 SP1 Upgrade Checklist

system center configuration manager system center 2012 configuration manager sccm 2012 configmgr2012 configmgr sccm cm2012 checklist  ConfigMgr SCCM 2012 SP1 Upgrade Checklist

Are you looking SCCM ConfigMgr 2012 R2 upgrade check list? Please go over here : ConfigMgr SCCM 2012 SP1 to R2 Upgrade Checklist

Microsoft has released the check list for Configuration Manager 2012 SP1 upgrades. Download the evaluation version of CM 2012 SP1 from here. Also, be aware of know issues of CM 2012 SP1 from here. Re download the CM 2012 SP1 if you’ve downloaded it before 25-Jan-2012. There are updates in the binaries. More details here. How to update client to SCCM 2012 SP1? What are the options available this will be the next challenge. More information on client upgrade to SP1 here. There is a Cumulative Update 1 for ConfigMgr 2012 SP1. CU1 and CU2 resolve some of the Known Issues of SP1. More details about CU2 fixes here.

Few Eye Catching Bullet Points

1. Top to Down approach. Need to upgrade the CAS server (if you’ve one) first then primary and it’s secondary servers.

2. Take backup of CAS as well as Primary servers. Ensure that you’ve a good copy (I would suggest to have 2 copies just in case) of backup.

3. Install Windows Assessment and Deployment Kit (Windows ADK). Available here.

4.Disable the site maintenance task “Delete Aged Client Operations” on primary sites. This is interesting step, this is the first time I’m hearing about it. More details are available in the following TechNet link.

5. Create a copy of all the build-in collections IF you’ve modified those. In ConfigMgr 2012 SP1 the built-in collections are read-only and cannot be modified. Isn’t that interesting?

6. Run the prerequisite checker, 1 or 2 days prior to the actual upgrade. It would be easy to identify whether there is any issue with prerequisites or not.

7. Download prerequisite files and redistributable files which are the required for ConfigMgr 2012 SP1.

8. Take a copy of CM 2012 DB and attach it to a test SQL server and run test the database upgrade.

9:  WSUS patches KB 2720211 and KB 2734608 need to be installed on CAS, primary and remote SUP servers (Creation of SUP will fail without these updates applied to WSUS).  Thanks to Mike !

10. Uninstall previous version Windows Automated Installation Kit (AIK) from the server before installing new version.

11.  Go through the KB article 2801416 to understand the process that we need to follow before SP1 upgrade.

12. Apply the following hotfix 2801987 before upgrading ConfigMgr 2012 SP1 Client.

More Details on System Center 2012 Configuration Manager SP1 Upgrade checklist HERE.

Some other important topics which we need to take care after the upgrade process are also available at  Considerations For Upgrading to CM 2012 SP1.

There is no supported way to uninstall the Service Pack 1, more details available at the bottom the above mentioned link.

Posted in: Checklist, CM2012, ConfigMgr (SCCM), Configmgr2012, SCCM 2012, System Center 2012 Configuration Manager, System Center Configuration Manager

19 Comments

  1. Recently I upgraded my infrastructure to SP1 . I have outlined the steps which I took to perform the upgrade . This might be helpful to some one as well !!!!

    • Check the SQL version perquisites http://technet.microsoft.com/en-us/library/jj822981.aspx
    • Install the latest security patches
    • Copy the perquisites for Windows Assessment and Development Kit. When we try to install the wadk , it tries to reach the internet and download the perquisites/updates. So if the primary site is not having internet access we need to copy the perquisites/updates locally
    • Install Windows Assessment and Development Kit
    • Need to ensure that there are no issues related to site , like database replication and site issues.
    • Stop the Migration job if any
    • Take the backup of smsbackup folder
    • Take the backup of SQL
    • Stop the maintenance task ‘delete aged client operation’ on primary site
    • Installation updates required for sp1 upgrade should be copied locally on the primary site
    • SUP Perquisites and precautions , we did not do SUP NLB today but this is what I think as of now
    o Remove the server from NLB
    o uninstall the NLB role from the server
    o check the SUP configuration, like Default SUP etc..
    • Reboot the server for pending updates
    Download the perquisites for CM2012 SP1
    • Install the CM2012 SP1 bits
    • Reboot the server

  2. Yes , Its a TAP Program. But today i found that the the SUP and WSUS are giving some issues after the upgrade . When we do CM2012 sp1 upgarde it reinstall’s all the componenets ,and the SUP component in my case failed . Upon Further investigation and by looking into logs it looks like KB 2734608 is required on the SUP servers .

    But even after installing this hotfix , i see some errors and the SUP’s are not working. Has anyone faced this problem while testing in SP1 Beta ?

  3. Any inputs or clue on this will be appreciated . IIS setting are as configured correctly , I wonder If anything new needs to be configured

    Site Server: wcm.log
    System.Web.Services.Protocols.SoapException: Server was unable to process request. —> The type initializer for ‘Microsoft.UpdateServices.Internal.ApiRemoting’ threw an exception. —> The type initializer for ‘Microsoft.UpdateServices.Internal.UtilConstants’ threw an exception. —> Access is denied~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)

    SUP:- wsyncntrl.log
    System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.TypeInitializationException: The type initializer for ‘Microsoft.UpdateServices.Internal.ApiRemoting’ threw an exception. —> System.TypeInitializationException: The type initializer for ‘Microsoft.UpdateServices.Internal.UtilConstants’ threw an exception. —> System.ComponentModel.Win32Exception: Access is denied~ at Microsoft.UpdateServices.Internal.UtilClassFactory.CreateInstance(Type type, Object[] args)~ at Microsoft.UpdateServices.Internal.SetupInfo.GetInstallDirectory()~ at Microsoft.UpdateServices.Internal.UtilConstants..cctor()~ — End of inner exception stack trace —~ at Microsoft.UpdateServices.Log.InitializeFromConfig()~ at Microsoft.UpdateServices.Log.InitializeIfNeeded()~ at Microsoft.UpdateServices.Internal.ApiRemoting..cctor()~ — End of inner exception stack trace —~ — End of inner exception stack trace —~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)

  4. Anoop's says:

    Have you confirmed your proxy user name and password? —> Access is denied~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[]

  5. Thanks Anoop …the accounts were correct . Today i started fresh reinstall of WSUS + SUP . There was a bit sucess , but now the sync is failing .
    Tried manually syncing it from WSUS console …still no luck

    Also if your expertise can point me to some hnits here ,,,,,while upgarding to CM2012 sp1 the SUP componnet failed, and by looking at the logs i figured out that it requires KB2734608. After installing this hotfix the SUP componnet got installled

    But now the problem is that the sync is not happening ……i wonder if its has to do with the hotfox which was applied …

    SoftwareDistrubution Log in UpdateServices :

    2012-12-06 23:35:48.762 UTC Error WsusService.27 MicrosoftUpdateRollup.DoRollup Error found when running rollup: System.Net.WebException: The operation has timed out

    wcm.log on Site Server :

    Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssCommunicationError: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning() SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 3:24:07 PM 5052 (0x13BC)
    Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 3:24:07 PM 5052 (0x13BC)

    • Anoop's says:

      So you’re not getting access denied error in WCM.log. Are you still able to see access denied error WCM.log then that could be something related to access.

  6. I am not sure if its a access isssue ……I also tried with Netwrk service acct ,,,still the same errors. Here the detailed logs when i try to trigeer the sync ……something fishy over here is ‘cATEGORY PROODUCT NOT FOUND’ …..IN wcm.log

    WSUSCNTRL.LOG on SUP

    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Checking runtime v2.0.50727… SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256 SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256 SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Supported WSUS version found SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Attempting connection to local WSUS server SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    No changes – local WSUS Server Proxy settings are correctly configured as Proxy Name XXXXXXXXXcom and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Attempting connection to local WSUS server SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    There are no unhealthy WSUS Server components on WSUS Server XXX.XXX.XXXX SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Successfully checked database connection on WSUS server XXXXXX.XXXX.XX SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)
    Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 12/6/2012 6:24:21 PM 4612 (0x1204)

    WSYSSYNCMGR.LOG ON cas

    Performing sync on local request SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:09 PM 8180 (0x1FF4)
    Full sync required due to changes in main WSUS server location. SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:09 PM 8180 (0x1FF4)
    Read SUPs from SCF for XXX.XXX.XXSMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:09 PM 8180 (0x1FF4)
    Found 1 SUPs SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:09 PM 8180 (0x1FF4)
    Found active SUP co1stgsqlppe01.phx.gbl from SCF File. SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:10 PM 8180 (0x1FF4)
    Sync failed: WSUS update source not found on site PPZ. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:10 PM 8180 (0x1FF4)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_WSUS_SYNC_MANAGER” SYS=CO2STGCMTSQLC01.phx.gbl SITE=PPZ PID=7700 TID=8180 GMTDATE=Fri Dec 07 02:17:10.120 2012 ISTR0=”getSiteUpdateSource” ISTR1=”WSUS update source not found on site PPZ. Please refer to WCM.log for configuration error details.” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:10 PM 8180 (0x1FF4)

    wcm.log on the CAS

    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:26 PM 6164 (0x1814)
    Checking runtime v2.0.50727… SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:26 PM 6164 (0x1814)
    Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:26 PM 6164 (0x1814)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:27 PM 6164 (0x1814)
    Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:27 PM 6164 (0x1814)
    Assembly WSUSMSP loaded in .NET runtime v4.0.30319.586 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:28 PM 6164 (0x1814)
    Attempting connection to WSUS server: XXX.XXX.XX, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:28 PM 6164 (0x1814)
    Successfully connected to server: XXX.XXX.XX, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:40 PM 6164 (0x1814)
    Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:40 PM 6164 (0x1814)
    No changes – WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:41 PM 6164 (0x1814)
    Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:41 PM 6164 (0x1814)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:41 PM 6164 (0x1814)
    Attempting connection to WSUS server: XXX.XXX.XX, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:41 PM 6164 (0x1814)
    Successfully connected to server: XXX.XXX.XX, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:42 PM 6164 (0x1814)
    Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:46 PM 6164 (0x1814)
    Attempting connection to WSUS server: XXX.XXX.XX, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:51 PM 6164 (0x1814)
    Successfully connected to server: XXX.XXX.XX, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:0a487050-8b0f-4f81-b401-be4ceacd61cd (Forefront Client Security) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:4e487029-f550-4c22-8b31-9173f3f95786 (Windows Server Manager – Windows Server Update Services (WSUS) Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:5312e4f1-6372-442d-aeb2-15f2132c9bd7 (Windows Internet Explorer 8 Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:84a54ea9-e574-457a-a750-17164c1d1679 (Forefront Threat Management Gateway, Definition Updates for HTTP Malware Inspection) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:ae4483f4-f3ce-4956-ae80-93c18d8886a6 (Threat Management Gateway Definition Updates for Network Inspection System) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf (Windows Server 2008) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:cb263e3f-6c5a-4b71-88fa-1706f9549f51 (Windows Internet Explorer 7 Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:52 PM 6164 (0x1814)
    Category Product:d7d32245-1064-4edf-bd09-0218cfb6a2da (Forefront Identity Manager 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:53 PM 6164 (0x1814)
    Category Product:e88a19fb-a847-4e3d-9ae2-13c2b84f58a6 (Windows Media Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:53 PM 6164 (0x1814)
    Category Product:ec9aaca2-f868-4f06-b201-fb8eefd84cef (Windows Server 2008 Server Manager Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:53 PM 6164 (0x1814)
    Category Product:fdfe8200-9d98-44ba-a12a-772282bf60ef (Windows Server 2008 R2) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:53 PM 6164 (0x1814)
    Category ProductFamily:48ce8c86-6850-4f68-8e9d-7dc8535ced60 (Developer Tools, Runtimes, and Redistributables) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:53 PM 6164 (0x1814)
    Starting WSUS category sync from upstream… SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:24:53 PM 6164 (0x1814)
    WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:25:54 PM 6164 (0x1814)
    WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:26:54 PM 6164 (0x1814)
    WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:27:54 PM 6164 (0x1814)
    WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:28:54 PM 6164 (0x1814)
    Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssCommunicationError: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning() SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:29:00 PM 6164 (0x1814)
    Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:29:00 PM 6164 (0x1814)
    STATMSG: ID=6603 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_WSUS_CONFIGURATION_MANAGER” SYS=CO2STGCMTSQLC01.phx.gbl SITE=PPZ PID=5916 TID=6164 GMTDATE=Fri Dec 07 02:29:00.809 2012 ISTR0=”XXX.XXX.XX” ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:29:00 PM 6164 (0x1814)
    Waiting for changes for 55 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/6/2012 6:29:00 PM 6164 (0x1814)

    When i manually try to sync from WSUS console

    WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 65.55.138.126:443
    at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
    at System.Net.HttpWebRequest.GetRequestStream()
    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
    at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
    at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
    at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
    at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
    at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

    WSYSSYNCMGR.LOG ON cas

    Performing sync on local request SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:09 PM 8180 (0x1FF4)
    Full sync required due to changes in main WSUS server location. SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:09 PM 8180 (0x1FF4)
    Read SUPs from SCF for XXX.XXX.XXSMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:09 PM 8180 (0x1FF4)
    Found 1 SUPs SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:09 PM 8180 (0x1FF4)
    Found active SUP co1stgsqlppe01.phx.gbl from SCF File. SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:10 PM 8180 (0x1FF4)
    Sync failed: WSUS update source not found on site PPZ. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:10 PM 8180 (0x1FF4)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_WSUS_SYNC_MANAGER” SYS=CO2STGCMTSQLC01.phx.gbl SITE=PPZ PID=7700 TID=8180 GMTDATE=Fri Dec 07 02:17:10.120 2012 ISTR0=”getSiteUpdateSource” ISTR1=”WSUS update source not found on site PPZ. Please refer to WCM.log for configuration error details.” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 12/6/2012 6:17:10 PM 8180 (0x1FF4)

  7. Anoop's says:

    Sure ! The problem is like, it’s very difficult to read the log files in this post and forums. So it’s advisable to post log files to sky drive or something like that and provide the link details.

  8. Stefan Schipper says:

    In the RTM Version of SCCM 2012 SP1 the two WSUS Updates KB2720211 and KB2734608 are included in the prererquisite checker.
    The Prerequisite checker now says:
    “Configuration Manager requires Windows Server Update Services (WSUS) of at least version 3.0 SP2 with KB2720211 and KB2734608 installed. If using remote software update points, site server must have WSUS administration console installed. For more information on WSUS installation see http://go.microsoft.com/fwlink/?LinkID=79477.”

Leave a Comment and Contact Anoop

Visit Us On TwitterVisit Us On FacebookVisit Us On Google PlusVisit Us On YoutubeVisit Us On LinkedinCheck Our Feed