The All TECHNICAL Blog

SharePoint Asset Inventory Tool Discontinued

The SharePoint Asset Inventory Tool has been discontinued. The Solution Accelerator team makes guidance and tools in the whitespace between products. Sometimes we are asked to move over, as a product team expands their capabilities into space once occupied by Solution Accelerators alone. Such is the case with SharePoint, where new administrative capabilities are being built all the time.

Watch the SharePoint TechCenter for updates on new tools: http://technet.microsoft.com/en-us/office/sharepointserver/default.aspx

SharePoint Asset Inventory Tool - Beta NOW Available!

Errors with Microsoft Deployment RC1

Known Issues with Microsoft Deployment RC1 – October 25, 2007

The development team has isolated three known issues in the initial Microsoft Deployment RC1 build and created a documented workaround to continue testing. An error will occur when running Configure ConfigMgr Integration, Configure Management Pack or Configure WDS PXE Filter.  The error occurs because two files were not properly signed in the Microsoft Deployment RC1 release.  We will be releasing an updated build and updated files within the next 24 hours.

If you would like to work around the issue.  You can follow the following steps:

1. Click on Start > All Programs > Accessories > Command Prompt, and then select  Run as Administrator (if on Vista).
2. You may see the screen grey and a 'User Account Control' dialog box appear. If this happens, click Continue so that the command prompt starts.

Obtain a copy of sn.exe, which is installed with Visual Studio 2005, and the .NET Framework 2.0 SDK. This executable may already be found on the host computer using the platform-specific commands below.

32-bit computer:
"<path_to_sn>\sn.exe" -Vr *,31bf3856ad364e35

64-bit computer:
"<path_to_sn>\sn.exe" -Vr *,31bf3856ad364e35

If it is not on the host computer, you can download .NET Framework 2.0 SDK to obtain it. The x86 version of the Software development kit can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=FE6F2099-B7B4-4F47-A244-C96D69C35DEC. The x64 version of the SDK can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=1AEF6FCE-6E06-4B66-AFE4-9AAD3C835D3D<

This should only be used as a temporary workaround until the updated files are posted, as this may weaken the security of your system.  Once we have released the updated files you will need to run sn.exe -Vx to re-enable Strong Name validation.

Thank you for your patience and your diligence in testing Microsoft Deployment.

Microsoft Deployment RC1 Now Available!

Microsoft Deployment is available as an open beta download.

Join the Microsoft Deployment Connection program on Microsoft Connect.

If you are already registered for the program, click here.

If you have not previously registered with Microsoft Connect, you might be required to register before you continue with the invitation process.

Moved on Business Desktop Deployment team

Hello folks,

Now, with DCM done, I have moved on to the Deployment team that released BDD 2007 in the recent past. I know you are no stranger when it comes to Client and Server deployment. So you will find me writing on Deployment 4 Solution Accelerator pretty soon...

Keep visiting!

Thanks,

Sai Kodi

DCM Solution Troubleshooting Steps

Here are some troubleshooting steps that you might want to perform for a successful DCM deployment / execution:

1. Install DCM Solution and ensure that all the files were deployed and the DCM Solution database created.
1. Create an SMS package / program and advertise it to any of the client machines.
2. Ensure that the client machines received the advertisement and executed the DCMCmd.exe program?
3. Check for any errors / failures during the DCMCmd.exe execution on any of the client machines? You can check this by looking at the Event Log of the Client Machine or by looking in the same folder where the advertisement was downloaded to on the client machine.
4. Ensure that you extended the SMS def.mof file by executing the Extend SMS def.mof vbscript file on the SMS Site server?
5. Ensure that Hardware Inventory happened?
6. Check for DCM related data in the Resource Explorer for each of the client machines where the advertisement was targeted to? The DCM related tables / views are created on the SMS Site Server database automatically after a successful Hardware Inventory. The installation of the DCM Solution.msi does not alter the SMS database in any respect.
7. Check if the DCM DTS packages have executed successfully.

Thanks,
Sai Kodi

DCM File System Data Source Properties

Hello,

I have got several requests regarding the File System data source properties and what they mean. Hence I decided to post the info in here... Here you go...

 File System Data Source Properties:

Name -> name for the data source

Absolute Path -> the absolute path to the file or folder

File Search Pattern -> what types of files to search for. Eg *.doc would search for doc files. This is applicable when scanning for files

