in

myITforum.com

This Blog

Syndication

SCUG at myITforum.com

December 2009 - Posts

  • System Center Data Protection Manager 2007: TCP Chimney and Bandwidth throttling

    Hey All, I’ve seen a number of cases where the backup of hyper-v guests is failing and also where the backup is extremely slow. Almost every time, some small adjustments need to be made to fix them, but if you are not the network administrator or hardware administrator, this can cause a lot of discussions. Suppose you have a DPM server with all the latest patches till date, a hyper-v host and some virtual machines. You are of course also backing up other stuff from other servers. You notice...(read more)
  • System Center Data Protection Manager: Cool script

    Hey All,

    One of my colleagues is managing a rather large environment on a daily base.  He has to manage two backup solutions (HP Data Protector and SCDPM) that share one tape library.  From time to time, he need to set a tape not free in that library (Otherwise SCDPM will use that tape while it is needed for the HP solution).  To do his work faster, he created a small powershell script where he has to give the name of the slot in order to mark that tape as not free.

    So here it is:

    $LIB = Get-DPMLibrary -DPMServerName "<servernaam>"

    $TP1 = Get-Tape -DPMLibrary $LIB

    $TapeLocationList = Read-Host "Tape location (Slot-x) "

    foreach ($media in $TP1)

    {

    if ($TapeLocationList -contains $media.Location)

    {

    Set-Tape -Tape $media -NotFree

    Echo "Tape in $($media.Location) marked as NOT FREE."

    }

    else

    {

    Echo "Tape in location $($media.Location) is not in requested slot."

    }

    }

     

    Enjoy

    Cheers,

    Mike

    PS: Thanks to Steven Van der Taelen for writing this script

  • SCCM : How to create a collection to list Windows Embedded Devices

    Hi , For a customer , I had the requirement for creating a collection that was filled with Windows Embedded Devices using the WMI property as selection criterion. This can be done by creating a new collection and create a dynamic membership rule that is a targeting the single criterion of the “OSProductSuite” property. If the value detected is 64, these systems are running XPe, Windows Embedded Standard or Embedded NT. Other possible values for OSProductSuite are shown in the table below: 1 - Small...(read more)
  • How to find Windows Embedded devices in SCCM.

    I am implementing at one of my customers a situation where 3000 Windows embedded devices will be installed. In this environments I want to be sure that any Windows Embedded devices connected to the network gets discovered as an embedded system. SCCM needs to be configured to include an additional WMI property’s to distinguish Windows XP systems from Windows Embedded operating systems. To do this , you need to open up the “SMS_def.mof” file on the SCCM Primary site server. It is located in the \inboxes...(read more)
  • System Center Service Manager 2010: Error when registering the Datawarehouse

    While registering a Datawarehouse with Service Manager 2010 I got the following error in the eventviewer of the Datawarehouse server… A module of type "Microsoft.SystemCenter.Orchestration.Module.WorkflowWorkItemModule" reported an exception System.FormatException: String was not recognized as a valid DateTime. at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles) at System.DateTime.Parse(String s, IFormatProvider provider) at Microsoft.SystemCenter...(read more)
  • Importing data into SCSM (part4) – The manual & CSV import CI creation

    To make the “Importing data into SCSM” blog list complete we also have to provide information about the manual and CSV file import. Previous blog posts have listed the “automated” ways to import CI’s in SCSM from AD, SCCM & SCOM. AD is a source for CI’s that in most cases can be used. SCCM and SCOM add information to existing CI’s and both create new CI’s who are not available in SCSM. In cases where both System Center products are not available, a manual or CVS import can be used for adding CI’s in SCSM.

    Manual creation of CI’s:

    Computers, printer, Users & Services can be imported via the manual way. (Default mgmt. console folders – other items can be imported and made visible via SCSM View’s.

    In brief, the manual procedure (As example, a computer CI is added)

    1. In the Service Manager console, select Configuration Items.

    2. In the Configuration Items pane, expand Configuration Items, and then expand Computers. In order to create a new printer, User or service, select the appropriate folder.

    3. Select All Computers, and then in the Tasks pane, under Computers, click Create Computer.

    4. In the form that appears, create a configuration item for a computer. Use the General, Software and Related Items tabs to fill in the information about the computer.

    image     

    5. Click OK to save the new configuration item.

    For your information, some form screenshots of the creation of the other CI’s.

    Note: Not all fields can be provided with data via the CSV file import. In certain cases it is mandatory to have SCCM or SCOM to add the required data.

    • Form for new printer CI’s

    image   

    • Form for New service CI’s

    image        

    • Form for New User CI’s

    image

    CSV import

    Configuration items contained in a comma-separated values (CSV) file can be imported into the Service Manager database by using the Import from CSV file feature. This feature allows you to bulk-import instances of any class type or projection type that is defined in the Service Manager database. This feature can be used to:

    • Create Configuration Item or Work Item instances from data stored in a tabular format.
    • Bulk-edit existing database instances.
    • Populate the Service Manager database with data exported from an external database.
    • Circumvent data entry through forms when many class instances must be created at once.

    Two files are required to import a set of instances by using the CSV import feature:

    • A data file that consists of a series of comma-delimited object instances. The data file must end with the ".csv" file name extension.
    • A format file that specifies the class type or projection type of the instances present in the data file. Every instance in the data file is assumed to be of this type. The format file also specifies
      • The subset of properties (and in the case of projections, components) being imported for the indicated type.
      • The order in which those properties appear (as columns) in the associated data file. The format file must have the same file name as the "csv" file that it describes, and it must end with the ".xml" file name extension.

    Note: For more information about CSV import and class type or projection types, see the blog post Using the CSV import feature (http://go.microsoft.com/fwlink/?LinkId=159957) and download the file CSVImport.docx. Very good explanation about the topic…

    The creation of the CSV data file

    To use the CSV Importer, we first need to save the spreadsheet as a “.csv” file. The first row of the spreadsheet is assumed to contain an object instance (and not a header), so we remove this line and save the spreadsheet in a file named "import.csv".

    Example of a csv file

    image

    Creating the format file

    The data file “import.csv” is now created. Next step is the creation of a format file that is suitable for importing the rows contained in the import.csv file. The first step in writing the format file is identifying the class type or projection type to be used for the instances in the CSV file.

    Microsoft.Windows.Computer is the most appropriate choice for the object type and property set that we wish to import. We begin by declaring the class of the object being imported:

    <CSVImportFormat>

    <Class Type="Microsoft.Windows.Computer">

    ...

    </Class>

    </CSVImportFormat>

    In our example the format file should look like this:

    image

    When these files are created, we can import this information into SCSM.

    Import of the data in SCSM

    With the format and data files prepared, we are ready to use the CSV Import task.

    1. To access it, navigate to the Administration page in SCSM console

    2. Click on the Connectors folder and select the Import from CSV file… task

    image

    3. On the Import Instances from CSV file page, provide the path to the xml format file and the actual CSV file.

    image

    4. Click Import to start the creation of the CI’s in SCSM.

    5. After the import a summary page is provided with the results of the import.

    6. All done…imported items should be visible in the Configuration items page in SCSM (corresponding folders)

    Update of a CI via CSV

    The update of a CI in SCSM goes in a similar way. Creation of the CSV file with a correct format file is required. When we re-use the example from above, the CSV and format files need to be updated with the additional information.

    For example, we add the required Properties.

    image

    FYI: List of possible Property ID’s for the Microsoft.Windows.Computer class

    image

    After the update on the format file we need to add the proper information in the CSV file.

    image

    Import the CSV file and job done!

    Enjoy,

    Kurt Van Hoecke

    http://www.linkedin.com/in/bunkco

    Part 1: (Importing data into SCSM (part 1) – the SCSM AD & SCCM connectors)

    Part 2: (Importing data into SCSM (part2) - the SCSM OpsMgr Alert connector)

    Part 3: (Importing data into SCSM (part3) - the SCSM OpsMgr CI connector)

  • OpsMgr Management pack APC ISX Central Integration Management Pack

    This week I had to implement an APC management pack at a customer site and I will explain how to get it working. This customer is using APC to monitor and configure his Uninterruptible power supply (UPS) infrastructure. “ The APC InfraStruXure (ISX) Central is a network appliance that collects data from, and monitors status of, devices that provide data-center-critical infrastructure. The ISX Central Integration Management pack for Microsoft’s System Center Operations Manager 2007 provides...(read more)
  • System Center Data Protection Manager 2007 SP1: Bare Metal Recovery of Windows Server 2008

    Hey All,

    Microsoft has updated its whitepaper Bare Metal Recovery of Windows Server 2008 with System Center Data Protection Manager 2007 SP1

    It can be found at http://download.microsoft.com/download/2/A/B/2AB50D28-D892-4BF3-B823-C62CA02E4CF8/DPM%202007%20SP1%20Bare%20Metal%20Recovery%20of%20Windows%20Server%202008.doc

    Important to know is that the DPM SRT (System Recovery Tool) that is used for recovering windows 2003 and windows XP has been completely replaced by the built-in backup utility of Windows server 2008, the WSB (Windows Server Backup) utility.

    In the white-paper, they give a step-by-step instruction on how to enable bare metal recovery of a windows server 2008

    Except for the fact that you need to do some additional work, this procedure certainly has some possibilities for the BMR of a physical windows server 2008. 

    Still, I believe more in the procedure of working with the offline P2V which was discussed two weeks ago.  Since Matthijs Vreeken has responded on my questions I’m gonna keep working on this procedure and test it out.

    Cheers,

    Mike

    Posted Dec 09 2009, 03:54 AM by SCUG.be
    Filed under: ,
  • SCCM : Issues with upgrading secondary sites to SP2 via Software Distribution on Windows 2008

    Scenario : Your Primary site server has been upgrade from SCCM 2007 SP1 R2 towards SCCM 2007 SP2.You want to upgrade all your secondary site server with are running on Windows Server 2008 to Service pack 2 on an automated way with Software distribution. The Secondary site server have the Proxy MP , State migration point and PXE service point role installed. You will create a package with the source files and create a program that runs unattended with the following parameters: setup.exe /upgrade <path...(read more)
  • OpsMgr : two new Novell Linux Management packs

    Hi,   Novell just announced two new additions to the Novell Linux Management Pack or NLMP family: SLES 11 and RHEL 5.x. The Novell Linux Management Packs for OpsMgr expands the monitoring capabilities of Operations Manager by enabling monitoring of key Linux services that are not monitored now with the Cross platform management packs.   You can download the NLMP for OpsMgr from here: http://download.novell.com/Download?buildid=QD-rc_brurs Thanks, Alexandre Verkinderen...(read more)
  • OpsMgr : Certificate for this system is not valid when installing Linux agent

    Today I ran into some Linux agent deployment issues. I needed to monitor about 20 Redhat Machines . In such an environment environment, Kerberos authentication is not possible. Therefore, certificates are used between the management server and the UNIX-based or Linux-based computers. First if you have some Cross-platform agent deployment issues please have a look at the following blog posts: http://wmug.co.uk/blogs/aquilaweb/archive/2009/07/21/opsmgr-r2-xplat-agent-deployment-field-notes.aspx http...(read more)
  • OpsMgr bug : console crashing when creating an override on cluster resource group monitor

    Be aware that there is a bug when you want to create an override on the resource group rollup monitor to change the maintenance mode behavior! Let’s see: In my example I have one cluster with 2 cluster nodes. I needed to do some maintenance on my nodes and they needed to be rebooted. So I put one node in maintenance mode so that my NOC team will not get alerted, do what I had to do and finally restarted my node and do the same for the other node. Suddenly I had someone of the NOC team yelling...(read more)
  • Importing data into SCSM (part3) – the SCSM OpsMgr CI connector

    As specified in previous blog, two OpsMgr connectors are available in Service Manager:

    • Operations Manager Alert connector: The OpsMgr alert connector is used to automatically generate incidents that are based on Operations Manager alerts.
    • Operations Manager CI connector: This connector will import objects that were discovered by Operations Manager into the Service Manager database. (For example, distributed apps or SQL databases.)

    This blog will handle the Operations Manager CI Connector.

    There are two steps that need to be followed for the installation of the OpsMgr CI connector:

    • Import of the management packs: In order to import objects discovered in Operations Manager, Service Manager will need a list of class definitions for these objects that we can obtain from the Operations Manager management packs.
    • Installation of the OpsMgr CI connector in SCSM: The actual installation and configuration of the connector in the SCSM mgmt console.

    Import the management packs

    Download the file InstallOMMPs.exe from the Connect Web site

    1. On the SCSM server, create a folder for the file InstallOMMPs.exe. (for example D:\MP)

    2. Double-click InstallOMMPs.exe to extract the files.

    3. In the Unzip to folder field, type the location of the folder that you created in step 1, and then click Unzip. (D:\MP)

    4. On the Windows desktop, click Start, click Programs, click Windows PowerShell 1.0, right-click Windows PowerShell, and then click Run as administrator.

    5. Change directories to folder you created in step 1, and then click ENTER. (D:\MP)

    6. In the Windows PowerShell window, run the following commands:

    1. set-ExecutionPolicy unrestricted

    2. .\installOMMPs.ps1

    clip_image002

    1. Type exit and then press ENTER.

    If you have installed additional management packs in Operations Manager and you want to add the data from those additional management packs to Service Manager, you can edit the Operations Manager CI Connector to add the additional management packs.

    • Copy the OpsMgr Mgmt pack to the folder where InstallOMMPs.exe is extracted (In this example D:\MP)
    • Add a line with the mgmt pack name on the en of the following section of the Powershell script.

    clip_image004

    Import of the mgmt packs can be verified in the Management pack folder in Administration pane of the SCSM console.

    Installation of the OpsMgr CI connector in SCSM

    Follow this procedure to create an Operations Manager 2007 CI Connector:

    1. In the SCSM console, click Administration.

    2. In the Administration pane, expand Administration, and then click Connectors.

    3. In the Tasks pane, under Connectors, click Create Connector, and then select Operations Manager CI Connector.

    clip_image006

    4. On the General page, in the Name box, type a name for the new connector. Make sure that Enabled is selected, and then click Next.

    clip_image008

    5. On the Server Details page, in the Server name box, type the name of the server that is hosting the Operations Manager root management server.

    Under Credentials, either select the Run As account you created for the Alert connector and proceed, or click New and in the User name, Password, and Domain fields, type the credentials for the Run As account, and then click OK.

    Test the connection before preceding the wizard.

    clip_image010

    6. On the MP Selection page, either click Select all or select the management packs which define the configuration items you would like to import, and then click Next.

    clip_image012

    7. On the Schedule page, adjust the Synchronization schedule as needed and click Next.

    clip_image014

    8. On the Summary page, review the configuration and then click Create.

    9. On the Completion page, click Close.

    clip_image016

    To validate the creation of an Operations Manager 2007 CI Connector

    • Objects discovered by Operations Manager are listed as Configuration Items in Service Manager.
    • Confirm the status of a connector by viewing the columns in the Connector pane where you will find information such as Start Time, Finish Time, Status, and Percentage.

     

    Create Views for the imported CI’s

    Configuring the OpsMgr CI Connector indicates that additional Configuration Items are required in SCSM. SCSM does not have system-defined views or forms for some items, like imported items via the OpsMgr CI Connector. Own created views can make this CI’s visible in the SCSM console.

    Follow the procedures below to create a view for imported SQL Server database configuration items.

    1. In the Service Manager console, select Configuration Items.

    2. In the Configuration Items pane, right click Configuration Items, and then click Create folder. (This is an optional step, you can create own views in existing folders)

    clip_image018

    3. In the Create folder page, provide a name for the folder and the management pack to store the information. Keep in mind to organize your information in the proper mgmt. packs. In this example we use an own created mgmt. pack for Views.

    clip_image020

    4. Back in the Configuration Items pane, select on the just created folder. In the Tasks pane, click Create View.

    5. In the Create View dialog box, on the General page, in the Name text box, type a name for the new view. For example, type SQL Databases.

    In the Description box, enter a description of the view you are creating. Click OK.

    clip_image022

    6. Drill down to the Criteria section,Search for objects of specific class, click Browse.

    7. In the Choose Class dialog box, in the View list select All basic classes.

    8. In the Search text field, type SQL, and then click the search button (blue magnifying glass).

    9. In the Class list, select SQL database, and then click OK.

    clip_image024

    10. No further criteria are required for this example and we can remove the existing criteria from the box.

    clip_image026

    11. Click the Display tab then in the Columns to display list, select Database Name, Database Size (MB) String, and other items that could be interested for as console info. Click OK.

    clip_image028

    12. Select the new view named SQL Server Databases to see the list of the imported SQL databases.

     

    All done…

     

    Enjoy,

    Kurt Van Hoecke

    http://www.linkedin.com/in/bunkco

    This is a second post in the importing data into SCSM series:

    Part 1: (Importing data into SCSM (part 1) – the SCSM AD & SCCM connectors)

    Part 2: (Importing data into SCSM (part 2) – the SCSM OpsMgr Alert connector)

  • OpsMgr Webconsole Runtime error “Server Error in ‘/’ Application”

    Just a little reminder that if you install the OpsMgr web console after the UI console has already been installed you will need to Copy the following files from the %Program Files%\System Center Operations Manager 2007 directory to the %Program Files%\System Center Operations Manager 2007\Web Console\Bin directory:   Corgent.Diagramming.CommandResources.dll Corgent.Diagramming.CustomElements.dll Microsoft.ReportViewer.Common.dll Microsoft.ReportViewer.Webforms.dll   Otherwise you will get...(read more)
  • System Center Data Protection Manager 2010 – SQL End-user Recovery

    Hey All,

    While reading up on the different blogs I follow, I found this interesting post from Anders Bengtsson, Microsoft MVP.

    It’s all about SQL End-user Recovery.   In DPM 2010, it is possible to give SQL Administrators the rights to recover their databases without the need for a backup administrator.

    See the article for the technical specifications (http://contoso.se/blog/?p=1130)

    The end-user recovery drew my attention for the following reasons:

    - End-user recovery makes the live of a backup administrator more easy.  In 2007, when we implement the end-user recovery for files for users, we notice every time again, that the backup administrators are having less work

    - Doing this for SQL administrators gives you an additional advantage.  Imagine that you have a test environment at your site.  This test environment is a virtualized “copy” of your production environment.  The programmers team is doing different things there and testing new features and so on.  They need a refresh of the database very often.  Now the SQL team can do this instead of the backup administrator.  How cool is that.  You as a backup administrator have less work, the programmers team will be helped more quickly, it’s a win win situation :-)

     

    Now I am wondering if Microsoft would pull this further? What if we could delegate end-user recovery tasks for exchange, sharepoint and so on…

    For the moment this is not possible, or at least I don’t have no documentation about this yet, but when I see the power of the SQL end-user recovery, I’m quite sure that this will be a much requested feature for the future

    Cheers,

    Mike

    Posted Dec 02 2009, 03:57 AM by SCUG.be
    Filed under:
More Posts Next page »
Copyright - www.myITforum.com, Inc. - 2010 All Rights reserved.
Powered by Community Server (Commercial Edition), by Telligent Systems