IcemanND

The problem you may run into is if you have a piece of software that uses the system pre-sysprepped SID and stores it in the registry or an INI file somewhere. Sysprep will not reset the stored SID when run and you will end up with duplicate SIDs with that application, SMS, SCCM, McAfee ePO, and TripWire are some that I know do this and I make sure to install after dropping an image.

It depends upon what you are doing from WinPE whether you need the language add-on or not. If all you are doing is Ghost then you probably don't need any of the additional packs added. I use my WinPE thumbdrives for image deployment, system recovery, data recovery, malware removal and more so I add all of them except the WinPE-SRT to my boot image.

There is no one cure all tutorial for this issue. It is different for every different type of installation method, MSI, InstallShield, Adobe, etc. So it will depend upon what software you want to deploy. Best result google "app title" silent install and you will likely find your answer in the first 5 results. Most of them I have looked for I find at appdeploy.com

if you re seeing the add new wizard message then windows is not finding the drivers added to the machine in the inf path. Copy the drivers to the machine and edit the infpath setting in HKLM\software\microsoft\currentversion to include the additional paths to the added INFs.

Best method is to capture an image before sys prepping. Or develop your images in a VM and take a snap shot first. Then you cam restore to the image or snapshot and continue. You are limited to 3 re-arms and syspreps.

if you don't have a restore point that fixes your profile you can do the following. Log in as a different user with admin rights after a reboot, do not log in as the user that is having the problem. Make a copy of the profile directory. Delete the original directory. Login as the user that had a problem, you will get a newly created profile. Copy the bad profile into the good profile, some files will be in use just skip those. You should have most of your profile and settings back except those stored in the registry.

Belkin router or belkin wireless adapter? Some wireless assorted will have driver updates which will include wpa2.

You will need some way to identify the partition you wish to have the permanent letter for. If you always have the same partition scheme you could run a script on first boot using disk part to select the partition and assign it a new letter.

What network adapter? And what driver version was installed?

each manufacturers software is different. you can look at the unattended windows guide there are some there http://www.msfn.org/board/links/goto/27-unattended-windows-guide/ or appdeploy.com, the other option is to search the manufacturers support site for more information.

Welcome to the forums

If the machines are joined to a domain add a domain user or group to the local administrators group will solve the problem also.

If you don't need the HTA GUI Trip pointed you to you can check out the guides I wrote on creating Win PE 2 & 3 images. http://www.msfn.org/board/index.php?showtopic=144914&view=findpost&p=929349 and http://www.msfn.org/board/index.php?showtopic=101383&view=findpost&p=674778 You just need to add the Ghost32.exe and any of the other 32-bit version of the Ghost tools you may want to the boot.wim and edit startnet.cmd to launch ghost32.exe with you desired switches.

USMT will only do his profile. Sounds like he wants to move everything, OS and programs included. This is a bit more problematic. The two biggest headaches of this are differing hard disk controllers, you exist one is likely IDE and the new machine is going to be SATA, the other issue will be the Hardware Abstraction Layer (HAL) depending upon the processor in your machine you could have one of 7 though really likely one of 5, compatibilty between HALs is limited. Both issues can be worked around, thee are commercial packages that can generalize your system so that it can be transferred or if you are the hands on technical type you can look for universal image creation information and do it yourself. You need to preinstall the SATA controller and change the HAL to one that is compatible with both systems. Personally I would move my data, reinstall my applications and be done with it.

Now that's interesting. I thought I had the same search logic in both versions. The error message is due to it not finding one of the files for a driver, unfortunately I don't have this issue with any of my machines so it is hard to troubleshoot which file causes this issue, or which place in the logic. Normally if you back up the drivers 1 or two at a time it will work until you hit the driver causing the problem. If you don't have mscomctl.ocx it won't even launch.

I did something similar with scanning the neighborhood and set my channel to one not used in my area. Didn't kill any of the rates a/b/g since I have devices that use all of them, but changing the channel made a big difference, since doing that and replacing my wireless phones that were 3.2ghz phones I have not been disconnected from wireless.

I would go for something else in your house interfering with your wireless connection. If it was just one machine I would have gone with drivers or hardware. So assuming it is interference any cordless phones in the house? Router is sitting on top of or near the microwave or other electrically noisy device (i.e. fridge, fan, air conditioner)? Other wireless networks in the neighborhood with strong signal at your house possibly using the same channel, even with a different SSID?

have you look through the list of available switch options for slmgr.vbs?

What are you using to create your install package?

You said they are all public variables but are they declared outside the subroutines or are they global to the entire script having been declared outside any sub? Can you post the code for us to look at?

@echo off for /f "skip=1" %%A in ('dir /b *.msu') do ( echo Installing Update "%%A" ... start "" /wait WUSA %%A /quiet /norestart > nul ) echo. echo ########################################################### echo. echo Updates are installed echo Press any key to reboot pause >NUL shutdown -r -t 0 Try this, changed the start command line.

open a cmd prompt manually and type the command in after changing to the directory the MSU files are in, what happens then?

for /f %i in ('dir /a /b *.msu') do wusa.exe "%i" /quiet pause Now the windw will stay open until you press a key so you can see any errors.

Sorry, my bad. for /f %i in ('dir /a /b *.msu') do wusa.exe "%i" /quiet If you run just the dir /a /b *.msu you should see a listing of the files, if run from another directory it should include the path in the name, but no other details will be with the file like time stamp etc.

Sorry, forgot to add that. Save as CMD file in the directory with the patches. If you need to put it somewhere else adjust the dir cmd inside the single quotes. You can run the dir cmd by itself and see the order that they will install in and that they are found. I haven't needed to use pkgmgr but you should be able to do something similar. You can check technet for the switches associated with pkgmgr. Package manager command line options