Change Temporary Location for SCCM Media Creation

When you create Task Sequence media in Configuration Manager, the environment variable TMP is used to locate temporary storage for the creation process.

By default this points to the users temp folder, which is usually on C: drive with limited space.

While this is normally not a problem for creating an online boot media, creating offline media with many driver packages, software packages etc. you are bound to run into trouble.

It is not only the Create TS Media wizard that uses this location, is also used when a WIM file needs to be mounted, so every time you create an new boot media or inject drivers/updates etc. into an image this temporary storage is used. In SCCM 2012 R2, the new Virtual Hard Disk feature will also uses this temporary storage location.

Symptoms

When using the Create Task media Wizard, you receive an error stating that there is not enough disk space.

2014-10-28 08_51_22-Coretech - KK-SCCM-SQL01.ks.kk.dk - [SCCM Siteserver] - Royal TS

When you investigate the CreateTsMedia.log (Located in the <ConfigMgr install path>\\AdminConsole\AdminUILog folder> you will notice that the temporary storage is the temp folder in the users profile.

log

Solution

Well the solution is simple, we must change the location of temp storage to a drive with enough space available.

Start the “System” control panel from Control panel –> System and Security –-> System –> Advanced System Settings. Click Environment Variables…

system

Edit the TMP variable in the user profile to a folder on a drive with plenty of space, make sure the folder already exist.

2014-10-28 08_57_13-Coretech - KK-SCCM-SQL01.ks.kk.dk - [SCCM Siteserver] - Royal TS

Restart the Configuration Manager console, and the new temporary location will be used.


Comments (3):

  1. Jaccob Samraj Devadason says:

    Hi Henrik,
    I changed the value as mentioned, but when i create the TS Media ,it still writes to C:\Users\{userprofile}\AppData\Local\Temp.
    Could you advise?
    Thanks.

  2. Henrik Rading Henrik Rading says:

    I have done this several times and never had any issues…
    Make sure that you exit and restart all active consoles. It is a normal Windows environment variable that you are changing, this value is read by the console on startup. So if you change the right value and restart the console it should work.

  3. Tom says:

    You’ll have to reboot to be sure to stop all CCM processes.

Leave a Reply