Sunday, March 15, 2009

How to Quickly Analyze your Windows Server 2008 Performance Monitor Logs

How to Quickly Analyze your Windows Server 2008 Performance Monitor Logs
 

Ever have a performance problem, but don't know what performance counters to collect or how to analyze them? The PAL (Performance Analysis of Logs) tool is a new and powerful tool that reads in a performance monitor counter log (any known format) and analyzes it using complex, but known thresholds (that are provided). The tool comes out-of-the-box with some predefined thresholds defined as high according to the Microsoft consulting/development but those can be adjusted to whatever you like.

The tool generates an HTML based report which graphically charts important performance counters and throws alerts when thresholds are exceeded. The thresholds are originally based on thresholds defined by the Microsoft product teams and members of Microsoft support, but continue to be expanded by this ongoing project. This tool is not a replacement of traditional performance analysis, but it automates the analysis of performance counter logs enough to save you time.

Features

  • Thresholds files for most of the major Microsoft products such as IIS, MOSS, SQL Server, BizTalk, Exchange, and Active Directory.
  • An easy to use GUI interface which makes creating batch files for the PAL.vbs script.
  • A GUI editor for creating or editing your own threshold files.
  • Creates an HTML based report for ease of copy/pasting into other applications.
  • Analyzes performance counter logs for thresholds using thresholds that change their criteria based on the computer's role or hardware specs.

Usage

The PAL tool is primarily a VBScript that requires arguments/parameters passed to it in order to properly analyze performance monitor logs. In v1.1 and later of PAL, a GUI interface has been added to help with this process.

In order to use PAL you need to install the tool (see download links below), and 2 additional tools from Microsoft – Log Parser 2.2 and Microsoft Office Web Components 2003. Note that you need this download EVEN IF YOU'RE USING Office 2007!

After installing, you run PAL from the Start menu and begin your analysis. Needless to say you will need to first capture some logs in order to "feed" them to PAL…

In order to capture the right counters from your server you can either use the counters you are knowledgeable of, or, in case you forgot which counters you should use, open PAL, select the correct pre-configured threshold file, and click on Edit. You'll see a list of pre-defined counters, which you can also manually edit if you wish to.

Now open Performance Monitor on the required server and navigate to Performance Logs and Alerts > Counter Logs.

Right-click Counter Logs and select New Log Settings. Give the new log a descriptive name, and then begin to add counters and objects as required. These counters will be captured on the server and used by PAL to analyze the system's performance.

You also need to define the interval for the capture (do not use a 1 second interval unless you really have to, as it will have a negative performance effect on the server).

When done, start the new log.

As stated above, PAL comes with a set of some threshold templates for AD, System Overview, IIS, SQL, Exchange and so on. You point the app at the performance log you've captured, choose a threshold template that best suits your needs, answer some questions, add the form and execute.

Back in PAL, choose the right threshold file and answer the file's specific questions on the bottom part of the window.

In step 3, select the right analysis interval. I used AUTO.

In step 4, click on the Add Form Settings to Batch File button. Now click Execute.

Once it completes it generates a webpage with the analysis information you desire. The webpage shows you alerts for activity that it finds suspect and graphs for the different areas of interest.

Looking at my results I can clearly see that my server is having some performance issues.

BTW, this capture was performed on a VM running with very modest hardware settings, so no wonder the results were so poor…

Requirements

Operating Systems - PAL runs successfully on all of the following operating systems: Windows XP SP2, Windows Vista, and Windows 2003 Server. Also, PAL is 32-bit only due to the OWC11 requirements.

Downloads

Use the following links to get PAL and the required additional files:

PAL v1.2 (current as of February 2008)Performance Analysis of Logs (PAL) Tool http://www.codeplex.com/PAL/Release/ProjectReleases.aspx?ReleaseId=10274

Log Parser 2.2

Log parser is a powerful, versatile tool that provides universal query access to text-based data such as log files, XML files and CSV files, as well as key data sources on the Windows® operating system such as the Event Log, the Registry, the file system, and Active Directory. PAL uses the Log Parser tool to query perform logs and to create charts and graphs for the PAL report.http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&DisplayLang=en

Microsoft Office Web Components 2003Log Parser requires the Office Web Components 2003 in order to create charts. You need this download EVEN IF YOU'RE USING Office 2007!http://www.microsoft.com/downloads/details.aspx?FamilyID=7287252c-402e-4f72-97a5-e0fd290d4b76

How to Quickly Analyze your Windows Server 2008 Performance Monitor Logs

How to Quickly Analyze your Windows Server 2008 Performance Monitor Logs
 

Ever have a performance problem, but don't know what performance counters to collect or how to analyze them? The PAL (Performance Analysis of Logs) tool is a new and powerful tool that reads in a performance monitor counter log (any known format) and analyzes it using complex, but known thresholds (that are provided). The tool comes out-of-the-box with some predefined thresholds defined as high according to the Microsoft consulting/development but those can be adjusted to whatever you like.

The tool generates an HTML based report which graphically charts important performance counters and throws alerts when thresholds are exceeded. The thresholds are originally based on thresholds defined by the Microsoft product teams and members of Microsoft support, but continue to be expanded by this ongoing project. This tool is not a replacement of traditional performance analysis, but it automates the analysis of performance counter logs enough to save you time.

Features

  • Thresholds files for most of the major Microsoft products such as IIS, MOSS, SQL Server, BizTalk, Exchange, and Active Directory.
  • An easy to use GUI interface which makes creating batch files for the PAL.vbs script.
  • A GUI editor for creating or editing your own threshold files.
  • Creates an HTML based report for ease of copy/pasting into other applications.
  • Analyzes performance counter logs for thresholds using thresholds that change their criteria based on the computer's role or hardware specs.

