So I checked SCCM db from which we are doing the import and it looks like even though only one records shows up in SCCM UI, DuplicateName1 is there twice in Computer_System_DATAĪnd both MachineIDs can be found in multiple tables, like:Ĭomputer_System_DATA, Disk_DATA, Processor_DATA, PC_Memory_DATA, and most importantly PC_BIOS_Data etc. However if serial numbers are not the same, they will not be merged. FNMS will query some tables and built computer records based on that. I looked into ImportedComputer table, querying by same name and found two ‘ DuplicateName1’ devices, each with different MachineID (previously mentioned ABC123 and new XYZ789) and distinct serial number.Īs I understand this data is being imported directly from SCCM database. Both records have SMS as last source of inventory, however when I check in System Center Configuration Manager UI, I see only one such device - let's give it a name of ‘ DuplicateName1’ and Resource ID (MachineID in FNMS db) of ABC123. Those devices have same names, but different serial numbers. My techs and I have tried searching, but we're either using the wrong keywords or no one else is having the issue - which I find hard to believe.We have a problem, where can see growing number of duplicates in FNMS. Any suggestions on how to get SCCM to keep the wired MAC address "active" without telling teachers to plug the laptops into the wired network periodically? So in reality, SCCM isn't forgetting the wired MAC, it's just not using it. On the flip side, we have SCCM setup to "ask" if an unknown computer should be image (we have an optional deployment setup for unknown computers, so you have to hit F12 to get it to run on PXE boot) - but the computers SCCM "forgets" don't ask to take the optional deployment. It doesn't work seemingly because SCCM doesn't recognize the MAC address.
The trouble comes in when we want to reimage the computers using PXE and have to use the wired card. Seems like it would be fine since it does update the computer's record with the wireless MAC address and software deployments work fine over wireless. What we've found over time is that SCCM seems to "forget" the MAC address of the wired nic of laptops who only use wireless for connecting.
We're using SCCM 2012 to image all our computers and have been since last summer.
0 kommentar(er)