Scope -> Three possible values: Base (look at the exact folder specified by the absolute path), OneLevel (look one level down from the specified absolute path) and Subtree (look down the complete tree from the specified absolute path)

Retrieval Type -> Three possible values: Files (retrieve only files), Directories (retrieve only folders) and All (retrieve both files and folders)

Comment -> comment for your purposes.

Thanks,

Sai Kodi

DCM v 2.0 Download Updated

Overview

Microsoft Systems Management Server (SMS) 2003 Desired Configuration Monitoring (DCM) 2.0 now supports configuration monitoring of desktops and servers. The accelerator allows the user to define desired hardware, operating system, and application configuration settings in multiple configuration data sources. Then, using the supplied auditing engine, DCM compares desired settings with actual settings and finally reports configuration compliance.

DCM 2.0 includes a redesigned user interface (UI) to reduce the time needed for defining Configuration Items. The new user interface supports complex rule definition with the Advanced View and adds a wizard-based simplified UI for defining simple rules as the Standard View. The new UI also includes common rule templates and enables users to define common rules specific to their organizations. In addition, CI rules can now be viewed and edited in a table view.

Notes

DCM 2.0 was updated and re-released on October 25, 2006, to address a known issue when parsing complex XPath query expressions generated using DCM 1.0. See the updated Release Notes for more details. If you have experienced any problems with DCM 2.0 rendering query expressions defined in DCM 1.0, I encourage you to download this updated version. Please see the updated Release Notes for more details.

Choose the SMS_DCM2.0_for_DotNet1.1.zip download package if you are using .NET Framework 1.1. Choose the SMS_DCM2.0_for_DotNet2.0.zip download package if you are using .NET Framework 2.0. With either DCM package, you also should download the Configuration_Items.zip and SMS_Reports.zip packages. You can select the files you want to download from the list on this page.

Send questions or feedback to us directly at CISfdbk@microsoft.com.

DCMSolution Database not created during installation

There was a known issue in Desired Configuration Monitoring (DCM) Solution Accelerator v 1.0 where the DCMSolution database was not created during installation in specific cases. The issue occurred because the v 1.0 installer retrieved SQL information from a different registry path. However it happens only when the default data / log file locations is altered after SQL Server is installed.

This issue has been fixed in the DCM v 2.0 releases. I am outlining how DCM installer detects the data / log folders for creating the DCMSolution database.

For SQL Server Default Instance:

1. The DCMSolution installer first retrieves the value of "DefaultData" under the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer". If it exists and is not blank, it goes with this path. This value is populated if you alter the data / log file locations after the SQL Server was installed.
2. If the “DefaultData” value is blank, then it gets the value of "SQLPath" under the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup". This is the default SQL location that you provide at the time of installing SQL Server.

For SQL Server Named Instance:

1. The DCMSolution installer first retrieves the value of "DefaultData" under the registry key " HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceName>\MSSQLServer". If it exists and is not blank, it goes with this path. This value is populated if you alter the data / log file locations after the SQL Server was installed.
2. If the DefaultData value is blank, then it gets the value of "SQLPath" under the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceName>\Setup". This is the default SQL location that you provide at the time of installing SQL Server.

The above is true for SQL Server 2000 SP3 and above. If you are facing a problem where the DCMSolution database is not being created at install time, you should check these registry locations and verify that the physical paths pointed to by these registry values exist on the physical server. Let me know if you have further questions.

Thanks,

Sai Kodi

XMLToDCMTransfer DTS package requires 3 mandatory files for proper execution

In DCM v 2.0, the functionality of the XMLToDCMTransfer DTS package has been altered. In the current version (v 2.0), the DTS package requires the following three files to be present in the DCM UI folder for successful execution:

• DCM.xsd
• DCMXMLValidator.exe
• <machinename>_Mapping.xml (at least one mapping file is required)

The DCM.xsd and DCMXMLValidator.exe are deployed when the DCM Author component is selected at the time of installation. The mapping file is created when you save a DCM CI using the DCM Authoring Tool.

If you do not have the DCM UI folder and any of these three files in the DCM UI folder (because you did not select DCM Author component during installation), then you should create the DCM UI folder manually and copy the required files to the folder before attempting to execute the XMLToDCMTransfer DTS package.

Feel free to post any appropriate questions.

Thanks,

Sai Kodi

Now Available: SMS 2003 Desired Configuration Monitoring Version 2.0

