You are browsing the archive for 2009 September.

SCCM 2007 Reporting : How to change the Maximum Rows Returned in the Values List that is default set to 1000 rows

1:34 pm in AdminUi, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, Reporting, sccm, SCCM 2007, SCCM 2007 R2 by Kenny Buntinx [MVP]

Report Viewer in Configuration Manager 2007 limits the number of rows returned to 1,000 rows when you click Values and the values list displays for a prompt. The maximum number of rows returned by the query for the prompt that populates the values list can be modified by creating a registry key and setting a value on site system computers that have the reporting point role.

IMPORTANT : Increasing the maximum number of rows for queries that return a large amount of data or for queries that are inefficiently written might cause performance issues when the values are displayed.

To do this and configure the number of rows returned in a values list

  1. Open the Registry Editor on the reporting point computer.

  2. On reporting points that run on a 32-bit operating system, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Reporting.

    On reporting points that run on a 64-bit operating system, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Reporting.

  3. Create a DWORD value named Values Rowcount, and then set its value to the number of rows that you want returned in the report query. If you want to return all rows, set the value to 0xffffffff, which is the hexadecimal equivalent of –1.

    The configured number of rows is returned by any prompt query that is run from this reporting point.

 

Hope it helps ,

Kenny Buntinx

SCUG Technet Session What’s new in SCCM SP2

5:30 pm in Uncategorized by Kenny Buntinx [MVP]

Abstract : What’s new in System Center Configuration Manager 2007 SP2 Session Discription : This session will talk about some of the improvements and new features that will be made available in Systems Center Configuration Manager 2007 SP2.We will talk about the difference between SCCM 2007 SP1 and SP2 and why this service pack is so important as Windows 7 and Windows Server 2008 R2 is infront of our doorstep.

 

Download the presentation at http://scug.be/media/p/1260.aspx

 

Hope it Helps ,

Kenny Buntinx

Adding WMIC right-click actions to the ConfigMgr 2007 admin console (2)

1:32 pm in AdminUi, ConfigMgr, ConfigMgr 2007, sccm, SCCM 2007 by Kenny Buntinx [MVP]

Hi All,

 

In Post 1 of this topic we looked at the different WMI-command line actions you could trigger on a SCCM 2007 client.

In this post we’ll use that knowledge together with the knowledge of extending the admin console with custom actions series I did a couple of months ago to add these actions to our console.

Customize the sccm admin console – deep dive 1: http://scug.be/blogs/sccm/archive/2008/08/04/customize-the-sccm-2007-console-deep-dive-1.aspx

Customize the sccm admin console – deep dive 2: http://scug.be/blogs/sccm/archive/2008/08/04/customize-the-sccm-2007-console-deep-dive-2.aspx

Customize the sccm admin console – deep dive 3: http://scug.be/blogs/sccm/archive/2008/08/04/customize-the-sccm-2007-console-deep-dive-3.aspx

 

In the first post of the admin console deep dive session you learned how to create an xml to add custom actions. The example xml at that time looked like this.

Notepad Example Action XML

<ActionDescription Class="Executable" DisplayName="Make a Note" MnemonicDisplayName="Note" Description = "Make a note about software updates">
      <Executable>
           <FilePath>Notepad.exe</FilePath>
           <Parameters>C:\MyConfigurationManagerNote.txt</Parameters>
      </Executable>
</ActionDescription>

As you can see this example launched notepad as an executable. Given our new wmic commandlines we could replace that xml with the following to add a trigger hardware inventory action.

WMIC Action XML – Initial attempt

<ActionDescription Class="Executable" DisplayName="Trigger hardware inventory" MnemonicDisplayName="Trigger Hardware inventory" Description = "Trigger Hardware inventory">
      <Executable>
           <FilePath>WMIC</FilePath>
           <Parameters>/node:computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000001}"</Parameters>
      </Executable>
</ActionDescription>

 

Although this WMIC XML might look good at first glance, there is still a problem with passing the parameters, more specifically the section /node:Computername should have Computername replaced with the actual computername from the console where we intended to initiate this action. That’ is were the ##SUB## parameters come into play.

