suspect0

Just tried this in my environment. Got 1607 working on at least 1 laptop so far, going to try mine at somepoint. Thank you for the excellent documentation!

This is what the default command line looks like for the upgrade: msiexec.exe /p configmgr2012ac-sp2r2sp1-kb3074857-x64.msp /L*v %TEMP%\configmgr2012ac-sp2r2sp1-kb3074857-x64.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous maybe try modifying your install command.

Go to Monitoring >> System Status >> All Status Messages >> Enter the approx. time frame for the logs. >> Filter for the Message ID 30037 (or for the component Microsoft.ConfigurationManagement.exe) This should give you the user and where they did it from, as well as the time of course.

Are they being detected as Windows NT Workstation 10.0 in CM?

Couple quick questions: 1. These are physical machines I'm assuming? 2. If so, could UEFI being off/on affect the task sequence? I'll keep scanning this, but after a quick look I don't see anything glaring that would cause a failure.

I skipped this part and had Config Manager create the database for me. I know creating it beforehand is probably the preferred method, but I'm not terribly good with SQL and didn't want to screw things up before I started. Sorry that really doesn't answer your question, but just sharing my process.

Potentially. I'm no expert, but 2 sets of eyes are better than 1 right? pastebin.com might be easier on the eyes

Are you looking at the log off the client being imaged? Should be located at x:\smstslog\smsts.log (location after the disk gets formatted) You can hit F8 during the TS to bring up a command prompt and from there either copy the file to a USB and open it in CMTrace or open notepad from that command prompt and navigate to the above log. <EDIT> Might need the storage controller driver imported to the boot image. Or if it's HP or Dell (not sure on others) you can grab the PXE drivers and import those and add them to the boot image.

In your DHCP scope, the correct PXE server is specified under the Boot Server Host Name?

We're going to start applying updates to workstations and servers every third week of the month (probably the wednesday). What I want to do is automatically download new updates on patch Tuesday -> Add them to the Update Group -> Make them available 1 week later (in our Maintenance Window) for users to download and install -> After 10 days make them force installed. I think I have it setup correctly, but I want to be sure. Template: (This is for Windows 10 Updates) http://pastebin.com/rYUajrCr

It seems plausible but I don't have an answer. You'd probably need to create a task sequence, and manipulate the ISO somehow? It's not really a function (at least that I've seen) that is needed from SCCM.

Uncheck all the products in that list, then perform a sync. Wait for it to complete, then re-add the products you want. You should see Windows 10 there. Also cumulitive update 1 is available for CM12 R2 SP1 https://support.microsoft.com/en-us/kb/3074857

I'm working on standing up a new Config Manager install for our company. I have about 5 years experience with SCCM 2007 but I've never installed it. It's going to be installed on a Hyper-V VM, hardware specs won't be an issue at all. My questions is really about getting started. Should I install SQL on a second box or on the same box as SCCM? How should I partition the drives for storage and for SQL? I gave myself 1TB to play with as far as disk space. Any help would be appreciated.