WSUS updates issue in SCCM 2007.

Hi Friends,
I have SCCM 2007 infra with multiple sites having a central site server (Windows server 2003 SP2 standered). Earlier it was working fine till May 2014 but now it is not syncing with Microsoft updates.  Below are the steps i took-
1. Checked the events logs and found the error with event ID 6703. " Cannot sync with WSUS server. WSUS server not configured" like this.
2. After that I found WSUS server not configured on the box.
3. In installed WSUS SP2 on the box and successfully synchronized with Microsoft updates (Proxy settings and port settings 8530 and 8531 configured).
4. Active Software update point role reconfigured after WSUS.
5. Now still these updates not synchronizing in SCCM console.
6. Getting same errors nothing good happened.
Can someone help me?

Check all possible causes http://technet.microsoft.com/en-in/library/bb735874.aspx
Narahari(Hurry) Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Similar Messages

  • WSUS Update KB2938066 and SCCM 2012 R2

    Looking at the newly release WSUS update KB2938066 and wondering if I need to apply it to my SCCM WSUS component. If so, what type of impact on the SCCM clients should I be aware of?
    Orange County District Attorney

    As the update is about securing and hardening WSUS and also the communication with WU/MU, I would definitely apply this update.
    The client-side is going to be tricky, depending on the configuration of your windows updates. Jason did a very good post about this here:
    http://blog.configmgrftw.com/the-wua-dilemma-in-configmgr/
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SCCM 2012 Client Communication Issue with SCCM 2007

    My Clients was installed SCCM 2007 client version but somehow those clients reporting to SCCM 2012 Server 
    Note : My SCCM 2007 Server still active mode . and the SCCM 2007 client IP boundaries was not added into SCCM 2012 server
    But still communicating to SCCM 2012 , what is the root cause ?  
    Best Regard's Krishna

    Either, during the client installation the client was manually assigned to the ConfigMgr 2012 site (by specifying the site code), or during the client installation the client was auto assigned to the ConfigMgr 2012 site (that can only happen when there
    is an overlap in the boundaries and that doesn't have to be the same type of boundary).
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SBS2008 WSUS Update Issues

    I'm trying to find out what the hell is going on with our WSUS. My desktop and laptop are the trial children for the issue and both were attached to the server the same way, both have the same errors when attempting to update (800B0001 or on install 800B0002).
    The desktop is the only domain connected computer in the WSUS computer list is one of my issues and this needs to be sorted but before this, no computers are able to update to WSUS but will via MU if forced. The update facility worked for a day or two after
    server install and been downhill since (assume a fixit f33ked it).
    I've run a heap of update repair utilities from MS and done WSUS SP installs etc but still nothing. I'm at a loss and quite frankly so far see WSUS as more of a nuisance than a pleasure. My desktop apparently hasn't synced in 48 odd days and I'm fed up with
    the server fails. Most of the machines on the network (including my two) are 8.1 but Win7 seems to be just as prone.
    Help pls.
    It is in great danger that we see great courage!

    Hi,
    à
    I've run a heap of update repair utilities from MS and done WSUS SP installs etc but still nothing.
    Would you please let me confirm whether had installed
    KB 2720211 and
    KB
    2734608? Please refer to following article and check if can help you.
    Windows Update error 800B0001
    If this issue still exists, please refer to following article to repair Windows Server Update Services on the
    SBS 2008 and monitor the result.
    Repair Windows Server Update Services
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • SCUP 2011 for SCCM 2007 - SUP, WSUS plus MS PKI certificates (not self-signed ones)

    I am installing System Center Updates Publisher 2011 for our SCCM 2007 R2 system.
    Our SCCM 2007 R2 system runs in mixed mode. We have a dedicated server for SUP/WSUS and OSD/PXE functions.
    Shall I install SCUP 2011 on the dedicated server? I have installed it on my Windows 7 computer. What is the best practice configuration? SCUP should be equivalent WSUS role for Microsoft Partners software updates. Am I right? In this case, I should install
    SCUP on the SUP/WSUS server in my opinion.
    We have used the SUP/WSUS to apply Microsoft updates without any problems so far.
    When I am investigating the certificate requirement for SCUP 2011 code signing, I have found out that our SUP/WSUS server has some self-signed certificates for SMS and WSUS.
    All our SCCM 2007 servers except one have self-signed SMS Encryption Certificate and
    SMS Signing Certificate - those certificates are issued to
    SMS by SMS. The SUP/WSUS server also has an extra self-signed certificate
    WSUS Publishers Self-signed for code signing.
    We do have our own Microsoft Active Directory Certificate Services internal PKI service which has been trusted by our AD domain. Therefore, I would like to use an certificate from the PKI service for SCUP 2011 server such that all our SCCM 2007 clients will
    trust the certificate for non Microsoft software updates.
    What should I do re the self-signed SMS or WSUS certificates on the SUP/WSUS server?
    I just want to add SCUP to our SCCM 2007 system without causing problems to Microsoft updates deployment via SUP/WSUS.
    Thanks,
    SJJ123

    Personally I have used the self signed certificate and used the AD Group policy to distribute the certificate. I think it would be possible to import a certificate from your PKI into SCUP. Have you tried this?
    Louis

  • SCCM 2007 R3 XP Embedded Software updates

    I need to have a question answered. With Windows XP now being EOL and no updates coming through SCCM 2007, How will the Windows Embedded 2009 devices that are still supported by Microsoft going to receive their updates through SCCM? In the past they just
    got updated with the other XP updates.
    Any help is appreciated

    Windows Embedded is not end of life until January 8, 2019 so you should still be able to receive product updates for that software.
    More information can be found here:
    http://blogs.msdn.com/b/windows-embedded/archive/2014/02/17/what-does-the-end-of-support-of-windows-xp-mean-for-windows-embedded.aspx
    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

  • Installing SCUP/WSUS and integration into SCCM

    I have tried installing SCUP onto a SCCM 2012 Server with WSUS hosted on another site. 
    I used the instructions that have been circulated on the internet from Kent Agerlund. Despite persevering with this I cannot get updates to show in system centre configuration manager to deploy. 
    Installed the site update role on the sccm server
    1)Installed Hotfix KB2530678-x64
    2) Installed the update sc update publisher
    3) Installed the Signing certificate using the designated port to our wsus server
    4) Enabled config mgr integration connecting to a local CM server
     5) Exported the certificate to the WSUS server
    6) Imported the partner catalogue and published the abobe flash player update. 
    I get 
    File C:\Users\<username>\AppData\Local\Temp\2\\1t1ilkm3.geb\AdobeFlashPlayerCatalog_SCUP.cab has certificate but signature check failed, will be treated as unsigned.
    Updates Publisher 01/12/2014 10:16:29
    9 (0x0009)
    The error log that I get now is 
    WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "<sccmsername>.Local".
    Is is easier to migrate all of the WSUS updates to the SCCM server and then install scup?

    Are you running SCUP with an account this is a local administrator on the WSUS instance and/or have you run SCUP elevated to ensure UAC is not getting in the way?
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCCM 2007 Drivers not importing

    I am having an issue with SCCM 2007 and some Lenovo T440-T540 Drivers
    The first issue I have is that the Win PE image doesnt recognize that I have a valid network driver on it. (USB OSD comes back with "not a valid network adapter found") even though I have verified that the Intel driver is there. 
    2) When I went to re-import the drivers I get an error stating the drivers are already imported. I have removed the drivers from the admin console and you cannot see them anywhere. Thinking I might have to go somewhere in the DB to nuke them out. 
    I have removed the drivers from sccm by just selecting and deleting the package is also gone from the DP. Not sure how i can re-import them into sccm for them to show up under OSD/Drivers/T44-T540. I have verified the boot image has the correct drivers on
    it for network. 

    The first issue I have is that the Win PE image doesnt recognize that I have a valid network driver on it. (USB OSD comes back with "not a valid network adapter found") even though I have verified that the Intel driver is there. 
    I have removed the drivers from sccm by just selecting and deleting the package is also gone from the DP. Not sure how i can re-import them into sccm for them to show up under OSD/Drivers/T44-T540. I have verified the boot image has the correct drivers on
    it for network. 
    If WinPE (your boot image) is returning "no valid network adaptor found", you need to diagnose that. Enabling F8 support can help with that. The driver store in the db, and driver packages, are not directly relevant to which drivers are (or are not) injected
    into your boot image. (The driver store in the db, and driver packages, are relevant to the post-image-apply steps, when FullOS is running)
    Have you followed the steps here?:
    http://technet.microsoft.com/en-us/library/bb680705.aspx
    Your site server is CM2007SP2 ?
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • SCCM 2007 R3 Software Updates Sync : 6703 WSUS server not configured

    Hi,
    We run SCCM 2007 R3 in native mode (Software Update Point and WSUS both reside on SCCM site server). We're having issues running Software Updates Synchronization which have previously worked fine. In SMS_WSUS_Control_Manager the errors appear as follows
    MessageID:6703
    SMS WSUS Synchronization failed.
    Message: WSUS server not configured.
    Source: CWSyncMgr::DoSync.
    The operating system reported error 2147500037: Unspecified error
    I've followed the suggested fixes in
    http://technet.micro...y/bb735874.aspx but still we have an issue.
    If I open the WSUS console directly and run a manual synchronization from Microsoft this completes successfully. However, I presume this will not be using SSL which is what SCCM will want to use in native mode. I've checked the bindings in IIS on WSUS Administration
    site to confirm that the certificate hasn't expired.
    Any ideas what else I can try?
    Cheers,
    Paul

    wsyncmgr.log repeatedly contains the following
    Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER 13/10/2013 14:02:11 612 (0x0264)
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CCPSCCM02 SITE=WES PID=8084 TID=612 GMTDATE=Sun Oct 13 13:02:11.288 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 13/10/2013
    14:02:11 612 (0x0264)
    Sync failed: WSUS server not configured. Source: CWSyncMgr::DoSync SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CCPSCCM02 SITE=WES PID=8084 TID=612 GMTDATE=Sun Oct 13 13:07:11.284 2013 ISTR0="CWSyncMgr::DoSync" ISTR1="WSUS server not configured" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
    ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
    Sync time: 0d00h05m00s SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)

  • Sccm 2007 wsus spk2 updated now missing FCS in products

    I have a TESTLAB with SCCM 2007 that has been running fine and deploying Forefront Client Security. In SCCM under SUP I can see FCS in the products. I installed the kb2720211 WSUS SPK 2 update and things are doing fine. So I do the same thing
    in production and upgrade to WSUS 3.0 SPK2. Then I saw where I need to install KB2734608 to be able to work with Windows 8 and 2012 SERVER from SCCM 2007. I only installed it in production not in TESTLAB, I guess I broke my rule there.  a week or two
    go by and I notice that the FCS definitions stopped gong to windows 7 clients. Only have one Windows 8.1 in testing right now. not deployed in Production yet.
    Now I go trouble shooting and on the TESTLAB I can go to SUP and configure my Classification and PRODUCTS, I can still see FCS in the software update point component listed in products. I can also open WSUS in TESTLAB from Admin tools but I know not
    to manage products from here. On Production I do not see FCS anymore, it shows Microsoft Client Protection and Forefront Endpoint Protection 2012 in the SUP Products. My question is do I continue to move forward with upgrading TESTLAB and production to
    use Forefront Endpoint Protection which I have not read how to upgrade yet? Or can I just uninstall the KB 2734608 and fix FCS for now?

    Again the ONLY support report is to use the CM07 restore procedures. Will everything work after your restore? Who know as there is no way to know what the problem was/is. There
    will be gotcha when you restore your CM07 site and they sometime will fix themselves and other times it is just faster to force them to work. As such, I ALWAYS recommend to my clients that if they ever have to restore their CM environment that they contact
    CSS directly for support. This way CSS can ensure that the site is healthy and working correctly. There is No way to do that within the forums in any meaningful way.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Patches not visible in SCCM 2007 Site server even after approving the patches in WSUS

    Hi,
    The patches are not appearing in SCCM 2007 site server after approving the same patches in WSUS.
    Below are the patches.
    MS14-080: Cumulative Security Update for Internet Explorer - Windows Server 2008 SP2 - IE 7 - KB3008923 [23,186.1]
    MS14-018: Cumulative Security Update for Internet Explorer - IE 11 - KB2929437 - Windows Server 2008 R2 SP1 (x64) [4,32.4]
    MS14-066: Vulnerability in Schannel Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2992611 (x64) - V2 [1,8.3]
    MS14-038: Vulnerability in Windows Journal Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2971850 [1,8.1]
    MS09-060: Vulnerabilities in Microsoft Active Template Library (ATL) ActiveX Controls for Microsoft Office Could Allow Remote Code Execution - Visio Viewer 2007 SP1/SP2 [1,8.1]
    MS12-001: Vulnerability in Windows Kernel Could Allow Security Feature Bypass - Windows Server 2008 R2 Gold (x64) [1,8.1]
    MS14-033: Vulnerability in Microsoft XML Core Services Could Allow Information Disclosure - Windows Server 2008 SP2 - KB2939576 [1,8.1]
    MS14-025: Vulnerability in Group Policy Preferences Could Allow Elevation of Privilege - Windows Server 2008 SP2 - KB2928120 (x64) [1,7.8]
    MS13-014: Vulnerability in NFS Server Could Allow Denial of Service - Windows Server 2008 R2 Gold/SP1 (x64) [1,7.7]
    I have approved the above patches in WSUS and ran syncronization. The log wsyncmgr.log show that synchronization is done and even all child sites are syncronized. But I am unable to find the above even in the parent site. Checked all the SUP settings and
    all the 2008 server updates are set and marked to download.
    Please help me out on fixing this.

    So you should NEVER approve anything in WSUS. This will cause problems with your clients. Honestly since you approved things in WSUS, I would uninstall WSUS and reinstall it, reinstall the SUP, this will clear up any issues that now exist.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

    I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
    Whilst doing this I came across the following issue:
    The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
    the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
    Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
    the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
    So, when I come to update the client from 2007 to 2012, the following occurs
    The Client uninstalls, and the GPO policy settings for Windows Update are removed.
    Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
    for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
    As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
    maintenance windows.
    I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
    new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
    What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
    Any help would be appreciated.

    First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
    to it. Approving updates in WSUS is unsupported for ConfigMgr.
    What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
    need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Software Distribution & Patching Design Issues - Migration of Packages SCCM 2007 to Application or Conventional Packages in SCCM 2012

    Hi All
    I am starting in discussion to deep root on Software Distribution & Patching model in large environments from SCCM 2007 migrating to SCCM 2012.
    Below are certain assertions i am putting forward for your expert views or you may in a similar situation
    1- I have migrated the packages from SCCM 2007 to SCCM 2012 as conventional methods, now i am deploying them [ not migrated the advertisements and collections ], so while deploying i am facing a peculiar situation that the deployment when created is of the
    name "<<Package name>>(program)". I am not able to rename the deployment for the conventional packages. is there a way out to that??
    2- Will the collection queries work the same in SCCM 2012 as was in SCCM 2007??
    3- In SCCM 2012 Primary site there is default role called Site System role in that there is tab for proxy settings. I have observed that if do not check the proxy tab there and punch in proxy IP and port then after some time in the WSUS server the update
    source and proxy server tab the proxy option gets unchecked and hence the sync in software update point status appears failed. Is that anyone else also has observed !!!!!
    Regards Sushain KApoor

    This is a duplicate of
    https://social.technet.microsoft.com/Forums/en-US/2ddb8170-529b-4652-830e-fd0ade384b98/software-distribution-patching?forum=configmanagermigration
    Please do not double post.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

    Hi,
    I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
    wsyncmgr:
    Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
    SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
    3668 (0x0E54)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
    on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
    3668 (0x0E54)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
    1/9/2015 12:00:00 PM 3668 (0x0E54)
    WCM:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
    1/9/2015 11:19:03 AM 4176 (0x1050)
    STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    Remote configuration failed on WSUS Server.
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
    4176 (0x1050)
    I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
    Regards,
    Malwinder

    WCM:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    It's not only a matter of installing the console, but also those hotfixes on a remote server ...
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2007 WSUS patch

    I have successfullt install WSUS and i believe configure good with SCCM 2007.
    patchs downloaded but its not come in SCCM 2007 server how to sync to receive patchs in SCCM server.
    [email protected]

    Hi,When you say downloads where do you look then? you shouln't configure anything in the WSUS admin console as all configuration will be overwritten by sccm and you risk that clients install updates unexpecetdly.
    Check the wsyncmgr.log file for any errors? do the updates show up in the sccm console? have you run a Synchronization of the repository?
    The actual updates are donwloaded ones you select to download and deploy them and not when WSUS syncs.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

Maybe you are looking for