You guys should really build your images on a Vmware Machine, you can take snap shots and you don't have to make ISO just go off of snap shots, then use BART PE to make a virtual to physical computer.

V TO P smile

I just updated my Vmware Server with the new version of the Driver Packs and has worked on 4 of 4 so far

Dell GX 620
GX 240
GX 260
Otiplex 755
Will test more and upload a video or something when I got time

Dude

Just register it before, then copy the profile you created the image to all users or default users, problem solved smile

Nope

THe drivers get installed after you sysprep and the scripts delete the files that are not used, but you need to have a huge driver directory in all off your images, I wanted to just add in Lan Drivers and run a script to pull the drivers off a nas located on my campus network.

I use this method here on campus for over 10,000 computers and it's about a %99 working smile

5

(7 replies, posted in Universal Imaging)

I'm going to make a video of my process with my co worker this week

I'm having the same issue as are 5 of my co workers

I'm going to documents my way to make images but I can't without the sound drivers, they fail to download after 40mb or so

I have the old version on my NAS but I want to do my method with the newest drivers


It would be nice to have a mirror or something

I have the old version I can send to someone if they want.

I'm having the same issue as are 5 of my co workers

I'm going to documents my way to make images but I can't without the sound drivers, they fail to download after 40mb or so

I have the old version on my NAS but I want to do my method with the newest drivers

8

(1 replies, posted in Universal Imaging)

Why not just user driver packs only? And add in custom drivers as needed. The driver packs have been really good for me when running off the local disk. They make those 25,000 driver CD that you can also put on a USB those work well.

http://sites.google.com/site/sysprpeallday/driverpacks

I do mine this way BTW

Ok Guys

I thought this would be helpfull

Build your Images with VMware Server 2.0 or 1.9 doesn't matter
Download the Driver Packs and Applications the same as it says in the forums.
Use my scripts. And sysprep files, I deleted my personal info, just add in for yourself
You are more then welcome to use my scripts, this will switch over the hal and sysprep for you
No need to run ROE.exe 937 this does it for you, done via script.
Just run my RUN sysprep Scripts and follow the directions.
Please give it a shot and let me know.

Info Here
http://sites.google.com/site/sysprpeallday/

Files here
http://sites.google.com/site/sysprpeall … prepallday
I hope it's not a problem using my sysprep files and files I use to pervent sysprep errors
I did not put the devcon.exe in the script folder (Due to being a windows file) I don't want to cause any issues let me know if this is a problem.

I use winrar to rar the needed files. Use winrar and let me know how it goes
I didn't put much time into this so let me know if it's helpful.
Quad-Damage

The second script

This is what I run right before I sysprep. This script syspreps my system with a few flags and tools I use. I use this tool to disable the intel ppm, so I can image AMD and intels. There is also a script re enables it called checkforintel.vbs\

This reenabled the intel ppm, if you are not doing AMD's don't worry about it.

http://blog.doylenet.net/?p=91

Has some good info here as well

I have this .bat in my sysprep folder

I also found you can script it to run the roe command before system if you ever forgot. I have done this before. Sysprep and didn't set the driver packs to run lol.

echo Driver Pack Scanner to run after next boot up
C:\Sysprep/ROE.exe 937

@echo off
cd C:\SYSPREP

echo Enabling image for AMD and Intel processors
reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

echo Running sysprep and shutting down.
sysprep.exe -forceshutdown -mini -reseal -quiet -activated

This is just used to sysprep the machine inside of running sysprep and selecting mini setup ect, this does everything for you with 1 click of a bat file.


