IcemanND

I set my install to give the machine a randomly generated name and then run a script at first login (I also set the machine to autologin twice) to get the ip address and and nslookup on the address to get the registered computer name and then change the computer name. We don't care what the workgroup name is so I set all of them to the same thing. If the workgroup it is supposed to be in is returned by nslookup you could parse it out and assign it there otherwise you will have to have a way to associate a machine name to a workgroup. Hope this helps.

put cmdow in the $oem$ folder add: cmdow @ /hid to the beginning of each cmd file I have all of my cmd files in the $oem$ also not sur eif it makes a difference or not. but everything I run, runs from cmdlines.txt. Only the updates run from svcpack.inf.

It can be even easier than that. If you are using the same processor and therefore the same HAL then the problem you have run up against is an unknown HDD controller. find the drivers for the HDD controller on the new motherboard and when booted on the old machine right click on the inf for the HDD controller and select install. Shutdown the system and move it. This has worked for me on all but a handfull of machines I have attempted this with. If you are using a different processor on the new motherboard then you also need to verify what HAL the old board had and what HAL the new board should have. Chances are it should not be a problem.

try running all of the scans from safe mode. In machines that have or are severly infected many times you will have better luck cleaning them when in safe mode where alot of the spy/malware does not load.

With the suggestions and testing help of Stealth111, I have been working on a new version of Keydecoder. The current version I am working on has the following features for looking up Microsoft license numbers: All of the options are available via either gui or command line and the results can be save to a csv file. I can't think of any other possible ways that one would want to try and access this information. But if anyone has any other suggestions let me know and I will look into added additional features. At this time I have no intentions of providing any method to change the license numbers of any of the products.

if you are trying to get it from a machine loaded with XP there are several products which can extract the key from the registry and decode it, one is here at msfn called keydecoder

I use the advanced install of Office and was refering to the tranforms file (xxxxxx.mst) see bottom of: http://unattended.msfn.org/unattended.xp/view/web/45/ Otherwise try looking in the MSI with ORCA or other MSI editor and search for your key to see if it is there and delete the value.

try this. I make no guarentees. Edit the answer file that is created with notepad and search for the key you entered. It is stored in clear text. Then either delete it or replace it with an invalid key. The install should then ask for a key. Or if you are doing the installs to the machines then change the key in the registry and when it sees that it is invalid at the first launch of an office app it asks for the correct key.

by the time runonce has run the drivers have been installed. So I would have to either manually remove the sound drivers and reinstall, or figure out a way to have it automatically remove and reinstall the sound drivers. I've never been successful at refreshing the drivers after install kb888111. I have a feeling I'm just gonna have to bite the bullet and resysprep the machine.

It does when you have added about 100 mass storage drivers along with the defaults.

I don't know of anyway to run anything yourself before cmdlines.txt and by then it is too late.

not when sysprep installs the drivers with minisetup. the hotfix needs to already be installed.

I have an image I am creating which sysprep just finished running on and I just realized I forgot to install kb888111 for High Definition Audio Devices. Anyone know of a way I can install it to an offline OS, so that I don't have to ressyprep the system just to install this one patch.

create both of your panes first. then under window select freeze panes and both panes will be frozen. don't try and do them ine at a time.

@ vaternl - I believe it's fixed. try new version .79 and let me know.

will it start in safe mode? then run spyware/virusscan if it will. Or create a BartPE cd on another machine and do the same.

only booting to something other than the windows installation first. I use Windows PE to script the partition creation and then run the installation from PE.

First of all Fdisk only creates and deletes partitions, it doesn't format them. If you are after multiple partitions then you will need to boot from other media and usee fdisk, or if you boot from a Windows PE cd then you can create the partitions with diskpart and format then format them NTFS with the format command. If you just want 1 partition the full size of the drive and don't care about what is on the drive then set [Data] AutoPartition=1 [unattended] Repartition=Yes

boot to the command console or from a BartPE cd etc and check your boot.ini file, sounds like it's either corrupted, missing or has the wrong path to your windows installation.

From what I see it looks like it's not office that it is looking for but another application which has a plugin of some kind in word, like adobe has for some of it's products. If you cancel it and get into word try disabling any addons for word that are not part of office.

no no pictures, just memories. Took 4 raisins and a magnet out of a G3 All-in-one CD my first week on the job. The multiple cd's brought back memories, 4 is the max i ever saw. Took six floppy shutters out of the same drive once. Worked on six laptops used as urinals. Took three credit card sized cd's out of slot loading cd drives where the cd's themselves said do not put in slot loading drives. and oh so many more.

LMAO - I wish I had thought do do this during my 8 years in the service department at a university.

make sure you have OemPreinstall=Yes under [unattended] in your winnt.sif file which is in i386. And your $oem$ folder is in the same directory as the i386 folder. Even after a making a number of unattended dvds over the last 3 years I just today forgot oempreinstall=yes

what _JD_ see's is what I have experienced. when starting with a UP HAL and going to the MP HAL it is installed automatically at the first full boot.

v78 beta released @madboy - I more programming experience than I admit to anyone. It's not something I do on a regular basis. I do it when I find something I need/want to do but can't find anything else that does the job I want. But I've been programming for more than 20 years in 8 languages. This is actually a small part of a much larger program I am working on.