Setting up Symantec Messaging Gateway “Brightmail Gateway” on Hyper-V

First disclaimer, to my knowledge Symantec still does not support the use of Brightmail as a virtual appliance on anything other than VMWare, so proceed at your own risk. Now with that said, if you snapshot your working image before you make any major changes you should be pretty safe.

Over the past few years I have been using the OS restore files to install Brightmail on a physical Dell 2850 server. This process has worked pretty well since the OS restore runs a hardware detection during the setup, the problem was when it came to upgrades more time than not the self-update process would render the system unbootable. It’s always been my desire to run Brightmail as a virtual server since it’s not very load intensive for our mail volume, but the dependence on SCSI boot disk rendered it Hyper-V incompatible. When I read the read me for the most recent version of Brightmail I noticed it listed additional hardware support, so I thought I would give it a try and it was successful.

For my setup I used Symantec_Messaging_Gateway_OSrestore_9.5.3-3_Linux_Int.iso file from Symantec download site. For the most part it’s a straight forward virtual machine setup except for the network adapter, I discovered after the initial install I had no network connectivity, I resolved this by removing the network adapter and adding a “Legacy Network Adapter” in its place. During the initial GUI Bright setup process it detected version 9.5.4, so I had it apply the update, and it was successful so a good sign.

This entry was posted in Computers and Internet, Exchange. Bookmark the permalink.

8 Responses to Setting up Symantec Messaging Gateway “Brightmail Gateway” on Hyper-V

  1. Urs says:

    Hi Scott, whitch logon name and password did you used for the first logon? Thanks a lot, Urs

  2. Ruben says:

    Hi Scott, Where did you get the 9.5.3-3 OS restore file? On Symantec’s file connect I only see 9.0.2-9 OS restore as the latest ISO. I tried with the 9.0 version, but can’t get the network adapter to work, even with a legacy network adapter.

    • Scott Waber says:

      That’s strange I’m using Symantec Protection Suite Enterprise Edition 4.0 – International English, and I just checked and I still see the file. Try setting the filter for Operating System “Appliances Only” and see if it’s there.

  3. Justin says:

    Hi Scott, thanks for sharing the information. I just want to confirm that the hyper-v server that you used was Windows Server 2012 or 2008? I saw that 2012 server supports some linuxes, but not 2008 server. Thanks,

  4. I know this is a dated thread but version 10.5 now supports Hyper V

    • Scott Waber says:

      Yes thank you for pointing that out, a welcome update to the product. While it could be made to work under pervious version, it was a little temperamental and the time skew was really annoying.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s