Windows Preinstallation Kit

No, the preinstallation kit is for System Builders who want to customize the installation.  It is not used for installing the OS....

It usually includes the following:

A set of software tools necessary for correct and efficient preinstallation and customization of the software is included in each multipack and called the OEM Preinstallation Kit (OPK).

During preinstallation using the OPK, you have the ability to customize and control the build. For example, the Windows XP OPK allows you to:

Customize the Windows XP Startup Screen to show your OEM logo.

Customize the Windows XP Start Menu with your favorite application shortcuts.

Control and customize unattended preinstallations using custom configuration sets.

It also allows you to deliver a ready-to-use, built-to-order system by preinstalling and testing all programs and applications, including updated drivers and patches.

Configure and customize Microsoft Internet Explorer, including Favorites and URL lists containing your Web site.

Ensure compliance with the terms of the Microsoft Distribution and Preinstallation Agreement.

It saves valuable time preinstalling Windows XP using a configuration set that does not require you to manually answer setup questions one by one.

Using the Setup Manager tool and your newly acquired Microsoft Windows XP product, you can preinstall the Windows XP operating system for different computer models with or without the use of a network or hard-disk duplicator.

Hope this helps explain it.....

RE

Also..  the PIK works a lot like Bart's PE Builder...  You will see this product mentioned a lot in the EE forums..  To do want you want to do, you may want to ck this out:

http://www.nu2.nu/pebuilder/

Also ck this regarding WinPE:

http://www.jsiinc.com/SUBN/tip6800/rh6818.htm

http://www.jsiinc.com/SUBL/tip5800/rh5805.htm

I found a MS word document that explains how the kit is used for distribution.  Unlike many of these documents from MS, it is a pretty easy to understand read, explaining the different methods that you would use to push these installs out to your machines...  primarily by imaging the systems...

Anyway, here is the dnload link....

http://download.microsoft.com/download/5/7/7/577a5684-8a83-43ae-9272-ff260a9c20e2/OPK.exe

FE

Hi,

I saw you still have the other thread open:

https://www.experts-exchange.com/questions/20842315/How-Do-I-create-a-re-install-CD.html

I don't really understand what you mean by saying, "All I seen that it would do is install a base install with the options to install other drivers perhaps?"

Surely an OEM pre-install is exactly that - a base install with pre-defined driver options?

You are creating a pre-build. In other words, you would use RIS and OPK to *SHIP OUT* a machine with XP, Service Packs, IE updates, OE updates and DirectX, along with all necessary drivers, ALREADY ON IT.

When the user powers on his machine for the first time, he would see a funky mini-setup with your branding on it, he wouldn't have to faff about with CDs or floppies or anything like that. It's all already on the machine.

This means you can clone new machines by the dozen in a pre-installed capacity. The user then just goes through the final stages himself.

You would still need some other technology to create recovery CDs - eMachines for example use OPK to create the pre-build that's on the machine when you buy it. But before they ship it out, they burn an image of that PC onto a set of CDs using Norton Ghost, and the first CD in the set has an OEM license of GHOST which is opened using a bog-standard batch file.

So, OPK supplies the end user with a customised eMachines branded mini-setup.
Ghost (for them) is the technology that allows the END USER to restore the HDD to that preinstalled configuration.

---

I used GHOST to upload an image of my own PC onto a CD along with a boot image from a bootable FreeDOS floppy containing the following files:

HIMEM.SYS
OAKCDROM.SYS
GHOST.EXE

CONFIG.SYS
containing the lines
DEVICE=himem.sys /testmem:off
DEVICE=oakcdrom.sys /D:MSCD000

AUTOEXEC.BAT
containing the lines
MSCDEX/D:MSCD000 /L:Z                                                                        (This tells it to mount the CDROM on Z drive)
GHOST.EXE -clone,MODE=pload,SRC=Z\IMAGE.GHO:1,DST=1:1

