Question: Server using Apache and Plesk 9.

I have set-up multiple domains each with its own IP for SSL. 
Each domain has its own SSL config file **/var/www/vhosts/mydomain/conf/vhost\_ssl.conf**

I have disabled SSLv2 in **/etc/httpd/conf.d/ssl.conf**
and checked it with 

`openssl s_client –ssl2 –connect localhost:443`
result is an error.. which is correct

However when i test the domain to see if SSLv2 is disabled

`openssl s_client –ssl2 –connect mydomain:443`
result is domain has SSLv2 support - not what i want

My question is... Do i have to add lines to /var/www/vhosts/mydomain/conf/vhost\_ssl.conf to disable SSLv2 support for that domain...?

Is yes, do i need to copy the full `<VirtualHost _default_:443>....</VirtualHost>` section form **/etc/httpd/conf.d/ssl.conf** and add it to **/var/www/vhosts/mydomain/conf/vhost\_ssl.conf** ?

Answer: 
The best way to encourage users to take up a new service, is to make sure that it is better than what you currently provide, otherwise what's the point. I would make sure they have the ability to store more than 200mb, or are trained in how to prune their mailboxes of large attachments, although lets be honest, who really does this?

We moved away from Personal Folders some time last year, and despite the added few minutes a week I might have showing users how to clean their mailboxes up, I haven't looked back. It was definitely met with some scepticism at first, as most users had been used to a 500mb limit on their mailboxes and then archiving to .pst since long before I joined the company five years ago, but approaching it in gradual stages lessened the burden.

The first step was to increase the disk space on the Exchange server, costs of which were quickly justified to management by explaining the cost of lost data in a corrupt personal folder as well as the time taken to attempt to restore corrupt .pst files, they bought it pretty quickly.

The next step was to write some documentation for users on how to decrease the amount of data they stored in the mailboxes / personal folders, the best way to do this is to explain that it's not necessaries the amount of emails you have that take up the space, moreso the size of each email. I showed them that not all emails are the same size, and how they can free up 50% of data by cleaning up the largest 10% of their emails. I found that 70% of the users cleaned up their email after this

Finally, after explaining to the users the pitfalls of personal folders and the benefits of mailbox storage, such as automated nightly backups of their data which could be restored to a point in time if they were to lose anything, the ability to access their emails from anywhere they needed, as well as stating (with management approval) that we would no longer be supporting personal folders corruption, as a superior service was now available (I should add, that I never refuse to support an issue if it arises, but I've found that sometimes telling your users something is no longer supported is enough to encourage them to move to the new system) I migrated their personal folder data into their mailboxes as a goodwill gesture, over the course of a few weeks.

I then monitored the amount of data used by each mailbox for a few weeks and adjusted limits on a per user basis. Most remain with a 1gb limit, a small few require 2-3gb and quite a few others on 500mb. The reason I didn't set these limits prior to the migration is that I figured most users would delete a lot of older emails when they knew everyone else was doing it, which actually worked okay.
The key stakeholders on the business side of the house need to understand why IT wants to banish PST files. The means folks in the trenches as well as the executive type people.

PSTs to the users aren't "bad" or "evil" -- they are an essential tool that allows them to get work done. Most folks aren't aware of the risks to the company in the event of litigation or the other negative things that keep IT people up at night. An archive accessible via Outlook should make end-users do backflips -- the fact that they aren't means that you need to work on communicating with them.