Jump to content


Search the Community

Showing results for tags '80244019 SCCM'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hi All, I just wanted to drop a quick message to let you know about an old error I came across this morning when configuring the client install through WSUS. After installing WSUS and the SUP on my Server 2012R2 install with SCCM CB, I was getting error 80244019 from the Windows Update client on the client machines. After some investigation, I found that the "Content" directory within IIS was inaccessible by IIS. I could manually reach it by going there myself, or using the run command. I could access it by the share name, and directly on the host itself, from multiple locations with multiple accounts. But when I right clicked on it and chose "Explore", it told me the directory could not be found/access (or something along those lines, sorry no screenshots! ). Following on from that, I decided to check the permssions of course, which were all correct. I removed and reinstalled WSUS and SUP a couple of times, but doing the same process each time I installed it. In the end, I removed both WSUS and SUP from the SCCM Server. Rebooted. Reinstalled WSUS, but rather than storing the updates using the UNC path, I pointed it to the local path, so "E:\Sources\Windows Updates" for example, rather than "\\SCCM\Sources\Windows Updates". I told SCCM to STOP installing the client through WSUS. Waited for the rule to finish to remove it from the deployment (you can confirm this by going back in to the setting and both boxes will be empty (nothing is published). Told it to publish by WSUS again, then waiting a few more minutes. After a short while, I checked the Windows Updates folder again, and there it was, CCMSetup.exe was present. I then checked the "Content" directory in IIS and it was accessible this time by clicking "Explore". I went back to one of my servers. Told it to check for updates, and it worked! Just in case anyone else comes across this in the future as I did search online, but nothing really pointed to this being an issue. To me, it looks like it doesn't like to use the UNC paths! But I'm sure someone will correct me if I'm wrong.
×
×
  • Create New...