You are browsing the archive for 2009 October.

Attend this SCCM Event with Wally Mead and 3 Belgian System Center MVP’s

1:05 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, events, SCCM v.Next, Wally Mead by Kenny Buntinx [MVP]

 Attend this SCCM Event with Wally Mead and 3 Belgian System Center MVP’s

More information can be found here http://scug.be/content/Events.aspx 

Agenda

·         15u30 Registration

·         16u Opening Keynote by Kenny Buntinx & Alexandre Verkinderen

·         16u15 Wmi & SCCM autodoc by Kim Oppalfens

·         17u15 Break and Drink

·         17u30 Demonstrations of ConfigMgr 2007 R2 addons by Wally Mead 

·         19u30 one hour lunch

·         20u30 Config Manager vNext overview by Wally Mead

·         21u30 Q&A and Drink

Configuration Manager 2007 Service Pack 2 RTW is available.

7:30 am in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, SCCM 2007, SCCM 2007 SP2 by Kenny Buntinx [MVP]

Configuration Manager 2007 Service Pack 2 Release to Web is available

The System Center Configuration Manager team has announced that the Configuration Manager 2007 Service Pack 2 RTW has been released on http://download.microsoft.com and available for download.

System Center Configuration Manager Service Pack 2 will add the following support :

  • New Operating System Support
    • Windows 7
    • Windows Vista Sp2
    • Windows Server 2008 R2
    • Windows Server 2008 SP2
  • New Features in Out of Band Management
    In addition to providing feature parity with SP1 and AMT firmware versions 3.2.1, 4.0 and 5.0, the following new features are supported:
    • Wireless management with up to 8 wireless profiles
    • End point access control: 802.1x support
    • Audit logging
    • Support for different power states
    • Power control options at the collection level
    • Data storage
    • Scheduling configuration for in-band provisioning
  • Asset Intelligence Certificate Requirement Removal
    Configuration Manager Service Pack 1 introduced Asset Intelligence v1.5. This version allowed customers to configure an online synchronization to ensure that their catalog was up to date with the latest Microsoft inventory for both hardware and applications. This initial release required a certificate. With Service Pack 2, the requirement to have the certificate has been removed, so any customer can configure their Asset Intelligence capabilities to connect online and update their catalog. Software Assurance is not required for this functionality.
  • 64-bit Architecture Development
    Service Pack 2 will also continue to deliver new support for x64 architectures, including the following:
    • X64 support for Operations Manager 2007 Client Agent
    • Update to Management Packs for 64-bit operating systems – SP2 will ship 64-bit performance counters (the management pack is a separate release)
    • Remote control support added for x64 XP and x64 Server 2003
  • Improved Client Policy Evaluation
    • Faster policy processing
    • More efficient software distribution configured to run at user logon
  • Branch Cache Support
    Support for scenarios where Windows Server 2008 R2 and Windows 7 Client are present and Branch Cache is enabled

 

Hope it Helps ,

Kenny

SccmAutoDoc by OSCC goes Beta 1

7:52 am in beta, ConfigMgr 2007, ConfigMgr 2007 R2, OSCC, SCCM 2007, SCCM 2007 R2, SccmAutoDoc by Kenny Buntinx [MVP]

What is SccmAutoDoc?

SccmAutoDoc is a command-line utility that documents a System Center Configuration Manager 2007 site in a human-readable format. Much effort has been put in making the document resemble closely to what you see in the Configuration Manager admin console. SccmAutodoc in other words documents your Site Configuration.

Additionally the goal is to document only relevant settings, and to not include items that are irrelevant. For example if the software inventory client agent is disabled, than it doesn’t make much sense to document the software inventory agent schedule.

What are the software requirements to be able to use SccmAutoDoc?

SccmAutodoc requires a machine with Word 2007 installed and access to the ConfigMgr site server and ConfigMgr Sms Provider. Word 2007 does NOT need to be installed on the Site server/SQL server or Sms Provider computer. The program can perfectly work from a remote machine running windows xp, Vista or Windows 7.

Word 2007 does need to have the primary interop assemblies installed, but these are part of a default word 2007 install. If you don’t have the primary interop assemblies for office 2007 installed, you can always download them here: <http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en>

What permissions do I need to run SccmAutoDoc?