The net result of this is, that I can roll my system back to the point where it has XP Service Pack 1a and all Critical Updates pre-installed on the system, along with the latest patches & Service Packs for Internet Explorer 6, DirectX, Outlook Express and so on.

But, the difference between you and me, is that I am building a recovery CD for my own system which already has all its settings. I don't need to "rebrand" my PC, or anything like that. So, I can skip that business and just create the recovery CD.

You are planning to build a recovery CD for an OEM pre-install which REQUIRES the user to put his/her own information in.
So, your image would have to go through the SYSPREP business, or whatever OPK processes are suitable for your needs, BEFORE you create the GHOST image.

"You are creating a pre-build. In other words, you would use RIS and OPK to *SHIP OUT* a machine with XP, Service Packs, IE updates, OE updates and DirectX, along with all necessary drivers, ALREADY ON IT."


This is what I am most interested in.   I did not see where you would install ie updates, and certain drivers on the prebuild so they would be installed automatically when transferred to the client PC for the OEM install

So, that's how to create a general central install for ALL machines.

All you then have to do is use the OEM Preinstall Kit to convert this into a re-deployable image.

tstaddon,

ok it looks like we are getting somewhere.

The drivers that I have are mostly Executable ie the video drivers installation is a .EXE that installs the video drivers and utilities that show up in the start menu.  Same for the USB Drivers, Network Drivers etc.  I am not sure how to get those exe files to be installed on the preinstallation image without having to take the extra steps to manually go through them on each machine

I will read your above links.

Randy

Also,

http://www.msfn.org/unattended/xp/installhotfixes.htm

This tells you how to integrate the HotFixes into the Windows 2000 CD - which is a bit more complicated than using the IEAK to do it, but probably a lot slicker!

As for integrating other applications, I would DEFINITELY recommend you include the following, since I cannot really envisage a situation where you wouldn't want them:

http://www.msfn.org/unattended/xp/applications/wmp9mm2.htm   - Media Player 9 & Movie Maker 2
http://www.msfn.org/unattended/xp/applications/netframework.htm - .NET Framework 1.1
http://www.msfn.org/unattended/xp/applications/windowsmessenger.htm - Windows Messenger
http://www.msfn.org/unattended/xp/applications/directx.htm - DirectX
http://www.msfn.org/unattended/xp/applications/msjava.htm - MS Java
http://www.msfn.org/unattended/xp/applications/powertoys.htm - XP PowerToys

For a really flash way of doing it -

http://xpinstall.voidfx.com/

If they are EXE based installs, you simply add them to the $1 folder as per one of these other applications.

The one thing you have to remember is that in the unattend file, the OEMPreInstall option must be set to YES to copy these files over.

The thing I do not see with the above urls is a way to strip the data after the unit has the software installed.  is it possible to use the sysprep command after the OS installation has taken place?

Randy

Yes, that's the point of SYSPREP.

Sysprep strips out the owner info, product key, System ID (SID) and activation status, so a backup of the hard drive does not have to be put back into EXACTLY the same machine. In oher words, you use SYSPREP if you want to copy a working Windows 2000/XP partition to another system with the same mass storage controller, HAL and chipset (ie any machine with a similar motherboard).

The operative phrase "same mass storage controller, HAL and chipset (ie any machine with a similar motherboard)"

There are ways around this, but it can get messy...

Glad to see we are coming around on this here...  Lots of help, I see..!!

FE

Think of it this way:

For Windows 3.1 and DOS, you could simply XCOPY the C drive of a hard disk up to the network and use XCOPY again to download those files to a similar machine. It didn't matter what apps were installed, by and large this would replicate your working machine without too many headaches.

For Windows 95, it wasn't quite as simple. You needed a truer "image" of the disk. Hence products like Ghost, which clone the whole logical partition (or disk) rather than just the files on the disk. To be sure the image would work on a new machine, Windows itself would re-detect the hardware (a formality really).

