Quick tips for Sysprep.

I'm just finishing up a new iteration of our XP pro OEM corporate image, and wanted to check a couple things. what switches should I use to get rid of the OEM key entry, and have the machine basically just boot to windows, skipping the minisetup and just resetting the SID's.

Customization Tweaking 1789 This topic was started by ,


data/avatar/default/avatar35.webp

17 Posts
Location -
Joined 2002-11-08
I'm just finishing up a new iteration of our XP pro OEM corporate image, and wanted to check a couple things.
 
 
what switches should I use to get rid of the OEM key entry, and have the machine basically just boot to windows, skipping the minisetup and just resetting the SID's. ( have predefined default profiles and a generic "agent" user account.)
 
I've tried
Code:
"sysprep -activated -mini"
and it still asks for the product key. 
 
Thanks for your input.

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar01.webp

1547 Posts
Location -
Joined 2002-05-29
Don't you still have to enter a valid OEM key into the WINNT.SIF file ?!?
 
Here's how I did our OEM Pre-Installs for XP Pro:
 
[Data]
AutoPartition=1
MsDosInitiated=0
UnattendedInstall=Yes
 
[unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
 
[GuiUnattended]
AdminPassword=*
AutoLogon=Yes
AutoLogonCount=5
OEMSkipRegional=1
OemSkipWelcome=1
 
[userData]
ProductID="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
FullName=ValuedCustomer
OrgName=ValuedCustomer
ComputerName=Workstation

data/avatar/default/avatar35.webp

17 Posts
Location -
Joined 2002-11-08
OP
Is that SIF file used as a config list for the sysprep? Should i build one and have sysyprep run from it? Not sure about using SIF files, I was just using switches on the command itself.
 
(prepping the image for ghost)

data/avatar/default/avatar01.webp

1547 Posts
Location -
Joined 2002-05-29
I use this for the OEM Pre-Installs as I work for a system builder and I create a load of CD's from an Image using Nero
 
I also slipstream the latest Service Packs and do the same for Win 2k Pro

data/avatar/default/avatar35.webp

17 Posts
Location -
Joined 2002-11-08
OP
Well, I'm looking to find out what switches I need to use with sysprep to get rid of the product key entry screen. ..?

data/avatar/default/avatar01.webp

1547 Posts
Location -
Joined 2002-05-29
Well I don't know if there's a way to do that but perhaps somebody else might know

data/avatar/default/avatar16.webp

2 Posts
Location -
Joined 2003-12-07
The Winnt.SIF file is only used when you want to automate setup when booting from the CD-ROM. To help automate the Sysprep mini-setup wizard, you need to create a Sysprep.INF file. This file can be created using the SetupMGR.exe utility found on the CD-ROM in the Support\Tools\Deploy.CAB file. You need to place the Sysprep.INF file in the C:\Sysprep folder on the image computer. You can use it to define the common variable asked, and leave the computer specific variables blank, setup will stop on the blank variables and ask you to fill them in.

data/avatar/default/avatar35.webp

17 Posts
Location -
Joined 2002-11-08
OP
Quote:The Winnt.SIF file is only used when you want to automate setup when booting from the CD-ROM. To help automate the Sysprep mini-setup wizard, you need to create a Sysprep.INF file. This file can be created using the SetupMGR.exe utility found on the CD-ROM in the Support\Tools\Deploy.CAB file. You need to place the Sysprep.INF file in the C:\Sysprep folder on the image computer. You can use it to define the common variable asked, and leave the computer specific variables blank, setup will stop on the blank variables and ask you to fill them in.

That's exactly what I was looking for. Damn, and the image has been pressed. Thanks though, I'll remember for next time!