Macrium Reflect

1. What is iSCSI (Internet Small Computer System Interface ...
   searchstorage.techtarget.com/definition/iSCSI
   The iSCSI protocol allows the SCSI command to be sent over LANs, WANs and the Internet. Learn about its role in modern data storage environments and iSCSI SANs.

 

If you are not using BitLocker XTS encryption on your system, it is not necessary to rebuild your Recovery Media.

 

Question that has probably already been answered but can't find it: Does Reflect work well with Shadow Defender? Anything specific to think about if using the two together?

 

I just had a new use for the rescue DVD. Windows 10 Pro 64 bit had an issue with a windows update. The quick fix is to remove all files in the Softwaredistributions/download folder. BUT, a few items were in use and could not be removed. So, I booted the Rescue DVD I made, and in the explorer I deleted them just fine. Rebooted into Windows and the Update ran just fine!

 

Out of curiosity, what would happen if you tried to take an image while Shadow Defender is active? I can think of four scenarios, there are probably more, but the ones I can think of are:

• The snapshot is taken without the changes that has been made.
• The snapshot is taken WITH the changes that has been made.
• The snapshot is taken and results in a mutant abomination which is determined to end all datakind.
• The snapshot doesn't finish correctly for whatever reason.

Imo the second scenario would be ideal while the third scenario would be somewhat entertaining, first scenario could probably be useful in some cases and fourth scenario not so.

Edit: Not that relevant really since the Shadow Defender driver is unsigned and Windows 10 blocks the driver.. *shrugs* Bummer.

Edit 2: Uhuh, that was weird, got a bluescreen after restoring an image:

1. Took an image (snapshot) of the system before trying to install Shadow Defender.
2. Tried to install Shadow Defender.
3. Windows blocked driver.
4. Uninstalled Shadow Defender (no reboots to far.)
5. Decided to restore the image I took just before.
6. Started it from Windows and let it go through it automatically, left to make lunch in the meantime.
7. Came back to a machine with a black screen, had to forcefully reboot (for some reason it happens sometimes when I have an Ethernet cable plugged in, no clue why)
8. Windows booted, entered my password, bada-bluescreen regarding partmgr something...
9. Rebooted, same issue.
10. Performed a full-restore of the same latest image, now working just fine..

Since it was specifically a blue-screen regarding partmgr it sounds to me as if something during the first restore went wrong?

 

With Macrium Reflect v6.3.1665, the release notes says PE 10 Release 1607, but the Rescue Media wizard says PE 10 Release 1507.
Which one is it? I have already done a rebuild.

 

You will only get the 1607 rebuild if you are using BitLocker XTS encryption on your system. Reflect looks at your System during the rebuild and makes that decision for you. There's nothing in the 1607 build that's any different except an 800+mB download.

 

The size of the WinPE is different, the boot.wim file is different. I suppose they are using [parts of] the WADK for 1607.

 

Macrium Support explains the 1607 release HERE...

 

You are right.

I rebuilt Rescue Media on my main computer and it made a smaller ISO than on another computer where it had never used Rescue Media before and required a fresh setup. In both cases, I did not select the other 2 options (iSCSI or BitLocker). Edit: "Automatically unlock encrypted drives" was selected by default.
The fresh setup also doesn't mention anything about 1507 or any version number at all.

 

mine does when you build the rescue media

 

Very interesting, kronckew. Is that a fresh build or a rebuild?
I've rebuilt a few times with the same result.

I think there is an issue here with some systems.
I might have to delete it and start afresh.

 

I deleted the folder "Windows Kits" from C:\ProgramData\Macrium\Reflect and re-downloaded and rebuilt.
The version 1507 is gone now.

Still not sure what the difference is but there are different ISO hashes.

 

There was no mention of a version number in my previous post.
But, if you close Reflect and go back in and attempt to make Rescue Media again, it will now show version 1607.
That is after deleting "Windows Kits".

 

I had to do the same earlier this week

 

Looking to see if something is doable with the PE rescue environment.

Is it possible to build the rescue environment to include the settings configured in the Windows application? Example - I'd like to save network location and credentials so they don't have to be entered each time a backup is taken using the recovery environment.
Also of interest would be to save the backup template in the rescue media.

Or would I have to build it using a custom .WIM file with this sort of stuff already set up?

Thanks.

 

Nice question @ssbtech! I would like to do something similar (set default compression, verification, and locations) for the PE rescue environment.

 

I (as Admin) plan to install MR6-Free and setup a backup schedule. If I am not logged-on but my wife (Std. User) is logged-on during a scheduled backup time will the backup run?

 

Yes it will run, it doesn't use credentials from logged in user. I have similar setup and it runs with no problems when I'm logged in as standard user.

 

Perhaps it's a setup issue but that has not been our experience... As the administrator of our family PC I created a backup schedule to run daily. Last week when my husband (a standard account) was using the PC he received a UAC prompt (from MR6) requesting the Admin password before it would run the backup! As soon as the password was entered the scheduled backup started...

 

I checked task scheduled - it's run under admin credentials with "Run with highest privileges" enabled. I don't remember changing anything and AFAIK I created task through Reflect.
I run version 5.3 on Windows 7.

Edit: also have set it to Run whether user is logged on or not.

 

Same settings here, but I'm using MR v6 (Free) on Win7 x64.

 

This new Windows 10 1607 PE environment fails to clone my hard drive each and every time.

Since the release of Reflect 6 I have been making an intelligent clone from my internal HD to an external HD on a weekly basis. This went well until this new PE, which aborts (always on the same partition) with a write error.

I performed a scan for bad spots on both drives with HD Tune, but they come up clean.

Can this be a bug in PE/Reflect?