Quinten

I have a string CIM_Chassis (CreationClassName = "CIM_DockingStation", Tag = "ABCD1234") How do I get just the ABCD1234 ? I have 2 equal signs and 2 sets of quotes and that is messing me up. Any help would be great.

Hello, I had a question on PowerShell Version: 5.1.19041.1023 If you look at the attached screenshot you'll see what I'm curious about. I run this command in PowerShell ISE: Get-CimInstance -ClassName win32_computersystem -Property * | Get-Member -MemberType Method You see what it displays in the display window. But when I run WEBMTEST and I choose OPEN CLASS and then Win32_ComputerSystem you'll notice the METHODS don't match what you see in the ISE command. My question is why? Thank you.

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!

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:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:29 AM 9784 (0x2638) Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:30 AM 9784 (0x2638) Failed to run: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall". Program returned c1030105 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) Machine is running Windows Server. (NTVersion=0X602, ServicePack=0) SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) No need to configure the firewall SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) Processing LAB00002 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) Expanding C:\SCCMContentLib\FileLib\BD88\BD88B94A0A4DE3BE6CCCA83D5572627F6650FD2D7E9BE8A18F1C2A6208A24498 from package LAB00002 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) Finding Wimgapi.Dll ... SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) Found wimgapi.dll in system folder, wimgapi path: C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) SetNamedSecurityInfo() failed. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) SetObjectOwner() failed. 0x80070003. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) SetFileSecurity() failed. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) Expanding LAB00002 to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638) Processing LAB00005 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) Expanding C:\SCCMContentLib\FileLib\88D5\88D543CD7DE2EF4F189DAED5B54D6D32B6CEB13262E7CFE407CE3014F8F32D32 from package LAB00005 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) Finding Wimgapi.Dll ... SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) Found wimgapi.dll in system folder, wimgapi path: C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) SetNamedSecurityInfo() failed. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) SetObjectOwner() failed. 0x80070002. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) SetFileSecurity() failed. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) Expanding LAB00005 to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638) CcmInstallPXE: Deleting the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) Finished ConfigurePXE - SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) Updating DP setting from SCF to DP machine, configure branchcache, LEDBAT, DOINC - SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) DP monitoring task is disabed on server SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) No need to initialize monitoring task on SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) DP settings have been updated to SCCM.TEST.NET [sccm.test.net]. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) Initialize usage gathering task on SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) IIS Version 10 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) Successfully saved iis settings. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) Log Location C:\inetpub\logs\LogFiles\W3SVC1 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) Successfully enabled usage gathering on the local distribution point. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) 1998-01-01T00:00:00 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) DP settings have been updated to SCCM.TEST.NET [sccm.test.net]. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) OS information for the server - 10.0.17763, ProductType=2 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) OS information for the server - 10.0.17763, ProductType=2 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638) OS information for the server - 10.0.17763, ProductType=2 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:34 AM 9784 (0x2638) Finished updating DP setting from SCF to DP machine, configured BranchCache, LEDBAT, MCC - SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:34 AM 9784 (0x2638) DP configuration thread done for distribution point SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:34 AM 9784 (0x2638) DP config change processing thread: thread completion event. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:34 AM 8052 (0x1F74)

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, Respond to PXE requests on all network interfaces, specify the PXE server response delay = 3 seconds. I even tried adding the WDM role. That did not work. So I removed the WDM. I have also injected the NET, SCSI and HDC drivers into the boot.wim. any other suggestions would be greatly appreciated.

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 process. Not sure what I'm missing. Thanks.

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.

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?

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.

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?

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 cycle repeats. And it only effects Dell. Our Lenovo and HP updated all work fine. Any hints or pointers would be great.