tguy

You will have to get some kind of some kind of remote control software for the Windows 2000 PC like UltraVNC and connect to the PC that way to set policies and monitor. Or you could implement Active Directory and do it that way but as you are probably aware, you will need a Win2K or Win2K3 domain controller server. Local security policies are just that, they are local to the PC you are working on. You cannot control security policies for another PC in a Workgroup configuration. As for monitoring, you can use scripts, monitoring utilities, and remote control software to accomplish that. Good luck.

Sounds like what you are wanting to try, might work but it is risky. If you haven't already done so, check out this article from MS. http://www.microsoft.com/resources/documen...bj_brr_VCGI.asp

Sure, you can use the diskpart.exe utility from MS. Create a text based batch file and paste these lines into the file: select volume 0 assign letter Z Save the file as something like diskpart.txt. Then create a batch file to call diskpart.exe with the following parameters: cmdow @ /HID @echo off REM ***Change CD-ROM drive letter to Z:*** %SYSTEMROOT%\SYSTEM32\DISKPART.EXE /s %SYSTEMROOT%\SYSTEM32\diskpart.txt

Try saving the document as a plain ASCII text document first. That should strip out the formatting. Next open the text document in Word, then apply then 8 pt. font to the document. CTRL + A to select the text, then from the Toolbar, select the font. Save the document as a new version of the original and you should be set.

Just a quick suggestion to andrewpayne's post. Step 2.5 Use the ntbackup.exe utility to run a quick system state backup of the server you are installing to first. Will help you recover if the uninstall of the SP does not work completely.

You could also try putting your WINNT.SIF file on a floppy and have it read from the A: drive at the very beginning of the installation. Make sure it is in the drive before the DOS mode screen reads press F2 or F6 at the bottom. MS actually recommends this method be used. While you can normally copy the WINNT.SIF into your i386 directory, putting it on a floppy provides greater flexibility in editing the file to add or remove components, change the computer name etc.

Is your M: drive a remapped drive from an application like Citrix or is it a secondary drive? Do you have Windows 2000 or XP loaded on the PC already so you can make use of the Disk Management feature? Please expand on your initial post to help us understand these things.

Trying updating the BIOS to the latest version. Some mainboard and BIOS chips require updates before XP will run on them. By any chance was the hard drive you replaced a SATA drive? If so, XP may not have driver support included for that drive natively. In which case you can go to the Device Drivers forum and get help integrating the driver. Good luck.

I think this might be what you are looking for: Microsoft has included three settings that can be modified in the WINNT.SIF file. These options are NOT generated by the Setupmgr.exe utility so they will have to be added manually. The settings, located in the [unattended] section of the WINNT.SIF file are: A) ExtendOemPartition=0 or 1 (0 means do not extend partition to full size of hard disk, 1 means utilize full size of hard disk.) NOTE: Only NTFS partitions can be extended. You can automatically format the partition NTFS if need be by utilizing the FileSystem=ConvertNTFS parameter also inserted into the [unattended] section. B) Repartition=Yes or No (YES means first drive is deleted and reformatted NTFS, NO means it is left as-is.) NOTE: This option can only be used when booting server from a Windows Server 2003 CD, and it will not affect HP/COMPAQ system partitions. C) AutoPartition=0 or 1 (0 means do not automatically partition drive, 1 means automatically partition drive. D) Here is an example of items A,B & C: [Data] AutoPartition= 0 or 1 [unattended] Repartition=Yes or No ExtendOemPartition=0 or 1 Good luck.

You should be able to just delete the ProductKey or ProductID line from your unattend file. I have seen in the past where if I have the wrong product key entered or no product key that I am prompted for it during setup. Play around with this setting and see what works for you.

Running these hotfixes through a batch file will work fine except you need to download qchain.exe and run it after the last hotfix is installed. This will allow you to install the updates with a single reboot and insure that the appropriate registry entries and system updates are registered.

You could add a rule to your firewall or IDS system that basically drops all packet traffic from the offending IP's to your network. Since it could be a worm trying to attack your network, perimeter antivirus scanning of some sort might be in order as well.

I don't know if there is a registry key tweak to turn macros on or off but you could explore Office .ADM template files or Group Policies to restrict macro creation and/or execution.

I had a problem similar to this that I resolved by reinstalling IE6 SP1.

@komar77r To expand on The-VOICE's comments: netsh interface set interface name="Local Area Connection" newname= "Prod" can be used at the command line. I run mine from a batch file called by the Runonceex.cmd file.

