Exchange 2007 SCR and MSExchangeMailboxAssistants Service

Morning All,
I did a SCR failover and failback yesterday to test Functionality on my exchange servers. everything worked as expected, however i am seeing the following error in my current live exchange server. Error is generated every 1 to 3 minutes.
An attempt to write an invalid event history watermark has been detected.
Database: '/o=XXX/ou=Exchange Administrative Group (XX)/cn=Configuration/cn=Servers/cn=xx/cn=Microsoft Private MDB'.
Consumer: 'df4b5565-53e9-4776-a824-185f22fb3ca6'.
Mailbox: '17a0f1bb-d835-4802-8135-3a0374ee6b71'.
Watermark counter: '0x89AF'.
Database event counter: '0x89B0'.
User performing the operation: 'SYSTEM'.
I have seen on previous posts that the MB server is not registering a MB as moved and that the MS Exchange Mailbox Assistants Service has to be restarted. What is the business impact of restarting this service on a server that is hosting all three exchange
roles (CAS, HT and MB). will it exffect mail flow or user outlook access in any way?
Thanks

Hello,
Glad to hear the issue is fixed.
Yes, some mailbox issues will be automatically fixed when moving it to another database.
Thanks,
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 Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

Update Rollup in Exchange 2007 SCR environment.

Dear Experts.
I am going to install Rollup 12 for Exchange 2007 SP3, so could you please confirm if any issue with Rollup 12 Exchange 2007 SP3?
Could you please advise to update Rollup in Exchange 2007 SCR environment with CCR.? I would appreciate. If you provide step by step
process, Thanks
Regards Vijaya Babu S | MCITP | MCTS | MCP| MCSA

Hi Vijaya,
Based on my known, Exchange 2007 SP3 Rollup 12 doesn't have a known issue so far.
About the steps of update Exchange 2007 SCR with CCR, please follow the above article Mike provided.
What's more, I recommend you make a complete backup of the clustered mailbox server prior to applying the update rollup and again after successfully applying the update rollup.
Here is an article for your reference.
How to Install Update Rollups in a CCR Environment
http://technet.microsoft.com/en-us/library/bb885047(v=exchg.80).aspx
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

How to Configure MS Exchange 2007 CCR and SCC Cluster in a single system

Hi i want to configure ms-exchange 2007 server for both SCC and CCR. i have two Windows Server 2008 on running on my hyper-v. by using cluster on both hyper v i want to install MS-Exchange 2007 for both SCC and CCR. ideally one windows server 2008 has
Active Nodes and another one has passive nodes. please guide me as i am new in the field

Duplicate of
http://social.technet.microsoft.com/Forums/exchange/en-US/edea43a1-59b4-4d26-9b41-76d0f4677095/how-to-configure-ms-exchange-2007-ccr-and-scc-cluster-in-a-single-system?forum=exchangesvrgenerallegacy#c6e08365-c01a-40aa-a8bc-94219757ef13
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2007, Contacts and Calendar OK , Email only folder structure

Hi, as i was reading many different topics I found that many of them had mixed answers between Exchange 2003, Exchange 2003 and 2007. Because of this mess, i wanted to focus ONLY on *EXCHANGE 2007*. That´s been said...
I have configured my iPhone with the user/pass/domain/address/SSL-ON, the iPhone connects to exchange and syncronize correctly Contacts and Calendar but not the Email. Email just shows folder structure.
After this first failed attempt I installed the certificate (Unsigned according to iphone and contains "Root Certificate")... No Improvement
I contacted my IT department , they said that Activesync was supposedly ON in my user profile and that SSL was mandatory. They also said that they cannot start testing thoroughly because it would disroupt other users. They also argue that many users are using activesync service with no problem what-so-ever. However they incouraged me to keep looking for an answer.
I couldnt find an apple guide to configuration for Exchange 2007, the enterprise deployment guide is just to vague.
_This info comes from "About" in OWA_
+Mailbox Owner: Juan I*** ****** [**@*****.net]+
+User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1+
+OWA Experience: Basic+
+User Language: English (United States)+
+User Timezone: (GMT-03:00) Buenos Aires, Georgetown+
+Exchange Mailbox Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=*+
+OWA Host Address: http://webmail.*****.net/owa+
+OWA Version: 8.0.605.16+
+Exchange Client Access Server .NET Framework Version: 2.0.50727.1433+
+Exchange Client Access Server OS Version: Microsoft Windows NT 5.2.3790 Service Pack 2+
+Exchange Client Access Server Version: 8.0.605.0+
+Exchange Client Access Server Language: en-US+
+Exchange Client Access Server Timezone: Hora estándar romance+
+Exchange Client Access Server Flavor: 32bit+
+Mailbox Server Name: exchange.*****.***+
+Mailbox Server Exchange Version: 8.0.605.0+
+Other roles currently installed on CAS server: Mailbox, Hub Transport+
+Authentication type associated with this OWA session: Basic+
+Public logon: Yes+
*Does anyone have a Check-List for Microsoft Exchange 2007?*
Please forgive my lousy English.
Message was edited by: Nachiarg

