Here is the last screencast in my Desired Configuration Management (DCM) series. Today’s screencast covers “Authoring XML (XPath) Query Settings”.  Enjoy!

To view this screencast in other formats visit: http://technet.microsoft.com/en-us/edge/dcm-authoring-xml-xpath-query-settings.aspx

Here is the latest screencast in my Desired Configuration Management (DCM) series.  Today’s screencast covers “Authoring WQL (WMI) Query Settings”.  Enjoy!

To view this screencast in other formats visit: http://technet.microsoft.com/en-us/edge/dcm-authoring-wql-wmi-query-settings.aspx

Here is the latest in my screencast series covering Desired Configuration Management (DCM) series.  Today’s screencast covers “Authoring SQL Query Settings”.  Enjoy!

To view this screencast in other formats visit: http://technet.microsoft.com/en-us/edge/dcm-authoring-sql-query-settings.aspx

Here is the latest in my screencast series covering Desired Configuration Management (DCM) series.  Today’s screencast covers “Authoring Script Settings”.  Enjoy!

To view this screencast in other formats visit: http://technet.microsoft.com/en-us/edge/dcm-authoring-script-settings.aspx

One of the most common questions I’ve been asked is, “How do I remove SCUP updates from Configuration Manager?”.  The answer is fairly easy, you expire the update in SCUP and the re-publish it into WSUS.  Then on the next scheduled ConfigMgr/WSUS synchronization the update will be marked as expired in the ConfigMgr UI.  Finally after a few weeks the update will be removed from the UI (unless the update is part of a deployment package).

Now this process becomes a little more work if you have deleted the update in SCUP and have no way of getting it back.  One thing to remember is that the flow of data is one way, meaning it flows from SCUP to WSUS (through publishing) and from WSUS to ConfigMgr (through synchronization).  If you publish an update to WSUS and then delete it from SCUP (before expiring/republishing) then the update will become orphaned in ConfigMgr and there is no easy way to remove it.  If you are in this situation the below steps should help remove those orphaned updates.

1. The first thing you need to do is find the Update in the ConfigMgr UI that is orphaned as we need to find the Update ID. To display the Update ID in the UI you will need to add a new column for display.
   
   
   
   Add the “Update Classification” column to the Displayed columns list.
   
   
   
   Now find the orphaned update (probably by title) and note the Update ID
   
   
   
   
2. Once you have the UpdateID you now need to find the InstallableItem ID.  To do this you can browse to your WSUS Server’s “UpdateServicesPackages” share. The path is \\<wsus server>\UpdateServicesPackagess\[Update GUID]\[InstallableItem ID GUID]
   
   
   
   
3. Now that you have the UpdateID and InstallableItem ID you can re-create the update.  Open SCUP and create a new update with the same title and fill in the required fields.  For Installable/Installed Rules you can but in any rules as you are going to expire the update.  It does not really matter which rules you use.
4. Export this newly created update. 
5. Delete the new update from SCUP console, don’t worry we will re-import it in a few steps.
6. Export/Save the XML file from inside the <catalogname>.cab file for editing.
7. Open the XML file in an XML editor if you have one or notepad.  If you have an XML editor you can reformat the text for easier reading.
8. Modify the PackageID with your orphaned UpdateID and modify the InstallableItem ID with your orphaned InstallableItem ID and save the file.
   
   
   
   
9. CAB the file using the following command – “makecab <filename>.xml <filename>.cab”
10. Re-Import the update into SCUP.
11. Mark the update as Expired and flag the update for Publish.
12. Publish the update.
13. Verify in the %user%\updatespublisher.log that the update was expired.
    
    
    

There are a couple of things to remember with managing SCUP updates.  Before you delete an update in SCUP make sure you have no use for it in the future.  If the update was never published then deleting it is fine, however, if you have published it into WSUS/ConfigMgr then you will want to keep the update or expire it and re-publish before deleting it.

Here is the next screencast in my Desired Configuration Management (DCM) series.  Today’s topic covers “Authoring Registry Settings”.  Enjoy!

To view this screencast in other formats visit: http://technet.microsoft.com/en-us/edge/dcm-authoring-registry-settings.aspx

Here is the next screencast in my Desired Configuration Management (DCM) series.  Today’s topic is “Authoring IIS Metabase Settings”.

To view this screencast in other formats visit: http://technet.microsoft.com/en-us/edge/dcm-authoring-iis-metabase-settings.aspx

This configuration pack contains configuration items intended to manage your Exchange Server 2007 server roles. The settings contained in this configuration pack are based on the results of service engagements by the IT Operational Excellence Organization, a part of the Microsoft Services division. 

The Microsoft Exchange Server 2007 Operational Configuration Pack includes configuration items for the following:

• Client Access Server (CAS)
• Exchange Core
• Gateway
• Hub Transport
• Mailbox
• Unified Messaging

You can download here.

Here is the next screencast in my Desired Configuration Management (DCM) series.  Today’s topic is “Authoring Active Directory Query Settings”.

If you would like to learn more about Active Directory Queries visit our TechNet site here.

To view this screencast in other formats visit: http://technet.microsoft.com/en-us/edge/dcm-authoring-active-directory-query-settings.aspx

Here is the next screencast in my Desired Configuration Management (DCM) series.  Today’s topic is “Authoring Registry Key Objects”.

To view this screencast in other formats visit: http://technet.microsoft.com/en-us/edge/dcm-authoring-registry-key-objects.aspx