Command performance

Administering network PCs is about as much fun as preparing your income taxes and equally unavoidable. Even with all the advances in operating system development, most desktop PCs still require hands-on configuration, installation and troubleshooting.

One way to reduce the hassle is with ON Technology's ON Command Comprehensive Client Management (CCM) 4.0 system. CCM lets you plug a computer into the network, and without leaving your seat, boot it, install an operating system, load software packages and customize the desktop properties. Once the PC is up and running, you can perform almost any task, including shutting down or rebooting the machines and redoing a partial install.

CCM works with any desktop, though existing stations are harder to integrate than new ones. Some older desktops and laptops will require a boot disk and manual intervention because of CCM's design.

CCM works primarily with Intel's Wired for Management (WFM) technology, which has been built into the BIOS of every major PC vendor's desktop system manufactured since mid-year 1998. WFM includes a Pre-OS Execution Environment (PXE), a mini operating system that allows you to administer hardware or load software without first installing a full operating system.

In turn, PCs with a PXE built into their BIOSes require network interface cards (NIC) that support PXEs. For older desktops, you can install a NIC that supports boot Programmable Read Only Memories (PROM) that contain a PXE. Alternatively, you can resort to a disk-based version of the boot software for older systems that don't support an appropriate NIC or PXE, and for laptops because PC Card-based NICs do not yet support PXEs.

There are three layers to the CCM structure: the client PC layer, the server layer and the administration layer. The client PC layer consists of a boot agent on the PROM, or a disk that has a simple BOOTP or Dynamic Host Configuration Protocol client to contact the server; a pre-OS agent; and a desktop configuration agent.

The server layer includes the CCM server and an API. The CCM server has three components: a configuration server, which keeps track of all client configurations; a software depot for installation profiles; and a repository server for client logs. The API lets different administration tools control the CCM server.

At the administration layer you'll find the CCM administration console, through which you perform all management tasks; the Enterprise Viewer, a snap-in for the Microsoft Management Console that allows you to view the status of all CCM-managed clients; and a command-line interface (CLI) tool that allows you to run any CCM command directly from a command window.

In the field

We wanted to see CCM do three things: install NT 4.0 Workstation on a desktop, install Microsoft Office 95, and upgrade the system to Office 97. We also wanted to test CCM's InstallCam system, which records the installation of software so it can be duplicated on other desktops.

Using CCM, we loaded a DOS 7.0 (the DOS side of Windows 95) minisystem into a client PC's memory and ran it as a RAM disk. Once loaded, CCM installs a full TCP/IP stack and contacts the CCM server for further instructions. We told CCM to partition and format the 10G-byte disk.

After we prepared our clients, we used the CCM server to select the package to be installed, which included NT 4.0 Workstation and the CCM 4.0 client software. When we saved the configuration, CCM automatically initiated installation on the remote client. After about 20 minutes, we had a full NT client sitting at the logon prompt.

When we began installing Microsoft Office 95, we discovered that the CCM depot did not include a profile for Office 95. This gave us our chance to test the installation recording system.

We started InstallCam, pressed the record button, and launched the Office 95 setup program. When we completed the installation, we uninstalled Office 95 and, as a test, attempted to run the automated installation based on the profile we just created. At one point, InstallCam became confused between two similar dialog boxes. After a few minutes, ON's technical support staff was able to talk us through the process of debugging the InstallCam script, and we were able to run the installation profile without incident.

Finally, we upgraded Office 95 to Office 97. First we had to record the uninstallation process for Office 95. The Office 97 profile was available on our server, so we didn't have to record this installation process. We made one change to the Office 97 profile: We asked CCM to see if a previous version of Office was installed, and if so, to remove that version before installing the new one.

To see if everything would go through smoothly, we wiped out the entire system and told the CCM server software to reinstall the operating system, install Office 95 and upgrade to Office 97. The reinstallation ran without a hitch. We then successfully ran the entire scenario on three clients.

Once a PC is managed by CCM, any changes to its local configuration are saved on the CCM server and automatically restored if the desktop fails. If a desktop problem requires personal attention, an administrator can temporarily lock out a user and take control of the system remotely rather than trying to diagnose problems over the phone.

When it comes to tracking which clients have what software, ON Technology could do a little more to spruce up CCM, which has a built in database system but is not yet integrated with Microsoft's Open Database Connectivity protocol or Oracle Call Interface. Instead, all importing or exporting is done through text files.

CCM makes the most sense in networks of 500 or more client desktops, at which point ON Technology drops its price from $200 to $145 per seat. It's still not inexpensive, but the money you'll save in support costs may end up paying for the package and installation within a year or two.

RELATED LINKS On Command CCM: Trial and error
Some installation tips.

Scorecard and NetResults
How we ranked it in several categories, key findings and vendor contact info.

Shah is a freelance writer based in Tucson, Ariz. He can be reached at rawn@rtd.com