It is time to upgrade – End of life Exchange 2007

Exchange 2007 End of Life Roadmap

Do you know that April 11 2017 is the date when Exchange 2007 will no longer be supported by Microsoft.

If you haven’t already begun your migration from Exchange 2007 to Exchange 2016 or Office 365 now’s the time to start your planning.

What does End of Life mean?

Exchange Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the date of the product’s initial release, and the end of this lifecycle is known as the product’s End of Life. When Exchange 2007 reaches its End of Life on April 11, 2017, Microsoft will no longer provide:

  • Technical support for problems that may occur;
  • Bug fixes for issues that are discovered and that may impact the stability and usability of the server;
  • Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches;
  • Time zone updates.

Your installation of Exchange 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Exchange 2007 as soon as possible.

Benefits of upgrading to Exchange 2016

Simpler and Better Server Architecture – Single Server Role
Better Collaboration
Saving files to OneDrive for Business
Uploading a file to OneDrive for Business.
Most Recently Used lists populated with both local and online files.
Office 365 hybrid
Messaging policy and compliance
In-place Archiving, retention, and eDiscovery
Improved performance and scalability
Auditing
Antimalware protection
Integration with SharePoint and Skype for Business

What are upgrade options?
#1-You can migrate to Office 365
#2- If you don’t want to migrate to cloud then you can upgrade to either Exchange 2010, Exchange 2013 or Exchange 2016.

I still have more questions, where do I get more details?
Follow this url – https://support.office.com/en-us/article/Exchange-2007-End-of-Life-Roadmap-c3024358-326b-404e-9fe6-b618e54d977d

 

 

Understanding Export-ActiveSyncLog

Export-ActiveSyncLog – Part 1-2

Is the iPhone ActiveSync is not fully supported by Microsoft?
Is the iPhone ActiveSync has some bugs?
Are Android Phones are fully supported?

I see very small hit count on the CAS Serve only from Windows Mobile while other smart phones hits are way higher and facing the issue.

Microsoft Exchange Server 2007 and Exchange ActiveSync offer a wide variety of features for both users and administrators. As an administrator, it is important that you know the volume and usage patterns of your deployment. This information can help you effectively manage your Exchange ActiveSync deployment, better understand user productivity, and plan for future needs. Reporting in Exchange ActiveSync for Exchange Server 2007 is a Windows PowerShell task that compiles a set of Internet Information Services (IIS) logs and processes to create a series of output files. Each file is a separate report that can help you understand your Exchange ActiveSync deployment. This topic provides an overview of the cmdlet you can use to generate these reports and information about the content of these reports.

I have been receiving complaints from the user community about their iPhone messing up on their ActiveSync accounts. This only happened to the iPhone and there was not a single complain from any Android user neither from any Windows Mobile User.  I came across a number of ways to export the logs but there was not enough information available except generate the result of the logs. I extracted the logs and tried to understand and below is the finding which very helpful.

 

Run Against all the IIS Logs

Get-Childitem C:WINDOWSsystem32LogFilesW3SVC1 | where-object {$_.lastwritetime -gt $DateToCompare} | ForEach { Export-ActiveSyncLog -FileName $_.FullName -OutputPath “C:reports” -OutputPrefix $_.Name.Replace(“.log”,”_”) -UseGMT:$true}

This cmdlet will go through all the logs in IIS under the W3SVC1 Directory and it will take time depending the size of logs OR if you want you can add the –StartDAte and –EndDate to the specific dates are looking for.

More than 123000 hits and they are all iPhone

 

When I sort the same sheet with Hits the minimum hits are generated by Windows Mobile 7.0

After doing this extensive research I am still unable to understand why there are so many hit by the devices which are non-Microsoft and why iPhone has the maximum hits on the server. I will end this post with these questions in my mind and I hope Microsoft or MS Exchange will look into this and provide some solution.

 

Run Against a specific date

Export-ActiveSyncLog -FileName: “C:WINDOWSsystem32LogFilesW3SVC1ex120126.log” -StartDate:”2012/01/25″ -EndDate:”2012/01/26″ -UseGMT:$true -OutputPath:”c:reportsthu”

The output is something like that with 6 files

Output of the Servers.csv