I don't think there will be a solution to this. Exchange 2003 just isn't supported.

Exchange 2010 - Decommissioning Exchange 2007 Coexistence and Removal of Public Folders

We are about to decommission exchange 2007, currently in coexistence with Exchange 2010.
We do not want to use ANY public folders in exchange 2010 going forward. Will do this after decom of 2007:
http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
I see this in the outlook connection status in outlook:
I have changed all Exchange 2010 mailbox databases to use a temporary 2010 public folders db named "public1" so that it is not communicating with the 2007 mailbox virtual server. However, the exact same connection status appears after I changed
the 2010 mailbox DBs to use a 2010 public folder db instead of the old 2007.
Question is, is it safe to decom the 2007 environment now? Is it normal to still have a connection to 2007 in "connection status" in outlook when the users mailbox is on a 2010 mailbox db? Is this connection related to public folders or something
else that needs modified before decom?
Thanks,
Josh

So, that wasn't the answer. I switched the Public folder DB on each mailbox database to a exchange 2010 server, PF DB, but hadn't actually moved any data from 2007 to 2010.
I didnt realize this is needed when we don't use public folders except for free-busy, default, etc.
What is the correct way to move the default public folders to a 2010 public folder?
I'm using the below URL as a template to migrate this info to a 2010 PF db.
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
"The user Public Folders then need to be replicated to the Exchange 2010 Public Folder database as well. It is possible to manually configure
all Public Folders with a new replication partner, but it’s better to use PowerShell scripts that Microsoft delivers with Exchange Server 2010. Open the Exchange Management Shell and navigate to the Scripts directory
by entering the CD $ExScripts command,
and execute the following script:
AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\"
-ServerToAdd 2010MBX"
My question is, do I have to do this "3rd step" since I don't think i have any custom "user public folders". Is this the user's free busy that I have to migrate, or is this author referring to custom PF db info?
Do I have to have public folders for free-busy and default exchange services at all in 2010?

Cannot connect to OWA after Exchange 2007 SP3 and Rollup 13 install.

Hi,
Our OWA website isn't accessible after we installed SP3 and rollup update 13 for Exchange 2007. When we attempt to visit the OWA URL, all we receive is HTTP 403.4 SSL is required to view this resource. Doug

Hi,
I recommend you follow the steps below for troubleshooting:
1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
https://URL), check "Only redirect" box and Status code Found 302.
4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
What's more, here is a thread for your reference.
Exchange 2007 SP3 Rollup 2 installed - OWA stopped working
http://social.technet.microsoft.com/Forums/en-US/8481eb3d-a6ab-42fc-b7ea-fa9a9a625e48/exchange-2007-sp3-rollup-2-installed-owa-stopped-working?forum=exchangesvrdeploylegacy
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2007 backup and recovery

hi...
I am using windows server 2008 and i installed exchge 2007 in that. who can i take backup only for my exchage 2007 log files and mailbox ect....
here i tryed using NTbackup utilities but it showing only the restore option in that utility....
Here we can take exchage 2007 backup using NTbackup???
Regards
Shahul

Hi Shahul,
You cannot use NTbackup to restore a particular mailbox from the VSS backup which was processed by Windows backup, and you also cannot use NTbackup with Windows 2008
to backup or restore Exchange. You can know more information from the following documents:
Ntbackup
http://technet.microsoft.com/en-us/library/cc754423(WS.10).aspx
Using Backup to Back Up and Restore Exchange Data
http://technet.microsoft.com/en-us/library/aa998870(EXCHG.80).aspx
Using Windows Server Backup to Back Up and Restore Exchange Data
http://technet.microsoft.com/en-us/library/ee221172(EXCHG.80).aspx
If anything is unclear, please feel free to let me know.
Best Regards,
Evan
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.

Problem with exchange 2007 SP3 and mac mail app loading mails

