You really have to understand your network environment going into it. You can't second guess it. You have to provide them with as much information as you can about your bandwidth, the server environment, the number of users, and where those users are located. A lot of those things needed to be right-sized, which just wasn't done upfront.

In a couple of instances, we had a little bit of trouble in getting it distributed throughout the organization. We ultimately managed to do it, and that was a little hickey, but we didn't have a problem otherwise.

In terms of the implementation strategy, we had a four-phase approach. We called it the four Ds. The first was Discovery. So, we had to go through a discovery process to determine things like:

• What is the key functionality?
• What are we looking for?
• What areas of solutions do we want it to fit in? 

We then had to discover what companies might be out there. We went through an analysis of companies. We did discovery.

The second phase was when we made a decision to work with Code42. We sat down, and we did a design session. We created an architectural design at a high level, and we talked about the outcomes that we're looking for from the standpoint of:

• Policy
• Technology
• User profile
• Acceptability
• Ease of use

We had all that designed in, and then we did the actual development. We developed all the charts. We used the standard waterfall project management implementation strategies or incorporated SDLC. We did all the things you would do for standard project management, such as critical path, key stakeholders, etc. All that was done in the development phase. That's when we actually onboarded the technology on our server environment. We then worked up a test scenario and did deployment, which was the fourth D. We did deployment on a group-by-group basis. We didn't do a big bang or everybody at once deployment. We took a subset of users from a department, and we implemented it in a department. We went to another department, and we implemented it in that department. We scaled all the way through. The first department we worked with was security. We implemented it within our own security team, and then in IT in general. So, we did security, IT, marketing and sales, HR, finance and administration, and then overall operations was the way we implemented it.

Code42 has a relatively simple deployment with an all-in-one sort of feel. It's simpler than deploying a lot of the three-tier solutions in the market. 

Although the initial setup was complex with a global reach and multiple policies for different business unit, Code42 stepped in to assist with the setup which helped make it straight forward.

There was technical complexity to configuring server IPs and ports. Deploying to the endpoints was much easier than expected because the user's could self-service a portion of the process and it was integrated into AD (via ADFS).

Super straightforward. Literally click a couple buttons and its up and running.

Extremely straightforward. I've installed on Linux (~30 minutes) and on OS X Server (~20 minutes), both are

The initial setup was not very complex for our deployment. Our assigned engineer walked our systems team through the configuration, we pushed the clients out and they began connecting with little fuss.

Even though the initial deployment was to almost 1000 users, it was very straightforward. That is one of the selling points of CrashPlan is that it is very easy to configure and deploy.

I actually enjoyed many facets of the deploy process because of its simplicity. The package customization process, specifically, is very intuitive.

Setup was mostly straightforward. We did have some issues with AD integration, but were able to get those resolved quickly. It took some time for us to understand the order of file inclusion and exclusion getting applied. The rule of thumb is exclusions run last so whatever you have in exclusions will never be backed up. We were trying to include a folder inside of a folder that we had excluded and could never get it to back up. We had to very carefully tailor the rules to get exactly what we wanted.

It was straightforward to install and setup. The client is not bloatware and the backend is modern and clean. No unusual performance issues.

I have no information on this topic.

Initial setup was straightforward. Download the software. Run the software. Configure the software. Let the backup run.

The initial implementation was not complex at all. It was very quick and extremely straightforward to install within the scale-up.

The initial setup was quite easy as we had a Code42 champion helping us the entire time. They help us by being a sounding board for our questions and getting us info for things like SSO and customizing the installer for our department.

Initial setup was very straightforward; simple server installs, and it's just a matter of pointing CrashPlan to a storage target and the app takes care of the rest.

A dedicated customer engineer was assigned to us for the initial setup. He was very knowledgeable of the entire product. He basically walked me through the setup of the organization and configurations. He was willing to take as much time as was needed to set us up.

I was less involved with the setup, but from my point of view, it seemed pretty simple.

