Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Building a Pre-activated CD from an existing installation

* * * * - 2 votes

  • Please log in to reply
179 replies to this topic

#126
Bezalel

Bezalel

    Senior Member

  • Member
  • PipPipPipPip
  • 591 posts

Is it possible (even in PM) to get public installation keys for XP HOME, XP MCE and SBS 2003 (R2)? on M$ link i found only XP PRO and TABLET... Many Thanks


There are no publicly released keys for the other OSs. Microsoft expects IT department to be constantly installing Windows XP Pro so thay have released those keys. They don't expect home users to constantly be installing home OSs or businesses to be constantly installing server OSs.

You will need to extract these keys from a working system or learn how to use Google.


How to remove advertisement from MSFN

#127
sgufa

sgufa

    Newbie

  • Member
  • 10 posts
I know but i'm finding slp key and oembios for sbs2003. Please help me in any way...

#128
visa tapani

visa tapani

    Newbie

  • Member
  • 18 posts
I tried this yesterday and couldn't get it to work, I'd really appreciate some help here.

I have an asus laptop with just recovery discs and I wanted to install clean without the bloat coming with them. So I got a Windows XP disc from a friend (a proper hologrammed retail version afaik), the same type (Pro) and language as the one shipping with the notebook. I copied the content to HD, overwrote the OEMBIOS.BI_, OEMBIOS.CA_, OEMBIOS.DA_, OEMBIOS.SI_ and winnt.sif in the I386 folder with the files gotten from the method described by Bezalel on page 1.

After this I ran the XP through some nLiting, incorporated SP2, removed some content, filled the right details in its unattended page, did other small adjustments and burned it to disc. However, after I had wiped my HD clean and started installing, everything went fine until to my surprise it asked for product key! Even worse, none of the keys I could think of worked. First I of course tried the real product key of my laptop facotry installation (the one that the Magical Jelly Bean Keyfinder reports and which was written to the winnt.sif) but it didn't work. Then I tried the product key on the bottom of my laptop and the product key found on this webpage, neither of which worked.

What have I done wrong? Could it be that the nLiting broke the installation somehow? When entering the 'unattended' stage it reported that there is previous unattended information in the installation which might be lost. I figured that this only refers to the unattended configuration, and does not break it. Should it work if I skip the unattended stage of nLite or have I misunderstood something about the whole process?

#129
uid0

uid0

    Advanced Member

  • Member
  • PipPipPip
  • 356 posts
After nlite has done its business, put your OEM key back in the winnt.sif, and all should be fine.
The key from the bottom of the laptop will not work - it has to be the original OEM one.

#130
visa tapani

visa tapani

    Newbie

  • Member
  • 18 posts
Thanks for the tip!

However, after nLite is finished, the proper OEM key *is* in the winnt.sif -but it still doesn't work.

This is how the winnt.sif looks after the whole thing is done:

; Generated by nLite 1.3.5

[Data]
AutomaticUpdates="No"
Autopartition=0
FloppyLess=1
MsDosInitiated=0
UnattendedInstall="Yes"

[Unattended]
UnattendMode=DefaultHide
UnattendSwitch="Yes"
OemPreinstall="Yes"
OemSkipEula="Yes"
FileSystem=*
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

[SystemRestore]
DisableSR=1
CreateFirstRunRp=0

[GuiUnattended]
EncryptedAdminPassword="No"
AutoLogon="Yes"
OemSkipWelcome=1

[Shell]
DefaultThemesOff="Yes"

[Components]

[UserData]
ProductKey="Q9RV4-G448X-F4WJP-F69MX-XXXXX"
ComputerName=ASUS_NOTEBOOK

[RegionalSettings]
Language= "040b"

[Networking]
InstallDefaultComponents="Yes"



This is how the winnt.sif looks like after generated by the getfiles.bat by Bezalel's method:

[UserData]
ProductKey="Q9RV4-G448X-F4WJP-F69MX-XXXXX"
[Data]
MSDosInitiated=0
UnattendedInstall=Yes


So it just seems nLite has added some extra parameters, but hasn't broken anything important. Also I just looked through the OEMBIOS.BI_, OEMBIOS.CA_, OEMBIOS.DA_ and OEMBIOS.SI_ filesizes of the finished nLited XP installation and they seem to be equal to those generated byt the getfiles.bat, suggesting that nLite hasn't modified them...

