The initial setup was straightforward and took three months because the client had a problematic environment.

We have deployed One Identity Safeguard in a phased manner. We deployed it for one line of business first, then for the second line, and we are planning to deploy it for other lines of business as well. The deployment for one line of business took approximately one month.

The deployment of One Identity Safeguard solution has been ongoing and is still under development. We are still deploying new changes, and it takes around three to four weeks.

The deployment of One Identity Safeguard solution has been ongoing and is still under development. We are still deploying new changes, and it takes around three to four weeks.

The deployment of One Identity Safeguard solution took one or two days.

The deployment of the solution takes about two to four weeks, give or take, but that's not counting waiting for the client to respond and all that.

Initially, we faced a complex implementation that took about two months, but after that, we achieved a stable configuration and environment for user access to critical systems.

It took about a week to set up the appliance itself and configure it, but we are talking about maybe a year to get everything configured the way we wanted it for the initial phase.

The deployment took three phases: first, I got support from the vendor for integration, second, I deployed across all users, and finally, I identified any associated risks.

The deployment of One Identity Safeguard took around three months.

The deployment of One Identity Safeguard took less than two weeks to fully implement and use.

The deployment of the solution took less than one month for my organization.

The deployment of the solution has taken less than one month, and it was a great experience. Regarding deployment, we have not faced any disruptive issues; it was very smooth for our privileged users, and after a short initial adjustment, they were able to access the system through One Identity Safeguard without issues, thanks to training and clear communication that minimized disruptions.

The deployment of One Identity Safeguard took less than one month.

The deployment of One Identity Safeguard in our organization took approximately four to six weeks end-to-end. The initial setup and basic configuration was completed within the first week. Integration with systems such as Active Directory and initial onboarding of privileged accounts took another one or two weeks. The remaining time was spent on policy configuration and session management setup, testing, and user onboarding.

The deployment of One Identity Safeguard in our environment took approximately four to six weeks. The initial setup of the physical appliance was straightforward, but the overall implementation required careful planning, especially for integration with Active Directory and onboarding the target systems.

The deployment of the solution took around two to four weeks due to initial setups, integrations, and policy configurations.

The initial deployment of One Identity Safeguard on virtual appliances took roughly six to eight weeks end-to-end, including planning, setup, integration, and user rollout.

The initial setup of the virtual appliances and basic configuration was completed within a few days, but the overall deployment, including integration, policy setup, access workflow, and testing, took a couple of weeks to fully stabilize.

Deployment of One Identity Safeguard in our organization took approximately a few days to a couple of weeks, including installation, configuration, and integration with Active Directory and internal systems as well. Most of the time was spent on testing and ensuring proper access policies were applied.

It took about one to two weeks for deployment of the solution.

The initial deployment of One Identity Safeguard took a few weeks, including setup, integration with Active Directory, policy configuration, onboarding asset accounting, testing, and user access validation. The timeline mainly depended on the environment size and security requirements.

The deployment of the solution took around one to two weeks.

The deployment of the solution took up to one month in my environment.

The deployment took around four to six weeks in our environment, including initial setup, integration, policies, configuration, and testing before going live.

The deployment of One Identity Safeguard took around four to five months.

The deployment of One Identity Safeguard was not a one-day or one-week activity. It was more of a phased rollout that took a few weeks to a couple of months overall.

The deployment of One Identity Safeguard took approximately two to four weeks, including planning, Active Directory integration testing, policy configuration, and phased rollout across Linux and UNIX systems.

For us, it took three to four months because we had multiple layers of negotiation regarding pricing and licensing.

The deployment of One Identity Safeguard in our environment took around two to four weeks, including planning, Active Directory integration, Linux server onboarding, testing, and phased rollout. The core deployment was manageable, but troubleshooting authentication dependencies such as DNS, Kerberos, and SSH configuration took additional effort during implementation.

The deployment of One Identity Safeguard took approximately four to eight weeks, including planning, installation, integration, and fine-tuning.

The deployment of One Identity Safeguard took three to seven weeks.

The deployment of One Identity Safeguard took approximately two to three months from initial planning to full production rollout. Most of the time was spent on requirements gathering, onboarding critical systems, configuring access policies, and testing workflows.

The initial deployment took almost three weeks. Most of the time was spent on planning, configuration, policies, integration with other existing directory services, testing privileged access workflows, and validating session recording before rolling it out to the administrators. Once the initial setup was complete, onboarding additional systems and users was relatively straightforward.