Configuresoft review how we did it

We installed ECM 4.5.2 on a Windows 2003 Server (2GHz, 2G bytes RAM) running IIS and SQL Server 2000, all fully patched. We installed ECM agents on five Windows systems, running default installations of Win 2000 Server, Win 2000 Professional, Windows XP Professional and Win 2003 server. We installed the ECM agent on a Win 2000 Server.

We modified audit settings, password policy and directory settings on the Win 2000 Server. We set them as a mandatory compliance policy and set e-mail alerts on systems not in compliance with our defined policy. We then changed the settings directly on the computer and confirmed ECM alerted us to the non-compliant system and changed the setting to its correct value. For the remaining systems, we enforced the SANS Security Windows template on the default installations.

We installed Office on the Win 2000 Professional system and ran the "Software Installation over Last X days" report to confirm it collected data from the system on new software installations. We also ran the change log report to confirm the changes made to the Win 2003 Server system, which included all the configuration changes required to enforce the SANS template.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

We installed ECM 4.5.2 on a Windows 2003 Server (2GHz, 2G bytes RAM) running IIS and SQL Server 2000, all fully patched. We installed ECM agents on five Windows systems, running default installations of Win 2000 Server, Win 2000 Professional, Windows XP Professional and Win 2003 server. We installed the ECM agent on a Win 2000 Server.

We modified audit settings, password policy and directory settings on the Win 2000 Server. We set them as a mandatory compliance policy and set e-mail alerts on systems not in compliance with our defined policy. We then changed the settings directly on the computer and confirmed ECM alerted us to the non-compliant system and changed the setting to its correct value. For the remaining systems, we enforced the SANS Security Windows template on the default installations.

We installed Office on the Win 2000 Professional system and ran the "Software Installation over Last X days" report to confirm it collected data from the system on new software installations. We also ran the change log report to confirm the changes made to the Win 2003 Server system, which included all the configuration changes required to enforce the SANS template.

Read more about infrastructure management in Network World's Infrastructure Management section.