New Dell WINPE 4.0 Driver CAB Pack 19/05-2013

With the Dell Client Systems Deployment CAB, you can perform the following tasks:

1) Use Microsoft Windows OS-based PnP enumeration capabilities to install drivers for applicable devices
2) Create a system-level optimized deployment sequence
3) Setup an appropriate boot control sequence
4) Optimize the deployment of targeted system-specific driver packages

Release Date: 5/19/2013
Importance: Optional
Version: 1.0,A01

http://www.dell.com/support/drivers/us/en/04/DriverDetails/Product/latitude-e6530?driverId=F80M9&osCode=W864&fileId=3181395316&languageCode=EN&categoryId=SM#

ConfigMgr 2012 SP1 issues with OSDPreseveDriveLetter

Ran into this issue when trying deploy an existing image – the image was created without the propertly OSDPreseveDriveLetter in the Build and Capture task sequence.

My deployment task sequence kept failing Setup Windows and Configmgr.
The CCM client installed on the system ended up broken

The error messages from ccmsetup.log

C:WINDOWSccmsetup{1AF71F68-6089-4211-ADDC-06DF40606141}client.msi installation failed. Error text: ExitCode: 1603
– Client installation has failed too many times. Ccmsetup will now abort.

Solution:

– Add OSDPreseveDriveLetter=False to Build and Capture Task sequecen

I really wanted to use the image that i already had created, so here is what i did:

1. Added the OSDPreseveDriveLetter=False in my deployment task sequecen
2. Added /forceinstall /SMSMP=FQDN /SMSSLP=FQDN to step Setup Windows and ConfigMgr

File cannot be loaded because the execution of scripts is disabled on this system

Error when trying to execute powershell script

cannot be loaded because the execution of scripts is disabled on this system

The machine was a x64 bit Windows Server 2012 so had to set the Powershell policy for BOTH x86 and x64 to solve my problem

command: Set-ExecutionPolicy Unrestricted
The x86 version can be found here: %windir%SysWOW64WindowsPowerShellv1.0

About Execution Policies: http://technet.microsoft.com/da-DK/library/hh847748.aspx
Using the Set-ExecutionPolicy Cmdlet: http://technet.microsoft.com/en-us/library/ee176961.aspx