[ceez]

it's unattended...in a different way if posting in wrong forum please move... so here it goes....


zup peeps!

I am learning to use sysprep (WinXP_Pro). We want to be able to use it's
capabilities along with Ghost corp ed @ work. we want to have
just a few images and not 40 gigs worth of them!!!

I've done alot of reading today and I am able to create the sysprep.inf file to my liking and run sysprep.exe with the following switches: -reboot -reseal -activated -factory

Everything works fine and sysprep actually goes through the process and windows loads, but just before sysprep starts (after the reboot) I get the a window asking to insert the WinXP CD because it needs a file (the only one I see is c_20127.nls, which is actually c_20127.nl_ in the CD!). I dont know if there are other files it requires since once you give it the path to the CD it copies whatever other files it needs. So does anyone know why it would require these files? I've tried it at work on a test pc and I am currently trying it at home on Virtual PC which gave me the same file request. At work I also received a DLL error message at the end of the sysprep process, right before it reboots so it can start windows, (i'll post that one tomorrow! )

I've read a bunch of articles and none mention anything about copying files.

Any thoughts?

Thkz

ceez

[gtaylor]

.NLS files are used for language support. Check the regional and keyboard settings specified in your SYSPREP.INF file.

[ceez]

gtaylor, thkz for the relpy.... I am leaving the default settings (US). Isn't it not supposed to ask for files if it's the default settings?

thkz for the feedback!

ceez

[turbomcp]

post your sysprep.inf file here and ill tell you whats wrong
(without sysprep.inf it will work for sure)
its something with the inf file
are you sure you set english to default
set as default and apply to all profiles?

[turbomcp]

check cryptographic service is running

[ceez]

turbomcp, here's my sysprep file

Quote

;SetupMgrTag
[Unattended]    OemSkipEula=Yes
    InstallFilesPath=C:\

[GuiUnattended]
    AdminPassword=blahblahencrypted
    EncryptedAdminPassword=Yes
    AutoLogon=Yes
    AutoLogonCount=1
    OEMSkipRegional=1
    TimeZone=35
    OemSkipWelcome=1
    OEMDuplicatorstring=Image-02-10-05
; === Registry path for OEMDuplicatorstring

HKEY_LOCAL_MACHINE\System\Setup\OemDuplicatorString

[UserData]
    ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    Fullname=""    OrgName="my company."
    ComputerName=

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

[Identification]
    JoinWorkgroup=WORKGROUP

[Networking]
    InstallDefaultComponents=No

[NetAdapters]
    Adapter1=params.Adapter1

[params.Adapter1]
    INFID=*

[NetClients]
    MS_MSClient=params.MS_MSClient

[NetServices]
    MS_SERVER=params.MS_SERVER

[NetProtocols]
    MS_TCPIP=params.MS_TCPIP

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

[params.MS_TCPIP.Adapter1]
    SpecificTo=Adapter1
    DHCP=Yes
    WINS=No
    NetBIOSOptions=1
    DefaultGateway = 10.201.1.2
    DNSServerSearchOrder=10.201.1.200,10.201.1.201

[Sysprep]
    BuildMassStorageSection = Yes

[SysprepMassStorage]

*note: [sysprep] and [sysprepmassstorage] was added to the file after encountering another prob explained below, will test this tomorrow*

I had to end up copying the i386 folder to C:\ and changing
InstallFilesPath=C:\sysprep\i386
TO
InstallFilesPath=C:\

this way it looks for that *.nls file and anyother files on C:\. but why would sysprep need to look for any files if it's default KB and regional settings!!!
again, when using setupmngr i leave the default settings which is US.

I was able to test the sysprep today at work. I installed Windows, configured it to our liking and installed all our software. I ran sysprep with the following switches -reseal -activated -mini. The PC shutdown, booted with a ghost CD, created image of the drive. once completed we loaded it onto a different machine, as soon as we got past the DELL post screen we just got a black screen and it would not go anywhere. I googled the prob and found that by adding:

Quote

[Sysprep]    BuildMassStorageSection = Yes

[SysprepMassStorage]

it might help the situation, something about building the mass-storage on the machine. I've read the deploy.chm file that comes with the support tool but it seems a bit iffy. Now I am waiting for tomorrow so we can try it out again with these 2 new entries in the sysprep.inf file

any thoughts on a black screen without reaching windowsXP at all?

thkz and hope I was able to explain this correctly.

ceez

ps- the host image came from a dell precision 340 and we're loading it on an older dell optiplex GX110

[ceez]

*bump*

[phaeton]

Dude sorry i can't help you but you might want to edit your post and remove the productkey and maybe the encrypted password.

[turbomcp]

so whats the problem now?
you got over the nls files by adding the i386 into the image?
and now the problem is black screen after using ghost?
are all machines same hardware?

[~ketchup~]

hi!

I've the same problem with Windows Server 2003!

If I make the same installation from the original CD I've no problem.

mfg
j.

the one difference I found is that after an original CD installation there exists a c_20127.nls in c:\windows\system32\dllcache and in c:\windows\systems32.

with nlite there is this file only in c:\windows\system32

I think it's not a problem of sysprep!!!!