I spent a portion of the last two weekends attempting to upgrade my homelab vCenter Server running on Server 2016 from 6.5.0 to 6.5.0-U1 with little success. My implementation is only a month old and non-complex, aside from the external Platform Service Controller servicing the single vCenter Server (so far).
Both the PSC and the VCS returned the same error during installation: “Installation of component VCSServiceManager failed with error code ‘1603’. Check the logs for more details.”
I built a new computer over the weekend and wanted to take advantage of Storage Spaces to group some drives together. Little did I know that adding BitLocker to the volume would quickly corrupt and obliterate the data on it.
The issue only appears relevant on the Windows 10 1511 Novenber Build (TH2, 10586) when the OS drive is also encrypted by BitLocker and when the new XTS-AES 128 format is used. Shortly after encryption begins, files and directories will begin to vanish from the volume. After a reboot the volume is entirely unmountable and the above error displays stating that “the disk structure is corrupted and unreadable.”
We’re now rolling through week four of the Windows 10 migration at DWR with only a few disruptions. One particular issue though popped up rather suddenly during wave two and strongly in wave three. We found a growing number of computers with networking issues. Specifically they were all failing to obtain DHCP leases both on startup or through manual renewal.
This week I’ve been making the final updates to the reference image for laptops to the library’s educational program involving Minecraft and other games for kids. However after laying in the last set of Windows updates and other applications, Sysprep failed and logged the error Package was installed for a user, but not provisioned for all users.
From the error log, it appeared that a Store app was causing a blocking failure. This was odd, because I hadn’t once launched the Store nor side-loaded any apps. Further, all the work was done on the builtin account with which the Store cannot even be used.
Here’s a short guide that was a bit too much to fit into the reference materials section.
I had been asked to install Classic Shell on some laptops and tablets for deployment. As part of the deployment process, I went ahead a built in into the reference image that would be used. In order to prevent the Classic Shell welcome screen from appearing at first logon I added the configuration registry keys to the default registry hive.
The below script will mount the default registry hive, insert the keys, and unmount the hive for you.