Jump to content

Script crach with Unattend Win2000 install


Guest tjabobom

Recommended Posts

Guest tjabobom

I have tried unattended installation with Win XP and it workt just fine to the end..

Well then I want to do the same with Win 2000 Pro. So with my Unattended XP knowlege I build up my unattend structure. I unpacked deply.cab from w2ksp4 and made unattend.txt file and fixed a share with w2k i386 same as I did with XP..

Well then I boot from PE to run the unattend script the script seems to halt and reboot no error msg....

Can I get some log file from an unattended installation to se what happend???

here is my script same as worked with XP

set AnswerFile=.\unattend.txt

set SetupFiles=.\I386

.\I386\winnt32 /syspart:c /tempdrive:c /s:%SetupFiles% /unattend:%AnswerFile%

my last slimed unattend.txt:

;SetupMgrTag

[Data]

AutoPartition=1

MsDosInitiated="0"

UnattendedInstall="Yes"

[unattended]

UnattendMode=FullUnattended

OemSkipEula=Yes

OemPreinstall=No

[GuiUnattended]

AdminPassword=*

OEMSkipRegional=1

TimeZone=85

OemSkipWelcome=1

[userData]

FullName=användaren

OrgName=VEAB

ComputerName=PCtest

[identification]

JoinWorkgroup=ARBETSGRUPP

[Networking]

InstallDefaultComponents=Yes

I have tried several unattend.txt file some created with the tool in deploy.cab..

I tryed to find how to troubleshooting unattended installations but no result..

Is there any with any ide?????

Per

Link to comment
Share on other sites


Try it without your username and specify your regional info. This will eliminate special character conflicts if the region is not set. I've included mine below

[Unattended]
DriverSigningPolicy = Ignore
ExtendOemPartition=1
FileSystem = ConvertNTFS
Hibernation = No
NtUpgrade = No
OEMFilesPath = .\$OEM$\;.\;WINNT\HPQ\;
OemPnPDriversPath = WINNT\;WINNT\HPQ\;
OEMPreinstall = Yes
OemSkipEula = Yes
OverwriteOemFilesOnUpgrade = No
TargetPath = winnt
Repartition = Yes
Unattendmode = FullUnattended
UnattendSwitch = Yes
WaitForReboot = No
Win9xUpgade = No

[Data]
AutoPartition = 1
MsDosInitiated = 0
UnattendedInstall = Yes

[GuiUnattended]
AdminPassword = *
AutoLogon = Yes
AutoLogonCount = 3
OEMSkipRegional = 1
OEMSkipWelcome = 1
TimeZone = 4
ProfilesDir = C:\WINNT\Profiles

[UserData]
FullName = "helpdesk"
OrgName = "CompanyName"
ComputerName = "XP01"
ProductId = YoursPlease

[Shell]
;Forces Windows 2000
;CustomDefaultThemeFile = "%ResourceDir%\Themes\Windows Classic.theme"

[Display]
BitsPerPel = 16
XResolution = 1280
YResolution = 1024
VRefresh = 75
ConfigureAtLogon = 0
AutoConfirm = 1

[TapiLocation]
CountryCode = 1
Dialing = Tone

[Identification]
JoinWorkgroup = YourCo

[Networking]
InstallDefaultComponents = Yes

[NetAdapters]
Adapter1=params.Adapter1

[params.Adapter1]
INFID=*

[NetProtocols]
MS_TCPIP=params.MS_TCPIP

[NetClients]
MS_MSClient=params.MS_MSClient

[params.MS_MSClient]

[params.MS_TCPIP]
DNS = Yes
UseDomainNameDevolution = No
EnableLMHosts = Yes
AdapterSections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP = Yes
WINS = No
NetBIOSOptions=1

Link to comment
Share on other sites

Guest tjabobom

Hi!

I want to thank MastaVR6 for respons on my problem...

I have made more tests with my unattended w2k problem...

I booted up in dos with a net disk and run the unattended script with winnt, it worked...

So it seems that the winnt32.exe (w2k pro sp3) crach under PE 1.2, so now I wonder if some one have had problem to execute w2k sp3 winnt32.exe under PE??

I will make a bartPE bootcd and test it...

I will be back...

/Per

Link to comment
Share on other sites

Guest tjabobom

I am back, I have made some more unattended labs!!

Now I have tried to run windows 2000 pro sp3 winnt32.exe under bartPE...

It will not start. So the situation for me is..

I can run Windows XP winnt32.exe unattend under WinPE and BartPE..No Problem

