Jump to content


owndotcom

Create Task Sequence Media Failure

Recommended Posts

CreateTSMedia.log:

 

Size available = 6719 Mb, size required = 6177 Mb

OS image has a size 6177 Mb exceeding max file size 4095

UFD media does not support this file size

Failed to create media (0x80004005)

CreateTsMedia failed with error 0x80004005, details=''

MediaGenerator::~MediaGenerator()

Media creation process that was started from Admin Console completed.

CreateMedia.exe finished with error code 80004005

 

The OS Image is from the previous SCCM 2007 environment.

 

The problem is that the Task Sequence Media Wizard formats the USB drive to FAT32 and since the OS Image is greater than 4GB it fails.

 

Is there a way to get SCCM to use NTFS by default, or perhaps have it split up the OS image when creating the package?

Share this post


Link to post
Share on other sites


Update to this topic,

 

Running the Create Task Sequence Media wizard and creating an ISO instead of the USB device worked as it was supposed to. I then had to format the USB drive with the DISKPART tool and copy the data from the ISO onto the USB drive.

 

I contacted MS Support and they're trying to determine if this is an actuall bug in the software.

Share this post


Link to post
Share on other sites

I contacted MS Support and they're trying to determine if this is an actuall bug in the software.

 

I'm having the same issue. Any feedback from Microsoft yet?

Share this post


Link to post
Share on other sites

The SCCM 2012 Standalone media wizard will not allow you to create USB media with .WIM files that are larger than 4095MB. The wizard will however create .ISO with WIM's larger than 4095MB. The wizard splits the .WIM files into multiple files smaller than 4095MB. Use the information below as a work around to create Bootable USB media with Large WIM files.

1. Create a Standalone media .ISO with the command line below. You must create the ISO via a command line because the SCCM wizard max ISO size is 8.5GB. This will cause you to have multiple ISO's. By using a command line you can specify the max .ISO file size to be larger with the /M switch which will create one large ISO. Replace the following Parameters below with information from your environment /P:"ManagementPoint" /S:"SiteCode" /D:"DistributionPoint" /A:"TaskID"

"C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\i386\CreateMedia.exe" /K:full /P:" ManagementPoint.domain.com" /S:" TST" /C:"" /D:" DistributionPoint.Domain.com" /L:"Configuration Manager 2012" /A:"TST00011" /Z:"False" /T:"CD" /M:"44482" /F:"C:\Deployment.iso"

Note: You can monitor the ISO creation by viewing the following log file (use CMTRACE.exe for best results). C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog\CreateTsMedia.log

2. Open an Administrator Command prompt and use Diskpart to configure your USB drive. Be sure to enter the correct disk number for your USB drive. (CAUTION THIS WILL ERASE ALL DATA ON THE DRIVE THAT YOU SELECT)

Note: I am setting my Partition to a size of 16GB. This may not be necessary but I am trying this due to problems I have read about with USB drives larger than 16GB.

Diskpart

List Disk

Select Disk ?

Clean

Create Partition Primary size=15175

Select Partition 1

Format FS=FAT32 Quick

Active

Assign letter=z

Exit

3. Mount the ISO file that was created. I use Virtual Clone drive from Slysoft to do this. (My favorite ISO mounting tool, Spyware free, doesn’t require a reboot, and free to use)

"C:\Program Files (x86)\Elaborate Bytes\VirtualCloneDrive\VCDMount.exe" C:\Deployment.iso

4. Use Xcopy to copy all of the files from the mounted ISO to the USB drive. You may need to modify the drive letters for your environment.

xcopy E:\*.* /s /e /f Z:\

5. This is the command line that unmounts the ISO using Virtual Clone Drive.

"C:\Program Files (x86)\Elaborate Bytes\VirtualCloneDrive\VCDMount.exe" /u

Share this post


Link to post
Share on other sites

I ran the CreateMedia.exe with the /? switch but nothing showed. So I then looked in the AdminUILog file and found this treasure trove of information:

USAGE:

 

boot media:

CreateMedia.exe

/K:boot

/P:<provider>

/S:<site code>

/C:<connection options>

/D:<list of DP server names>

/L:<media label>

/E:<pre-execution package id>

/G:<pre-execution command line>

/Y:<password to encrypt certificate>

/R:<certificate file path>

/W:<certificate file password>

/U:<unknown machine support>

/J:<internet client>

/Z:<unattended media>

/1:<[certificate start time] HIGH;LOW>

/2:<[certificate expiration time] HIGH;LOW>

/5:<uda setting>

/X:<Task Sequence Variable>

/B:<boot image id>

/T:<media type>

/F:<destination of media file>

 

capture media:

CreateMedia.exe

/K:capture

/P:<provider>

/S:<site code>

/C:<connection options>

/D:<list of DP server names>

/L:<media label>

/B:<boot image id>

/T:<media type>

/F:<destination of media file>

 

stand-alone media:

CreateMedia.exe

/K:full

/P:<provider>

/S:<site code>

/C:<connection options>

/D:<list of DP server names>

/L:<media label>

/E:<pre-execution package id>

/G:<pre-execution command line>

/Y:<password to encrypt certificate>

/A:<task sequence id>

/Z:<unattended media>

/X:<Task Sequence Variable>

/T:<media type>

/M:<media size>

/F:<destination of media file>

 

prestaged media:

CreateMedia.exe

/K:prestaged

/P:<provider>

/S:<site code>

/C:<connection options>

/D:<list of DP server names>

/L:<image created by>

/3:<image version >

/4:<image description >

/E:<pre-execution package id>

/G:<pre-execution command line>

/Y:<password to encrypt certificate>

/R:<certificate file path>

/W:<certificate file password>

/U:<unknown machine support>

/Z:<unattended media>

/1:<[certificate start time] HIGH;LOW>

/2:<[certificate expiration time] HIGH;LOW>

/5:<uda setting>

/X:<Task Sequence Variable>

/B:<boot image id>

/O:<OS image id>

/I:<OS image index>

/T:<media type>

/F:<destination of media file>

Share this post


Link to post
Share on other sites

Dears,

II'm Making a stand-alone media , what are the mandatory switches to create it ?

Also what does /P:<provider> means ???

Hint: my WIM Image is more than 11 Gb so what I'm supposed to make the switch /M ??

Also for /A should I make any Random Task ID ??

Share this post


Link to post
Share on other sites

Hello

 

I had a issue where it was not creating the iso failing with - Failed to verify hash value of package

 

i worked out that i needed to use CMD under run as administrator and it solved the issue.

 

Just thought i share encase others have issues

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...