Windows OEM/Recovery Options

[at1105]

I'm needing someone to demystify this for me. I recently did a repair to a computer that had a failing HDD and ended up requiring the factory Recovery Discs to do a clean install on a replacement drive. Unfortunately, I did not have any OEM factory discs so the client had to bring them to me. Is there a legitimate option to prevent a client from having to bring the discs in a situation like this? A better question may be "How do you guys handle it when a client's PC needs the operating system reinstalled but they do not have the original installation media and no recovery discs but they do have a valid Product Key/COA on the PC/Laptop?" Do you keep several different OEM Reinstallation Discs (Dell, Toshiba, Etc) for such a case as this?

 

[AndyM]

Please try and provide as much information as you can,

Make, model, Operating System etc,

It will then be easier for us to help...

Andy

 

[mraikes]

I'm needing someone to demystify this for me. I recently did a repair to a computer that had a failing HDD and ended up requiring the factory Recovery Discs to do a clean install on a replacement drive. Unfortunately, I did not have any OEM factory discs so the client had to bring them to me. Is there a legitimate option to prevent a client from having to bring the discs in a situation like this? A better question may be "How do you guys handle it when a client's PC needs the operating system reinstalled but they do not have the original installation media and no recovery discs but they do have a valid Product Key/COA on the PC/Laptop?" Do you keep several different OEM Reinstallation Discs (Dell, Toshiba, Etc) for such a case as this?

Of course the strict answer is that in most cases you're required to contact the appropriate vendor to obtain recovery media for that specific computer.

However, for the sake of discussion, it's sometimes possible to use other install discs and activate with the customer's COA. For example, Dell reinstall disks are fairly generic and are rumoured to work with pretty much anyone else's hardware - but require activation with the destination computer's key. If you experiment with cross-installs, one thing you'll notice (and possibly have to correct) is that the OEM info listed in Windows will of course be based on the source disk and not from the original hardware vendor.

 

[nlinecomputers]

Please try and provide as much information as you can,

Make, model, Operating System etc,

It will then be easier for us to help...

Andy

How can he do that when he is obviously asking a generic question?

 

[Markverhyden]

So as not to violate the EULA the owner must order recovery disks if they did not make/get a set when they got the machine.

During experimentation in my lab I have found OEM disks (meaning the base OS not the product recovery) can be installed on different manufacturers. It will require registration but you just use the COA off of the machine.

 

[Porthos]

I would never use factory media with all of the bloat/crapware. I have all the digital river ISO's I will ever need. The ONLY and EVER reason I would use the Factory disk (and it WILL cost more) if the customer insists(has never happened) Or if I did not have the Oem activation backup on hand.

 

[at1105]

I would never use factory media with all of the bloat/crapware. I have all the digital river ISO's I will ever need. The ONLY and EVER reason I would use the Factory disk (and it WILL cost more) if the customer insists(has never happened) Or if I did not have the Oem activation backup on hand.

I've seen the digital river iso's and thought about keeping those on hand but i wasn't sure if it were possible to activate it with the original key. So basically as long as the version of the iso (i.e., 7 Home Premium) matches exactly what is on the Product Key Sticker/COA, then it should activate with that key on the sticker?

 

[nlinecomputers]

I've seen the digital river iso's and thought about keeping those on hand but i wasn't sure if it were possible to activate it with the original key. So basically as long as the version of the iso (i.e., 7 Home Premium) matches exactly what is on the Product Key Sticker/COA, then it should activate with that key on the sticker?

Yes.

Not counting retail and VLK media there are 3 kinds of OEM disks. You have DSP(Delivery Service Partner) versions. There are the generic OEM copies you can purchase from many vendors from Tech Data, D&H, or NewEgg. They install on any system so long as you have the Product Key on the side of the machine.

Next you have SLP(System Locked for Pre-installation) OEM. This is the same as above except that they during the install look for a code in the BIOS. If found the install will not prompt you for a product key it will use a special key built into the disk. If you use it on a non matching bios it will prompt you for the key as usual. Each major OEM has it's own key (Dell, HP, Lenovo, Acer, etc.) Except for Dell most OEMs don't offer this version, although they are required to make one for internal use and most if you call them up will sell you a copy of this disk. If you have ever used Belarc Advisor or Magic Jelly Bean to retrieve a Product Key on a Dell, Hp, or some other OEM you will find that the same key is on all of them and they never works. This is why.