To use the machine on a network, you would have to manually change the workstation's name after downloading the image. This, however, is also a formality - you just right-clicked on My Computer, selected Properties, and changed the name.

For Windows NT based operating systems, not only do the NETBIOS name AND the SID need to be changed, the entire registry would have to be forensically scanned to replace every instance of the old SID with the new.  

On top of that, the file system itself - NTFS - is tied into the security of the OS, so you DEFINITELY need to use imaging to clone a completely operational system. But more than that, the security of the file system will have to change to reflect the change of the SID and all security accounts on the PC.

It's far too involved to do all this work manually. So, you really need a third party tool to do it for you.

Ghost Walker - which comes with GHOST - was designed originally for NT, and it prompts for a new workstation name. After that, it generated a new SID for the workstation. It then did a forensic search-and-replace of the Registry to replace all instances of the old SID with the new.

SYSPREP is a lot more elegant: not only does it do this, it re-runs the MINI SETUP, which is something that normally happens after the first reboot when you are installing 2000 or XP.

SYSPREP.INF is simply a file that contains a list of answers it has. So, SYSPREP.INF as an answer file allows you to either ask the user (through a mini-setup wizard) what country they're in, what language, the owner's name and company name, and so on. You can tell it to get an IP address, join a workgroup, set the display resolution -or you can leave the INF file virtually blank and require the user to put everything in himself/herself.

I would recommend you install Windows 2000 or XP to a new machine, then simply extract DEPLOY.CAB into C:\SYSPREP and run the SYSPREP EXE file with the -PNP and -NOSIDGEN parameters. These switches mean it'll re-detect PNP devices, retain the existing SID, but prompt the user for all other phases of the setup.

After the reboot, you'll be able to see what the mini-setup deals with - and, at the end of it, you will see that the applications and drivers that were on the machine before you ran SYSPREP will still be there.

Then, take a look at an example SYSPREP.INF (there are many on the Internet) and you should get a good idea of what it actually does.

Nice explanation ts...

I thank you!

Here's an example SYSPREP.INF with comments:

[Unattended]
UnattendMode = FullUnattended                                    No user Interaction
OemSkipEula = no                                                        Display the EULA "Yes to accept" dialog box
ExtendOemPartition = 1                                                "Grow" the partition to fit the drive (if no other partitions on it)
DriverSigningPolicy=Ignore                                            Allow non-certified drivers to install without warning
OemPreinstall=Yes

OemPnPDriversPath=Packages\nic;Packages\audio;Packages\video;Packages\chipset;

' (Which corresponds to C:\Packages on a machine being SYSPREPped)

InstallFilesPath=C:\sysprep\i386
TargetPath=\winnt

[Oem_Ads]
 background=background.bmp

[GuiUnattended]
TimeZone=10                                                              Set the Time Zone to this preset value
OemSkipWelcome = 1                                                  Bypass Welcome screen
OemSkipRegional = 1                                                   Skip regional options page
OEMDuplicatorstring="XP Pre-Install by RJohnson"          The title of the mini-setup routine

[UserData]
FullName="TSTADDON"                                               The name of the machine's owner (leave this line out if not known)
OrgName="EXPERTS-EXCHANGE"                                 "Workgroup" name (leave this line out if not known)
computername=*                                                        * indicates a random machine name based on the orgname

[Display]                                                                    Pre-define the screen resolution after setup
BitsPerPel=24
Xresolution=1024
YResolution=768
Vrefresh=60

[TapiLocation]                                                            Pre-define the area code (for modems)    
AreaCode=937

[Networking]
InstallDefaultComponents = Yes                                    Don't customize the network settings

[GuiRunOnce]                                                              Section to install additional applications AFTER Windows Setup  

[data]
UseBIOSToBoot = 1
UnattendedInstall = Yes

