Hello, Evgenie Muzychenko, you wrote: O>> In Server 2016 promise that will not be loaded neither SHA-1-Standard, nor SHA-2-EV. I eat> In sense - at independent (without sysdev) signing? And at sysdev too the Reference I can not find yet, but there wrote that Windows Server 2016 will accept only drivers which transited HLK-tests. That is, probably, the sequence of "signing" of the driver under this edition Win will look somehow so: we put Hardware Logo Kit, we are tested, we receive a file with results, we sign it EV-shnym and it is sent in Microsoft. There they the driver, sign the and return back. A-lja WHQL. O>> dialogue with DigiCert occupied From us three months and in what good as a result did not result. I eat> And at you what problems were? At first, very long. Three months for purchase of any certificate is a search. The person who with them communicated, complained that to it was necessary to transit a heap of any bureaucratic procedures which anywhere, except as in DigiCert, no, well, etc. And as a result refused certificate output, referred on on any ' security criteria '. I any more do not remember Accurate information. Secondly, they strange, these DigiCert. My acquaintance opened , bought from them very quickly. Then they a month later called it and withdrew , returning money, also referred to any trust relationships policies, etc. an USB-token, at a logging in it is necessary to enter into which each time PIN is one more . At us developers are scattered on all the CIS, and a token one. On RDP it normally does not work, PIN it is possible to enter only in local session.