SccmAutoDoc requires a user with Read permissions on the site object of the Configuration Manager site to be documented. The commandline allows you to optionally pass a user and password as arguments to perform the documentation. If you don’t specify a username and password than the currently logged in credentials are used.

Where can I get SccmAutoDoc?

SccmAutoDoc beta1 can be downloaded from  http://scug.be/media/g/sccmautodoc/default.aspx

How do I use SccmAutoDoc?

Just unzip the zipfile to a folder (the zip contains sccmautodoc.exe 2 dll’s and an xml file).

Then execute SccmAutoDoc from a command prompt, which will display the Usage statement.

Sample commandlines:

Ex1: sccmautodoc -sitecode S01 -server sccm01
     This command documents the site with sitecode S01 on server sccm01 with the user
     account that launched SccmAutodoc
Ex2: sccmautodoc -sitecode S01
     This command documents the site with sitecode S01 when running locally on the server.
Ex3: sccmautodoc -sitecode S01 -server sccm01
       -username Contosso\sccmadmin -password P@ssw0rd
     This command documents the site with sitecode S01 on server sccm01 with the user
     account Contosso\SccmAdmin and password
P@ssw0rd

 

 

Where can I send bug reports/feature request/suggestions?

All comment/bug reports/suggestsions/feature request are more than welcome at mailto:sccmautodoc@oscc.be .

Unless I am swamped with suggestions, I will do my utmost to respond to any inquires you might have.

If you send a bug report, please include the error you are receiving and a copy of the document created by the execution that errored out.

Is SccmAutoDoc freeware?

SccmAutodoc is not freeware, at present it is beta software, that eventually might end up as a reasonably priced documentation tool.

Preliminary plans around licensing are around creating a ConfigMgr Site, ConfigMgr hierarchy, Consultant/Consultancy firm license.

When does this beta Expire?

This beta version expires on the 15th december 2009. At which point a new version (Beta 1.5 of Beta 2) should be available.

What does SccmAutoDoc currently document?

SccmAutoDoc currently documents everything you see in the ConfigMgr Admin Console underneath the Site Settings node, with some small exceptions listed below:

  • Address schedule and Bandwidth limiting configuration.
  • Certificates node
  • Status Filter Rules

For a sample on what SccmAutoDoc documents have a look at SccmAutoDoc-1.125-Sample at:

http://scug.be/media/g/sccmautodoc/default.aspx

SccmAutodoc currently has no plans to document “volatile” data. In other words, packages, programs, advertisements, … Will Not be documented. It is determined that this data changes to often, which would require SccmAutoDoc to run several times a day. Additionally the documentation would then become quite large making it lose its purpose as a Site Configuraiton document.

What are some of the known issues so far with SccmAutoDoc?

SccmAutoDoc errors out if you open up a focus-capturing box in Word while the program tries to write data to the document.

How does SccmAutoDoc work?

SccmAutoDoc works by querying WMI and parsing the results to look like they appear in the ConfigMgr Admin console. The main engine behing SccmAutoDoc is the included XML file which lists the queries that are executed.

Installing the Service Manager WebPortal

6:38 pm in beta, Installation, SCSM, System Center Service Manager by Kenny Buntinx [MVP]

Hi All,

 

System center service manager beta 2 comes with a webportal to allow for:

  • It to end-user announcements (Send out infrastructure status updates: Eg: Mail functionality temporarily unavailable)
  • Self service end-user password (not implemented in this beta2, will require ilm v3)
  • End-user request for help allows a user to log an incident
  • End-user request software

Below are the steps to get the portal installed:

The portal is based on IIS, so you’ll first have to install IIS.

The webportal needs a default IIS setup, with the following 2 role services added.

  • Asp.Net (and all additional dependant features)
  • Windows authentication
  • IIS 6.0 Metabase compatibility

 

Once you have installed these prerequisites you can start the webportal installation.

First extract the smcdimage_Architecture  and subsequently launch setup.exe.

The window that opens allows you to start the webportal installation.

 

Step 1:

step01

Step 2:

step02

Step 3:

step03

Step 4:

step04

Step 5:

step05

Step 6:

step06

Step 7:

step07

Step 8:

step08

Step 9:

step09

 

That’s it in regards to the installation of the portal, for end-users to be able to use the portal they need to have the ActiveX Webportal client installed.

You can find the ActiveX component in the setup folder of the Cd Image for the architecture of the client systems, the file is called portalclient.msi.

