Jump to content


bosco

Established Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bosco

  • Rank
    Newbie
  1. I determined that Windows Updates for the InTune Co-Mgmt had been switched to Intune and the Feature Updates needed to be configured there.
  2. Our desktop team didn't get off of 1809 before EOL. Now in SCCM, any newer feature update says "Affected products Windows 10 1903 or newer" So the FUs don't show required for any 1809 systems. Any way to easily fix that, or are they going to have to do task sequences? I think they said task sequences worked, but the look to the user was clunky.
  3. Ran into this, wanted to post my findings in case it helps anyone else out. We just got in the new Dell model - Latitude E6320. It needed the NIC driver for boot image and Windows. I added that to SCCM, and the OSD task sequence worked fine for Windows 7 x64 SP1. It was missing some drivers, so I added all the missing drivers to SCCM. Then the next one failed the OSD task sequence. I got error - Exiting with code 0x80004005 Windows setup failed, code 31. I had tested all the drivers and new they were good. However, the OSD doesn't appear to like DriverVer=10/19/2010,7.0.0.1144 of the I
  4. In the software deployment section, Tobie had a guide on doing the same thing by manually creating a package/program/advertisement. What are the benefits and drawbacks of doing it the two different ways? It seems easier to do it via the Software Update. Do you get more information returned about the successes/failures with one method compared to the other? thanks, bosco
×
×
  • Create New...