The initial setup process was straightforward.

Setting up Symantec Data Center Security was easy, thanks to a smooth deployment process and a handy deployment file. But when it comes to doing tasks on the platform, it has been a bit tricky. The day-to-day activities aren't as straightforward and user-friendly as the setup process. Using Symantec Data Center Security can be tricky when repairs or updates require a system reboot. This is especially tough in production environments where interruptions are discouraged. Most companies use the product to protect servers, and the need for a system restart poses a challenge. In production, the time it takes for a reboot can be a significant headache, making it a practical issue for users. When deploying Symantec Data Center Security, I followed a systematic approach. Firstly, I assessed the tool's compatibility with peer requests and verified the support for our current setup. I also checked for any additional resource requirements. Prior to production, I conducted a test enrollment in a controlled environment to ensure a smooth deployment. Recognizing the possibility of system reboots, I factored that into the plan. As a precaution, I took backups of servers to maintain data integrity during the deployment, temporarily disabling prevention policies.

The initial setup might prove challenging for those unfamiliar with SQL. If you're well-versed in SQL, the process is straightforward. I would rate it five out of ten.

The product installation is straightforward. However, the policy configuration is highly complex. For the initial deployment, I rate the tool five out of five in terms of ease of setup.

the deployment was very easy. It typically took 20 to 25 days, and that was due to the fact that we had dependencies on other teams. We depended on the SQL team to create a particular instance of SQL DB. We depended on the network team to provide the IP address and open the ports on the firewall. Due to dependencies, it took around one and a half months. 

The post-installation activities that require PCs and which require some policy testing, configuration, and agent installation, took more than six months.

Since we were running 24/7 operations, I cannot commit how many people were required from beginning to end.

Maybe in another organization, the customer could easily provide the product on time - if they have redundancy or a well-established HA network. At least four associates are required for the deployment part and policy configuration, and you have to monitor the events daily as well, eventually. There would be a lot of events.

We're providing maintenance for the company currently. We have two people responsible for maintenance tasks. 

The initial setup is cumbersome because it is agent-based. I face many challenges in the Linux environment. It has a lot of dependencies.

It is an easy-to-install product. The process is quite straightforward to understand.

The initial setup is complex for the most part.

We have three different types of deployments including on-premises, cloud-based, and hybrid. The choice of deployment model depends on the requirements.

The length of time for deployment depends on the configuration and what you want to deploy. It generally takes between four and five hours for a fresh installation.

The initial setup was not complex but we faced some issues which were unrelated to the actual product itself. It took some time to resolve that. Deployment took us around two months because of the issues but generally it would take two days to implement. 

The most recent version was pretty simple, although we had our own hiccups and issues related to it. It is based on the environment, and ours has dependency challenges.

Generally, it takes time and diligence to set it up, but it is worth the effort.

Our deployment was done in stages. We have mission-critical servers, critical servers, and business servers. We started with the least critical, which is the business servers. From there we moved to the critical, and then on to the mission-critical. Those were also broken into different groups.

The business servers, where we had to learn the most, took us more than four months. For the critical servers, a lot of the work had been done, and they took us one to two weeks. The mission-critical servers are being set up now. It happens gradually because of our operational dependency.

The initial setup is pretty straightforward and not very complex.