Don Hite at myITforum.com : ConfigMgr 2007

The Prerequisite Hotfix For Configuration Manager 2007 R3 Is Unavailable

dhite — Sat, 16 Oct 2010 13:50:58 GMT

MS KB977384 is required in order to install R3 so why is it unavailable? Is the website flooded, corrupted or it is just a Microsoft thing that we are slowly becoming accustomed to? At either rate I think that Microsoft should reevaluate their Rx releases and do a better job at distributing them. How much time would it take to add the hotfix to the download or maybe recompile the download to integrate it? Enquiring minds want to know.

Hotfix Request

The system is currently unavailable. Please try back later, or contact support if you want immediate assistance.http://support.microsoft.com/contactus/?ws=support

Last Review : October 16, 2010

The Configuration Manager 2007 Dashboard Download

dhite — Wed, 13 Oct 2010 15:56:15 GMT

The Configuration Manager 2007 Dashboard allows you to watch and track application and operating system deployments as well as security updates and site health status via a customizable internet web interface.

The dashboard requires Windows SharePoint Services and can be accessed from a workstation desktop without the Configuration Manager console.

The dashboard installs to the x:\Program Files\ConfigMgr Dashboard Framework and the x:\ProgramData\ConfigMgr Dashboard Framework directories.

The dashboard can be accessed via your web browser http://Server_Name:Port_Number and comes preconfigured with a handful of web parts to get you started and you don’t need to be a Sharepoint or MOSS expert to develop your own dashboard reports..

Download:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=27fe0d80-38c6-464a-953a-1c2edcf35c2d

Setting Configuration Manager Web Reports and R2 Reporting Services Display Options

dhite — Fri, 29 Jan 2010 21:05:43 GMT

Here you will find the steps necessary to set or configure ConfigMgr 2007 Web Reports or ConfigMgr 2007 R2 Reporting options to open the selected reports within the console or with Internet Explorer.

1. Open the Configuration Manager console "System Center Configuration Manager"

2. Right mouse click on your "Site Database (Site_Code – Server_Name, Description) and from the context menu select "Report Options"

3. Then select “Open reports in a new window”

Note: This configuration change is console specific meaning that if you make the change on the site server it will not be set on your workstation console. Simply follow the same steps above provided you upgraded your workstation console to ConfigMgr 2007 R2 to open the reports in Internet Explorer.

Tip: From the Report Options dialog box you can also find the ConfigMgr Web Reports web page link (URL) and copy and pasted the link into your Internet browser to access the reports from IE. You can also see the Report Server NetBIOS name as well as set options to “Use Reporting Services Reports for Admin console report links”.

For additional information select “Help” on the “Report Options” dialog box.

TechNet Magazine: SQL Server Reporting Services and SCCM

dhite — Thu, 28 Jan 2010 19:11:50 GMT

In the January 2010 Issue of TechNet Magazine Microsoft’s Steve Rachui has a great write up on System Center Configuration Manager: SQL Server Reporting Services and System Center Configuration Manager.

Check it out and drop by his blog page too.

SQL Server Reporting Services and System Center Configuration Manager

http://technet.microsoft.com/en-us/magazine/ee914611.aspx

Steve Rachui's Manageability blog - ConfigMgr/OpsMgr

http://blogs.msdn.com/steverac

Common SMS Log File Names

dhite — Wed, 23 Dec 2009 19:43:55 GMT

Provided here for your reference - and mine - is a list of the more common SMS log files with an easy to use description of each.

Client Component Installation Manager - Ccim

Client Configuration Manager - Ccm

Client Install Data Manager - Cidm

Collection Evaluator - Colleval

Component Status Summarizer - Compsumm

Courier Sender - Coursend

Courier Sender Confirmation - Cscnfsvc

Despooler - Despool

Discovery Data Manager - Ddm

Distribution Manager - Distmgr

Hardware Inventory Agent - Hinv

Hierarchy Manager - Hman

Hierarchy Manager - Sitecomp

Inbox Manager - Inboxmgr

Inbox Manager Assistant - Inboxast

Inventory Data Loader - Dataldr

Inventory Processor - Invproc

LAN Sender - Sender

License Metering - Licrsvc

License Server Manager - Licsvcfg

Network Discovery - Netdisc

Offer Manager - Offermgr

Offer Status Summarizer - Offersum

Replication Manager - Replmgr

Scheduler - Sched

Sender - Sender

Setup - SMSsetup

Site Component Manager - Sitecomp

Site Control Manager - Sitectrl

Site System Status Summarizer - Sitestat

SMS Administrator Provider - SMSprov

SMS Executive - SMSexec

