Messaging 25

How to Setup POSTFIX as SMARTHOST or SMTP GATEWAY before Microsoft Exchange Server Overview:

How to Build your own Email Security Gateway for free Overview: What we need to do ? 1. Build up Bare-Bone Linux Server (Ubuntu/CentOS/Suse) 2. Installation & Configuration of POST-FIX as MTA (Mail Transfer Agent) 3. Installation & Configuration of Mail Scanner 4. Installation & Configuration of SpamAssassin 5. Installation & Configuration of ClamAV

Exchange 2013 mailbox migrations reporting wrong time stamp and /or timezone (Solved) The migrationbatch showed that it started 4 hours from when it was actually started.  I immediately wondered if it was normal because the time was right, but in UTC, not my timezone which is Eastern, but  I distinctly recall that this should show my local time instead.  In digging I found that if in powershell I issue a get-migrationbatch | fl * it lists the various time properties, including properties specific to UTC.  The interesting part though, they were one in the same.  See example below. I went and checked my dev exchange environment and it's reporting this as expected.  Further if I, personally, issue a migration in production it shows as expected as well.  It seems to have only happened to my customer.  I even had him do another migration with the same result.  I had him check his local timezone on his machine that issued the request and his timezone is set to Eastern. I'm completely

Microsoft Exchange System Attendant Service Proxy Active Directory requests and to regulate internal Exchange Server functions. It is critical to Exchange Server's performance, since many Exchange-related services will not function without it. In Exchange 2003, for example, you cannot mount the databases unless the Exchange System Attendant service is running. The Exchange information store is also dependent on the Exchange System Attendant service. Even in previous versions of Exchange Server, various Exchange-related services fail to start unless the Exchange System Attendant is running.  Overview of the Microsoft Exchange System Attendant The Microsoft Exchange System Attendant service performs a wide variety of tasks. It is responsible for everything from facilitating Active Directory communications to enforcing retention policies and mailbox quotas. As you might expect from such a diverse service, the Exchange System Attendant is based on a primary executable file that runs as

In coexistence environment (exchange 2007-2013), we could set Exchange 2013 ActiveSync External URL to mail.yourexternaldomain.com and set Internal URL to mail.yourinternaldomain.com . And set Exchange 2007 Internal URL to  mail.yourinternaldomain.com  and set External URL to Null .  We could run the following commands. Set-ActiveSyncVirtualDirectory -Identity "<CAS2013>\Microsoft-Server-ActiveSync (Default Web Site)" -ExternalUrl "https:// mail.yourexternaldomain.com /Microsoft-Server-ActiveSync"    –InternalURL “https:// mail.yourinternaldomain.com /Microsoft-Server ActiveSync” Set-ActiveSyncVirtualDirectory -Identity "<CAS2007>\Microsoft-Server-ActiveSync (Default Web Site)" -ExternalUrl $Null    –InternalURL “https:// mail.yourinternaldomain.com  /Microsoft-Server-ActiveSync”

Troubleshooting Microsoft Exchange Server 2010  Unable to initialize the information store service on Exchange 2010 , error code is - 2147221233, Event ID 5000 and 1122 This problem caused by the following; Default Policy item was deleted from the E-mail Address Policies tab, and if it was replaced by a custom e-mail address policy. Exchange Server : 2010 - SP3 - Roll Update 11 Domain Controller : Server 2003 All Mailbox Databases were dismounted. Exchange 2010 was also unable to communicate with Domain Controller... Possible Solutions:  Question: How to restore the deleted or replaced Default Policy Item? Answer: The Default Policy Item can be restored by applying the following steps: Insert the Exchange Server 2010 Media and run; 1. setup.com /PrepareSchema 2. Setup.com /PrepareAD After applying the above mentioned instructions the Default Policy Item was restored successfully. Microsoft Exchange Information Store Service is still down and i have the same error...  Applying the Sugge

Setup previously failed while performing the action "BuildToBuildUpgrade". You can't resume setup by performing the action "Install". (Resolved) Because of this you will be unable to perform various actions like given below; /PrepareAD,  Upgrade, Uninstall etc..... This error occurred because of Action and Watermark keys are there in registry that's why exchange server remembers previous installation. So, what you will do ? You just have to remove those registry keys... There you go.............

Windows could not start the Microsoft Exchange RPC Client Access Service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion. Exchange Server 2013 - CU 16 (Fig. 1.0) Solution: It's bit strange solution, I don't know how did it work but it did..... let's try this out... I had this issue on my exchange 2013 (installed with CU16), I tried couple of methods found while googling but they didn't work so, what I did to sort out this ??? Tweaking this config. file Microsoft.Exchange.RpcClientAccess.Service.exe.config located at C:\Program Files\Microsoft\Exchange Server\V15\Bin. Microsoft.Exchange.RpcClientAccess.Service.exe.config.old     (renamed with .old) Microsoft.Exchange.RpcClientAccess.Service.exe.config            (revert back it's original name) Restart the server and it worked like a charm !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Cannot access certificate server via https://localhost/certsrv or http://localhost/certsrv on Windows Server 2003. When you install Certificate Authority on Windows Server 2003 it won't create directory in IIS Server automatically, you have to create directory by yourself. for this do the following; certsrv directory is located in C:\System32\certsrv; Solution: Open up Command Prompt and run Certutil -vroot Command. The above command will create a certsrv directory that will be accessible from web browser.

Microsoft Outlook 2007 Clients won't connect to Exchange Server 2013 Microsoft Outlook 2007 Clients lower than Service Pack 3 will not connect to Exchange Server 2013. Solution: Note: This (12.0.6665.5003 Standard SP3) build number of Outlook 2007 Service Pack 3 will work fine with Exchange 2013 Server. You will need to install the following packages to get it done... 1. office2007sp3-kb2526086-fullfile-en-us (Service Pack 3 Bundle) 2. outlookloc2007-kb2687404-fullfile-x86-glb (Hotfix) Download links are given below; office2007sp3-kb2526086-fullfile-en-us outlookloc2007-kb2687404-fullfile-x86-glb For Outlook 2010; Outlook 2010 Service Pack 1 with the Outlook 2010 November 2012 update, link is given below. Outlook 2010 SP1 November 2012 Hotfix Please do not hesitate if you have any further question.