Imaging with free Macrium

   Information

This tutorial shows imaging with free Macrium Version 5.0. If you are still using Macrium Version 4.2, go to this Vimeo site where the tutorial of that version is stored.

The Video does not show the recovery part because I have no setup to screen capture it. But Keith (Kado) made this excellent recovery tutorial with text (but no sound) that he captured from a virtual partition.

   Warning

Note that the external disk to which you image must be formatted in NTFS. A disk that is formatted in Fat32 will accept an image, but the recovery programs cannot restore that image. You can, however, mount (open) a Fat32 image as VHD.

   Note

The production of the WinPE recovery CD (which is highly recommended) may take up to 3 hours because Macrium needs to download the 1.7GB WAIK (Windows Application Installation Kit). For your convenience I have uploaded a ready made .iso of the WinPE recovery disc. That can be downloaded in appr. 8 minutes which clearly beats the WAIK download. Once you downloaded and unzipped the folder, you can burn it directly to a CD with e.g. ImgBurn.

Here is the link to my Skydrive site.

Here is an alternate link from FileSwap (courtesy of Gary - Britton30)

I draw your attention to the fact that this WinPE CD can also be used to make images. That may be convenient in case you do not want to install Macrium on your PC.

This video tutorial explains the full cycle of the imaging process which is:

· Initial setups
· Image definition
· Image scheduling
· Image production

The imaging program that was used for this tutorial is free Macrium. But the basic principles are the same for other imaging programs although the user interface will be different.

This video runs for appr. 7 minutes.
There is a related thread on the Vista forum which gives a brief introduction to Macrium followed by a discussion.
You can download the free Macrium edition from here.

Note: If you have a problem with the loudness of the sound output of the video, check the "Loudness Equalization" box in your Playback device. It is under the 'Enhancements' tab.

Related Tutorials

---

• How to Create a System Image Backup in Windows 7
• How to Do a System Image Recovery in Windows 7
• How to Backup User and System Files in Windows 7
• How to Restore Backup User and System Files in Windows 7
• How to Restore your System with a Broken Windows 7 System Image
• How to Create a Bootable Rescue USB Flash Drive for Macrium Reflect

 

[RedLad]

Hi there,

I will be creating a system image one I have all my programs installed. I have Windows 7 installed on the SSD and have a separate HDD drive in the PC too. I have moved my user folders to this HDD. So, is it still possible to create an image with my setup?

Thanks

 

[Kari]

Hi there,

I will be creating a system image one I have all my programs installed. I have Windows 7 installed on the SSD and have a separate HDD drive in the PC too. I have moved my user folders to this HDD. So, is it still possible to create an image with my setup?

Thanks

I always move the complete Users folder to another drive than C: in all my Windows 7, 8.1 and 10 installs and have never had any issues in using Macrium as told in this tutorial.

The only difference is that you have to also select the drive containing your Users folder when creating the image.

Kari

 

[RedLad]

Thanks, it sounds like a great tool.

 

[kado897]

The problem with moving the "user" folder to another partition is that you have to image that partition as well. If you can move most of your data off the SSD and leave the "user" folder alone maybe using libraries to consolidate your data your images will be much smaller and faster.

 

[RedLad]

I'm not 100% sure what you mean there. I just have the OS on the SSD and the user folders separate on the HDD. I wouldn't mind having to backup the two sections. To be honest, the user folders don't have anything in them at the moment except for a few files as I have only just done a clean reinstall.

 

[kado897]

The problem is that you need to image both the ssd and the partition that contains the "user" folder at the same time as it is considered by Windows to be part of the OS. (It contains user registry entries). In fact if you were to do a Windows image it wouldn't allow you to do just the SSD. If you leave the user folder on the SSD you avoid that.

 

[RedLad]

The problem is that you need to image both the ssd and the partition that contains the "user" folder at the same time as it is considered by Windows to be part of the OS. (It contains user registry entries). In fact if you were to do a Windows image it wouldn't allow you to do just the SSD. If you leave the user folder on the SSD you avoid that.

Ah right, I get you. I want to keep the setup I have, so I will be using Macrium to do the image. I read also that AOMEI backupper is very good.

 

[kado897]

The problem is that you need to image both the ssd and the partition that contains the "user" folder at the same time as it is considered by Windows to be part of the OS. (It contains user registry entries). In fact if you were to do a Windows image it wouldn't allow you to do just the SSD. If you leave the user folder on the SSD you avoid that.

Ah right, I get you. I want to keep the setup I have, so I will be using Macrium to do the image. I read also that AOMEI backupper is very good.

Yes it is. I also use that. In some ways it is better than Macrium Free in that it can do incremental and file backups. You need the paid Macrium for that. Cant have too many backups.

 

[RedLad]

OK, thanks for the info.

 

