IT Central Station is now PeerSpot: Here's why
Buyer's Guide
Application Virtualization
June 2022
Get our free report covering Microsoft, Citrix, Numecent, and other competitors of VMware ThinApp. Updated: June 2022.
610,045 professionals have used our research since 2012.

Read reviews of VMware ThinApp alternatives and competitors

Director System Integration at a computer software company with 10,001+ employees
Real User
Top 20
A mature product and an industry leader with great application virtualization
Pros and Cons
  • "Citrix is one of the companies that is delivering virtual apps and desktops in a big way. They are mature enough to understand the level of stability required and deliver it."
  • "If Citrix can develop something which can have more reach towards the backend infrastructure, other components of the Citrix environment, that would be ideal."

What is our primary use case?

For virtual desktops, like Windows 10 or Windows 7, we primarily use the solution to offer some customized applications to the users. 

Some of the basic applications, like Windows applications, are being used across all VDIs. 

The usage depends on the specific customer. They decide what applications they want to have in their VDI. We have certain items as far as their requirements, and we just manage the infrastructure in the background.

What is most valuable?

Citrix tends to have the most capabilities surrounding desktops.

The application virtualization is very, very good.

What needs improvement?

The customer is always looking for a unified solution. They need a single place where everything can be managed from while using a web application. With Citrix's system, there's an administrative tool and a helpdesk tool. Those two tools are very different, and the Citrix administrative tool is not meant for web-based use. It's in a heavy application. If they could build it into their web-based applications, that would be ideal. That way, administrators can log in from anywhere on any browser and they can just manage the environment in the background. 

Citrix does not have an in depth assessment tool. Some customers ask for components in Citrix that can give information around the hypervisor's resources or in-depth metrics of the hypervisor's site. There is a free tool from Citrix, however, it does not give you the deeper information of the other components like hypervisor or the OS or the storage, or downloads in the network. Those are the limitations of that particular tool right now. We might need to use a third party tool to gain that information. 

If Citrix can develop something which can have more reach towards the backend infrastructure, other components of the Citrix environment, that would be ideal. 

For how long have I used the solution?

We've most likely been using the solution for over eight years at this point.

What do I think about the stability of the solution?

Citrix is one of the companies that is delivering virtual apps and desktops in a big way. They are mature enough to understand the level of stability required and deliver it. 

Now, they are moving towards the cloud and offering everything as a service. The redundancy part is already taken care of by the company. 

We have many components and have controlled redundancies. From the end-user side, a user won't see any disruption in the services. That's due to the fact that the infrastructure in the background is highly available. Elasticity is also introduced. We're always building provisioning desktops on-demand and shutting the machines that are not in demand. 

We have certain policies defined in the infrastructure in the background, which can enable our administrators to utilize the resources as they need them. Therefore, it's quite stable.

What do I think about the scalability of the solution?

We use this solution ourselves in our own organization and have a 60,000-70,000 userbase currently. We have more than 40 customers within the virtual workspace. Most are medium-sized entities. A few have 20,000-40,000 users. We'll be adding another client in healthcare that has about 20,000 desktops.

Scalability is not an issue. You can scale up to any number. There's only the requirement of adding the infrastructure and building that horizontally. You'll need to set up the different components horizontally. For example, if we have a 10,000 user base, then we can probably have 10 master servers. If the user base is around 40,000, then we can double the master servers so that they can take up the load.

How are customer service and technical support?

We often contact technical support.

They are very engaged, whenever we have an issue. They are very helpful. Most of the time, whenever we run into an issue where we need to reach out to Citrix they are available to us.

We do not support only Citrix. We also support the backend infrastructure and hosting infrastructure that are also Citrix products. If it's tied to another product, such as Microsoft, they'll work together to resolve whatever the issue is. 

We haven't found any difficulty in working with them. It's rare that we'd need to reach out to other vendors as well as Citrix (usually once in a quarter), however, if it happens, we know Citrix will do what they can to work with all parties.

Which solution did I use previously and why did I switch?

We do not exclusively work with Citrix. It's much more high-end than other services, however, we do also offer, for example, VMware and Horizon.

How was the initial setup?

The initial setup is very simple currently. Earlier we used to install many components separately. Now, we have a basic software installation setup. We can build the environment in a few hours. It does not take much time now. Earlier, we used to have to secure the servers, for example. It is all virtualized. One administrator can build the environment from scratch and in a very short period of time. It's not complex now. Earlier it was, but not anymore.

The deployment time depends on the sizing of the environment. If the customer is looking for only 500 desktops, it takes one day to build everything. If there is planning involved, and there are some different components or key bits and pieces that the administrator needs to collect, it might take a bit longer.

If it is in a scalable environment that's sized, for example, at 1,000, 10,000, or 20,000, it will definitely take time. This is due to the fact that we need to choose the appropriate technology for the background. We need to figure out if the customer's willing to have a provision desktop, basically. That all depends on what the customer size is and what the customer requirements are.

We also offer managed services, so we can help our clients manage everything once the solution is fully deployed.

What about the implementation team?

Our team can help implement the solution for our clients. That said, I don't handle the process directly myself.

