Hi   were on 1709 and have been for some time, we do not show any further updates in the updates section. all systems including SUP work fine and the system can download patches etc from MS, so can get to the outside world through the FW,   what log will show any issues?   cheers

Hi All, We are running SCCM 1806 and Windows 10 1709 clients and currently have an issue where we try to image a machine using PXE we get the following error:     Previously it was working fine (about 6 weeks ago) but it has now just stopped. If i look at the SMSPXE.log i get the following: 16/10/2018 12:25:30 PM    ============> Received from client:
16/10/2018 12:25:30 PM     Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 09DF8E1C
 Sec Since Boot: 0 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
 Addr: 00:15:5d:98:2f:03:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 1=Discover
  Type=57 Max Msg Size: 05c0
  Type=55 Param Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
  Type=97 UUID: 00c5aa2830da4b354c927442798bf8d6fd
  Type=94 UNDI: 010300
  Type=93 Client Arch: EFI BC
  Type=60 ClassId: PXEClient:Arch:00007:UNDI:003000
16/10/2018 12:25:30 PM    Prioritizing local MP http://xxxxxxxx.xxxxxxxx.local.
16/10/2018 12:25:30 PM    Not in SSL
16/10/2018 12:25:31 PM    Not in SSL
16/10/2018 12:25:31 PM    Client lookup reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="16777501" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 16/10/2018 12:25:31 PM    00:15:5D:98:2F:03, 3028AAC5-4BDA-4C35-9274-42798BF8D6FD: device is in the database.
16/10/2018 12:25:31 PM    Prioritizing local MP http://xxxxxxxx.xxxxxxxxx.local.
16/10/2018 12:25:31 PM    Not in SSL
16/10/2018 12:25:31 PM    Request using architecture 9.
16/10/2018 12:25:31 PM    Not in SSL
16/10/2018 12:25:31 PM    Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="16777501" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply> 16/10/2018 12:25:31 PM    00:15:5D:98:2F:03, 3028AAC5-4BDA-4C35-9274-42798BF8D6FD: no advertisements found
16/10/2018 12:25:31 PM    Prioritizing local MP http://xxxxxxx.xxxxxxxxxx.local.
16/10/2018 12:25:31 PM    Not in SSL
16/10/2018 12:25:31 PM    Not in SSL
16/10/2018 12:25:31 PM    00:15:5D:98:2F:03, 3028AAC5-4BDA-4C35-9274-42798BF8D6FD: No boot action. Aborted.
16/10/2018 12:25:31 PM     Operation: BootReply (2)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 09DF8E1C
 Sec Since Boot: 0 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 192.168.152.025 Relay Agent IP: 000.000.000.000
 Addr: 00:15:5d:98:2f:03:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 2=Offer
  Type=54 Svr id: 192.168.152.025
  Type=97 UUID: 00c5aa2830da4b354c927442798bf8d6fd
  Type=60 ClassId: PXEClient
16/10/2018 12:25:31 PM    00:15:5D:98:2F:03, 3028AAC5-4BDA-4C35-9274-42798BF8D6FD: Not serviced.
16/10/2018 12:25:34 PM    ============> Received from client:
16/10/2018 12:25:34 PM     Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 09DF8E1C
 Sec Since Boot: 0 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
 Addr: 00:15:5d:98:2f:03:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 3=Request
  Type=54 Svr id: 192.168.152.017
  Type=50 Requested IP: 192.168.152.100
  Type=57 Max Msg Size: ff00
  Type=55 Param Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
  Type=97 UUID: 00c5aa2830da4b354c927442798bf8d6fd
  Type=94 UNDI: 010300
  Type=93 Client Arch: EFI BC
  Type=60 ClassId: PXEClient:Arch:00007:UNDI:003000
16/10/2018 12:25:34 PM    ============> Received from client:
16/10/2018 12:25:34 PM     Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0404FBE8
 Sec Since Boot: 0 Client IP: 192.168.152.100 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
 Addr: 00:15:5d:98:2f:03:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 3=Request
  Type=55 Param Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
  Type=57 Max Msg Size: 05c0
  Type=60 ClassId: PXEClient:Arch:00007:UNDI:003000
  Type=93 Client Arch: EFI BC
  Type=94 UNDI: 010300
  Type=97 UUID: 00c5aa2830da4b354c927442798bf8d6fd
16/10/2018 12:25:34 PM    Prioritizing local MP http://xxxxxxx.xxxxxxxxx.local.
16/10/2018 12:25:34 PM    Not in SSL
16/10/2018 12:25:34 PM    Request using architecture 9.
16/10/2018 12:25:34 PM    Not in SSL
16/10/2018 12:25:34 PM    Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="16777501" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply> 16/10/2018 12:25:34 PM    00:15:5D:98:2F:03, 3028AAC5-4BDA-4C35-9274-42798BF8D6FD: no advertisements found
16/10/2018 12:25:35 PM    Prioritizing local MP http://xxxxxxxxxxx.xxxxxxxxxxx.local.
16/10/2018 12:25:35 PM    Not in SSL
16/10/2018 12:25:35 PM    Not in SSL
16/10/2018 12:25:35 PM    ============> REQUEST Reply to client ([192.168.152.100:4011]) Len:285
16/10/2018 12:25:35 PM     Operation: BootReply (2)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0404FBE8
 Sec Since Boot: 0 Client IP: 192.168.152.100 Your IP: 000.000.000.000 Server IP: 192.168.152.025 Relay Agent IP: 000.000.000.000
 Addr: 00:15:5d:98:2f:03:
 BootFile: smsboot\x64\wdsmgfw.efi
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 5=Ask
  Type=54 Svr id: 192.168.152.025
  Type=97 UUID: 00c5aa2830da4b354c927442798bf8d6fd
  Type=60 ClassId: PXEClient
  Type=250 020105
16/10/2018 12:25:35 PM    <============ REQUEST Reply (end)
  Any help would be appreciated.   Thanks in Advance.   Paul    

Hi All, I have a large number of satellite sites all with there own domain which is untrusted to our main Domain with our Primary site although connectivity to these sites are all serviced via the same underlying network. What are the basic steps for me to discover these workstations in my Sccm current branch1806 environment. I was thinking about testing with one of these sites, firstly by manually creating a boundary group for one of the untrusted subnets, adding a network access account to the primary site, system or network discovery? I'm looking for recommendations for the best approach.   Any assistance would greatly appreciated   

Current patched SCCM on a prior working Windows 10 OSD for some reason starting failing on Pre-Provision Bitlocker. Nothing changed that I can think of. Also first time posting and am kind of new at running SCCM so forgive me. I've checked logs I know of and see nothing about Bitlocker. For now I had to "Continue on error" so the techs can keep imaging computers.    I have other issues with my task sequence I would like to ask about later but this is the issue I need to work on first. Please let me know logs and such I should post. If there are any task sequence experts out there I would be more than willing to do a paid engagement to help me get this, and the other issues I'm having sorted.  Short list of other issues I can't seem to work out -After first PXE boot to format the drive in the even the drive is currently encrypted, many of the Dell BIOS settings seem hit and miss. The computer then reboots but tries to PXE boot again and must fail then will continue booting off hard drive. How do I ensure on "install operating system" part it's booting PE off the C drive. The larger issue is if I make offline media. The computer will keep booting and formatting the drive over and over. The fix is to pull the USB stick on the first reboot. The computer will then boot PE off the C drive and ask for the USB drive when ready. I'm usually quite skilled at reading manuals and figuring things out but I always feel like SCCM has so many little moving parts and I never seem to have a full grasp of it.   Thanks!

Hello,   I have the problem with my SCCM that I cannot open the Administration Console anymore. The last think I have do bevor it don't works anymore was to fix my 0% downloading from Software Center Problem. I have tried these steps from Arthur_Li (because the fix with the .mof files don't work for me): https://social.technet.microsoft.com/Forums/windows/en-US/df00b2e4-3bab-4b46-ad5a-95e82617a039/wmi-errors?forum=winserverNIS Here are the SMSAdmin Logs: [19, PID:1928][10/11/2018 08:50:07] :Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__74.MoveNext() [19, PID:1928][10/11/2018 08:50:07] :Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__74.MoveNext()    at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nConfigMgr Error Object: instance of __ExtendedStatus
{
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'PS0'";
ProviderName = "WinMgmt"; } Error Code: ProviderLoadFailure [19, PID:1928][10/11/2018 08:50:07] :Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__74.MoveNext()   I have tried to reinstall the console with the AdminConsole.msi but this don't work. Also I have tried to connect with my IP, but also no success. The complete D drive where SCCM is installed, the SMSAdmins Group has "Full control" permissions. At this group are all user where can connected to the server and the server itself.
All sms services are running.   One think I found out is that my wmi maybe don't work right. At another Topic (https://www.windows-noob.com/forums/topic/10298-applications-suddenly-wont-deploy-hung-stuck-at-0-downloading/) they tried "Run the query select * from sms_sci_component where componentname=SMS_DISTRIBUTION_MANAGER" to fix the wmi problem, but if I try this query I get the following error: Number: 0x80041017
Facility: WMI
Description: Invalid query   Could it be that this query is only for 2012? At the wmiprov.log I get this error by trying to open the Console from SCCM: (Wed Oct 10 10:16:42 2018.780762406) : WDM call returned error: 5   The WMIDIAG Log is attach below     WMIDIAG-V2.2_2K12R2.SRV.RTM.64_SRV-SCCM_2018.10.12_09.52.41-REPORT.TXT

Hello Guys,   We have the Problem that our Surface wont boot from Network. The last Message we get is "nbp file downloaded successfully" When i use the same TS an USB-Stick it works fine.. a normal HP Workstation over Legacy installation works fine..   Any ideas? best Regards

We just upgraded SCCM to 1806 including the hotfix.  Everything seemed to be ok.  I updated the ADK as well so I could install the new version of Windows 10.  I'm currently having trouble with that as well, but that's a different post.  Any idea why my windows 7 images fail at the driver package now that I upgraded SCCM?  Nothing else has changed.  Logs don't show anything of use that I can find. ** Update ** For all my windows 7 driver packages, I had to check "Install driver package via running DISM with recurse option".  Wish that was in some kind of documentation I had read ahead of time.

We just downloaded Win 10 1809 and started to attempt to roll it out (testing) but every time the task sequence fails with unknown errors (0x80004005) at the Apply Operating System Step.  I did some searching and it sounded like the version of SCCM we were on was not compatible so yesterday I upgraded to Config Mgr 1806 and also the 1806 hotfix.  Thought that would resolve the issue but it doesn't.  I copied the original task sequence for 1803 that was working and replaced the OS thinking that would be the easiest way to do it.  Any ideas what might we wrong with the 1809 version?   *Edit, my Network Admin downloaded the ARM version which will not work on our pc's.  Now that 1809 is paused, I'm not going to worry about it anymore.  Until the next version...