Deploying an Exchange Server Dashboard

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The Exchange Server Digital Dashboard provides a scalable platform for deploying Digital Dashboards. Microsoft® Exchange 2000 Server makes it possible for administrators to secure dashboards and provides the ability for users to personalize shared dashboards.

To deploy an exchange dashboard

  1. From the Development Environment, in the Solution Explorer, select the dashboard that you want to deploy.
  2. From the File menu, select File Save Copy As.
  3. In the File Save As dialog box, for the location, specify the server to which you want to deploy.

Secure Dashboards

As an administrator of an Exchange Server Digital Dashboard, you can control the extent to which users can modify their Digital Dashboards and Web Parts. The amount of control you give users often depends on the types of dashboards you deploy in your organization; for example, you probably want to give users full control of their personal dashboards, but you make it possible for users to modify only limited properties on a team dashboard or a dashboard that displays company news.

Here are some of the options that are available to you:

  • Complete lock down. In this scenario, you set Access Control Lists (ACLs) to restrict all write permissions to the administrator group only. Users cannot add or remove Web Parts or modify dashboard properties. When you deploy a Digital Dashboard that is locked down completely, links to the Layout and Settings pages do not appear in the user interface. The link to the Content page is present; however, on the Content page, users only can see a list of Web Parts. They cannot import or delete Web Parts or modify their properties.
  • Users can view Web Parts in a dashboard based on role. In this scenario, you use read ACLs to limit access to certain Web parts in a given dashboard. This way, you can create a dashboard with a large number of Web Parts and control which users can see specific Web Parts in their dashboards. For example, the executives in your company would see a different set of Web Parts than the salespeople. If a user does not have permission to access a specific Web Part, that Web Part does not appear in the list of Web Parts on the Content page.
  • Users can customize Web Parts but cannot import or delete them. In this scenario, you use ACLs that control whether users can insert or delete rows in the Exchange Server catalog database. The Web Parts on the dashboard are locked down, but users can still customize the look and feel of the Web Parts and the dashboard.
  • Users have full control. In this scenario, you use ACLs to give users full control over a dashboard. Users can import and delete Web Parts and modify the look and feel of the dashboard by setting Web Part and dashboard properties.

See Also

Understanding the Digital Dashboard | Why Digital Dashboards? | Creating a Digital Dashboard Project | Security