Most orgs don't reduce the interface level :) / Johan
From: [email protected] [mailto:[email protected]] On Behalf Of Klish, Brian Sent: den 2 november 2015 07:13 To: '[email protected]' <[email protected]> Subject: [MDT-OSD] RE: Windows Server 2012 R2 interface levels on custom image I confirmed this today: This was caused by running a cleanup of the custom image during deployment image creation. If I ran this command: DISM.exe /online /Cleanup-Image /startcomponentcleanup /resetbase It prohibited me from reducing to interface level 2. It's the /resetbase part that breaks it. I rebuilt my Windows Server 2012 R2 image and still did a cleanup, but this time I left off the /resetbase and now it works fine. Very surprising that this isn't a common problem for a lot of people considering how popular the image cleanup has become to reduce image size. -Brian From: Klish, Brian Sent: Thursday, October 15, 2015 8:58 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: RE: Windows Server 2012 R2 interface levels on custom image This problem appears to be caused by doing the "DISM.exe /online /Cleanup-Image /startcomponentcleanup /resetbase" when I create the server image. It works fine if I don't do that. I guess my server images are going to be 1.2GB bigger. -Brian From: Klish, Brian Sent: Tuesday, September 29, 2015 9:08 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: Windows Server 2012 R2 interface levels on custom image I create and deploy my server images just like my client images. The only difference is I do the server deployments using offline media since the network configuration is so much more complicated depending on teaming, physical or VM, iSCSI, etc. I recently decided to start looking at moving to a different interface level since Server 2012 R2 supports adding and removing interface components as necessary. For some reason I can't move to interface level 2 - in other words I can't remove Server Graphical Shell and run only with Graphical Management Tools and Infrastructure. I can go from interface level 3 to 1 (core), but I still can't go from level 1 to 2 once I do that. Basically it always gives me an error saying "The request is not supported. Error: 0x80070032". This is only a problem if I build a custom image in MDT and deploy it. I found that if I deploy a vanilla image using MDT from a "Full set of source files" then it works fine. So what doesn't it like about my image? The only thing I do for my server image is Windows updates, and then a "DISM.exe /online /Cleanup-Image /startcomponentcleanup /resetbase", install Ultra VNC, and install Adobe Reader. Nothing else is in the image. I've tried doing it before joining the domain and I've even if I uninstall the apps in the image it still won't work. Anyone ever run in to this? Also, this was a problem for me before and after upgrading to MDT 2013 update 1. -Brian
