Frogger1

Hi Guys

I have been given the huge task of creating a HII image (XP SP3). I have fallen at the first hurdle, the Scripted OS Install is failing on installation. I have created a job which runs on a PC but appears to hang with the status "Setup is running in GUI mode". The installation does not appear to have finished as the resolution is set as 640 x 480 instead of 12800 x 1024 as per the unattend.txt. We are using DS 6.9 SP1. The Scripted Install is XP SP3.

Any ideas why this has failed? Is there a log file I can look at to give me some help?

Thank you

Newbie

tmsmith2

That you used the dialog boxes to create the script job. I would think you would need to have PXE operational, also format the partitition beforehand. Make sure all permissions are set for the altiris account to access the drive. And be sure that all the setting such as key is done in the scripted install setup. If you could give me step by step what you did I can try to help.

deemacgee

Dammit, my post got eaten!! Anyway, the short version goes like this:

Test your SOSI on a model of PC for which Windows XP already has built-in NIC drivers. You might have to find something quite old, or run VMWare Server and test on a virtual machine (Windows includes drivers for the default NIC model [*edit - this won't work if you're using WinPE, so try it in DOS first]). If it works, your SOSI is fine, it's probably just your drivers that need tweaking.

The wizard makes it dead simple to add drivers; just bang them under \\DEPLOYMENTSERVER\DEPLOY\WinOS00(number)\i386\$OE M$\$1\DRIVERS (for example), then go back into the Wizard and click Next until it asks you about including the extra files found under $OEM$ (say yes). After that, run your SOSI, and once it's finished, check for the existence of C:\DRIVERS. If it's there, everything is in place and should be quite OK.

Hope that helps you somewhat?

__________________
I don't want more choice, I just want nicer things!

Edina Monsoon (Jennifer Saunders)
Absolutely Fabulous, "Jealous"

Frogger1

Hi
I used the Scripted OS Install wizard to create the job. Os Windows XP
Professional, OS Language English, using Default Automation (Auto-Select).
The DOS disk image is FAT32.img.
Thank you for coming back to me.
Right I have used the Scripted OS Install wizard to create the job. Pretty
standard stuff, OS is Windows XP Professional, Language set to English,
Automation pre-boot is set to Default Automation (Auto-select). Windows XP SP3
is the OS source files. The DOS disk image is FAT32.IMG. I thought this
partitioned and formatted the disk? Do i need to format before the scripted
install then? I also appear to have 2 boot.ini menu options, one of them
being "Microsoft Windows XP Professional" and the other one is "previous
operating system on C:" Not sure why i am getting this, is this because the
drive wasn't formatted? I've imported an unattend.txt file:
Unattend.txt
;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
driversigningPolicy=Ignore
WaitForReboot=No
FactoryMode=Yes
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
Repartition=Yes
UnattendSwitch=Yes
[GuiUnattended]
AdminPassword="password"
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=4
OEMSkipRegional=1
TimeZone=85
OemSkipWelcome=1
[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX
FullName="A User"
OrgName="Company Name"
ComputerName=%COMPNAME%
[Display]
Xresolution=1024
YResolution=768
BitsPerPel=4
Vrefresh=60
AutoConfirm=1
[TapiLocation]
CountryCode=44
Dialing=Tone
[RegionalSettings]
LanguageGroup=1
SystemLocale=00000809
UserLocale=00000809
InputLocale=0409:00000409
UserLocale_DefaultUser=00000809
InputLocale_DefaultUser=0809:00000809
[Identification]
JoinWorkgroup=WORKGROUP
[Networking]
InstallDefaultComponents=Yes

I'll have to find another PC to test my SOSI on, will let you know if it works on that.
Thanks again.

deemacgee

Most welcome. I am a HUGE fan of the SOSI.
So much better (IMHO) than imaging.

What's your Default Automation platform (DOS or WinPE)?

Hallelujah.

Nope, that should be enough.

Yup, in my experience, if the drive is formatted in FAT/FAT32 and the install launched from DOS, you'll get a second boot.ini option. Don't worry, there are ways around that.

OK, two small things:
1. Display --> BitsPerPel=4
4bpp is 16 colours. Try:
2. You're missing the Unattended --> OemPnpDriversPath section. Have you added extra drivers to the deployment point?

Good luck.

__________________
I don't want more choice, I just want nicer things!

Edina Monsoon (Jennifer Saunders)
Absolutely Fabulous, "Jealous"

Frogger1

Ok got a little further now, thanks for the tips. I had to change my unattend.txt - OemPreinstall=Yes. Also added the drivers in and the install works and completes. It is asking for a reboot at the end even though I have set WaitForReboot=Yes. Also need to create a second partition as the d: drive, what's the best way to do this?

Thanks again for your help.

deemacgee

Umm... okaaaaaay (?)

Another partition? To store the userprofiles in? My suggestion would be: grab a USB hard drive, create the partition structure you're after, format with the relevant file systems. Save it as an image, then use that image in the SOSI build.

I'm actually writing a blog for SOSI configurations (with built-in recovery partitions for quick-restores - especially good in educational/training facilities); will PM you the address when it's finished... might find it useful.

__________________
I don't want more choice, I just want nicer things!

Edina Monsoon (Jennifer Saunders)
Absolutely Fabulous, "Jealous"

Frogger1

Hi, i've finally managed to create my scripted install. Just having another slight issue. I want to make some tweaks which are held in the HKEY_CURRENT_USER keys. I have added a line to the CMDLINES.TXT file to run a .reg file. The settings are not being applied to every new profile created. Any help would be appreciated.

Thanks

deemacgee

You're adding them to HKU\.DEFAULT, right?

__________________
I don't want more choice, I just want nicer things!

Edina Monsoon (Jennifer Saunders)
Absolutely Fabulous, "Jealous"

Frogger1

No I added the keys to HKCU, this still adds them to .\default as this is the hive loaded. I have also tried in .\default but neither work. I have also read that this doesn't always work and people are editing the ntuser.dat file. What is your experience with this?

Your help is appreciated.

Thanks

Sean.Duan

Useful document, please see the document attached.
Page1-7 is about how to build a script OS install task.
I have been succeed with it.

But, actually, to finish a HII task, the OS script installation is not necessary.

To accomplish a HII task, you can install the OS (for example, Windows Xp) manually, optimize the source computer, run sysprep, then capture the image.

It doesn't matter to install the OS on the source computer by an OS script task or by a CD-ROM.

Attached Files

Deployment Solution 6_5 Hardware Independent Imaging v4.pdf (280.9 KB, 9 views)

__________________