Hi,
since a few days i am having a problem with mac's (using either the included mail app or outlooc 2011 for mac) syncing mails with my exchange server. both, mail and outlook) connect successfully to my excahnge 2007 sp3 rollup 14 server, but when
they start syncing mail they dont load any mails or only load the headers and keep saying loading (of body)
when i open the https://server/EWS/Exchange.asmx on the browser it asks for the user/pwd and lets me open the xml once, the next time it crashes.
in the eventlog i am getting the error that: a process for app-pool MSExchangeServicesAppPool couldnt respond to a ping. the event id is 5010.
all my microsoft outlook accounts, outlook web acces and the mail on mobile devices (iphone and android) work fine.
does anyone have an idea what could be the issue for this strange behavior?
thanks,
chris

Hi,
According to the error message, "a process for app-pool MSExchangeServicesAppPool couldnt respond to a ping. the event id is 5010", I find a related article for your reference:
Event ID 5010 — IIS Application Pool Availability
http://technet.microsoft.com/en-us/library/cc734991(v=WS.10).aspx
Please follow the article to check whether application pool has been started.
Additionally, I notice that you said "all my microsoft outlook accounts, outlook web acces and the mail on mobile devices (iphone and android) work fine.", please run following command to check whether parameter "EwsAllowMacOutlook"
value is True:
Get-CasMailbox | FL
If the parameter "EwsAllowMacOutlook" value is False, please set it to True via following command:
Set-CasMailbox -Identity FQDN -EwsAllowMacOutlook $True
If still not work, please contact MAC Support for help. For your convenience:
http://answers.microsoft.com/en-us/mac/forum/macoutlook?tab=Threads
Thanks
Mavis Huang
TechNet Community Support

Unable to share calendars - This sharing message is not valid - Outlook 2013 Exchange 2007

Running Exchange 2007 latest and greatest service pack and rollup with Outlook 2013 fully patched. When users attempt to share their calendar, the recipient receives an email that says "This sharing message is not valid. All action buttons have been
disabled" and "(Sender not verified) - Calendar".
We're not using IMAP or POP. Was working in the past and stopped working.

Hi,
Is Exchange account the default account in Outlook?
Does this issue occur on all users? (If no, please try to recreate problematic user’s profile to check this issue)
Please check the following setting:
Open AD users and computers.
Right-click on problematic user to properties.
Under General tab, check if the E-mail field is right.
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]
Lynn-Li
TechNet Community Support

Coexistence Exchange 2007 and 2013 - Clients on 2013 cant connect to Outlook, OWA works fine

Hi
We are currently running all our users on Exchange 2007. I've installed Exchange 2013 on another hardware following several guides on coexistence between 2007 and 2013.
I'm now testing with a few test users I've migrated from 2007 to 2013.
Everything was working fine until I messed up with something. It's either the certificates and/or Exchange Web Services and/or activating Outlook Anywhere.
Now, all my tests users on Exchange 2013 can connect and send/receive emails on OWA, but Outlook clients cannot connect to Exchange server.
When I start Outlook, I get the error Unable to open the default mail folders
When I try to create a new Outlook profile, I get the error: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
When I click on Check Name, I get: "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
Thanks for any help you could provide
Martin

Changed the
ExternalClientAuthenticationMethod for the 2007 server.
Output for Get-OutlookAnywhere | fl *method*
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
Now everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's
asking for credentials.
If I dig further and try to manually configure server settings:
If I specify the Exchange 2013 server and try a 'Check
Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
If I specify the Exchange 2007 server and try a 'Check
Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"
Any other thoughts on this issue?
Thanks,
Martin

Can't sync Work exchange 2007 email, calendar and contacts on my Mac

I am new to Mac. I've been trying to set up my work email, calendar and contacts (Exchange 2007) on my new personal Mac without much success. I have all contacts, calendars and mail syncronized on my Iphone, but when trying to sync calendars via Itunes with Mac ICal, all it does is add ICal entries onto my Iphone (and then they appear twice on iphone and work calendar)
Haven't figured out how to import contacts into email either, although I had some success in setting the account up as a pop account in Mail (we use OWA otherwise for web access)- but can't send, just receive.
Please help - where can I find some stept by step guidance / tutorials on how to do this? I don't want to subscribe to MobileMe or install any windows or Microsoft software on my Mac. Many thanks in advance.

I could very well be wrong, but here's what I did.
At my work we got an Exchange 2007 server and I got an account on it, so I set up my iPhone, but I didn't sync it to the calendars on my desktop Mac, instead I went into Mac Mail, Preferences, Accounts, then added an Exchange account inserting all the same account information that I had put into the iPhone. Then my iCal, Mail, Address Book all synced over the air. I do not have MobileMe, but I'm not sure what my work has on their Exchange server.

Exchange 2007 edb to Exchange 2013 - mailbox extraction and mounting