Could it be that I need to overwrite/modify more files of the FPP retail XP I386 folder than those aforementioned 5? In this thread jdboeck said that if you want to make a OEM preactivated XP cd from a FPP retail cd, you need to copy these 8 files from your recovery disc: "dpcdll.dll, oembios.bin, oembios.cat, oembios.sig, oembios.dat, setupp.ini, pidgen.dll, setupreg.hiv". So in addition to the files discussed here I'd need dpcdll.dll, setupp.ini, pidgen.dll and setupreg.hiv, is this true?

For example regarding the setupp.ini I found this in a guide once:
"So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read:
Pid=51882335
And if you wanted a retail CD that took OEM keys, you'd use:
Pid=51882OEM"


Could this be the reason why my installation disc refused the OEM key I gave it - it is customed to only accept retail keys? This is how the setupp.ini of the final cd looked like:

[Pid]
ExtraData=7573666361697474646DC3545CBB62
Pid=55697270


In contrast, this is how the setupp.ini of my recovery disc looks like:

[Pid]
ExtraData=786F687170637175716954806365EF
Pid=76409OEM


I'm getting a bit confused by all this... If I'd just copy dpcdll.dll, setupp.ini, pidgen.dll and setupreg.hiv from the I386 folder of my recovery cd to the I386 folder of the retail XP I'm installing from (in addition to the OEMBIOS.BI_, OEMBIOS.CA_, OEMBIOS.DA_, OEMBIOS.SI_ and winnt.sif files gotten with Bezalel's getfiles.bat) would it just solve my problem?

Any help is greatly appreciated!

Edited by visa tapani, 20 July 2007 - 08:01 AM.


#131
Bezalel

Bezalel

    Senior Member

  • Member
  • PipPipPipPip
  • 591 posts

I tried this yesterday and couldn't get it to work, I'd really appreciate some help here.

I have an asus laptop with just recovery discs and I wanted to install clean without the bloat coming with them. So I got a Windows XP disc from a friend (a proper hologrammed retail version afaik), the same type (Pro) and language as the one shipping with the notebook. I copied the content to HD, overwrote the OEMBIOS.BI_, OEMBIOS.CA_, OEMBIOS.DA_, OEMBIOS.SI_ and winnt.sif in the I386 folder with the files gotten from the method described by Bezalel on page 1.

After this I ran the XP through some nLiting, incorporated SP2, removed some content, filled the right details in its unattended page, did other small adjustments and burned it to disc. However, after I had wiped my HD clean and started installing, everything went fine until to my surprise it asked for product key! Even worse, none of the keys I could think of worked. First I of course tried the real product key of my laptop facotry installation (the one that the Magical Jelly Bean Keyfinder reports and which was written to the winnt.sif) but it didn't work. Then I tried the product key on the bottom of my laptop and the product key found on this webpage, neither of which worked.

What have I done wrong? Could it be that the nLiting broke the installation somehow? When entering the 'unattended' stage it reported that there is previous unattended information in the installation which might be lost. I figured that this only refers to the unattended configuration, and does not break it. Should it work if I skip the unattended stage of nLite or have I misunderstood something about the whole process?


You need to start with an OEM CD, not a Retail CD.

#132
Bezalel

Bezalel

    Senior Member

  • Member
  • PipPipPipPip
  • 591 posts

I'm getting a bit confused by all this... If I'd just copy dpcdll.dll, setupp.ini, pidgen.dll and setupreg.hiv from the I386 folder of my recovery cd to the I386 folder of the retail XP I'm installing from (in addition to the OEMBIOS.BI_, OEMBIOS.CA_, OEMBIOS.DA_, OEMBIOS.SI_ and winnt.sif files gotten with Bezalel's getfiles.bat) would it just solve my problem?

Any help is greatly appreciated!


Setupp.ini should be enough.

#133
visa tapani

visa tapani

    Newbie

  • Member
  • 18 posts

You need to start with an OEM CD, not a Retail CD.

Ahaa, I see now, thanks. Got a bit mixed up with terms as I wasn't really sure what an OEM CD is... But if I copy the setupp.ini file from my recovery disc it should work even with the retail XP cd?

#134
tencount

tencount
  • Member
  • 1 posts
Hi Guys,

I was a little confused from reading the forums able the steps that I need to take to setup a pre-activation image from ghost.

What I was trying to do was setup a standard image of ghost for OEM machines which are all the same type, HPs. Each HP machine has its own OEM license and does have 2 recovery cds.. One for the xp install and the other for HP restoration process.

So here are my steps...
  • Step up a working machine.
  • I created the 5 files from Bezalel's
  • I copied over the OEMBIOS.BI_, OEMBIOS.CA_, OEMBIOS.DA_, OEMBIOS.SI_ and winnt.sif into the c:\1386 folder of the image with the current key on the machine.
  • Ran Sysprep, leaving the license key empty.
  • After, the system came up, It still ask to reactivate windows and requires me to phone Microsoft.
From looking through the winnt.sif, the product key is different from the OEM sticker on the machine.
So, I tried to run JellyBean to change the windows license key but it would not change the key. It stated that it was an invalid key.
--
Also, I notice that every time sysprep is run, and the image is copied over to another machine. This key will be invalid on the OEM sticker. I will need to call into microsoft to active the machine.

-----
Does anyone know which steps that I may be missing. ...? Or what I am doing wrong...

Edited by tencount, 26 July 2007 - 02:24 PM.


#135
Bezalel

Bezalel

    Senior Member

  • Member
  • PipPipPipPip
  • 591 posts

Hi Guys,

I was a little confused from reading the forums able the steps that I need to take to setup a pre-activation image from ghost.

What I was trying to do was setup a standard image of ghost for OEM machines which are all the same type, HPs. Each HP machine has its own OEM license and does have 2 recovery cds.. One for the xp install and the other for HP restoration process.

So here are my steps...

  • Step up a working machine.
  • I created the 5 files from Bezalel's
  • I copied over the OEMBIOS.BI_, OEMBIOS.CA_, OEMBIOS.DA_, OEMBIOS.SI_ and winnt.sif into the c:\1386 folder of the image with the current key on the machine.
  • Ran Sysprep, leaving the license key empty.
  • After, the system came up, It still ask to reactivate windows and requires me to phone Microsoft.
From looking through the winnt.sif, the product key is different from the OEM sticker on the machine.
So, I tried to run JellyBean to change the windows license key but it would not change the key. It stated that it was an invalid key.

Does anyone know which steps that I may be missing. ...? Or what I am doing wrong...


This project is designed to create an install CD, not modify an image. If you want to modify an existing installation take a look at OEMScan - Automated Multi Manufacture Pre-Activation Utility. You cannot modify an image without having the risk of WFP restoring the origional files.

#136
severach

severach

    Member

  • Member
  • PipPip
  • 163 posts
Jellybean uses the official script so it can only switch Corporate Edition style VLK keys. It doesn't switch OEM SLP VLK keys. Some claim that older versions were able to switch more.

#137
onelovekir

onelovekir

    Newbie

  • Member
  • 13 posts
ok i have an oem blue/green coa windows media center product key from dell. i did a clean install of my media center and when i entered the key it would not allow it. so i quickly found a key online just to get it to install and then i was going to change it later using the product key changer. well it will not let me change it and i dont have my original cds that came from dell and im not waiting for them to send me new ones either. is there a way i can get my original cd key validated so i can update my computer?

thnx

#138
onelovekir

onelovekir

    Newbie

  • Member
  • 13 posts
please... i need my computer back to normal can anyone help me? got this computer from dell a couple years ago and its out of its warranty and i lost the original disks but i have my backup... but for some reason it wont let me enter my OEM product key that is on my machine. how do i enter that key so i can validate it and update my software via windows updates?

thnx

#139
Bezalel

Bezalel

    Senior Member

  • Member
  • PipPipPipPip
  • 591 posts

please... i need my computer back to normal can anyone help me? got this computer from dell a couple years ago and its out of its warranty and i lost the original disks but i have my backup... but for some reason it wont let me enter my OEM product key that is on my machine. how do i enter that key so i can validate it and update my software via windows updates?

thnx


What kind of backup do you have? And why do you need to enter a product key?

#140
onelovekir

onelovekir

    Newbie

  • Member
  • 13 posts