Anyways for the 2 hal scripts. I'm just showing you 2 different ways to change the hal.
There is the offlinesysprep way (I can't get it working correctly as well)
The method i jacked off the net the 1st code (Works well)
And the lazy way UpdateUPHAL="ACPIAPIC_MP,%WINDIR%\inf\hal.inf
^ this just changes all cpus to muti, but works on uni just says it's a muit. (I have not see anything wrong with the way it works on a uni process, even tho it says it's a muti, they boot up and run fine, it's just the 1/2 assed way of doing things.

You can either do 1 or the other, i wouldn't do both.
-Quad

No? 3937? I always do 937 and it works for me

Just before you run the sysprep (I like the bat file I provided above)

Make sure you have extracted the driver path to the C: (D) folder and make sure you have all the correct devon and driver pack finisher files in the correct location. The 1st page has information on how to do this.

Open command, in Run type cmd
Then type cd ..
cd ..
cd ..
cd ..
untill you are in the root C: drive
Then type CD sysprep
Then in the folder type ROE.exe 937

In Command you are running
C:\sysprep\ROE.exe 937

This calls for the computer to install the driver packs after the next reboot.
I do a mini setup that just promps for a name and then adds the computer to my Active Directory.

Make sure you have a file called ROE.exe in your sysprep folder as well

Post your sysprep

Don't do the inf files, this saved me some problems

Setup everything like the directions say but skip the makepnf.

Before you sysprep in command cd/sysprep/roe.exe 3937
Make sue that file is there

and then run this bat file to start your sysprep. Make sure you are changing your HAL file with either a script. offlinesysprep, or this

@echo off
cd C:\SYSPREP

echo Enabling image for AMD and Intel processors
reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

echo Running sysprep and shutting down.
sysprep.exe -forceshutdown -mini -reseal -quiet -activated

For the Hal this works about %90 of the time

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    OemPnPDriversPath=C:\i386\drivers 
    UpdateInstalledDrivers = Yes
    DriverSigningPolicy=Ignore
    NonDriverSigningPolicy=Ignore
    UpdateUPHAL="ACPIAPIC_MP,%WINDIR%\inf\hal.inf"

This would be added to the sysprep

Build the PC on a Uni Processor and this will switch to a Muti or Uni works well most of the time. I like my bat script better but this works as well.

Here is my CMDlines.txt

[COMMANDS]
"C:/VBSscripts.\hal_Update.bat" 
"C:/sysprep\i386\$oem$\runonce.cmd"

If you look back one page you can use my script to update the hal, has been working great for myself.

Ok here is what I'm trying to do

I want to run my firstboot.bat as soon as windows loads into desktop

Many of my reg files are on the local admin desktop and need to be run after syprep

Anyways

Here is what I have currently

In my C:sysprep\i386\$oem
I have the runonce.cmd
and i have my cmdlines.txt


Here is my runconce.cmd

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
REG ADD %KEY% /V runtwiceex /C "C:\firstboot.cmd"

Here is a nice autologin script if people use local machines that want autologin

 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="Smart Classroom"
"AutoAdminLogon"="1"
"ForceAutoLogon"="1"

This auto logs into a machine called Smart Classroom with no password

Anyone who loves Steady State Here is my bat as well

:: 
::  firstboot.bat
::  

@echo Installing Bomgar Jump 

runas /trustedlevel:unrestricted ""bomgar-RA"

@echo Running Bginfo

runas /trustedlevel:unrestricted ""Bginfo.exe" /accepteula /timer:0

@echo Locking D Drive Documents

runas /trustedlevel:unrestricted ""REGEDIT.EXE /S "Reg_My_Documents_Fixed.reg"

@echo Setup Auto Login

runas /trustedlevel:unrestricted ""REGEDIT.EXE /S "autologon.reg" 

@echo L Key SPSS 18

runas /trustedlevel:unrestricted ""spssactivator.exe" OUR KEY"

@echo Open Steady State and User Must Set Disk Protection to On

runas /trustedlevel:unrestricted "C:\Program Files\Windows SteadyState\SCTUI.exe /enableandreboot"

I have it log into as admin run these scripts, lock the drive with some reg and start up steady state. We use steady state on our smart classroom shared PC's where I work.

Oh I fixed it no worries

Here it is anyways tho

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    OemPnPDriversPath=C:\i386\drivers 
    OemPnPDriversPath=C:\sysprep\i386
    UpdateInstalledDrivers = Yes
    DriverSigningPolicy=Ignore
    NonDriverSigningPolicy=Ignore

[GuiUnattended]
    AdminPassword="XXXXXX"
    EncryptedAdminPassword=NO
    AutoLogon=Yes
    AutoLogonCount=1
    OEMSkipRegional=1
    TimeZone=4
    OemSkipWelcome=1

[UserData]
    ProductKey=XXXXXXXXXXXXXXXXXXXXXX
    FullName="Smart Classroom"
    OrgName="XXX"
    ComputerName=

[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=60

[TapiLocation]
    CountryCode=1
    Dialing=Tone
    AreaCode=510
    LongDistanceAccess="1"

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

[Identification]
    JoinWorkgroup=SmartClassroom

[Networking]
    InstallDefaultComponents=Yes

[GuiRunOnce]
Command8="C:\Documents and Settings\wsadmin\Desktop\firstboot.cmd"

[SysprepMassStorage]
*pnp0a00=c:\windows\inf\machine.inf
*pnp0a01=c:\windows\inf\machine.inf
*pnp0a04=c:\windows\inf\machine.inf
*pnp0a03=c:\windows\inf\machine.inf
pci\cc_0604=c:\windows\inf\machine.inf
pci\cc_0601=c:\windows\inf\machine.inf
pci\cc_0602=c:\windows\inf\machine.inf
pci\cc_0600=c:\windows\inf\machine.inf
pci\cc_0500=c:\windows\inf\machine.inf
root\ftdisk=c:\windows\inf\machine.inf
root\swenum=c:\windows\inf\machine.inf
root\update=c:\windows\inf\machine.inf
root\mssmbios=c:\windows\inf\machine.inf
root\dmio=c:\windows\inf\machine.inf
lptenum\microsoftrawport958a=c:\windows\inf\machine.inf
root\rdpdr=c:\windows\inf\machine.inf
root\rdp_mou=c:\windows\inf\machine.inf
root\rdp_kbd=c:\windows\inf\machine.inf
*pnp0000=c:\windows\inf\machine.inf
*pnp0001=c:\windows\inf\machine.inf
*pnp0003=c:\windows\inf\machine.inf
*pnp0004=c:\windows\inf\machine.inf
*pnp0100=c:\windows\inf\machine.inf

alot more then this

edit = code tags added

Installing ATI2MTAG.SYS
Type in the following paths for the requested files:
ATI2MTAG.SYS -> C:\WINNT\SYSTEM32\DRIVERS
ATI2DVAG.DLL -> C:\WINNT\SYSTEM32

The file is in both locations as well and it's still looking on the D drive when it shouldn't sad

Fixed this stupid sysprep

System Viewer is file Manger system viewer in Bart PE

It's the PE File Mangers
Turbo Nvigator v146
2xExplorer
Servant slamander
ect

I run your program in the Pe file manger, just to set the mass stroge becuase that what I'm having an issue with.

I'm getting the damn atimtag.sys missing file after I deleted the pnf files btw

I have this file already in the driver pack + in my sysprem OEM folder.

Installing ATI2MTAG.SYS
Type in the following paths for the requested files:
ATI2MTAG.SYS -> C:\WINNT\SYSTEM32\DRIVERS
ATI2DVAG.DLL -> C:\WINNT\SYSTEM32

The file is in both locations as well and it's still looking on the D drive when it shouldn't sad

@Galapo

Is there any way to host you program and run the whole thing in windows? By copying the  under windows and run the same program in a PE with a system viewer program. (It could run it from PE but the files would be hosted locally and ran locally just in a PE viewer) I have been doing this to make changes to the OS, If i forget after I have ran ROE.exe 937; due to not wanting the drivers packet program to run. I think that was my error before this was not desisnged to work that way and needs to be ran from within a PE or LiveXP. I couldn't get it to load with my Bartpe (I know it's old school but it works well for me)

I will give liveXp another go with your offline sysprep program.

I really just want to use your program to inject mass storage devices, the -bmsd is not cutting it for me.

@Galapo

Well

I didn't do the Make PNF + this method with the ROE.937

When I run offline in my bartpe I get
It goes all the way past your hal, then I get
RunScanner Error

Create of raget process failed, ret=2
The system cannot find the file Specified

Yes, I'm going to have it install just network drivers and create a script to map into my Nas Share and run the driver off our network shares. This will save me 2 GB from my default image.

2GB Images in the near future smile Hopefully

The machine was built on a ACPI and it will switch over

I'm going to give your offline sysprep another. Thanks to Overflow help

I have my Vmware snapshot.

I deleted my old pnf files in the ini folder. I will not do the makepnf

I copied over your offline files, moved the devcon and put the driver pack mass storage on the C drive not the D/M directory.

Do the ROE.exe 937 command
I will boot in BARTPE run the massstorage injector and the fixes your program has.
Then Sysprep and and Ghost the Sysprep image, hopefully will work with my 60 model computers

Will give an update on how it goes

Any updates on this?