Sign in with
Sign up | Sign in
Your question

Sysprep and Windows Activation

Last response: in Windows XP
Share
Anonymous
October 14, 2004 6:05:04 PM

Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

Ok,
Tried using sysprep before imaging on a new XPsp2 Professional box, but
received an error that there was a conflict, and I couldn't run it. I found
newer version of sysprep for XPsp1, (version 5.1.2600.1106) and ran that.
However, I inadvertently enabled Windows Activation. We have volume
licensing, so this is not supposed to be an issue. I need to find a way to
fix this so I can create a new image. Here's what I did/happened when I ran
sysprep...

First - normal warning box came up with the Sysprep Tool 2.0 header (I just
did this through Run, not the command line)

Next I got a gray dialogue box with the following options on it (have to
pick one of them to proceed and actually run the utility).

1) To skip Windows Welcome or Mini setup & configure the installation as
scripted in winbom.ini, click Factory

2) To reboot this computer & manually test the install, click audit
(available only in factory mode)

3) To prepare for end user, click reseal

I clicked on the reseal option, and that obviously wasn't a good choice, as
now the 30 days windows activation balloon pops up on the first PC I put the
image onto.

Any thoughts on how to undo this? TIA, lostagain
Anonymous
February 8, 2005 12:59:04 PM

Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

you need a custom sysprep.ini file. the setupmgr.exe will help you make one
but then you can customize it. here is an example of the one I use. Its not
real sophisticated but it works well. Obviously remove any "" or ** and
insert your own answers

;SetupMgrTag

[Unattended]
OemSkipEula = Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS

[GuiUnattended]
OEMSkipRegional=1
OemSkipWelcome = 1
OemSkipEula=Yes
TimeZone=35
OEMDuplicatorString = "blah blah blah"

[UserData]
FullName="blah"
OrgName="blah blah"
ComputerName = **leave this blank and the mini setup will prompt you for
a computer name***
;prod id for win XP
ProductID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx


[Display]
BitsPerPel=16
Xresolution=1024
YResolution=768
Vrefresh=70

[RegionalSettings]
LanguageGroup=1
Language=00000409

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=win2000dist

[GuiRunOnce]

[Identification]
JoinDomain="domain name"
DomainAdmin=domain name\account name whos only right is adding pcs to
the domain"
DomainAdminPassword="password for user account"

[Networking]
InstallDefaultComponents=yes

[NetClients]
MS_MSClient=params.MS_MSClient
MS_NWClient=params.MS_NWClient

[params.MS_NWClient]
PreferredServer="no body still uses netware do they...<grin>"
LogonScript=No


"lostagain82" wrote:

> Ok,
> Tried using sysprep before imaging on a new XPsp2 Professional box, but
> received an error that there was a conflict, and I couldn't run it. I found
> newer version of sysprep for XPsp1, (version 5.1.2600.1106) and ran that.
> However, I inadvertently enabled Windows Activation. We have volume
> licensing, so this is not supposed to be an issue. I need to find a way to
> fix this so I can create a new image. Here's what I did/happened when I ran
> sysprep...
>
> First - normal warning box came up with the Sysprep Tool 2.0 header (I just
> did this through Run, not the command line)
>
> Next I got a gray dialogue box with the following options on it (have to
> pick one of them to proceed and actually run the utility).
>
> 1) To skip Windows Welcome or Mini setup & configure the installation as
> scripted in winbom.ini, click Factory
>
> 2) To reboot this computer & manually test the install, click audit
> (available only in factory mode)
>
> 3) To prepare for end user, click reseal
>
> I clicked on the reseal option, and that obviously wasn't a good choice, as
> now the 30 days windows activation balloon pops up on the first PC I put the
> image onto.
>
> Any thoughts on how to undo this? TIA, lostagain
!