I saw the same thing and had a laugh; quality control seems to be going by the wayside in the early days of “Windows as a Service.” It looks like someone in that thread has opened a case; maybe I will do the same.
From: [email protected] [mailto:[email protected]] On Behalf Of Steve Whitcher Sent: Tuesday, 17 November, 2015 10:55 AM To: [email protected] Subject: Re: [mssms] Deploying Win10 1511 install.wim I imported the OS image into MDT this morning, and was surprised to find that the install.wim from this new ISO identifies itself as "Windows 10 Enterprise Technical Preview". That's as far as I've gotten. On Tue, Nov 17, 2015 at 10:25 AM, Fusco, Brendan <[email protected]<mailto:[email protected]>> wrote: Has anyone else tried to deploy the new Windows 10 build (1511 / 10586) via an OSD task sequence using the install.wim from the media? I’m seeing the same issue that a poster in the TechNet forums described at https://social.technet.microsoft.com/Forums/en-US/f2313d6f-e42f-44ae-8506-3cb1f81e2a22/windows-10-build-1511-100105860-and-sccm-osd-changes-os-drive-assignment-to-x. The OS drive gets assigned as X: and the task sequence fails after the reboot into Windows. The same task sequence works fine with the RTM (10240) install.wim. This is on ConfigMgr 2012 R2 SP1 CU1.
