Windows Server 2003 Standard R2 SP2 OEM iso hash

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

Page 2 of 2
  1. sebus

    sebus MDL Guru

    Jul 23, 2008
    6,356
    2,026
    210
    #21 sebus, Mar 9, 2012
    BX2SXFPP_EN is not OEM
     
  2. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
    #22 Oz, Mar 9, 2012
    Sorry got the 64 and 86 version mixed up, not used to two X's in label.
     
  3. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,557
    3,832
    120
    #23 FreeStyler, Mar 10, 2012
    Last edited by a moderator: Apr 20, 2017
  4. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
    #24 Oz, Mar 10, 2012
    Last edited by a moderator: Apr 20, 2017
    Did this a while back.

    This is what I ended up with, using the FPP PID.INF:

    Code:
      File: en_win_srv_2003_r2_enterprise_with_sp2_cd1_X13-_OEM_.iso
CRC-32: ffffffff
  SIZE: 595 MB (624,517,120 bytes)
   MD4: 4cd285501c7d838aa66457e28d71703c
   MD5: 7e5efef6079e600bc5db89276f5a7621
 SHA-1: 0e8953d1fd86e191d4813b74c38cddc2cfc52255
     
  5. MBaNL

    MBaNL MDL Novice

    Oct 6, 2011
    7
    0
    0
    #25 MBaNL, Mar 10, 2012 (OP)
    @Oz, got the same here when also using the FPP PID.INF...

    Yesterday I tried to look trough the files from SP2 and found PID.INF files but none of them had the "StagingKey" filled in... So i suppose the place to look for this key is just the real media or at least a copy of that...
     
  6. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,557
    3,832
    120
    #26 FreeStyler, Mar 10, 2012
    Last edited by a moderator: Apr 20, 2017
  7. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
    #27 Oz, Mar 10, 2012
    Some x64 ENT/STD OEM's would be better ;)
     
  8. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,557
    3,832
    120
    #28 FreeStyler, Mar 13, 2012
    Last edited by a moderator: Apr 20, 2017
  9. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
    #29 Oz, Mar 13, 2012
    Didn't actually install it as it was, changed it to a Dell version and used it in VPC.

    Don't have my hard drive with all the ISO stuff hooked up right now, but those keys on MS site, they are not the StagingKeys right? Just vanilla OEM.
     
  10. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,557
    3,832
    120
    #30 FreeStyler, Mar 13, 2012
    OEM:SLP, so with right oembios set & SLP string it preactivates automaticly
    With FPP PID.INF you can not skip COA Dialog, setup won't continue (the retail key isn't accepted as we altered SETUPP.INI, it expects a OEM key)
     
  11. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
    #31 Oz, Mar 13, 2012
    Last edited: Mar 13, 2012
    Yeah, didn't have that problem, since I tossed in a WINNT.SIF with a Dell SLP key

    EDIT

    Yep, getting same sums:

     
  12. stream

    stream MDL Member

    Nov 5, 2010
    206
    104
    10
    #32 stream, Mar 14, 2012
    A question:

    How did you arrive at these values using CRMSOEM_EN as the source?

    Thanks in advance.
     
  13. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,557
    3,832
    120
    #33 FreeStyler, Mar 14, 2012
    Last edited by a moderator: Apr 20, 2017
  14. mathijn75

    mathijn75 MDL Novice

    Dec 20, 2012
    6
    0
    0
    #34 mathijn75, Jan 31, 2013
    Freestyler,
    You have a HP Windows Server 2003 Standard R2 SP2 installation disc? I am looking for it...
    Have a Compaq Proliant ML350 G5 (with OEM COA) that I need to reinstall, but can not find any installation disc in my archives.
    I checked this forum to create one myself, but in fact I can not follow how to do it. Can you help me?
     
  15. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
    #35 Tito, Jan 31, 2013
  16. pottzman

    pottzman MDL Member

    Dec 8, 2009
    143
    105
    10
    #36 pottzman, Aug 15, 2021
    So based on the info you can find that is readily available you can see that

    Windows Server 2003 Standard R2 with SP2 Retail PID.INF ProductKey has a ProductID of "XXXXX-783-0120004-44737" based on a Valid Pid Range between 783-000000 & 784-999999
    Windows Server 2003 Standard R2 with SP2 Retail Unattended.txt ProductKey has a ProductID of "XXXXX-012-0000545-42007" based on a Valid Pid Range between 012-000000 & 065-999999 <------- Seems to be a Non R2 key

    &

    Windows Server 2003 Enterprise R2 with SP2 Retail PID.INF ProductKey has a ProductID of "XXXXX-786-0120004-44356" based on a Valid Pid Range between 786-000000 & 787-999999
    Windows Server 2003 Enterprise R2 with SP2 Retail Unattended.txt ProductKey has a ProductID of "XXXXX-071-0000545-42971" based on a Valid Pid Range between 071-000000 & 082-999999 <-------- Seems to be a Non R2 key

    &

    Windows Server 2003 Standard R2 with SP2 OEM PID.INF ProductKey has a ProductID of "XXXXX-OEM-4418004-53925" based on a Valid Pid Range between 170-000000 & 269-999999
    Windows Server 2003 Standard R2 with SP2 OEM Unattended.txt No ProductKey

    So

    Windows Server 2003 Enterprise R2 with SP2 OEM PID.INF ProductKey has a ProductID of "What do you think it should/could be?" based on a Valid Pid Range between 140-000000 & 160-999999
    Windows Server 2003 Enterprise R2 with SP2 OEM Unattended.txt No ProductKey
     
Page 2 of 2