When you execute any action in the console, some specific paramaters are passed on in the following syntax: ##SUB:Parametername##, which parameters are available depends on the location you execute the action from in the ConfigMgr Admin console. For our purposes the most important thing is that the Name parameter is passed on when you click a resource in the details pane of a collection. With that knowledge, our WMIC Action XML should actually become:

 

<ActionDescription Class="Executable" DisplayName="Trigger hardware inventory" MnemonicDisplayName="Trigger Hardware inventory" Description = "Trigger Hardware inventory">
      <Executable>
           <FilePath>WMIC</FilePath>
           <Parameters>/node:##SUB:Name## /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000001}"</Parameters>
      </Executable>
</ActionDescription>

Note that the Computername has been replaced by ##SUB:Name## which will dynamically be resolved to the name of the resource you right-clicked on to launch the action.

 

Final step – Add the action to the console

To actually make the action appear in the console, we need to copy the above xml into  the folder with the right guid underneath:

Program Files\Microsoft Configuration Manager\AdminUI\XmlStorage\Extensions\Actions

For our specific purposes we want the action to appear when we right-click a computer system inside a collection, which corresponds to guid:

7ba8bf44-2344-4035-bdb4-16630291dcf6

So just create the folder Program Files\Microsoft Configuration Manager\AdminUI\XmlStorage\Extensions\Actions\7ba8bf44-2344-4035-bdb4-16630291dcf6 copy the WMIC xml inside the folder and restart the ConfigMgr Admin console.

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

Adding WMIC right-click actions to the ConfigMgr 2007 admin console (1)

8:51 am in AdminUi, ConfigMgr, ConfigMgr 2007, configmgr2007, sccm, SCCM 2007, sccm2007 by Kenny Buntinx [MVP]

Hi All,

I previously blogged about customizing the sccm admin console using the right-click actions and blogged about how you can customize the console yourself using the correct guid and a fairly easy to construct xml.

Most of these extensions use some form of vbscript to trigger these actions, but if you are not a great scripter, don’t despair you can achieve quite a lot of these tasks using a single command line. The following 2 links give you a decent overview of what is achievable using wmic:

Specifically for ConfigMgr the following command lines are interesting from my point of view:

  • Trigger hardware inventory: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000001}”
  • Trigger software inventory: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000002}”
  • Trigger data discovery: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000003}”
  • Trigger machine policy assignment request: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000021}”
  • Trigger machine policy evaluation: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000022}”
  • Trigger Refresh default management point: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000023}”
  • Trigger Refresh location (Ad site, or subnet): WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000024}”
  • Trigger Software metering usage reporting: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000031}”
  • Trigger sourcelist update cycle: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000032}”
  • Refresh proxy manamgement point: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000037}”
  • Trigger cleanup policy: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000040}”
  • Trigger validate assignments: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000042}”
  • Trigger certificate maintenance: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000051}”
  • Trigger branch dp scheduled maintenance: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000061}”
  • Trigger branchdp provisioning status reporting: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000062}”
  • Trigger software update deployment: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000108}”
  • Trigger state message upload: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000111}”
  • Trigger state message cache cleanup: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000112}”
  • Trigger sofware update scan: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000113}”
  • Trigger software update deployment re-eval: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000114}”
  • Trigger OOBS discovery: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000120}”

And some more general ones:

  • reboot computer: wmic /node:computername os Where (name like ‘%windows%’) call reboot
  • shutdown computer: wmic /node:computername os Where (name like ‘%windows%’) call shutdown

 

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

SCCM AMT Provisioning Flowcharts by Steve Rachui

6:58 pm in Uncategorized by Kenny Buntinx [MVP]

Have you ever wanted to learn more about how Active Management Technology (AMT) and System Center Configuration Manager 2007 work together?  Steve Rachui posted some great flowcharts that should help explain how all the pieces fit together .

See on his blog for more information : http://blogs.msdn.com/steverac/archive/2009/09/02/sccm-amt-provisioning-flowcharts.aspx