Try this: Section II – Modifying the i386 directory & TXTSETUP.SIF file This section will explain one method for adding driver support for newer drive controllers to overcome this issue. Here is what you need to do: A) Identify the appropriate driver files for the controller you are working with ie: Compaq Smart Array 5i (as will be discussed in this example) B) The driver files can typically be obtained from the manufacturer’s website. Once obtained, expand/copy the files to a temporary directory, ie: C:\Temp. C) Most driver file sets will consist of at least three files. For instance with the Smart Array 5i controller the files are: a. CPQCISSM.CAT b. CPQCISSM.INF c. CPQCISSM.SYS D) Copy the .SYS driver file into the root of the i386 directory where your source files are located. E) Next, in the i386 directory, locate a file called TXTSETUP.SIF and open with Notepad or another text editor. F) You will need to add the following entries for your driver to each of the four sections shown below: 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 Server 2003. 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 Server 2003 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" 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 d. [sCSI] cpqcissm = "Compaq Smart Array 53xx-series Controller" ADDING DRIVERS TO THE BUILD: In addition to the RAID disk drivers discussed above you may find it necessary to add additional LAN, VIDEO, MODEM or other OEM drivers to the .ISO image for compatibility with newer servers. To accomplish this task: 1) Download the appropriate drivers from the manufacturer and expand to temp directory. 2) Open the $OEM$\$1\PnPdrvrs directory where the source files are located. 3) If the files you wish to update are Array, or LAN drivers simply copy the driver files from the temp directory into the existing directory. Be sure to repeat this process for each $OEM$ directory corresponding to the version of Windows server. For instance you will need to copy the files to the Enterprise Edition $OEM$ directory as well as the Standard and Web Editions $OEM$ directories. 4) If the driver files are for another piece of hardware for which there is not a current directory you will need to create one. The naming convention starts out with a series of numbers 000, 001 etc. This corresponds directly to the order in which the drivers are installed. Create the directory following the established convention noted in the path from Step 2. 5) Lastly, you will need to add the new directory to the OEMPnPDriversPath line in the [unattended] section of the WINNT.SIF

There are tons of tweaks for Win 2K, check out Prathapml's thread for Registry tweaks. What you apply really depends on what you are hoping to accomplish. Cosmetic changes Preference settings Performance enhancements for network, browsing and other services Security You could also look to: Winguides.com

There are a number of things that could be causing your network latency. You could try these things to improve the speed. 1) Hard code the flow control/port speed of your NICS in the Advanced Properties. 2) In My Network Places, right click and choose Properties. Click the Advanced menu then choose Advanced Settings. Make sure your primary NIC is at the top of the connections list. 3) Also in properties, right click your NIC and choose Properties, then TCP/IP. On the WINS tab, you could try changing Enabling Netbios over TCP/IP as opposed to getting the settings from a DHCP server. 4) Try replacing the network patch cable. 5) Update the NIC drivers on the pc's and server. Hope one of these work for you.

Try changing the cmdlines.txt to read: [Commands] .\users.bat Helps to qualify the path to the batch file.

For some reason, 1024 characters seems to come to mind as the max. limit for a message box. Check the documentation but I remember reading it somewhere.

@kurt476 Go back to the link http://una.ua and click on the English link in the lower left hand corner of the page, it will take you to the English version of the website.

You can do RAID configurations with the diskpart.exe utility. Why would you want to install XP Pro on a RAID 5 array? Is there something specific you are trying to accomplish? RAID 0 or RAID 1 would seem to make more sense for performance reasons.

As for the username, firewall, IE setup issue: For username check into the oobeinfo.ini Your firewall settings look fine And for IE, try removing the proxy settings if you are not using a proxy server. You may want to consider creating your own custom install of IE with the IEAK to configure it the way you want it. Then launch ie6setup.exe from cmdlines.txt or something. Good luck.

The problem probably stems from the upgrade and your profile possibly changing. If you have not already done so, try logging in with your old profile to see if that works. Not sure why an Office 2000 installation would be looking for an OfficeXP with Frontpage CD but there may be some components like Frontpage Server Extensions that got installed when you installed IIS that require the .cab files. In any event, I would see if Mom and Dad can send you a copy of the Office CD as there may be no other way to get around the problem without updating or reinstalling Office.

You could get a copy of Adobe Acrobat, the full version, that will unlock the .PDF file for you and manipulate it from there. It is not free though.