RE: Sysprep question

Ty,

Could you post your sysprep.inf file here? That will make diagnosing the
problem a lot easier.

--
--
Brian Desmond
Windows Server MVP
desmondb@payton.cps.k12.il.us

Http://www.briandesmond.com


"Ty" <anonymous@discussions.microsoft.com> wrote in message
news:1d45701c42353$374da670$a501280a@phx.gbl...

> Darrell......thanks for the quick reply. To answer your
> questions:
> This is the article I referenced:
> Microsoft Knowledge Base Article - 307316
> Product key is entered in sysprep.inf
> It is not encrypted.
> Not being prompted to enter any information during
> sysprep setup. ......(it is all automated). The product
> id is an enterprise volume license, it is entered
> properly...the product id screen just shows for 5-10
> seconds. Would like to setup without this key showing.
> I don't have the sysprep folder available here
> now.....can get it tomorrow if necessary.
> Thanks for the help!
>

> >-----Original Message-----
> >Hello Ty,
> >What article are you refering to?
> >Do you have the product key entered into you sysprep.inf?
> >Are you encrypting the product key?
> >Can you post the sysprep.inf? IF so xxx out any

> information like the

> >product key or passwords.
> >What are the first 8 digits under registered to on My

> Computer Properties?

> >Usually if you are prompted for the product key either

> the syntax is

> >incorrect in the inf, the product key used does not

> match the media that

> >the image was installed with, or the product key was not

> entered properly

> >Thanks,
> >Darrell Gorter[MSFT]
> >
> >This posting is provided "AS IS" with no warranties, and

> confers no rights

> >--------------------

> >>Content-Class: urn:content-classes:message
> >>From: "Ty" <anonymous@discussions.microsoft.com>
> >>Sender: "Ty" <anonymous@discussions.microsoft.com>
> >>Subject: Sysprep question
> >>Date: Thu, 15 Apr 2004 16:43:13 -0700
> >>Lines: 17
> >>Message-ID: <1d3f701c42343$6adfa840$a501280a@phx.gbl>
> >>MIME-Version: 1.0
> >>Content-Type: text/plain;
> >> charset="iso-8859-1"
> >>Content-Transfer-Encoding: 7bit
> >>X-Newsreader: Microsoft CDO for Windows 2000
> >>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
> >>Thread-Index: AcQjQ2rdotkoSoA+T3GHiBAqJsTUiw==
> >>Newsgroups: microsoft.public.windowsxp.setup_deployment
> >>Path: cpmsftngxa06.phx.gbl
> >>Xref: cpmsftngxa06.phx.gbl

> >microsoft.public.windowsxp.setup_deployment:10832 0

> >>NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
> >>X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
> >>
> >>Deploying XP machines using premade image distributed
> >>using Ghost software. Using Sysprep for automated setup
> >>regarding: Volume product id, sid generation, admin
> >>password, etc... I have set up Sysprep folder with
> >>sysprep.inf configured inside at C:\ location. I run

> the

> >>mini setup, with Reseal.
> >>Problem: When Sysprep sets up new machine, the product

> id

> >>screen shows. I have studied the KB article on this

> bug,

> >>but the fix they offer does not exist. They also say it
> >>was first fixed with SP1, however, my image is up to

> date

> >>with all hotfixes, and still showing the screen.
> >>Anyone help me stop the Product id screen from showing?
> >>Please?
> >>
> >>Thank you
> >>
> >>
> >>

> >
> >.
> >

I realize the product key can be attained using different
methods, but those methods require some knowledge and
skill. This product id is simply given to them by
appearing on screen.

Here is the sysprep.inf I am using. Not much to it. Have
changed specific info for posting here. Your help is
appreciated.

;SetupMgrTag
[Unattended]
OemSkipEula=Yes

[GuiUnattended]
AdminPassword=xxxxxxxx
Autologon=0
OEMSkipRegional=1
OEMDuplicatorstring="xxx Standard Image 3.1x (Core OS
Only)"
TimeZone=4
OemSkipWelcome=1

[UserData]
ProductID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
FullName="Our Company xxxxx"
OrgName="Townxx, Statexx, Zipxx"
ComputerName=*

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000409
UserLocale=00000409
InputLocale=0409:00000409

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

[Identification]
JoinWorkgroup=xxx

[Networking]
InstallDefaultComponents=Yes

>-----Original Message-----
>Ty,
>
>Could you post your sysprep.inf file here? That will

make diagnosing the

>problem a lot easier.
>
>--
>--
>Brian Desmond
>Windows Server MVP
>desmondb@payton.cps.k12.il.us
>
>Http://www.briandesmond.com
>
>
>"Ty" <anonymous@discussions.microsoft.com> wrote in

message

>news:1d45701c42353$374da670$a501280a@phx.gbl...

>> Darrell......thanks for the quick reply. To answer your
>> questions:
>> This is the article I referenced:
>> Microsoft Knowledge Base Article - 307316
>> Product key is entered in sysprep.inf
>> It is not encrypted.
>> Not being prompted to enter any information during
>> sysprep setup. ......(it is all automated). The

product

>> id is an enterprise volume license, it is entered
>> properly...the product id screen just shows for 5-10
>> seconds. Would like to setup without this key showing.
>> I don't have the sysprep folder available here
>> now.....can get it tomorrow if necessary.
>> Thanks for the help!
>>

>> >-----Original Message-----
>> >Hello Ty,
>> >What article are you refering to?
>> >Do you have the product key entered into you

sysprep.inf?

>> >Are you encrypting the product key?
>> >Can you post the sysprep.inf? IF so xxx out any

>> information like the

>> >product key or passwords.
>> >What are the first 8 digits under registered to on My

