Decommission Exchange 2007 Mailbox Server from Cluster

Hi! I realize this is an Exchange 2013 forum, however as I do not see any forums for older flavors of Exchange I'm going to post this here. If a better forum exists please let me know and I'll happily move to that forum for my answers.
I am just finishing a migration from Exchange 2007 to Exchange 2013. In the Exchange 2007 environment I have 2 CCR Mailbox Clusters. While working to decommission the first of the two clusters I successfully evicted the passive node, however
I mistakenly evicted the active node rather than removing it by running the Exchange Setup Wizard as outlined in the TechNet article "How to Remove the Active Mailbox Role from a CCR Environment".
Now, when attempting to uninstall Exchange 2007 using the Setup Wizard in Add/Remove Program I get the following error during the prerequisite check for the 'Mailbox Role':
Error:
Exchange server FQDN was not found. Please make sure you have typed it correctly."
Setup then completes.
Is there a way to cleanly uninstall Exchange 2007 and clean-up Active Directory?
Thanks!

Hi Jesse,
Thank you for your question.
We could run “ADsiedit.msc” in run, then navigate
Configuration [<domainController>.contoso.com]> CN=Configuration,DC=contoso,DC=com> CN=Services> CN=Microsoft Exchange> CN=<OrganizationName> CN=Administrative Group> CN=Exchange Administrative Group>CN=Server
We could check if mailbox server is existed in this container, we could remove it.
Notice: Before we remove it, we could make a backup for AD database. We suggest you call MS engineer for help.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Similar Messages

How to decomission a Exchange 2007 Mailbox server

Hello,
We are running Exchange 2007 SP3 servers. We currently have a Mailbox server we want to decommission. I'd like help on how to achieve this. I want to make sure that all mailboxes have been moved from that server and remove the Public Folder database as well.
I understand that the Public Folders needs to stop replicating to this server, can someone please guide me on how to do that?
All kinds of help are appreciated. Thanks!

For the public folder stuff, see these scripts: https://technet.microsoft.com/en-us/library/aa997966(v=exchg.141).aspx
The system folders can be replicated with the '\non_ipm_subtree' identifier, but some system folders are per-server and don't need to replicate. OAB distribution however
is one that might matter.
Mike Crowley | Microsoft MVP
Baseline
Technologies

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?

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

How to connect Exchange 2007 mailboxes to existing users

Hi all
We use IDM/Waveset 8.1.1 and the Active Directory adapter for Exchange 2007 mailbox provisioning. We use a role for the AD account and a role for the Exchange mailbox.
When we add the Exchange role for a user, the mailbox is created (the IDM gateway sends the powershell command enable-mailbox) => it is fine.
When we remove the Exchange role for the same user (after some mails have been sent with this mailbox), the mailbox is disconnected (the IDM gateway sends the powershell command disable-mailbox) => It is also fine.
But when we add a second time the Exchange role for the same user, a new mailbox is created, while we want that the disconnected mailbox would be re-connect to the AD account (with the powershell command connect-mailbox).
Does anybody know if it is possible to do so ?
Thank you
Gilles

As long as your I.T. folks have the same DNS name pointed to the server from the inside as they do from the outside, it should work fine. To be clear, if your server is mail.company.com that name should oint to the server from inside and outside the company. Then it will work fine without any changes on your iPhone.

Error during Exchange 2007 mailbox provisioning with IDM 8.1.1.1

Hi
We want to create Exchange 2007 mailboxes from IDM.
When we let Exchange set the SMTP address (EmailAddressPolicyEnabled=true), it works fine
But when we set the SMTP address in IDM with the attribute PrimarySmtpAddress (and EmailAddressPolicyEnabled=false) there are an error and an information in the provisioning task
Error : PowerShell:6c13f14c-3825-4064-a585-48b4756de3a3 is not a mailbox user
Information : Added exchange mailbox to the user based on the RecipientType change from: 'User' to: 'UserMailbox'
We see that the mailbox has the SMTP address set by Exchange.
After 5mn, the task ends successfully and we see that the SMTP address is the one set by the IDM attribute PrimarySmtpAddress.
We guess that this error is caused by the active directory replication delay between controllers.
Does anybody know how to solve this problem ?
Thank you

Hi Patrick
Thank you for your answer.
The cmdlet enable-mailbox can be used with the PrimarySmtpAddress option and, in this case, the EmailAddressPolicyEnabled option is automatically set to false.
Cf. the MS technet help : "The PrimarySmtpAddress parameter specifies the primary SMTP address for the mailbox. By default, the primary SMTP address is generated based on the default e-mail address policy. If you specify a primary SMTP address by using this parameter, the command sets the EmailAddressPolicyEnabled attribute of the mailbox to $false, and the e-mail addresses of this mailbox aren't automatically updated based on e-mail address policies."
I have tested this option on our Exchange 2007 environment and it works fine.
In IDM if PrimarySmtpAddress is used but not EmailAddressPolicyEnabled, there is an error : "PowerShell:The e-mail addresses for this recipient are automatically generated based on e-mail address policies. To modify the primary SMTP address for this recipient, you must disable automatic updating of e-mail addresses based on e-mail address policy”
If PrimarySmtpAddress is used and EmailAddressPolicyEnabled is set to false, then the log shows that 2 powershell commands are run by the gateway, the second immediately after the first.
Enable-Mailbox with the parameters -Identity and -Database, run with no error
Set-Mailbox with the parameters -Identity, -EmailAddressPolicyEnabled (set to FALSE) and -PrimarySmtpAddress, run with the error “…is not a mailbox user.”
After 5 mn (the retry delay) another powershell command is run :
Set-Mailbox with the parameters -Identity, -EmailAddressPolicyEnabled (set to FALSE) and -PrimarySmtpAddress, run with no error.
The solution would be that IDM, when PrimarySmtpAddress is set, runs only the command Enable-Mailbox with the parameters PrimarySmtpAddress, which set automatically EmailAddressPolicyEnabled to FALSE
Gilles

How to introduce exchange 2013 mailbox server in an existing Exchange 2010 Environment

Hi All,
we are planning to install exchange 2013 mailbox server in an Exchange 2010 environment. we have 3 MB servers, 1 CAS 1 HUB which is installed with Exchange 2010 SP3 Enterprise Edition. how to install new exchange server 2013 and i have to add the 2013
servers in to existing DAG and migrate all mailboxes in to 2013 server. Please advise me from the scratch. also will it be create any impact in my existing setup.
Thanks, Venkatesh. "Hardwork Never Fails"

For a step by step follow the deployment assistant
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Migrate exchange 2007 mailboxes to exchange 2013

Hi Guys,
im trying to move exchange 2007 mailboxes to 2013. to cut to the chase, is this possible because im getting different kinds of errors?
Please advise if this is possible and how to do it.
Thanks!

Hi,
Below link also will help you
Microsoft Exchange Server Deployment Assistant
http://technet.microsoft.com/en-us/office/dn756393.aspx
Before migrating exchange server, Make a plan
try to practcice on lab. " Production environment and practice lab is entire different"
I dont know your environment. Hope your Domain controller and Exchange environment is residing in same place. If it is different site, move FSMO roles to that site for installing purpose.
IT is really challenge and excitement .
Try to find the solution of client outlook connectivity,
I had this problem, after I install Cumulative update, this problem gone.
Login ECP console after install exchange server,
Certificate installation,
DNS pointing, port forward,
Apply auto discover.
I faced another issue as well during the installation. My ex admin upgraded exchange server 2003 to 2007. He may not uninstall exchange server 2003 properly. Exchange server
2003 record was in active directory. Exchange 2013 doesnt suport mixed version of exchange 2003 and 2013. I have to delete the Exchange server 2003 record under DNS and Adsiedit. After that only exchange server 2013 allow to continue to install.
Best of Luck " Nothing is impossible"
Regards,
Joby

Exchange 2007 edge server with ironport

I currently have a frontend exch 2003 and backend exch 2003 server with ironport. my mx record is the ironport which then forwards into the backend server. The frontend server was only used for owa and using outlook with https connection to exchange.
With 2007 it has more functionality and the front end server is now called an edge server. Should I have mx go there then to ironport or vice versa? I'm thinking ironport to edge server to hub transport server. Is that correct? will it work?
anyone have exchange 2007 edge server with ironport? what are you doing?

