Does Microsoft Buy Citrix?

I had a discussion with a colleague yesterday about what is happening with Citrix on a long term. My answer was Microsoft will buy them! Why? There are multiple small pieces that if you put them together the picture might look like that

1. the new Citrix CEO Kirill Tatrinov was originally working for Microsoft. Did you heard already anything from him? I did not hear any noise except that his Synergy keynote was not very well received. Maybe he is not really interested in keynotes because he is preparing something else?

2. Citrix sold all departments, that are totally not interesting for Microsoft like the whole online stuff. Microsoft already has products in this area that would compete with this – like skype for business vs gotomeeting.

3. Microsoft retired TMG – so they have nothing at the endpoint to the internet – their new strategy is cloud first, mobile first – would not netscaler fit perfectly?

4. Server 2016 has not much additional features announced for RDSH, it is an optimized gateway that host more users (indeed I heard they found a bug), multipoint server, OpenGL Support. That’s pretty it – so probably they just don’t develop that much anymore.

5. ARA – Azure Remote App is lacking management for larger environments – the citrix cloud products allow this (they anyhow already run on Azure)

So – I am curious what will happen in future!

Does Microsoft Buy Citrix?

AppDNA AND APPv Part 1

Probably a hidden feature in AppDNA is the possibility to create App-V packages. This can happen full automated. Honestly I don’t see AppV in general as an OS Compatibility mitigation technology. From my perspective if solves interoperability issues and migth ease deployment.

But if you are allowed to use AppDNA probably is is even a cool solution to optimize your current packaging process. What you need:

– AppDNA Server
– A VDI sequencer machine
– A VDI machine with an App-V Client
– Service Account with local admin rights on the machines
– a service account that can control your VDI on the hypervisor (Create snapshot and revert)

What you need in the first step is a hypervisor and a virtual machine. AppDNA will use this machine to create the sequence but you can still interact during the sequencing process if you want. Prepare the following for step 1:

A vritual machine with an installed sequencer, the “Citrix AppDNA VM Configuration.msi” needs to be installed. This tool will allow the AppDNA server to talk to the virtual machine. Because the agent is embedded in the RUN key you should also enable Autologon probably with the same named sysinternals tool. This will allow, that the agent starts after AppDNA resets the machine in a later step. Also don’t forget the standard cleanup tasks for your sequencer machine like disabling windows search or defender. Create now a snapshot.

What you need then to do in AppDNA:

Configure –> Solutions –> AppV

Define a name for the solution


Define a network share (if you Test it tells you which files AppDNA would like to store there)


Here is the screen for defining the two VMS – the first is the sequencer the second a test machine – select “Add VM”




Define your hypervisor


The service account to manage your hypervisor


Select the sequencing machine


Select or create a snapshot and check “Do not show the VM Console”

After this step AppDNA will reset your virtual machine to the snapshot


Here you define the name of your virtual machine – you should use an FQDN. The port is the default port used by the AppDNA agent. If your fails probably the computer is not logged in or AppDNA reverted to the wrong snapshot (happened to me under certain circumstances – now I only have one snapshot)


Define the output file share


Select what AppDNA should do with your VM


Here you get the summary


Repeat this steps for the second virtual machine

You should get this then


Here you can chose no to speed up


Nearly ready


Define how AppV Packages should be generated.


You are ready – press close.

Now you can use use solution to sequence applications that were imported to AppDNA!


AppDNA AND APPv Part 1