|
|
A Windows Media server must be enabled for load-testing before Windows Media Load Simulator can initiate simulated client connections to the server. You enable the Windows Media server for load-testing by placing an .asf file named WMLoad.asf in the home publishing point on the Windows Media server (usually SystemDrive\ASFRoot). You can create a WMLoad.asf file with Windows Media Encoder or Windows Media On-Demand Producer, or you can rename one of the existing .asf files in the ASFRoot folder to WMLoad.asf. Windows Media Load Simulator cannot access the Windows Media server if this file is not present.
Important Note After load-testing is completed on the server but before the server is placed into service, WMLoad.asf should be removed from the home publishing point or its file name should be changed, so that unauthorized users cannot use the load simulator to maliciously launch stream requests against the server.
One example of a malicious use of Windows Media Load Simulator is a denial-of-service attack. If a Windows Media server that is enabled for load-testing is actively streaming Windows Media content to clients on your intranet or on the Internet, an unauthorized user potentially can use the load simulator to initiate many simulated client connections to the server, thereby degrading the quality of streams viewed by your clients or even preventing your clients from accessing the Windows Media server.