| Omar's profileOmar's Blog on Systems M...PhotosBlogLists |  Tools  Help |
|
July 08 Task sequence media and storage best practiseWhen you create your Task Sequence Media (e.g. when you want to deploy your images offline) and all goes well, you'll probably wonder why I'm getting excited about a little thing as the location SCCM uses to store the packages temporarily during compilation.
It's the temp folder under your user profile (%USERPROFILE%\Local Settings\Temp). In a test environment that brought me into trouble because my system drive had not enough disk space (you get a 0x80070070 error that states that SCCM failed to stage {PackageCode} in your CreateTSMedia.log). So depending how much stuff you need to pile into your image, the temp folder can easily grow to the size of the content of your average desktop / laptop system drive.
From a network perspective, it's interesting to understand what happens when you are working from a administrative desktop with your SCCM console. If you start to build your offline task media all necessary files and packages will be copied over the network into your %USERPROFILE%\Local Settings\Temp. Then if you selected a remote share on the network to store your images on, all that data (as one or more ISO files) will travel a second time over the network. And what happens if you decide to burn the ISO on your local DVD burner? I guess you get the point
 ...So what could you do as a best practise? You could consider the following:
TrackbacksThe trackback URL for this entry is: http://oehoeven.spaces.live.com/blog/cns!DA5513D12D034F6E!505.trak Weblogs that reference this entry
|
|
|