When I look at the UserAgent CSV file from the date the user’s complained I was surprised to see there were more than 293000 hits in total from 452 Unique Devices and out which 172 Unique Devices had More than 123000 hits and they are all iPhone

When I sort the same sheet with Hits the minimum hits are generated by Windows Mobile 7.0

After doing this extensive research I am still unable to understand why there are so many hit by the devices which are non-Microsoft and why iPhone has the maximum hits on the server. I will end this post with these questions in my mind and I hope Microsoft or MS Exchange will look into this and provide some solution.

Soon I will update the part 2 of this post which will cover the ActiveSync Report using Log Parser comparing the same data and two different output.

Related Links

http://support.microsoft.com/kb/2469722
http://support.apple.com/kb/TS339
http://tools.ietf.org/html/rfc1945#section-10.15
http://msdn.microsoft.com/en-us/library/ee204257(v=exchg.80).aspx
http://msdn.microsoft.com/en-us/library/dd299446(v=EXCHG.80).aspx

 

 

 

 

Export/Import Exchange 2007 Mailbox

export/import mailbox feature is one of the best tool for any IT Admin.
If you are into a situation where you need to backup the old mailboxes then you can use this tool rather configuring the Oulook Client and making PST.It is very easy to use.

Things to remember - You should have Manage Full Access Permission on the desired mailbox, else it won't work.

 Export-Mailbox -Identity <MailboxIdParameter> -TargetMailbox <MailboxIdParameter> -TargetFolder <Folder_Name>
 
 
 

Tweaking Exchange 2007

Tweaking Exchange 2007

Managing Connectivity Logging

The following permissions are required on the connectivity log directory:

Administrator: Full Control
System: Full Control
Network Service: Read, Write, and Delete Subfolders and Files

Enabling Connectivity Logging using cmdlet
Set-TransportServer Exchange01 -ConnectivityLogEnabled $true

Change the location of Log Files
Set-TransportServer Exchange01 -ConnectivityLogPath “C:Connectivity”

Configure the maximum size of each connectivity log file
Set-TransportServer Exchange01 –ConnectivityLogMaxFileSize 20MB

Setting up the maximum size of the connectivity log directory
Set-TransportServer Exchange01 –ConnectivityLogMaxDirectorySize 250MB

Configure the Age for the Connectivity Log Files – How long you wanna keep the log files
Set-TrasnportServer Exchange01 –ConnectivityLogMaxAge 30:00:00:00
-where dd.hh:mm:ss, where d = days, h = hours, m = minutes, and s = seconds

Managing Message Tracking

Permission required – Exchange Organization Administrator role
The following permissions are required on the message tracking log directory:
Administrator: Full Control
System: Full Control
Network Service: Read, Write, and Delete Subfolders and Files

Enable/Disable Message Tracking log
Set-TransportServer Exchange01  -MessageTrackingLogEnable $True
Set-TransportServer Exchange01 – MessageTrackingLogEnables $False
Set-MailboxServer Exchange01 –MessageTrackingLogEnabled $True
Set-MailboxServer Exchange01 –MessageTrackingLogpath “c:mailbox tracking”

Resources:
http://technet.microsoft.com/en-us/library/aa996827(EXCHG.80).aspx

Exchange 2007 Transport Dumpster – How does it work

Exchange 2007 Transport Dumpster – how does it work

There are some important points

  • Dumpster works only with CCR implementation
  • The maximum size of the Transport dumpster queue per storage group is for all the storage groups
  • To disable the dumpster we should define to 0
  • The cmdlet used to define is set-transportconfig
  • An eventid 2099 will appear when a failover event occurs
  • The recommended size of MaxDumpsterSizePerStorageGroup should be 3 times more than the maximum message size
  • When the limit is reached the first in is the first out
  • The transport dumpster depends on the RPC between two cluster nodes. Once the failed node come back online it will keep trying to sync with the other node and deliver the queue. The maximum time is several times a day for the 7 days.

[PS] C:>get-transportconfig

http://blogs.msexchange.org/patricio/2007/01/18/how-the-transport-dumpster-works-with-a-ccr-cluster/

http://msexchangeteam.com/archive/2007/01/17/432237.aspx

http://technet.microsoft.com/en-us/library/aa997963(EXCHG.80).aspx