Once all this is done, the only additional step you need is to request a certificate for your System center service manager(SCSM) webportal, but that is food for a next blog post.

Enjoy.

"Everyone is an expert at something"
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS
http://www.scug.be/blogs/sccm/default.aspx

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

How to monitor the hardware of an HP server when running VMWARE ESX in SCOM R2

12:25 pm in MOM, Operations Manager 2007, Opsmgr 2007, SCOM 2007, Virtual machine, Vmware by Kenny Buntinx [MVP]

I ran into a situation that a customer did not want to pay for an expensive management pack to monitor their ESX server Hardware . They all ran on HP Proliant hardware. Here is a small tutorial on how to integrate & configuring the Insight Manager Agents for VMware ESX Servers and let them report into System center Operations Manager 2007 R2

  1. Go to the HP website and search for HP Insight Manager Agents for VMware ESX Server 8.2.0
  2. Download the Agents
  3. Open WinSCP and upload the .tar file you just downloaded to a folder
  4. Log into putty with your root account
  5. Issue the following command to unzip the contents: tar -zxvf hpmgmt-8.2.0-vmware.tgz.
  6. Stop the pegasus services : “Service pagasus stop”
  7. Run “hpmgmt820preinstall.sh –install”
  8. Reboot
  9. Stop the pegasus services : “Service pagasus stop”
  10. Run “hpmgmt820install.sh – install”
  11. Follow the wizard, when asked for the public string enter (if you use this string) public 2 times (it will not be visible), and be sure to have the HP SIM server’s IP or FQDN. Always answer Y when asked to activate the port 2381 (HPMHP) & the Snmpd deamon.
  12. After the config you need to start the pegasus services : “Service pagasus start”
  13. To check if the configuration has succeeded, log in to the HP System Homepage https://<esx server>:2381/. You should see the servername on the right side.Log in with Root
  14. Check your snmpd.conf  at /etc/snmp/snmpd.conf . It should look like this :

———————————————————————————–

# Following entries were added by HP Insight Management Agents

dlmod cmaX /usr/lib/libcmaX.so

rwcommunity public 127.0.0.1

rocommunity public 127.0.0.1

rwcommunity  public <The FQDN name of your RMS server>

rocommunity public <The FQDN name of your RMS server>

trapcommunity public

trapsink <The FQDN name of your RMS server> public

syscontact root@localhost (edit snmpd.conf)

syslocation DATACENTER

# ———————- END ——————–

# Sample snmpd.conf containing VMware MIB module entries.

# This is a simple snmpd.conf that may help you test SNMP.

# It is not recommended for production use. Consult the

# snmpd.conf(5) man pages to set up a secure installation.

# VMware MIB modules. To enable/disable VMware MIB items

# add/remove the following entries.

dlmod SNMPESX            /usr/lib/vmware/snmp/libSNMPESX.so

———————————————————————————–

You are done on the ESX Level ! Now we move on to the SCOM R2 Level .

It is relatively simple to monitor the hardware status of your ProLiant servers with Operations Manager. HP  has a free management pack (HP ProLiant Management Pack for System Center Operations Manager 2007), that discovers and monitors them. However if your ProLiant servers happen to have a different OS than Windows installed, it will not not work without a hassle.

I was looking for a way to include the hardware status of our HP servers that ran VMware ESX 3.5 update 4  into OpsMgr. HP does provide a specifically adapted Management Agent for ESX (HP Management Agents for VMware ESX Server as described above ). That allows accessing hardware information about the server using SNMP queries.

On Raphael Burri’s blog you will find a custom written MP that will collaborate with the HP Management pack for Windows and let you monitor your HP hardware . Many thanks to him !!!!

  1. Download the custom made management pack from Raphael Burri on http://rburri.wordpress.com/2008/06/03/snmp-only-hp-proliant-hardware-management-pack/
  2. Download the official HP Management pack for HP Proliant Servers
  3. Install the SNMP stack on your RMS server
  4. Import the both Management packs in your RMS
  5. Configure the SNMP stack of the non-windows ProLiants to allow access from the OpsMgr server or gateway that is going to act as SNMP proxy.
  6. Discover the ProLiant servers as SNMP Network Devices
  7. You are done . Create your own views and rules as you want .

 

Hope it Helps ,

Kenny Buntinx