well that wouldve been nice to know a little earlier. anyway I have ironport successfully sending mail to the edge server who sends it on to the hub transport server. right now the client access server is on the same as the hub but can be easily moved later. this is for very few people so its not like I need to off load anything as its a powerful dual core server. anyway now with the edge server I can test how effective it is versus the ironport. I'll let everyone know when you can ditch the ironport for msft's edge server. (Don't hold your breath).

Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

I'm trying to remove Exchange 2007 from an SBS 2008 server
(Server 2008 Standard FE). My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers. We have two full blown DC's in the environment.
I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server. I can NOT seem to find a TechNet article that shows me how
to proceed in this kind of scenario. I am trying to use the TechNet article:
http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard.
When I go to Disable Mailboxes I get the following error:
Microsoft Exchange Error
Action 'Disable' could not be performed on object 'Username (edited)'.
Username (edited)
Failed
Error:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
OK
I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010. I just want
to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
Can someone point me in the right direction?
Thanks!

Hi,
Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
On current situation, please refer to following articles and check if can help you.
Transition
from Small Business Server to Standard Windows Server
Removing SBS 2008 –
Step 1: Exchange 2007
Removing SBS 2008 – Step 2:
ADCS
Removing
SBS 2008 – Step 3: remove from domain / DCPROMO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best regards,
Justin Gu

Removing mailbox server from Exchange 2010 DAG - Node not fully cleaned up

Hi,
We are in the process of decommissioning some old Exchange 2010 servers. I have just attempted to remove one of our mailbox servers and have received a number of errors, related to its removal from the DAG.
I have already removed the Public Folder replicas and all mailbox database copies. I then tried to evict the server from the DAG and received the following warning:
I then ran the command that was recommended, from another server and in an administrative command prompt:
I have looked in this log on both the server I ran the command on, a CAS server, and the mailbox server itself and can see no evidence of this error 2 that is listed here.
If I run the Powershell command to look at the DAG I cannot see it there any more. I am assuming that this error message might only be an issue if I was planning on re-using this server somewhere else in Exchange or perhaps adding this server to another
DAG. But I just want to decommission it.
Can anyone put my mind at rest as to whether this is a genuine concern or not. If not my next step is to uninstall Exchange 2010 from this server and turn it off.

Hi Belinda,
I get the following:
[PS] C:\Windows\system32>Get-DatabaseAvailabilityGroup
Name Member Servers
Operational Servers
DAG01 {WSR-EX-01, WSR-EX-101, WSR21}
It doesn't look like that server is part of the DAG any more as far as I can see. I just can't explain that error message reported from the cluster command. As far as I can see the server is isolated. I already removed its database copies as a pre-requisite
before removing it from the DAG as per this guide:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27039933.html
I found a nice little script that gave reports on your Public Folder configuration and it highlighted that some of our folders were not being replicated properly across our mailbox servers. This helped me in removing these services from the server.
It is currently doing nothing at this time as far as Exchange Services are concerned.

Errors Decommissioning Exchange 2007 Server

We are attempting to decommission an Exchange 2007 Server (single server). We have already gotten 2010 set up, installed, mailboxes moved and public folders moved. We went through and removed the replicas on the old server as well as removing the mailbox
database and public folder database.
From this point we are attempting to Uninstall Exchange 2007 using either the Wizard or through cmd using setup.com /mode:uninstall after navigating to the Bin folder in the Exchange server. Each time however, we get the same error regardless of how we are
doing it.
We uncheck all roles, hit Next, and it fails during the Readiness Check within 10 seconds on each role (Mailbox, Client Access, Hub Transport) each time saying: 'An error occurred while running the test. The Computer may be out of Memory, or the XML files
have been modified. Parameter name: ConfigurationFileLocation'
I've gone through using ADSI Edit and removed the server from the Configuration>Services>SiteDomain>Administrative Groups>Exchange Administrative Groups>Servers
and it was none existent in the Databases section.
Even after all of these steps I'm still getting the error about the memory or XML file issue. Is there a way to replace the XML files with 'clean' ones or a way to repair the existing ones? I'm just simply wanting to uninstall it at this point.
Thanks!

Hi,
From your description, I would like to clarify the following things:
1. It is not recommended to uninstall Exchange server in ADSIEdit.
2. The above error indicates that one of the xml files is corrupted, you need to re-download it for troubleshooting.
Hope my clarification can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

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

Exchange 2007 setup, transitioning from Exchange 2003

Hello Exchange Experts,
I just setup a Exchange 2007 within our domain, transistioning from Exchange 2003, question: When I added the mailbox role on the setup of Exchange 2007, the mailboxes appeared instantly from our Exchange 2003..the connector I'm assuming automatically connected
during the 07 setup. Is this normal? I was under the assumption to migrate mailboxes from 03 to 07 Exchange, the wizard must be ran. All active mailboxes from 03 appear. I attempted to migrate one mailbox using the wizard, error after the wizard completed,
mailbox exists. Makes sense, just not understanding how the mailboxes flowed/migrated automatically without running the migration steps. Would someone explain? You could say, this migration is very new to me.
Thanks in advance!
James

Ronny, our company had an existing license for 2007. Of courser 2010 or 2013 would have been a better transition, but 2007 is it. The server 2007 has met all the criteria for the transition, spent last moth prepping everything on 2003 and 2007. I'm just
not understanding why the mailboxes appeared upon 2007 immediately after adding the mailbox role. The management console on 07 shows the mailboxes reside on 03 exchange server. I did not go through the process/wizard to move to 07. Perhaps because
during the installation of Exchange 07 created the connector from 2003? Maybe that's my question.
Mail flow is very responsive now, just wondering for the reasons of decommissioning exchange 2003 at a later date. Exchange 2003 is functioning now as a bridgehead, working perfectly now.
Thanks for your input.
James
Thanks Ronnie for your input! Issue resolved

Enabling Exchange 2007 Mailbox

We are provisioning a mailbox to Exchange 2007 in IDM and we are being forced to run a PowerShell script which in turn runs some Exchange commands. These keep bombing out with an error saying that Exchange server is crashing (which it is not!). We have tested these scripts locally on the machine and they execute perfectly. We have also troubleshot up to the PowerShell execution which outputs test info but will not execute the Exchange items. Is there something that IDM needs to set in order to execute remote Exchange actions in PowerShell??

I've found the solution. The error I got was related to the DOS environment variables SET. So, I had to set inside my resource action all the variables I suppose I need to run the powershell. This is the code of my resource action:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE Waveset PUBLIC 'waveset.dtd' 'waveset.dtd'>
<Waveset>
<ResourceAction name='AfterCreate_AD'>
<ResTypeAction restype='Windows Active Directory' timeout='100000'>
<act>
@echo off
SET ALLUSERSPROFILE=C:\Documents and Settings\All Users
SET APPDATA=C:\Documents and Settings\zuser\Application Data
SET CLIENTNAME=T0001895481
SET ClusterLog=C:\WINDOWS\Cluster\cluster.log
SET CommonProgramFiles=C:\Program Files\Common Files
SET COMPUTERNAME=SUN-EM2QWM22QOR
SET ComSpec=C:\WINDOWS\system32\cmd.exe
SET FP_NO_HOST_CHECK=NO
SET HOMEDRIVE=C:
SET HOMEPATH=\Documents and Settings\zuser
SET LOGONSERVER=\\server
SET NUMBER_OF_PROCESSORS=1
SET OS=Windows_NT
SET PROCESSOR_ARCHITECTURE=x86
SET PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 8, GenuineIntel
SET PROCESSOR_LEVEL=15
SET PROCESSOR_REVISION=0408
SET ProgramFiles=C:\Program Files
SET SESSIONNAME=RDP-Tcp#6
SET SystemDrive=C:
SET SystemRoot=C:\WINDOWS
SET TEMP=C:\DOCUME~1\zuser\LOCALS~1\Temp
SET TMP=C:\DOCUME~1\zuser\LOCALS~1\Temp
SET USERDNSDOMAIN=server.domain
SET USERDOMAIN=domain
SET USERNAME=zuser
SET USERPROFILE=C:\Documents and Settings\zuser
SET windir=C:\WINDOWS
%comspec% /c C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "E:\Program Files\Microsoft\Exchange Server\Bin\exshell.psc1" -NoLogo -Noninteractive -Command ". Enable-Mailbox -Identity '%WSUSER_canonicalName%' -Alias '%WSUSER_AdMailNickName%' -Database '%WSUSER_AdServername%' -DomainController %WSUSER_AdDomainController%"
exit 0
</act>
</ResTypeAction>
</ResourceAction>
</Waveset>
Hope it helps

Decommission Exchange 2007 Mailbox Server from Cluster

Similar Messages

Maybe you are looking for