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

We implement the solution for customers. 

The implementation is completed in-house by our team.

Citrix Virtual Apps and Desktops is a decade-old technology. We don't need any consultants to set it up. Any candidate with five to six years of experience should be able to set it up. We analyze the applications, the customers, and the users. We also consider the type of user base and the type of applications, and then we plan our infrastructure to meet their requirements and do a POC before deploying the solution. Considering Citrix Virtual Apps and Desktops is a 24/7 uptime solution, we need at least six technical staff for its deployment and maintenance.

The implementation is completed in-house.

The implementation strategy is always very simple, though people often confuse deployment strategy with mere installation. 

Before deployment, it's crucial to understand the business use case for deploying Citrix infrastructure. This involves assessing what type of users are involved, whether they're suitable for VDI, and if there are any within this user base who cannot use VDI and instead need physical laptops. 

This assessment covers their profile needs, required bandwidth, and resources. After this assessment, a testing phase, followed by a pilot, should be undertaken before a full rollout. This thorough approach is essential; without it, many customers face issues.

Therefore, the timeframe truly depends on several factors, such as the type of applications, the number of servers, and the number of users involved. So, it really varies.

On average, it might take around eight weeks. A lot of resources would not be needed if you have the right resource or a team with the right skill set. They would be able to deploy and scale it very easily.

Citrix itself doesn't require much maintenance, but it's important to have people with the necessary skill set to identify issues related to other components like networking or storage.

Getting access to Citrix DaaS took a while, but installing the solution took five to ten minutes. Just one person is enough for the solution's deployment.

We recommended a partnership the first time we bought it from Citrix and Citrix. The partnership was closed several years ago, and the new partner could be better. It's not good. Now, Citrix has been bought by another company.

To set it up as I wanted, it took me one month. However, I don't do that as a job. I just did it as a hobby or for personal reasons, which are not my job. Then, I worked on it when I had the time, not all day. 

Our deployment took probably three months altogether, not very long at all. For Citrix Cloud, we had Citrix Consulting services come in and do that for us. We have always been super happy with Citrix Consulting services. They have such fantastic people. They have such huge talent on their bench. They help organizations, such as ours, do what we need to do in the Citrix space. So, we had them come in, and for three months, they implemented the product. It was super straightforward. Everything was documented. 

When it came time to hand that service off to our operational staff, it was super easy. The overhead of managing Citrix Virtual Apps and Desktops is way less than it was when we had our on-prem farm with Citrix. So, we are super happy with the ease of manageability and the implementation that took place as well as the professionalism and maturity of that implementation. Things went super smoothly, and we couldn't have been happier.

We have a dedicated IT department. They have a contract with Citrix and they're employed here. 

We did it ourselves as we're a Platinum Citrix partner.

In the beginning, we used a partner as an integrator to help us design the Citrix and implement the first part. We have been using a partner for maintenance and upgrades because we don't have the knowledge at this moment about the newest version of Citrix. 

As partners, we used Acidos to build our first version, then we used SecureLink. However, I don't think the Citrix partner aspect of SecureLink's company exists anymore.

We deployed the first bit with our partner. We did this with seven or eight system engineers to build and go through tests. That was the first version. Today, for Belgium and Luxembourg, we have only three system engineers to maintain and publish new applications.

We help deploy the solution to our clients. We are able to handle any implementations. We don't work directly with Citrix, however, we do work with another third-party company. The experience we had with the company, overall, was positive. 

The implementation was done in-house. 

The Citrix integrator we used was moderately helpful. They tried to help but they didn't have much experience with a cloud deployment. They were able to do on-prem fast, but GCP took them a lot of time.

We had help from a Citrix partner. From a project management standpoint, I would rate them at eight out of 10. The project management resources are not available from Citrix itself. They have to rely on partners and, sometimes, the partners also have to rely on the OEM.

We did it ourselves.

Implementation was completed by our in-house team.

We did our own deployment in-house with the help of one or two staff members.

Ongoing maintenance and support is generally required since there are multiple users, many of which are using Microsoft Windows, and we tend to encounter maintenance issues about once a month. However, most of the problems we see are related more to the Windows environment rather than being the fault of Citrix itself.

