Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Quinten

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. very odd.....it started working. I guess removing the DP and adding it back worked. But I still would like to know why, if starting in 1806 WDS is not need it gets added when you add the DP role? thank you for your help!
  2. yes, I have distributed the boot image. here is something I don't get. I removed WDS. Since I am in a lab I removed the DP role. I then re-added the DP role and it Reinstalled the WDS Role and it recreated the C:\RemoteInstall folder. It populates the folder with my boot images etc... I read that starting in CB 1806 WDS is no longer needed? Why did adding the DP role reinstall WDS? my distman log says this: WDSServer is STARTED SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:29 AM 9784 (0x2638) Running: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstal
  3. Hello. Yes, I have that setting enabled on my boot image. In my BIOS on my target laptop I have enabled secure boot, UEFI, PXE. I have tried with RAID and with ACHI. in the SCCM everything seems to work. system discovery, user discovery. I can deploy both packages and applications. on my target laptops Software Center works and I can pull applications from there. So content distribution is working. Which should mean boundaries are working. on my DP\PXE role I have: Enable PXE, Allow this DP to respond to incoming PXE requests, Enable unknown computer support, Resp
  4. I have stood up SCCM-CB 2010 I have enabled PXE boot on the DP I have setup all boundaries I am able to deploy software and push data to my DP I have added the ADK including WinPE portion I have read that starting in 1806 you no longer need WDS to make PXE work I PXE a laptop and it dies brining me to the menu press F1 key to retry boot Press F2 key to reboot into setup Press F5 key to run onboard diagnostics I checked the time when I started the F12 / PXE on my laptop I see nothing written to SMSPXE.LOG on my primary site server at the time I ran the F12 / PXE proc
  5. Does Partition Disk 0 - UEFI call Diskpart.exe? And does it pass diskpart.exe a .txt with a list of commands? I thought when in WinPE the SCCM task sequence will use OSDDiskPart.exe.
  6. when my windows 10 updated to version 2004 it broke my headphones. I have tried EVERYTHING I can find on the Internet. Nothing works. I have deleted all drivers and uninstalled all driver software. I have gone to ReakTek and installed all drivers for my hardware. reboot over and over. Nothing works. I have tried with and without a docking station too, nothing works. When I plug in a headset it is Never detected. I know my headphones work since I have an older laptop that has Windows 10 1703 on and they work fine. What else can fix this?
  7. I have enabled 3rd party software updates within SCCM. When I try to download any 3rd party update I get this error "All software updates in this selection are expired and meta-data only, and cannot be downloaded" What causes this and how do you fix it? Thank you.
  8. In my WUAHandler.log I see the same updates installing each day for the past 4 days. No errors, just the same updates each day are being installed and each says Reboot Required = Yes. We reboot all of our systems each night so that should get flushed out. UpdateDeployments, UpdateHander have no errors. what would case this behavior?
  9. We have enabled 3rd party patching and we've noticed that when we deploy Dell 3rd party updates they do deploy down to our systems (both Latitudes and Optiplex) We setup our SUGS to run at night. on any target system once the updates run you can view them in Software Center \ Updates. They show as Installed. Here is the problems. The updates never clear out of Software Center \ Updates and each night they reinstalled. I've sat there and watched at the Software Center \ Updates and each will change from Installed to Installing.... and then they show as Installed again. This
  • Create New...