DCM v2.0 automates the configuration management audits between desired or defined configuration settings and actual configuration settings. DCM accomplishes this by allowing the user to define desired hardware, operating system and application configuration settings in multiple configuration data sources and then using the supplied auditing engine, DCM compares desired settings with actual settings and then reports configuration compliance. SMS 2003 Desired Configuration Monitoring (DCM) Version 2.0 now supports configuration monitoring of desktops and servers.

New 3rd Party Offerings for DCM

Alpha Tech Solutions has recently released training for SMS 2003 DCM and they also offer an automatic rule generator to help create configuration manifests. I have not yet used or tested the rule generator tool, but I have seen the training and it combines useful audio and video instruction across multiple scenarios for using the DCM solution.

Below are quotes from the Alpha Tech Solutions website (http://www.alpha-tech-solutions.com).

1. Desired Configuration Monitoring Training

Alpha Tech Solutions computer based training provides you with in-depth step by step instructions on solutions, concepts and best practices that are supported by Alpha Tech leading edge solutions. … 

The SMS 2003 Desired Configuration Monitoring Training will take you though the installation and deployment of the solution and provide you with valuable knowledge on how to create configuration manifests. Included in the training are real world scenarios and samples that you can use for configuration monitoring.

2. ATS Rule Generator

This time saving solution allows you to generate rules for configuration settings in a DCM configuration manifest by capturing them from a given “ideal” machine. The ATS Rule Generator will create configuration rules on the fly for any xml file generated by Microsoft’s Desired Configuration Monitoring Product.

--

In April, Configuresoft also released “ECM Management Extensions for DCM.”

Below is a quote from the Configuresoft website (http://www.configuresoft.com/Products/dcm.aspx).

Compliance expertise for Microsoft management frameworks

Enterprise Configuration Manager Management Extensions for DCM (ECMMX) allow Microsoft® SMS users to quickly and easily monitor and manage system compliance for both Windows and non-Windows platforms from a familiar interface. Working in partnership with Microsoft to extend the System Center management framework, Configuresoft provides compliance reporting and control for heterogeneous environments. ECMMX seamlessly integrates with existing Windows® server management tools, making extensive compliance information visible and instantly available. ECM prioritizes and continuously validates the state of system compliance via its Compliance Toolkits, which feature rule-based templates, reports and dashboards that plug into ECM.

Sample DCM Manifests Available!

Visit http://connect.microsoft.com to register for the DCM Configuration Manifest Beta program! This program has been established to test and validate sample configuration files for Microsoft Internet Security and Acceleration Server 2004, Microsoft Windows Server 2003 and Microsoft Exchange Server 2003. These manifests will help get you started with the DCM solution and save time in creating the initial configuration manifests required to use the DCM solution in your environment. Each manifest can be edited by the DCM authoring tool to meet your specific needs. Visit Microsoft Connect and register today!

Thanks!

Windows Server Deployment Automation Survey

The Solutions for Infrastructure and Management team in the Core Infrastructure Solutions group wants to better understand customer needs around installation and configuration for Longhorn server deployment. We would appreciate it if you would complete a short survey on this topic. Your feedback will be a critical factor in the design of the solution.   http://connect.microsoft.com

The Role of DTS packages in DCM Solution

The Desired Configuration Monitoring Solution Accelerator (DCM Solution) comes with two DTS Packages: SMSToDCMTransfer and XMLToDCMTransfer. The reports are rendered based on data available in the DCMSolution database. The two DTS Packages transfer data from the SMS Database and the XML mapping file respectively to the DCM Solution database.

·        SMSToDCMTransfer

The SMSToDCMTransfer DTS package transfers the data from the SMS database to the DCM Solution database. This DTS package is scheduled to run every 8 hours.

·        XMLToDCMTransfer

The XMLToDCMTransfer DTS package transfers data from the servername_mapping.xml file to the DCM Solution database. Before running the XMLToDCMTransfer DTS package, the servername_mapping file needs to be copied from the DCM UI folder (where the UI is installed) to the DCM installation folder. Usually the DCM installation folder is c:\Program Files\Microsoft\DCM Solution (unless changed during installation). The servername_mapping.xml file is created in the DCM UI folder. After the xml file is copied to the installation location, XMLToDCMTransfer DTS package can be executed. If the servername_mapping.xml file is not found at the location (installation folder), the DTS package continues execution and does not complain. Whenever DCM Author UI saves a manifest, the manifest details are written to the servername_mapping.xml file located in the DCM UI folder.

Thanks!