Exchange 2007 Archiving Licensing Question

Simple question (I hope)
What type of CALS do I need for Archiving in Exchange 2007 (Hosted on an SBS Server).
Also, does the version of outlook matter for the archiving?
This topic first appeared in the Spiceworks Community

Agree with Cara on this and the transaction logs can be fairly hefty in size when migrating a bunch of data. One other option would be to;
1. do a backup of the associated stores/database right before migration.
2. then run on circular logging for those all databases within a storage group which will keep the logs in check
3. upon completion turn circular logging OFF, do a full backup and proceed along your way.
There is however some risk with using circular logging and you should read the articles below
http://exchangeserverpro.com/ems-enabledisable-exchange-server-2007-circular-logging/
http://technet.microsoft.com/en-us/library/bb331968%28v=exchg.80%29.aspx
http://technet.microsoft.com/en-us/library/bb331951%28v=exchg.80%29.aspx
http://blogs.technet.com/b/scottschnoll/archive/2011/06/27/circular-logging-and-mailbox-database-copies.aspx
Of course you could also keep things as they are and then monitor disk space and log volume during migration and as things rise Execute a Full backup to clear/truncate the logs. Technically its safer to do this then turn on circular logging but its
allot more resource intensive all the way around. Another option would be to schedule several full backups during the migration process, i.e. every NN hours etc and then the backups will happen automatically and all should be well as long as the
backups complete before the disk runs out of space from log file generation
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Similar Messages

Exchange 2013 and exchange 2007 mixed mode questions

I made my first attempt at migrating from 2007 to 2013 but ran into some problems. My 2013 CAS and MB servers are successfully installed along with their prerequisites (AD entries, external and internal DNS is active or ready to be, FW rules etc..). I'm
at this point here in the Microsoft plan..
http://technet.microsoft.com/en-US/exdeploy2013/PrintChecklist?state=2284-W-CQCkAgIAQACACEEAAQAAAA~~
"Perform the switch over"
My questions are about behavior.
1. When I have everything setup correctly and DNS and the SCP's changed, the Webmail OWA site for all users will be the 2013 login interface, and after logging in will my 2007 users then see the 2007 OWA interface on my old CAS?, or will they access their
2007 MB using the 2013 interface?
2. There is a "backend imap4" service on my 2013 servers. We will still have some 2007 mapi connected MB clients. Do I need these services started to hand off 2007 mapi requests to the 2007 portion of the environment?

Hi,
Yes.
Based on my knowledge, we should do some configurations.
More details in the following articles:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
Please also add the new URLs into certificates.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2007 mailbox migration question

Hi, I'm using Exchange 2007 and had most of my mailboxes are currently on a single mail server. I recently built two new mail servers and used CCR. I have 7800+ mailboxes and was told that when I move the mailboxes from the old mail server to the new
mail server that this will create a huge amount of additional transaction logs that wouldn't be cleared out until the next backup. We do nightly backup and have 1 TB of free space on our log drive. I can't find anywhere that documents that moving mailboxes
from one mail server to another would create additional transaction logs. I could understand the existing transaction logs would follow the mailboxes to the new mail server, but I don't see where it would create new transaction logs? I'm planning on moving
only 200-300 mailboxes a night, so this wouldn't happen all at once.
Any clarification would be helpful.
         Thanks,
          Andrew

Agree with Cara on this and the transaction logs can be fairly hefty in size when migrating a bunch of data. One other option would be to;
1. do a backup of the associated stores/database right before migration.
2. then run on circular logging for those all databases within a storage group which will keep the logs in check
3. upon completion turn circular logging OFF, do a full backup and proceed along your way.
There is however some risk with using circular logging and you should read the articles below
http://exchangeserverpro.com/ems-enabledisable-exchange-server-2007-circular-logging/
http://technet.microsoft.com/en-us/library/bb331968%28v=exchg.80%29.aspx
http://technet.microsoft.com/en-us/library/bb331951%28v=exchg.80%29.aspx
http://blogs.technet.com/b/scottschnoll/archive/2011/06/27/circular-logging-and-mailbox-database-copies.aspx
Of course you could also keep things as they are and then monitor disk space and log volume during migration and as things rise Execute a Full backup to clear/truncate the logs. Technically its safer to do this then turn on circular logging but its
allot more resource intensive all the way around.   Another option would be to schedule several full backups during the migration process, i.e. every NN hours etc and then the backups will happen automatically and all should be well as long as the
backups complete before the disk runs out of space from log file generation
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange 2007 Archiving

Hi all,
My client is starting to run low on server space and have identified that they would like to archive all emails before a certain date (i.e. 01/01/2010). Is there a way to achieve this from the EMC or EMS? Any searching I do just seems to show
information on how an end-user can achieve this from within their Outlook... hoping for a global solution I can run from the server to export and free up space.
Thanks

Hi,
Please check what takes up the most server space in Exchange 2007 server.
If it's transaction log, you can do full backup to truncate these transaction logs.
If it's database file, deleting mail items won't shrunk database size. You need to defrag your database after you delete mails. You can use MRM in Exchange 2007 to delete the messages.
For more details, please refer to the following article.
http://technet.microsoft.com/en-us/library/bb123548(v=exchg.80).aspx
Or you can export mails to pst file and then remove these mails from mailbox using
Export-Mailbox command with the DeleteContent parameter. You can look at the articles below.
How to Export Mailbox Data
http://technet.microsoft.com/en-gb/library/bb266964(v=exchg.80).aspx
Export-Mailbox
http://technet.microsoft.com/en-gb/library/aa998579(v=exchg.80).aspx
Best regards,
Belinda Ma
TechNet Community Support

Migration questions from Exchange 2007 to Exchange 2013

Dear Forum Members,
I'd ask just two short questions, regarding a migration from Small Business Server 2008 (Exchange 2007) to 2013. We installed the two Exchange 2013 servers, configured a DAG and updated every single URL (OWA, ECP, AnyWhere, Autodiscover etc.) to be a mail.domain.com
record (DNS round robin, since no HW load balancer :( )
Thankfully, the mail flow between the Internet and the other Exchange 2007 users are still working. Now for those users I've already migrated, if I check outlook connections there are several connections for GUID based servers via the DNS Round Robin
name proxy (the AnyWhere address). But I saw that there are still just one connection (type: Exchange Public Folders) to the old 2007 server. Is it okay? I'm a bit afraid to uninstall it because of this.
And the other thing: Based on what I wrote, do you think I've done it good? Or could I miss any important things? You are much experienced than me in these migrations so I hope that I can get some confirmation/advice here :(
ps: Is it good if I set NTLM authentication for Outlook AnyWhere?
Thank you really much for your help,
Best Regards,
Chris

Hi Chris,
Agree with Hinte, the user will still connect to the exchange 2007 server if there is a public folder database in the old server.
If the old public folders are no longer in use, you can delete the public folder database and create a new one in the exchange 2013 server, you can also consider migrating public folders to Exchange 2013 .
The following articles for your reference:
Use serial migration to migrate public folders to Exchange 2013 from previous versions
Set up public folders in a new organization
Step-by-Step Exchange 2007 to 2013 Migration
>>Is it good if I set NTLM authentication for Outlook AnyWhere?
The Outlook Anywhere authentication method you choose will depend on a few factors in your environment,
I recommend you refer to the following thread to understand how to choose:
https://social.technet.microsoft.com/Forums/exchange/en-US/75f8d6c4-70f4-49e5-ac32-a49dd91b5520/outlook-anywhere-ntlm-for-internal-users-and-basic-for-external-users?forum=exchangesvrclients
Exchange 2013: Configuring Outlook anywhere
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Online Archive for Exchange 2007

Prior to upgrading to Exchange 2013 before end of year, we are currently undergoing a thorough cleanout of our Exchange 2007 environment. Sadly, we had some users with well over 100K items in their deleted items, so you can only imagine what the rest
of their mailboxes look like. While we implement proposed policies for Exchange, we need an online Exchange Archive (preferably free) to be as seemless as possible to the user, but something that can automatically move messages to the archive based
on whatever threshold we set: 3 months after delivery, 6 months after delivery, or whatever. We would also plan to import any errant PSTs into this archive.
I found
THIS article, but it only mentions a patch that we are well beyond. Is there anything in Exchange 2007 similar to the
archive in 2010?
Thanks,
Nelson

Hi,
In Exchange 2007, there is no online archive feature, this feature is available in Exchange 2010 or later.
If you want to keep items for some time, as a workaround, you can use the Export-Mailbox cmdlet in Exchange 2007 to export items to PST file.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2013 Archiving question

Hi all,
I have a question on Exchange 2013 Archiving.
In the Default MRM Policy it has the Default 2 year move to archive tag.
When this runs it moves any emails over 2 years old to the users Archive mailbox.
I also know it will recreate the folder structure that was in the inbox.
My question is once it's moved to the users Archive what policy is applied to the emails and folders by default?
When you look at them it just says Using Parent folder Policy.
Would the parent folder be the Archive - %username it's self? Or is nothing applied and the users must go in a assign a tag to it?
Thanks

Hi,
If you apply one retention policy to a mailbox, then this retention policy will be applied to the primary and archive mailbox, this means that the archive mailbox have the same retention policy as primary mailbox.
Here is an example to help you to understand this.
You can use a DPT with the Move to Archive action to move items to the archive mailbox in two years, and a DPT with a deletion action to remove items from the mailbox
in seven years. Items in both primary and archive mailboxes will be deleted after seven years.
You can refer to the following article for more information.
http://technet.microsoft.com/en-gb/library/dd297955(v=exchg.150).aspx
Best regards,
Belinda Ma
TechNet Community Support

PowerShell Exchange 2007 Question To count up the total number of email addresses (view/hidden) per GAL

Hello All:
I am very new to Power Shell and need some help:
I have 224 GAL's on our Exchange System (Ex 2007) where, I need to count the total number of email addresses/display names assigned to each GAL. I am not sure how to set up a for-next loop in PowerShell. I am not sure how to set a input
file/variable, with the names of each GAL. (GAL is Global Address List)
I think it's $GALLIST = 'NameofGal1, NameofGal2, etc thru to NameofGaln' where n is the last GAL in the list.
So I need to now a command which would get all the gal names (Get-AddressList(?) for all the GAL's in the Exchange System and then pipe them into a function to count the number of email addresses.
In making a start with the following code and got stuck:
Get-Mailbox | Where {$_.GlobalAddressList -eq “GAL” -and $_.} | Select-Object Displayname, EmailAddresses, count
Missing or invalid property reference or expression.
At line:1 char:71
+ Get-Mailbox | Where {$_.GlobalAddressList -eq "GAL" -and $_.} <<<< | Select-Object Displayname, EmailAddresses, count
I think I know how to pipe the results to a csv file - with - Export-Csv -path c:\filename.csv - NoTypeInformation.
Please can someone advise. Please help.
Thanks in advance
PS - is there a way to access, read and display variable name and value which stores the number of email addresses/per GAL in exchange 2007 database so you don't have carry out a count exercise. Because this metadata will be in the Exchange DB?
Would this be easier to get?
Started building conditional statement:
Get-Mailbox | Where {$_.GlobalAddressList -eq "GAL" AND {{HiddenFromAddressListsEnabled -eq $True} OR {HiddenFromAddressListsEnabled -eq $False}} |
If {{HiddenFromAddressListsEnabled -eq $True} | Select-Object Displayname, EmailAddresses, count ELSE {HiddenFromAddressListsEnabled -eq $False}} | Select-Object Displayname, EmailAddresses, count
ENDIF
Export-Csv -path c:\test.csv -NoTypeInformation
Will this work? Checking to see how to do a for-next loop.
$GAL = Get-GlobalAddressList
foreach($GAL IN $GAL)
Get-Mailbox | Where {$_.GlobalAddressList -eq $GAL AND {{HiddenFromAddressListsEnabled -eq $True} OR {HiddenFromAddressListsEnabled -eq $False}} |
If {{HiddenFromAddressListsEnabled -eq $True} | Select-Object Displayname, EmailAddresses, count AS "Count of Hidden Addresses" ELSE {HiddenFromAddressListsEnabled -eq $False}} | Select-Object Displayname, EmailAddresses, count AS "Count of
Visible Addresses" |
Export-Csv -path c:\test.csv -NoTypeInformation |
not sure if this works and looks spaghetti -like!

Hi Everton,
In addition, If you want to export GlobalAddressList, please refer to the script below:
$filter = (Get-GlobalAddressList 'Default Global Address List').RecipientFilter
#filter HiddenFromAddressListsEnabled is ture
Get-Recipient -RecipientPreviewFilter $filter | Where-Object {$_.HiddenFromAddressListsEnabled -eq $ture} | Select-Object Name,PrimarySmtpAddress
#filter HiddenFromAddressListsEnabled is false
Get-Recipient -RecipientPreviewFilter $filter | Where-Object {$_.HiddenFromAddressListsEnabled -eq $false} | Select-Object Name,PrimarySmtpAddress
Refer to:
How to Export the Exchange 2010 Default Global Address List (GAL)
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Quick question about exporting email address and their alias from Exchange 2007 mailbox

Hi Everyone,
We have Exchange 2007 and 2013 servers. All users are still 2007 servers. I have a list of users around 179 out of 3000 in a CSV file. I would like to export those 179 users primary smtp and their aliases. Is it possible to achieve through any script?
Thanks in advance.
Regards,
Siva

Hello Siva,
You don't need a script for this. Information can be obtained with simple command.
$AllUsers = Get-Mailbox -ResultSize Unlimited | Select DisplayName,Alias,PrimarySMTPAddress,SamACcountName,Database,LegacyExchangeDN
$AllUsers | Export-Csv Outputfile.csv -NoTypeInformation
Try this and let me know if it helps!
if you want PrimarySMTPAddress and alias of only those users whose information on the excel sheet, then what do you have as the column name in the excel sheet which you are using to query on the server.
Considering that you are using Alias to query the server to get the details you can try below:
$Global:Output = @()
$CsvData = Import-Csv Inputfile.csv
foreach($line in $CsvData)
{$CurrentObject = $Line.AliasWrite-Host “Processing Obect “$CurrentObject “From Csv File”
–ForeGroundColor YELLOW$EmailIDJoin = ""$EmailAddresses = @()$UserInfo = "" | Select DisplayName,PrimarySMTPAddress,Alias,SamAccountName,Database,LegacyExchangeDN,EmailAddresses
$UserInfo.DisplayName = (Get-Mailbox $CurrentObject).DisplayName
$UserInfo.PrimarySMTPAddress = (Get-Mailbox $CurrentObject).PrimarySMTPAddress
$UserInfo.Alias = (Get-Mailbox $CurrentObject).Alias
$UserInfo.SamAccountName = (Get-Mailbox $CurrentObject).SamAccountName
$UserInfo.Database = (Get-Mailbox $CurrentObject).Database
$UserInfo.LegacyExchangeDN = (Get-Mailbox $CurrentObject).LegacyExchangeDN
$EmailAddresses = (Get-Mailbox $CurrentObject)|%{$_.EmailAddresses}
for($i=0;$i -lt $EmailAddresses.Count;$i++)
$EmailIDJoin += $EmailAddresses[$i].ProxyAddressString
if($i -lt $EmailAddresses.Count - 1)
$EmailIDJoin += ','
$UserInfo.EmailAddresses = $EmailIdJoin
$Global:Output += $UserInfo
#Export output to CSV File
$Global:Output | Export-Csv GlobalOutput.csv -NoTypeInformation

SBS2008: Move email from Exchange 2007 to new server with Exchange 2013

We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server.
Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one?
Old Server:
SBS2008 running Exchange 2007
New Server:
Server 2012
Exchange 2013
Any help is appreciated!

Hi Dave,
It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
you in the past).
For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model. In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
up to 2 Virtual Machines on same host).
There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration.
You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration. But the high points are in here. If it looks
like something you would be comfortable with then you should research more.
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
and migrate your workstations out of old domain into new domain. Whether this is more or less work at your workstation count is dependent upon a lot of variables.
If you have more questions about the process, update the thread and we'll try to assist.
Hopefully this info answered your original question.
Cheers,
-Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

Instaling forefront exchange 2007 SP2 in exchagne 2007

Hi ,
We have two exchange 2007 SP3 exchange server 1)cas and hub and 2)mail box server.
currently we configured cisco iron port as a send and recieve connector , all the mails are first come to iron ports .
there we enabled anti spam policies, but unfortunately cisco iron port license got expired , due to this we getting lot of spam mails .
now im planning to install Forefront security 2007 in both the server .
1)if configure FFS it will affect our mail flow settings ?
2)after configure FFS we have change the connector settings?
Regards,
Velu M
Regards, Velu M