What's my experience with pricing, setup cost, and licensing?

Citrix is competitive, however, at the same time, they give great service. VMware, Horizon, or other VDI solutions may be cheaper. That said, they do not have the same capability that Citrix has. 

We offer other VDI solutions like Microsoft WVDs and the VMware's Horizon, that are on the cheaper side. It's up to the customer, what they want to do. If they want to have premium services, we will host their VDIs on Citrix system components only. That will give them better features and better capabilities or maybe less frustration on the user experience side.

We offer cloud and managed services offerings as well as environments hosted on our data center. We have a variety of options and therefore can offer a variety of prices according to what they need/want.

What other advice do I have?

We're currently using the latest version of the solution.

While we mostly work with on-premises deployments, we also occasionally handle cloud deployments as well. 

We have our internal Cloud offering. Form there, we have a managed data center and within our company's premises, the customers are just subscribing to services based on their need for virtual desktops.

I would recommend the product. It's an industry leader in the VDI environment. Nobody can match their capabilities right now.

I'd rate the solution nine out of ten overall. If they had better capability testing, I might rate it higher.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Application Integrator at a financial services firm with 1,001-5,000 employees
Real User
Top 10
Stable, scalable, easy to install, great support, and it upgrades and deploys apps easily
Pros and Cons
  • "The most interesting and powerful feature for us is the fact that we can upgrade any kind of app instantly."
  • "The downside is that Microsoft bought this product and they are going to discontinue it in 2026. This is worrisome for us."

What is our primary use case?

We are integrators. We integrate this product.

We use this solution to deploy applications to end-users in a very fast, secure manner, and in an isolated container.

What is most valuable?

The most interesting and powerful feature for us is the fact that we can upgrade any kind of app instantly.

We like that we can deploy apps, both globally or per-user.

Also, that the applications follow the user. For example, if the end-user connects to a different station and the application is published for him, the application will follow him no matter where he is.

We can run scripts on different triggers for when an application is published, unpublished, or when a package is added or removed.

It's very flexible.

What needs improvement?

The downside is that Microsoft bought this product and they are going to discontinue it in 2026. This is worrisome for us.

I would like to see them continue to maintain the product. From my point of view, it reached a maturity where we can consider it to be perfect.

If we wanted to be picky, Microsoft could improve the synchronization of the client. We were forced to put our own PowerShell script, which mimics the built-in functionality of the syncing. It would avoid errors.

Another feature that has not been implemented, but would be nice to have is the possibility to publish different shortcuts within the same package, to different groups. 

There is a solution in place, but it's not really working. If you have two different groups on two different shortcuts, everything works fine, as long as you don't have a common set of users in those groups. As soon as you have one user in both groups, then the client won't know which one to publish, and it is not able to do a merge between those two settings.

I would like the synchronization improved and to have the possibility to publish different shortcuts to different groups within the same package.

For how long have I used the solution?

I have been using this solution for a very long time. Since the time that it was still SoftGrid.

We are using the latest version.

What do I think about the stability of the solution?

It's a stable product.

What do I think about the scalability of the solution?

It is very scalable. We have approximately 4,000 users.

How are customer service and technical support?

From my point of view, the interaction with Microsoft support was great. 

Actually, at one point in the past, they were delivering patches just for us. So I think they're great.

Which solution did I use previously and why did I switch?

Before Microsoft App-V, we had MSA, which is still a great product. 

The disadvantage of MSA is that it is difficult to deploy compared to App-V.

You need to perform an installation on the user's computer in a timeframe where the user is not there. 

Everything runs in the system account. You have conflicts with other apps because everything is locally installed, with MSA being the main installation engine, in MSA through SSCM. 

I believe that they are trying to put MSA X in place, which is not very good, but MSA would remain the main way to install applications.

How was the initial setup?

If the installation is on the client it is a part of the Windows 10 Operating System.

If it is on the server-side, or publication, it is straightforward. Depending on the complexity of your infrastructure, there may be some configurations to do.

In theory, for a small company, it is straightforward. You deploy the setup and that is it. For a normal infrastructure, with a publication server, management server, and reporting server, this can be done in five to six hours.

A more complex infrastructure, where you need to load balancers and multiple servers, with test and production infrastructure, it can take up to one month. This is not the installation itself, it's the normal workflow so that you make sure you don't impact end-users.

We have a team of five that includes one manager, three packagers, and one admin to deploy and maintain this solution.

What other advice do I have?

I have a lot of experience with Microsoft App-V and VMware as a normal user. I'm not managing the infrastructure, and we do a lot of publications through Citrix.

We use it on-premises and I am not aware if there is a cloud version for App-V.

This solution would be suited for big companies with many users. A normal user at home would never use this product. 

In the current context, since the end of life has already been reached and we are at the extended end of life, I wouldn't recommend adopting this solution.

With this critical exception, Microsoft App-V is a great product.

I would rate Microsoft App-V a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Buyer's Guide
Application Virtualization
June 2022
Get our free report covering Microsoft, Citrix, Numecent, and other competitors of VMware ThinApp. Updated: June 2022.
610,045 professionals have used our research since 2012.