Understanding the content library
In the world of content distribution within Configuration Manager, the introduction of the content library is the biggest change. The content library will efficiently store content, which you will distribute to your distribution points. Single instance storage is also used on the content share. If the same package, for example, uses the same content, only one instance will be stored and references kept to indicate the file will be part of both the packages.
The whole reason for the introduction of the content library is to optimize storage space and avoid the distribution of files, which already exist on the distribution point in order to save bandwidth usage on WAN. Single instance storage will even work if the files are named differently. This is a common misconception that the file has to be named the same to be single instance stored.
Anatomy of the content library
The content library is stored in the root of a drive in a folder called SCCMContentLib. To...