Usage

The PAL tool is primarily a VBScript that requires arguments/parameters passed to it in order to properly analyze performance monitor logs. In v1.1 and later of PAL, a GUI interface has been added to help with this process.

In order to use PAL you need to install the tool (see download links below), and 2 additional tools from Microsoft – Log Parser 2.2 and Microsoft Office Web Components 2003. Note that you need this download EVEN IF YOU'RE USING Office 2007!

After installing, you run PAL from the Start menu and begin your analysis. Needless to say you will need to first capture some logs in order to "feed" them to PAL…

In order to capture the right counters from your server you can either use the counters you are knowledgeable of, or, in case you forgot which counters you should use, open PAL, select the correct pre-configured threshold file, and click on Edit. You'll see a list of pre-defined counters, which you can also manually edit if you wish to.

Now open Performance Monitor on the required server and navigate to Performance Logs and Alerts > Counter Logs.

Right-click Counter Logs and select New Log Settings. Give the new log a descriptive name, and then begin to add counters and objects as required. These counters will be captured on the server and used by PAL to analyze the system's performance.

You also need to define the interval for the capture (do not use a 1 second interval unless you really have to, as it will have a negative performance effect on the server).

When done, start the new log.

As stated above, PAL comes with a set of some threshold templates for AD, System Overview, IIS, SQL, Exchange and so on. You point the app at the performance log you've captured, choose a threshold template that best suits your needs, answer some questions, add the form and execute.

Back in PAL, choose the right threshold file and answer the file's specific questions on the bottom part of the window.

In step 3, select the right analysis interval. I used AUTO.

In step 4, click on the Add Form Settings to Batch File button. Now click Execute.

Once it completes it generates a webpage with the analysis information you desire. The webpage shows you alerts for activity that it finds suspect and graphs for the different areas of interest.

Looking at my results I can clearly see that my server is having some performance issues.

BTW, this capture was performed on a VM running with very modest hardware settings, so no wonder the results were so poor…

Requirements

Operating Systems - PAL runs successfully on all of the following operating systems: Windows XP SP2, Windows Vista, and Windows 2003 Server. Also, PAL is 32-bit only due to the OWC11 requirements.

Downloads

Use the following links to get PAL and the required additional files:

PAL v1.2 (current as of February 2008)Performance Analysis of Logs (PAL) Tool http://www.codeplex.com/PAL/Release/ProjectReleases.aspx?ReleaseId=10274

Log Parser 2.2

Log parser is a powerful, versatile tool that provides universal query access to text-based data such as log files, XML files and CSV files, as well as key data sources on the Windows® operating system such as the Event Log, the Registry, the file system, and Active Directory. PAL uses the Log Parser tool to query perform logs and to create charts and graphs for the PAL report.http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&DisplayLang=en

Microsoft Office Web Components 2003Log Parser requires the Office Web Components 2003 in order to create charts. You need this download EVEN IF YOU'RE USING Office 2007!http://www.microsoft.com/downloads/details.aspx?FamilyID=7287252c-402e-4f72-97a5-e0fd290d4b76

An update for the .NET Framework 3.5 Service Pack 1 is available

An update for the .NET Framework 3.5 Service Pack 1 is available
 

The issues that this update fixes

The update for the .NET Framework 3.5 SP1 fixes the issues that are described in the following articles in the Microsoft Knowledge Base:
958481  (http://support.microsoft.com/kb/958481/ ) List of the issues that are addressed by the Application Compatibility Update for the .NET Framework 2.0 Service Pack 2
958483  (http://support.microsoft.com/kb/958483/ ) List of the issues that are addressed by the Application Compatibility Update for the .NET Framework 3.0 Service Pack 2
958484  (http://support.microsoft.com/kb/958484/ ) List of the issues that are addressed by the Application Compatibility Update for the .NET Framework 3.5 Service Pack 1

Download information

The following files are available for download from the Microsoft Download Center:

For Windows XP and for Windows Server 2003

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows XP x86 and Windows Server 2003 x86 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=6c095bba-6100-4ec9-9c54-6450b0212565&displaylang=en)

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows Server 2003 IA-64 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=F762C302-CC21-4FA7-A4D5-0C7FC68A6BCD&displaylang=en)

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows XP x64 and Windows Server 2003 x64 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=A4F52459-DFE5-4BC3-8F7F-AA688879B1DC&displaylang=en)

For Windows Vista and for Windows Server 2008

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows Vista x86 and Windows Server 2008 x86 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=B9DE7937-2C12-4F16-AD66-A31B83931953&displaylang=en)

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows Server 2008 IA-64 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=CB8395F9-6D70-4C94-8430-AAE7C08FDCC2&displaylang=en)

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows Vista x64 and Windows Server 2008 x64 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=98E83614-C30A-4B75-9E05-0A9C3FBDD20D&displaylang=en)

Windows Installer 4.5 is available

Windows Installer 4.5 is available
 

Microsoft Windows Installer is a component of the Windows operating system. Windows Installer provides a standard foundation for installing and uninstalling software. Software manufacturers can create the setup of their products to use Windows Installer to help make software installation, maintenance, and uninstallation straightforward and easy.

