At Infor we’re more and more utilizing Server Core as a result of it’s superior scaling time. Nonetheless, once I do have to construct a server with the GUI – having a non-functional begin menu defeats the purpose. Home windows 10 and Server 2016 undergo from a selected sysprep bug which causes the beginning menu to not pop when the beginning button is clicked. Right here’s repair it – together with a code snippet for automating the AWS construct.
In my work, this downside appears to have unfold to Server 2012 R2 with latest patches.
It seems that Home windows 10 and Server 2016 each undergo from a selected sysprep bug that’s well-known, however by some means retains creeping again into Home windows – so it appears Microsoft could also be having a tough time retaining this bug out:
This technet thread exhibits that the issue was first observed on Home windows 10 and crept again in throughout the Creators Replace: https://social.technet.microsoft.com/Boards/azure/en-US/39659172-1917-4796-9c2e-9b1adfeced86/win-10-unattendxml-copyprofile-true-breaks-search-bar?discussion board=win10itprosetup
This technet thread exhibits that, like myself, others discovered that it additionally impacts Server 2016: https://social.technet.microsoft.com/Boards/en-US/5516e208-793a-4bac-ba52-d7ad09b5a3b5/postsysprep-start-menu-issues-on-win10-enterprise?discussion board=win10itprosetup
Should you comb via the above articles you’ll find that disabling “CopyProfile” in unattend.xml fixes this downside. On desktop OSes it will not be a sensible choice to disable this as a result of necessities of customizing particular person consumer logons. Nonetheless, for Server OSes consumer customization isn’t wanted. So I elected to take the simple manner out and simply disable it in unattend.xml
Should you automate Home windows AMIs in AWS you understand that there are particular scripts and a particular unattend.xml offered and utilized by AWS once they put together machines. As well as, in Server 2016 AWS began utilizing a brand new method to making ready Home windows. As an alternative of utilizing the legacy ec2config service, it makes use of ec2launch – which is applied as a helpful PowerShell module with many system preparation capabilities.
This being the case, I wish to edit relatively than substitute the unattend.xml in order that I’ll preserve utilizing the one offered by AWS – this fashion in the event that they improve or bug repair it, I get the advantages of these updates with out having to find the exhausting manner that my static copy of unattended.xml now not matches the one offered by AWS.
The next traces of code will replace the AWS offered unattend.xml on a Server 2016 GUI or Core machine that’s produced from an AWS AMI.
$unattendxml = "C:ProgramDataAmazonEC2-WindowsLaunchsysprepunattend.xml"
(gc $unattendxml).substitute('<CopyProfile>true</CopyProfile>','<CopyProfile>false</CopyProfile>') | Out-file $unattendxml
I’m utilizing this code in Infor’s automated Home windows AMI construct course of.
