This is easy way. However, with the great help from @sk00ter , @pottzman and @UruWay Trek , i was able to calculate myself. It is the most comprehensive tool to generate keys for a broad range of MS products. And, more important it was before UMSKT and others.
Hiya @un user PID is interesting, but "EE" is not BINK id. And "***" -> Random value based on time. I don't know to be honest... maybe. I have oem:slp's that states different. Would be cool to have a discussion on this. Amen to that.
Went over my head that the R2 is x86 when the non-R2 is x64. For Non-R2, doing "umskt.exe -b 68 -c 313" with 313 based on your validation above works. How did you get that output above? umskt just says validated, not detailed info. Also, how can I find the correct channel for R2 x86 Storage server?
Still listed: In PRODSPEC.INI - Windows Server 2003, Standard Edition In EULAID - WS03R2_RM.0_STD-ENT_RTL_EN Code: 4cf9f19406a0a5319642151d7c08724ca6eaeba5 *en_win_srv_2003_r2_standard_cd1.iso BRMSFPP_EN 20051130 It was replaced by: Code: a8e7ee732bcda9a2d7cd70ae59e105fa71b92d29 *en_win_srv_2003_r2_standard_cd1.iso BX2SFPP_EN 20060322 PID ranges - if you "Import BINK" in Elliptic Curve Tool using pidgen from image (pidgen was not changed in these two images) you get: Code: Found Valid BINK Resources located at offset address 0x6F40 in the file... E:\PIDGEN.DLL. Resources for BINK ID54 have been saved. Resources for BINK ID55 have been saved. Resources for BINK ID58 have been saved. Resources for BINK ID59 have been saved. One or more Product ID Ranges found | Blacklisted | BINKID | Pid Minimum | Pid Maximum | |-------------|--------|-------------|-------------| | No | 54 | 012-000000 | 065-999999 | | No | 54 | 084-000000 | 084-999999 | | No | 54 | 347-000000 | 351-999999 | | No | 54 | 367-000000 | 369-999999 | | No | 54 | 763-000000 | 766-999999 | | No | 54 | 779-000000 | 780-999999 | | No | 54 | 783-000000 | 784-999999 | | No | 54 | 789-000000 | 789-999999 | | No | 55 | 119-002000 | 119-002999 | | No | 55 | 119-006000 | 119-006999 | | No | 55 | 163-000000 | 163-999999 | | No | 55 | 170-000000 | 269-999999 | | No | 58 | 012-000000 | 065-999999 | | No | 58 | 085-000000 | 086-999999 | | No | 58 | 087-000000 | 088-999999 | | No | 58 | 089-000000 | 090-999999 | | No | 58 | 099-000000 | 100-999999 | | No | 58 | 103-000000 | 104-999999 | | No | 58 | 296-000000 | 300-999999 | | No | 58 | 783-000000 | 784-999999 | | No | 58 | 792-000000 | 792-999999 | | No | 58 | 794-000000 | 794-999999 | | No | 59 | 119-002000 | 119-002999 | | No | 59 | 119-007000 | 119-007999 | | No | 59 | 119-008000 | 119-008999 | | No | 59 | 119-009000 | 119-009999 | | No | 59 | 119-011000 | 119-011999 | | No | 59 | 170-000000 | 171-999999 | | No | 59 | 172-000000 | 173-999999 | | No | 59 | 174-000000 | 175-999999 | | No | 59 | 178-000000 | 179-999999 | | No | 59 | 180-000000 | 269-999999 | | No | 59 | 271-000000 | 280-999999 | |-------------|--------|-------------|-------------| Code: 08aea0ff734899a6c649ee97449586df843542ad *en_win_srv_2003_r2_enterprise_x64_cd1.iso BRMEXFPP_EN 20051130 Have not checked it's updated equivalent here (yet) but the one listed here list's following PID ranges: Code: Found Valid BINK Resources located at offset address 0x10D40 in the file... E:\PIDGEN.DLL. Resources for BINK ID68 have been saved. Resources for BINK ID69 have been saved. Resources for BINK ID6C have been saved. Resources for BINK ID6D have been saved. One or more Product ID Ranges found | Blacklisted | BINKID | Pid Minimum | Pid Maximum | |-------------|--------|-------------|-------------| | No | 68 | 071-000000 | 082-999999 | | No | 68 | 089-000000 | 090-999999 | | No | 68 | 095-000000 | 095-999999 | | No | 68 | 301-000000 | 305-999999 | | No | 68 | 313-000000 | 314-999999 | | No | 68 | 321-000000 | 330-999999 | | No | 68 | 786-000000 | 787-999999 | | No | 69 | 119-004000 | 119-004999 | | No | 69 | 119-009000 | 119-009999 | | No | 69 | 232-000000 | 261-999999 | | No | 69 | 277-000000 | 278-999999 | | No | 6C | 071-000000 | 082-999999 | | No | 6C | 090-100000 | 092-099999 | | No | 6C | 300-000000 | 309-999999 | | No | 6D | 119-004000 | 119-004999 | | No | 6D | 232-000000 | 261-999999 | |-------------|--------|-------------|-------------| It's updated equivalent (no changes in pidgen) Code: 5e42321ff851f13fcb66290c4594ad0b93e5106e *en_win_srv_2003_r2_enterprise_x64_cd1.iso BX2EXFPP_EN 20060322
Question is, how do you pick the correct | No | 58 | 103-000000 | 104-999999 | range instead of the others? Or simply try each range if it works?
Updated previous post with re-released Enterprise edition SHA-1 To be honest, i dunno exactly how this is performed - hoping @pottzman have some additional info here. What i do know is: Full Version Volume R2 - BINK 0x5A CID 651 (a legal volume key from past work) Full Version Retail - BINK 0x56 CID 006 (a evaluation key - 180 days) Both need their own specific image/BINK