SCCM 2012 OSD with Multiple Drive letters using StandAlone Media

Hey guys I have a client who is required to partition their Windows 8.1 installation in three different partitions:
C:(OS Partition)
d:(SQLData Partition)
E:(Client Data Partition)
G:(CD-ROM)
I Already know that I should not use multiple drives for OSD but this is the requirement I have been given...
When I deploy my TS through PxE or USB Bootable Media all the drives are labeled correctly... C,D and E but if I Use Standalone USB Media then I end up with C, E and F and G as CDRom. I know that WinPE assigns a drive letter to the usb stick usually d: but
not always so how can I set the USB Standalone media to act the same way as PxE and Usb Boot Media? is there a way to have PE set the USB drive to drives latter in the alphabet? s, t or w?
Please help

Hey Joyce thanks for the response but I am not talking about the fact that the drives are labeled differently in PE I am stating that once the imaging process is complete the drive letters are not the same when doing a deployment through PxE or USB Bootable
media... When using Full standalone USB media to deploy the exact same TS the drive letter assignment is not consistent so to be as clear as I can I will explain again...
When doing a deployment from PxE, USB BOOT Media or USB BOOT Media attached to a VM, all the drives end up correct at the end of the deployment so C: is the OS drive D: is the Data Drive and E: is the Maps Drive (Keep in mind that if I do a usb
bootable media deployment and leave the USB in the computer I have the same issue as the standalone media)
But if I run the deployment from a STANDALONE USB Media then everything runs as it should but when I enter windows and look at my drive letter assignment the C: is the OS drive the D: drive is the USB the E: drive is the Data drive and G: is the Maps
Drive...
Which means to me that when windows is assigning drive letters it is assigning the USB Drive as D and not something less intrusive like y: or o:
So the question is: How can I have the drive letters assigned properly when using full standalone media So that my deployments are consistent when deploying through PxE, Usb Boot Media and USB Standalone media? Did no one ever test this out? and if so is
this what I can expect from SCCM 2012R2 For consistency to not be available across all deployment methods?

Similar Messages

SCCM 2012 OSD; Not finding driver package during deployment

I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction. Specifically I am having trouble with device driver deployment while deploying my reference image.
I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012.  I am building an OSD deployment and have successfully captured my reference image. I am not sure if it matters, but I manually built a reference
PC and using capture media (USB stick), I successfully captured my reference image. I have imported my drivers for the target PC into Config Manager and into a driver package. The driver package has been deployed to the distribution point
(DP).  I checked the status of the driver package within the console and verified it has been deployed to the DP.   I created a new task sequence (TS) to deploy the captured wim. Within the TS, I added an "Apply
Driver Package" step and pointed it to the aforementioned driver package. I added a WMI query to the step as follows
select * from Win32_ComputerSystem where Model like "HP Probook 6570b%."
Incidentally, I did a wmi query on the target PC to verify the model. I deployed the TS to the unknown computers collection and PXE booted the target PC. I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found." I checked the smsts.log log and found the following:
Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
for deployment. After more research I have done the following:
Deleted the Driver Package and recreated it and updated the TS step to point to this package.
Deleted and recreated the TS along with the driver package.
Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
When distributing content I verified it was successfully completed each time as per the console.
Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error. If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
I have run out of options to try and hope someone can help point me in the next direction to take.  After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
Thanks in advance,
Mike G.

Thanks for responding.
Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points. I checked now (about 12 hours later) and the package is showing it has not finished updating. I checked the content status and
it is "waiting for content." I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1". This error would occur every 30 min after each time the DP retried to process
the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
it retried, the error cleared, however the package status is still waiting for content. I tried doing a validation on the package but so far there has been no change.

Multiple Drive Letters to Share

Hi,
We have had an issue where a PC assigned multiple drive letters to a share when it should have just assigned U:.
I have never seen this before the PC is running Windows 7 64 bit and the server with the share is Server 2008 R2. Our PDC is Server 2012.
The drives are mapped via group policy preferences.
I have noticed some CD/DVD drives mapping twice before, but this hasn't really caused an issue.
Please advise.
Kind Regards,
John

Hi,
Have you checked the log under event viewer\Applications and Sevices\Microsoft\Windows\Group Policy? Anything valuable about this issue?
You can also configuer logging and tracing about mapped drive udner Computer Configuration\Administrator Templete\System\Group Policy\Logging and Tracing\"Configure drive maps preference logging and tracing" in case this issue happens again.
Yolanda Zhu
TechNet Community Support