;The last 2 sections allow a SYSPREP image to install on a machine with ANY of the drive controller types matching the
;plug and play IDs of the lines below. You can add other controllers, like Ultra320 SCSI and Serial ATA, to this section of the
; file.
;
;Format of this section is:
;   PlugAndPlayID = location of supporting *.INF file
;
;Any lines ending in MSHDC.INF are for IDE
;Any lines ending in SCSI.INF are for SCSI

[SysPrep]
BuildMassStorageSection=Yes

[SysprepMassStorage]
PCMCIA\*PNP0600=%systemroot%\inf\mshdc.inf
*PNP0600=%systemroot%\inf\mshdc.inf
PCMCIA\KME-KXLC005-A99E=%systemroot%\inf\mshdc.inf
PCMCIA\_-NinjaATA--3768=%systemroot%\inf\mshdc.inf
PCMCIA\FUJITSU-IDE-PC_CARD-DDF2=%systemroot%\inf\mshdc.inf
*AZT0502=%systemroot%\inf\mshdc.inf
PCI\CC_0101=%systemroot%\inf\mshdc.inf
PCI\VEN_10B9&DEV_5215=%systemroot%\inf\mshdc.inf

;End of File

ok one last quick question

after the unattend cd install is done everything is there a way to make it run the sysprep command and then reboot itself


Ie I stick the CD in , it installs, runs the sysprep command and then either shuts down or reboots or just run the sysprep command and then sit there for me to take cd out and shut it down?

Thanks

Randy

I have never used such a command...  hmm  

Here is a list of all the switches, if you want to visit it...  also a nice example of a script..

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q196/6/67.ASP&NoWebContent=1

FE

ok here is the last question.   for real this time.


I have created the cd and the OS installs just fine,

I put a touchscreen program that installs touch screen software and drivers in the GUI Run once section when the computer boots into the factory mode the application starts and installs the software and drivers.

The problem is after the computer is resealed and is started up by the end user it runs the software installation again.  

How do I get the software to install during the initial installation and not again when the computer is resealed and ran the first time by the end user?

If the software's already been run prior to the SYSPREP, you shouldn't need to include it in the GUI RunOnce.

As ts says...  since it has already been installed, you will not need it in the answer file..  Whatever you have in the GUI Runonce section will be run when the hard drive is booted....

So you are using a touchscreen, eh?   Nice..  never messed around with one of those...  just curious, what software are you using for it?  

FE

Put it this way:

If you set up your PC with Office, IE6 Service Pack 1, Windows Media Player, Adobe Photoshop, AutoCAD, Novell Client, hardware drivers and any other apps, and then SYSPREP an image, all machines that are built with that image will come preconfigured with all those apps, drivers etc pre-loaded.

The SYSPREP answer file's RunOnce entry is best used to specify actions that can only take place AFTER the machine has been personalised.

For example, joining a PC to a domain requires it to have a unique SID.

Naturally, a PC that has been cloned will only know it has to generate a new unique SID if the image itself has been SYSPREPped.

So you would run DCPROMO (the Active Directory Installation Wizard) in GUI RunOnce, rather than installing it on the base PC BEFORE running SYSPREP.

after reading the last comment again,  There is a separtate answer file for sysprep?   Besides the winnt.sif?

Thanks

Randy

Randy,

Call it what you like - it's pretty much the same file.

Of course, it would defeat the object of calling it an "unattended" setup if the user was ever prompted for the name and location of the answer file, so there are three ways to specify an answer file BEFORE setup runs.

1 - SYSPREP.INF in the SYSPREP folder.

