it manager salary

Replicate Public Folders From Exchange 2003 Server

Just in case you are still using Exchange Server 2003 and trying to replicate public folders, or doing a public folder migration to Exchange 2007, 2010, or even Exchange 2013 then you are in luck.  Read recent insert below from Microsoft Exchange Team blog.

To read the entire blog post all you have to do is click the “via” link below the insert.

“Recently, we have released a Guided Walk Through (GWT) for troubleshooting public Folder replication issues in Microsoft Exchange 2003.  There are a couple of ways to access the troubleshooter.  You can use the link here to access it directly.  As well, it will be embedded in various related public folder replication articles such as the following:

via      “

Microsoft has recently released a Guided Walk Through (GWT) tool for trouble shooting public folder replication and public folder migration issues. You can access the tool by referring to my little insert above that was posted on the Exchange Team Blog, just recently.

If you are not aware, Exchange Server 2003 has also been moved from mainstream support. What this means is that you will no longer be able to receive support via of the phone.

I guess you are probably wondering why the Exchange Team created a modified version of the GWT tool if Exchange Server 2003 is out of mainstream support.

For answers on all of my above points, please visit the link in my quote above from the Exchange Team Blog.

it manager salary

store.exe high memory exchange 2010

If your exchange server 2010 continues to display high memory allocation usage then do what I have done. Search on Google for using the words, “store.exe high memory exchange 2010”. You will be amazed at what you will find, just like me. See excerpt below from the exchange team blog on the subject.

First, let’s start with why Store.exe uses so much RAM. If we take a step back in time to the Exchange 2003 era, this blog was quite active on how to tune memory on an Exchange 2003 server. I am not going to go in to specifics or great detail, but one thing to call out is that on the 32-bit architecture, we were limited to addressing 4GB of virtual memory on any given server. So essentially, any 32bit program could address up to 4GB of virtual memory. This address space is typically split so that applications could address 2GB of memory and 2GB would be for the Windows Executive. By adding the /3GB switch in the boot.ini, applications could now access up to a 3GB virtual address space and lower the Executive down to addressing only 1GB, essentially halving the memory that is can be addressed or is available for kernel drivers, paged/non-paged pool memory, PTE’s etc. The larger the load that you put on a server has the potential to exhaust important resources on the server which eventually causes a failure or server outages. Any type of memory leak in these areas could be detrimental to the stability of the serve

Have you ever wondered why store.exe always displays very high memory usage? At first I was very concerned when I noticed this on all of our exchange 2010 servers.

I proceeded to Google to do some research on why this always happens even though I would add so much more memory to our systems. Google has everything about anything related to Information Technology.

At Google I typed in many different combination of the problem. At first I tried searching only on what the server showed as high memory usage but that did not give me any good results.

I then proceeded to type the words store.exe, and believed it or not Google completed the phase, as usual. Google give me the phase “store.exe high memory exchange 2010”, that led me to a discussion that was happening at the Tech Net blog, about this same issue.  See link below.

The discussion on the forum then led me to a document at the Exchange Team Blog site where I finally understood in detail why this was happening, even though I had so much memory in the server.

Even though the document is related to Exchange 2007, it also applies to exchange 2010. It seem as though this behavior is normal in the exchange application. Microsoft explained that this was by design and there was no need to worry about how the memory was allocated.I was so relieved.

Exchange store.exe was designed to eat up as much memory as possible. When other processes needed this memory, exchange store.exe will give the memory back to other processes as needed.

Please visit the link in the quote above from the Microsoft team blog for the full story.


it manager salary

Installing SSL Certificates for Exchange 2013


When you are configuring SSL certificates for Exchange Server 2013, after you have generated the certificate request and received the SSL certificate from the certificate authority, you then need to complete the pending certificate request.

Sounds familiar? It really does appear that nothing has changed in reference to installing certificates in Exchange Server 2013 compared to Exchange Server 2010.

Paul from Exchange Server has just released a tutorial on how to complete a pending certificate request in Exchange 2013. This is a really good read if you have Exchange Server 2013 installed already.

Installing SSL Certificates for Exchange 2013 does appear to be no different from exchange server 2010.