tguy

You might also need: XoftSpy HiJackThis Anti-Virus scanner

On some of the new HP servers with iLO cards and firmware version 1.62 or > you can mount an .ISO from the local PC or server and boot the HP server with it. I have done this to build servers with in the past. I would imagine it would work with a KNOPPIX .iso as well. Not sure if other servers or desktop PC's would allow for this though.

Are any of the clients running XP SP2 or another software firewall package? If so, disable the firewall(s) on the individual clients as your router will act as a firewall of sorts for you. Make sure they are all on the same network and subnet and you should be able to communicate with them without a problem.

Have you tried using the Alternate Configuration under the IP settings to set your IP address statically? Try that as a possibility. Good luck.

Have you considered adding their network id (domain or AD account) to the local administrator's group? Try that.

Try removing the *.* from d:\software on this line: xcopy %cdrom%\software\*.* d:\software\*.* /e

As for the logon problem, try changing: EncryptedAdminPassword=No I could not get mine to work until I did this.

@S0mEOneMinds1 - This forum was not setup for you to flame other members. Remember everyone has different levels of technical expertise and experience. While huneyman's question may have been located in the wrong section of the forum, it is still legitimate. Remember the Golden Rule - Do unto others as you would them to do to you, treat others how you would like to be treated.

DVDXCopy works well too.

You could try selecting 'Run in separate memory space' as well.

Try using DHTML. DHTML MenuBuilder is an excellent tool for what you are trying to accomplish.

Try not to double post as it will be harder to get an answer with multiple threads. Forum rules discourage this practice as well. See the reply I gave you in the other section.

Try changing EncryptedAdminPassword=No I could not get it to work until I did this.

See this MS Article. May not be a good idea to turn off Language Bar. http://support.microsoft.com/?kbid=819783 As for search interface, check out this article. http://www.petri.co.il/restore_classic_sea..._windows_xp.htm Good luck.

Check to make sure that the file is listed in the [sourceFiles] section of the txtsetup.sif.

Have you looked at the Guide to Unattended Setup from MS? There is lots of good info. in there on Regional settings. Another good source is the ref.chm from XP or Server 2003 deployment tools. Check them out.

Sure just create a batch file that maps a drive to the network share where Office 2K is located and launch setup from there. Call the batch file using the Runonceex.cmd to put the entry into the Registry to be used the first time the server PC starts up in GUI mode. Search The Unattended XPCD site for how-to's with Runonceex.cmd Good luck.

The problem with installing printers is that it affects parts of the registry and the services (spooler etc.) You need to be an administrator to gain rights to modify these settings. You could try and use RunAs to install the printer but you may have some difficulty trying to script it with nLite.

Did any of the updates you downloaded and I assume installed, update your NIC drivers? Try uninstalling, and deleting the NIC driver files, then install the new drivers from the manufacturer.

You can find information on the DriverSigningPolicy on the MS MSDN site. Also in the unattend.doc or ref.chm help files. Did you try disabling the System File Checker?

