So I saw a link to a company that has an interesting product for App Virtualization and I wanted to read more. I headed on over to AppZero.com and started browsing around to see what their product offered. As I am doing this I thought to myself that AppZero sounded a lot like NetZero. Then I noticed the logo for AppZero and quickly took a look at the logo for NetZero. There are some shocking similarities and with the name and the logo being that close I thought they might be owned by the same parent but it does not appear to be so.
This doesn’t really matter much but it did remind me of a Brian Madden post on how he told Microsoft a new exchange logo looked an awful lot like his. Link
Just wanted to share this observation as I found a bit of humor in it.
Uncategorized
So last month I did a comparison test with MFCOM vs the new XenApp cmdlets. My intention was simply to see if the cmdlets had the same (or any) performance issues that plagued MFCOM. The results initially shocked me since MFCOM in VbScript seemed to be faster (albeit marginally) than the cmdlets. After posting my results one of the developers of the cmdlets made a comment that my testing method was off.
LoadData loads the app specific data (according to the app type), not its associations, which are more expensive to read (accounts, servers, etc).
This is why I suggested to compare it to Get-XAApplication. –
I had always been under the impression that LoadData() pulled backed all information about the application including Servers, Users/Groups. So I did a few tests and realized that I was completely wrong. When throwing a few for..next loops in to enumerate servers,users and groups the MFCOM time shot up by at least 10-15 seconds.
Felipe also suggest comparing LoadData() vs the Get-XAApplication cmdlet instead of Get-XAApplicationReport since the former does not make a call to obtain servers,users/groups.
Using this method the cmdlet obtained most properties on 100 applications in about 1-2 seconds..That’s FAST. On the flip side using MFCOM to enumerate the same application set (100) WITHOUT using LoadData() still takes roughly 5-6 seconds. There are a number of properties that are readable without using LoaData() but I have yet compared those to Get-XAApplication properties.
I plan to do more in depth testing when I have some additional free time but I wanted to post an update to show that my initial results appear to be wrong. As I stated in my previous post the cmdlets easily win for simplicity and ease of use but in my opinion until Powershell V2 is released (not as a CTP) and brings WinRM with it I think MFCOM is still the winner for multi-farm management. Maybe by the time the XA cmdlets go out of Tech Preview phase, Powershell V2 will as well?!
MFCOM, Tech
Recent Comments