SMS NT Logon Manager - NT_logon

SMS Provider - SMSprov

SMS SQL Monitor - SMSdbmon

SMS_Bootstrap Service - SMS_bootstrap

Software Inventory Agent - Sinv

Software Inventory Processor - Sinvproc

SQL Error Logs - Errorlog (Supports up yo .6)

Status Manager - Statmgr

Windows Networking Logon Discovery - NTlgdscm

Windows Networking Logon Installation - NTlginst

Windows NT Logon Discovery Agent - Ntlgdsca

Windows NT Logon Discovery Manager - Ntlgdscm

Windows NT Logon Server Manager - NT_logon

Windows NT Server Discovery Agent – Ntsvrdis

Desired Configuration Monitoring Log File Table

dhite — Mon, 22 Dec 2008 15:36:57 GMT

The table below will briefly describe the Desired Configuration Monitoring (DCM) log files and their purposes.

Log File	Description
DcmAgent	Provides information about assigned configuration baselines evaluations and desired configuration management processes.
CiAgent	Provides information about downloading, storing, and accessing assigned configuration baselines.
SdmAgent	Provides information about downloading, storing, and accessing configuration item content.
SdmDiscAgent	Provides high-level information about the evaluation process for objects and settings configured in the referenced configuration items.
Discovery	Provides detailed information about the Service Modeling Language (SML) processes.

Inside the Configuration Manager Remote Control Registry Hive

dhite — Sat, 06 Dec 2008 14:17:07 GMT

On your Configuration Manager Site server the remote control information is stored in the registry. Below you will find the available keys.

The information is stored in the “Hkey_Local_Machine\Software\Microsoft\SMS\Client” hive under “Client Components\Remote Control” and includes the following:

Access Level = dword value

Allow Client Change = dword value

Allow Takeover = dword value

Audible Signal = dword value

CommandLine = dword value

CompressionType = dword value

Control Level = dword value

Enabled = dword value

IndicatorType = dword value

Permission Required = dword value

PermittedViewers = hex value

System Tray Visible Signal = dword value

Use IDIS = dword value

Visible Signal = dword value

User information is stored under “User Settings” and includes the following:

Access Level = dword value

Allow Takeover = dword value

Audible Signal = dword value

Control Level = dword value

IndicatorType = dword value

Permission Required = dword value

Use Local Settings = dword value

Visible Signal = dword value

Note: You know what Microsoft says about dinking with the registry so I will spare you the warnings.

Common SMS And Configuration Manager Client Installation Issues

dhite — Mon, 17 Nov 2008 01:42:56 GMT

When troubleshooting client installation issues the log files on the client machine and the site server usually provide you with a clue as to what the issue is. It may at times seem cryptic but generally the logs will provide you with a direction to take when troubleshooting client installation issues.

It is important to note here that in order to install a client the resource needs to be discovered and assigned to the site. This is initiated by adding site boundaries and enabling and executing a network discovery to locate potential client resources before they can be installed.

On the potential client resource the machine must obviously have sufficient free disk space and have network connectivity in the domain and meet the minimum client requirements for SMS or ConfigMgr. For example a ConfigMgr SP 1 client machine must have at least the following at a minimum:

Windows 2000 Professional SP 4 Operating system or later.

350 MB Free disk space.

233-MHz Processor.

128 MB RAM.

Additionally the client must have File and Print Sharing enabled and you must be able to access to the ADMIN$ share on the machine and remote WMI access must be enabled. In most cases the firewall or the firewall restrictions are preventing WMI access and access to the site server files necessary to initiate and complete the client installation. You can configure the firewall to allow the necessary access or you can temporarily disable the firewall on the client to see if the installation will function as expected.

The site server and your domain infrastructure may also be preventing client Installation as well. On the site server make sure that you have an admin account for the Client Push Installation specified that has administrator rights on the client machines and try and determine that there are no name resolution issues in the domain.

ConfigMgr Branch DP Add Tool

dhite — Sun, 26 Oct 2008 19:31:52 GMT

BDPAdd is a tool that will bulk add protected branch distribution points to a ConfigMgr 2007 (SCCM) hierarchy. There is currently not a way, in the ConfigMgr console, to add multiple protected Branch distribution points at once. This tools attempts to address that problem.

Running the tool

BDPAdd.exe /s {central site server} /file {excel file} /log {path}

/s Central Site Server name.

/file Path to Excel files.

/log Log file path.

The input for this tool is an Excel 2003 spreadsheet and there are some requirements for the format of this spreadsheet. Review the example spreadsheet, bdpexample.xls, attached. Any deviation from this will either produce errors or unexpected results.

