I rate the initial setup a six out of ten. With deployment, policy push doesn't take time, but the next level in terms of encryption takes a while. The time taken varies depending on the type of processor, type of device, version of OS, and how much disk encryption time it takes.

The solution's initial setup was straightforward for me, who has worked as an IT professional to date.

The deployment model for the solution consists of not just the machine but also it is deployed in the cloud. Hence, it follows a dual-deployment model.

We found the initial setup to be very simple and straightforward. It's not overly complex or difficult. 

We've used it for about three months and are still doing tests. 

We have 25 to 50 people that are handling the deployment and maintenance. They are our engineers. 

There was a team that handled the deployment. The process was straightforward. It is easy to deploy and install. It also doesn't take too long to implement. We don't deploy it centrally. Our team contacts the end users of sensitive endpoints. For future mobility, the strategy is to ensure all users in the future will have this on their laptops. 

We have about five admins to handle the maintenance of the product. 

The setup, like any other, was done at a corporate level. We are using it because we are licensed to Microsoft. It was a requirement to use all Microsoft products.

Initial setup was straightforward. 

The initial setup is pretty simple. You might have to do a bit of education in terms of understanding the logic, however, after that, it’s all very simple.

For the actual deployment, basically, I did it in pieces. I did the initial deployment on my laptop. I had raised queries with Microsoft Support for this. Once I got the basic settings in place, I stabilized this as my policy, and then I drove it out to all my users.

The initial setup is very easy. If you want to use BitLocker on the system, different steps are involved. If you only want to encrypt external drives, it's easier, especially if the external disk is blank.

The initial setup is straightforward. It involves leveraging our SaaS platform, allowing the backend to be subscribed.

The initial setup is quite simple. Deploying BitLocker took a relatively short time since we had a tech expert familiar with it. We had less than 20 laptops to secure, and the deployment speed was impressive. With the technical guidance in place, they could deploy it on about five to ten laptops simultaneously in a single day.

Microsoft BitLocker's initial setup is extremely simple.

BitLocker is pre-installed on Windows Pro, so you only need to switch it on. It takes a while to run, but you can switch it on and go do something else. It takes a minute or so to find it in the settings and enable it. 

With newer versions of Windows,  the initial setup has become better. It was a challenge with Windows 8 because you needed to first put the TPM in a certain mode and things like that. Where Windows 10 or Windows 11, once we enable BitLocker, it could be straightforward. So, there's been a lot of improvements in that.

The initial setup is straightforward.

The initial setup is not complex.

The solution’s initial setup is straightforward for an end user.

The initial setup was straightforward; very simple to install and modify from 128-bit to 256-bit encryption, 256-bit being the government standard for "Top Secret" information.

The initial setup must be easy, but I couldn't understand the process. Some devices can automatically activate it. However, the documentation makes it seem like a complicated project to deploy. I would like to understand clearly how it works.

We have it on-prem, and we have a couple of devices in the cloud, but we are a hybrid environment. Our main thing was to get it on our traveling laptops and protect them. We push it through another vendor, not Microsoft. We push it through another SolarWinds vendor, and then we push it down. The only thing that we've had problems with was that the encryption level wasn't as high as we needed it by default. So, we had to do some tweaking to get the correct encryption level that we wanted. It is all default. So, you have to be aware of how you deploy it. If you deploy it one way, it doesn't really fully encrypt the machine.

It took days only because it was a slow rollout. It was intentionally a slow rollout. It didn't take long to do it, but we just wanted to make sure it was done right and correctly.

We deploy the product in the client’s environment using group policy configuration. It takes a week to complete the process.

The tool's setup is quite difficult I would rate the tool's setup around three to four out of ten. We had to deploy the solution on thousands of machines. Hence, we implemented it in phases. 

The initial setup is straightforward.

The initial setup was very simple.

We expected that the devices had to encrypt themselves once we initiated BitLocker.

Deploying them and having the encryption run only took a few days to implement. This was all being done in the background and no one was impacted while they worked.

We only need one staff member for deployment and no one for maintenance, as it is auto-updating from the Microsoft Cloud.

I have a very small project and I implemented Microsoft BitLocker using GPO. Previously, we deploy Microsoft BitLocker using MBAM.

You can do a silent remote deployment very fast.

I didn't handle the initial setup. It would be impossible for me to discuss the process or to talk about if it is difficult or straightforward. I didn't handle any aspect of the implementation.

You need to know the technical aspects and have a good understanding of Microsoft Client/Server OS. If you know that, then yes, it is pretty straightforward.

The initial setup is not difficult. You can set it up using policy levels. The pilot testing took less than one week.

It is usually based on the number of computers and how this will be leveraged by the user. A normal project takes from one to two months, depending on the numbers. These numbers are read on the different departments and different mindsets of the users, in order to convince them to start correcting their data and explain to them that you will force a policy that will have an impact on their laptops. Afterward, encourage them in how this is chiefly for them. Usually, it takes a month or two months maximum.

The initial setup is easy and takes approximately one to two days. A day for implementation and a second day for compliance.

It is very easy to set up and deploy Microsoft BitLocker.

You have to set up the central server, and the configuration may take a day or two. After this, all of you have to do is go to every employee and then launch it, after they choose a personal PIN.

I had some technical issues with one of my deployments, but everything was working properly by the end of the first day. My issues arose because not all of the PCs had an updated version of Windows 10, so it took me some time to work out how to do the upgrades properly. It is important because TPM 2.0 is not supported in Legacy. 

That was the very odd part of the solution, and what we needed to do was to make sure that all of the PCs had the same type of Windows license. Once this was done properly, most of the PCs could be encrypted at the same time. It still required going to every PC though, because each needs to be given a PIN and configured. This was a disruption to some of the employees and it would be better if IT had total control, being able to do this from a central server and then simply notifying each user of their PIN. If there were one thousand employees then this would take a really long time.

I rate Microsoft BitLocker's deployment a seven out of ten. It is straightforward and is a matter of following guidance. You need three to four resources to handle the tool's deployment. Deployment takes around a week and a half to complete. 

The initial setup is easy. 

It’s not a straightforward setup. It’s a bit complex.

While I did not personally set up the solution myself, it's my understanding that the process is not overly complex. My colleague managed the process, and for them, it was quite straightforward. They didn't run into any issues. A company, in general, should be able to do it quite easily.

The initial setup is a bit complex. It works on Windows, yet it may not be compatible with other operating systems.

We deployed the solution over the last eight months. We keep getting more customers and continue to implement it. 

We also manage the solution for the clients. 

The initial setup is very simple. I would rate it a five out of five.

It wasn't complex. It just took me a while to figure it out and make it do what I wanted it to do. Everything is documented, and you just follow the documentation.

It is deployed on all new computers, and it is part of the build. It doesn't take very long. It takes only 10 or 15 minutes. While the disk is encrypting, you can do other things.

The solution's setup is straightforward. We required a team of three people to manage the tool's deployment. 

The initial setup for this solution is straightforward. We needed to change the group policy setting.

The initial setup was a bit complex.

The initial setup is straightforward. 

The initial setup is simple. You have the task of turning on the TPM of all computers before attempting to use the BitLocker. When using MBAM + SCCM + SQL it is important to have a CA root in your environment to issue the digital certificate to the MBAM.

Engineering and testing took about 10 days and was medium level complexity.

We have our own in-house team for maintenance.