Client Security Solution Manager

The Client Security Solution Manager allows you to create, manage, and deploy multiple security preferences to computers that have been configured to run the ThinkVantage plug-in collection. It consists of two tools: CSS Configurations, through which you can create and manage security settings, and CSS Deployment, which is used to deliver security configurations to remote workstations.

To deploy CSS to a client Machine

  1. Access the CSS Deployment window by clicking the New CSS Deployment button on the toolbar or by right-clicking on CSS Deployment and selecting New.
  2. Select the deployment settings you wish to apply. Notice that the CSS version you want to deploy is included in the configuration.
  3. Click Save.

The CSS Deployment window allows you to select the install language, install Password Manager, or create a private, remotely-authorized disk on the target computer. This window also allows you to set the BIOS admin password or the TPM chip password. Private disk is only available for CSS7 configurations.

Creating a new CSS Configuration

  1. Select Tools | ThinkVantage | Client Security Solution Manager.
  2. Access the CSS Configuration window by clicking on the New CSS Configuration button on the toolbar or by right clicking on CSS Configurations and selecting New.
  3. Select the appropriate security settings.
  4. Click Save at the bottom of the window.

Within the CSS Configuration window, you can select the appropriate level of security needed for items including: logging on to Windows, unlocking computers, logging on to Rescue and Recover, file sharing, and screensavers. General convenience levels for security settings are also available, allowing the overall setting to be either more secure or more convenient. CSS Configuration also supports password management for Mozilla, Windows applications, and Internet Explorer. Configurations that are unique to a version of CSS are noted.

After a new CSS Configuration has been created, you can right-click it to schedule it as an automated task, rename the configuration, change any of the settings you chose when it was created, or delete it entirely.

Follow the same procedure to schedule the distribution of configurations that you use to schedule all other types of tasks in the console.