The last version is the most common and that is the image disk. With the image a full "ghost" image of the system, complete with the bloatware installed is offered as recovery disks. The system was setup in the factory using an in house SLP version of Windows and then fully setup for retail use. Again the product key used is NOT the sticker on the side but the SLP mass production key assigned to that OEM.

The only legal method that an OEM can provide an end user is either the SLP disk or the image disk. OEMs may not provide the generic DSP disk. Yet those versions are readily available and they are the only ones that the key on the side of the machine can work with.

Yet Microsoft tells you that you can't use a DSP OEM disk on your Dell nor the HP disk on your Dell. Even though both will work and activate.

 

[smashedbotatos]

I use the factory image or recovery disks when I can. Reason being some of them have been preloaded with software that the end users likes and uses. As for the bloatware I remove most of the garbage.

Another problem you can and will run in to is drivers and software utilities for laptops. Sometimes the bundled software differs from the downloads on the support site.

I find it so much easier to just use a factory image and remove bloatware afterwards. Using an OEM disk and downloading drivers/software can be a lengthy process. Which is another reason I try to stay away from OEM disks. Some cases even if you use an OEM disk you have to call to activate too.

 

[ProfessorCPU]

Also look up OEM SLP. It is the method used by OEMs to factory install systems. There are different methods for xp vista/windows7 and windows 8. It is the closest you can get to installing it the same way as the oem... without using their bloated crappy disks. It utalizes the info on the oem motherboard with a royalty oem key and some files needed for the activation. It also is a way of offline activating. ;-)

 

[PC Ops]

This excellent post (sticky) by Cadishead Computers has all the answers

http://www.technibble.com/forums/showthread.php?t=38781

 

[Porthos]

Using an OEM disk and downloading drivers/software can be a lengthy process.

I always take a Fabs and a Double driver backup if there is going to be a reformat. They can both be used offline on your bench machine if needed.

If the machine boots I also get the OEM activation backed up as well. ( I have a good collection if not possible to back up)

On hp-toshiba-acer-gateway in most cases there is a folder with the original software installers I grab as well. (just in case)

The items available in Ninite like codecs media players libre office CD burners ect covers most things. Plus I personally use all items I install with ninite so I can support if needed. I leave a Ninite installer on the desktop for the items like flash java ect and rename it to Run Weekly and instruct client to run it every week to make sure all those vulnerable programs are kept up to date .

I keep images for all of my normal OS installs Vista,7 and 8.1 that are are no more than a month or two out of date update wise and loaded with my normal software already installed. Those images are already custom branded with my business info. Thanks foolishit for your OS branding tool.

And because desktop and browsers are profile independent, I also have created a (generic) fabs backup to run to install my desktop items and my browser customizations like ad block for firefox and chrome when it is a generic install with no customer data.

My steps
1 Restore image 10 min
2 restore double driver backup 5-10min
3 Restore activation 1 min
4 re run the ninite installer for my setup to update those items 5-10 min
5 get leftover windows updates remember I am no more than 2 months out of date.

Total give or take 30 minutes. Now I just because I like to to be anal and to do a little good will and CYA (future restores). I create a partition with a Macrium image backup at this point if the drive is at least 250 gig. This image usually fits in 15 gigs. This is another 10- 20 minutes at most.

Also try to up-sell an external drive as well so they can continue to keep backups as well with Macrium. Some people just wont learn from their mistakes.

After that restore fabs backup or what ever else the customer has paid for(Office ect).

Then make sure the browsers weren't hijacked in the fabs backup.(Open each browser for a quick look) I had already scanned the rest of the backup while I had had it on my bench external.
My bench is a dual core 8 gig USB 3 machine with a USB 3 dock. (just love customer computers with 3.0)

Defrag computer and call customer -get paid.

Wow this is most likely my longest post on here I hope this is helpful to someone.

 

[at1105]

Perfect! Thank for all the input. You guys rock!

 

[SpaceSquad]

I leave a Ninite installer on the desktop for the items like flash java ect and rename it to Run Weekly and instruct client to run it every week to make sure all those vulnerable programs are kept up to date .

Great post! I really like this part...might be something to consider.