I have heard through some not so nefarious channels that it was be a
staged removal of attestation signing support in 2016, or for any future
server release. With the exception of Nano which Bill has already
confirmed it does not work.
Pete
–
Kernel Drivers
Windows File System and Device Driver Consulting www.KernelDrivers.com
866.263.9295
------ Original Message ------
From: “Mark Roddy” To: “Windows System Software Devs Interest List” Sent: 3/2/2017 3:35:57 PM Subject: Re: [ntdev] HLK, what the &*$% is going on?
>until it doesn’t of course. > >Mark Roddy > >On Thu, Mar 2, 2017 at 7:48 AM, wrote: >>And, to be clear, contrary to public ally announced policy, >>attestation signing DOES work on Server 2016. >> >>Peter >>OSR >>@OSRDrivers >> >> >>— >>NTDEV is sponsored by OSR >> >>Visit the list online at: >>http:>>http:> >> >>MONTHLY seminars on crash dump analysis, WDF, Windows internals and >>software drivers! >>Details at http: >> >>To unsubscribe, visit the List Server section of OSR Online at >>http:>>http:> > >— NTDEV is sponsored by OSR Visit the list online at: MONTHLY >seminars on crash dump analysis, WDF, Windows internals and software >drivers! Details at To unsubscribe, visit the List Server section of >OSR Online at</http:></http:></http:></http:></http:>
And then, after it stops working and we complain about not having notice of the change, we’ll be told “We told you that attestation signing wouldn’t work for Server 2016 back in November 2016”… even though, contrary to what we were being told, it definitely did work back in November 2016.
I’d like to clarify one point, and then add a complication to the original question:
It seems that after the 90 day limit, you need to run TWO HLK servers, and
test in TWO win 10 builds, to support all win 10 builds.
This is what I glean from that blog, though I could be, hope I am, wrong.
I’ve had this all set up for the last couple of months and I’m running it this way:
HyperV System running 12 VMs
HCK VM (last version they posted) for testing Win7, Win8 and Win8.1
HLK VM (1607 version) for testing Win10 TH2 and Win10 RS1
6 vms for Win7/Win8/Win8.1 (32 and 64 bit)
4 vms for Win10 TH2/Win10 RS1 (32 and 64 bit)
Here comes the trick - You can use the 1607 HLK to test both the RS1 and TH2 machines *BUT* they cannot be run in the same project or you get an error adding the target that says something like “this target is already added”. So you create two projects, add the TH2 machines & targets to one and the RS1 machines & targets to the other.
Of course, then you have to export the HCK package, Merge it into the TH2 package, export the result and then merge that into the RS1 package, export that result *then* you can submit to the new dashboard.
It sounds like a huge pain in the ass but you can script all that into powershell which makes it pretty simple.
Now for the complication; I don’t know if this is going to be necessary with the RS2 build coming out. If it is, I may just lose my mind.
Do you mean to say RS2 will make things less complicated or more complicated? I am hoping it is the former, but you could also mean RS2 will require yet another version of HLK testing.
I also wanted to ask you about your VM’s- I’d like to create the same setup for our driver testing/signing as well, but we sign a few different device-drivers so I am not familiar with how well USB/1394/Gige pass-through is on Hyper-V VMs.
In any case I will be testing out VM’s in the next few days but thought I’d pick your brain while I do it.
> We thought that HLK testing had to be done on physical hardware, because > of what’s written here: > > https://msdn.microsoft.com/en-us/library/windows/hardware/ > jj124068(v=vs.85).aspx > > “Controller isn’t supported in a virtual PC or any third-party Hypervisor > environment.” > > “Test computers are not supported in a virtual PC or any third-party > Hypervisor environment.” > > Have we missed the point here? > > — > NTDEV is sponsored by OSR > > Visit the list online at: http:> showlists.cfm?list=ntdev> > > MONTHLY seminars on crash dump analysis, WDF, Windows internals and > software drivers! > Details at http: > > To unsubscribe, visit the List Server section of OSR Online at < > http://www.osronline.com/page.cfm?name=ListServer> ></http:></http:>
Okay, after some Googling I now understand that Virtual PC in this context is referring to the predecessor to Hyper-V rather than virtual machines in general. It would be nice if the documentation was clearer about this.
Just to let you know, I’m using Hyper-V VMs to test as well, but was having issues with the file system Oplocks testing, only with the Version 1607 64-bit (Windows 10 and Windows 2016).
Ran the tests in a physical machine with Windows 10 version 1607 64-bit and it worked.
From: xxxxx@gmail.commailto:xxxxx Sent: March 23, 2017 7:09 AM To: Windows System Software Devs Interest Listmailto:xxxxx Subject: RE:[ntdev] Re[2]: HLK, what the &*$% is going on?
Okay, after some Googling I now understand that Virtual PC in this context is referring to the predecessor to Hyper-V rather than virtual machines in general. It would be nice if the documentation was clearer about this.