Reporting Service Error Code 7403, on SCCM 2012 R2 with SQL 2012 SP1 CU6

Dear All,
I am facing issue to install Reporting Services Point on SCCM 2012 R2 with SQL 2012 SP1 CU6. getting error messages id 7403. please let me know if SQL 2012 SP1 CU6 is supported with SCCM 2012 R2 or not & if you have any solution on it.
Error Message: The report server service is not running on Reporting Service Point server "SCCM2012"; start the service to enable reporting.

I am getting below error msg when trying to browse both sites
1) For Reports
The report server cannot decrypt the
symmetric key that is used to access sensitive or encrypted data in a report
server database. You must either restore a backup key or delete all encrypted
content. (rsReportServerDisabled)
Get Online Help
Keyset does not exist (Exception from
HRESULT:
0x80090016)
2) For Reportserver
Reporting Services Error
The report server cannot decrypt the symmetric key that is used to access
sensitive or encrypted data in a report server database. You must either restore
a backup key or delete all encrypted content. (rsReportServerDisabled)
Get Online Help
Keyset does not exist (Exception from HRESULT: 0x80090016)
SQL Server Reporting Services

SCCM 2012 OSD Task Sequence - force Policy and SCEP update?

Hi,
How can I force a policy update to update machine policy and scep definitions at the end of
SCCM 2012 OSD Task Sequence,
Thanks,
Ward.

Hi,
I normally use this solution from Chris Nackers to deploy the latest EP definitions during OSD and deploy a custom EP policy, it works great. The policy will be downloaded when the client is registered.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2012 OSD task sequence condition

Is there a way to set a condition on a step that looks to see if the machine is already known to SCCM / Active Directory?
I have a step that names the PC using ITX Solutions AutoName function. I want to say only use this step if the machine is not known.

This is essentially a follow on to: http://social.technet.microsoft.com/Forums/en-US/3c6f37ad-b3dc-4219-ae7f-e6c51f05d5bf/sccm-2012-osd-retain-computer-name-on-reimage-rebuild?forum=configmanagerosd
To my knowledge, there is nothing explicitly built-in; however, you might be able to check _SMSTSMachineName to see if it matches the default WinPE naming convention of MINNIT_* or _SMSTSClientGUID to see if it has a value.
You could also put a task in before the format and partition step to check for an existing installation.
Jason | http://blog.configmgrftw.com

Single step workflow with multiple approvers (without using a group)

Hi,
is it possible to have a single step workflow with multiple approvers without using a group? This is for a contract document.
i want to add a number of users based on particular logic. The approvers are random and do not belong to any particular group.
DO let me know if it is possible or if any of you have done that.
thanks in advance.
regards,
rubio

Hi Rubio,
I believe the behavior would be, if individual users are added as approvers then the system would require each approver to approve the document. However, if you use the user group, you could set the role so that it would be either ALL or ANY.
Regards,
Vikram

Can I update 2012 mini with sad drive?

can I update 2012 macmini with ssd drive?

Take a look at the video Illaass pointed to, it shows what you'll have to do. If you've never poked inside the innards of a computer before, it looks a bit scary but its pretty easy to do if you view the video a couple times and take it slowly. But I honestly have to say it is closer to a moderate task than an easy task so you may want to take den.thed's advice and find an independant Apple service provider. You won't get this done at an Apple store.
Another possibility is to get an SSD in a thunderbolt or USB3 enclosure. It won't be quite as fast as if it were installed internally but you won't lose much and if you decide against doing the upgrade yourself it will probably be less expensive than going to an AASP.

How to use OSD with Multiple DPs to remote locations

Hi
My SCCM 2012 R2 Primary site is located on my corporate office but i need to use OSD for multiple branch locations in different subnets.in My Organization there is network level DHCP server rather than Windows DHCP...
What would be the complete configuration in this case .. can some one provide the steps..
Shailendra Dev

Hi,
The best way to forward the PXE boot requests to the DP/PXE server is to use IP Helpers in the routers/switches. I assume that the branch locations are without a DP. You can use DHCP scope options in the DHCP servers as well but you will end up with problems
when PXE-booting machines that run UEFI becuase it is not the same bootfile used and it is not really supported.
Maybe standalone media could be an option where you have the most of the TS on a USB stick/Drive.
Regards,>
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

