HP Integrity iLO 2 Operations Guide

NOTE:
• Scriptable vMedia is available only if you have the iLO 2 Advanced Pack license and the
vMedia user privilege.
• Only one vMedia connection is supported at a time. You cannot connect with the scriptable
vMedia while the Applet vMedia is connected and vice versa.
Scriptable vMedia Supported Operating Systems
• Linux (Red Hat and SuSE)
• Windows
• HP-UX
• OpenVMS
• EFI
Setting Up IIS for Scripted vMedia
Before setting up Internet Information Services (IIS) for scripted vMedia, make sure IIS is operational.
Use IIS Manager to set up a simple website and verify that it is working correctly by browsing to
the site.
To configure IIS to serve diskette or ISO-9660 CD images for read only access:
1. Add a directory to your website, and place your images in the directory.
2. Verify that IIS can access the MIME type for the files you are serving. For example, if you
name your diskette images with the extension .img, you must add a MIME type for that
extension. Use the IIS Manager to access the Properties dialog of your website. On the HTTP
Headers tab, click MIME Types to add additional MIME types.
HP recommends you add the following types:
.img – application/octet-stream
.iso – application/octet-stream
3. Browse to the location of your images with a web browser, and download them to a client.
Your web server is configured properly for serving read-only diskette and CD images.
To configure IIS to serve diskette images for read/write operations:
1. Install Perl (if necessary). Active State's ActivePerl is an installer program that also sets itself
up to be a script interpreter for IIS. You can obtain it from the web at: http://
www.activestate.com/
2. Create a directory on your web site to hold the vMedia helper script, and copy the script to
that location.
3. To create an application directory, use the properties page for your directory. Under
Application Settings, click Create.
The icon for your directory in IIS Manager should change from a folder to a gear.
4. Set Execute Permissions to Scripts Only.
5. Verify that Perl is set up as a script interpreter. To view the application associations, click
Configuration on the properties page. Verify that Perl is configured as follows:
.pl c:\perl\bin\perl.exe "%s" %s GET,HEAD,POST
6. Verify your Web Service Extensions allows Perl scripts to execute. If not, click Web Service
Extensions, and set Perl CGI Extension to Allowed.
7. Verify the prefix variable in the helper script is set correctly. You can set it to the same path
as your document root, which can be similar to C:\inetpub\wwwroot.
SMASH Server Management Command Line Protocol 161