Monday, 11 May 2015

Documenting Task Sequences Automagically


Load PowerShell from the Configuration Manager Console
1. Start by launching the Configuration Manager console. In the upper left corner, there’s a blue rectangle. Click the white arrow in the blue rectangle, and choose “Connect via Windows PowerShell”.

Run This Command
(Get-CMTaskSequence | Where-Object {$_.Name -eq “<Name of the Task Sequence>”}).Sequence | Out-File J:YourFileName1.xml

Follow these Steps 
1. Copy this file to the same folder as your YourFileName1.xml.

3. Open your task sequence in your favourite text editor.

4. After the first line which should look something like this:

<?xml version="1.0"?> or <?xml version="1.0" encoding="utf-8"?>

enter the following as the second line:

<?xml-stylesheet type="text/xsl" href="tsDocumentorv2.xsl" mce_href="tsDocumentorv2.xsl"?>

5. Save your file and open it in Internet Explorer.


The XSL takes care of formatting, indents and sizing.

Wednesday, 6 May 2015

The software change returned error code 0x87D00324 (-2016410844)

The software change returned error code 0x87D00324 (-2016410844)


And the application will be marked as failed in software center.
You may get this error msg for various reasons. Basically the error msg is indicating that the installation is not successful.
Surprisingly if we check AppEnforce.log, it shows looking for exit code:0 which means the installation is successful.


So the application is installed successfully, however the software center showing the deployment as Failed with error code 0x87D00324 (-2016410844).

Now it is time to look at the specified detection rule. If we are using MSI GUID as a product detection rule, make sure that we have correct GUID in the detection clause.
Unfortunately the detection GUID clause is different than the actual installed product GUID. Hence the evaluation of product is failing so the configuration manager flagging the install as failed.


Once I corrected the GUID in detection rule updated the content. Run the machine Policy and Evaluation cycle. As soon as the machine received the new policy, the software center msg changed from Failed to Installed.


Thanks: http://blogs.technet.com/b/cmpfekevin/archive/2013/11/21/import-computer-does-not-show-up-in-collection.aspx