Basically, from your POV, it's the same as the UNATTEND.TXT or WINNT.SIF file you've been using, but with the user name, product key, workgroup etc stripped out of it (as you'll be wanting the end user to put this in).

2- WINNT.SIF

A bootable XP install CD will always look for WINNT.SIF either in the I386 directory on the CD itself, or on a floppy disk. If it doesn't find the file in either location it will assume you don't want to use an answer file.

3. UNATTEND.TXT

UNATTEND.TXT is exactly the same file as WINNT.SIF, but you use it as a command line parameter (eg within a batch file or login script). For that reason yuo can stick the answer file anywhere you like, so long as the command line can find it.

For example, this batch file:

@ECHO OFF
CLS
NET USE Z: \\MyServer\XPInstall
WINNT32 /U:z:\DesktopPC\unattend.txt \s:Z:\I386

is a batch file that will commence SETUP using an answer file for Desktop PCs, on the Z drive.

So would it be possible to do a 1 - SYSPREP.INF in the SYSPREP folder option and still do an unattended install like I am doing now with the winnt.sif?

Randy

Sorry for the sporadic responses, my wife gave birth on Friday so I've been a little preoccupied.

Yes, by all means.

You can use the winnt.sif to automate the setup from CD, then create a copy of that file as SYSPREP.INF.

In the SYSPREP inf file, remove the bits you don't need.

For example, if your kiosk software is installed by the WINNT.SIF file, there isn't any practical need to leave it in the SYSPREP.INF, unless you want it re-installed.

Also, your WINNT.SIF might specify a generic product key, your own personal org name and workgroup, so you can get the base PC image up and running with the minimum of effort, you'd DEFINITELY want this information stripped out of the SYSPREP file if you want the customer to put in his/her own organisation settings.

I don't mean to be cheeky, but you do still have the other question open - do you still need more info?

https://www.experts-exchange.com/questions/20842315/How-Do-I-create-a-re-install-CD.html

Congrats on Your Baby :-)


The problem I am having is that I put the Touchscreen software in the Gui Runonce  of the winnt.sif  so it runs the first time around which is great,  but it also wants to run after the computer has been resealed for the user and when this happens the setup wants to uninstall the software,

So what I am trying to do is INstall it during Factory installation and not after the computer has been resealed for the end user.

You done a great job at answering my origional question so I moved on to a new question to carry on the conversation

Thanks

Randy

Not to get too far off subject..  But...  That is awesome TS..!!!!  Boy or Girl..  just got to ask..

Again, sorry for getting off topic here..!!  Also, good explanation of the answer files too..!

FE

Girl, 5lb 12 oz. Born two weeks early, courtesy of Mummy getting very poorly.

Randy,

Fine by me - but I'd suggest you close the other thread if it's finished - you'll only get the mods hunting you down if you don't.

Kenneniah put you on track with the OEM stuff, gemarti provided a link which answers to your very last point, and Fatal_Exception's also been handy with turning up documentation, so why not split the points between them?

TST can you help me out with this?

The problem I am having is that I put the Touchscreen software in the Gui Runonce  of the winnt.sif  so it runs the first time around which is great,  but it also wants to run after the computer has been resealed for the user and when this happens the setup wants to uninstall the software,

So what I am trying to do is INstall it during Factory installation and not after the computer has been resealed for the end user.


Thanks

Hmm..   If you are installing it during the factory mode, you should not need to include it in the answer file..  at least that is my understanding....   The reason it wants to uninstall is that it sees that it is already installed and uninstall is the only option at that point...  

TS..  what do you think...  ??

FE

I want to automate the installation of it  or get it to start automatically in factory mode.  How do I do that so it only runs in factory mode and not in end user mode.  

Anybody else have any ideas how I can get software to automatically install off the CD in factory mode and not in end user mode

Thanks

Randy

Fatal_Exception is right. The only obvious reason why this is happening is because when you are SYSPREPping the machine, you are in effect telling the PC to run the setup again.

Again, a custom application needs to be setup in either WINNT.SIF or SYSPREP.INF, but NOT BOTH.

If a software option is put in WINNT.SIF it's installed along with Windows XP itself, in the context of setting up Windows onto a PC for the first time.

The "Mini-Setup" is a subsection of that install process where Windows collects personal information about the end user, the product key, company name etc, and you can at this point install stuff specific to END USERS.