While the centralized policy control and distributed enforcement work well, I wish we understood it better. I had a local engineer with Citrix certification build my farm for me. Since it was a brand new concept for me, it was very difficult to grasp at first. He did some preliminary training for us: How to admin it, how to update, how to make things run. But I am in no way an expert on the back-end. If I was able to take the time, which is kind of hard, to learn how all of the nuts and bolts work, I could improve the user experience a little bit. It's a lack of knowledge from my side.

From start to finish, our deployment took about two weeks, and that was mostly because the engineer could not dedicate his full time to me. It was a couple of hours here and there. Overall, the time billed was about 20 hours.

We built the servers, we tested the servers, and then we pushed them out to the handful of attorneys who had requested the ability to work from home. Then we fine-tuned it from there. I really let my users be my test-bed.

Any maintenance is done by me, but it requires minimal maintenance, mostly upgrades.

Our own in-house team made the full implementation and operation as well.

We have a teamed on seasoned Citrix Consultants, specialists in their chosen field covering off the complete Citrix Product Suite from XenMobile, to XenDesktop

The implementation was done in-house mostly, however with the design considerations we approached Citrix for assistance and to confirm whether or notour design considerations were following best practices. One thing to consider when implementing Citrix and a set of policies is that if it is a big environment, you are deploying, please ensure that the person or team that's doing the design knows what they are doing. Citrix works marvellously when properly configured but if not, you will find a world of trouble trying to make it work as you want.

For implementation, my advice is if you are designing a big environment contact Citrix Professional Services. If you're not sure on some aspects of your design, and have a CCE-V in your team, this is the key person to contact when doing a design for a large environment - 5000+ workloads for desktop or server.

Implementation varies from company to company. If you have more than 10,000 users in your company, I prefer to perform implementation in-house.

I do not use other resources for implementation. I do it all myself as I am a partner and reseller.  

We used a vendor team and they were excellent.

We used Citrix’s professional services for the engagement. While they were very easy to deal with and tried to accommodate our design, I think they were still new to their roles.

It was a hybrid implementation. Design was done by vendor and implementation was done jointly.

We had a third party, the supplier, do the initial implementation for us.  

We did everything in-house. Since we have the capabilities in-house for such projects, I prefer to go through an implementation, at least as a functioning demo, before hiring outside contracts. In our case, we were able use the functioning demo we built.

The XenServer piece was done by a VAR from the RFP process. The original plan was for them to also do the XenDesktop piece but, as I mention elsewhere, while they were familiar with Virtual Iron, they were not familiar with XenDesktop and did not wish to undertake it. They subcontracted it to another installer, who tried to set it up but didn’t get it done past the problems I mention elsewhere. Then another VAR took a shot at it, but also couldn’t fix it. I spent a lot of time studying, learning, and trying to fix the issues and found the hardware problems and fixed them. But it still didn’t work properly. I finally bit the golden bullet and paid the price for a Citrix gold partner who rebuilt the XenDesktop installation correctly and taught me at the same time. From then on, it worked beautifully and met our vision. But that first 1.5 years was a bear to wrestle.

Implementation was done in house. My best advice if you are migrating from another product to XenDesktop would be to deploy new VDI’s and migrate the users. This allows you to validate the stack and avoid legacy configuration and applications that might have issues. If that is not an option, researching what the VDI’s have installed, and what other remoting technologies are in use, will prove valuable and avoid some of the pitfalls that we had.

I have a lot of experience with third-party consultants and of course Citrix vendors. I have Citrix Architect Certification, so I have implemented my own solutions, but for big projects, it's much better to count on Citrix itself.

We used a mix of a vendor and an in-house one. The vendor was excellent, and they advised on the right architecture for performance and scalability, so I would give them a 10/10.

We used a mix of a vendor and an in-house one. The vendor was excellent, and they advised on the right architecture for performance and scalability, so I would give them a 10/10.

Our in-house team deploys this solution for our clients.

In-house application deployments are not always easy to integrate, because it is not always compatible with client-server environments.

Citrix Mexico helped us understand some issues, but mostly it was developed in-house.

We deployed it with the use of one consultant.

The product was implemented by a solution provider along with the server hardware as part of the project.

We implemented the product to check the feasibility and acceptability of VD in our organisation.

We implemented it in-house. It's easy with support.

We deployed this solution using our in-house team.