Initial setup was very easy and we worked with professional services, so they handled 99% of it. We went to backup everything, excluded stuff we knew we didn't need, then fine tuned it more as we went along.

It was very simple and straightforward. Nothing complex about it.

The setup was very straightforward; probably the easiest we've ever done. We the support of our engineer and the design of the product. We literally kept repeating the phrase, "That's it?", in regards to that's all we had to do; it was so simple.

The initial set up could not have been easier. Both the server side and the user side were very easy to set up.

Software was very simple to deploy. Changing a few variables on the install and then adding the datastore. Pushing out clients was very easy with an MSI deployment.

The initial set up was smooth. As mentioned, we were noobies and were able to implement on our two campuses without issue. Set up / installation was simple. We are a small staff and the network was easy for us.

The setup was simple, basically Next, Next, Next, Finish. There's nothing major to configure and most of the out-of-the-box settings are already optimal.

I have configured Crashplan at my home without any trouble at all. At work, I enlisted the support team to help me configure our setup because I needed to be sure it was done correctly. They saved me a bunch of time

It was a little complex due to our having 9 offices and a central console to manage all the sites. But we were able to work through it and it was worth it.

It is a wonderful relief to know that user data can be backed up to or restored from the cloud from anywhere there is an internet connection.

Setup was a breeze. The documentation was very straight forward and if you just follow the steps it just worked. I was concerned that most companies do not lean towards using Linux however they do.

The initial setup was very straightforward and very easy to install. There were no problems. The process was very simple.

Setting up CrashPlan was easy from start to finish. My users do their own installations.

Initial setup was straightforward, but we luckily have in-house knowledge to set up external access to the internal server for backup purposes.

It was very straightforward as it's a very easy process and gives you a lot of flexibility. For example, you can schedule it with the client or push it out with group policy.

So easy - The PRO team showed us how to install CrashPlan on Red Hat Linux Enterprise and it was so easy. They have a great team to help accomplish a flawless install.

It was very simple and straightforward, though we did end up using all three versions before we found the right one. Home, Pro, and PROe - we're on PROe now. It was a case of we wanted more features, not complexity issues.

The initial setup of the dashboard, and then of the clients was straightforward and very low stress. Once we got the deployment sorted out, we've never had a complaint!

It was straightforward on the setup. We did have their professional services group help us with the install, but it did not take them that long to set it up and was around $500, which I did not think was a bad deal.

Very simple.

It was a little complex but with the assistance of the code 42 engineers things were very smooth.

very easy

Straightforward. You take a computer, install the server application, and public the port. Everything else can be done by the end users without issues.

The setup was quite easy. It was a Linux deployment that we have since moved to Windows.

No.

straightforward

i was not during the initial set up for the server but when i set up new customers is really straighforward basically we install the software , enter the license on our side then just go next and set up the account with the user and password and just entered the proserver ip and connect thats really about all we do , is really easy to set up.

It is complex but Code42 provides a dedicated service engineer to help.

Initial setup was very easy.

Setup could not have been much easier. 

Setup was straightforward and relatively painless.

The initial setup was not to difficult, it has taken some time to master the web UI functionality and problem troubleshooting. But thanks to the documentation and the tech support I solved every problem.

Deploy really is simple, but it's true what everyone else is saying, the cost is prohibitive for some people without a fair amount of negotiating and bargaining.

This solution was already installed by the time I became involved with my company. 

It was straightforward.

very straightforward

Very straight forward, it took no time for the solutions architect to throw something together for us.

It was very straightforward. Very simple to install: install the management console with some light configurations. Then install the agent on the endpoint and enter the account name and registration code and you're off.

Straightforward, I had a rep stay on the phone with me and help.

Was not present for the implementation of the software, but setup of the Clients is easy and straightforward. Could not be any simpler than logging in.

We required a custom solution so it was a little difficult. Without a deployment tool the client was challenging to automate the install.