All output from this tool is written to the log file only. (The Trace utility from the ConfigMgr toolkit can be used to view the log)

BDPAdd 1.0 http://www.codeplex.com/bdpadd/Release/ProjectReleases.aspx?ReleaseId=14111

Additional Information

http://www.codeplex.com/bdpadd

Configuration Manager SQL Server Available Site Boundary Views

dhite — Sun, 19 Oct 2008 18:10:49 GMT

Provided here is a list of the SQL Views available for ConfigMgr 2007 to allow you to review your site(s) local and roaming boundaries information from SQL rather than viewing the Control file.

I have also listed the column names for each of the views as well for your reference and mine.

v_BoundaryInfo

Returns the BoundaryId, SiteCode, BoundaryType, Value, BoundaryFlags, DisplayName and Action

v_SiteBoundary_ADSite

Returns the SiteCode and ADSiteName

v_SiteBoundary_IPSubnet

Returns the SiteCode and IPSubnet

v_SiteRoamingBoundary_ADSite

Returns the SiteCode, ADSiteName, DownloadExecute and DisplayName

v_SiteRoamingBoundary_IPRange

Returns the SiteCode, StartingIP, EndingIP, DownloadExecute and the DisplayName

v_SiteRoamingBoundary_IPSubnet

Returns the SiteCode, IPSubnet, DownloadExecute and DisplayName

v_SiteRoamingBoundary_IPv6Prefix

Returns the SiteCode, IPv6Prefix, DownloadExecute and DisplayName

vSMS_CurrentBoundary

Returns the SiteCode, Value, BoundaryFlags, DisplayName and BoundaryType

Notes:

A DownloadExecute value of 0 is local and a value of 1 is remote.

The following simple SQL query syntax can be used to retrieve information form the views listed above: Select * From View_Name

The views v_SiteRoamingBoundary_IPv6Prefix and vSMS_CurrentBoundary are new to ConfigMgr 2007.

Upgrading Your ConfigMgr 2007 SQL 2005 Database Backend To SQL 2008

dhite — Sun, 05 Oct 2008 19:41:50 GMT

Provided here you will find the steps necessary to upgrade your ConfigMgr 2007 SQL Server 2005 backend to SQL Server 2008.

Note: This was tested on the following: Windows 2008 Enterprise Server Service Pack (SP) 1, ConfigMgr 2007 SP1 and SQL 2005 Server SP 2.

1. Apply the appropriate required hotfix below:

ConfigMgr 2007 RTM – No Service Pack

http://support.microsoft.com/kb/955229

ConfigMgr 2007 SP1

http://support.microsoft.com/kb/955262

2. Insert the SQL 2008 Server installation media and start Auto run if it does not start automatically or double click on Setup.Exe

3. Select “OK” at the Microsoft SQL Server 2008 Setup dialog box stating:

SQL Server 2008 setup requires Microsoft .NET Framework and an updated Windows Installer to be installed

To install these prerequisites and continue with Setup, click Ok. To exit Setup, click Cancel.

4. At this point the files will then be extracted and the Setup task process bar will start loading the installation components and may take several minutes to complete.

5. Next the Microsoft .NET Framework 3.5 SP1 Setup dialog box will appear. Review the license agreement and select ‘I have read and ACCEPT the terms of the License Agreement” and then select “Install” to begin.

6. The Download and Install Progress screen will appear and the install will begin and this process will take some time to install and can take from 5 to 15 minutes depending on your server speed and internet connectivity speed.

7. At the Setup Complete Microsoft .NET Framework 3.5 SP1 Setup dialog box stating: Microsoft .NET Framework 3.5 SP1 has been installed successfully select “Exit”

8. Reboot the server to finish installing the updates.

9. Log back onto the server and repeat step # 2 if necessary and allow several seconds for the SQL Server 2008 dialog box stating: Please wait while SQL Server 2008 Setup processes the current operation message disappears.

10. At the SQL Server Installation Center task list dialog box select “Installation” or select “Upgrade Documentation” for additional upgrade information.

11. From the Installation task pane select “Upgrade from SQL Server 2000 or SQL Server 2005” and wait for the message box in step # 9 to disappear.

12. At the SQL Sever 2008 Setup dialog box for the Setup Support Rules select “OK” to continue unless you have any “Failed” or “Warning” issues that need to be resolved. If this is the case leave the dialog box open and then correct the issues to resolve them and select “Re-run” to initiate the checks again.

13. After the message box in step # 9 disappears at the Product Key task leaf enter your product key in the space provided and select “Next” to continue.

14. At the License Terms task leaf review the license terms and select “I accept the License Terms” and then select “Next”