Hi,
As far as I know, Forefront help us keep viruses out of our Exchange server. And it has no influence on the mail flow settings and the connector settings.
We can use Antispam filtering on Forefront to avoid spam emails. For more information about Forefront Protection 2010 for Exchange Server spam filtering, you can refer to the following article:
http://blogs.technet.com/b/fss/archive/2010/07/20/forefront-protection-2010-for-exchange-server-spam-filtering-filtering-and-powershell-videos-available.aspx
Additionally, you are welcomed to confirm it on our Forefront forum:
http://social.technet.microsoft.com/Forums/forefront/en-US/home?category=forefront
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them.
With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
Questions are, Is this the right way to migrate all the users to Exchange 2013?
Will it affect the operation of existing Exchange 2007 server?

Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
2013 for standardization.
Refer article for configuring URLs -
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Sarvesh Goel - Enterprise Messaging Administrator

Migrate from Exchange 2007 to Exchange 2013.

Hi All,
Need some advised here,
I am about to migrate Exchange 2007 with Windows Server 2003 to Exchange 2013 with Windows Server 2012 R2.
Which one should I migrate first? Windows Server or Exchange?
I tried to search it, i am a bit confuse with some of the answer. If someone can give some ideas, it will be great.
Thanks,

I'm not really sure what you are asking here. If you are asking here. I think you need to upgrade your Domain Controllers AND Exchange to 2012R2 and Exchange 2013.
I'm going to assume that they are going to be different servers. I would probably do the Exchange Migration first (assuming that you already at a supported level for Exchange 2013 https://technet.microsoft.com/en-us/library/aa996719%28v=exchg.150%29.aspx)
Also, before you actually make the change to your Domain Functional level, take a look at this blog post.
http://blogs.technet.com/b/exchange/archive/2015/02/13/considering-updating-your-domain-functional-level-from-windows-2003-read-this.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

How to migrate from exchange 2007 to 2013 step by step tutorials please

Hi
I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
We have 800 mailbox in total
Our domain controllers are
Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
I currently only have 1 exchange server 2007, with all the roles on the one server. I would like to keep that same as
well with exchange 2013.
Thanks

Exchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
migration task in more secure way.

From Exchange 2007 to exchange 2013

hi everyone,,
I need a video with brief description of how to deploy exchange 2007 to four servers exchange 2013
please to help,
thnx

Hi,
For your reference, here are some articles and step by steps migration from Exchange 2007 to Exchange 2013:
Upgrade from Exchange 2007 to Exchange 2013
https://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
Part 1: Step-by-Step Exchange 2007 to 2013 Migration
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Additionally, we can use Microsoft Exchange Server Deployment Assistant for deployment help. It is a web-based tool that asks you a few questions about your current environment and then generates a custom step-by-step checklist that will
help you deploy different versions of Exchange Server for different types of scenarios:
https://technet.microsoft.com/en-us/office/dn756393.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2007 Archiving Licensing Question

Similar Messages

Maybe you are looking for