Jump to content


mudkips

Established Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mudkips

  • Rank
    Newbie

Recent Profile Visitors

571 profile views
  1. This turned out to be as simple as hitting enter as soon as " Succeed to download NBP" was displayed. I've added a PXE response delay to give us time to hit enter, but there's still no indication that you have to do so in order to continue with the network boot. I'm not sure why it fails on a VM, but it works for a physical machine.
  2. I've tried defining the vendor classes and policies as described in the video, but I've had no luck. I've also tried removing all of the DHCP options (60, 66, and 67) as well as defining 60 and 67 only (setting 67 to smsboot\x64\wdsmgfw.efi), but every combination results in the same 0xc0000225 error for a UEFI PXE booted VM, and the same "Succeed to download NBP" message (and then nothing) for a physical machine. Could this be an issue with the boot image? The PXE booting process loads boot.sdi instantly, then proceeds to load the x64 boot image. This boot image was created using the
  3. I can add an account and add it to the local administrators group during audit mode, and that works fine. Doing this also prevents the defaultuser0 account from being recreated during deployment. This will be my workaround for now, I guess, through we'd prefer to enter OOBE after the task sequence applies the image (or have the actual administrator account available).
  4. I'm trying to set up a task sequence to deploy Windows 10 via PXE. We have SCCM 2012 SP2 CU4 running on Server 2012 (not R2), with WDS 6.5.9200.16384, ADK 10.1.14393.0, and MDT 6.3.8443.1000. It's s single site and single server. I'm building the image from the official v1607 Enterprise ISO in a VM, entering System Audit Mode and doing some minimal config, and then using a freshly-built SCCM Capture Media ISO to handle the sysprep and image capture. Once captured, I create a basic (non-MDT) task sequence and deploy it as available to the unknown computers group for media and PXE o
  5. I'm trying to set up a task sequence to deploy Windows 10 via PXE to both UEFI and BIOS clients. We have SCCM 2012 SP2 CU4 running on Server 2012 (not R2), with WDS 6.5.9200.16384, ADK 10.1.14393.0, and MDT 6.3.8443.1000. It's s single site and single server. PXE booting to BIOS clients seems to work fine. When PXE booting UEFI client, it loads the boot file and then throws out 0xc0000225 complaining about \Windows\Syetem32\boot\winload.efi . We're deploying the task sequence to the "Unknown Computers" group, and we only care about x64 clients. The task sequence has an x
  6. Well I've decided to just grab the client via manual check of Windows Update (for any random things we don't do via PXE OSD). So my Windows Update Group Policy now just has the update server specified, and nothing else configured, as per this image: But it looks like this results in machines getting the default Windows Update settings applied. A 22 hour detection frequency, a daily install at 3 AM, and automatic reboots (even with logged on users). What is the proper way to disable the Windows Update stuff and let SCCM's SUP role handle everything? We currently have a Patch
  7. I have a question about using the Software Update Point to push out the Congifuration Manager client. I've enabled this option in SCCM, and I've set up a GPO so that all domain machines point to the WSUS/SUP site. "Specify intranet Microsoft update service location" is Enabled with both fields set to http://machine.domain:8530 . But I want all domain-joined machines to automatically install the configuration manager client. What I've done to achieve this is set "Configure Automatic Updates" to Enabled, with the options "4 - Auto download and schedule the install", "0 - Every day", an
×
×
  • Create New...