Hope it Helps ,

Kenny Buntinx

System Center Configuration Manager 2007 R3 on his way ! Register for TAP nomination.

6:51 pm in Uncategorized by Kenny Buntinx [MVP]

Today, the System Center team is excited to share with you our plan to release System Center Configuration Manager 2007 R3.  This new release of the ConfigMgr is packed with some extremely cool features, which over the coming months we plan to share with you in different ways. 

There are a few areas of focus for ConfigMgr R3, with the main engineering effort concentrating on Power Management.  Here are the goals for this feature:

Power Management
The goal of this capability is to enable Configuration Manager to further reduce the operational costs of IT by providing basic power management features native to the product.  Our approach is based on 3 primary areas:

A. Help the organization plan a power strategy by monitoring current power state and consumptions and reporting on machine utilization trends, current power settings and current energy consumption

B. Enable the Administrator to easily create, deploy and enforce specific power settings using the existing ConfigMgr infrastructure 
   −Ability to set peak and non-peak schedules
   −Ability to remediate settings if changed
   −Ability to opt out machines from power policy

C. Provide the business meaningful report formats that are relevant to Power Management

An effective approach to power management needs to maximize power policy deployment while minimizing the impact to the end-user. System Center Configuration Manager helps customers further reduce their operational costs by adding new in box capability to their ConfigMgr infrastructure, and by seamlessly enabling power management client agent services to their existing Collection landscape.

 

Read the whole story on http://blogs.technet.com/systemcenter/archive/2009/09/08/announcing-system-center-configuration-manager-2007-r3.aspx

 

Hope it helps ,

 

Kenny Buntinx

SMS to ConfigMgr 2007 secondary child site upgrade & Mplist issue

8:33 am in ConfigMgr, ConfigMgr 2007, configmgr2007, migration, sccm, SCCM 2007, sccm2007 by Kenny Buntinx [MVP]

Hi All,

 

During an SMS 2003 to System Center COnfiguration Manager 2007 upgrade recently I ran into the same issue described here:

http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/0d15a643-99e1-4b5f-9060-810fd89c68f4

After some investigation this seems to be “normal”. There seems to be an issue where the mplist procedure reports an error if the capabilities field for a site is empty in the database.

There are several things you can do to see whether this is the issue that is impacting you:

If you are seeing symptoms where the mplist url fails, whereas mplist1 and mpcert work fine, than this is a pretty strong indicator you are suffering from the above issue.

There are a several queries you can execute against the SMS database to confirm your suspicionn, if any of the below queries show an empty capabilities field for a ConfigMgr site than your suspicion is confirmed :

  • exec mp_getmplistforsite ‘sitecode
  • Select * from sites
  • exec mp_getlistofmpsinsite ‘sitecode‘,’0′

Result of this issue is that the mpcontrol.log will start spewing out errors as the mp uses the mplist url for its health check. All other functions of the mp seem to be operations, so inventory, software distribution, etc… seem not to be impacted.

There seems to be one situation where this always occurs, namely during in-place upgrades of secondary child sites. From the minute you start the upgrade until the upgrade successfully finishes mplist for all mp’s attached to the same primary site will fail.

The reason I uncovered this error is that one of the secondary site upgrades failed because of lack of diskspace, and hence the period in which the mplist url was unavailable was severely increased. Once the secondary site upgrade issue was fixed, the mplist url returned back to full working order without any other intervention.

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

Configuration Manager 2007 Service Pack 2 Release Candidate is available

5:30 am in Uncategorized by Kenny Buntinx [MVP]

The System Center Configuration Manager team has announced that the Configuration Manager 2007 Service Pack 2 Release Candidate

has been released on https://connect.microsoft.com and available for download.

Regards,

Kenny

Technet Events

7:28 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, events, live Meetings by Kenny Buntinx [MVP]

In the comming weeks Microsoft Belgium is hosting some very interesting Technet events.

Full details can be found on the links below :

Dutch Live Meetings :

French Live Meetings :

 

 

Have Fun,

Alexandre Verkinderen