Recently I was tasked to do a demo on Thinapp. I have a Windows XP SP3 32bit running with Thinapp version 4.x.
I did some thinapp on Internet Explore 7, 8 and 9. Everything was working fine.
Next I spin off a Windows 10 64bit VM and try to run these Internet Explorer thinapp'ed and I got the error below:
Did a Google search and came across information that Windows 10 can only support Internet Explorer 8 and above which I find that weird since Thinapp should be able to support to run as it's a packaged container.
Eventually, I chanced upon Thinapp release notes to discover it only support Windows 10 in version 5.2.0 and 5.2.2 recently support Windows 10 Anniversary Update. How silly of me not checking out my Thinapp version.
Upon updating my Thinapp on my Windows XP VM and using relink to update my Thinapp Package in the bin, it is now able to run in Windows 10. Yes, I do not have to run through the prescan and post scan all over with relink. Check out this KB to see how t…
Recently got into a requirement from a customer that a need for using vRealize Operations as a centralized monitoring and pulling in the metrics from other apps. This would need to cover physical and VMware virtual environment.
The first thing that came to my mind was to use vSphere Enterprise Plus and utilize the old vRealize Operations Insight which comprises of vRealize Operations and Log Insight. However, this bundle has EOA as stated here.
That was a bummer. As cost is a big issue, we cannot just quote vCloud Suite (vCS) Enterprise where vRealize Operations Enterprise is provided and App Monitoring will be covered. However, there are many components in it which my customer will not be using and cost does not justify it (though it would be nice for me :) but bad for my customer's pocket).
Just for those who ain't aware vCloud Suite just consists of vRealize Suite + vSphere Enterprise Plus. The editions of vCloud Suite is in line with vRealize Suite.
With vSAN 6.2, the support for ROBO site been introduced. There have been lots of questions regarding how do we license the witness in a more effective manner. Some of the thought in using vSphere ROBO licenses, vSphere Essentials licenses, and even free ESXi hypervisor.
Here this article is to explain the do-able methods that have not been very clear. Before we start, check out the vSAN 6.5 Licensing Guide.
First of all the common way to place the vSAN Witness are normally in a vSphere cluster. So this cluster is already licensed. It doesn't matter if its the lowest Essential Edition to Enterprise Plus Edition. So if you like to run this even using a vSphere ROBO license, this can be done since ROBO is meant for a small site, not more than 25 VMs. Do take note that, using vSphere ROBO, you will not be able to power on more than 25 VMs (assuming your license is 25VMs pack and has not been divided). You cannot combine the license. Even if you have a lot of hosts, you still…
Previously I have talked about the difference between an Open and OEM licensing here. Why OEM license are cheaper in general since they are provided by OEM vendor instead of direct from the Principle. This applies not to just software but also hardware although I used software as a subject in writing.
Following on the different support structure contact point between Open and OEM licensing here. Support are typically directly from OEM rather than from the original Principle vendor of the hardware of software.
Question why would OEM support cost cheaper than Principle support or why Principle support is more expensive than OEM support? Is it because the Principle owns the product (software/hardware) that makes it more expensive?
There are several reasons why OEM is less expensive if you do a study. Below is what I have observed:
1) Principle vendor owns the product, in such, it cost more. OEM vendors use their own support and only to a certain level will they have support from Pr…