XP OEM Sysprep License Issue

  • Thread starter Thread starter Craig Fiegert
  • Start date Start date
C

Craig Fiegert

I have a sysprepped image that we are deploying using OEM licenses that came
with the machines.

The issue is that the image we have built has only 17 days of the 30
required for activation left and i'm assuming will stop working after the 30
days expire.

We activate the machines after they are imaged so we are legal, but how can
we get around the countdown with an image using OEM keys?

How do OEMs do it?
 
Craig Fiegert said:
I have a sysprepped image that we are deploying using OEM licenses that came
with the machines.

The issue is that the image we have built has only 17 days of the 30
required for activation left and i'm assuming will stop working after the 30
days expire.

We activate the machines after they are imaged so we are legal, but how can
we get around the countdown with an image using OEM keys?

How do OEMs do it?

If you did a factory reseal on the image once you had updated all the
drivers in Factory mode, you shouldn't get this issue as the first thing you
would need to do on booting up the freshly restored image is enter the OEM
product key, you should then get the normal 30 days to activate.

Lorne
 
thats what i would have thought....

unless something has gone wrong in the sysprep because when the pc boots
back up, the mini setup runs and you re-enter the product key. This should
give you 30 days but we're only getting 17 of the 30....

any idea what options to pick in the sysprep? I did tick mini setup and
pre-activated before hitting re-seal...
 
I'm afraid I've about reached the limit of my knowledge for SysPrep... I
only know what I'd mentioned because I setup an image for a friend who runs
his own computer store and he wanted them left unactivated so I didn't
really delve much deeper into it... I'm sure one of the MVPs in here can
help further, or there is a LOT of information about Windows PE on the MS
website...

Lorne
 
Thanks Lorne

I think it may be because i ticked pre-activated. Am going to try this later
today without ticking it....

Anyone else care to comment?
 
Craig,

This gets complicated because your using the OEM installs. If you run
sysprep it can reset the activation period 3 times. Since you are using
OEM installs though you would have to have minisetup prompt for the
productkey and supply the productkey that is usually printed on the sticker
on the side of the machine during setup. If you run sysprep and choose
mini and reseal does it reset the activation period to 30 days? It's
possible they have reached their limit on on how many times it can be reset
since they are oem installs.

FYI. We only support sysprepping volume media installations due to the
issues like this you may encounter involving activation.

Scott McArthur[MS]
Microsoft Windows Server Setup Support
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| From: "Craig Fiegert" <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<#5guLy#[email protected]>
| Subject: Re: XP OEM Sysprep License Issue
| Date: Fri, 17 Oct 2003 08:24:05 +0930
| Lines: 72
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.windowsxp.setup_deployment
| NNTP-Posting-Host: 203-6-132-1.adam.com.au 203.6.132.1
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.windowsxp.setup_deployment:88486
| X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
|
| Thanks Lorne
|
| I think it may be because i ticked pre-activated. Am going to try this
later
| today without ticking it....
|
| Anyone else care to comment?
| | > I'm afraid I've about reached the limit of my knowledge for SysPrep... I
| > only know what I'd mentioned because I setup an image for a friend who
| runs
| > his own computer store and he wanted them left unactivated so I didn't
| > really delve much deeper into it... I'm sure one of the MVPs in here
can
| > help further, or there is a LOT of information about Windows PE on the
MS
| > website...
| >
| > Lorne
| >
| > | > > thats what i would have thought....
| > >
| > > unless something has gone wrong in the sysprep because when the pc
boots
| > > back up, the mini setup runs and you re-enter the product key. This
| should
| > > give you 30 days but we're only getting 17 of the 30....
| > >
| > > any idea what options to pick in the sysprep? I did tick mini setup
and
| > > pre-activated before hitting re-seal...
| > >
| > > | > > > | > > > > I have a sysprepped image that we are deploying using OEM licenses
| > that
| > > > came
| > > > > with the machines.
| > > > >
| > > > > The issue is that the image we have built has only 17 days of the
30
| > > > > required for activation left and i'm assuming will stop working
| after
| > > the
| > > > 30
| > > > > days expire.
| > > > >
| > > > > We activate the machines after they are imaged so we are legal,
but
| > how
| > > > can
| > > > > we get around the countdown with an image using OEM keys?
| > > > >
| > > > > How do OEMs do it?
| > > > >
| > > > >
| > > >
| > > > If you did a factory reseal on the image once you had updated all
the
| > > > drivers in Factory mode, you shouldn't get this issue as the first
| thing
| > > you
| > > > would need to do on booting up the freshly restored image is enter
the
| > OEM
| > > > product key, you should then get the normal 30 days to activate.
| > > >
| > > > Lorne
| > > >
| > > >
| > >
| > >
| >
| >
|
|
|
 
Back
Top