[Guide] Install and run Windows 7/8 from an external drive without using bootcamp (works for late 2012 iMacs with 3TB drive)

This is a copy of a post from my blog, you can also Read it on my blog...
Introduction
After I received my new iMac with a 3 TB Fusion Drive, I was disappointed when I realized that Bootcamp was not running on this model and prevented me from installing Windows on it. I wanted to take advantage of the powerful iMac hardware to play games but I couldn't.
There are a few ways of working around this limitation, but I found most of them quite complex and most of the time they required formatting the internal hard drive or repartitioning it and go for a brand new installation of Mac OS X. I was not comfortable with that.
But there is another way, and that is to install Windows on an external hard drive, using either USB or Thunderbolt. Personally I used a Lacie Rugged 1 TB drive that has both USB3 and Thunderbolt connectors. Both work very well.
This guide may interest you if:
You have an internal hard drive of more than 2TB and you can't run bootcamp at all (like late 2012 iMacs with a 3TB drive)
You have limited space or you don't want to dedicate disk space on your internal hard disk drive to a Windows installation
What this guide will make you do:
It will make you erase all your data from your external USB3/Thunderbolt hard drive
It will make you install Windows on your external USB3/Thunderbolt hard drive
It will make you install bootcamp drivers
What this will not make you do:
It will not make you modify anything on your internal Mac hard drive
It will not make you use or install the bootcamp assistant
It will not activate the Preference Pane for the default boot drive. You have to boot by pressing the ALT key to manually select your boot drive each tome you want to boot Windows.
What you'll need
An external hard drive with a USB3 and/or Thunderbolt connector. This drive will be formatted so ensure you saved your files before going further. You can use either an SSD drive or a classic hard drive.
A Windows 7 or 8 install DVD or ISO (check whether to install 32 or 64 bits versions based on your Bootcamp drivers) and the corresponding Windows serial number.
One of the following:
Mac OS X with a Windows 7 or 8 Virtual Machine (use VMWare Fusion or Parallels Desktop for example. Note: VMWare Fusion seems to have some issues with Thunderbolt and USB3. Plug your drive to a USB2 enclosure or hub to work around this -it worked for me-, or use another VM software) → Read the important note below
A PC running Windows 7 or 8 → Read the important note below
Windows AIK (free) running on your Virtual Machine or on your PC, or just the imagex.exe file (the rest of the Windows AIK package is not needed)
Download imagex.exe
Download Windows AIK (this download and installation is not required if you have already downloaded imagex.exe)
Bootcamp drivers for your Mac. You can get these either by running bootcamp from your Mac (Applications > Utilities > Bootcamp) or, if like me you have a 3TB drive and can't run bootcamp at all, use the direct download links here.
A USB stick to store your bootcamp drivers
IMPORTANT: If your Mac has a 64 bits processor, your Windows Virtual Machine on OSX, your Windows installation on your PC and your Windows DVD/ISO must also be in 64 bits!
Step by Step guide
Step 1: Get the install.wim file
If you have a Windows ISO file:
Mount the ISO
If you're on OS X: double click on the ISO file
If you're on on Windows 7: Use a software like Virtual Clone Drive (free)
If you're on Windows 8: double click on the ISO file
Open the mounted drive, then go to the "sources" folder and locate the "install.wim" file. Save this file to C:\wim\ on your Windows installation or virtual machine.
If you have a Windows DVD: open the "sources" folder on the DVD and locate the "install.wim" file. Save this file to C:\wim\ on your Windows installation or virtual machine.
IMPORTANT: If instead of a "install.wim" file, you have "install.esd", you can not continue this step by step guide. And an ESD file can not be converted into a WIM file. So you must get a version of the Windows installation DVD/ISO that has an install.wim file.
Step 2: Clean, partition and format your external hard drive
On your Windows installation or virtual machine, plug in your external hard drive (can be plugged using USB2, USB3 or Thunderbolt at this stage)
Open the command prompt in administrator mode (cmd.exe). To run it in administrator mode, right click on cmd.exe > Run as admin.
Type the following and hit enter to open the disk partitioner utility:
diskpartType the following and hit enter to list your drives:
list disk
This will display a list of disks mounted on your computer or virtual machine. Make sure your drive is listed here before you continue.Identify the disk ID of your external hard drive. Replace # by your real external disk ID in the command below:
select disk #Clean all partitions by typing the following (warning: this will erase all data from your external drive!):
clean
Create the boot parition by typing the following followed by the enter key:
create partition primary size=350
This will create a 350MB partition on your external driveFormat the partition in FAT32 by typing the following:
format fs=fat32 quick
Set this partition to active by typing:
active
Assign a letter to mount this partition. We will use letter B in our example. If B is already used on your PC, replace B by any other available letter:
assign letter=b
Windows will detect a new drive and probably display a pop-up. Ignore that.Create the Windows installation partition using all the remaining space available on the external drive by typing the following:
create partition primary
Format the new partition in NTFS:
format fs=ntfs quick
Assign a letter to mount this partition. We will use letter O in our example. If O is already used on your PC, replace O by any other available letter:
assign letter=o
Windows will detect a new drive and probably display a pop-up. Ignore that.Exit the disk partitioner utility by typing:
exit
Step 3: Deploy the Windows installation image
Still using the command prompt in admin mode (you didn't close it, did you? ), locate the imagex.exe file mentioned in the "What you'll need" section and access its folder. In our example, we have put this file in C:\imagex\imagex.exe
Type the following and hit enter (remember to replace o: with the letter you have chosen in the previous step):
imagex.exe /apply C:\wim\install.wim 1 o:
This will take some time. The Windows installation image is being deployed to your external driveOnce done, type the following to create the boot section (remember to replace o: and b: with the letters you've chosen in the previous step):
o:\windows\system32\bcdboot o:\windows /f ALL /s b:
If you get an error message saying that you can't run this program on your PC, then most probably you are running on a 32 bits installation of windows and you're trying to deploy a 64 bits install. This means you did not read the important notes in the beginning of this guide
If you get an error message on the options that can be used with the BCDBOOT command, then it's because you're installing Windows 7, and the /f option is not supported. If that is the case, remove /f ALL from the command and retry.
Step 4: Boot from your external drive and install Windows
Plug in your external drive:
If you've done all the previous steps from a Windows PC, unplug your external drive from your PC and plug it to your Mac, either on a USB3 or a Thunderbolt port.
If you've done all the previous steps from your Mac using a Virtual Machine, ensure the external drive is plugged in to a USB3 or Thunderbolt port. Using USB2 should also work but you'll get very poor performance so I don't recommend doing that.
Reboot your Mac and once the bootup sound is over, immediately press the ALT (option) key and release it only when the boot drives selection screen appears. If you did not get the boot drives selection screen, reboot and try again. The timing to press the ALT (option) key is quite short. It must not be too early or too late.
On the boot selection screen, choose "Windows" using the arrow keys on your keyboard, then press enter.
The Windows installation starts. Follow the on-screen instructions as normal. The installation program will restart your computer one or 2 times. Don't forget to press ALT (option) right after the bootup sound, and boot on Windows again each time to continue the installation.
Step 5: Install bootcamp drivers
Once the Windows installation is complete, plug in the USB stick where you stored the bootcamp drivers (see "what you'll need" section), open it and right click on "setup.exe" and select "Run as admin". Follow the on-screen instructions.If you have an error saying that you can't run this program on this PC, obviously you have installed a 32 bits version of Windows and the bootcamp drivers for your Mac are made for a 64 bits version. You have to restart the whole guide and make sure to get a 64 bits version of Windows this time!
Once the bootcamp drivers are all installed, reboot and press ALT (option) after the bootup sound to boot on Windows again. And Voilà, you have Windows installed on your USB3/Thunderbolt drive running on your Mac.
Now each time you want to boot on Windows, press and hold the ALT (option) key after the startup sound and select "Windows", then press Enter.

Hi i'm trying to follow your guide, I installed windows 8 on bootcamp to do it planning to remove it after the operation is done, but i get stuck at part 3: every command i give to imagex i get a pop-up ftom windws asking how do I want to open this kind of file install.wim and imagex does nothing, what do i have to do to stop those pop-ups?

Helix gen.2 very slow with USB 3.0 and SCCM 2012 OSD

Hello there, i have a problem with our Helix gen.2. i would like deploy the OSD with SCCM 2012 and so i insert the USB 3.0 Dongle driver in WinPE. The Download and WIM installation is very fast but slows down after the OSD TS insert all Drivers for the system an makes a reboot. After the reboot the machine runs very slow over the network (1GB) and over 20 Hours and breaks down with a unsigned Error Message 80004005. i change the driver to an old version for the UBS 3.0 but it doesn´t helps so i need help from you. with best regards andré

What OS are you deploying on the box, 7 or 8.1?
Did you import the drivers from the Helix2 SCCM driver pack for the appropriate OS into a Driver Package?
Did you also add the USB 3.0 drivers specific to the OS being deployed into that same Driver Package?
Do you have an Apply Drivers task that references this driver package in the task sequence? If so, you should be able to find the task ID in the SMSTS.log file and verfiy it is running.

Create a prompt using MDT 2012 in SCCM 2012 OSD task sequence

Hi Experts,
I need some help with SCCM 2012 Task sequence using MDT 2012.
Here is the scenario:I want to build a task sequence where it will propmt whether the technican want to build a new build or refresh. Based on the technicians choice the task sequence will perform specific actions.
We can create the prompt using HTA or VBScript or some otherways.
But the requiremnt for us is to Use ONLY MDT 2012, not any other ways.
Is it possible to do like the above with UDI?
Please can someone shed some light how to do will be great.
Thanks in advance,

Hi,
UDI may achieve what you want. Take a look at the blogs below.
http://blogs.technet.com/b/anilm/archive/2012/06/01/integrating-mdt-2012-rtm-with-configuration-manager-2012-rtm-part-3-creating-and-deploying-a-udi-task-sequence.aspx
http://heinrichandsccm.blogspot.com/2013/04/how-to-setup-and-configure-sccm-2012.html
Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Juke Chou
TechNet Community Support

SCCM 2012 - OSD - HAL.dll error (windows XP) using USB

Hi
SCCM 2012
I'm creating OSD for Windows XP and create .iso files
1. I create ISO files
2. make the USB bootable
3. Copy the ISO files in content in USB
4. Boot from USB, when it finish I;m getting the HAL.dll error
Please advise
Robert

The hal.dll is missing?
http://support.microsoft.com/kb/314477/en-gb
Juke Chou
TechNet Community Support

SCCM 2012 OSD Replace Scenario

Hi,
I am using SCCM 2012 with MDT integration. My MDT OSD task sequence works fine, except in a replace Scenario. I run the client replace task sequence on the old machine and the USMT back is successful. I then boot with a USB thumb drive with boot media on
the new machine. I get the correct task sequence but it seems like the OS want to install on the BDE Drive, which I to small. My new computer and refresh works without problems and install on the correct drive. I don't understand why I get this issue in a
replace scenario. I am very new to SCCM OSD and your assistance would be greatly appreciated.

Hi,
Have you checked the log file smsts.log? Maybe it can give us some clues.
Here is a similar post for your reference.
Replace Scenario alternative for USMT Migration
http://blogs.technet.com/b/deploymentguys/archive/2011/09/01/replace-scenario-alternative-for-usmt-migration.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 r2 with CU1 - XP Refresh

Hi Everyone,
Hoping someone out there can assist with this. I am doing a refresh for XP to win7. I have read
http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd
and
http://www.windows-noob.com/forums/index.php?/topic/9418-referesh-task-sequence-from-xp-fails-on-sccm-2012-r2/
none of these work. I took a look at this and I was able to get pass the staging of the boot image
http://blogs.technet.com/b/brandonlinton/archive/2013/06/21/how-to-create-and-import-a-winpe-3-1-boot-image-for-use-in-configmgr-2012-sp1-cu2.aspx
however when the machine rebooted I received this. I also inject the nic drivers using dism and still the same issue. Any idea of a fix or how to go about refresh for
XP using sccm 2012 r2?
thanks all!

Hi,
Also ran into this issue, you're encountering this error because some components are missing in your WinPE image.
Note that this refresh scenario is not supported, however you can get this to work by manually customizing (especially importing WMI component) your WinPE image
before importing it ConfigMgr.
I made the script below, ran in on a base WinPE image from WADK for Windows 8 (a 6.2 version image so) to make it work (sorry for french comments Inside but I'm sure you'll get it :) ):
#Adapt these variables to you environment
$ADK = "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit" #Chemin d'ADK
$DismArchitecture = "amd64" #archi a utiliser pour DISM
$CompArchitecture = "x86" #archi a utiliser pour les composants
$MountDir = "e:\Mount" #point de montage a utiliser
$Wimdir = "E:\winpe.wim" #chemin du wim a modifier
$InjectDrivers = $TRUE #Choisir si il faut ajouter des pilotes ou non
$DriversDir = "E:\Pilotes\WinPE3.1_x86" #chemin contenant les pilotes
$AddCMTrace = $FALSE #Choisir si il faut ajouter cmtrace ou non
$CMTraceDir = "E:\Microsoft Configuration Manager\tools\cmtrace.exe" #chemin de cmtrace
$ChangeLocale = $TRUE #Choisir si il faut modifier les paramètre regionnaux ou non
$Locale = "fr-FR" #param regionnaux a utiliser
$DismFolder = "$ADK\Deployment Tools\$DismArchitecture\DISM" #ne pas modifier
$OptComponents = "$ADK\Windows Preinstallation Environment\$CompArchitecture\WinPE_OCs"; #ne pas modifier
$AddOPTComponents = $TRUE #Choisir si il faut ajouter des composants ou non
#liste des composants:
$ComponentList = @(
“$OptComponents\WinPE-WMI.cab”
“$OptComponents\$Locale\WinPE-WMI_$Locale.cab”
“$OptComponents\en-us\WinPE-WMI_en-us.cab”
“$OptComponents\WinPE-NetFx4.cab”
“$OptComponents\$Locale\WinPE-NetFx4_$Locale.cab”
“$OptComponents\en-us\WinPE-NetFx4_en-us.cab”
“$OptComponents\WinPE-HTA.cab”
“$OptComponents\$Locale\WinPE-HTA_$Locale.cab”
“$OptComponents\en-us\WinPE-HTA_en-us.cab”
“$OptComponents\WinPE-DismCmdlets.cab”
“$OptComponents\$Locale\WinPE-DismCmdlets_$Locale.cab”
“$OptComponents\en-us\WinPE-DismCmdlets_en-us.cab” );
#Composants pour WinPE 6.3: (a inserer a la place de NetFx4)
#“$OptComponents\WinPE-NetFx.cab”
#“$OptComponents\$Locale\WinPE-NetFx_$Locale.cab”
#“$OptComponents\en-us\WinPE-NetFx_en-us.cab”
#“$OptComponents\WinPE-PowerShell.cab”
#“$OptComponents\$Locale\WinPE-PowerShell_$Locale.cab”
#-----debut du script
#Creation du point de montage
New-Item -ItemType Directory -Force -Path $MountDir
#import de DISM
import-module $DismFolder
#montage de l'image
Write-Host "Mounting WIM file"
Mount-WindowsImage -ImagePath $Wimdir -Index 1 -Path $MountDir -ErrorAction Stop
#changement de locale
if($ChangeLocale -eq $TRUE)
Write-Host "Changing locale"
cd $DismFolder
dism.exe /image:$MountDir /set-syslocale:$Locale
dism.exe /image:$MountDir /set-userlocale:$Locale
dism.exe /image:$MountDir /set-inputlocale:$Locale
#ajout de cmtrace
if($AddCMTrace -eq $TRUE)
Write-Host "Adding CMTrace"
$CMTraceDest = $MountDir + "\Windows\System32"
Copy-Item -Path $CMTraceDir -Destination $CMTraceDest
#ajout des pilotes
if($InjectDrivers -eq $TRUE)
Write-Host "Injecting Drivers"
Add-WindowsDriver -Recurse -ForceUnsigned -Driver $DriversDir -Path $MountDir -Verbose -ErrorAction SilentlyContinue
#ajout des composants
if($AddOPTComponents -eq $TRUE)
Write-Host "Adding Optionnal Components"
foreach ($Component in $ComponentList)
Write-Host -Object (’Installing component: {0}’ -f $Component);
Add-WindowsPackage -Path $MountDir -PackagePath $Component -ErrorAction SilentlyContinue;
#demontage de l'image
Write-Host "Unmounting WIM file"
Dismount-WindowsImage -Path $MountDir -Save -Verbose
Mickael, My technet galleries contributions : ConfigMgr driver injector : http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d SCCM Collection splitter : http://gallery.technet.microsoft.com/SCCM-Collection-Splitter-e1c82b06 ConfigMgr
TS Tools : http://gallery.technet.microsoft.com/TSTools-f9b01357

SCCM 2012 OSD with Multiple Drive letters using StandAlone Media

Similar Messages

Maybe you are looking for