How to configure an SMTP relay for Office 365

This article describes how to configure a Simple Mail Transfer Protocol (SMTP) relay in Windows Server 2012 R2 to use with Microsoft Office 365.

You may want to do this in scenarios where you no longer have an on-premises messaging environment, such as
Microsoft Exchange Server, and you have on-premise MFP’s or copy machiens that still need to email via SMTP.

In this scenario, you will configure Microsoft Exchange Online as an SMTP relay to send email messages.

Before you get going notice that you will need the following:

  1. A Licensed mailbox with atleast an exchange online license attached.
  2. The login information for this account (Emailaddress + Password)
  3. A Windows Server 2012 R2 Server that the machine or application that needs to email can access.
  4. Office 365 SMTP server address is

Install & Configure SMTP Server Feature

  1. Open up Server Manager in your on premise Server.
  2. Go to Manage in the top right and click it. Choose Add Roles and Features
  3. Click Next with Role-Based or feature-based installation selected.
  4. Choose your server and click Next.
  5. For Server Roles just click Next.
  6. On the Features page Scroll down till you see SMTP Server and choose that and hit Next and finally Install.
  7. Next click on the Startbutton and choose Administrative Tools. Click on Internet Information Services (IIS) 6.0 Manager.
  8. Expand SMTP Virtual Server #1 and click on Domains.
  9. Right click and choose New > Domain.
  10. Select Remote domain type and hit Next.
  11. For the name you name it depending on your ending root domain name. So if i have i will name my virtual server *.com
  12. Right-Click your new *.com domain or w.e you named it and select Properties.
  13. Select the checkbox “Allow incoming mail to be relayed to this domain”
  14. Under Route domain, select “Forward all mail to smart host” and type
  15. Click on “Outbound Security” 
  16. Within Outbound security select Basic Authentication type in your email address and password for your office 365 account and select the check box for TLS encryption
  17. Next Right-Click on your SMTP Virtual Server and select Properties.
  18. Go to the “Delivery” tab and Click on Outbound Security.
  19. Set the settings as in Step 16 with email adress and password and TLS enabled. Click OK
  20. Next click on “Outbound Connections” still under the Delivery tab.
  21. Change the port to 587. Click OK.
  22. Next go to the “Messages” Tab. Change Limit message size to “15000” Change Limit session size to “30000”

  23. Next Click OK and you’re all done.

On the Copy Machine or Application you can now point to the server as a smtp server and use port 25. In some instances you may need to open port 25 in the windows firewall on the server. Make sure that the application or copy machine has the same emailadress as the office 365 email account or otherwise all your emails will be stacked in the bad mail folder.

Leave a comment if you need any help or clarification.

Step-by-Step: Installing SQL Server Management Studio 2008 Express

UPDATE 7/31/2012 – Since this post new versions of SQL Server & Visual Studio have been released. To install the latest version of SQL Server see SQL Server Install. For more information on working with SQL Server Local DB in Visual Studio 2012 see Working with SQL Server LocalDB in Visual Studio 2012 and the MSDN Library SQL Server 2012 Express LocalDB.

One of the first things I always do after installing Visual Studio is to install SQL Server Management Studio (SSMS). Visual Studio 2010 installs SQL Server 2008 Express on your machine but doesn’t include SSMS. Although you can use Visual Studio to create/connect/design databases, I like having SSMS around for advanced management. I recall SSMS for SQL Server 2005 was a simple install, unfortunately they threw the kitchen sink into the SSMS 2008 installer and I’m always confused at which buttons I need to push to get it to do what I want. So I’m writing up this blog post for two reasons 1) So I remember the steps and 2) So you can be less frustrated 🙂 (BTW, a birdie tells me that the SQL team is looking at making this installer much simpler in the future. Hooray!)

Okay the first thing you need is to make sure you get the right version of SSMS. If you installed Visual Studio 2010 then you will need the 2008 version (not R2).

STEP 1: Download Microsoft® SQL Server® 2008 Management Studio Express and select either SQLManagementStudio_x64_ENU.exe or SQLManagementStudio_x86_ENU.exe depending on your machine’s OS bit-ness. I’m running Windows 7-64bit so I’ll be detailing the steps as it pertains to that OS.