meaning a backup copy of Media Center but its not the original recovery disk from dell, thats why i need to enter my key. but i was reading somewhere either in this post or another that usually the key from the royalty oem recovery disk is different then the one they post on the computer itself. so what do i do to get my product key licensed with MCE so i can be "genuine"? i dont want to have to do that stupid phone activation cuz im trying to make a "recovery" disk of my own since reading the unattended section of msfn.org and reading a lot of posts here. i've already scratched my hard drive on my dell so i have to find out how to activate it using the key that is on my computer.

#141
onelovekir

onelovekir

    Newbie

  • Member
  • 13 posts
anybody?..... i really dont want to use a wga fix or anything like that cuz i did pay for this and i would like to be genuine on my own. please can somebody help.... thanks

#142
Bezalel

Bezalel

    Senior Member

  • Member
  • PipPipPipPip
  • 591 posts

meaning a backup copy of Media Center but its not the original recovery disk from dell


Do you mean you have a copy of the generic CD set?

If so you can use the key on the sticker and use Phone Activation method. If you want to use the OEMBIOS method you will have to find a SLP key somewhere else.

#143
onelovekir

onelovekir

    Newbie

  • Member
  • 13 posts
yeah its the generic 2 cd set from MSDN and it didnt accept my key from my cpu. so what SLP key will work for MCE so i can do an unattended or even not an unattended install? how can i reactivate my software through phone activation if its already activated with the non-genuine key?

#144
ZaForD

ZaForD

    Member

  • Member
  • PipPip
  • 182 posts

yeah its the generic 2 cd set from MSDN and it didnt accept my key from my cpu.

MSDN disks use a Retail CD key, which is why the one on the COA won't work.

You'll need to use an OEM disk set to use the COA key or a SLP key.
But if you use the COA key you'll still have to phone MS to activated your PC, as they don't activate online anymore.

Edited by ZaForD, 18 September 2007 - 10:33 AM.

Posted Image
-------------- Posted Image --------------


#145
onelovekir

onelovekir

    Newbie

  • Member
  • 13 posts
oh man.... thats what i was afraid of.... i guess i will call now. that sucks cuz i usually do a clean install on my computer about 2 or 3 times a year. thnx anyways

#146
dagon

dagon
  • Member
  • 4 posts
this is an interesting topic

ive read through most of the 8 pages and pretty much understand what the purpose and point to all of this is.. but i honestly don't recall after going through the 8 pages if this question/thought is answered (ive been at work all night, and have been drinking some very alcoholic beverages since i came home, so i dont recall too much of what ive read) :

what is the purpose or significance of needing or the requirement to have a "holographic" CD from the factory? if using this method produces four required files (not including the winnt.sif here, only the oembios.* files) could these files be used in a generic OEM cd to essentially recreate the pre-activated installation? by "generic" i mean an ISO created from one of the forementioned 9 in 1 or 11 in 1 "warez" internet releases.

are there other modified files on the factory cd that are required to make use of this function that would not/may not be present on a generic cd?

i only ask this out of educational interest and not because i am trying to anything "illegal". i have a brand spanking new Dell system that has come with an XP reinstall CD, but i have not used it nor do i know if it "restores" the activation or if it is a straight XP install disc that I would have to use my COA key on or if it is built in with the SLP key.

i had already started to test the "9in1" OEM ISO with these oembios.* files when I got to the page in the thread that said it would not work in a virtual machine since the VM's bios would not match. I dont want to waste CDR's and my already-activated system by testing to see if the 9in1 OEM would work or not.. don't ask me why I didn't just make an ISO of the restore cd, there's no answer for that... i just didnt.

as i write this lengthy post, i'm testing this method on my Toshiba laptop using the oembios.* files from it and the SLP key to see if it comes out pre-activated or not.


second question

how does using this method differ or how is it different than the "OEMScan - Automated Multi Manufacture Pre-Activation Utility" thread? or does it not differ?

from the sound of it both methods get the SLP key, and create the oembios.* files... is this correct?

Ultimately what I want to accomplish is to be able to create a custom install CD using nLite/etc that is already activated--which normally would not be possible unless you started with a VLK source/key--on my laptop (which legit coa, slp, etc) and my Dell desktop (ditto on the legit). I have a restore cd for the Toshiba that restores it to factory, including the activation, but also including all the junk software. And as I said, I'm not sure what the Dell restore CD is... if it's just a straight XP install of it its an actual "restore" cd..

Sorry for the long winded post, I tend to blab on and on when I've been drinking.

Thanks.