>> Computer Properties?

>> >Usually if you are prompted for the product key either

>> the syntax is

>> >incorrect in the inf, the product key used does not

>> match the media that

>> >the image was installed with, or the product key was

not

>> entered properly

>> >Thanks,
>> >Darrell Gorter[MSFT]
>> >
>> >This posting is provided "AS IS" with no warranties,

and

>> confers no rights

>> >--------------------
>> >>Content-Class: urn:content-classes:message
>> >>From: "Ty" <anonymous@discussions.microsoft.com>
>> >>Sender: "Ty" <anonymous@discussions.microsoft.com>
>> >>Subject: Sysprep question
>> >>Date: Thu, 15 Apr 2004 16:43:13 -0700
>> >>Lines: 17
>> >>Message-ID: <1d3f701c42343$6adfa840$a501280a@phx.gbl>
>> >>MIME-Version: 1.0
>> >>Content-Type: text/plain;
>> >> charset="iso-8859-1"
>> >>Content-Transfer-Encoding: 7bit
>> >>X-Newsreader: Microsoft CDO for Windows 2000
>> >>X-MimeOLE: Produced By Microsoft MimeOLE

V5.50.4910.0300

>> >>Thread-Index: AcQjQ2rdotkoSoA+T3GHiBAqJsTUiw==
>> >>Newsgroups:

microsoft.public.windowsxp.setup_deployment

>> >>Path: cpmsftngxa06.phx.gbl
>> >>Xref: cpmsftngxa06.phx.gbl
>> >microsoft.public.windowsxp.setup_deployment:10832 0
>> >>NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
>> >>X-Tomcat-NG:

microsoft.public.windowsxp.setup_deployment

>> >>
>> >>Deploying XP machines using premade image distributed
>> >>using Ghost software. Using Sysprep for automated

setup

>> >>regarding: Volume product id, sid generation, admin
>> >>password, etc... I have set up Sysprep folder with
>> >>sysprep.inf configured inside at C:\ location. I run

>> the

>> >>mini setup, with Reseal.
>> >>Problem: When Sysprep sets up new machine, the

product

>> id

>> >>screen shows. I have studied the KB article on this

>> bug,

>> >>but the fix they offer does not exist. They also say

it

>> >>was first fixed with SP1, however, my image is up to

>> date

>> >>with all hotfixes, and still showing the screen.
>> >>Anyone help me stop the Product id screen from

showing?

>> >>Please?
>> >>
>> >>Thank you
>> >>
>> >>
>> >>
>> >
>> >.
>> >

>
>
>.
>

I used sysprep on an XP Professional system when it was configured properly
to autologon to windows & novell. Sysprep trashed my autologon entries and
doesn't work wen I put them back in. WE ARE LICENSED for XP. What is the
problem with ghosting the computer without running sysprep...changing the
computername before connecting to the network? All my settings stay if done
like this.

In article <#9vYw2UVEHA.2592@TK2MSFTNGP09.phx.gbl>, keith@nospan.net
says...

> I used sysprep on an XP Professional system when it was configured properly
> to autologon to windows & novell. Sysprep trashed my autologon entries and
> doesn't work wen I put them back in. WE ARE LICENSED for XP. What is the
> problem with ghosting the computer without running sysprep...changing the
> computername before connecting to the network? All my settings stay if done
> like this.

Each machine must have a unique SID - ghosting will produce clones of
SIDs which is why Sysprep is needed to generate a new SID for each
installation.

Hello everyone,

I have a few machines that are XP professional and I imaged them using
Zenworks 4.0.1, however I did not sysprep them. I'm having some quarks with
them and thinking its due to not syspreping them. Can I resysprep those
computers and in the process retain the user's profiles and settings? I'm
just not sure if it will delete anything as far as the user goes.

Thank you
Alex Anderson

Hello everyone,

What is the difference running and not running mini-setup when you
reseal a computer during sysprep? Basically you have the mini-setup and
some type of mini-setup that is more fisher price?

Thank you
Alex Anderson

There are two options when running Sysprep.

-Reseal and -Reseal -Mini.

-Mini = Mini Setup
Mini Setup will process all the supported feilds in the
Sysprep.inf.

-Reseal = Windows Welcome (OOBE)
Windows Welcome will only process a few of the supported
feilds in the sysprep.inf and will also process the
oobeinfo.ini.

For Corporate Deployments you will want to use Mini Setup.

Hawkens

>-----Original Message-----
>Hello everyone,
>
> What is the difference running and not running mini-

setup when you

>reseal a computer during sysprep? Basically you have

the mini-setup and

>some type of mini-setup that is more fisher price?
>
>Thank you
>Alex Anderson
>
>
>.
>

Hawkens,

Understood, thank you very much.

Alex Anderson

"Hawkens" <anonymous@discussions.microsoft.com> wrote in message
news:2147d01c45a12$d63bc910$a001280a@phx.gbl...

> There are two options when running Sysprep.
>
> -Reseal and -Reseal -Mini.
>
> -Mini = Mini Setup
> Mini Setup will process all the supported feilds in the
> Sysprep.inf.
>
> -Reseal = Windows Welcome (OOBE)
> Windows Welcome will only process a few of the supported
> feilds in the sysprep.inf and will also process the
> oobeinfo.ini.
>
> For Corporate Deployments you will want to use Mini Setup.
>
> Hawkens
>

> >-----Original Message-----
> >Hello everyone,
> >
> > What is the difference running and not running mini-

> setup when you

> >reseal a computer during sysprep? Basically you have

> the mini-setup and

> >some type of mini-setup that is more fisher price?
> >
> >Thank you
> >Alex Anderson
> >
> >
> >.
> >