best practices

Some light reading for the bus ride home:

Download Whitepaper on Top 10 Best Practices on Windows 10 OSD with SCCM ConfigMgr

Re: Install Application Step fails in Task Sequence

Great blog post about a similar issue we were having in production.

Instances where application will not install after a reboot. Even when the logs say they installed correctly. We found this was more likely to happen on devices with SSD compared to SATA drives.

Looks like a know bug, but nothing a sleep command can solve: http://www.bctechnet.com/install-application-step-fails-in-task-sequence/

MDT Installing Office 365 – Check license and the correct Product ID

Always good to make sure you have the correct Product ID in you configuration file when installing Office 365. An easy way to do this is to check you license in the Office 365 Portal.

  1. Login to the Office 365 Admin Center and click Billing then Licenses.
    Capture
  2. Then go to the TechNet page: Product IDs that are supported by the Office Deployment Tool for Click-to-Run
  3. The page lists all the Product IDs that are supported by the Microsoft Office Deployment Tool for Click-to-Run
    Capture
  4. Ensure you select the right one when downloading and install the appropriate Office application.
    In my example I would use:

    <Product ID="O365BusinessRetail">

Reference for Click-to-Run configuration.xml file

 

Failed to run the action: Use Toolkit Package – Error: 80070002; Source: Windows

Error:

Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)

Use Toolkit Package Error 80070002

Environment:

System Centre 2012 R2 CU5 Integrated with MDT 2013. Deployment Windows 7 SP1 with Office 2013.

Cause:

If the Drive Letter task sequence variable is configured to True. This does not occur if it is configured to False.

Solution:

To work around this issue, create the following two Task Sequence variables at the very top of the Task Sequence:

SMSTSDownloadRetryCount = 5
SMSTSDownloadRetryDelay = 15

Place them immediately after the Execute Task Sequence group.

Troubleshooting OSD – Now where are those logs again?

When troubleshooting you’re OSD, it is always good to know those log locations. Here is a quick list of the smsts.log and it’s locations during the deployment:

  • WindowsPE, before HDD format: x:\windows\temp\smstslog\smsts.log
  • WindowsPE, after HDD format: x:\smstslog\smsts.log
  • Windows, SCCM agent not installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
  • Windows, SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log
  • Windows x64, SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
  • Task Sequence completed: c:\windows\system32\ccm\logs\smsts.log
  • Task Sequence completed x64: c:\windows\sysWOW64\ccm\logs\smsts.log

Are you PXE booting?

Better have this log file in you favourites; \\DPServer\D$\SMS_DP$\sms\logs\SMSPXE.log. It records details about the responses to PXE boot clients and details about expansion of boot images and boot files.

Document a Configuration Manager 2012 Task Sequence

After sometime I was able to document a Configuration Manager 2012 Task Sequence using the tsDocumentorv2.xsl file that was previously used for MDT Task Sequences.

  1. In Configuration Manager 2012 export the TS to a zip file.
  2. Extract the zip file.
  3. Navigate to SMS_TaskSequencePackage\{packageid}.
  4. Copy tsDocumentorv2.xls into the SMS_TaskSequencePackage\{packageid} folder.
  5. Open the file object.xml and search for CDATA
  6. Copy everything between <VALUE><![CDATA[ and ]]></VALUE>
  7. Paste it into a new text file. The contents should start with <sequence version=”3.00″> and finish with </sequence>.
  8. Add the following text to the top of the new file <?xml-stylesheet type=”text/xsl” href=”tsDocumentorv2.xsl”?>.
  9. Save the new file with a .xml file extension into SMS_TaskSequencePackage\packageid folder.
  10. Start Internet Explorer and open the newliy created xml file.
  11. Hit F12 and enable Compatability View browser mode.

Michael Niehaus Notes from TechEd North America

As we were going through our TechEd North America deployment pre-conference today, we showed a lot of links for pages of interest.  Here is a list of those (at least the ones I remembered):

Also, be sure to look for the session slides on http://deploymentbunny.com.

Cannot perform Offline Servicing with an online-only package

FAILURE (5627): -2146498514 0x800F082E: Run DSIM.exe
Litetouch deployment failed, Return Code = -2147467259 0x80004005

To find packages that cannot be used for Offline Servicing, open the DISM log file located on the client machine: X:\Windows\Logs\DISM\dism.log.

The following should be excluded from Offline Servicing:

Windows 7 x64

KB2496898 – An update to support the new currency symbol for the Indian Rupee in Windows 7
KB2506143 – Windows Management Framework 3.0 for Windows 7 SP1
KB2533552 – An update that prevents a “0xC0000034” error message when you try to install Windows 7 SP1
KB2604521 – An update to country codes of Curaçao, of Bonaire, Sint Eustatius and Saba, or of Sint Maarten (Dutch part) in Windows 7
KB2726535 – An update is available that adds South Sudan to the list of countries in Windows 7
KB2819745 – Windows Management Framework 4.0 for Windows 7 SP1

Task Sequence WMI Queries for Lenovo BIOS Updates

wmic ComputerSystem get model

Model
3093AC7

Task Sequence WMI Query:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%3093AC7%” OR Model LIKE “%30933FR%”

 

wmic BIOS get version

Version
LENOVO – 1230

Task Sequence WMI Query:

SELECT * FROM Win32_BIOS WHERE NOT Version LIKE “%1230%”

Configuration Manager OSD Task Sequence WMI Queries

During your OSD Task Sequence you may want to determine whether the machine is a laptop or not, install software to a specific machine name format, or install drivers to only specific models of laptops.  For this you can use the WMI Query Condition within the Tasks of your Task Sequence.  A great tool to look up what can be queried from of WMI is WMICodeCreator and is provided by Microsoft.

Examples:

Laptop Hardware: Select * FROM Win32_Battery WHERE Chemistry > 3

Computer Model:  Select * FROM Win32_ComputerSystem WHERE Model like ‘%latitude%5400%’

Computer Name:  Select * FROM Win32_ComputerSystem WHERE Name like ‘CH%’ or Name like ‘AR%’