For those who are privy to the MSDN Subscription, MS had a utility called "System Stress for Windows 2000" on the Purple December 2002 DVD Disc #1914.
Basically you set up a Stress Server that you have the clients (that you want to stress or burn in) connect to, via network share. After the install, you have to make some custom configuration changes on the stress server. See the bottom part of this post under "To Start Stress" if you want to know more about this tool.
My problem (besides using MS !):
I have had problems with the following steps:
"For Windows 2000:
Expand the self extracting file \i386\DBG.EXE on the Windows 2000 Support Tools CD to C:\DEBUG.
Copy remote.exe and i386kd.exe from the \Debug\BIN\ directory to the \Debug\BIN\W2KFRE directory.
Copy the \i386\symbols directory of the Windows 2000 Support Tools CD to \Debug."
First of all there is no DBG.exe on my Win2k Support Tools CD. I have a Tools\I386\DBGPlus.exe file. I expanded this file an it does not have the Remote.exe or i386kd.exe mentioned in step b above. If I can get this resolved, I should be OK- got any takers?
I have not been able to find any info about this tool on MS site. If you find anything in the knowledge base/ technet/ etc, please let me know. MrMMills@onebox.com
To Start Stress
On the client type \\NTSTRESS\stress\stress.cmd or (for autostress) \\NTSTRESS\autostress\autostress.cmd.
Stress will start on the Client machine.
If this is the first time you have run stress on the Client, the 'Munger' window will appear. NT4.0 or Windows 2000 System Stress may be selected. Fill in the rest of information as requested. Click OK.
The Stress Sign On dialog will then appear. Fill in the information as requested. In the 'Type of stress' field, select csd. The values in this dropdown box are controlled by the stress.ini file on the Server.
In the Stress Sign On dialog, check "sched shutdown for" and fill in the month, day, year and hour you want stress to stop. for HCT testing, 48 hour stress testing runs are required.
Click 'OK'. Stress will start copying files from the server to the client.
When the Stress Manager appears, add any of the following tests that remain in the Additional Tests list to the Selected Tests list. These are required tests for HCT testing:
Connects
Data_Integrity
Datachk
Dd_Foxbear
Dd_Roids
Dx3_Fly
Dx3_Globe
GDI32
GDIMan
Gmemstress
GUIMan_Csd
GUIMan16
Handlecleanup
Heapstress
Lmemstress
Memfile
Menustrs
Mktropcl
OpenGL_Csd
OpenGL2_Csd
VDM_Fltsimulator
VDM_Foxpro
VDM_Word
The server will display the status of each client in the Stress Server GUI (regsrv).
The information on this screen will allow you to track failed and running machines. Machines will show as DEAD when they have crashed or have not fully rebooted.
Basically you set up a Stress Server that you have the clients (that you want to stress or burn in) connect to, via network share. After the install, you have to make some custom configuration changes on the stress server. See the bottom part of this post under "To Start Stress" if you want to know more about this tool.
My problem (besides using MS !):
I have had problems with the following steps:
"For Windows 2000:
Expand the self extracting file \i386\DBG.EXE on the Windows 2000 Support Tools CD to C:\DEBUG.
Copy remote.exe and i386kd.exe from the \Debug\BIN\ directory to the \Debug\BIN\W2KFRE directory.
Copy the \i386\symbols directory of the Windows 2000 Support Tools CD to \Debug."
First of all there is no DBG.exe on my Win2k Support Tools CD. I have a Tools\I386\DBGPlus.exe file. I expanded this file an it does not have the Remote.exe or i386kd.exe mentioned in step b above. If I can get this resolved, I should be OK- got any takers?
I have not been able to find any info about this tool on MS site. If you find anything in the knowledge base/ technet/ etc, please let me know. MrMMills@onebox.com
To Start Stress
On the client type \\NTSTRESS\stress\stress.cmd or (for autostress) \\NTSTRESS\autostress\autostress.cmd.
Stress will start on the Client machine.
If this is the first time you have run stress on the Client, the 'Munger' window will appear. NT4.0 or Windows 2000 System Stress may be selected. Fill in the rest of information as requested. Click OK.
The Stress Sign On dialog will then appear. Fill in the information as requested. In the 'Type of stress' field, select csd. The values in this dropdown box are controlled by the stress.ini file on the Server.
In the Stress Sign On dialog, check "sched shutdown for" and fill in the month, day, year and hour you want stress to stop. for HCT testing, 48 hour stress testing runs are required.
Click 'OK'. Stress will start copying files from the server to the client.
When the Stress Manager appears, add any of the following tests that remain in the Additional Tests list to the Selected Tests list. These are required tests for HCT testing:
Connects
Data_Integrity
Datachk
Dd_Foxbear
Dd_Roids
Dx3_Fly
Dx3_Globe
GDI32
GDIMan
Gmemstress
GUIMan_Csd
GUIMan16
Handlecleanup
Heapstress
Lmemstress
Memfile
Menustrs
Mktropcl
OpenGL_Csd
OpenGL2_Csd
VDM_Fltsimulator
VDM_Foxpro
VDM_Word
The server will display the status of each client in the Stress Server GUI (regsrv).
The information on this screen will allow you to track failed and running machines. Machines will show as DEAD when they have crashed or have not fully rebooted.