Hello everyone, here is my question:
I have a client who has Exchange 2007 running on a Domain Controller which is a Server 2008 and that is the only domain controller in his environment. That said, his domain controller crashed and all the AD data is now lost along with Exchange except the
EDB files. He wants to create a new domain controller with Server 2012 and wants to deploy Exchange Server 2013. Since the Domain Name will be the same, is it even possible to extract the mailbox information from Exchange 2007 EDB and attach it with new Exchange
Server 2013 and point them to newly created users on Exchange? If yes, how exactly will this work? Thanks in advance.

Excellent and factual responses from the others and the instructions/guidance should serve you well. If however you want to avoid building a new server etc you could use Lucid8's DigiScope
http://www.lucid8.com/product/digiscope.asp to open the 2007 EDB on a 64 bit machine and then you could take 1 of 2 actions to resolve your issue.
1. You could then export all mailboxes to PST and then Import them into the 2013 environment
2. OR you could have DigiScope migrate/recover the data directly from the offline 2007 EDB into the Production 2013 server on the fly, i.e. no end user downtime is required.
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

BPA shows domain prepped for Exchange 2007 SP1 after SP3 install

Hello,
I have a Client with a domain that is at 2003 domain functional level and 2000 forest level.
The client had Exchange 2007 SP1 and I have just upgraded it to SP3. There is one CAS, one Hub Transport, and one Mailbox Server (All three had Exchange 2007 SP1).
The domain and forest were prepped earlier by someone else and when I ran the installation program, it didn't pop up any errors on any of the servers.
The upgrade to SP3 is in preperation to Exchange 2010. Everything is working ok. I have checked:
1) In ADSIEdit, Exchange System Objects properties: Object Version =11221.
2) In ADSIEdit, Services>Microsoft Exchange>Organization: Object Version =11222
3) In ADSIEdit, RangeUpper value of ms-Exch-Schema-Version-Pt object = 14625
However, When I run the Exchange BPA, it reports that the domain is prepped for Exchange Server 2007 Service Pack 1 (In informational items). This is an informational item and not a warning or alert. However, I am concerned. Is this normal, and will it affect
the migration to Exchange 2010?
Thanks,
HA

Hello Ha20,
Based on my experience, it will not affect the migration. However, it’s recommended to prepare the schema again to avoid any potential issues.
Thanks,
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 Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

SBS 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

Exchange 2007 Renew Certificate via IIS Manager

I am currently in the process of renewing the Exchange 2007 certs and have searched through forums in regards to this topic and can't seem to come across a proper answer. Is it possible to renew the Exchange 2007 cert using the IIS Manager or is Powershell
the only way of doing so? Under the "IIS Manager > expanding server name > expand websites > default website properties > Directory Security > Server Certificate" you are presented with the option to renew the existing cert. This to
me seems a lot easier than using shell to request a whole new cert. I am not a fan of the how Powershell can be a bit destructive when requesting a new cert and overwriting the existing one leaving your little ways of backing out if something goes wrong. Can
someone confirm if using IIS manager is a viable way of renewing the Exchange 2007 cert. I prefer to keep the exact settings of the existing certificates.
Thank you,
Emmanuel
Emmanuel Fumero Exchange Administrator

Hi
Yes its possible in Exchange 2010 through EMC . Not sure if this works in Exchange 2007 since i haven't tried renewing through GUI in exchange 2007 and currently do not have any customers running e2k7 to check this option. Probably you can give it
a try in Exchange 2007 and see if these options are visible. Please check the following,
When you right-click your Exchange Server, you can select New Exchange Certificate, which will launch the New Exchange Certificate Wizard.
After defining a friendly name, you are ready to provide all needed information:
After clicking Finish, you will have a certificate request that you can use ti get a certificate from your own CA, or from an external CA. The Exchange Management Console will show the request as well
1.Start the Exchange Management Shell. Click Start > Programs > Microsoft Exchange Server 2007, and then click Exchange Management Console.
2.Click the link to "Manage Databases", and then go to "Server configuration".
3.Select your certificate from the menu in the center of the screen (The certificate will be listed by the Friendly Name you chose when creating the CSR), and then click the link in the Actions menu to "Complete Pending Request".
4.Browse to the certificate file you just copied to your server, then click Open > Complete.
URGENT!! You may receive the following error: "The source data is corrupted or not properly Base64 encoded." You can ignore this error
5.Press F5 to refresh the certificate list. Verify that it says "False" under "Self Signed".( if its 3rd party or feom CA)
6.To enable your certificate, return to the Exchange Management Console and click the link to "Assign Services to Certificate."
Hope this helps
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.
Regards
Sathish

Exchange 2007 SCR and MSExchangeMailboxAssistants Service

Similar Messages

Maybe you are looking for