STEP 2: Make sure you’re logged in as an administrator of the machine then right-click on the exe you downloaded and select “Run as Administrator”. If you’re on Windows 7 then you’ll get a compatibility warning. Click past it for now to continue with the install. Later you’ll need to apply SQL 2008 Service Pack 2.

STEP 3: You should now see the “SQL Server Installation Center” window. Yes it looks scary. Select the “Installation” tab.


STEP 4: Select “New SQL Server stand-alone installation or add features to an existing installation”. It will then run a rule check. Make sure there are no failures and then click OK.


STEP 5: The next step is misleading. The Setup Support Files window looks like it’s doing something and stuck on “Gathering user settings.” It’s actually waiting for you to click the Install button! Doh!


STEP 6: Another rule check. You’ll probably end up with a Windows Firewall warning this time. If you want to enable remote access to SQL Server you’ll need to configure the firewall later. Since I’m using SQL Server Express for development purposes on this machine only, I won’t need to worry about that. Click Next.


STEP 7: Okay here is the step I always mess up because it’s just not intuitive at all. On the Installation Type window you have a choice between “Perform a new installation of SQL Server 2008” OR “Add features to an existing instance of SQL Server 2008”. You need to select new installation, NOT add features. I know I know, totally weird. You would think that since you just want to add SSMS that it would be Add features to existing instance – I mean I don’t want a new instance, just the dang tools. Sigh. Click Next.


STEP 8: Next you get the Product Key window. You obviously don’t need a product key for SQL Server Express since it’s free so just click Next.


STEP 9: Accept the License Terms and click Next.


STEP 10: Okay now for the window we’ve all been waiting for – Feature Selection. Check off “Management Tools – Basic” and then click Next.


STEP 11: Verify your disk space requirements and click Next.


STEP 12: Help Microsoft improve SQL Server features and services by selecting to send usage and error reports to them (or not). Click Next.


STEP 13: Another quick rule check runs. Click Next.


STEP 14: Now it looks like we’re ready to install. Click the Install button.


The install will kick off and will take about 5 minutes to complete.

STEP 15: Once the installation completes, click the Next button again.


STEP 16: Complete! Click the Close button and you should be all set.


STEP 17: Fire up SQL Server Management Studio! You should now see it in your Programs under Microsoft SQL Server 2008. Make sure you run it as an administrator for access to all the features.


And don’t forget at some point to install the latest SQL Server 2008 Service Pack. I hope this helps people who have just installed Visual Studio 2010 but also want to install SQL Server Management Studio. I know I’ll be referring to my own post on this when I need to do it again 🙂


Configure Windows 7 to display what software is installed at startup/login

In Windows XP and Windows 8 you will see what software is being installed via GPO at start or login. In Windows 7 this has been shut off as standard. To enable this behavior do the following.

Open up GPMC and create a new group policy.

Browse to:
Computer Configuration\Policies\Administrative Templates\System

The policy is called on Windows Server 2008 R2:
“Verbose vs normal status messages” = Enabled

The policy may also be called on Windows Server 2012 + 2012 R2:
“Display highly detailed status messages” = Enabled

Enable it and you’re done.

Enable Outlook Anywhere

Exchange 2010

Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2011-03-19

Use the Enable Outlook Anywhere wizard on the Exchange Server 2010 Client Access server to allow users to connect to their Exchange mailbox from the Internet. Outlook Anywhere eliminates the need for users in remote offices or mobile users to use a virtual private network (VPN) to connect to their Exchange servers.

Outlook Anywhere will be enabled on your Client Access server after a configuration period of approximately 15 minutes. To verify that Outlook Anywhere has been enabled, check the application event log on the Client Access server.


  • Install a valid Secure Sockets Layer (SSL) certificate from a certification authority (CA) that the client trusts.
  • Install the Microsoft Windows RPC over HTTP Proxy component if it wasn’t already installed by default in Windows Server 2008. For detailed steps, see Install the Windows RPC Over HTTP Proxy Component.
  • Enable Outlook Anywhere on the Client Access server.

When you install Exchange 2010, you can install a default SSL certificate that’s created by Exchange Setup. However, this certificate isn’t a valid SSL certificate that’s trusted by the client. To use Outlook Anywhere, you must install an SSL certificate that’s trusted by the client.