In other words, the "Mini-Setup" is the "registration" and "post-registration" part of Setup.

SYSPREP simply re-runs the Mini-Setup on the machine.

To use an analogy, WINNT.SIF is a bit like having a checklist to help you assemble a kit car with all the trimmings. You can use the checklist over and over again, with different kit cars, but you will only ever apply it to a kit that isn't already assembled.

If you want a CD jukebox to be installed into EVERY kit car you sell, you'd put it in your checklist.

The "Mini-Setup" (ie final step of that process) is the process by which you register the vehicle in someone's name (license plate, tax, insurance, roadworthiness checks etc).

It doesn't matter if it's a kit car or not - once a car is sold, it always has to be registered BY THE NEW OWNER before it can be put on the road.

So, if you sell the car, you will expect a buyer to go through the "Mini-Setup" process himself to register the vehicle in his name. But you wouldn't tell him to install the CD jukebox again, because it'll already be fitted.

That is my point exactly,  I don't know If I am missing something or what here.  I want the software to install when the machine is setup like your car analogy I want the cd jukebox installed at the factory, and not when the end user gets it.

That is what happens when you put it under the GUI Runonce function of winnt.sif


Randy

Nice analogy TS..  really like the way you put it...  :)

If you are installing it in Factory mode, do not put it in the GUI Runonce function of winnt.sif...  It is already installed...  Take the reference out of there and try it again...

FE

I do not want to install manually though in factory so how do I get it to install in factory automatically when the computer boots into factory.

Here is the process

Cd goes in-->Cd Installs windows-->Computer Reboots-->Computer Starts in Factory mode-->

At this point it runs the gui runonce-->installs the touch screen software --> I then reseal the computer

Now if the end user logs in, it runs gui run once again and trys to uninstall the software.


That is a problem

If I take it out of winnt.sif/gui runonce how do I get it to install?

Thanks

Randy

Why don't you install it first, before you run sysprep -factory...??  And do not place any reference to it in the answer file...??

http://www.microsoft.com/windowsxp/pro/using/itpro/deploying/factorymode.asp

Is there a way to do this right after the windows installs before it reboots into factory mode?

I also thought about adding it to gui runonce and have the install batchfile check to see if the directory exists in program files and if it does do not install.  

Thoughts

I don't have near the experience with Sysprep as TS does, so I am probably way wrong here..  but I would think you would prepare your system with the application already installed...  Once everything is ready and running correctly, then you use the sysprep -factory command to prepare the image for distribution..  Upon reboot, it does not run the mini setup wizard, but allows you to dnload additional drivers, etc...  Then you reseal it to get it ready to go to your endusers...  I don't think you need any reference to it in the answer file after that...

but perhaps we need to wait for TS to come back in, eh..???  

FE

The idea here is to use the preinstallation Cd as an automated install disk.  Instead of ghosting the image , I want to just use the installation CD and it is working fine accept for the touch screen software and drivers install during factory and then during end user because of Gui Run once.

I have it the way I want it accept for the Gui Run once issue.


Randy

I think you're going to have to go back to first principles.

When you use WINNT.SIF in conjunction with an XP CD, this is only to create YOUR OWN generic install with the minimum amount of intervention. No more, no less.

Sure, you can install apps with it, but ONLY apps you want on EVERY machine built with that CD and SIF file.

This is the thing you SYSPREP; this is the FACTORY build. It's something only YOU will ever use.


To create the END USER'S build, you need to visit an individual machine, apply the FACTORY build to it, and RESEAL that machine.

To explain the two seperate uses of SYSPREP:

SYSPREP -FACTORY tells the machine that the next time it boots up, it will get a new SID, but it will NOT run Mini-Setup. It will do a PNP scan, update drivers, install apps and a few other things, but NOT give you any need to personalise the machine in any other way.

