Citrix – From IMA to FMA

Today, I wanted to introduce a perfect blog post about differences between XenApp 6.x and 7.x.
Indeed, I’m still managing an old XenApp 6.5 farm, in process of migration to 7.x (currently 7.14, updating to 7.17 in progress).

This article: ] explains clearly where to find feature in the different version which can avoir some headache for guy like me 🙂

Just wanted to “re-blog” this.


Veeam – Backup Proxy Automount

Just a reminder for myself:
To avoid problems with Hotadd, when backuping via a Veeam Backup Proxy, think to disable automount:

1. diskpart
2. automount disable
3. automount scrub

Windows Update – 0x800F0831 – CBS_E_STORE_CORRUPTION

Today, i faced a weird problem with one of my Windows Server.
Indeed, since somtimes now, a particular update (from Windows Update) was not installing successfully.

Today, I decided to work on it, and found a particular way to correct it.

Step 1:
First as usual, we download the corresponding patch from Windows Update Catalog to retrieve the real true error (instead of using the automated process).
The error was on a Windows Server 2012 R2 Citrix server, with the KB3000483.
The installation process failed with error 0x800F0831

Step 2:
Investigating – searching with my friend Internet, I found some people, having the exact same error with the same patch on the same kind of Platform. However, no one had a real solution.

Step 3:
I decided to look at some logs file, and particulary C:\Windows\Logs\CBS\CBS.log which contains interesting informations – but is a bit confusing.
The perfect information is: Store corruption, manifest missing for package: Package_108_for_KB3067505~31bf3856ad364e35~amd64~~ and on the next line: [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
All is here: Something is missing in the Store (CBS_E_STORE_CORRUPTION / KB3067505), and this explain why the KB3000483 is not installing (error 0x800f0831)

Step 4 / Resolving
Trying to install KB3067505 vi MSU is not working because Not Applicable.
So we need to find a way to add this KB to the manifest – which is pretty easy when you know how to do it:

1. Put MSU in C:\TEMP
2. expand {updateName}.msu -f:* C:\TEMP
3. DISM.exe /Online /Add-Package /PackagePath:C:\TEMP\{updateName}.cab

Now, you can reinstall the update original KB3000483 and it should work!