For many different reasons, administrators may want to have an image backup of a machine. SCCM along with the integrated MDT tools, give administrators a simple solution for creating wim based backups of machine, which can be fully restored if the machine has problems. In addition for complex tasks, this can be incorporated as part of the sequence for a complete backup of a computer before imaging with a new operating system.
- File Server: with space to store backups can be very simple. In some scenarios, workstations have been used (Instructions to setup the file server shares in the procedure section).
- Hotfix KB2910552 for windows XP: If you are running Windows XP make and SCCM 2012 R2 make sure that Hotfix KB2910552. For more detailed information please see blog post: https://davejaskie.wordpress.com/2014/03/30/system-center-configuration-manager-sccm-2012-r2-and-xp-migrations-require-hotfix-2910552-to-ensure-no-ntldr-missing-error/
- MDT 2013 Tools: Backups use the MDT 2013 Tools. If you do not have this integrated into your SCCM environment, it is a very minor addition to the sccm site. For additional information see blog post: https://davejaskie.wordpress.com/2014/03/31/15/
- Build an Active Directory security group for the sccm servers.
- Setup a file Share to Store Wims.
- Build a task to run a backup of the computer.
- While not required it is recommended that the sccm servers be added to a security group. This will ensure that in a large environment all of the sccm servers have access to save the information to the backup share. In this example we will use the group SCCM-SiteServers.
- Open up the sccm site servers group and click on the members tab, then click the add button.
- When prompted for the object name, click object types.
- Make sure that computer objects are selected and click OK.
- After the Active Directory group for the site servers is populated, we can move to setting up the file server to store the backed up WIM files.
- Log on to the file server and create a share. The share name is not important; however the sccm site servers need full access to drop the newly created wim files. In this example we use an sccm share name on the server \\sccm-backups.testsite.com
- After the file share is setup, the next step is to build the task sequence.
- The Task sequence has 5 steps,
- Reboot the machine to Windows PE
- Use MDT toolkit package: We use 2013, however previous versions work as well. For more information on MDT integration see my post (https://davejaskie.wordpress.com/2014/03/31/15/)
- Set a task sequence variable to use the backup share that was created in the previous file share setup sequence
- Set another variable for the backup drive. I would recommend doing all.
- Finally run a command line to perform the backup
- Once the task is created it can be deployed to computers and successfully pull images.