Windows Server 2003 Standard R2 SP2 OEM iso hash

Discussion in 'Windows Server' started by MBaNL, Mar 7, 2012.

  1. MBaNL

    MBaNL MDL Novice

    Oct 6, 2011
    7
    0
    0
    #1 MBaNL, Mar 7, 2012
    Last edited: Mar 8, 2012
    Does someone knows the hash for "CRMSOEM_EN"? Cant find a hash on the web anywhere and the ISO I have (read: made) makes an hash that could not be found with Google.

    If someone has the ISO and could provide me the hashes it would be great... :)

    EDIT: If someone could provide me a delta file for turning "en_win_srv_2003_r2_standard_with_sp2_cd1_x13-04790.iso" into the OEM iso it would be even better...
     
  2. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,502
    3,611
    120
    #2 FreeStyler, Mar 8, 2012
    Last edited: Mar 8, 2012
    You never get an identical hash when you make one yourself as the real MS version is a signed version (seems MS signed Server 2003 ISO's, and apparently XP ISO's not)
    Anyway, think you are out off luck, official OEM:COA CRMSOEM_EN version never got leaked, so it's hashes are unknown
     
  3. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,502
    3,611
    120
    BTW, the reason I say MS (probably) signed the Server 2003 ISO's is the fact i can reproduce an exact, 100% identical to MSDN version of my Windows XP Professional Vl build using CDImage 2.52p but i can not do the same for a retail version of MSDN Windows Server 2003 R2 SP2, somehow the resulting hashes are always different than the MSDN Windows Server 2003 R2 SP2 hashes.
     
  4. MBaNL

    MBaNL MDL Novice

    Oct 6, 2011
    7
    0
    0
    Remaking "en_win_srv_2003_r2_standard_with_sp2_cd1_x13-04790.iso" is fairly simple and exactly the same procedure as XP SP3 (even the boot sector is the same)... No signature in the image (Like NT 4.0 had).

    Down to the EULA.TXT (EULAID:WS03SP2_RM.0_SRV-ENT_OEM_EN) file I suppose I got all the original files.

    The list of the files I replaced (with their SHA1 hashes):
    I386\DPCDLL.DL_ (1957cda29cfc2b2f0eae7a27282ce47ba59b0220)
    I386\EULA.TXT (6ab6518198ceeced42561833c3a9d8a749cd9c06)
    I386\OEMBIOS.BI_ (bb062a3c8c3cbf727d3884a466ca2b2c5e23902c)
    I386\OEMBIOS.CA_ (0a33d0d1eaf768147dd99a1f3180cd20bb7b1d5d)
    I386\OEMBIOS.DA_ (70f71f7b976258bdc450fc9e1623997390e2a1ad)
    I386\OEMBIOS.SI_ (885fdcefd2a542748990c988e4e01e9d3bfce0dc)
    I386\PID.INF (ce08d14138e7c759dfd3248828e5c746e2dc5d3e)
    I386\PIDGEN.DLL (89f4b670ef19f2ee38a1c0127f0ff66ec5bc6c85)
    I386\SETUPP.INI (a9ee00e3d727db113c1fdefba993cb6c659dcc46)
    I386\SETUPREG.HIV (992ab031c24575aac010deb81e7c497fd3f439b1)
     
  5. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,502
    3,611
    120
    #6 FreeStyler, Mar 8, 2012
    Last edited: Mar 8, 2012
    I never managed to do so, always is a few bytes off, so what is your secret?


    FYI:
    You can grab the OEM EULA from disc 2

    I386\OEMBIOS.BI_ (bb062a3c8c3cbf727d3884a466ca2b2c5e23902c) (Not needed, already using Retail, not VLK as BASE image)
    I386\OEMBIOS.CA_ (0a33d0d1eaf768147dd99a1f3180cd20bb7b1d5d) (Not needed, already using Retail, not VLK as BASE image)
    I386\OEMBIOS.DA_ (70f71f7b976258bdc450fc9e1623997390e2a1ad) (Not needed, already using Retail, not VLK as BASE image)
    I386\OEMBIOS.SI_ (885fdcefd2a542748990c988e4e01e9d3bfce0dc) (Not needed, already using Retail, not VLK as BASE image)
    I386\DPCDLL.DL_ (1957cda29cfc2b2f0eae7a27282ce47ba59b0220) (Not needed, already using Retail, not VLK as BASE image)
    I386\SETUPREG.HIV (992ab031c24575aac010deb81e7c497fd3f439b1) (Not needed, already using Retail, not VLK as BASE image)
    I386\PIDGEN.DLL (89f4b670ef19f2ee38a1c0127f0ff66ec5bc6c85) (Not needed, already using Retail, not VLK as BASE image)

    And what about?

    ACC_DIS.CH_
    ACCESSIB.CH_
    IESUPP.CH_
    IEWEBHLP.CH_
    SUPP_EDS.CH_
    UNATTEND.TXT

    These files are also reported to be different between retail/oem (Compared it to Dell OEM version, here)
     
  6. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,043
    701
    60
    #7 Oz, Mar 8, 2012
    Last edited by a moderator: Apr 20, 2017


    Code:
    CDIMAGE-2.52 -nt -o -xx -bboot.bin -g224 -t2/18/2007,12 -lCRMSFPP_EN CRMSFPP_EN en_win_srv_2003_r2_standard_with_sp2_cd1_X13-04790.iso
     
  7. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,502
    3,611
    120
    #8 FreeStyler, Mar 8, 2012
    Last edited by a moderator: Apr 20, 2017
    Hey, thanks man!
    Seems to be related to the '-g224' switch, working fine now

    I think i have all files needed to re-create a OEM:COA CRMSOEM_EN disc, except for 1 file

    The DELL version has a modified UNATTEND.TXT, holding it's OEM:SLP key
    My FUJITSU-SIEMENS version also has a modified UNATTEND.TXT.... at least I think it does, as there is no key, eg: ProductKey = ""

    [EDIT] FUJITSU-SIEMENS UNATTEND.TXT proves to be the real one

    Code:
    37a7813e7ec415e727cc5083e374800c *I386\ACC_DIS.CH_
    50a8280ea2f0550301fefb990509276c *I386\ACCESSIB.CH_
    dc902311775f461a45be8a026b780a24 *I386\EULA.TXT
    181857fbb262aef980065e1940916171 *I386\IESUPP.CH_
    50a5d01eaffb0c2645a7e6181246283d *I386\IEWEBHLP.CH_
    008c200de99d7f200c4317e04a2537ec *I386\PID.INF
    e417b6c0ca3d33d71cc97c3006992bfa *I386\SETUPP.INI
    a0cfa89065cd483ff33156d46ed73b7d *I386\SUPP_EDS.CH_
    a45aa976ac8c51e56df068234ffd9d8c *I386\UNATTEND.TXT
    
    
     
  8. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,043
    701
    60
    #9 Oz, Mar 8, 2012
    Last edited by a moderator: Apr 20, 2017
    Delete the product key in-between quotes in unattend.

    Seems on OEM, it is left that way. Have a look at the XP x64 OEM I had deltas for a while back

    Delete WINNT.SIF
    Replace OEMBIOS with FPP.


    Code:
      File: CRMSOEM_EN.iso
    CRC-32: ffffffff
       MD4: b24213bce0de9e6404a97d919982975f
       MD5: 06c62b07562fa11b39f9ad858672640f
     SHA-1: c21295ad34725054b5a7b3825abdda79ac452376
    
    If you Google MD5 you get a match ;)
     
  9. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,502
    3,611
    120
    Thx, my build now has the same hashes as yours
     
  10. MBaNL

    MBaNL MDL Novice

    Oct 6, 2011
    7
    0
    0
    Thanks Oz! Got the same hashes and found the page with the MD5 hash you mentioned.
     
  11. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,502
    3,611
    120
    #12 FreeStyler, Mar 8, 2012
    Last edited by a moderator: Apr 20, 2017

    Attached Files:

  12. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,043
    701
    60
    If someone has:

    Feel free to join the party.
     
  13. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,834
    1,748
    180
    #14 sebus, Mar 9, 2012
    Last edited by a moderator: Apr 20, 2017
    OK, not with SP2, but:

    Code:
    Windows Server 2003 R2 Standard
    BX2SOEM_EN.iso
    600,559,616 bytes
    
    CRC32: FFFFFFFF
    MD5: 6FD9B75B54BD73A9490114F5D9B90FC6
    SHA-1: E96AEB17FF5397FA9BF77AB1CA83776C15370DD7
    
    
    sebus
     
  14. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,502
    3,611
    120
    #15 FreeStyler, Mar 9, 2012
    Last edited: Mar 9, 2012
    @Oz, i got the feeling only PID.INF and SETUPP.INI are the files that differ for 'CRMEOEM_EN.iso'

    If i for example compare ACC_DIS.CH_ taken from Retail Enterprise with the one from Retail Standard they are both binary the same, this is the same for all other *.CH_ files
    So most likely this also is the case in the OEM images, meaning the only difference is to be found in PID.INF and SETUPP.INI
     
  15. MBaNL

    MBaNL MDL Novice

    Oct 6, 2011
    7
    0
    0
    #16 MBaNL, Mar 9, 2012
    Last edited: Mar 9, 2012
    (OP)
    @FreeStyler, when I compare "CRMSFPP_EN", "CRMSOEM_EN" and "CRMEFPP_EN" than it's exactly the same conclusion. Unattend.txt is also different between S and E but since the key is not in the OEM version and that's the only difference between S and E I suppose we could use the OEM file.

    This would mean that we need to know:
    The "StagingKey" for PID.INF and;
    the "Pid" for SETUP.INI

    although the last one seems to be simple...
    CRMSFPP_EN = Pid=69712000
    CRMEFPP_EN = Pid=69713000
    CRMSOEM_EN = Pid=69712OEM

    So I think:
    CRMEOEM_EN = Pid=69713OEM

    That leaves us with the "StagingKey"... anyone?

    EDIT: something about the UNATTEND.TXT file...

    the Enterprise Edition (as well the Retail version as the Evaluation) had more spaces between "ProductKey" and "=" than the Standard Edition. So I suppose we need to use the Enterprise Edition file without the key... something to keep in mind if we could find the "StagingKey"...
     
  16. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,043
    701
    60
    #17 Oz, Mar 9, 2012
    Last edited: Mar 9, 2012
    @FreeStyler

    I did make a Dell Enterprise 2003 SP2 x86 a while back and it worked fine, pre-activated, just don't have the real thing.

    @MBaNL

    Yes, the genuine PID is the problem, and since Microsoft always tells us to only use genuine software.....
     
  17. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,834
    1,748
    180
    #18 sebus, Mar 9, 2012
    Last edited by a moderator: Apr 20, 2017
    The size is correct, just checked my iso

    Code:
    en_win_srv_2003_r2_standard_x64_cd1.iso
    
    649,490,432 bytes
    
    CRC32: FFFFFFFF
    MD5: E7C31EF556396DA7E2AA9A8F3C2CA7C3
    SHA-1: B42F7C67F319FBA737809886D29FE6C1D1A34003
    
    sebus
     
  18. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,043
    701
    60
    50MB Smaller than the retail version?

    Doesn't look right.
     
  19. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,834
    1,748
    180
    It IS right, my iso is from Technet, and BX2SXFPP_EN is retail

    sebus