IcemanND

the Ghost boot wizard gives you and option to create a cd iso to use for imaging, cpaturing, deploying, multicasting, etc. You can also create a Windows PE 2 cd and add the Ghost32 executable to it and ghost from a 32 bit environment. Not sure what you are using multiboot for.

Some systems have drives that when they install require a certain HAL, then TPM driver in Lenovo laptops for example will not install if the HAL is standard ACPI and mini setup will stall. You can switch between uni and multi processor HALs using sysprep, to go back to standard ACPI you need to script something to cahnge the HAL. If you start with ACPI standard then you need to script something to cahnge it to uni or multiporcessor. There are many topis here regarding this search for "universal image" or "hardware independent image"

Try giving power users full control of HKLM\software\adobe and its sub-keys.

There is a registry key that the account needs full access to for many Adobe products. I don't have the details with me right now but will post them tomorrow when I get to work.

Posts unrelated to exist topic of imaging software and related to freezeing the system state have been move to a new topic here: http://www.msfn.org/board/index.php?showtopic=107268

@molecule - doesn't make images but sound like you want deepfreeze.

Not sure whta happened there. It didn't look like that on my view after the edit. Fixed. Thanks.

Used to be a good site. apparently it is no more.

depending upon the application it is not likely going to happen. You can sometimes get past the file and folder permissions but if it has to write to protected portions of the registry you'll be out of luck without admin rights.

No only the administrator account will be affected.

I have never tried creating the image using an nLited install. The last time I did I had further problems post sysprep, those problems may have been resolved but I have just never tried it again.

bit for bit no, but an image that contains everything needed for a windows installation yes. bit for bit is a little extreme, thiat is normally reserved for forensics. Windows Imaging is a file based imaging method and allows you to mount the image as a folder on your machine for editing. It is what is used for Vista, and can be used for XP. I have a guide available here: http://www.msfn.org/board/index.php?showto...st&p=674778

if you are using sysprep the recommended way is to use the massstorage section of the sysprep.inf to add boot up mass stroage controllers.

Last I checked ghost will not capture a drive which is currently in use by an OS. It could be used as a starting piint and then use ntbackup to backup and restire changes after the initial ghost image.

You can do it with out the \ at the end of the %key% value but then you need to add a \ between %key% and the number in each of the REG ADD lines as it is shown in the unattended guide. it is a matter of looks and preference. SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%05 /VE /D "Shockwave" /f REG ADD %KEY%05 /V 1 /D "%systemdrive%\Install\shockwave\swinstaller.exe" /f or SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%\05 /VE /D "Shockwave" /f REG ADD %KEY%\05 /V 1 /D "%systemdrive%\Install\shockwave\swinstaller.exe" /f

Good catch jbm. in your runonceex.cmd SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx Should be SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\

try removing: cmdow @ /HID @echo off from runonceex.cmd and add a pause command to the end and see if any errors come up when it is running. You can also press Shift-f12 after this should have run to open a CMD window and the launch regedit and check to see if anything has been added to the registry.

do your cleanup.cmd and useraccounts.cmd commands run?

No, as far as I know only the massstorage drives will cause any issues. The other drivers are not used until mini-setup after deployment.

don't need to buy anything you can use Windows imaging for free. Along with some of the other software on the list.

I haven't used the current massstorage driver packs but I have in the past, the last time was probably about 6 months ago. When I did I found a handful of the drivers were not properly arranged so they wouldn't add correctly. Did you add the massstorage pack to your installation media or are you using it only at sysprep?

what application are you trying to use with RunAs?

if your drives are only lasting a year, buy one with a 3-5 year warranty. You get what you pay for.

Have you tried the universal driver that is used by the boot disk wizard in GSS 2.o? I have not found a card that it doesn't work with yet.

You will have to setup accounts on the file server with local accounts that have the appropriate permissions to the folders and give that account information to the desired users.