I can run Windows 2000 pro sp3 winnt.exe under dos....No problem

But I cant run Windows 2000 pro sp3 winnt32.exe under winPE or BartPE I cant understand what wrong I do....

Is the any help out there.....???

If I manuly run the winnt32.exe nothing happend just a clear promt show up under BartPE..

The Unattended script:

under winPE it crach with reboot...

under BartPE the command window hang...

/Per

Link to comment
Share on other sites

Well then I boot from PE to run the unattend script the script seems to halt and reboot no error msg....

Where does this happen? How are you calling Winnt32? Do you have a reboot command right after you call the setup? If you can, post the script that you are using to call Win2K setup.

Mike

Link to comment
Share on other sites

Glad I could help.

As for resolving the setup failures, try swapping the drive into another (XP/2003) box and check for the setup logs on the drive.

I don't use winPE/BartPE for building installs- All the setups I deal with avoid the upgrade nightmares, using a complete wipe of the existing OS, and replacing the drive data.

Link to comment
Share on other sites

Guest tjabobom

Thanks for the feedback!!

to mbouchard:

Firts I boot the box into WinPE or BartPE, then I use "net use" to logon and map me to a net share were I have all my files, the unattend script and i386 for Win2000 then I have a start script I call to fix the HD and then start the unattended script..

I have tried to fix the partition c: manualy with pqmagic8.0 and I have used fat32 and then exluded the diskpart in the script..

then when I run my start script diskpart run just fine I dont reboot after diskpart I use the "/syspart:c /tempdrive:c" (any way I have tried manualy run diskpart and then reboot then run the unattended inst. manualy with no results...)

Then when the script call for wnnt32.exe it some how crach the screen went black with a reboot under WinPE but under BartPE the script hung the cmd promt and it will not come back I have to close the cmd windows..

I have also try to run Win2000 winnt32.exe from the promt noting happend, well if I do the same with XP the setup starts...

about reboot command: I use "Exit" it reboot WinPE for me..

I have tried several ways to call Winnt32 no one works for me, I put some off my latest here...

my start script:

@rem SetupMgrTag

@echo off

rem

rem 1. DiskPart

rem

DISKPART /s diskpartcfg.txt

FORMAT C: /fs:ntfs /q /v:sys /y

cacls c:\ /p Everyone:F

rem

rem 2. Unattend

rem

set AnswerFile=.\unattend.txt

set SetupFiles=.\I386

.\I386\winnt32.exe /syspart:c /tempdrive:c /s:%SetupFiles% /unattend:%AnswerFile%

EXIT

rem end of the script

The diskpart cfg file diskpartcfg.txt:

select disk 0

clean

create partition primary size=12000

assign letter=c

active

exit

TO MastaVR6:

I do mainly new installation and wipe the disk with diskpart. what kind of deploy environment do you use? I want to use a 32bit environment so I can use powerfull tools to work with and not be limit with ex. the dos name space.....

I will try to look for setup logs...

Thanks again

/Per

Link to comment
Share on other sites

Then when the script call for wnnt32.exe it some how crach the screen went black with a reboot under WinPE
I gather from what you are saying, that the setup crashes as soon as it launches. If that is correct you might want to look at a couple things.

1) Hardware. While it may seem strange, try a different PC (unless you have already done this).

2) Replace the Win2000 OS files. There is a chance that the Winnt32 file is corrupt.

3) Try and place a pause before the EXIT command. Just on the chance that Winnt32 is stopping and releaseing to the exit command.

4) Try the setup without the CACLS command. It is possible that this is causing it.

5) Try formating to FAT32. Doubt it will work but worth the try.

I do not believe that the cause of all this is the unattend.txt.

As to the question you asked MastaVR6 -

what kind of deploy environment do you use?

I am doing essentially the same thing that you are and have been for quite sometime. Almost everything is automated, except fot the initial boot and info collection phase, which only takes at most 5 min. Once the tech answers some questions they leave and about 2 hours later, the PC is fully setup, including standard apps.

Good luck,

Mike

Link to comment
Share on other sites

Guest tjabobom

Hi!

Thanks for the support mbouchard...and you troubleshooting list

My problem is with winnt32.exe, I have used a CD-set from Dell I have copy i386 two times to my share. Same Problem with crach, Then I looked for a other CD-set I found an Windows 2000 pro sp3 US,, wolla the winnt32.exe started quick and fine I am happy again :)

So to day I have put a oder for a new Swedish CD-set

/Per

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...