I’m getting a little frustrated with support and haven’t really made any progress on my PMR, I was curious if any other users out there are deploying Windows 10 version N LTSB 2016 (1607)? I can capture an image of the VM with this deployed without problem. I cannot deploy the captured image however, once the machine boots up post image, it’s bricked. It will flick the windows log on the screen briefly and then generic error immediately, as if the hard drive is missing or not plugged in (on multiple devices) -
“Your PC/Device needs to be repaired. A required device isn’t connected
or can’t be accessed. Error code: 0xc0000000f.
You’ll need to use recovery tools if you don’t have any installation
media (like a disc or USB Device). contact your pc administrator
or pc/device manufacturer.”
another issue I’ve had with this variant of the OS, which may be related, I can’t import the base ISO of this windows variant to the image library as a setup/resource image. I’ll select 'installation media (.iso) and select the win 10 N LTSB 2016 iso, and it will bomb out and flick the radio button option over to Linux capture image and display an error
“Image checking failed. Verify that the image version is supported and that the specified input path is correct. for more infornation, check %userprofile%\OSDeployment\rbagent.trc”
I’m not finding anything helpful in the .trc file.
Our BigFix environment is 9.2.5.130 with the latest versions for all of the OSD items. I’m tempted to upgrade to 9.5.4 but not thinking it will have any impact. I feel like this version just isn’t supported but support hasn’t been able to definitively answer that. when I see the available IBM provided upgrade fixlets for the 2015 edition of windows 10, offered for the 1607 version, none of my machines are relevant, they don’t have a fixlet matching our edition ID of “EnterpriseSN”, which is the LTSB N identifier.
one other bit I figured out while troubleshooting this, the WADK version require to deploy this version of the OS is higher than what BigFix installs, and if you use a stand alone tool like windows image and configuration designer, it requires the higher version to work with it. I’m tempted to remove WADK and install the newer version, but I’d think this would be offered as an upgrade if it were required. knowing how complex the osd environment is makes me reluctant to fiddle with changing out some of the backend manually.