Posted by RvdH under Computer & Peripherals  on May 22 2010

This utility is a successor of the 'Vista OEM Activation Backup' i crafted up in 2008. OEMDump is designed to make a backup of everything needed to do a clean install of Windows Vista, Windows 7 or Windows Server 2008 (R2) allowing you still be able to use the OEM preactivation Mechanism. 

Updated version available, see:
OEMDump Windows 2012 (R2) Compatible
 

What is OEMDump?



The program will backup the following files:

* OEM Certificate
* OEM SLP Product Key
* OEM SLIC

What is needed to successfully use this program?

A OEM vendor system that came pre-installed with Windows Vista, Windows 7 or Windows Server 2008 (R2). You can check if your system is preactivated by using Microsoft MGADiag.



If MGADiag reports your systems Product ID Type as: OEM SLP your system uses the preactivation mechanism and you are good to go.

Further system requirements

  • Microsoft Windows Vista, Windows 7 or Windows Server 2008 (R2)
  • Administrator Privileges to execute the program

How to use these files after a clean install?

  • During Windows setup use the backup product key
     
  • After setup completes import the OEM Certificate by running this command from a Command Prompt started with Administrator Privileges: (right click -> Run as administrator)
    C:\Windows\System32\cscript slmgr.vbs -ilc [PATH to XRM-MS File]
  • The BIOS SLIC table is not really required to re-preactivated your system, i included it just for safekeeping incase a BIOS update makes you loose activation.
Download:
OEMDump.zip

Credits for this utility go out to MasterDisaster @mdl

Tagged Windows  Activation  OEM 
share the love!



comments


just a little typo.
C:\\Windows\\System32\\cscript slmgr-vbs -ilc [PATH to XRM-MS File]

in the line above it should be C:\Windows\System32\cscript slmgr.vbs -ilc [PATH to XRM-MS File]

(note the . instead of - )

posted by tim at 9/4/2015 12:33

When I was upgrading win 10, it had some problem and failed. Then it started talking that it's not genuine.

The problem seems that the slic file is gone. How can I use BIOS slic table. Fortunately, I had backed up the Bios slic table.

posted by dustwhirl at 8/8/2015 14:21

You definitely know how to code utilities!
I run a computer repair shop and I often need to restore activated OEM loads. Having a repository of certs and keys is easy as they are readily available, however, a command line unattended way to restore OEM activation for all brands is needed in that it would save time and could even be made part of the OS install.
I've put just such a script together using your OEM Dump utility. Only your utility will essentially report the slic level from the command prompt. With this I can run one script and, if the key and cert are on file, correctly and quickly re-activate a Windows Vista or 7 OS reload.
Of course, in this case, I have to parse the .BIN file name to get teh info what I need.
Have you ever thought about a command line utility that would report just the BIOS slic level?
I'm thinking it would simply report 2.0 or 2.1 or none. either echoing to the console or populate an environment variable.
What do you think?
Also, do you know if there is a way to determine the slic level of a cert file just by examing the contents?


posted by SRBISHB at 10/31/2011 19:52

tnx very much


posted by solution at 3/23/2011 22:26

it's really useful!
thank you


posted by xain at 10/17/2010 12:12



post your comment

 (*) - required