TechNet Virtual Lab: System Center Service Manager 2010 Setup and Deployment

TechNet Virtual Lab: System Center Service Manager 2010 Setup and Deployment

  • Comments 1
  • Likes

image Language(s): English.

Product(s): Microsoft System Center.

Audience(s): IT Generalist.

Duration: 90 Minutes

Event Overview

The high level steps you will be exercising in this lab are: reading about various topologies, getting an overview of the sizing tool, and reading about the system requirements, installing a management server, Service Manager Database, data warehouse management server, data warehouse databases, analyst console (installed with the management server), and Self Service Portal, importing data into the Service Manager Database from Active Directory, System Center Configuration Manager, and System Center Operations Manager, configuring notification subscriptions and Workflows, and registering the data warehouse management server with the Service Manager management server.

For more details visit this site.

J.C. Hornbeck | System Center Knowledge Engineer

clip_image001 clip_image002

Bookmark and Share
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • SETUP & DEPLOYMENT WIZARD

    How do we use it?

    First of all, we have to select the ‘Other Project Types’ option from the New Project. Then, we get some options:

    1)Setup Project: Creates a Windows Installer project to which files can be added. This project type is the most general of all.

    2)Web Setup Project: The deployment tools in Visual Studio .NET also support deployment to a Web server. Using deployment to install files on a Web server provides an advantage over simply copying files, in that deployment handles any issues with registration and configuration automatically.

    3)Merge Module Project: Most commonly, merge modules are used for files that are installed to a common location (such as the System folders) and/or shared by multiple applications. For example, many ActiveX and .NET controls that are sold by third-party tool vendors come with their own merge modules so that the developer can simply merge the installation logic of the control into their setup without worrying about having to manually specify the file’s information and setup logic.

    4)Setup Wizard: Creates a Windows Installer project with the aid of a wizard.

    5)Cab Project: The CAB project is a Setup and Deployment project, which is used to create a .cab file containing a set of files in a compressed archive. This .cab file is used to package ActiveX controls that can be downloaded from a Web server. The CAB project reduces the size of a distribution package. Using CAB project, developers can implement Authenticode signing and specify the display name, version, level of compression, and location of dependent files.

    You can have a look at the Video Tutorial @

    visiontechno.net/studymats

    to see that how do we use Setup And Deployment Wizard.