Server 2003 Stan-Ent OEM Files - DELL

Discussion in 'Windows Server' started by Suicide Solution, May 6, 2008.

  1. Liebo

    Liebo MDL Member

    Jul 9, 2009
    thanks again, I saw the change in the first post after my reply to this thread ;)
  2. 5253h

    5253h MDL Novice

    May 16, 2011

    -Does anyone still have these files, or a link to a location I can download them from? I need to convert my VL install of Server 2003 ENT 32bit to an OEM install. Thank you in advance for your assistance.
  3. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
  4. soroka69

    soroka69 MDL Novice

    Dec 7, 2010
    Got mad

    I'm using a Dell Poweredge 840 I need to instal the server 2003 on it.
    Need to convert to Dell OEM...
    I can use the DELL_Server2k3_Trial2OEM.rar
    The hyperlink is no longer work...
    Thank you. Paul.
  5. tnjman

    tnjman MDL Novice

    Nov 30, 2011
    #66 tnjman, Nov 30, 2011
    Last edited: Nov 30, 2011
    sebus - where is the OEM_Files.rar that you mentioned? And is there difference in Ent vs. Std?
    I need only the R2 STD oem files; and I'm not sure if mine is SLP or non-SLP - which seems to be a huge thing that would impact how we would burn the right set of stuff, right?

    I did same exact as you: used 64-bit, downloaded the VLK version both CD1 & CD2 from M$.

    BUT, I did not realize that also you have to change PIDGEN, DCPDLL & - from the top post in the forum, there is only the OEMBIOS files for STD & ENT, and crc.txt & SLP.TXT - I'm very unclear on the exact steps, especially how to modify whatever PID (setupp.ini). I changed the setupp.ini & winnt.sif files, copied those in, but did NOT change any of the pidgen, dcpdll &

    So, My Goal: Take Windows Server 2003 R2 Standard 64-BIT VLK, change it to OEM, so I can use my current/valid COAs, without using up my volume licenses. My COAs are stickers on these Dell 860 boxes, known to be 64-bit capable, and they are valid COAs for W2k3R2 STD 32-BIT, but nothing on the boxes anywhere says that they are real - live OEM, so... but I called Dell & Microsoft and they believe they are OEM product keys.

    So, assuming they are OEM, It would be nice to have ONE SINGLE DOCUMENT (sorry for 'yelling' - lol) - that outlines the steps, exactly, i.e., Step 1, change pid in setupp.ini to be
    a) nnnnOEM for 64-bit R2 2003 STD
    b) nnn2OEM for 32-bit R2 2003 STD
    c) nnn3OEM for 32-bit R2 2003 ENT, etc.
    Step 2, Take the info in the SLP.TXT file and do 'something?' with it - or, is that just for reference?
    Step 3, How do I really know if I have an SLP sever/bios or? how the heck do we tell?
    Step 4, copy the pidgen, dcpdll and files in to your distro
    Step 5, copy the SOMETHING-EULA file into the distro? is this needed?
    Step 5, copy the OEM bios files in to your distro
    Burn, enter valid Lic key,
    Be happy.

    So, is there somewhere with 'precise steps?' If not, that would be a very nice 'sticky' to have! Because the first post at top is nice, but it does NOT have a lot of the other files mentioned that need to be replaced.

    And, per Dell & M$, I don't necessarily have to have any place that says OEM-nnnnn (etc.) for it to be an OEM COA.
    And, [ALLEGEDLY] the COAs should work for either 32-bit or 64-bit, BUT another forum said that [some] COAs are tied to specific class of machine - i.e., might be 32-bit-ONLY COAs.

    [BTW, the recent burn, even without copying in the pidgen and so forth, gets to the point of asking for license, and appears to look like the OEM version, but does not take any of the OEM keys I have, so... again, I'm sure I flubbed up by not copying/changing things the right way]

    All I did - copy OEM* files, winnt.sif & setupp.ini (changing only the setupp.ini file to have the key that 'ss' had at the top of this forum - and it did try to auto-enter that key, and said "no go, dude. key not valid." So I entered my COAs - also, key not valid.

    Any help is greatly appreciated! Thanks from the 'newbie.'
  6. tnjman

    tnjman MDL Novice

    Nov 30, 2011
    Thanks sebus! hoping I can get a 64-bit version of R2 modded & working

    Thanks = I did, indeed, read most of the posts, but not necessarily all the links and so forth.

    But no, I have official Microsoft VLK media - but maybe something I [didnt' do] caused it to change to MSDN???
    I pulled down directly from our Volume Licensing Link on Microsoft's site. Matter of fact, I can use my VLK and activate it, but that costs 'twice,' so as one poster put it, "that's no fun."

    One thing that came to mind: I keep seeing various posts that say, "[BIOS-changer?] Only works on 32-bit R2, and only on Enterprise," but I need 64-bit R2, and Standard. (or maybe I'm misunderstanding, but it looked as if previous posts did indicate that one of the BIOS mod utilities works only on the 32 bit ENT version.

    At any rate, I will take your sage advice and read prev link and also post # 13 - many thanks!

    Also note: my apologies for long post/question - I shall endeavur to read more deeply and to break my queries into snippets that make more sense - you folks do AWESOME work, btw! i know you don't get 'paid' for this, but you should
  7. tnjman

    tnjman MDL Novice

    Nov 30, 2011
    1) Good point(s). Yes, Post #13 (or... 12, actually) - those are the 'first' ones we tried, but obviously, we missed a step (or two), but I am [re]-trying now, so, the post 12-13, that = Trial to MSDN, then I need to do MSDN to OEM, right?

    2) Somewhere it seems there is a step that we need to do where we use a tool to put the "Dell Server; Dell System" piece into the BIOS somehow, I think, after that, then we can use the media, right? (Is that the 'BIOSchanger' part?)
    a) convert trial to MSDN via xdelta3
    b) run the bioschanger
    c) convert MSDN to OEM - copy oem* files, pidgen, winnt.sif, setupp.ini etc. to the distro (change PID to have OEM in it - change prod key)
    d) burn the dvd/cd...

    i will review the additional thread you provided as well. Thanks again - sorry for being newbie-question-guy.
  8. tnjman

    tnjman MDL Novice

    Nov 30, 2011
    Okay, the 'changer' says it is only for Enterprise version. All I have is 'Standard;' I will give it a try, BUT both the 'mirror' and 'fileden' are down, so... whenever they (hopefully) come back, then I can try this.

    Since I am going from a valid, downloaded VLK, I actually should be able to skip the 'xdelta3' step, I think.
    But again, I just never did copy the pidgen, and other files mentioned (and those are not included in the initial forum post, so again, it is somewhat confusing - apparently, there is an "OEMfiles.rar" that has those DLLs and so forth, right?) - I'm going back through all the posts and threads now, so I can "read more deeply", and I never ran the 'bioschanger' either, so I think those are the only steps I missed.

  9. sebus

    sebus MDL Guru

    Jul 23, 2008
    #73 sebus, Dec 1, 2011
    Last edited by a moderator: Apr 20, 2017
  10. tnjman

    tnjman MDL Novice

    Nov 30, 2011
    Okay, I re-ran the delta against the trial, no errors, but it doesn't give any display, like in the "Code: " part, where you guys are showing the "before and after" in your examples. But no errors should mean okay, right?

    1) Where to get the DCPCLL.DL_, PIDGEN.DLL? Or do I even need to change those? (from that OEMfiles.rar that someone mentioned?)
    2) Will your OEMBIOS files work just fine, even on 64-bit - the system doesn't care, right? (seems like you said they should work on either)
    3) Do I need an altered - or that is one I don't have to change - leave as-is, right; since it already is from a Std version?

    I'm changing the delta (which is now, I guess, MSDN) and copying in your OEMBIOS files, and changing setupp.ini
    I think I also have to change Winnt.SIF, right? I'll make sure it says the OEM-style, like in your download (and the G78PD key)
  11. tnjman

    tnjman MDL Novice

    Nov 30, 2011
    UPDATE: Thanks to the patience of sebus, it worked! Well, okay, it did NOT accept any of the COA's I have so far, it said "invalid key," so I am thinking those are tied definitely to 32-bit version, maybe? So, I had to use the "generic SLP key" for W2k3 Server R2 64-bit as found on a public wiki page. Not sure why the generic keys are posted there - will see if any of that hinders activation - but per Dell / Microsoft licensing, I should be able to use either 32-bit or 64-bit. THANK YOU 'sebus.' !