[Kari]

The problem is that you need to image both the ssd and the partition that contains the "user" folder at the same time as it is considered by Windows to be part of the OS. (It contains user registry entries). In fact if you were to do a Windows image it wouldn't allow you to do just the SSD. If you leave the user folder on the SSD you avoid that.

As a user who has since Vista always sysprepped the Users to another drive than C: I just have to comment:

Using Windows native backup, yes you have to include the partition where the Users folder is located. Using Macrium that is not necessary although it is recommended; I have run several tests where I have only imaged the system reserved and C:, when the image is restored it picks the Users folder nicely along and system works again without issues. If the user has for instance installed software after the image was made which has let's say AppData\Roaming folders, these folders will of course remain in the system also after the image which no longer contains said software has been restored, but this really is a minor issue as those folders will be replaced as soon as the software is reinstalled after the restore.

The system works so well I have started to image only the C:, not the partition with Users because those files and folders are already securely backed up on OneDrive which I sync with my libraries. No need to image the Users with a terabyte of OneDrive.

Most of the registry is anyway stored on C:\Windows\System32\Config. Using Macrium instead of Windows native imaging, and keeping the Users folder relocated on another drive I can image and restore my system in a couple of minutes because the necessary image is relatively small, only containing software and Windows folders and when restored "picking up" my Users folder securely stored on another drive.

 

[kado897]

The problem is that you need to image both the ssd and the partition that contains the "user" folder at the same time as it is considered by Windows to be part of the OS. (It contains user registry entries). In fact if you were to do a Windows image it wouldn't allow you to do just the SSD. If you leave the user folder on the SSD you avoid that.

As a user who has since Vista always sysprepped the Users to another drive than C: I just have to comment:

Using Windows native backup, yes you have to include the partition where the Users folder is located. Using Macrium that is not necessary although it is recommended; I have run several tests where I have only imaged the system reserved and C:, when the image is restored it picks the Users folder nicely along and system works again without issues. If the user has for instance installed software after the image was made which has let's say AppData\Roaming folders, these folders will of course remain in the system also after the image which no longer contains said software has been restored, but this really is a minor issue as those folders will be replaced as soon as the software is reinstalled after the restore.

The system works so well I have started to image only the C:, not the partition with Users because those files and folders are already securely backed up on OneDrive which I sync with my libraries. No need to image the Users with a terabyte of OneDrive.

Most of the registry is anyway stored on C:\Windows\System32\Config. Using Macrium instead of Windows native imaging, and keeping the Users folder relocated on another drive I can image and restore my system in a couple of minutes because the necessary image is relatively small, only containing software and Windows folders and when restored "picking up" my Users folder securely stored on another drive.

That's good to know Kari.

 

[Lady Fitzgerald]

The problem is that you need to image both the ssd and the partition that contains the "user" folder at the same time as it is considered by Windows to be part of the OS. (It contains user registry entries). In fact if you were to do a Windows image it wouldn't allow you to do just the SSD. If you leave the user folder on the SSD you avoid that.

As a user who has since Vista always sysprepped the Users to another drive than C: I just have to comment:

Using Windows native backup, yes you have to include the partition where the Users folder is located. Using Macrium that is not necessary although it is recommended; I have run several tests where I have only imaged the system reserved and C:, when the image is restored it picks the Users folder nicely along and system works again without issues. If the user has for instance installed software after the image was made which has let's say AppData\Roaming folders, these folders will of course remain in the system also after the image which no longer contains said software has been restored, but this really is a minor issue as those folders will be replaced as soon as the software is reinstalled after the restore.

The system works so well I have started to image only the C:, not the partition with Users because those files and folders are already securely backed up on OneDrive which I sync with my libraries. No need to image the Users with a terabyte of OneDrive.

Most of the registry is anyway stored on C:\Windows\System32\Config. Using Macrium instead of Windows native imaging, and keeping the Users folder relocated on another drive I can image and restore my system in a couple of minutes because the necessary image is relatively small, only containing software and Windows folders and when restored "picking up" my Users folder securely stored on another drive.

That's what I thought. Windows backup will include all partitions/drives that have system folders/files whereas Macrium Reflect will image only what you tell it to, even if the User Folder is on another partition/drive.

 

[RedLad]

The problem is that you need to image both the ssd and the partition that contains the "user" folder at the same time as it is considered by Windows to be part of the OS. (It contains user registry entries). In fact if you were to do a Windows image it wouldn't allow you to do just the SSD. If you leave the user folder on the SSD you avoid that.

As a user who has since Vista always sysprepped the Users to another drive than C: I just have to comment:

Using Windows native backup, yes you have to include the partition where the Users folder is located. Using Macrium that is not necessary although it is recommended; I have run several tests where I have only imaged the system reserved and C:, when the image is restored it picks the Users folder nicely along and system works again without issues. If the user has for instance installed software after the image was made which has let's say AppData\Roaming folders, these folders will of course remain in the system also after the image which no longer contains said software has been restored, but this really is a minor issue as those folders will be replaced as soon as the software is reinstalled after the restore.

The system works so well I have started to image only the C:, not the partition with Users because those files and folders are already securely backed up on OneDrive which I sync with my libraries. No need to image the Users with a terabyte of OneDrive.

Most of the registry is anyway stored on C:\Windows\System32\Config. Using Macrium instead of Windows native imaging, and keeping the Users folder relocated on another drive I can image and restore my system in a couple of minutes because the necessary image is relatively small, only containing software and Windows folders and when restored "picking up" my Users folder securely stored on another drive.

Hi, thanks for the post. I'm just a little unclear on it though, just because this is new to me. The way I have my setup, as mentioned above, is an SSD withe my OS, the the user folders on the HDD. I don't have much installed right now as I have just done a clean reinstall of Windows 7. But one program (3ds Max) created folders on in the Documents folder upon install. So if I go to do an image using Macrium once I have all of my programs up and running, will it be able to know to create them files in the image also?

Basically what I want to know is - if Windows somehow gets corrupt on me, can I just restore from an image (Of SSD & HDD) to bring it back to a fully, working state, with all of my programs? Without having to reinstall any of the programs.

 

[kado897]

1. An image is everything on the partition so yes it will include those files.

2. When you restore an image you restore the partitions to the exact state they were when you made the image so if all your programs have been installed when you create the image then they will be there after the restore. Anything added afterwards, programs or data, will be lost.

 

[RedLad]

1. An image is everything on the partition so yes it will include those files.

2. When you restore an image you restore the partitions to the exact state they were when you made the image so if all your programs have been installed when you create the image then they will be there after the restore. Anything added afterwards, programs or data, will be lost.

Thanks for clearing it up. So I guess this is the technique IT people would use in companies for rolling out new PC's for staff. They'd just have an image built, then just distribute this to the other PC's that need that exact setup?

 

[kado897]

Yes pretty much that.

 

[Kari]

1. An image is everything on the partition so yes it will include those files.

2. When you restore an image you restore the partitions to the exact state they were when you made the image so if all your programs have been installed when you create the image then they will be there after the restore. Anything added afterwards, programs or data, will be lost.

Thanks for clearing it up. So I guess this is the technique IT people would use in companies for rolling out new PC's for staff. They'd just have an image built, then just distribute this to the other PC's that need that exact setup?

Yes pretty much that.

As Kado said, you almost nailed it . They are talking about deployment which is, to put it simple, just a fancy Geek lingo word for installation. To deploy Windows is to install Windows using a more or less customized pre-made image.

Here's a walkthrough for using deployment with Macrium made image instead of clean install on your own one or more machine network: http://www.sevenforums.com/tutorials/319903-windows-7-image-customize-audit-mode-sysprep.html. It also covers relocating the Users folder to another partition.

 

[kado897]

That's very comprehensive Kari.

 

[RedLad]

1. An image is everything on the partition so yes it will include those files.

2. When you restore an image you restore the partitions to the exact state they were when you made the image so if all your programs have been installed when you create the image then they will be there after the restore. Anything added afterwards, programs or data, will be lost.

Thanks for clearing it up. So I guess this is the technique IT people would use in companies for rolling out new PC's for staff. They'd just have an image built, then just distribute this to the other PC's that need that exact setup?

Yes pretty much that.

As Kado said, you almost nailed it . They are talking about deployment which is, to put it simple, just a fancy Geek lingo word for installation. To deploy Windows is to install Windows using a more or less customized pre-made image.

Here's a walkthrough for using deployment with Macrium made image instead of clean install on your own one or more machine network: http://www.sevenforums.com/tutorials/319903-windows-7-image-customize-audit-mode-sysprep.html. It also covers relocating the Users folder to another partition.

I'm a bit late replying, but thanks a mill for that link. It looks very useful. The thing is, I have already just done a clean install and will be doing a system image soon, once I get more programs installed. I will be getting a replacement SSD soon too as this current one isn't performing to what I thought it would. So hopefully I can use parts of your tutorial to do the imaging part and then get that image onto my new SSD.

 

[profdlp]

Here's a question:

Is it possible to use Macrium Reflect to restore a single image to multiple destination drives? For instance, if I had three identical laptops and wanted to put the same image on each of them can I do this in one shot? I would be removing the destination drives and hooking them up to a desktop computer for the imaging process.

As a corollary, could I run multiple instances of Macrium simultaneously from the same computer, each dumping a single image to a different HD?

Best Macrium tutorial there is, by the way.