At a few sites I have experienced a problem where none of the Power Management charts will show in the canned SQL Reporting Services reports. Everything looks like fine from the client side, power management is part of the inventory and data is being send correctly back to the Management Point. Yesterday evening I found the solution the Technet forums (credit goes to Paul024). The solution In order to fix the problem, log on to the SQL Reporting Services point and run Dunsetup.exe (found in Configuration Manager install dir\Bin\I386\) The report after running Dunsetup.exe

The new name for Configuration Manager has been announced at TechEd Berlin, more info http://scug.dk/blogs/configurationmanager/archive/2010/11/09/configmgr-v-next-is-changing-name-to-configmgr-2012.aspx

Configuration Manager will by default utilize the standard SQL ports when accessing the database. If you have configured the SQL server to use a non-standard port you will need to configure a SQL failure to do so will result in a non-working Management Point and WDS. The error: In the MPcontrol.log file you will see that the Management Point is unable to connect to the database. Attempting to connect to the configured SQL database.  $$<SMS_MP_CONTROL_MANAGER><Fri Oct 08 07:53:58.211 2010 Coordinated Universal Time><thread=2772 (0xAD4)> *** [08001][11][Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.  $$<SMS_MP_CONTROL_MANAGER><Fri Oct 08 07:59:00.227 2010 Coordinated [...]

According to this post from http://blogs.technet.com/b/systemcenter/archive/2010/10/14/system-center-configuration-manager-2007-r3-unleashed.aspx from the System center team R3 will be available to download today 02:00 PM :-)

I had a problem with my PSP (PXE Service Point) on a Windows 2008 R2 box. Every time I restarted the server the service wouldn’t start (Which is not good). The error only happens when I add the PXE Service Point role in the Configuration Manager console, without the role my WDS service is starting like a charm. The errors in the event viewer First error An error occurred while trying to initialize provider SMSPXE loaded from C:\Windows\SysWOW64\CCM\x64\smspxe.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x4005 Source: WDSPXE Second Error [...]

In this post I will explain how you can integrate SCUPdates from Shavlik from A to Z. I’ll focus the post on these topics. Installation of the product Richness of the update catalog Configuration Manager integration Approving Updates Deploying Updates Reporting How to get started Installation of the product SCUPdates requires that you have installed and configured Microsoft System Center Updates Publisher (SCUP). In my test lab I already use SCUP to monitor and deploy updates from different hardware vendors like HP and Dell. For those of you who hasn’t yet played with SCUP I strongly advise you to have [...]

In the following weeks I will blog about the some of the different 3rd. party software update solution we can integrate with Configuration Manager. I will focus my articles on: Installation of the product Richness of the update catalog Configuration Manager integration Approving Updates Deploying Updates Reporting How to get started First I will test drive Secunia, a world-leading provider of Vulnerability Intelligence. Secunia has been around since 2002 and is most known for its award winning product CSI - Corporate Software Inspector. The installation Secunia requires a few components that are all easy to install and configure: The CSI [...]

Just downloaded a few HP Bios updates with ConfigMgr 2007 and SCUP 4.5 today. Being an old football player I have often heard from my coach that I should “give 100%”. In my world 100% is pretty much but apparently not when you are downloading HP updates. 220 percent - not bad :-)

A new version of ConfigMgr. 2007 toolkit is released, more info http://scug.dk/blogs/configurationmanager/archive/2010/04/30/new-version-of-the-configmgr-2007-toolkit.aspx