Microsoft Outlook 2010 550 Access denied Invalid HELO name

550 Access denied Invalid HELO name

If you're getting this error when sending out email. Please double check your email setting to use the following For outlook Click Tools then E-mail Accounts... Select "View or change existing e-mail accounts" and click Next Select the email account and click Change Click on "More settings" Select "Outgoing Server" tab Tick "My outgoing server (SMTP) requires authentication" Select "Use same settings as my incoming email server" Click Ok Press Next Lastly, press Finish

Migrate Symantec Endpoint Protection Manger Server to a new Installed Server

This How-To will explain in detail how you can "Migrate" your Symantec Endpoint Protection Server to a new server with new hardware.

I would normally image the old server with Symantec System Restore, but I am upgrading the base OS as well from Server 2003 Enterprise to Server 2008 Enterprise 64-bit, so we will have to go through the motions of moving it.

1.	Install, activate, and update the new server. Install Server 2008 or whichever operating system you will be using, and make sure all drivers are working. You will also want to make sure to perform all MS updates while you are at it. Additionally, if you are a fan of redundancy (as most of us are), go ahead and team/bond your NICs while you have the opportunity so that you do not disrupt the network connectivity after it is in production.
2.	Add the server to the domain. This should be pretty straight forward.
3.	Install Symantec Endpoint Protection Manager on the new server. Again, should be straight forward.
4.	Use the Configuration Wizard to prep it. When you get to the Management Server Configuration Wizard panel, go through with the Advanced Configuration type and select how many computers will be managed by this server. Choose to Install an additional site. This is the only option that will install a Management Server and a database for replication. In the Server Information panel, accept or change the default values and then click Next. In the Site Information panel, accept or change the name in the Site Name box and then click Next. The Site Name cannot be the same as what you have on your other SEPM.
5.	Point it to the old server for replication, and input the old server's credentials. In the Replication Information panel, type values in the following boxes: * Replication Server Name (The Name or IP address of the old Symantec Endpoint Protection Manager) * Replication Server Port (The default is 8443 but you need to use the same port as the old server here) * Administrator Name (The Username used to log on to the old console) * Password (The password used to log on to the old console.) Click Next.
6.	In the Certificate Warning dialog box, click Yes You must accept this certificate, or the replication cannot occur due to the server being seen as untrusted.
7.	Select the database type to use. In the Database Server Choice panel select either the Embedded database or the Microsoft SQL Server irrespective of what you have on your old server and click Next to complete the installation. Note that the embedded version is fine for most SMBs as it can support up to 5,000 client computers. SQL Server would be useful in a very large organization, but it would be a resource hog. I will choose embedded.
8.	Setup database security credentials. Note that after much troubleshooting at this step upon ANY initial install, you would do well to use something like your company's name "MyCompanyIncorporated" and then change it afterwards. I could not login because (according to symantec support) the initial install doesn't like numbers or special characters for the database password. They advised me to use a single simple word longer than 6 characters. Additionally, you may need to change the default port here so it does not conflict with the old network AV manager. You may also want to logout of the old one. Additionally, if you encounter some failure issues, your best bet is to go to your windows firewall on both machines and add the appropriate TCP port exceptions. In my case as seen by the port numbers, I added an exception on both servers for 8443 (new server port), 8444 (old server port), and 2638 (new server database port). It took me a while to realize this was the reason my setup was failing.
9.	Login and check that everything has migrated Log in to the new Symantec Endpoint Protection Manager (SEPM) and ensure that all the clients and policies are Migrated successfully. Note that you will also have to reassign them to the new server BEFORE removing SEPM from the old server.
10.	Reassign the clients to report to the new server At this juncture everything should be running fine. However, we still have to tell our clients to begin reporting to the new server before we can remove the application from the old one. If you see this type of icon representing your clients on the new server then go to the next step to handle it.
11.	Reassign part 2 To reassign the clients to report to the new server, open the SEPM console of the old server and login. Now, click on policies, and drop down policy components. Select management server lists and find the new server under the name tab. Double click it to verify the IP and name are correct. Now cancel out. Right-click on the server and select "Assign..." from the popup menu. Check all the boxes to change the reporting for all clients. Finally click on "Assign". Be patient. Depending on how many clients you have and how many may not be connected this can take several minutes. I have elected to leave the old server up for an additional week or 2 to ensure that I get all machines moved. For example those that may be off at the time of the initial reassignment.
12.	Double Check the assignment on the new server Make sure the icons on the new server have updated to represent that they are now reporting to it instead of the old server.
13.	Once all have reassigned successfully Log in to the new SEPM and delete the old SEPM server from the Replication partners list and the Remote Sites. Under the Management Server Lists Policy Component, Delete the Default Management Server List for ‘OLD SEPM’ server.
14.	Congratulations! You have successfully migrated a Symantec Endpoint Protection Management Server!

Conclusion

This took a while to write up as I ran into several issues which I had to fix with ports. I also got a corrupted NIC driver out of the blue on the old server during this process and had to start over. I was migrating to a newer faster more redundant server for obvious reasons. I would recommend that you leave the old server up for a solid week and check on the assignment regularly. I do not know what would happen to a client assigned to the old server if you took it offline. I imagine you would have to uninstall and redeploy to those clients, and then reapply the policies, so if you are willing to go through all of this, more power to you, but I was not.
I sincerely hope this helps the next person who has to go through this. Enjoy!

Server Core Some Commands

Configuration of IP address:

Netsh interface ipv4 set address name=2 source=staic address=10.10.10.74 mask=255.255.255.0 gateway=10.10.10.1

Set the DNS Server IP address

Netsh interface ipv4 add dnsserver name=2 address=10.10.10.70 index=1

Rename the computer to W2k8-Core by using the following commands

Netdom renamecomputer %computername% /newname:W2k8-Core /userd:trainer@nuggetlab.com /password:Nu66et$ /reboot:0

Join the server to the company.com domain

Netdom joing %computername% /domain:nuggetlab.com /userd:trainer@nuggetslabs.com /password:* /reboot

Turn off the firewall

Netsh advfirewall set allporfiles stat off