-- Edit

The Toshiba reinstall using the generic OEM cd is not accepting the SLP key. Dont know if I did something wrong or not (and ive wasted a cdr on this). Looking at the Toshiba restore CD its a ghost image so it would not be easy to work with.

Edited by dagon, 19 September 2007 - 08:28 AM.


#147
Bezalel

Bezalel

    Senior Member

  • Member
  • PipPipPipPip
  • 591 posts

what is the purpose or significance of needing or the requirement to have a "holographic" CD from the factory? if using this method produces four required files (not including the winnt.sif here, only the oembios.* files) could these files be used in a generic OEM cd to essentially recreate the pre-activated installation? by "generic" i mean an ISO created from one of the forementioned 9 in 1 or 11 in 1 "warez" internet releases.


The Hologram CD ensures that you have the rest of the required files and that everyone is starting with the same files. Starting with a different source may or may not work. (Also warez distibutions cannot be discussed on this forum and they often have other illegal cracks that may interfere with the procedure)

i only ask this out of educational interest and not because i am trying to anything "illegal". i have a brand spanking new Dell system that has come with an XP reinstall CD, but i have not used it nor do i know if it "restores" the activation or if it is a straight XP install disc that I would have to use my COA key on or if it is built in with the SLP key.


If you have the Dell CD you don't need this. In setting up this procedure I compared a Dell CD to a hologram CD and wrote a program that would generate the files that were different.

how does using this method differ or how is it different than the "OEMScan - Automated Multi Manufacture Pre-Activation Utility" thread? or does it not differ?


OEMScan is an offshoot of this method. The differances are as follows:
  • This method will only work with 1 manufacturer and OEMScan will work with multiple manufacturers
  • This method replaces the files before Windows is installed and OEMScan changes them after Windows is installed
  • This method doesn't require any additional software to be run or configured on the target PC

from the sound of it both methods get the SLP key, and create the oembios.* files... is this correct?


Yes.

Ultimately what I want to accomplish is to be able to create a custom install CD using nLite/etc that is already activated--which normally would not be possible unless you started with a VLK source/key--on my laptop (which legit coa, slp, etc) and my Dell desktop (ditto on the legit). I have a restore cd for the Toshiba that restores it to factory, including the activation, but also including all the junk software. And as I said, I'm not sure what the Dell restore CD is... if it's just a straight XP install of it its an actual "restore" cd..


If you want your CD to work for multiple manufacturers use OEMScan, otherwise use this procedure

#148
onelovekir

onelovekir

    Newbie

  • Member
  • 13 posts
i called MS to activate but they couldnt tell me how to change my key to the COA key that i have on my system (it doesnt help that everytime i called MS that i get a foreigner on the phone who is so anxious to just hang up on me). they said i have to contact dell on the issue. this creates a problem cuz how can they tell me when my warranty is finished? i dont know.... this whole thing just p***es me off.

#149
ZaForD

ZaForD

    Member

  • Member
  • PipPip
  • 182 posts

i called MS to activate but they couldnt tell me how to change my key to the COA key that i have on my system

Even if this was possible and the guy kenw how to do it, he couldn't tell you. Without lossing his job.
I don't know if this would be classed as piracy, but it would definitely violate your licence agreement.

it doesnt help that everytime i called MS that i get a foreigner on the phone who is so anxious to just hang up on me

If you were asking me to put my job on the line. I'd be trying to hang up on you.
But then again as you can see by my nationality on the left, I'm a foreigner too.

they said i have to contact dell on the issue.

As you said in your post, you bought this PC [and its OS] from Dell. So they should really be the people your talking to. Because they're the ones that took your money.
But no company is gonna tell you that outright.

The only way your gonna solve this is to get/find/buy/borrow/steal a Genuine Dell or Holographic OEM CD. As thats the only disks that will accept your COA number.
That may not be the answer your after, but its the right best your gonna get from this foreigner. ;)

Posted Image
-------------- Posted Image --------------


#150
Bezalel

Bezalel

    Senior Member

  • Member
  • PipPipPipPip
  • 591 posts

The only way your gonna solve this is to get/find/buy/borrow/steal a Genuine Dell or Holographic OEM CD. As thats the only disks that will accept your COA number.
That may not be the answer your after, but its the right best your gonna get from this foreigner. ;)


Google is your friend.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN