Change the location of the Azure Backup Agent Scratch / Cache folder (without reinstalling)

So far Azure Backup is great, but it has a couple of shortcomings:


There's the issue with passphrases; if you lose this text-file based passphrase created at startup, any and all data you've backed up to Azure becomes unrecoverable.


The major one for me ended up being the cache /scratch location. This is, by default, stored here:  %ProgramFiles%\Microsoft Azure Recovery Services Agent\Scratch\.


The scratch location requires 10-15% of the total data set you are backing up to Azure... So when backing up large data sets, you're in danger of running out of free space on your system drive, which is exactly what happened to me.


No fear, I said. I'll just adjust the location of the scratch folder in the GUI.


There is no option to change this location in the GUI.


Oh well, <rolls up sleeves> the Powershell cmd set will have what I'm looking for.....


Nope..


The only TechNet post I found, had the solution as reinstalling the agent. I thought there had to be a better way.


I went searching the reg for the location and found it under HKLM\Software\Microsoft\Windows Azure Backup\Config\ScratchLocation.


I thought I'd better get hold of @AzureSupport to confirm the official approach. They advised the following:


1. Run up an elevated Command Prompt, and stop the engine service:


Net stop obengine


2. Copy the scratch folder (default path is %ProgramFiles%\Microsoft Azure Recovery Services Agent\Scratch\) to the new desired location.


3. Update the following registry entries with the new path to the scratch folder:


[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Azure Backup\Config\ScratchLocation]


[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Azure Backup\Config\CloudBackupProvider]  (this key is optional and only required to be changed if already present)


4. Run up an elevated Command Prompt and start the engine :


Net start obengine


And you should be good to go!


I've requested this is added to the cmdlets for Powershell for Windows Azure Backup..


HTH someone....

SysInternals tools - an easy download link!

got this tidbit during a vendor support call recently:

live.sysinternals.com provides a straight text based listing of all the sysinternals tools that we know and love.

This link should save you at least 5 mouseclicks navigating the Microsoft download site looking for the sysinternals tools.

HTH!

Max

PRINCE2 Practitioner exam sat and passed!

Late last month I sat PRINCE2 Practitioner training and passed the PRINCE2 Practitioner exam

I thoroughly enjoyed the training, in part due to a wonderful trainer, with an encyclopaedic knowledge of the training material.

I recommend PRINCE2 training via ilxgroup  in Auckland if you wanted to formalise your project management experiences with a globally recognised certification.

The first (of many) errors - Failed to inject a ConfigMgr driver into the mounted WIM file Status code=2147749889

The first error! Hopefully this helps someone out..

So, I was working away on our SCCM 2007 R3 infrastructure, which I'm in the process of migrating to SCCM 2012 SP1.

I've set up the migration jobs, which seemed to go swimmingly - that is until they hit the boot images..

The migration job failed with the following error message:

Failed to inject a ConfigMgr driver into the mounted WIM file
The ConfigMgr Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
Description = "Failed to insert OSD binaries into the WIM file";
ErrorCode = 2152205056;
File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
Line = 4262;
ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
Operation = "ExecMethod";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"<PACKAGEIDREPLACED>\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
};

I searched the above and found the following link:

http://www.itbl0b.com/2012/02/failed-to-inject-configmgr-driver-into.html#.Unlue4f293A

This article explains exactly what is the issue ( the driver path ( since being imported into CM )has changed), but doesn't go into detail on how to troubleshoot exactly which drivers have the incorrect path.

If you don't want to spend all day verifying the paths for all your drivers, open C:\windows\logs\dism.log. You can see the specific drivers that are causing you the issues

Open the SCCM console, and OSD>Drivers, find the driver, Properties>Update the path.. Retry update to the WIM, everything works fine!  :)

Get Ye to The Microsoft Virtual Academy

The IT industry is one of the fastest moving industries on the planet, and keeping up to date is a perennial challenge for IT professionals.

With 5 day courses priced at $3,000+ , there's often not enough money in the training budget to keep all your staff up to date with all the technologies they are using or are exposed to on a daily basis.

There's nothing quite like free technology training from certified professionals and the Microsoft Virtual Academy is a terrific alternative to pricey e-learning subscriptions, or the logistics of inhouse or offsite traning.

www.microsoftvirtualacademy.com

 There is an overall and a 'by country' points ladder, with points awarded for completing course modules, and bonus points for entire course completion, so it can become quite competitive.. I'm up to the gold tier now, and have got a lot out of the training I have completed so far.

They even have an 'Aspiring Technologist' section, with beginners courses in everything from Networking Fundamentals to Windows Phone Development.

Think about integrating some of these courses into your next technical project, as training prerequisites before you hand over new technologies or solutions to your clients.. or use course plans to help build your staff capability development targets.

Max