Pushing out the Mimecast Services for Outlook

I have had the beta version of the Mimecast Services for Outlook running for some time now and I have to say it is very useful, I find myself using it quite frequently. As we are not Journaling emails to Mimecast just now I am only using it for external emails, however I am working on a plan to push the final release to the users within the Firm in the coming weeks.

The connector itself is an MSI file so this is easily pushed out through GPO, however the connector requires Visual C++ Redistributable files which are installed by an exe so my answer to this was install both files at computer startup.

The actual Mimecast Services for Outlook I installed as a published software through GPO as mentioned above, the VCRedist_x86.exe I pushed out through a computer startup script as a batch file, the batch file is very straight forward:

if exist C:\Support\Flags\vcredist_x86.log goto installed
vcredist_x86.exe /q:a /c:"msiexec /i vcredist.msi /qb! /l*v C:\support\flags\vcredist_x86.log"
exit
:installed
exit

On our PC's we have a support\flags folder where all flag files/logs are put for software installations, so if we need to keep these scripts in place for any length of time they will check to see if a flag or log file exists and then skip the installation.

And it is that simple to put out the Mimecast Services for Outlook. To be honest I did not check to see if running the setup.exe (that combines the two packages) will work silently or not. But this method works ok for me.

I am just waiting for the global configuration tool so that when I do push this out to the users we have some way of creating their profiles within outlook automatically too.

  Add to Technorati Favorites StumbleUpon Toolbar

  1. Gravatar
    Sarrl 7/30/2008 12:04 PM

    # re: Pushing out the Mimecast Services for Outlook

    Do you have any thoughts or comments about the Mimecast "Ingestion" service? I know it was a pretty time heavy process to manually collate and rename all of the user PST files before sending them over to Mimecast to "process".

    I've got an old colleague reviewing Mimecast (after seeing it in operation at our place) for a possible implementation, but they have 1200 users and a (currently unknown) number of PST files to collect together.

    Is there anyway of automating this whole process, for example, a tool to scan user local hard drives for PSTs and user network drives?

    It could save a lot of time and pain I think.

  2. Gravatar
    Andrew Kemp 7/30/2008 11:06 PM

    # re: Pushing out the Mimecast Services for Outlook

    We were looking at the “Ingestion” process to import our cryoserver data as we have 2 years worth of emails stored in there, but it worked out far too expensive even at a very generous discounted rate, and there was just now way that £10k would have been approved to ingest the email. In the bigger picture I think that it would have been worth it as it now means we have to keep our Cryoserver Box running parallel to Mimecast for the next 8 years, and we no longer have support on it so if it fails we will have to pay for the consultancy as well as the hardware so that could in turn end up to be more than £10k.
    In terms of automating the “Ingestion” process I would imagine that there would be a way to somehow automatically scan a user’s PC, Network share etc... For a pst file then potentially copy it to a location under his her username and then run a loop command to rename each PST ???
    We are quite fortunate as we have implemented a public folder store for users for archived emails. Sits on a low end with big disks exchange server. We basically have said in company policy not to store PST files on the users local PC, as it causes more trouble down the line, say when they PC crashed or they move desks etc...

Leave a reply

Title *

Name *

Email

Url

Comment *  

Please add 1 and 2 and type the answer here: