Using a small footprint GUI and a web application, Lansweeper can run reports and show extensive information as to what’s in the environment. What’s more, Lansweeper gives the admin some control of those computers that other tools can’t, or are too cumbersome to use. The prerequisites for installing Lansweeper are fairly simple. The Windows 2003 server that will be running the app needs to have. Net Framework 2.0 and Internet Information Systems (IIS) installed. Lansweeper also stores it’s data in SQL, so access to SQL Server 2000 or later, or SQL express, is required. This can be on the local server, or a remote, dedicated SQL server. The installer prompts for the website virtual directory name, installation path, and service account credentials. The service account must have administrative access to whatever resources you’ll be monitoring. ![]() Domain administrator access is preferred. ![]() Once installed, some minor steps are needed so that remote computers can check in. The easiest way to accomplish this is via a group policy. The excellent documentation for Lansweeper walks the administrator through each step of creating the GPO and linking the. The next time computers boot, they’ll begin checking in with the server running Lansweeper. Once machines start checking in, they are visible in the web interface for Lansweeper. When launched, the web interface opens to the Digital Dashboard as seen in Figure 1 below. The Digital Dashboard provides a general overview of information on the environment, including high priority and important and informational alerts. Each is a hyperlink to one of more than 80 detailed reports, allowing the administrator to drill down to the minutest detail. Other views in the web interface include the Software and Hardware reports, General Reports, and two pages of license compliance – one for applications, and one for Operating Systems.
0 Comments
Leave a Reply. |