They had an advisory team to help us in onboarding it. We got the consulting support. We had an individual come out. I don't know what his exact title was, but he was a senior consultant who had done multiple implementations in the past and was familiar with the product. He wasn't a junior guy by any stretch of the imagination. He knew the information he needed and he knew how to work with us. He was a pretty reasonable guy. He was around the first couple of weeks. He came on site for a week, and then after that, he came in every once in a while for about three months. By then, we had already done most of the heavy lifting, and we were into full-scale development and implementation. We would talk to him all the time, but he didn't come on-site anymore. I would rate him a five out of five. We thought he was really good. He was capable, and he was knowledgeable. He had a great personality. He wasn't high-minded or anything like that. He was a good guy to work with. In fact, he's still around today.

For the deployment, on the security team, I was the overall leader. I didn't work on it full time, but I was the overall leader of it. Then I had a security analyst from my team on it, and I had a security service engineer on it pretty much full time. As supplementary, I'd have a junior guy or a network analyst help out from time to time, but there were really about three people who worked on it throughout. There was also a project manager, but he was from the project management team, not from our team.

In terms of maintenance, there is a regular tuning. We pay for the software maintenance. There is software maintenance, but we tune it. Like everybody else, there is regular care and checkups to make sure that everything is running properly. If we see anything that's running amiss, or if we do a heavy patch load, sometimes, we'll pay closer attention to what's going on at the endpoint because of the patch load. It is not cumbersome for sure. Its maintenance is handled by the network admin. A security architect is also there from time to time, but it is mainly done by the network administrator. He may dish that out to one of his support people, but by and large, that's all that's involved. We haven't had to call Code42 for anything that we couldn't figure out.

We implemented through an in-house team with assistance from Code42. Given the relatively small nature of our deployments compared to others we have completed this was all we required.

in-house.

In-house.

One person in-house. I cannot imagine CrashPlan requiring much of an implementation team even in larger environments, it's bone simple.

We had a Code42 engineer assigned to us to assist with the configuration of the VM and the installation of the environment. After we installed a client and confirmed connectivity, we were able to take it from there and pretty much self-teach.

We deployed in-house. The initial deployment as about 1000 users and even though we did it ourselves, it was fairly easy and straightforward.

Because the deployment of CrashPlan was so simple, intuitive, and generally a fast process, it was conducted by an in-house team.

We deployed using an in-house team although a vendor team was available. We had done extensive work during our trial phase, so going live with that was relatively easy. Converting from the trial to live was so easy for us that it really was just a matter of applying the license key and then installing the clients on computers and storage servers.

We implement with in-house staff. We used assistance from Code 42 staff with developing some reporting capability that was on in the default set.

This was implemented through an in-house team.

An in-house team implemented it. It is just not that difficult.

Our in-house IT department (my associate and me) setup and deployed it to our users. It was a great learning experience as we have to maintain the system as well.

We implemented the solution through our in-house IT team. It seemed simple enough to not warrant the use of an outside service.

We implemented through an in-house team. Documentation was created for the remote installs that included screen shots and embedded links for software downloads.

We used Code42 to implement and they were awesome. They knew the solution very well and helped with customizing to fit our needs

In-house

We implemented it in-house. We had access to a dedicated engineer to walk us through and assist us. We were not transitioned away from our dedicated engineer until we were ready.

We did the implementation with our own team of 3. We were able to get our entire sales force of 150 on the application with relative ease.

Implemented through an in-house team. The only part which was a bit tricky was the AD/LDAP integration. The automated reports and monitoring are a click away.

We have an in-house team. Our level of expertise is higher now that we've worked with CrashPlan employees and understand the rationale behind the way the product is supposed to and intended to function.

We handled the setup, installation, and configuration of Crashplan fully in-house as our installation was very small and our needs were not complex.

I implemented Crashplan Pro E with the help of the Code42 support team. Their experience was exceptional. I remember telling everyone that would listen how great the software was.

We used our own in-house team to deploy the product. Each member of the team took a couple of sites and we were up and running within two months and that was with all of our regular work and chasing down users to install the client and establish the backup.

I installed and configured the server and deployment on my own. I did not feel the need to contract someone out to do this install. If I was to have any issues, I felt comfortable knowing that I could just pick up the phone and ask for assistance.

I installed and configured the server and deployment on my own. I did not feel the need to contract someone out to do this install. If I was to have any issues I felt comfortable knowing that I could just pick up the phone and ask for assistance.

We implemented this in-house. There was no vendor team that helped with the implementation. One of my technicians implemented this and had no trouble.

We implemented in house and had a quick setup with CrashPlan rep since we deployed the hardware in house with the CrashPlan software. I imagine most companies just use CrashPlan's storage in the cloud but we preferred to keep it in house.

In-house all the way.

No - we dealt with Code42 directly. I think that made our connection to Code42 stronger, not having a 3rd party vendor in the middle.

We used our own expertise in-house to install it, no issues were experienced, though our storage is from a network share and Crashplan did not want to backup to a NAS, so we had to trick it by mapping the CP storage as iSCSI and giving it to CP as a drive letter instead. Has worked perfect ever since.

We implemented CrashPlan with our internal Infrastructure team without any need for consultants or any outside assistance.

For the main server, we used Code42's professional services team and they were great to work with. The rest we did in-house.

Vendor team and in-house team together. Professional services expertise was excellent.

in-house

In-house

In-house only. It is easy to deploy, so you don't need any help. You may think about it if case of a very large deployment in a short time window.

In-house

In-house.

it was in house and they had been working with this solution for years that means they level of expertise is really good and they handled everything to us and the trainign was really a challenge but once you got it right is really easy to implement on any supported OS

In house with a dedicated service engineer doing remote sessions.

Implemented via in-house team.

We installed the product in-house.

I implemented in our server farm. We have not implemented through a vendor team, because the have the right knowledge and skill to do this ourself.

In-house.

We used an in-house tool to deploy, although any client upgrades come directly through the console.

In-house

In House team. We manage the solution as well in house. It's a very simple process that the admin console lends a hand to.

We did it with the help of the vendor. Their field engineer was very knowledgeable.