15. At the Setup Support Files task leaf select “Install” to begin the upgrade process which will take just a few minutes to complete.

16. After the message box in step # 9 disappears at the Setup Support Files dialog review the Setup Support Rules task leaf status for any “Failed” or “Warning” status messages and then select “Next” to continue.

17. At the Select Instance task leaf select “Next” to continue.

18. At the Select Features task leaf accept the defaults or change them as needed and then select “Next” to continue.

19. At the Instance Configuration task leaf select “Next” to continue.

20. At the Disk Space Requirements task leaf select “Next” to continue.

21. At the Server Configuration task leaf select “Next” to continue.

22. At the Full-Text Upgrade task leaf accept the default of “Import” or select “Rebuild” or “Reset” as needed and then select “Next” to continue.

23. At the Error and Usage Reporting task leaf select “Next” to continue.

24. After the Upgrade Rules task leaf completes select “Next” to continue.

25. At the Ready to Upgrade task leaf review your summary information or copy and paste the contents to a text file for later reference select “Upgrade” to start the upgrade process

26. The Upgrade Progress task leaf will then appear and will take quite some time to conclude up to an hour in some cases then select “Next” at the “Setup Process Compete” task pane.

27. At the Complete task leaf review the installation status and review the “Supplemental Information:” and then select “Close” to complete the install.

Notes:

When you choose to upgrade your SQL server to SQL 2008 the previous versions program group and files are not removed by design and you must uninstall the pervious version using Programs and Features to remove them

SQL 2008 is not backward compatible with SQL 2000 or SQL 2005 and as a result you must upgrade any workstations or servers to the new version to resolve any comparability issues.

To avoid having to compete the first few steps of the upgrade process above you can download and install Microsoft .NET Framework 3.5 SP1 and Windows Installer 4.5 before beginning the installation found below.

Microsoft .NET Framework 3.5 SP1

http://go.microsoft.com/fwlink/?LinkId=120550

Windows Installer 4.5

http://support.microsoft.com/KB/942288

ConfigMgr 2007 Component And Site System Status Available Hidden Columns

dhite — Sun, 28 Sep 2008 18:46:51 GMT

In ConfigMgr 2007 in the Site Status leaf the Component Status and the Site System Status leafs are provided for you to get a general overview of your site(s) current status. You can see or view the status of all the components or threads and the status for the site systems respectively in the results pane.

In the Component Status leaf there are two hidden columns that are not displayed by default that can be added and are the “Site Code” and the “Tally Interval”. For the Site System Status there are two available as well the “Object Type” and the “Site Code”. Follow the steps below to add the columns you wish to have displayed.

1. Select either the Component Status or the Site System Status leaf and right mouse click on it.

2. From the context menu select “View” and then select “Add/Remove Columns”.

3. From the Add/Remove Columns dialog box select the column(s) you want to add from the “Available columns” pane and click “Add” to add them and select “OK” when you are done.

Note: You can restore the defaults, move items up or down and even remove items from here as needed.

The newly added columns are now appended to the end of the pane and can be moved where needed by using the “Move Up” or “Move Down” buttons if you are not happy with the new view by repeating the steps above.

Tips: You can also add the “Site Name” and “Tally Interval” columns to the Site Status leaf as well following the steps above.

The following are also available for the Status Message Queries leaf: Comments, Expression, Limit To Collection Id, Query ID and Resource Class.

Configuration Manager Site Systems Daily Checks List

dhite — Sun, 21 Sep 2008 20:01:16 GMT

Provided here is a recommended minimum daily check list for tasks that should be performed each morning before your daily grind begins. This will ensure that your site(s) is running as expected and will keep you a step ahead of the game so that you can avoid any last minute lunch time surprises.

1. Check the “System Status” – “Site Status” leaf.

Examine the “Component Status” leaf and ensure that there are no components with a state other than “OK”.
Examine the Site “System Status” leaf and ensure that there are no components with a state other than “OK”.

SMS Web Report To Get Current Site Status

http://myitforum.com/cs2/blogs/dhite/archive/2007/08/12/sms-web-report-to-get-current-site-status.aspx

2. Check SMS_XXX\Inboxes for any file backlogs:

ConfigMgr 2007 Inboxes To Monitor

http://myitforum.com/cs2/blogs/dhite/archive/2008/06/08/configmgr-2007-inboxes-to-monitor.aspx

3. Check the SQL Server Error Log File.

Check the ERRORLOG file for any errors that may have been encountered.
Look of any Autogrow issues.
Examine the DBCC CHECKDB output for any errors.
Examine the Database Backup state.

4. Inspect the Site Servers Event Log.

