SCCM 2012 R2 "The Create Task Sequence Media Wizard Completed with Errors -2147212243" Refer to CreateTSMedia.log File

You are trying to create a Stand-Alone SCCM 2012 R2 USB Boot drive from one of your Task Sequences. It get all the way to the end and fails with The Create Task Sequence Media Wizard Completed with Errors -2147212243" Refer to CreateTSMedia.log File

 

It turns out in this instance that the Operating System image that was attempting to be compiled into a Stand-Alone USB Drive was approximately 10GB's in size. Having done some research on the Internet it appears to be a known issue for OS images greater than 4.75GB's to fail with The Create Task Sequence Media Wizard Completed with Errors -2147212243" Refer to CreateTSMedia.log File.

I opened up the CreateTSMedia.log file using the CMTrace utility, the log can be found at C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog.

From the log file there is a number of error relating to the formatting of the USB Drive. The USB Drive was brand new out of the packet, 32GB in size and was formatted in NTFS. I decided to manually format the USB Drive and try again, same result.

 

It transpires that to work around this issue you must use the Command Prompt to manually create an ISO containing all the SCCM components. The ISO file can be larger than 4.75GB's therefore it does not suffer the same issues as the automated wizard.

The following command can be used at an Administrative Command Prompt to generate an ISO file of an entire Task Sequence's components.

cd C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\i386

 

CreateMedia.exe /K:Full  /P:”sccm_dp_fqdn” /S:”sccm_site_code” /C: /D:”sccm_mgmt_fdqn” /L:”Configuration Manager 2012” /A:”sccm_taskseqID” /Z:”False” /T:”CD” /M:”10240” /F:”C:\New\NewSCCM.iso”

 

Change each of the variables in the command above to match the environment.

sccm_dp_fqdn	Configuration Manager Distribution Point FQDN
sccm_site_code	Site Code for the SCCM Site
sccm_mgmt_fqdn	Configuration Manager Management Point FQDN
sccm_taskseqID	The Task Sequence ID
/M:value	Sets the maximum size of the ISO (mine is 10GB’s)
/F:”File Path”	Output path for the ISO file

 

 

To keep an eye on how the ISO being created the CreateTSMedia.log can be used to monitor the progress. It will end with the statement CreateMedia.exe: Success if the ISO has been created successfully.

 

Now instead of using diskpart you can use the Windows 7 USB/DVD Download Tool to create a bootable USB Drive from the ISO file. It will usually fail at 99% reporting it is unable to copy files, in most cases the USB Drive still works correctly.

 

 

SCCM 2012 R2 - Task Sequence Failed "This Task Sequence cannot be run because the program files for TSID cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator."

You have created a new Task Sequence in SCCM, from your Central Administration Site. This Task Sequence will be used to deploy an entirely new Windows 7 x64 SP1 image to client devices. In the first instance you PXE boot a new device and try and run the Task Sequence, it fails with the error This Task Sequence cannot be run because the program files for TSID cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator.

 

As the Operating System images and the Task Sequence were provisioned in on the Central Administration Site Server my first thought was that I had forgot to Distribute Content from the ribon. Therefore I went ahead and done this again to ensure it was done.

 

When this did not fix the issue immediately I looked at the Content Status of the newly created software from Monitoring/Distribution Status and it appears the Distribution Manager was still replicating the content to other sites/DP's.

 

I then clicked on View Status and it reassured me that the content is being redistributed. Although quite a bit of time passed and it still remained in the In Progress state.

 

After around 2 hours, the Content Status changed to Success and the light turned to Green. It transpired in this instance the Active Directory did not have Sites and Subnets properly defined, therefore it is my guess that this caused the of the lengthy delay.