What is our primary use case?
We are helping our customers create secure and redundant networks. That's the primary use case.
How has it helped my organization?
It’s helped my clients. For example, we did multiple roll-outs. The other banks, bank branches, require good connectivity, which is very important for a branch to have. They managed to have an SLA of almost 100%. In the case of network failures, they had very few issues, and most of the links, since they were on a traditional network, used active-passive. However, with this product, they could aggregate the bandwidth and come up with new use cases. The customers are really happy.
What is most valuable?
They have a zero downtime failover mechanism, where, when there's a link failure or a link weakness, or bad link conditions, they provide the ability to fail back seamlessly. That's the most important feature I have worked with.
The initial setup is pretty seamless.
The solution is stable.
It’s scalable.
What needs improvement?
Right now, certain SD-WAN vendors work with very strong enterprise-scale firewall features. For example, Fortinet is what most of my customers prefer to have. However, in terms of Citrix, they had minimal features. Now, they have improved things. That's an area where Citrix has to improve since Citrix is not a security company. They rely on other vendors like Zscaler. Overall, network security and next-generation firewall features are areas that they can improve on.
For how long have I used the solution?
We have worked with them for around five years.
What do I think about the stability of the solution?
We haven’t had any real issues with stability. We put it in for countrywide operations, however, and we expected there would be a lot of returns. There are actually very few, and even these returns were out of Citrix's control. For example, we had a few appliances return back due to lightning and the resulting power surges. Besides that, we rarely have failures, so the client is happy.
What do I think about the scalability of the solution?
In my case, my geography is relatively small. I operate in Sri Lanka, Bangladesh, and the Maldives - these kinds of countries. Here, we don't have many installations over 1,000. That said, Citrix can very easily go beyond 1,000 branches and endpoints. They have large scalable models also. For my use cases, they are scalable enough.
The customers who are using the solution 100% rely on it, at least for the branch connectivity. They are not quite keen to use inter-data-center use cases, such as WAN optimization. However, in terms of my customers, they use it 100% in most cases. We have helped some customers to improve their application performance with this solution. Most customers ask from our side from a traditional SD-WAN whether they can move to a zero-trust network. It was the evolution of Citrix. We are helping and educating our customers, et cetera.
How are customer service and support?
Customer service is really good. We have had a few tech support cases. We had to do some version upgrades where we had some challenges. However, the tech support is really good. I have worked across many products, for example, for Extender Top, XenServer, et cetera. The Citrix team has been extra helpful.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
My customers used the traditional BGP routing base on a normal Cisco-based solution. So this is the evolution of new tech for them. They are moving from traditional interest to SD-WAN.
We recommend products like Meraki and Fortinet. Fortinet is good, especially for some hospitality customers. We find it quite interesting. In terms of Fortinet, the customers are really keen since their CPs are very cost-efficient, so they have a big advantage in TC when compared with Citrix. Especially Fortinet, people like it due to the security advantage, and Fortinet is influencing this market in terms of network security.
How was the initial setup?
Once we do the base configuration or the head setup and then the configuration, then we can send an L2 team to do the deployment with very few instructions. We ask them just to plug in the cables and download their profiles. It's quite seamless. My customers evolved from a traditional BGP environment. For them, this is quite seamless. They are happy, and the operational overhead is also lower for them.
For a single customer, the effort involved in the deployment varies. Maybe a five-man team could very easily manage the network since the failures are lower, and they also have this failover feature where even when the branch is down, they can still help the customer. Five or six people would be sufficient to manage and maintain everything. With Citrix cloud coming in and analytics help, you won’t need a big team. It's quite proactive, and not quite reactive. The number of people required is relatively low to maintain everything.
What about the implementation team?
We do the deployment ourselves.
What's my experience with pricing, setup cost, and licensing?
There are multiple pricing options. They have an MSP model also. However, we deployed the channel or the normal appliance model. Of course, it has been three to four years on the same price point. I'm not quite sure of the price ranges. Roughly, the hidden devices can scale up to $20K for one appliance. However, the branch CPs are USD $1,000 to $2,500.
We get everything under the list price. However, especially if you are thinking of having a branch internet breakout, then sometimes you might have to get another solution like Zscaler or Symantec for the proxy of internet security.
What other advice do I have?
I’m just an end-user.
I used to work for a Citrix partner, so we were the Citrix regular partner. Right now, in my present job, I'm not affiliated with them.
What we used is the on-prem deployment. They have certain companies on the cloud. However, it's pretty much on-prem for this solution.
Potential users should ask Citrix to give firm commitments regarding product life cycles and changes. Usually, Citrix is undergoing a lot of changes internally. Their product directions change, product names change, and many things change. So Users need to check, especially if they are modernizing the network.
I’d rate the solution seven out of ten.