The Generic files actually run and detect other data such as the MSDM stuff etc, it just the SLIC version that it fails on with S2016, very odd indeed. It is not blocked by defender as that is not active during oobe and the files are not deleted.
This looks to be a problem with M$ rather then MRP. Your workaround (that you mentioned earlier) would be a solution until M$ can fix it, if they do. lol Or you come up with another alt.
Testing a alternative.... worked ok in manual testing without fail - just hope it works via OOBE stage now... Test 8 install in progress...
Nope no go again. So for the time being Server 2016/19 will brand but may not activate via SLIC. Nothing i can do about it spent 12hrs on the damn thing already. Tomorrow is another day.
yes and it worked -- well at the time slic 2.5 was not out as such when we tested that. But slic 2.4 was and we got it to work - im sure it posted somewhere...
https://forums.mydigitallife.net/threads/multi-oem-retail-project-mrp-mk3.71555/page-89#post-1394777 knew i got it to work before
So the question to me is whats the difference between 2.4 and 2.5. Obviously something changed. I cant find any info online yet but trying to research what changes were made.
Sent pm to you with info on how to now activate 2016 with slic 2.5 from M$ support. I also sent a suggestion on the "possibility" of activating it. Hope it helps.
Server 2008 - Vista kernel 6.0 Server 2008 R2 - Windows 7 kernel 6.1 Server 2012 - Windows 8.0 kernel 6.2 Server 2012 R2 - Windows 8.1 kernel 6.3 Server 2016 - Windows 10 RS1 (1607) kernel Server 2019 - Windows 10 RS5 (1809) kernel Server 2012 R2 is 8.1 kernel, not 7
Some progress with S2016 activation - i now can get the code to 'see' part of the SLIC [MBINF] #09 SLIC Information : [2.x SLIC table with marker present] But still getting: [NOSLC] No valid SLIC was found for Server OEM activation. I have now 3 methods to detect the SLIC numbering if MRP can only 'see' the '2.' part then it will show the 2.x message as above, the hard part is to make MRP 'see' the SLIC table's other data and attempt to use it to activate with the SLP Key+Cert+SLIC... Sadly i not have a copy of MRP 76/79 that worked originally to compare the code with, but the new 3 methods used should enhance what was being done before and if this test i am installing now fails then i am at a loss at how to fix it at this time as the SLIC is being obscured using every method possible! Install almost at OOBE stage... fingers crossed -- but i am clutching at straws now.
Getting there! Cert copied OK SLP Server2016 ServerStandard Key - Nope... But working on that routine as i think a variable name has changed with all the messing about But if i enter the SLP key for S2016 ServerStandard it activates instantly offline
BTW: it seems not to be related to SLIC 2.5, because my test system does not with SLIC 2.4 as well. Tested with modifies BIOS440 on Player 15 using Phoenix tools 2.73. SLIC 2.4 and SLIC 2.5 are detected and shown in SLIC Toolkit as well.
Other question: can I create an OEM disk for a single machine by copying the cert and branding images to a certain location on the install disk or the install.wim file? Any howto/instructions?
I am attempting to sort out the final piece in the Server puzzle (SLP-Key) for 2.4/2.5 activation. Although Server 2019 Key stuff may be another days project, about sick of servers for the time being As for the Cert and branding it can be done you will need a script to copy the stuff over but i not have the time myself to answer that query but it is quite complex for Windows 10 as you have to edit quite a few permissions on the system controlled images such as lock/login screens (img100 + img105) and then you have the User Account Pictures - that is fun too. I am sure there are tutorials on the net about how it can be done - most will be windows 7/8.x related as that was quite easy compared to Windows 10!
Hmm i got the ServerStandard 2016 SLP key 'Dell' wrong for some odd reason the key was for ServerStandard 2019 SLP Dell no wonder it not activate
reminds me of a qualified engineer i know.. having serviced his car, that was running on lpg and could be switched to run on ordinary fuel by turning a switch, he decided, as the finishing touch, to make it run perfectly on fuel too.. whatever he tried, the good old engine refused to run on fuel.if he had managed to do it, he would be a millionair by now. [he is still trying,lol.] he had run his car on lpg for so long, that all that was left in the fuel tank was condense water..