R2 and non-R2 changer Does someone have a copy of the R2 and non-R2 version of the 2003 changer? The 1st post's links are no longer valid. Thanks
If anybody does have a copy of the changers, please upload them. I seem to have misplaced the script files and the las I had were on the server here...PM is good also.. Thanks
It turned out that my conversion archive (not 911medic's) had bad values for SETUPP.INI. Once I replaced the last 3 characters of Pid with OEM the conversion was successful.
Thanks, the xp ones I have..I am looking for the server 2003 changers I posted. I lost a harddrive and these were on it...Not sure where the backup is.
Thanks for the HP one and the r2 detector. I also need the generic 2k3 changer if someone has it..Thanks again!!
Just so you know, I've been able to activate a Windows Server 2003 R2 Standard Edition with this tool (Server_2k3_Enterprs_R2_HP_Activatr.exe, MD5 3a0f50f2bbae1a13a4c73a934ca7fb33), confirmed as activated by XP_Activatn_OOBE_Check.exe, running in ESXi 4.1 with an HP patched BIOS.
Hi, sorry for being dense, but I can't work out what I'm supposed to be running in this tool. I have the tool downloaded and extracted, and I have checked my SLP version and put the correct four OEMBIOS files in the uncompressed directory. But now the instructions say to "Run the VLK_TO_OEM executable file.", but which file is this? There are several executables in the VLK_TO_OEM folder, but none of them appear to do anything. There is an OEM.exe but this does nothing either? I'm certain i'm missing something obvious, but i have no idea what. Help would be much appreciated, thanks.
When you extract the OEMBIOS changer.7z archive just run the OEMBIOS changer.exe select your destination folder I put in C:\OembiosChanger the file you need to run once you have copied oembios files to folder is called OEM.CMD
911 Thanks for updated links, may i suggest that you change the winrar.sfx so it installs to a folder older versions installed to C:\ OEMBIOS changer at the moment if user uses the default path C:\ it puts folders all over the c:\ drive
Okay, i ran OEM.CMD, but it gives me error messages about not finding registry values. So I looked at what the cmd file is checking for, and the 'CSDVersion' and 'PID value' registry keys aren't present on my system. Is there a workaround for this?
Add them. You have SP0?? I looked into adding them to the tool, but it is to much grief. You can run SP1-3.. You can also use dobbelina's script at the bottom of the first post..it is just a basic script. I (You) can make you a script for the OEMBIOS files and you add the serial manually??