lotsill, Looks like you need to OemPNPDriversPath line to: OemPnPDriversPath=Drivers\SCSI (remove the first set of quotes and the last back slash) You can probably get away with removing the OemFilesPath line. You will need to relocate the SCSI drivers to: $OEM$\$1\Drivers\SCSI OR Change the OemPnPDriversPath=SCSI You can follow my instructions for modifying your TXTSETUP.SIF as outlined below. Be sure to copy the ADPU160M.SYS file into the root of the i386 folder. NOTE: Some of the instructions are copied from other postings on this forum. Gotta give credit where credit is do. Here is what I did to integrate my SCSI drivers. TXTSETUP.SIF: a. [sourceDisksFiles] cpqcissm.sys = 1,,,,,,6_,4,1,,,1,4 (Note: the first 4 listed indicates the file is to be copied to the ..\SYSTEM32\DRIVERS directory at the destination location) To identify the exact parameters to list after the = sign, first check a Windows Server 2003 CD to see if driver support for your controller is listed. Then copy the parameters from the TXTSETUP.SIF file on the Server 2003 CD to the TXTSETUP.SIF file for Windows 2000. If the driver is not listed, find a similar driver and mirror those parameters. The [sourceDisksFiles] section lists all files for the installation. This section is critical for customization because it controls which files are copied during the installation. Using a text editor (such as Notepad), you can search for the [sourceDisksFiles] section to obtain a list of all Windows 2000 installation files. These settings can be difficult to figure out. Below is a graphic example that helps to explain what this numeric string does. The following line shows the syntax of each line in the [sourceDisksFiles] section: filename_on_source=diskid,subdir,upgradecode,newinstallcode,spare,spare,newfilename Extra fields specified by commas (,) are Windows NT—specific. diskid is used when a floppy disk installation is used. (Or multiple CDs?) subdir is the directory to which files are copied. Codes defined in the [WinntDirectories] section of the TXTSETUP.SIF file are used to identify the destination directory. upgradecode is a single digit that is used if this is an upgrade from an earlier version. It specifies whether the file is copied during the text-mode portion. Codes in the [Files] Section of TXTSETUP.SIF for File Copy Status Code - Copy Action 0 - Always copies the file 1 - Copies the file only if it exists in the installation directory 2 - Does not copy the file if it exists in the installation directory 3 - Does not copy the file newinstallcode is a single digit that is used if this is a fresh installation. It specifies whether the file is copied during the text-mode portion. The same codes are used as for upgrading Windows 2000 and are described in Table 4.3. The newinstallcode is optional; if it is not included, the file is not copied (code = 3). newfilename is the name to which the file is renamed if it is copied. As an example, consider this line from the [sourceDisksFiles] section. NOTE: In the above diagram, if the driver file you copy to the i386 directory is not compressed, you will need to replace the 3_ or 4_ with a _x. This tells the installation that the file is not compressed and to go ahead and copy it anyway without attempting expansion. b. [HardwareIdsDatabase] PCI\VEN_0E11&DEV_B060 = "cpqcissm" PCI\VEN_0E11&DEV_B178&SUBSYS_40820E11 = "cpqcissm" PCI\VEN_0E11&DEV_B178&SUBSYS_40830E11 = "cpqcissm" PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11 = "cpqcissm" NOTE: Again, if available mirror settings from TXTSETUP.SIF file on Server 2003 CD These hardware ID strings are typically found in the .inf files that accompany the actual drivers in the download package. Copy each string relative the driver you are installing to the TXTSETUP.SIF file in this section. c. [sCSI.load] cpqcissm = cpqcissm.sys,4 NOTE: Again, if available mirror settings from TXTSETUP.SIF file on Server 2003 CD d. [sCSI] cpqcissm = "Compaq Smart Array 53xx-series Controller" NOTE: Again, if available mirror settings from TXTSETUP.SIF file on Server 2003 CD WINNT.SIF: [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINNT NoWaitAfterGUIMode=1 FileSystem-ConvertNTFS Repartition=No ExtendOemPartition=1 DriverSigningPolicy=Ignore OemPnPDriversPath=PnPdrvrs\000_cpq_arry;PnPdrvrs\001_cpq_LAN;PnPdrvrs\002_cpq_PSP WaitForReboot="No" Good luck. tguy

If the record still persists in DNS you could use the DNSCMD.EXE utility from the resource kit to flush it. DNSCMD /RECORDDELETE....

Sounds like you are using DHCP. Try setting your DHCP server to expire the lease after 8 hours. That may help to get rid of the problem. If you are using WINS you can tombstone the old record and delete it. Restart WINS and it should pick up the new information.

There is a known bug in WIN 98 for this problem. See MS Support site for the KB article on what to do. If you are running 98 SE then try this. http://www.microsoft.com/windows98/downloa...8SE/Default.asp

VBScript will create a shortcut for you from the command line. All you have to do is execute the script. Here is an example of how to create a shortcut for Windows Explorer on the Desktop. 'Create Windows Explorer Desktop icon Set Shell = CreateObject("WScript.Shell") DesktopPath = Shell.SpecialFolders("AllUsersDesktop") Set link = Shell.CreateShortcut(DesktopPath & "\Explorer.lnk") link.Arguments = "/n,/e,c:\" link.Description = "Explorer link" link.HotKey = "CTRL+ALT+SHIFT+E" link.IconLocation = "%SystemRoot%\explorer.exe" link.TargetPath = "%SystemRoot%\explorer.exe" link.WindowStyle = 1 link.WorkingDirectory = "%HOMEDRIVE%%HOMEPATH%" link.Save tguy