Jump to content


Search the Community

Showing results for tags 'Boot images'.

  • Search By Tags

    • boot images ×
    Type tags separated by commas.
  • Search By Author

Content Type



Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Found 5 results

  1. Hi all Currently preparing for the 1710 upgrade from a previous version. According to MS, it's advisable to upgrade ADK on site servers beforehand. Currently running ADK 1607 (10.1.14393.0) and our default Production Boot Image is located in the ADK installation folder. I'm supposing that if/wh...
  2. Hello All, Hope everyone is doing good. I am facing issue while importing the boot images or modifying the existing boot images post upgrade to SCCM CB from sccm 2012. We have recently upgraded from SCCM 2012 R2 SP1 to SCCM CB 1606 and then immediately to 1702. We have ADK v1607...
  3. After upgrading to 1511 and ADK win10 and running the patch kb314370, F12 a client and get "No boot file name available". Cannot get F8 to open a cmd prompt for support logs either, yes it is enabled. Both the new (x86 and x64 from ADK) boot images are distributed and have WinPE 10 drivers....
  4. So every time I inject drivers into my x64 boot image, it ends up getting renamed. And it's done this several times before, apparently. If I browse to \\sccm\SMS_GSU\OSD\boot\x64, the boot image will be named "boot.GSU00002.wim". I will right-click on a driver in the driver store, tell it to...
  5. Ok, I'm slightly confused (read: very). My environment is as follows (simplified). One primary SCCM server (SVR-SCCM) W2K8r2 with SCCM 2007r3 that is also the PXE server for our Main Office. This site has been doing OSD perfectly. One Remote site (SVR-SITE1) that has it's own subnet, DC (with DH...
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.