Below is an excerpt from a Technet article that describes an approach to deploying Windows Intune client software on PC images.
Creating custom Windows images containing applications, including management agents, was once a common practice that has fallen out of favor lately. Known as thick imaging, the practice was to build monolithic images that were difficult to maintain and gobbled up vast amounts of storage. The process was to install Windows on a master computer, install applications and configure the computer, and then capture a new image that contained the applications.
The Windows Intune client software is not compatible with the thick imaging process. The client software enrolls the computer in the service during installation, which is why an Internet connection is required during installation. So, the following scenario does not work:
- Install Windows on a master computer.
- Install the Windows Intune client software, which enrolls the computer in the service. The enrollment data is specific to the computer.
- Capture a custom Windows image.
- Deploy the image to other computers in the organization. The Windows Intune client does not enroll each computer again, so each machine receives the same enrollment data. This clearly does not work.
As a result, you must use a thin imaging process to deploy the Windows Intune client software. In this process, you install the default Windows image, and then automatically install required applications immediately afterward. Both MDT 2010 and System Center Configuration Manager make this process easy. The benefit is that thin imaging reduces image maintenance and image count considerably. Updating an application no longer requires capturing a new image. You simply update the application in the deployment share.
A hybrid process is possible for organizations that do not use MDT 2010 or System Center Configuration Manager. You can add the Windows Intune installation files to an image, and then run the installer the first time the image boots. You can do this by creating an Unattend.xml file, which Work with Answer Files describes.