It is "factory" in the sense that YOU are the factory; you would use this switch if you wanted (for example) to configure a batch of Dell GX260s so that each one is up and running and ready to use, straight out of the box, with all the apps already loaded, without having to put in any organisational information.

THIS ONLY APPLIES WHILE THE MACHINE IS IN YOUR "FACTORY".

SYSPREP -RESEAL is the option you use on a factory-built PC prior to shipping it out. This means you power up a factory-built PC, make sure it's running OK, that all the customer's software is loaded, etc, and THEN reseal the machine. It's the software equivalent of shrink-wrapping a customer order.

Mini-Setup is set to start the next time the machine starts up at the next boot, so the customer can personalise the machine, but other than that, the machine arrives in a ready-to-use state.

The ONLY time I would use a SYSPREP.INF file on a reseal, is if I had a VIP customer paying a little extra for their machines to be pre-configured with organisation details put in for them.

-------------

Note: I personally haven't ever followed this process. As far as I'm concerned, the command line SYSPREP -PNP -RESEAL does a combination of the two tasks.

So, if I had a job lot of 100 Dell GX260s, I'd set one up the way I want them all set up, then use that command line, and upload that image to a RIS server or use GHOST to clone the hard drive.

Each machine would then have a basic image on it; I could always add more software to the machine and then re-run SYSPREP -PNP -RESEAL to creat more images.

That is what I am trying to do we have a computers that will go out the door with the same software on all machines.

I decided to go with the check to see if the program is installed and if it is , do not install it.

I have it working on the computer now I just need to add it to the CD

I will let you know how it goes.

I appreciate all your help, even though I am confused as to why my question does not get answered.  I guess I am not communicating what I need very well :-)

Thanks Again

Randy

Good explanation TS...   RJ..I just think we are on different pages here...  Tell you the truth, I am following the thread closely and I think you are making it hard on yourself..  My problem arose at the first when you were using the Preinstallation Kit, as I have never even opened it up to see what it contains..  :)    I have just used Sysprep off the installation cd, or the one dnloaded from the MS site..  But do not get frustrated here, we will all try to help in any way possible...  In fact, I am already learning some things I was a little fuzzy on...  so just keep asking the questions..  

FE

I am not upset at all really I am not.  This is really good information.

I am not sure how to explain what I need to happen, more than  I already have.

Instead of using ghost to ghost the image and install we are using the winnt.sif CD to do it.  Reason being is because the touch screen software is standard on everyone of our units.  so Doing it manually on every unit is not an option.

I believe the batch file work around will work nicely.  Though I am up for better suggestions.  There has to be a way to install software in factory mode automated and not have it run for the end user in GUI Run Once.

Keep in Mind I am a Factory guy not the end user



Randy

Randy,

If you are ONLY using the WINNT.SIF then you will get this "problem"; the fact is, the SIF file is ONLY for use when you are setting up the machine inside your lab, NOT for when it gets to the end user.

SYSPREP needs to be run on the machine to prep it for shipping out.

Let's say you have a "normal" bootable XP installation CD, and all you do is add the install files for the touchscreen app, so that the directory of your "new" bootable XP install CD looks like this:

\I386\                              [Slipstreamed with SP1]
\I386\WINNT.SIF                        [Your SIF file]

\$OEM$\$1\Install\                        [Apps you want to bundle on the CD]
\$OEM$\$1\Install\TouchScreen\                  [Setup files]
\$OEM$\$1\Install\Windows Media Player 9\            [Setup File]

\$OEM$\$1\SysPrep\                        [Files expanded from DEPLOY.CAB]

Your WINNT.SIF should, in addition to all other options you want to predetermine, contain this EXACT set of directives:

[GuiUnattended]
    AdminPassword=password
    Autologon = Yes
    AutoLogonCount=1

[UserData]
    FullName="Randy"
    OrgName=Randy'sCompany
    ComputerName=*
 
