Architecture

As you might expect, such a solution must have both client and server-side components. The client executes scripts and returns success/failure to the server. The server processes feedback and provides reports. That is essentially all there is to it as the deployment functionality leverages the familiar Group Policy mechanism.

Requirements

Installation Overview
Once you have downloaded Specops Command setup, execute it on the server you wish to function as the Specops Command Server.

Server installation requires that you select the database server you wish to use; this can be either a MS SQL Server already in your environment, or you can install a local instance of SQL Server Express. Setup also has you create security groups for accessing feedback on the Specops Command Server (two actually: Specops Command Admins who get full access to everything, and Specops Command Users who get read access to feedback information).

The Admin Tools installation lets you install the Specops Command administrative tools. There are no real options here: either they are installed or not. The installation is separated so that you can choose to install the admin tools on other systems, separate from the local installation of the Specops Command Server.

There is also a Specops Reporting component you can install which allows for web based reporting which leverages IIS server. This can be installed on the Specops Command server or another server in your environment.

That covers the server components, finally we have client deployment. Available as a task within the same setup assistant wizard, you can either ignored the action or use it to get one client up and running quickly for testing. The preferred method of client deployment is (you guessed it) Group Policy.

I must report that I did have some issues in rolling the client out via Group Policy and finally resorted to a local installation on my lab systems. While the client rollout may go very smoothly for you, when things do not go so smoothly troubleshooting can be a challenge. It should be noted here that the .NET Framework is installed prior to the client side extension installation. PowerShell is not actually installed until a PowerShell script is assigned to it using Specops Command. If you are troubleshooting client installation you may find this helpful to know.

Performing the Installation

Start by creating a (or specifying an existing) GPO linked to all computers that should receive the client. You'll also need to choose a file share where the client, .NET Framework and PowerShell installations are offered for installation. You must download PowerShell from Microsoft for yourself (MS does not let vendors distribute PowerShell). Specops Command requires that you download each of the different distributions of PowerShell (both 32-bit and 64-bit installations for Server, XP, and Vista). In the end, the client setup is linked to the GPO and your deployment of Specops Command is ready to go. If this sounds like a lot of work, fear not: the Specops Command Setup Assistant actually makes each task as easy as pushing a button (really).

[Page 2 of 4]     1 | 2 | 3 | 4