Microsoft was all about Windows 10 Last month & when we have a Windows 10 technical preview build (9926) out after so long then why not to deploy & test it. So, was trying to deploy windows 10 build 9926 using SCCM 2012 R2 CU4 in my lab & here are few things i found out during the deployment.
1. When you import windows 10 image in SCCM by default the package name is windows 8.1 enterprise (or pro).
2. When you import the windows 10 technical preview build # 9926 into SCCM and add it to the task sequence, under image section there are 2 images which appears in the drop down menu :
1. Windows 8.1 pro
2. Windows 8.1
When you select and deploy windows 8.1 pro every thing works fine. The image gets properly deployed and it gets joined to domain or workgroup.
But when you select windows 8.1 & then try to deploy it (joining it to workgroup or domain), it fails. There is no error in the SMSTS.log file but the task sequence UI shows error (will post the exact error codes).
3. When you import windows 10 enterprise technical preview, there's a single image appearing under image section, here also the name appears as windows 8.1 enterprise. But every thing works fine with this image. It gets deployed properly & the image gets joined to domain.
4. After deploying Windows 10 Technical preview build # 9926 on a Hyper-V VM there's a battery icon appearing in the splash screen. Strange !!
5. When you upgrade a windows 8.1 machine to windows 10 and if windows 8.1 image (there are 2 images windows 8.1 pro & windows 8.1) gets applied from the windows 10 image package, then it wont join to domain. The domain option is greyed out and following message appears :
6. SCCM Client Push installation don't work on Windows 10 Build # 9926.
CCM.log file says the OS is not supported :-
