Issue with automatically generated names based on serial numbers for virtual machines in SCCM
I noticed this issue at a customer where they were deploying machines and automatically configuring the machine name according to serial number.
There were no issues with deploying physical machines, but virtual machines were failing during the “Apply Windows Settings” step with the following error code:
Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure you are running this executable inside a properly configured OS
The reason why we see this issue is that virtual machines have longer serial numbers than 16 characters, which is the maximum amount of characters allowed for a machine name during OSD.
If you have a script that sets the serial number automatically, you will need to configure it to only take the first 16 characters of the serial number.
About the author
Daniel Classon works as a Senior Consultant at Mansoft, focusing on Microsoft Configuration Manager, Windows 10 and Powershell
- How to install .NET Framework 3.5 on Windows Server 2012, Windows Server 2016 and Windows 10 966,050 views
- Issue with mounting new ISO files from TechNet in Windows 8 and Windows 8.1 Preview 63,837 views
- 2 steps to solving SCCM deployment error “sending with winhttp failed; 80072ee7” in Windows PE 31,550 views
- Powershell: Script to set Outlook 2010/2013 signature using information populated from Active Directory 32,098 views
- How to get PXE to work in Hyper-V for Legacy Boot 108,236 views
- How to force specific sites to always run in Compatibility View using Group Policy 143,821 views
- How to change between a Full Installation (GUI) and Server Core in Windows Server 2012 64,082 views
- How to solve WDS issue with DHCP port conflict 12,114 views
- Hyper-V: Issue when starting virtual machine from downloaded ISO file 7,471 views
- Command to check Bitlocker status in Windows 10 119,067 views