Use the EMC to enable Outlook Anywhere

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the “Outlook Anywhere configuration settings” entry in the Client Access Permissions topic.

  1.  In the console tree, navigate to Server Configuration > Client Access.
  2. In the action pane, click Enable Outlook Anywhere.
  3. In the Enable Outlook Anywhere wizard, type the external host name or URL for your organization in the box under External host name.
    This is the URL, for example, that users will use to connect to the Exchange server by using Outlook Anywhere.
  4. Select an available external authentication method. You can select Basic authentication or NTLM authentication.
    Basic authentication sends the user name and password in clear text. It also requires that users enter domain, user name, and password every time that they connect to the Exchange server. When you use NTLM authentication, the user’s credentials are never sent over the network. Instead, the client computer and the server exchange hashed values of the user’s credentials. NTLM can also use the current Windows operating system logon information.
    Even though it’s more secure, NTLM may not work with firewalls that examine and modify traffic. You can use an advanced firewall server such as Microsoft Internet Security and Acceleration (ISA) Server 2006 together with NTLM authentication for Outlook Anywhere.

    Negotiate Ex authentication is an authentication type that’s reserved for future Microsoft use and should not be used. Use of this setting will cause authentication to fail.
  5. If you’re using an SSL accelerator and you want to use SSL offloading, select the check box next to Allow secure channel (SSL) offloading.
    Select this check box if you’ll be using a separate server to handle Secure Sockets Layer (SSL) encryption and decryption. When you use SSL offloading, the firewall in front of the Client Access server ends the SSL session and then establishes a new non-SSL session to the Exchange server.

    Don’t use this option unless you’re sure that you have an SSL accelerator that can handle SSL offloading. If you don’t have an SSL accelerator that can handle SSL offloading, and you select this option, Outlook Anywhere won’t function correctly.
  6. Click Enable to apply these settings and enable Outlook Anywhere.
  7.  Click Finish to close the Enable Outlook Anywhere wizard.


Use the Shell to enable Outlook Anywhere

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the “Outlook Anywhere configuration settings” entry in the Client Access Permissions topic.

In this example, the Client Access server named Exch1 is enabled for Outlook Anywhere with its external host name as, the default authentication set to Basic, and SSL offloading not selected.

Enable-OutlookAnywhere -Server 'Exch1' -ExternalHostname '' -DefaultAuthenticationMethod 'Basic' -SSLOffloading $false

This example enables the server named Server01 for Outlook Anywhere. The external host name is set to, both Basic and NTLM authentication are used, and SSL offloading is set to $true. The ClientAuthenticationMethod parameter specifies the authentication method that the Autodiscover service provides to the Outlook Anywhere clients to authenticate to the Client Access server. The authentication method can be set to Basic or NTLM.

Enable-OutlookAnywhere -Server:Server01 -ClientAuthenticationMethod:Ntlm -SSLOffloading:$true

For more information about syntax and parameters, see Enable-OutlookAnywhere.

Other Tasks

After you enable Outlook Anywhere, you may want to Configure Client Access Server Properties.

Outlook 2010 does not save password with Exchange

If Outlook 2010 will not save your password, and you are connecting to a Microsoft Exchange Server, give this a try….

Close Outlook

In Windows 7 (x64 or x86), start the Credentials Manager in your Control Panel.

In Windows XP, go to the User Settings.

Remove all saved entries that have anything to do with your Exchange Server or your Domain Credentials.  They would look like:

  • domain\username
  • exchange.domain.local
  • MS.Outlook:

Then start Outlook and enter your credentials, saving your password.

Then restart Outlook and it should go right in!

How to Install and Configure Dell’s OpenManage Integration for vCenter

This is a wonderful tool that I last used as a plug-in for the vSphere Client.  This is the first time using it in the vSphere Web Client and of course I am impressed.  I have talked to a number of people who have worked for Dell and while they know of it, they have not seen it.  So I figured it is a good idea to have an install / configure post on getting this great tool working.  The prices on it have dropped seriously as well – I paid around 450 US$ for a 3 year subscription for four hosts.  But I thought before the install / configure I would talk about why.

Why have the Dell OpenManage integration for vCenter?

It is not because it is a vSphere Web Client plug-in.  It is not because on each host I have information like the screenshot below shows.


It is not because of the screenshot below either.

Dell server info at the Cluster level

While all three things I mention / show are nice, the following screen is what I really like the best.

Firmware Update Wizard!

I started the Firmware Update process on a host – bosesx01 in this case.  It will allow me to update firmware – like server BIOS – without an outage.  Sort of like VUM but for Dell hardware.  I can do this at the cluster level, or at the host level.  I am doing it here at the host level since I am playing and learning.

But I have not mentioned something else that is important.  You can decide to enable a very interesting feature that is off by default.  You can enable a feature that will put a host into maintenance mode if it has a hardware issue.  Something to test and learn about before you enable it but it is very handy indeed!

So lets get this very nice software working!

Installing OpenManage for vCenter

Things to gather before you start

  • If you are using 12th Generation servers (like R720) you do not have to install the OpenManage VIB first as it will be install automatically.  If you are using 11th Gen servers like the R710, or older you can use OpenManage (OM) to install the VIB I am told.  Not sure how however.
  • Make sure your iDRAC are all configured and you have the credentials for them.
  • You need an IP address and DNS entry.  Do the DNS entry before installing as I think it saves on watching a few error messages.
  • Service account for vC connectivity.  It should be a member of Domain Users, and a vC admin level account.
  • It looks like for 5 hosts or less there is no license or license file.  This was confusing for me as I found a bunch of conflicting information on this subject and finally had to install to confirm!
  • The documentation is here.
  • You do need the bits – which you will normally download via a link in the email after your purchase – or maybe from here.  Note – when I bought the license info email was sent to someone else in the company that bought something from Dell a long time ago.  When you get the bits you will need to extract them to find the .ovf / .vmdk files.  See below what you are extracting down to.


  • Here is a link to a central point of info on OpenManage.

Deploy Appliance

You would deploy the appliance as per normal.  However be aware that you do not set password or network info during the deployment.  I was so surprised, I did it twice!  The documentation was not always exactly what I needed!  After you have deployed the VM you access the VM console and set the password and network info – see below for the main screen you see after logging in.


Once you have finished with Time Zone, Admin Password and the network you should log out.  You will be told to access a particular URL but ignore that.  It doesn’t work.

Configure Appliance

You will see in places to access HTTPS://IP_address_OR_FQDN/DellAdminPortal/index.html but that did not work for me but HTTPS://IP_address or HTTPS://FQDN did work and so that was good!

Once logged in you will need to do a couple of things.  When you log in the first time you will see something like below.


  • The first thing we will do is to configure the OM to vC connection.  Use the Register New vCenter Server button to start this process.
  • You will see a dialog like below you will need to fill in.  My service account is svcom but use whatever yours is.


Once this is done, and the Register process works, you should see something like below.


Notice at the bottom of the screen where you can see my license info?  That is with no license applied.  After a day or two, and after my inventory is being scanned by OM, this screen looks a little different.


Now you can see that my four hosts are using up licenses.

We need to configure NTP now so select Appliance Management in the list in the top left corner of the screen.  After you do that, and scroll down the new screen you will see NTP Settings and will be able to configure it.


BTW, at the top of the Appliance Management screen you can do pretty easy upgrades.  I have pointed at the Update version info, and the update button in the screenshot below.  I will do an article about upgrades the next time I do an upgrade.


The next section is Alert Management and normally I do not make any changes there until after I have had things running for a while and actually know why I would make a change.

We do need to make changes in Backup and Restore. I do suggest you setup a CIFS share that the appliance can access and do a backup too.  I use the same service account I use to connect to vC to secure the folder that the appliance will backup to.  See what the configuration looks like when it is done.


You can see I setup the schedule backups too.  This is particularly important as you use OM more and have more and more configuration that you don’t want to lose.  Also note that I tested things?  Important to do that.  BTW, the location where you specify the backups to be written too will look like below once you have some backups.

OM backup location

The appliance is now configured and we are ready to move forward!

Configuration in vSphere Web Client

We have some interesting things to do in the Web Client now.  Lets get started!

  • Log out of your vSphere Web Client and log back in.
  • When you log back in you should see a new icon in the Home page.


See it in the bottom row on the right?  You need to click on it now and you will see a popup about the initial setup.


This starts a wizard to help you get things configured.

The first screen is just a welcome screen but I suggest you also check and enable the Do Not show the Configuration Wizardagain as that will be irritating and you can always start it again.

Starting to work through the Initial Config Wizard

After you press Next you will see the next screen.


You should see your vC already selected.  After Next you will see an informational screen which is followed by a Connection Profile screen.  When it is filled in it will look something like below.


There is some important things to understand on this form.  Note in the iDRAC Credential section I am not using AD but I have a blank user name and yet a password defined?  That password is for the root account in my iDRACs.

As well, the Host Root section is similar.  See below for that example.


For the root account on the hosts you need the password as well.  On the next screen you select your Dell hosts.  In my case my whole Gold cluster is Dell hosts.


The next screen just confirms information.  On the next screen however you need to enable and configure Inventory Data retrieval.  This is important.  Check out what mine looks like.


The next screen is about configuring Warranty Data retrieval. I do not think it needs to be done often at all.  See how I configured mine below.


The next screen is Events and Alarms and I do not make any changes there at this time.  I do later on after I am more familiar with how things work with this product.


When you are finished with this wizard you will see something like below.


The configuration is now finished!  We need to wait until the Inventory and Warranty details are retrieved but at least things are ready now.

Tour Time

So some time has passed, enough so my Inventory retrieval has run.  Lets go look.  You should see something at the Cluster level, and on Monitor / Dell Cluster Information.  Like below.


Or if you change to the Firmware option you will see something like below.


There you have it.  Things are good.  You now have OM installed and can see a lot more info on your Dell servers and you can now start doing other things like firmware updates without an outage – which I will show you how in a new article soon.

How do I push install to client(s) using ESET Remote Administrator? (4.x)

How do I push install to client(s) using ESET Remote Administrator? (4.x)
Posted by Wouter Makkinje on 23 April 2014 10:55 AM

How do I push install to client(s) using ESET Remote Administrator? (4.x)

KB Solution ID: SOLN2444|Last Revised: November 06, 2013

In order to complete the setup of ESET Remote Administrator and protect your network with your ESET product, you will need to perform a four-part process:



Upgrade to version 5

This article applies to servers running ESET Remote Administrator (ERA) version 4.x. ERA 4 should only be used to manage client workstations running ESET endpoint products version 4.x and earlier. To upgrade to version 5 of ESET server / endpoint products, see the following ESET Knowledgebase article:



  1. Download and install ESET Remote Administrator and ESET NOD32 Antivirus
  2. Set up your Mirror server

    This article outlines parts III and IV. For detailed instructions on parts I and II, refer to the following Knowledgebase article: How do I install ESET Remote Administrator and configure a Mirror server?

  3. Create an installation package (containing your ESET product and a configuration .xml file)
  4. Push installation package out to client workstations


Before proceeding, we highly recommend that you first read the ESET Remote Administrator Guide.

Video tutorial

III. Create an installation package

Creating an installation package and “pushing” it out to the network allows an administrator to quickly install/uninstall ESET NOD32 Antivirus or ESET Smart Security on multiple client workstations.


If you are upgrading a client workstation to a later version of ESET NOD32 Antivirus or ESET Smart Security, we recommend uninstalling the previous version first. 

To create an installation package, refer to the following step-by-step instructions:

  1. Open the ESET Remote Administrator Console (ERAC) by clicking Start  All Programs  ESET  ESET Remote Administrator Console. Click the Remote Install tab.
  2. Click Actions  Manage Packages.
  3. To add an installation package, click Add… in the Installation Packages Editor window.

    fig 1

    Figure 1-1

  4. Click “” and browse for the .msi installation file or click Download from the web >> and click the ESET product that you want to push install. Make sure the version number is current and that you have the correct package selected. This information is displayed in the Product Info field. Click Create.

    Figure 1-2

  5. To make changes to the configuration, click Edit. In the ESET Configuration Editor window you can customize the settings of the ESET NOD32 Antivirus installation package that will be pushed to the client(s). If you choose to edit the settings in the ESET Configuration Editor, click the Save disk icon to save your configuration and then click Console to exit the ESET Configuration Editor.

    fig 3

    Figure 1-3

  6. Click Save As and give your installation package a descriptive name, then click Save. Click Close to return to the ERAC window.


IV. Push the installation package out to client workstations


Before proceeding with a push installation, make sure you have verified all of the items on our push installation requirements and checklist.

To push install ESET NOD32 Antivirus or ESET Smart Security to your client(s), follow the steps below:

  1. Select the clients to which you would like to push install from the Computers list in the Remote Install tab of the ERAC.
  2. Right-click the selected clients and click Push Installation from the context menu.
  3. In the Computers Logon Settings window, specify the logon information for each client by selecting the client name and clicking Set or by selecting all clients and clicking Set All. Enter the username and password for the domain or workgroup in the Logon Information window and click OK. Click Next.

    fig 4

    Figure 1-4

  4. In the Package Settings window, select ESET Security Products package from the Type drop-down menu. Select the installation package you created earlier from the Name drop-down menu. Click Next.
  5. Enter the Task Settings in the final window, including a name for your Remote Install task and a specific time at which it will be performed. Click Finish to complete the push installation task.

Migrate the same version of ESET Remote Administrator from an old server to a new one

How do I migrate the same version of ESET Remote Administrator from an old server to a new one?

KB Solution ID: SOLN2683|Last Revised: January 29, 2014


  • Make sure that you have sufficient free disk space and temporary disk space to perform this migration (the migration process requires 3-4 times more free disk space than the actual size of the database). Insufficient disk space is a common cause of migration failure.
  • Do not deactivate the older server until you are sure that your client workstations are communicating with the new server.

To migrate the same version of ESET Remote Administrator from an old server to a new one, complete the following step-by-step process:

  1. Configure ESET Remote Administrator Server to ignore server name mismatches
  2. Perform database cleanup (optional)
  3. Export policies / groups
  4. Back up the old server
  5. Download and install ERAS and ERAC on the new server
  6. Move your client workstations to the new server
  7. Restore saved database onto the new server


I. Configure ESET Remote Administrator Server to ignore server name mismatches:

In order to prevent server name mismatches after migration, configure the ESET Remote Administrator Server to ignore server name mismatches by following the steps below:

  1. Open the ESET Remote Administrator Console (ERAC) by double-clicking the ERAC icon on your Desktop, or by clickingStart  All Programs  ESET  ESET Remote Administrator Console  ESET Remote Administrator Console.
  2. Click Tools  Server Options.
  3. Click the Advanced tab, then click Edit Advanced Settings.
  4. In the ESET Configuration Editor, expand Remote Administrator  ERA Server  Settings  Advanced and selectIgnore database server name mismatch.
  5. Select the check box next to Yes / No. Click Console to save your changes.
  6. Click OK to exit the Server Options window. You can now proceed to Part II below (performing database cleanup).

II. Perform database cleanup (optional):


Performing a database cleanup is an optional step that might help to speed up the database import in part VII.

  1. Open the ESET Remote Administrator Console (ERAC) by double-clicking the ERAC icon on your Desktop, or by clickingStart  All Programs  ESET  ESET Remote Administrator Console  ESET Remote Administrator Console.
  2. Click Tools  Server Options  Server Maintenance tab.
  3. In the Cleanup scheduler section, click Clean Up Now, then Yes to confirm the action. Once the clean up is complete, proceed to Part III.


III. Export policies / groups

Before continuing, export any policies and groups that you would like to import after migration using the Knowledgebase article below:

IV. Back up the old server:


V. Download and install the ESET Remote Administrator Server and Console on the new server:


VI. Move your client workstations to the new server:

Configure your client workstations to report to the new server hostname or IP Address. Refer to the following Knowledgebase article for step-by-step instructions :

If migration fails 
due to insufficient disk space, follow the steps below:

  1. Reinstall your version of ESET Remote Administrator.
  2. Restore the database using the ERA Maintenance Tool.
  3. Restore the following directory: C:\Documents and Settings\All Users\Application Data\ESET\ESET Remote Administrator\Server\
  4. Resolve the insufficient disk space issue by ensuring that you are accounting for the increased disk space necessary to perform this migration.
  5. Perform the steps in Part V again.


VII. Restore the saved database onto the new server:

    1. On the new server, open the Start Menu and click All Programs  ESET  ESET Remote Administrator Server  ESET Remote Administrator Maintenance Tool.
    1. In the ERA Maintenance Tool window, click Next twice.
    1. In the Maintenance Task section, select Database restore (from an external dump file).

      Figure 1-1

    1. In the Database connection properties section, click Load all settings from file and choose the file you saved when you backed up the old server.
    2. Click Test connection to make sure the connection is functioning properly. Click Next to continue.

      Figure 1-2

    1. In the Dump file window, locate the your saved dump file.
  1. Click Next, then Start to begin restoring the server.


Once you have completed steps 1-7 in part VI, verify that all of your settings have been restored successfully. If the ESET Remote Administrator Server service does not start successfully after migration, verify that it is not due to a server name mismatch issue by examining the following directories:

  • Server 2003, XP: C:\Documents and Settings\All Users\Application Data\ESET\ESET Remote Administrator\Server\logs\era.log
  • SBS 2011, Server 2008, Windows 7: C:\ProgramData\ESET\ESET Remote Administrator\Server\logs\era.log

Repair a server name discrepancy: Run the ERA service with the ‘-server_name_repair’ option from the Windows command prompt.

For example, open a Windows command prompt as an administrator (click Start  All Programs  Accessories. Right-click Command Prompt and choose Run as administrator from the context menu) and enter the following command replacing the path to the ERA service in this example with the path to ‘era.exe’ on your server:

C:\Program Files\ESET\ESET Remote Administrator\Server\era.exe -server_name_repair




Which ports does ESET Remote Administrator use?

Which ports does ESET Remote Administrator use?

KB Solution ID: SOLN2221|Last Revised: November 27, 2012

ESET Remote Administrator (ERA) requires certain ports to be open in order to function properly. The table below lists the possible network communications used when ESET Remote Administrator Server (ERAS) is installed. The process EHttpSrv.exe listens on TCP port 2221 and the process era.exe listens on TCP ports 2222, 2223, 2224 and 2846. Other communications occur using native operating system processes (for example, “NetBIOS over TCP/IP”).

For more information regarding ports used by ERA, consult section 2.1.2 (page 5) of the ESET Remote Administrator Manual.

Protocol Port Description
TCP 2221 (ERAS listening) Default port used by the Mirror feature integrated in ERAS (HTTP version)
TCP 2222 (ERAS listening) Communication between clients and ERAS
TCP 2223 (ERAS listening) Communication between ESET Remote Administrator Console (ERAC) and ERAS

If you are using all features of the program, the following network ports need to be open:

Protocol Port Description
TCP 2224 (ERAS listening) Communication between the agent einstaller.exe and ERAS during remote install
TCP 2225 (ERAS listening) Communication between the ESET Dashboard HTTP Server and ERAS
TCP 2846 (ERAS listening) ERAS replication
TCP 139 (target port from the point of view of ERAS) Copying of the agent einstaller.exe from ERAS to a client using the share admin$
UDP 137 (target port from the point of view of ERAS) “Name resolving” during remote install
UDP 138 (target port from the point of view of ERAS) “Browsing” during remote install
TCP 445 (target port from the point of view of ERAS) Direct access to shared resources using TCP/IP during remote install (an alternative to TCP 139)



All ports listed in the table above must be open in order for all components of ERA to properly function.



Update ESXi 5.5 to latest patch

Here is an easy step by step guide, how you can update this ESXi 5 host to the latest version…

1: Start your VMware Hypervisor EXSi 5 like you normal do, and connect to this host with your vSphere Client.

2: Switch the host to maintenance mode.

3: Install the needed patches (they can be found here: ) on one of you datastore’s in a folder called patch (in my case the Datastore is called Backup Smile

5-5-2012 12-27-00 AM

5-5-2012 12-39-29 AM

4: goto the Configuration tab of your host, select Security Profile (under Software in the left) and select the Services Properties in the upper right of your screen.

5-5-2012 12-43-51 AM

5: Select ESXi Shell and SSH and start these Services with the Start Service command button under Options…
make sure (just as on the screen both services are running(!)

5-5-2012 12-53-00 AM

6: Start PuTTY (you can find it here:

and login as the root to this host…

5-5-2012 1-05-26 AM

now run the command:

esxcli software vib update –depot /vmfs/volumes/[Datastorename]/[patchfilename].zip

(note: please be aware of the double ( – -) before depot)

5-5-2012 1-19-45 AM

7: be patient(!) this can take some minutes(!) and repeat this for all the patch zip files (make sure you do this in the released order…

8 close puTTY, delete the patch directory from the datastore,  reboot the host. When the host is back, exit the maintenance mode and you are done!

your host is running the latest patches

5-5-2012 1-29-40 AM

5-5-2012 1-37-03 AM