drewmccabe

We stood up our SCCM implementation about a year ago and have seen a small percentage of clients 5% that do not report a hardware inventory. They pull down the machine policy fine and the heartbeat DDR is also reporting back in a normal time frame. I have initiated full inventory scans using the SCCM Client center tool and I see in the inventoryagent.log file on the client that it sends the inventory up to the MP (there are errors that certain collection tasks failed but that looks like that occurs because they don’t apply SMS_Windows8ApplicationUserInfo for instance). When I look in the dataldr.log I see it processing mifs for unknown computers that get put into the badmif nonexistant row folder that when I open them have the computer name of the pcs that aren’t reporting software inventory. I have looked and there are not duplicate computers that I can easily find and the PC reports normally otherwise (EPP gets updates etc). Here is an example of what I see in dataldr.log Processing Inventory for Machine: Unknown Version 55.24 Generated: 11/06/2013 07:57:42 SMS_INVENTORY_DATA_LOADER 11/6/2013 7:58:22 AM 27140 (0x6A04) Thanks for any help! Drew

I restarted the WDS service and the log does up. It shows the following: Machine is running Windows Longhorn. (NTVersion=0X601, ServicePack=1) SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) MAC Ignore List Filename in registry is empty SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Begin validation of Certificate [Thumbprint 0D3E37083601409E657770EE9173ACCCF02E7AA1] issued to '{A3B4D7A2-07CB-435F-8018-2896096BECCE}' SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Completed validation of Certificate [Thumbprint 0D3E37083601409E657770EE9173ACCCF02E7AA1] issued to '{A3B4D7A2-07CB-435F-8018-2896096BECCE}' SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Initializing PXEPerfObject. SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Could not load logging configuration for component ccmperf. Using default values. SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Client is set to use HTTPS when available. The current state is 224. SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Adding BF100004.6 SMSPXE 6/3/2013 9:16:37 AM 7128 (0x1BD8) Adding BF100018.2 SMSPXE 6/3/2013 9:16:45 AM 7128 (0x1BD8) Found new image BF100004 SMSPXE 6/3/2013 9:16:52 AM 7128 (0x1BD8) Opening image file F:\RemoteInstall\SMSImages\BF100004\boot.BF100004.wim SMSPXE 6/3/2013 9:16:52 AM 7128 (0x1BD8) Found Image file: F:\RemoteInstall\SMSImages\BF100004\boot.BF100004.wim PackageID: BF100004 ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 6/3/2013 9:16:52 AM 7128 (0x1BD8) Closing image file F:\RemoteInstall\SMSImages\BF100004\boot.BF100004.wim SMSPXE 6/3/2013 9:16:52 AM 7128 (0x1BD8) Found new image BF100018 SMSPXE 6/3/2013 9:16:54 AM 7128 (0x1BD8) Opening image file F:\RemoteInstall\SMSImages\BF100018\boot.BF100018.wim SMSPXE 6/3/2013 9:16:54 AM 7128 (0x1BD8) Found Image file: F:\RemoteInstall\SMSImages\BF100018\boot.BF100018.wim PackageID: BF100018 ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 6/3/2013 9:16:54 AM 7128 (0x1BD8) Closing image file F:\RemoteInstall\SMSImages\BF100018\boot.BF100018.wim SMSPXE 6/3/2013 9:16:54 AM 7128 (0x1BD8) Begin validation of Certificate [Thumbprint 0D3E37083601409E657770EE9173ACCCF02E7AA1] issued to '{A3B4D7A2-07CB-435F-8018-2896096BECCE}' SMSPXE 6/3/2013 9:16:56 AM 7128 (0x1BD8) Completed validation of Certificate [Thumbprint 0D3E37083601409E657770EE9173ACCCF02E7AA1] issued to '{A3B4D7A2-07CB-435F-8018-2896096BECCE}' SMSPXE 6/3/2013 9:16:56 AM 7128 (0x1BD8) PXE Provider finished loading. SMSPXE 6/3/2013 9:16:56 AM 7128 (0x1BD8)

Hello, I have been banging my head against this one for a few days now. So we have SCCM 2012 SP1 installed and I have been unable to get a machine to successfully PXE boot from the SCCM server. The SCCM server and the DHCP server are two separate boxes. IP-helpers are in place between the two boxes and the workstation network. I have already unchecked PXE under the DP settings and let it remove WDS and then rechecked it letting it re-install. The WDS service is running and shows started. I have also enabled unknown computer support on the DP. I have also removed and re-distributed the boot images to the DP and verified that the option to deploy from PXE distribution point is checked. If we do not specify DHCP option 67 I get the PXE-E53 error and if I do specify option 67 with SMSBoot\x86\wdsnbp.com i get the error "No Response from Windows Deployment Services server". I also verified the images are in the remoteinstall directory. The smspxe.log does not show any errors just beginning validation of cert and completed validation of cert over and over. The DP is also configured for HTTP not HTTPS. We do see tftp traffic from the workstation to the SCCM server. Any thoughts on what else I should try? Thanks! Andrew