Getting Started with Service Manager Cmdlets for Windows PowerShell: Create $Profile #sysctr

Every time you start a Windows PowerShell session to run a Service Manager cmdlet, you must first add the Service Manager Windows PowerShell snap-in. As most of us are lazy admins I created a “service manager” profile having all Service Manager cmdlets by default available when starting PowerShell session.

Create a profile

  • Before we decide to create a profile, let’s check to see whether we already have one:

Test-Path $profile
  • If the profile exists this command will return True; if it doesn’t exist, the command will return False. If this command returns False, you need to create the profile.
  • Creating a profile is really easy. Simply type this at the command prompt:
  •  

    New-Item -path $profile -type file -force
    

      Continue reading “Getting Started with Service Manager Cmdlets for Windows PowerShell: Create $Profile #sysctr”

    Service Manager Exchange Connector in different domains #sysctr

    Early this year, the Exchange connector for Service Manager was released. The Exchange Connector provides the following capabilities:

    • Create incident from email (replaces out of the box functionality; just turn it off)
    • The sending user is looked up in the CMDB and related to the incident as the affected user
    • The email subject becomes the incident title
    • The email body becomes the incident description
    • Update incident action log from email
    • Resolve or close incidents from email
    • Approve/reject change requests from email
    • Update change request “action log” from email
    • Mark manual activities completed from email
    • Add email file attachment to work items as attachments
    • Emails can be sent in from outside the organization
    • Emails can be sent from users which do not exist in the CMDB yet and a new user record will be created for them and related to the incident

    Implementing Service Manager Exchange connector for a customer last week brings me to the following challange; the Service Manager setup is installed in domain X but the Exchange environment was installed in domain Y without any chains or trusts. Service Manager workflow Account (domain X) requires permissions to domain Y accessing the mailbox defined.

    Continue reading “Service Manager Exchange Connector in different domains #sysctr”

    Troubleshooting Service Manager 2010 Reporting #sysctr

    Last week I had some challenges getting Service Manager Reporting working properly in a scenario with a remote SQL Server Reporting Services (SSRS) as shown below.

    Context.
    During deployment of the Service Manager data warehouse management server, you can specify the server to which Microsoft SQL Server Reporting Services (SSRS) will be deployed. By default, the computer that is hosting the data warehouse management server is selected during setup. If you specify a different computer, you are prompted to follow this procedure to configure the remote SSRS server. Before you follow this procedure, you must perform the following actions:

    • Copy Microsoft.EnterpriseManagement.Reporting.Code.dll from the Service Manager installation media to the computer that is hosting SSRS.
    • Add a code segment to a configuration file on the computer that is hosting SSRS.
    Manual Steps to Configure the Remote SQL Server Reporting Services http://technet.microsoft.com/en-us/library/ff461215.aspx

    Service Manager Roadmap Update – What’s Coming ?

    At Tech Ed Africa and Tech Ed Europe in the past few weeks we have publicly unveiled more of the roadmap for Service Manager.  Below are a couple of the slides that were shared.

    SP1 is a release that is focused only on the following things:

    • Bug fixes – includes all the bug fixes in cumulative updates 1, 2, and 3.
    • Support for SQL 2008 R2
    • 9 additional languages for the entire product (not just the portal)
      • Czech
      • Danish
      • Finnish
      • Swedish
      • Greek
      • Dutch
      • Norwegian
      • Portuguese (Portugal)
      • Polish

    The next major release is currently called “R2” and will include:

    image

    As each of these areas is currently in design/development right now we aren’t really going into details about the specifics, but we did want to share with you some of the new and exciting things we are currently working on.  This next release will line up with the planned next SCOM, SCCM, and SCVMM releases.  We’ll update the connectors in SCSM as needed to work with those new versions as well.

    Here’s the timeframes (unchanged from the announcement at MMS 2010):

    image

    V1, Authoring Tool, and Compliance/Risk MP are released now.  SP1 release is targeted for “around the end of the year”.  We are in the final testing phases now with zero bugs meeting the bar left to fix for SP1 right now.  The R2 beta will be sometime in the middle of CY 2011 and the R2 release in the second half of 2011.

    The SCSM “R2” TAP program is in full swing now.  We have been demonstrating some of the new builds with these features already working to the TAP customers and partners to get feedback.  Great to see the rapid progress on new developments while also seeing customers rapidly adopting and deploying SCSM 2010

    Source System Center Service Manager TechNet blog

    Open Beta for Microsoft System Center Service Manager 2010 IPD Guide—Now Available for Download!

     

    The Infrastructure Planning and Design team is working on a new guide: Microsoft System Center Service Manager 2010. Get the beta by visiting the Connect
    website at https://connect.microsoft.com/content/content.aspx?ContentID=6556&SiteID=14.

    This IPD guide takes the IT architect through an easy-to-follow process for successfully designing the servers and components for a System Center Service
    Manager implementation, resulting in a design that is sized, configured, and appropriately placed to deliver the stated business benefits, while also considering the performance, capacity, and fault tolerance of the system.

    The guide covers these key steps in the System Center Service Manager infrastructure design process:

    • Defining the project scope by identifying the necessary System Center Service Manager features, the requirements of the process management packs, and the
      targeted population of the organization.
    • Mapping the selected features and scope to determine the required server roles.
    • Designing the fault tolerance, configuration, and placement of the management servers, portals, and supporting SQL Server databases.

    The IPD Guide for System Center Service Manager 2010 can help you reduce planning time and costs, and ensure a successful rollout of System Center
    Service Manager—helping your organization to more quickly benefit from this platform for automating and adapting IT Service Management best practices such
    as those found in Microsoft Operations Framework (MOF) and the IT Infrastructure Library (ITIL).

     

    Tell us what you think!
    Download the beta guide and please provide us with the following:

    1. Your honest feedback. No matter what it is or how you phrase it, we can handle it.

    2. Your edits and comments in the doc. Please open the doc, add comments, and use track changes to show us what changes you would make.

    3. A marked-up doc sent to us by email at IPDfdbk@microsoft.com by November 9, 2010.

     

    Benefits for participation:

    • You get an early look at the guide.
    • You will be listed on the acknowledgments page for providing useable feedback.

    We appreciate your input and will work to make each guide as helpful and useful as possible. Infrastructure Planning and Design streamlines the planning process by:

    • Defining the technical decision flow through the planning process.
    • Listing the decisions to be made and the commonly available options and considerations.
    • Relating the decisions and options to the business in terms of cost, complexity, and other characteristics.
    • Framing decisions in terms of additional questions to the business to ensure a comprehensive alignment with the appropriate business landscape.

     

    Tell your peers about IPD guides!

    Please forward this mail to anyone who wants to learn more about Infrastructure Planning and Design guides.

    Join the Beta Program

    Subscribe to the IPD beta program and we will notify you when new beta guides become available for your review and feedback. These are open beta downloads. If you are not already a member of the IPD Beta Program and would like to join, follow these steps:

    1. Go here to join the IPD beta program:

    https://connect.microsoft.com/InvitationUse.aspx?ProgramID=1587&InvitationID=IPDM-QX6H-7TTV&SiteID=14

    If the link does not work for you, copy and paste it into the Web browser address bar.

    2. Sign in using a valid Windows Live ID.

    3. Enter your registration information.

    4. Continue to the IPD program beta page, scroll down to Infrastructure Planning and Design, and click the link to join the IPD beta program.

    Already a member of the IPD beta program? Go here to get the latest IPD beta downloads:

    https://connect.microsoft.com/content/content.aspx?ContentID=6556&SiteID=14

    Related Resources

    Check out all the Infrastructure Planning and Design team has to offer! Visit the IPD page on TechNet, http://www.microsoft.com/ipd, for additional information,
    including our most recent guides.