Check the Application log file for any Errors.
Check the Security log file for any audits other than successful.
Check the System log file for any Errors.

5. Check Site server’s available free disk space.

VBS Script To Return Logical Disk Information For A List Of Machines

http://myitforum.com/cs2/blogs/dhite/archive/2007/07/29/vbs-script-to-return-logical-disk-information-for-a-list-of-machines.aspx

The Bernard White SMS Server Tools 0.2.2 Release

dhite — Sun, 07 Sep 2008 17:22:36 GMT

Bernard White’s SMS Server Tools version 0.2.2 was released on August 14 th 2008 and is available for download.

New Features

Distribution Point Mod Tool has new built-in scheduling functionality that allows an action to be to run at a latter date / time.

Site Information Tool now shows site components roles and which servers they are installed on for each site. Also the COLL_OUT.BOX has been added to the list of reported inboxes.

Package Information Tool now shows details on Distributions In-Transit when the "-s d" switch is used.

Site Services Tool now has a new "-restart" switch added, allowing a component to be stopped and then started again in a single command.

Collection Membership Tool added to SMS Server Tools suite. This tool allows system, user or group resources to be added to a collection's membership. It also features regular expression matching.

SMS Server Tools 0.2.2 Download:

http://community.netplantation.com/download.php?view.4

Using ConfigMgr 2007 To Capture Microsoft Windows Media Player Media Files

dhite — Sun, 24 Aug 2008 18:04:29 GMT

Software Inventory in ConfigMgr 2007 as well as in the previous versions - SMS 2.0 and SMS 2003 - can be harnessed to capture application executable (Exe) file extensions by default. However you can always add file extensions such as Outlook Personal Folder Files (PST) files, Initialization and Configuration Files (INI) files, WinRAR Compressed Archive (RAR) files and Compressed Archive (ZIP) files just to name a few to see what is installed on client resources in your infrastructure environment.

Any time you have clients with Microsoft Windows Media Player installed and they have access to the internet or removable media chances are that they will begin using the resources at their disposal even if it is frowned upon. Listening to music on your computer is not distractive or a big time waster and it is no different than listening to a radio in your office and neither one are uncommon today. Watching movies like Juno or watching the antics of Harold and Kumar the other hand can be disruptive and a time waster when employees are on the clock.

From an infrastructure standpoint both music and movies can affect the environment especially where shared resources such as users home shares and departmental shares are concerned. The problem is not so much that the employees are wasting time and are not being as productive as they should be. The real problem is that users seem to have the need to keep and store their digital media on their local machines or on shared resources and therein lays the problem. This can even cost the company money when they have to expand the disk space or buy additional disks when the resource run low or out of physical disk space.

To find machines and users that are storing Windows Media Player media files on shares or their local machines use the chart below and add the file type file extensions to your Software Inventory Client Agent Inventory Collection.

Microsoft Windows Media Player File Extensions

File Extension	Description
AIF	Audio Interchange File Format
AIFC	Audio Interchange File Format
AIFF	Audio Interchange File Format
AVI	Audio Visual Interleave
CDA	CD Audio Track
DRV-MS	Microsoft Digital Video Recording
IVF	Indeo Video Technology
M3U	M3U
MOV	QuickTime Content
MP2	MPEG Audio Layer II
MP3	MPEG Audio Layer III
MP4	MPEG-4
MPA	MPEG Audio Layer II
QT	QuickTime content
RA	RealNetworks content
RAM	RealNetworks content
WAV	Audio for Windows
WAX	Windows Media Audio Redirector
WM	Windows Media Video
WMA	Windows Media Audio
WMD	Windows Media Download Package
WMV	Windows Media Video
WMX	Windows Media Redirector
WPL	Windows Media Player Playlist
WVX	Windows Media Video Redirector

Additional File Type And Extension Information:

File Type	File Extension
Audio Interchange File Format (AIFF) audio files	.aif, .aifc, and .aiff
CD audio disc	.cda
DVD-Video disc	.vob
JPEG picture file	.jpg
Macromedia Flash animation file	.swf
Microsoft Recorded TV Show	.dvr-ms
MP3 audio files	.mp3 and .m3u
MPEG video files	.mpeg, .mpg, .m1v, .mp2, .mpa, .mpe, .mp2v, and .mpv2
Musical Instrument Digital Interface (MIDI) audio files	.mid, .midi, and .rmi
Windows audio and video files	.avi and .wav
Windows Media audio and video files	.asf, .asx, .wax, .wm, .wma, .wmd, .wmp, .wmv, .wmx, .wpl, and .wvx
Windows Media Player skin file	.wmz