[GuiRunOnce]
    Command0 = "START /WAIT %systemdrive%\install\TouchScreen\Setup.exe"
    Command1 = "START /WAIT %systemdrive%\install\WMP9\MPSetupXP.exe /Q:A /R:N"
    Command2 = "START /WAIT %systemdrive%\SYSPREP\SYSPREP.EXE -PNP -RESEAL"

This will mean that during the setup process, the machine will be set up in YOUR name, a folder will be created on the C drive of the PC, called INSTALL; and that folder will contain the different applications. A seperate folder will be created for SYSPREP, and the files copied into it.

Once setup is complete, each additional program will be set up in sequence. Assuming you know the command line options for silent / answered installation of the touchscreen software, your IN-HOUSE use of this CD will register XP in your name, then install these apps.

Finally, once these apps are ALL set up, SYSPREP will automatically remove your own organisational settings and seal the machine.

At the next reboot, it will know NOTHING about your own organisation, and will ask the end user to supply HIS organisation settings.

You could then simply bung a copy of this CD in with your user's machine - as far as the end user is concerned he has a single bootable CD which will install XP from scratch, along with all the apps you've bundled in.

Remember, if you do it this way the user will ONLY have it "ready-to-run" when he/she first takes delivery of the machine.

To actually give the user a complete hands-free installation of XP, you would need imaging software.

TS...  You need to write a book on Sysprep...  :)

This thread is one of the most interesting and informative sysprep threads I have been involved with..  Kudos to you, my friend..!!  

What you say totally makes sense I follow you, but I still have the problem that when I put stuff in GUI Run once it actually runs twice.

ONce during the factory startup and once when the end user starts the machine for the first time.

In my case it should be called Guiruntwice or GuiRunOnce During Factory and Guirunonce during enduser first startup.


Boy I wish they had voice chat on here :-)

Randy

Hilarious..!!

Fatal,

My ego is duly inflated. I'll nip over to the Suggestions forum and request a Deployment TA...

Randy, What package is it? We use SMART Boards at the college (electronic whiteboards) and I do find, occasionally, that the software appears to run a "registration" mini-setup itself. This is similar to MS Office, which by default requests specific user information for each user.

Perhaps if you can find the setup command lines for the touchscreen software you use, maybe you can make that in itself an unattended install, so it won't matter if it does run twice!

That is an interesting idea.

What I did to get around it is In the batch file that runs the software I check for the existance of the TouchKit Directory in the program files and if it exists I do not install.   It worked out nice because a black window did not even come up when it ran.

If it runs twice it trys to do an uninstall of the software.


Randy

Would it be this package?

http://www.dfiusa.com/p_m_download/Files/Touchkit%20XP.html

If so, it's an InstallShield 6.02 SETUP.EXE; so to creat an answer file for the setup, run SETUP.EXE with the command line option /R, and complete the setup, selecting NO to the reboot prompt.

After the software is installed (and the PC is rebooted) there will be a new file called SETUP.ISS in your Windows directory and it will start off like this:

[InstallShield Silent]
Version=v6.00.000
File=Response File
[File Transfer]
OverwrittenReadOnly=NoToAll

All you have to do is copy this file into the TouchKit setup directory on your unattended CD, and update WINNT.SIF for the command line to use SETUP.EXE with the parameters /S and /SMS - for example:

[GuiRunOnce]
    Command0 = "START %systemdrive%\install\TouchKitXP\Setup.exe /S /SMS"

Remember of course that when you use SYSPREP, you make sure the GuiRunOnce section in it does NOT run Touchkit Setup.

(I meant SYSPREP.INF in that last paragraph)

No but I am going to email the creators of the one that I have for something similiar.  I thought of this same thing yesterday on my way home from work.  Thanks for example :-)

Randy

Randy..  A friend and I am working on developing an idea that would utilize touch screens.

Would you mind telling me what application you are using for this..??

And what Monitor(s) you might want to recommend..??

Thanks,

FE