Support is >Here<

Use WizardSelectionProfile to make MDT2012 Boot images act like MDT2010 Boot images.

Brian Gonzalez — Tue, 29 Jan 2013 16:16:32 +0000

In MDT2012, the x86 or x64 boot images deploy any/all OSes (regardless of architecture), excluding a small subset of scenarios, which I can discuss further, if desired. MDT2010 boot images only supported deploying the OS of the booted architecture, i.e. the x86 boot image only displayed the x86 Task Sequences. If you want 2012 to still behave like this, use the “WizardSelectionProfile” Custom Settings INI rule/property to display only a subset of Task Sequences, specified with a Selection Profile.

1. Create 2 selection profiles, one containing the desired x86 Task Sequences and one for x64.

2. Update your Custom Settings INI (Rules) to display only the appropriate Task Sequences.

3. Test changes…

-BG

Some Common Install Packages Updated.. Flash, Reader, and Java.

Brian Gonzalez — Thu, 10 Jan 2013 20:50:04 +0000

The following silent packages were updated:

FlashPlayerIE_11.5.502.146.zip
FlashPlayerPlugIn_11.5.502.146.zip
Java7Update10-7×64.zip
Java7Update10-7×86.zip
AdobeReader_11.0.01.zip

URL: http://panaconsulting.box.com/bundles
* Navigate to the “CommonInstalls” folder.

-BG

Receiving “CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package” error in the SetupAct.Log when installing Win 7 x64 via SCCM 2012 SP1 Beta using Install DVD as Source Files. — SOLVED

Brian Gonzalez — Wed, 09 Jan 2013 17:29:12 +0000

- SOLVED (See Below)

Post URL: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/ad6e34d8-3314-4637-affb-f1a35d5f6652

Using the Auto-Apply Drivers, no issues occur, but the Install Windows step is failing regularly when using the “Apply Driver Package” step. I need this feature working as I have multiple customers using the SCCM Media Deployments.

setupact.log output:

2013-01-09 12:07:12, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [E:\_SMSTaskSequence\drivers\2\iaAHCIC.inf]
2013-01-09 12:07:12, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x9]
2013-01-09 12:07:12, Info IBS AddDriverPackageIntoDriverStore:System root is [E:\Windows]
2013-01-09 12:07:12, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\]
2013-01-09 12:07:33, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [E:\_SMSTaskSequence\drivers\2\iaAHCIC.inf] into driver store. Error code is [0x80070032]
2013-01-09 12:07:33, Error [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [E:\_SMSTaskSequence\drivers\2\iaAHCIC.inf]. Driver package is [Critical]. Error code is [0x32][gle=0x00000032]
2013-01-09 12:07:33, Error [0x0602ab] IBS CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x32][gle=0x00000032]
2013-01-09 12:07:33, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows installation cannot continue because a required driver could not be installed.]
2013-01-09 12:07:34, Info [SETUP.EXE] Called script [X:\windows\Setup\Scripts\ErrorHandler.cmd] to handle fatal error
2013-01-09 12:07:34, Info IBS Callback_Rollback_ExecuteOnlineRollback: Executing [E:\_SMSTaskSequence\Packages\PS100008\SOURCES\rollback.exe /CleanInstallFromWinPE /noui /BTFolder:E:\$WINDOWS.~BT\Sources]…

I’m also seeing alot of these errors in the SMS..log:

Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type

Any help is much appreciated.

.ZIP of Log Files: https://panaconsulting.box.com/s/yxhqadtx80zjrbcar4gt
Storage Drivers being injected: https://panaconsulting.box.com/s/mqjhgsblwvop3kh1nyl1

Issue was related to the Intel MSD driver package. This driver package was intended to be installed AFTER the OS is installed. SCCM was determining the driver as critical to the Install of the OS as its an MSD driver and exiting the TS.

Receiving “The /target parameter specifies an invalid target location.” when attempting to Install XP SP3 via MDT 2012 TS in SCCM 2012 SP1 Beta

Brian Gonzalez — Wed, 09 Jan 2013 16:55:05 +0000

Post URL: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/ca4ca7ba-b208-4c19-9a60-cd8a5f1e7169

Built DC01 and CM01 via Johan’s Hydration Kit. Win 7 deploys with no issues, but fails when attempting to install XP via a clean or .WIM installation.

Receiving a “The /target parameter specifies an invalid target location.” error.

SMS..log output:

0) || (arg == L"0")) && (g_Target.Partition >= c_MinPartition), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,254)]LOG]!>

Log Files .ZIP: https://panaconsulting.box.com/s/k9h067346p8g2mwzt473

Microsoft released “How To..” videos on SCCM 2012 (42 in total!)