Windows Installer 4.5 is now available as a redistributable system component for the following operating systems:
  • Windows Server 2008, 32-bit editions
  • Windows Server 2008, 64-bit editions
  • Windows Server 2008, Itanium-based editions
  • Windows Vista
  • Windows Vista Service Pack 1 (SP1)
  • Windows XP Service Pack 2 (SP2)
  • Windows XP Service Pack 3 (SP3)
  • Windows Server 2003 SP1
  • Windows Server SP2
This article describes all the new and improved features of Windows Installer 4.5. Windows Installer 4.5 is a minor update to Windows Installer 4.0. Windows Installer 4.0 was released in November 2006. Windows Installer 4.5 contains new and improved features and addresses some issues in Windows Installer 4.0. All the packages and updates that you can apply to Windows Installer 4.0, to Windows Installer 3.x, and to Windows Installer 2.0 are fully supported in Windows Installer 4.5.

 

Download the installer for all versions of Windows

The following file is available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download
Download the Windows Installer 4.5 Redistributable package now. (http://go.microsoft.com/fwlink/?LinkId=120486)

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591  (http://support.microsoft.com/kb/119591/ ) How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

New and improved features in Windows Installer 4.5

The following new and improved features have been implemented in Windows Installer 4.5.

Multiple package transaction

In a multiple package transaction, you can create a single transaction from multiple packages. In a multiple package transaction, a chainer is used to dynamically include packages in the transaction. If one or more of the packages do not install as expected, you can roll back the installation.

Embedded UI handler

You can embed a custom user interface (UI) handler in the Windows Installer package. This makes a custom UI easier to integrate. You can also invoke an embedded UI handler from the Add or Remove Programs item in Control Panel. Or, you can invoke an embedded UI handler during a Windows Installer repair process.

Embedded chainer

You can use the embedded chainer to add packages to a multiple package transaction. You can use an embedded chainer to enable installation events across multiple packages. For example, you can enable install-on-demand events, repair events, and uninstall events across multiple packages.

Update supersedence resiliency

This feature lets you correct for changes in the FeatureComponent table during supersedence.

Shared component patching resiliency during uninstall

This feature makes sure that the most recent version of a component is available to all products.

Custom action execution on update uninstall

This feature lets an update add or change a custom action so that the custom action is called when an update is uninstalled.

Issues that are addressed in Windows Installer 4.5

The issues present in earlier versions of Windows Installer that are addressed in Windows Installer 4.5 are as follows:
  • The SeBackupPrivilege user right was missing in the Windows Installer service. This lack hindered any custom actions that needed this user right.
  • Some case-sensitive service-name comparisons in the InstallValidate action resulted in an unnecessary "files in use" message in Windows Vista.
  • When you uninstalled an update that added a new component, the component was also uninstalled. This occurred even if the component was shared by other products

An update for the .NET Framework 3.5 Service Pack 1 is available

An update for the .NET Framework 3.5 Service Pack 1 is available
 

The issues that this update fixes

The update for the .NET Framework 3.5 SP1 fixes the issues that are described in the following articles in the Microsoft Knowledge Base:
958481  (http://support.microsoft.com/kb/958481/ ) List of the issues that are addressed by the Application Compatibility Update for the .NET Framework 2.0 Service Pack 2
958483  (http://support.microsoft.com/kb/958483/ ) List of the issues that are addressed by the Application Compatibility Update for the .NET Framework 3.0 Service Pack 2
958484  (http://support.microsoft.com/kb/958484/ ) List of the issues that are addressed by the Application Compatibility Update for the .NET Framework 3.5 Service Pack 1

Download information

The following files are available for download from the Microsoft Download Center:

For Windows XP and for Windows Server 2003

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows XP x86 and Windows Server 2003 x86 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=6c095bba-6100-4ec9-9c54-6450b0212565&displaylang=en)

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows Server 2003 IA-64 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=F762C302-CC21-4FA7-A4D5-0C7FC68A6BCD&displaylang=en)

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows XP x64 and Windows Server 2003 x64 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=A4F52459-DFE5-4BC3-8F7F-AA688879B1DC&displaylang=en)

For Windows Vista and for Windows Server 2008

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows Vista x86 and Windows Server 2008 x86 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=B9DE7937-2C12-4F16-AD66-A31B83931953&displaylang=en)

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows Server 2008 IA-64 package now. (http://www.microsoft.com/downloads/details.aspx?familyid=CB8395F9-6D70-4C94-8430-AAE7C08FDCC2&displaylang=en)

Collapse this imageExpand this image
Download
Download the Microsoft .NET Framework 3.5 Family Update for Windows Vista x64 and Windows Server 2008 x64 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=98E83614-C30A-4B75-9E05-0A9C3FBDD20D&displaylang=en)

Windows Installer 4.5 is available

Windows Installer 4.5 is available
 

Microsoft Windows Installer is a component of the Windows operating system. Windows Installer provides a standard foundation for installing and uninstalling software. Software manufacturers can create the setup of their products to use Windows Installer to help make software installation, maintenance, and uninstallation straightforward and easy.

Windows Installer 4.5 is now available as a redistributable system component for the following operating systems:
  • Windows Server 2008, 32-bit editions
  • Windows Server 2008, 64-bit editions
  • Windows Server 2008, Itanium-based editions
  • Windows Vista
  • Windows Vista Service Pack 1 (SP1)
  • Windows XP Service Pack 2 (SP2)
  • Windows XP Service Pack 3 (SP3)
  • Windows Server 2003 SP1
  • Windows Server SP2
This article describes all the new and improved features of Windows Installer 4.5. Windows Installer 4.5 is a minor update to Windows Installer 4.0. Windows Installer 4.0 was released in November 2006. Windows Installer 4.5 contains new and improved features and addresses some issues in Windows Installer 4.0. All the packages and updates that you can apply to Windows Installer 4.0, to Windows Installer 3.x, and to Windows Installer 2.0 are fully supported in Windows Installer 4.5.

 

Download the installer for all versions of Windows

The following file is available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download
Download the Windows Installer 4.5 Redistributable package now. (http://go.microsoft.com/fwlink/?LinkId=120486)

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591  (http://support.microsoft.com/kb/119591/ ) How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

New and improved features in Windows Installer 4.5

The following new and improved features have been implemented in Windows Installer 4.5.

Multiple package transaction

In a multiple package transaction, you can create a single transaction from multiple packages. In a multiple package transaction, a chainer is used to dynamically include packages in the transaction. If one or more of the packages do not install as expected, you can roll back the installation.

Embedded UI handler

You can embed a custom user interface (UI) handler in the Windows Installer package. This makes a custom UI easier to integrate. You can also invoke an embedded UI handler from the Add or Remove Programs item in Control Panel. Or, you can invoke an embedded UI handler during a Windows Installer repair process.

Embedded chainer

You can use the embedded chainer to add packages to a multiple package transaction. You can use an embedded chainer to enable installation events across multiple packages. For example, you can enable install-on-demand events, repair events, and uninstall events across multiple packages.

Update supersedence resiliency

This feature lets you correct for changes in the FeatureComponent table during supersedence.

Shared component patching resiliency during uninstall

This feature makes sure that the most recent version of a component is available to all products.

Custom action execution on update uninstall

This feature lets an update add or change a custom action so that the custom action is called when an update is uninstalled.

Issues that are addressed in Windows Installer 4.5

The issues present in earlier versions of Windows Installer that are addressed in Windows Installer 4.5 are as follows:
  • The SeBackupPrivilege user right was missing in the Windows Installer service. This lack hindered any custom actions that needed this user right.
  • Some case-sensitive service-name comparisons in the InstallValidate action resulted in an unnecessary "files in use" message in Windows Vista.
  • When you uninstalled an update that added a new component, the component was also uninstalled. This occurred even if the component was shared by other products

How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000

How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
 
This step-by-step article describes methods that you can use to troubleshoot the "NTLDR Is Missing" error message that you may receive when you try to start Microsoft Windows 2000.

How to Troubleshoot the "NTLDR Is Missing" Error Message

When you start your Windows 2000-based computer, you may receive the following error message:
NTLDR is missing
Press any key to restart
This problem may occur if the basic input/output system (BIOS) on your computer is outdated, or if one or more of the following Windows boot files are missing or damaged:
Ntldr
Ntdetect.com
Boot.ini
To resolve this issue, verify that the BIOS on your computer is current, and then use one or more of the following methods, as appropriate to your situation, to repair the Windows 2000 startup environment.

IMPORTANT: Microsoft recommends that you fully back up your data on a regular basis. This is the best defense against data loss, and it must be a part of any disaster recovery plan.

Verify That the BIOS on the Computer Is Current

Make sure that the latest revision for BIOS is installed on the computer. Contact the computer manufacturer to inquire about how to obtain, and then install the latest BIOS update that is available for the computer.

For information about how to configure and how to verify the correct BIOS settings for the computer, see the computer documentation or contact the manufacturer of the computer. For information about how to contact your computer manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
65416  (http://support.microsoft.com/kb/65416/ ) Hardware and software vendor contact information, A-K

60781  (http://support.microsoft.com/kb/60781/ ) Hardware and software vendor contact information, L-P

60782  (http://support.microsoft.com/kb/60782/ ) Hardware and software vendor contact information, Q-Z
For more information about how to contact BIOS manufacturers, click the following article numbers to view the articles in the Microsoft Knowledge Base:
243909  (http://support.microsoft.com/kb/243909/ ) List of BIOS manufacturer Web sites Part 1
243971  (http://support.microsoft.com/kb/243971/ ) List of BIOS manufacturer Web sites Part 2

To repair the Windows startup environment, use one or more of the following methods, as appropriate to your situation.

Method 1: Use a Boot Disk to Start the Computer

  1. Create a Windows 2000 boot disk that contains the following files:
    Ntldr
    Ntdetect.com
    Boot.ini
    Ntbootdd.sys
    For more information about how to create a boot disk, click the following article numbers to view the articles in the Microsoft Knowledge Base:
    301680  (http://support.microsoft.com/kb/301680/ ) How to create a boot disk for an NTFS or FAT partition in Windows
    101668  (http://support.microsoft.com/kb/101668/ ) How to use a Windows boot disk to prevent boot failure
  2. Modify the Boot.ini file to point to the correct hard disk controller and to the correct volume for your Windows installation. For more information about how to create a boot disk, click the following article number to view the article in the Microsoft Knowledge Base:
    311578  (http://support.microsoft.com/kb/311578/ ) How to edit the Boot.ini file in Windows 2000
  3. Insert the boot disk into the computer's floppy disk drive, and then restart the computer.
  4. Copy the Ntldr file, the Ntdetect.com file, and the Boot.ini file from the boot disk to the system partition of the local hard disk.

Method 2: Use the Recovery Console

  1. Use the Windows 2000 Setup disks to restart the computer, or use the Windows 2000 CD-ROM to restart the computer.
  2. At the Welcome to Setup screen, press R to repair the Windows 2000 installation.
  3. Press C to repair the Windows 2000 installation by using the Recovery Console.
  4. Type the number that corresponds to the Windows installation that you want to repair, and then press ENTER. For example, type 1, and then press ENTER. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    229716  (http://support.microsoft.com/kb/229716/ ) Description of the Windows Recovery Console
  5. Type the Administrator password, and then press ENTER.
  6. Type map, and then press ENTER. Note the drive letter that is assigned to the CD-ROM drive that contains the Windows 2000 CD-ROM.
  7. Type the following commands, pressing ENTER after you type each one, where drive is the drive letter that you typed in step 4 of "Method 2: Use the Recovery Console," of this article:
    copy drive:\i386\ntldr c:\

    copy drive:\i386\ntdetect.com c:\
    If you are prompted to overwrite the file, type y, and then press ENTER.

    NOTE: In these commands, there is a space between the ntldr and c:\, and between ntdetect.com and c:\.
  8. Type the following command, and then press ENTER:
    type c:\Boot.ini
    A list similar to the following list appears:
    [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT  [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect 						
    If you receive the following message, the Boot.ini file may be missing or damaged:
    The system cannot find the file or directory specified.
  9. If the Boot.ini file is missing or damaged, create a new one. To do so, follow these steps:
    1. Use a text editor, such as Notepad or Edit.com, to create a boot loader file similar to the following boot loader file:
      [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT  [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect 						
      For more information, click the following article number to view the article in the Microsoft Knowledge Base:
      102873  (http://support.microsoft.com/kb/102873/ ) Boot.ini and ARC path naming conventions and usage
      301680  (http://support.microsoft.com/kb/301680/ ) How to create a boot disk for an NTFS or FAT partition in Windows
    2. Save the file to a floppy disk as Boot.ini.

      NOTE: If you used Notepad to create the file, make sure that the .txt extension is not appended to the Boot.ini file name.
    3. Type the following command at the Recovery Console command prompt to copy the Boot.ini file from the floppy disk to the computer:
      copy a:\Boot.ini c:\
  10. Type exit, and then press ENTER. The computer restarts.

Method 3: Use the Windows 2000 CD-ROM

  1. Insert the Windows 2000 CD-ROM into the computer's CD-ROM drive or DVD-ROM drive, and start Windows 2000 Setup.
  2. On the Welcome to Setup page, press R.
  3. On the Windows 2000 Repair Options page, press R.
  4. When you are prompted to select one of the repair options, press M.
  5. Press the UP ARROW, press the UP ARROW again, to select Verify Windows 2000 system files, and then press ENTER to clear the selection.
  6. Press the DOWN ARROW to select Continue (perform selected tasks), and then press ENTER. The following message appears:
    You need an Emergency Repair disk for the Windows 2000
    installation you want to repair.
  7. Do one of the following, as appropriate to your situation:
    • If you have an Emergency Repair Disk, follow these steps:
      1. Press ENTER.
      2. Insert the Emergency Repair Disk into the computer's floppy disk drive, and then press ENTER.
      3. Follow the instructions to repair the installation, and then restart the computer.
      -or-
    • If you do not have an Emergency Repair Disk, follow these steps:
      1. Press L. You receive a message similar to the following:
        Setup has found Windows 2000 in the following folder:
        drive:\WINNT "Microsoft Windows 2000"
      2. Press ENTER.

        Setup examines the disks, and then completes the repair process.
    For more information about the emergency repair feature, click the following article number to view the article in the Microsoft Knowledge Base:
    231777  (http://support.microsoft.com/kb/231777/ ) How to create an Emergency Repair Disk in Windows 2000


If Setup Cannot Locate Windows 2000

If you do not have a Windows 2000 Emergency Repair Disk, and if Setup cannot locate the Windows 2000 installation, follow these steps:
  1. Start Windows 2000 Setup.
  2. On the Setup will install Windows 2000 on partition page, select Leave the current file system intact (no changes), and then press ENTER.
  3. Press ESC to install Windows 2000 to a new folder.
  4. In the Select the folder in which the files should be copied box, type \tempwin, and then press ENTER.

    Setup installs a new copy of Windows 2000.
  5. Log on to the new copy of Windows 2000.
  6. Click Start, and then click Run.
  7. In the Open box, type cmd, and then click OK.
  8. At the command prompt, type drive:, where drive is the boot drive of the computer, and then press ENTER. For example, type c:, and then press ENTER.
  9. Type attrib -h -r -s Boot.ini, and then press ENTER.
  10. Type edit Boot.ini, and then press ENTER.

    Edit.com opens a Boot.ini file that is similar to the following file:
    [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN [operating systems] multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN="Microsoft Windows 2000 Professional" /fastdetect  					
  11. Replace all instances of TEMPWIN with WINNT. The Boot.ini file that appears is similar to the following file:
    [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect  					
  12. Press ALT+F, and then press S.
  13. Press ALT+F, and then press X.
  14. Type attrib +h +r +s Boot.ini, and then press ENTER.
  15. Type exit to quit the command prompt.
  16. Restart the computer.
  17. At the Please select the operating system to start screen, use the ARROW keys to select Microsoft Windows 2000, and then press ENTER.
  18. Start Windows Explorer, locate the following folders, and then delete them:
    Tempwin
    All Users.Tempwin

Additional Resources

For more information about how to troubleshoot the "NTLDR is Missing" error message, click the following article numbers to view the articles in the Microsoft Knowledge Base:
255220  (http://support.microsoft.com/kb/255220/ ) "NTLDR is missing" error message when you upgrade or install Windows 2000 over Windows 95, Windows 98 or Windows Millennium Edition
228004  (http://support.microsoft.com/kb/228004/ ) Changing active partition can make your system unbootable
883275  (http://support.microsoft.com/kb/883275/ ) You cannot start your computer after you modify the permissions in Windows Server 2003, in Windows XP, or in Windows 2000

Perform a Parallel Installation of Windows 2000

If you cannot resolve the behavior described in the "Symptoms" section of this article by using any of the methods discussed in this article or by viewing the Knowledge Base articles in the Additional Resources section of this article, perform a parallel installation of Windows 2000, and then use Windows Explorer to copy the data that you want to recover from your original Windows installation.

For more information about how to perform a parallel installation of Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
266465  (http://support.microsoft.com/kb/266465/ ) How to perform a parallel installation of Windows 2000 or Windows Server 2003

How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000

How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
 
This step-by-step article describes methods that you can use to troubleshoot the "NTLDR Is Missing" error message that you may receive when you try to start Microsoft Windows 2000.

How to Troubleshoot the "NTLDR Is Missing" Error Message

When you start your Windows 2000-based computer, you may receive the following error message:
NTLDR is missing
Press any key to restart
This problem may occur if the basic input/output system (BIOS) on your computer is outdated, or if one or more of the following Windows boot files are missing or damaged:
Ntldr
Ntdetect.com
Boot.ini
To resolve this issue, verify that the BIOS on your computer is current, and then use one or more of the following methods, as appropriate to your situation, to repair the Windows 2000 startup environment.

IMPORTANT: Microsoft recommends that you fully back up your data on a regular basis. This is the best defense against data loss, and it must be a part of any disaster recovery plan.

Verify That the BIOS on the Computer Is Current

Make sure that the latest revision for BIOS is installed on the computer. Contact the computer manufacturer to inquire about how to obtain, and then install the latest BIOS update that is available for the computer.

For information about how to configure and how to verify the correct BIOS settings for the computer, see the computer documentation or contact the manufacturer of the computer. For information about how to contact your computer manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
65416  (http://support.microsoft.com/kb/65416/ ) Hardware and software vendor contact information, A-K

60781  (http://support.microsoft.com/kb/60781/ ) Hardware and software vendor contact information, L-P

60782  (http://support.microsoft.com/kb/60782/ ) Hardware and software vendor contact information, Q-Z
For more information about how to contact BIOS manufacturers, click the following article numbers to view the articles in the Microsoft Knowledge Base:
243909  (http://support.microsoft.com/kb/243909/ ) List of BIOS manufacturer Web sites Part 1
243971  (http://support.microsoft.com/kb/243971/ ) List of BIOS manufacturer Web sites Part 2

To repair the Windows startup environment, use one or more of the following methods, as appropriate to your situation.

Method 1: Use a Boot Disk to Start the Computer

  1. Create a Windows 2000 boot disk that contains the following files:
    Ntldr
    Ntdetect.com
    Boot.ini
    Ntbootdd.sys
    For more information about how to create a boot disk, click the following article numbers to view the articles in the Microsoft Knowledge Base:
    301680  (http://support.microsoft.com/kb/301680/ ) How to create a boot disk for an NTFS or FAT partition in Windows
    101668  (http://support.microsoft.com/kb/101668/ ) How to use a Windows boot disk to prevent boot failure
  2. Modify the Boot.ini file to point to the correct hard disk controller and to the correct volume for your Windows installation. For more information about how to create a boot disk, click the following article number to view the article in the Microsoft Knowledge Base:
    311578  (http://support.microsoft.com/kb/311578/ ) How to edit the Boot.ini file in Windows 2000
  3. Insert the boot disk into the computer's floppy disk drive, and then restart the computer.
  4. Copy the Ntldr file, the Ntdetect.com file, and the Boot.ini file from the boot disk to the system partition of the local hard disk.

Method 2: Use the Recovery Console

  1. Use the Windows 2000 Setup disks to restart the computer, or use the Windows 2000 CD-ROM to restart the computer.
  2. At the Welcome to Setup screen, press R to repair the Windows 2000 installation.
  3. Press C to repair the Windows 2000 installation by using the Recovery Console.
  4. Type the number that corresponds to the Windows installation that you want to repair, and then press ENTER. For example, type 1, and then press ENTER. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    229716  (http://support.microsoft.com/kb/229716/ ) Description of the Windows Recovery Console
  5. Type the Administrator password, and then press ENTER.
  6. Type map, and then press ENTER. Note the drive letter that is assigned to the CD-ROM drive that contains the Windows 2000 CD-ROM.
  7. Type the following commands, pressing ENTER after you type each one, where drive is the drive letter that you typed in step 4 of "Method 2: Use the Recovery Console," of this article:
    copy drive:\i386\ntldr c:\

    copy drive:\i386\ntdetect.com c:\
    If you are prompted to overwrite the file, type y, and then press ENTER.

    NOTE: In these commands, there is a space between the ntldr and c:\, and between ntdetect.com and c:\.
  8. Type the following command, and then press ENTER:
    type c:\Boot.ini
    A list similar to the following list appears:
    [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT  [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect 						
    If you receive the following message, the Boot.ini file may be missing or damaged:
    The system cannot find the file or directory specified.
  9. If the Boot.ini file is missing or damaged, create a new one. To do so, follow these steps:
    1. Use a text editor, such as Notepad or Edit.com, to create a boot loader file similar to the following boot loader file:
      [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT  [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect 						
      For more information, click the following article number to view the article in the Microsoft Knowledge Base:
      102873  (http://support.microsoft.com/kb/102873/ ) Boot.ini and ARC path naming conventions and usage
      301680  (http://support.microsoft.com/kb/301680/ ) How to create a boot disk for an NTFS or FAT partition in Windows
    2. Save the file to a floppy disk as Boot.ini.

      NOTE: If you used Notepad to create the file, make sure that the .txt extension is not appended to the Boot.ini file name.
    3. Type the following command at the Recovery Console command prompt to copy the Boot.ini file from the floppy disk to the computer:
      copy a:\Boot.ini c:\
  10. Type exit, and then press ENTER. The computer restarts.

Method 3: Use the Windows 2000 CD-ROM

  1. Insert the Windows 2000 CD-ROM into the computer's CD-ROM drive or DVD-ROM drive, and start Windows 2000 Setup.
  2. On the Welcome to Setup page, press R.
  3. On the Windows 2000 Repair Options page, press R.
  4. When you are prompted to select one of the repair options, press M.
  5. Press the UP ARROW, press the UP ARROW again, to select Verify Windows 2000 system files, and then press ENTER to clear the selection.
  6. Press the DOWN ARROW to select Continue (perform selected tasks), and then press ENTER. The following message appears:
    You need an Emergency Repair disk for the Windows 2000
    installation you want to repair.
  7. Do one of the following, as appropriate to your situation:
    • If you have an Emergency Repair Disk, follow these steps:
      1. Press ENTER.
      2. Insert the Emergency Repair Disk into the computer's floppy disk drive, and then press ENTER.
      3. Follow the instructions to repair the installation, and then restart the computer.
      -or-
    • If you do not have an Emergency Repair Disk, follow these steps:
      1. Press L. You receive a message similar to the following:
        Setup has found Windows 2000 in the following folder:
        drive:\WINNT "Microsoft Windows 2000"
      2. Press ENTER.

        Setup examines the disks, and then completes the repair process.
    For more information about the emergency repair feature, click the following article number to view the article in the Microsoft Knowledge Base:
    231777  (http://support.microsoft.com/kb/231777/ ) How to create an Emergency Repair Disk in Windows 2000


If Setup Cannot Locate Windows 2000

If you do not have a Windows 2000 Emergency Repair Disk, and if Setup cannot locate the Windows 2000 installation, follow these steps:
  1. Start Windows 2000 Setup.
  2. On the Setup will install Windows 2000 on partition page, select Leave the current file system intact (no changes), and then press ENTER.
  3. Press ESC to install Windows 2000 to a new folder.
  4. In the Select the folder in which the files should be copied box, type \tempwin, and then press ENTER.

    Setup installs a new copy of Windows 2000.
  5. Log on to the new copy of Windows 2000.
  6. Click Start, and then click Run.
  7. In the Open box, type cmd, and then click OK.
  8. At the command prompt, type drive:, where drive is the boot drive of the computer, and then press ENTER. For example, type c:, and then press ENTER.
  9. Type attrib -h -r -s Boot.ini, and then press ENTER.
  10. Type edit Boot.ini, and then press ENTER.

    Edit.com opens a Boot.ini file that is similar to the following file:
    [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN [operating systems] multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN="Microsoft Windows 2000 Professional" /fastdetect  					
  11. Replace all instances of TEMPWIN with WINNT. The Boot.ini file that appears is similar to the following file:
    [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect  					
  12. Press ALT+F, and then press S.
  13. Press ALT+F, and then press X.
  14. Type attrib +h +r +s Boot.ini, and then press ENTER.
  15. Type exit to quit the command prompt.
  16. Restart the computer.
  17. At the Please select the operating system to start screen, use the ARROW keys to select Microsoft Windows 2000, and then press ENTER.
  18. Start Windows Explorer, locate the following folders, and then delete them:
    Tempwin
    All Users.Tempwin

Additional Resources

For more information about how to troubleshoot the "NTLDR is Missing" error message, click the following article numbers to view the articles in the Microsoft Knowledge Base:
255220  (http://support.microsoft.com/kb/255220/ ) "NTLDR is missing" error message when you upgrade or install Windows 2000 over Windows 95, Windows 98 or Windows Millennium Edition
228004  (http://support.microsoft.com/kb/228004/ ) Changing active partition can make your system unbootable
883275  (http://support.microsoft.com/kb/883275/ ) You cannot start your computer after you modify the permissions in Windows Server 2003, in Windows XP, or in Windows 2000

Perform a Parallel Installation of Windows 2000

If you cannot resolve the behavior described in the "Symptoms" section of this article by using any of the methods discussed in this article or by viewing the Knowledge Base articles in the Additional Resources section of this article, perform a parallel installation of Windows 2000, and then use Windows Explorer to copy the data that you want to recover from your original Windows installation.

For more information about how to perform a parallel installation of Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
266465  (http://support.microsoft.com/kb/266465/ ) How to perform a parallel installation of Windows 2000 or Windows Server 2003

How to configure Internet Connection Sharing in Windows XP

How to configure Internet Connection Sharing in Windows XP
 
 

This article describes how to set up and use the Internet Connection Sharing feature in Microsoft Windows XP. With Internet Connection Sharing, you can use networked computers to share a single connection to the Internet.

 

How to use Internet Connection Sharing

To use Internet Connection Sharing to share your Internet connection, the host computer must have one network adapter that is configured to connect to the internal network, and one network adapter or modem that is configured to connect to the Internet.

On the host computer

On the host computer, follow these steps to share the Internet connection:
  1. Log on to the host computer as Administrator or as Owner.
  2. Click Start, and then click Control Panel.
  3. Click Network and Internet Connections.
  4. Click Network Connections.
  5. Right-click the connection that you use to connect to the Internet. For example, if you connect to the Internet by using a modem, right-click the connection that you want under Dial-up.
  6. Click Properties.
  7. Click the Advanced tab.
  8. Under Internet Connection Sharing, select the Allow other network users to connect through this computer's Internet connection check box.
  9. If you are sharing a dial-up Internet connection, select the Establish a dial-up connection whenever a computer on my network attempts to access the Internet check box if you want to permit your computer to automatically connect to the Internet.
  10. Click OK. You receive the following message:
    When Internet Connection Sharing is enabled, your LAN adapter will be set to use IP
    address 192.168.0.1. Your computer may lose connectivity with other computers on
    your network. If these other computers have static IP addresses, it is a good idea to set them
    to obtain their IP addresses automatically. Are you sure you want to enable Internet
    Connection Sharing?
  11. Click Yes.
The connection to the Internet is shared to other computers on the local area network (LAN). The network adapter that is connected to the LAN is configured with a static IP address of 192.168.0.1 and a subnet mask of 255.255.255.0

To view a video about how to configure the host computer for Internet Connection Sharing, click the Play button (
Collapse this imageExpand this image
Play
				button
) on the following Windows Media Player viewer:


<<The embedded streaming media event requires Microsoft Windows Media Player to view.>>


If you have problems viewing this video, click here.


Note To view this video, you must use Windows Media Player 7.0 or later.

For additional information about how to obtain Windows Media Player version 7.1, click the following article number to view the article in the Microsoft Knowledge Base:
299321  (http://support.microsoft.com/kb/299321/ ) Description and availability of Windows Media Player 7.1

On the client computer

To connect to the Internet by using the shared connection, you must confirm the LAN adapter IP configuration, and then configure the client computer. To confirm the LAN adapter IP configuration, follow these steps:
  1. Log on to the client computer as Administrator or as Owner.
  2. Click Start, and then click Control Panel.
  3. Click Network and Internet Connections.
  4. Click Network Connections.
  5. Right-click Local Area Connection, and then click Properties.
  6. Click the General tab, click Internet Protocol (TCP/IP) in the This connection uses the following items list, and then click Properties.
  7. In the Internet Protocol (TCP/IP) Properties dialog box, click Obtain an IP address automatically (if it is not already selected), and then click OK.

    Note You can also assign a unique static IP address in the range of 192.168.0.2 to 192.168.0.254. For example, you can assign the following static IP address, subnet mask, and default gateway:
       IP Address      192.168.0.2    Subnet mask     255.255.255.0    Default gateway 192.168.0.1 					
  8. In the Local Area Connection Properties dialog box, click OK.
  9. Quit Control Panel.
To view a video about how to confirm the LAN adapter IP configuration, click the Play button (
Collapse this imageExpand this image
Play button
) on the following Windows Media Player viewer:


<<The embedded streaming media event requires Microsoft Windows Media Player to view.>>


If you have problems viewing this video, click here.


Note To view this video, you must use Windows Media Player 7.0 or later.

For additional information about how to obtain Windows Media Player version 7.1, click the following article number to view the article in the Microsoft Knowledge Base:
299321  (http://support.microsoft.com/kb/299321/ ) Description and availability of Windows Media Player 7.1
To configure the client computer to use the shared Internet connection, follow these steps:
  1. Click Start, and then click Control Panel.
  2. Click Network and Internet Connections.
  3. Click Internet Options.
  4. In the Internet Properties dialog box, click the Connections tab.
  5. Click the Setup button.

    The New Connection Wizard starts.
  6. On the Welcome to the New Connection Wizard page, click Next.
  7. Click Connect to the Internet, and then click Next.
  8. Click Set up my connection manually, and then click Next.
  9. Click Connect using a broadband connection that is always on, and then click Next.
  10. On the Completing the New Connection Wizard page, click Finish.
  11. Quit Control Panel.
When you now start Microsoft Internet Explorer, the client computer will try to connect to the Internet by using the host computer's shared Internet connection.

To view a video of how to configure the client computer to use the shared Internet connection, click the Play button (
Collapse this imageExpand this image
Play
				button
) on the following Windows Media Player viewer:


<<The embedded streaming media event requires Microsoft Windows Media Player to view.>>


If you have problems viewing this video, click here.


Note To view this video, you must use Windows Media Player 7.0 or later.

For additional information about how to obtain Windows Media Player version 7.1, click the following article number to view the article in the Microsoft Knowledge Base:
299321  (http://support.microsoft.com/kb/299321/ ) Description and availability of Windows Media Player 7.1
 

Troubleshooting

When you turn on Internet Connection Sharing on the host computer, the host computer's LAN adapter is automatically assigned the IP address of 192.168.0.1. Therefore, one of the following situations may occur:
  • IP address conflict
    Each computer on the LAN must have a unique IP address. If more than one computer has the same IP address, an IP conflict occurs, and one of the network adapters turns off until the conflict is resolved. To resolve this conflict, configure the client computer to automatically obtain an IP address, or assign it a unique IP address.
  • Loss of network connectivity
    If your network is configured with a different IP address range than Internet Connection Sharing uses, you will lose network connectivity with the host computer. To resolve this issue, configure the client computers to automatically obtain an IP address, or assign each client computer a unique IP address in the range of 192.168.0.2 to 192.168.0.254

LinkWithin

Popular Posts