Config Mangler

Had something similar recently. Fixed by: 1. Deselect all update classifications in SCCM - run a synch and it will say nothing to sync 2. On WSUS server run wsusutil reset 3. Re-Select the classifications in SCCM and run a synch

Looks like it's skipping installing your driver packages as it's evaluating them to be false. "The action (HP ProDesk 400 G2.5 SFF) has been skipped because the condition is evaluated to be false" Is that really the WMI name of that model?

I didn't post the original topic, but I'm just manually importing a single computer record and it's failing. We're ramping up our Win 10 migration and I now have to reinstall the SCCM client and let it inventory before I can do an OSD. Thanks for checking when the rollup might be available, that's what I need to know. Chasing this via MS account manger too.

We are experiencing this bug in SCCM 1702 where we can’t import certain computer records. https://social.technet.microsoft.com/Forums/en-US/fadf5381-793f-4a9b-865d-17c6b9cddbe4/cm-1702-importcmcomputerinformation?forum=ConfigMgrPowerShell SCCM seems to be holding the MAC address even though there is no computer record so gives an error that the MAC is not unique when importing. Quoting Adam Meltzer Microsoft employee "This will be fixed in the next update rollup with a fix to the SMS Provider." I would be wary of installing 1702 in production until this is fixed.

Same here, pinned items gone. Not great for the users. Also had a corrupted tile, one I'd previously added for IE11. The tile then disappeared after a second reboot. Noticed all the AppX clutter is back again, Solitaire, Xbox etc. - apparently this will not get reinstalled again after 1703.

I can't read your attached logs, but what happens if you drop all the certificate stuff? Do you get any further?

There is an element of trial and error! Just want to check your process: - Identify the right driver for your OSD - it must be x64 to connect to x64 task sequence - and use a Win 10 driver for SCCM 2012 R2 - Import the driver - Tick the box to update the boot images - this takes 10 minutes or more - If booting off USB stick - re-create it. PXE will be fine.

It's still missing a driver. From your log - Failed to create list element with key value '74-df-bf-18-2f-0a' Is that the MAC address of your Ethernet NIC? 74-DF checks out as a Liteon hardware so that probably isn't the Ethernet NIC. Confirm the Ethernet MAC address, then install windows on one of each model of the laptops and check exactly what driver it's using in device manager - something like e1d65x64.sys - confirm you imported the matching driver.

Nah. You will still get OS updates. Home users get updates and they don't have SA! SA gives you data centre licences so e.g. you can have two copies of say a SQL server for DR purposes and pay for one. Also gives you product upgrades. Talk to your Microsoft chap!

Strange one. When you do ipconfig /all does it show a real NIC and MAC address? Can you ping the FQDN of the SCCM box? I'd be looking at adding a proper NIC driver. It's the Windows 10 / NDIS 6.5 one you want. Import that and add it to the boot images.

Not sure if you have done this but you need to import the drivers into the Boot images for them to be available in WinPE - just importing them without doing this will only make them available to the Windows OS.

Certainly a disk problem. Was the drive previously encrypted? Get a command prompt up in WinPE with F8. Do a diskpart - clean and try again. "The requested target could not be resolved to a valid volume on this computer. Check your task sequence to ensure this drive is correct and that it is being created The parameter is incorrect. (Error: 80070057; Source: Windows)"

Have you redistributed the boot images? Right-click "update distribution points"

I find if you get that far and it doesn't do applications it's a network driver or domain join issue. Check you can ping the SCCM box FQDN and check it is domain joined.

Probably the same issue we are seeing. Microsoft changed the update classifications without telling anyone. We previously used a rule to search for updates with a SEVERITY of "critical" or "Important" they have moved that value under the "update classification" so we were getting no updates.

Is it a VMware VM? That will disable the local admin when it runs sysprep or clones. If not I'd be looking at the unattend answer file Could also use net user administrator /active:yes to re-enable it.

Store access was the problem for me. We needed to allow access (with AppLocker) to Microsoft.Windows.ShellExperienceHost" and "Microsoft.Windows.Cortana" for the start menu to work. It was working in my lab as it has unrestricted internet access and no proxy server. In Production this was the opposite. If it's the same problem you'll see events that those applications cannot activate.

I don't think it purges the records so it would still be there in SQL. It's a pretty odd scenario recovering hardware deleted from AD a year ago. I'd tell them to forget it!

Why would you want to upgrade to 1511 during OSD. Just download the 1511 ISO, extract the install.wim, import it then drop it in to the Apply Operating System step.

That doesn't seem right to me. This is how it works for me: We activate BitLocker in the task sequence which stores the recovery key in AD. The MBAM client and group policy kick in later and the key is escrowed to the MBAM database. The MBAM database is then the authoratitive source as if the user changes the BitLocker password the recovery key is changed in the MBAM database but not in AD.

If they are identical hardware I'm guessing the one that works is on later firmware.

Have just implemented MBAM with SCCM integration in a lab following the Noob book. It looks like it's working but the Enterprise reports are all showing 100% unknown. If I run the individual computer compliance report that shown the computer is encrypted. I double-checked the new Classes were added ok and the database looks like it has the required fields but are not populated so it looks like the client isn't populating those fields so the reports have nothing to use. It's SQL 2014. There's a technet article about latency (kb2620269) but the system has been up for several days so should be updated by now. Any ideas where to look?

I am building the 840G3. It's very likely to be the same NIC driver. I'm using the Win 10 driver version 12.13.17.7 - E1D65x64.INF

I used SCCM driver detection to install the latest drivers. I used DISM to pull in the HP ESU - Essential System updates - this is a list of 40 KB's about 20 of which would actually install. This was at the request of HP support just to rule it out, but didn't fix my issue. Try the BIOS first and don't worry when it beeps 18 times. That's normal!

I'm using SCCM, but the issue we had was that it would randomly fail after a reboot during OSD. BIOS fix cured that. We have another on-going issue with these where they just reset during use. HP are working on that one. I used DISM to add the KB's just to satisfy HP, but most weren't relevant and didn't fix the first or second problem.