All Customization must be re-done in 1703 (feedback to Microsoft)

Brass Contributor

I have SCCM 1702 with Win10 ENT 1607. I have done lot of work to fully customize and automatize this enviroment. Now everything works and everyone is happy.
 
If I change 1607 CBB to 1703 CB in my SCCM OSD Wipe-and-Load deployment, this things will break/lost;
 
- Lockscreen not effected
- Start Screen is a mess
- Taskbar not effected...
- Fingerprint is grayed out again, not working
 
So is it so, that IT organizations must do lot of customization work (1/3 of full Win10 enroll project) every time the new build comes in place?

0 Replies