Brian Gonzalez — Tue, 08 Jan 2013 06:47:25 +0000

http://technet.microsoft.com/en-us/video/system-center-2012-configuration-manager-how-do-i-video-series.aspx

I’ll highlight videos I found helpful in the next couple of days, as I watch them myself.

-BG

MS page that lists all of the Powershell commands that replaced VBS script (Shell Scripting)

Brian Gonzalez — Mon, 07 Jan 2013 19:19:26 +0000

http://technet.microsoft.com/en-us/library/hh848796.aspx

Due to how busy I constantly am, a majority, if not all, of my scripting is still done in VBS code. Its simply easier to just whip together a VBS script using PrimalScript than learning the proper way to write and execute the powershell script. With SCCM2012 and MDT2012 supporting PS scripts out-of-the-box, there is NO excuse not to move in this direction for all of my scripts. This page will serve as my foundation until I get used to looking up commands in ISE.

-BG

Complaint: STILL no RETRY when missing “Program Files” in an SCCM 2012 Task Sequence…

Brian Gonzalez — Mon, 07 Jan 2013 18:53:28 +0000

Post URL: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/694ae620-f92e-4076-b8ee-368bae20d97d

Why in god’s name doesn’t the Developers of SCCM add a retry button to this dialog. Anytime I’m missing 1 package, I have to restart the machine? Seems silly at this point..

-BG

Question: SCCM 2012 SP1 Lab Clients not finding MDT 2012 Boot Image via PXE… – SOLVED

Brian Gonzalez — Fri, 04 Jan 2013 03:13:29 +0000

Question Posted: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/52fea4c4-6711-4ad0-b3bb-98201fe90fff

- SOLVED (See Below)

1 2008 R2 server acting as DC, WSUS, WDS, and SCCM 2012 SP1 server. Running in a VM Workstation V9.01. VMNet 2 is assigned to both the SCCM server and Client VM. MDT 2012 has been added and Boot Images have been created and staged in DP. Boundaries created for both the IP Subnet (192.168.5.0) and AD. Clients PXE boot, but then get the “AbortPXE” packet.

The server “SMSPXE.log” is showing the following:
00:0C:29:60:B8:16, 428B4D56-B0E3-A0C3-1316-1286D560B816: could not find boot image S0100009
00:0C:29:60:B8:16, 428B4D56-B0E3-A0C3-1316-1286D560B816: Not serviced.

As per the content status, the boot image is staged and raring to go..

To fix the issue, I needed to do the following:
1. Tick the “Deploy this boot image from the PXE-enabled dis…” box from the “Data Source” tab of the Boot Image used in the Task Sequence.

2. Remove the “Distribution Point” role from “Servers and Site System Roles”.
3. Re-Add the “Distribution Point” role and re-distribute all packages.

-Brian G (http://supportishere.com)

New Panasonic Toughbook Imaging Bundles Available For Download NOW (Updated)

Brian Gonzalez — Mon, 31 Dec 2012 04:56:12 +0000

— Fixed Bundles URL (May 1, 2013)

In some Panasonic Toughbook models upwards of 15 utilities are required to be installed to function properly. Add in some optional components, such as Wireless WAN Connectivity, GPS, and a Barcode Reader, and we could be in the neighborhood of 20-30 required installs. These “bundles” were produced to greatly simplify all of these mandatory installs.

Bundles Pros:

ONE install step per Model/Mark (19A – Mk5)
Logs all activity to single file (C:\Windows\Temp\Pana….log)
Works with all Imaging Suites (SCCM, MDT2010/2012, LANDesk, KACE, Altiris, etc.)
Supported and Produced by Panasonic.
Installs and Drivers are NOT Re-Packaged or Re-Engineered.

Cons:

Does not include Storage or LAN drivers, these must be downloaded from Intel (http://downloadcenter.intel.com/)
Added into Imaging Suites, yet managed on File level (.ZIP file names in SRC\ folders dictate what and when they are installed)

See the following .PDF for assistance in downloading and utilizing the bundles.

Updated URL – 5/1/2013
https://panaconsulting.egnyte.com/publicController.do?folderName=20130501&fileName=02ce201186d84d71

Feedback is encouraged! (Comment here or email my team at imaging@us.panasonic.com)

-BG

Helpful Tool: Hide Hardware Found Wizard screens in XP AutoIt App

Brian Gonzalez — Mon, 31 Dec 2012 04:41:30 +0000

I use this tool on all of my XP installs. You know XP right.. You’d be surprised how many companies are still using it..

Use: Download and extract .ZIP and run PInstall.bat upon initial startup of Win XP out of Mini-Setup:

FYI, this works well with MDT2010 and 2012.

-BG