Installation / cleaning exchange 2003
Hello,
In our environment, we used to have exchange 2003 but the server is crashed and not turning on. Also, we are not concerned about restoring its data.
I want to install Exchange 2013 but am not able to do so as the AD is still recognizing that there was an exchange 2003 version installed.
What is the best way to clean the active directory so that I can proceed with installing the exchange 2013? My current environment is based on Windows 2012.
Thank you
Goldenberg
I would reinstall Exchange 2003, restore your databases, and then perform a 2step migration to 2013 if you want to go to Exchange 2013.
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
Similar Messages
-
Exchange 2003 Permissions Error when attempting to forward emails
Server 2003 R2 (fully patched as of 11/2013) running Exchange 2003 SP2 (Built 7638.x2) on ESXi 4.1; WinXP clients and Server 2003 Terminal Servers running Outlook 2003; Domain and Forest are running at 2008 Functional Levels.
Occasionally, some users are receiving this error message: "You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator" intermittently when attempting
to 1) forward email both to and from senders/recipients inside and outside the domain, 2) When attempting to modify the subject of a previously received email (I didn't know you could do that), 3) When attempting to open received attachments.
There is no discernible pattern to the users or the original senders of the emails.
Most of the results I've found when searching relate to NTFS permissions or a ReadOnly propery on items in the users's profile folder, or sending on behalf of another user - these either do not apply or have been verified as not the cause.
During the initial rash of problems when there was a problem with an attachment and we absolutely needed it, I was able to connect to OWA using a special administrative account with access to the mailbox, open the attachment and log out. Once I had
done so with this account, the end user was able to open the attachment on their own without a warning.
Changes made to the environment prior to this issue that may be related (nobody remembers when exactly this started, so I can't state that it definitively happened after this change):
All servers were virtualized on ESXi 4.1 in late 2011; subsequently converted and migrated to Hyper-V Server 2012 in early 2013 (with the exception of the Exchange and SQL servers).
All 2003/R2 domain controllers demoted and removed; DFL/FFL raised to 2008; SYSVOL replication was migrated from FRS to DFS-R.
Troubleshooting steps:
Exchange server and affected client computers have been restarted several times; the various exchange services have been restarted; permissions on the mailboxes and AD objects have been verified; event logs are generally clean with the exception of ActiveSync
errors for a single user not currently affected by forwarding emails, there are no other errors reported.
Per recommendations on another forum, I had enabled several diagnostic logs in the diagnostic logging tab of the server. Unfortunately not much was found in the Application log even after filtering out the basics. There were occasional errors
referencing User A failed to modify an item in User B's mailbox because access was denied; however, I was unable to correlate these errors to any reported incidence of the above message.
I created a new mailbox database on the same server and migrated all the mailboxes to the new database, there was no change; users immediately began seeing these errors.
Over a holiday weekend, I then spun up a new Win 2003 R2 server, with a fresh installation of Server 2003 R2 (also fully patched through 11/2013) running the same version of Exchange 2003 SP2 this time running as a virtual guest on Hyper-V Server 2012.
I migrated all mailboxes from the original mail server to the new mail server and it appeared that the problem was remedied; however, it has slowly started up again and is starting to become more frequent.
I'm really at my wits end with this problem and would like to get it resolved before we purchase and install our new Exchange Server later this year.Updates
Users have reported that they can forward the email from OWA; even after doing so, they are unable to forward from Outlook. So either my previous notes on the issue were wrong, or this is just more of the "intermittent" nature of the problem.
I will have to investigate what logging options are available to me at the Outlook client level - any thoughts on that subject are also welcome.
Users have now reported that a previous (rarely used) workaround (the administrative account opening the email in OWA) no longer enables them to view attachments or forward emails in Outlook.
I'm still adjusting the various diagnostic logging settings to see if I can spot an event which corresponds to a reported occurrence. The most unusual warning reported is the following:
Source:MSExchangeIS Mailbox Store
Category: Access Control
Event ID: 1029
[email protected] failed an operation because the user did not have the following access rights:
'Delete' 'Read Property' 'Write Property' 'Create Message' 'View Item' 'Create Subfolder' 'Write Security Descriptor' 'Write Owner' 'Read Security Descriptor' 'Contact'
The distinguished name of the owning mailbox is /O=DOMAIN/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=USER_B. The folder ID is in the data section of this event.
However odd these occasional warnings are, they do not appears to correlate to the reported permissions issue. Everytime I've seen one of these events, I've inquired with "user_A" to see if they've recently seen the popup and in each case they have
not. -
Error 0xc1037986 during Exchange 2003 std remove
This morning I tried to remove Exchange 2003 on a server due to be decommissioned. During the removal I received a prompt for the installation media, and after I pointed it to my Exchange disk I received this error: "Setup failed while installing sub-component of Windows Active Directory schema update with error code 0xc1037986". It then asked to reboot, so I said yes. After a reboot, none of the Exchange services will start. I've noticed these in the event log:
Exchange Server component Microsoft Exchange Messaging and Collaboration Services failed.
Error: 0x8000ffff - An unexpected error occurred.
Exchange Server component Microsoft Exchange Forest Preparation failed.
Error: 0xc1037986 - Cannot find the file.
EventType exchangesetuperror, P1 6_5_6944_0, P2 remove, P3 microsoft exchange forest preparation, P4 install, P5 c1037986, P6 _null_, P7 1, P8 NIL, P9 NIL, P10 NIL.
Exchange Server component Microsoft Exchange System Management Tools failed.
Error: 0xe0070101 - An unknown error has occurred.
EventType exchangesetuperror, P1 6_5_6944_0, P2 remove, P3 microsoft exchange system management tools, P4 install, P5 e0070101, P6 _null_, P7 1, P8 NIL, P9 NIL, P10 NIL.
I thought I would reapply SP2 and try the removal again, but SP2 will not install because I can't start the Exchange services.
The error I am receiving matches up with "Microsoft Exchange Forest Preparation failed". Why would it be trying to run forestprep? Is there a course of action for this server now - it's in a very bad way!I know this is an old thread, But I ran into this issue and discovered that the sbs 2003 r2 disks that were used for install wouldn't work for exchange2003 removal. since sbs2003 is nolonger available on technet, I downloaded and extracted the exchange 2003
iso ( no service packs). when asked for the sbs disk i pointed the wizard to D:\exchange2003disk\SETUP\I386\EXCHANGE and the wizard completed without error.
I hope this helps save someone the time it took me to dig through old boxes of disks looking for sbs2003 disks that would work
This did the trick for me also. I was using Exch2003SP2 media when I received the "Setup failed while installing sub-component of Windows Active Directory schema update with error code 0xc1037986" error, but when I re-attempted the uninstall using
Exch2003 (w/o any Service Packs) the uninstall completed successfully and prompted for a reboot. The Microsoft Error Reporting service popped up with 3 error reports that were generated during the uninstall and requested permission to send the reports
(which I did not) and I just rebooted instead as instructed. After reboot, system displayed message that some services could not be started. Checked the services and found that "Microsoft Exchange Management" and Simple Mail Transfer Protocol (SMTP)"
services were still listed and set to Automatic. Changed startup to Manual on each, rebooted again w/o incident. So the removal of Exch2003 with original media works, but is not 100% clean (no surprise there) during the uninstall cleanup. This is the
1st of 2 old Exch 2003 servers I am retiring. I suspect the 2nd one will behave similarly when we're ready to shut-down that unit also. Thanks for the pointers. -
Unity 4.2 voice mail only with Exchange 2003
Hi Team,
we are replacing window 2000 OS with Win 2003 for unity 4.2. This is a single box solution. Exchange 2000 is installed on same unity server. Now we are upgrading the OS from 2000 to 2003. With window 2003 we have to installed the Exchange 2003. In unity installation 4.0(5) following paragraph is mentioned which means we need separate hardware for Exchange. Kindly advise whether we need a separate server for Exchange 2003 or we can install on the on unity box.
If you are using Exchange 2003, install Exchange 2003 administration software on the Cisco Unity server. (Exchange 2003 is installed on a separate server.)
If you are using Exchange 2000, you can install Exchange 2000 either on the Cisco Unity server or on a separate server. If you install Exchange 2000 on a separate server (typically for systems with a large number of subscribers), install Exchange 2000 administration software on the Cisco Unity server.
BR
Muhammad IrfanThank you Javalenc,
I can understand from following that Exchange 2003 can be installed on same server.
Voice Messaging
•Exchange 2003 on the Cisco Unity server or on a separate server. If you want to install Exchange 2003 on the Cisco Unity server, note the following:
–The Cisco Unity server must be running Windows Server 2003.
–Exchange 2003 can be installed only on the currently shipping servers supported for use with Cisco Unity 4.2 (MCS-78xx-x2, MCS-78xx-x3, or later, including IBM and HP equivalents). Currently shipping servers are listed in the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/
As you know we are just replacing the OS, from win 2K to 2k3. So any thing I need to take care to back up the existing Unity with win 2000 and exchange 2000..
I am taking the back up of my unity 4.2 installed on window 2000 with DiRT and will restore on unity 4.2 with win 2003 and Exchange 2003.
Kindly advise.
BR -
IOS 4 / Exchange 2003 No longer works
I just upgraded my iPhone 3G to iOS 4.0. We did not have any problems with connectivity with an Exchange 2003 mail server. Now my Inbox no longer works. My calendar and contacts work just fine. I make an update on my phone and it is pushed to Exchange. We are running Exchange 2003 and ISA Server 2004. I checked the firewall logs and everything is clean. My other external emails are just fine. Any ideas?
I had 3 users show up with iPhone 4s. 2 of the 3 synced fine against Exchange 2003. The third would attempt to sync but eventually time out and get a server connection failed error after adding the account. All three users were previously syncing fine with iPhone 3GS phones against the same Exchange 2003 setup.
Upon further inspection I noticed that the account was successfully connecting and retrieving the mailbox subfolders that the user had created and that the user was able to send mail from his phone. This led me to believe that there was nothing wrong with the account but rather the phone was having trouble enumerating all of the mail in the user's mailbox.
Turns out the user had around 40,744 items in his main inbox folder. Upon creating subfolders for 2004/2005/2006/2007/2008 and moving all older mail into these subfolders, the user was left with approximately 13,000 items in his main inbox from 2009-2010. Immediately after archiving the older mail, the phone began successfully syncing again.
Hope this helps -
We are not able to successfully complete a migration of all users from
Exchange 2003 to GroupWise 7 on Netware. Issues below:
** NOT Necessarily in exact order of sequence **
System config:
Netware OES fully service packed, new server, 4GB RAM, 4 Processors.
GroupWise 7.0.1 IR1 Post Office installed. Domain located on an older,
existing server.
Microsoft Windows Server 2003, Exchange 2003 single server. Nothing
special or unusual about this setup for Exchange, pretty generic.
1. Issue attempting to install Migration utility. Utility unable to run
after installation on any workstation. Various errors from "unable to
create GroupWise account" to "unable to login to Exchange mailbox" and a
few others. We also got "fatal errors when trying to extract .csv file".
This was resolved later by running fixmapi.
2. After nearly 18 hours attempting to get the utility to work, we were
able to successfully load it onto 2 workstations. It appeared that it
would work on both.
3. We tried many things to install and run the utility on 15 additional
workstations with no success.
4. Found that the only 2 workstations that appeared to run the utility
were fairly new, less than 2 months old. We then tried fresh installations
of WINXP and WIN2000 on 2 workstations with no success. One of the 2
workstations that did work, later no longer would run the utility. After
running fixmapi.exe on that workstation, it did again work.
5. A suggestion from Novell NTS was to run fixmapi.exe. This appeared to
have corrected 4 of the 10 workstations on which we tried it.
6. Found on 2 workstations that if ZEN DLU (Dynamic Local User) was used,
the migration utility did not work. We found this by logging in as
"Workstation Only" which connected the workstation to the domain, then a
login to eDirectory. The utility did work. So, again we tried to login on
startup to eDirectory and again were not able to run the utility. So, the
fact that some workstations here use DLU may be an issue for this utility.
7. Found that on other workstations, the utility would run ONLY if
"Workstation Only" was selected, then login to eDirectory. We were able to
repeat this sequence multiple times. This is on a workstation not running
ZEN DLU.
8. Of the 6 workstations we were able to run the utility, 1 failed in the
first 5 minutes and would no longer work. So, we split the .csv file from
the Exchange server into 5 parts and started the migration on the 5
available operating workstations. Of the 5, only 2 completed the utility.
Of those 2, only 7 of the 45 users to be migrated completed on 1
workstation and 15 of 45 completed on another.
9. On the 2 workstations that completed, all user accounts were created
but the utility was unable to access the GroupWise account. Login to
GroupWise account failed.
10. Migration utility rules creation issue. There are 2 issues here.
10a. The utility suggests to create a rule using a sub-domain and a
forward rule in Exchange to the new GroupWise system. We are migrating
from: royalmouldings.com to ggc.com. So, the sub-domain is
marexch.ggc.com. The rule would read "forward all mail to
[email protected]. However, Exchange cannot forward to an external
domain at the client level. The only means to do so is to create a contact
in AD with an SMTP email address of the domain to be forwarded to. Then,
in the users account a rule may be created to forward to that newly
created contact. The fact that we are forwarding to an external internet
domain, as in NOT the same one currently used in Exchange, is not
indicated in the documentation. Additionally, if anyone is to do this, a
lot of manual work must be done to accomplish this task. Not too practical
to do for hundreds or thousands of users. This has been a big problem as a
result of the large amount of users in the system and the time it takes to
create each of these contacts.
10b. The second issue is the fact that the rule was created for 1 user,
then no other users had the rule created. So, even if the rule were to
work or we were migrating from and to the same domain name, we'd still
have the rule issue as it was never again created by the utility after the
first user was migrated.
Any help would be greatly appreciated.
ThanksBill, you're understandably frustrated. I have a couple of comments.
1. The network authentication system used by Microsoft Exchange requires that you log in to your workstation with the same user ID and password as your account on Exchange. If they don't match, Exchange returns errors that are not always understandable. That might explain why Zen DLU has problems.
2. It seems that every application that deals with e-mail has its own version of MAPI, and they're not always compatible with each other. Outlook, GroupWise, and the migration utility all use MAPI. The fixmapi utility will restore the MAPI DLLs that Outlook expects, which is usually the version that works best.
3. The migration utility should be improved to detect potential errors like these.
>>> Bill Long<[email protected]> 5/19/07 11:59 AM >>>
We are not able to successfully complete a migration of all users from
Exchange 2003 to GroupWise 7 on Netware. Issues below:
** NOT Necessarily in exact order of sequence **
System config:
Netware OES fully service packed, new server, 4GB RAM, 4 Processors.
GroupWise 7.0.1 IR1 Post Office installed. Domain located on an older,
existing server.
Microsoft Windows Server 2003, Exchange 2003 single server. Nothing
special or unusual about this setup for Exchange, pretty generic.
1. Issue attempting to install Migration utility. Utility unable to run
after installation on any workstation. Various errors from "unable to
create GroupWise account" to "unable to login to Exchange mailbox" and a
few others. We also got "fatal errors when trying to extract .csv file".
This was resolved later by running fixmapi.
2. After nearly 18 hours attempting to get the utility to work, we were
able to successfully load it onto 2 workstations. It appeared that it
would work on both.
3. We tried many things to install and run the utility on 15 additional
workstations with no success.
4. Found that the only 2 workstations that appeared to run the utility
were fairly new, less than 2 months old. We then tried fresh installations
of WINXP and WIN2000 on 2 workstations with no success. One of the 2
workstations that did work, later no longer would run the utility. After
running fixmapi.exe on that workstation, it did again work.
5. A suggestion from Novell NTS was to run fixmapi.exe. This appeared to
have corrected 4 of the 10 workstations on which we tried it.
6. Found on 2 workstations that if ZEN DLU (Dynamic Local User) was used,
the migration utility did not work. We found this by logging in as
"Workstation Only" which connected the workstation to the domain, then a
login to eDirectory. The utility did work. So, again we tried to login on
startup to eDirectory and again were not able to run the utility. So, the
fact that some workstations here use DLU may be an issue for this utility.
7. Found that on other workstations, the utility would run ONLY if
"Workstation Only" was selected, then login to eDirectory. We were able to
repeat this sequence multiple times. This is on a workstation not running
ZEN DLU.
8. Of the 6 workstations we were able to run the utility, 1 failed in the
first 5 minutes and would no longer work. So, we split the .csv file from
the Exchange server into 5 parts and started the migration on the 5
available operating workstations. Of the 5, only 2 completed the utility.
Of those 2, only 7 of the 45 users to be migrated completed on 1
workstation and 15 of 45 completed on another.
9. On the 2 workstations that completed, all user accounts were created
but the utility was unable to access the GroupWise account. Login to
GroupWise account failed.
10. Migration utility rules creation issue. There are 2 issues here.
10a. The utility suggests to create a rule using a sub-domain and a
forward rule in Exchange to the new GroupWise system. We are migrating
from: royalmouldings.com to ggc.com. So, the sub-domain is
marexch.ggc.com. The rule would read "forward all mail to
[email protected]. However, Exchange cannot forward to an external
domain at the client level. The only means to do so is to create a contact
in AD with an SMTP email address of the domain to be forwarded to. Then,
in the users account a rule may be created to forward to that newly
created contact. The fact that we are forwarding to an external internet
domain, as in NOT the same one currently used in Exchange, is not
indicated in the documentation. Additionally, if anyone is to do this, a
lot of manual work must be done to accomplish this task. Not too practical
to do for hundreds or thousands of users. This has been a big problem as a
result of the large amount of users in the system and the time it takes to
create each of these contacts.
10b. The second issue is the fact that the rule was created for 1 user,
then no other users had the rule created. So, even if the rule were to
work or we were migrating from and to the same domain name, we'd still
have the rule issue as it was never again created by the utility after the
first user was migrated.
Any help would be greatly appreciated.
Thanks -
Oracle Application Server Provider for Microsoft Exchange 2003 Error
Hi, i´m trying to install Exchange portlet in my portal. I passed each step of this manual (http://www.oracle.com/technology/products/ias/portal/point/exchange2003/installation.html), but I get an error in the following step:
6. Test the ASP page access to the sample Exchange 2003 mailbox
When I try to access the .asp through the internet explorer I get this error:
Tipo de error:
Objeto Server, ASP 0177 (0x800401F3)
Cadena clase no válida
/exchange/test.asp, línea 13
The asp code is:
<%
Option Explicit
Dim objLogon
Dim objSession
Dim sUser
Dim sDomain
Dim sPassword
Dim sMailBox
Dim sExchangeServer
Dim lngToken
Dim msgCount
'RETRIEVE EXCHANGE CREDENTIALS FROM REQUEST
sMailBox = Request.QueryString("MBox")
sExchangeServer = Request.QueryString("ExServer")
sUser = Request.QueryString("UName")
sDomain = Request.QueryString("UDomain")
sPassword = Request.QueryString("UPwd")
If Len(Trim(sPassword)) = 0 Or Len(Trim(sMailBox)) = 0 Or _
Len(Trim(sExchangeServer)) = 0 Or Len(Trim(sUser)) = 0 Or _
Len(Trim(sDomain)) = 0 Then
Response.write "ERROR"
Else
Set objLogon = Server.CreateObject("LoginAdmin.ImpersonateUser")
lngToken = objLogon.ImpersonateToken(sUser, sPassword, sDomain)
If lngToken = 0 Then
Response.write "ERROR"
Else
Set objSession = server.CreateObject("MAPI.Session")
objSession.Logon ,,,,,,sExchangeServer & vblf & sMailBox
msgCount = objSession.Inbox.Messages.Count
'SUCCESSFUL AUTHENTICATION
Response.write "VALID"
objSession.Logoff
Set objSession = Nothing
End If
objLogon.Logoff
Set objLogon = Nothing
End If
%>
Thanks for your help,
Regards.Hello Chino,
Have a look here
Collaboration Portlets: calendar, task, email, contact
Thanks
Neeraj Sidhaye -
Exchange 2003 giving occasional NDR's
We have an Exchange 2003 Server awaiting a migration to 2013.
Before we can migrate we need to find out the reason for some occasional mail, sending NDR's to a sender of email. The mail that generates an NDR, will 'leak through' to the recipients with no listed names in the To and no subject.
The funny thing is, in the Exchange tracking log, I can see the mail inbound, accepted and delivery started, but then you see the NDR being send out.
On the protocol logs on the Exchange server I am not seeing any issues.
On the protocol logs on the Edge Server again, I am not seeing any issues.
Not too sure where to go to next, or what to log next to find the issue.
Logs, email headers etc following.
Email header from mail that leaked through and NDR created.
Microsoft Mail Internet Headers Version 2.0
Received: from edge1.ReceiverDomain.com ([ReceiverDomainIP]) by mail.ReceiverDomain.com with Microsoft SMTPSVC(6.0.3790.1830);
Received: from edge1.ReceiverDomain.com ([ReceiverDomainIP]) by mail.ReceiverDomain.com with Microsoft SMTPSVC(6.0.3790.1830);
Tue, 1 Oct 2013 15:59:26 +0100
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-WatchGuard-AntiVirus: part scanned. clean action=allow
From: [email protected]
Bcc:
Return-Path: [email protected]
Message-ID: <[email protected]>
X-OriginalArrivalTime: 01 Oct 2013 14:59:26.0825 (UTC) FILETIME=[D2ADBD90:01CEBEB6]
Date: 1 Oct 2013 15:59:26 +0100
Email header from accepted email
Microsoft Mail Internet Headers Version 2.0
Received: from edge1.ReceiverDomain.com ([ReceiverDomainIP]) by mail.ReceiverDomain.com with Microsoft SMTPSVC(6.0.3790.1830);
Tue, 1 Oct 2013 16:01:04 +0100
Received: from SENDERINTMAIL.prod.ds.SenderDomain.com (SenderDomainIP) by
edge1.ReceiverDomain.com (ReceiverDomainIP) with Microsoft SMTP Server (TLS) id
8.1.436.0; Tue, 1 Oct 2013 16:00:58 +0100
Received: from SENDERINT2.prod.ds.SenderDomain.com ([169.254.1.152]) by
SENDERINTMAIL.prod.ds.SenderDomain.com ([169.254.2.131]) with mapi id
14.02.0298.004; Tue, 1 Oct 2013 16:01:00 +0100
From: "Sender, of Email" <[email protected]>
To: "Sender, of Email" <[email protected]>, Receiver1
<[email protected]>, "Receiver2" <[email protected]>
CC: SenderDomainFactsheets <[email protected]>, Receiver3
<[email protected]>, Receiver4<[email protected]>
Subject: RE: Subject line
Thread-Topic: Subject line
Thread-Index: Ac6+lzKxFtHC6ZksQlSoTTK2f8AezQAD2bEQAAFJwVAAARDjsAABYWnAAABGLHAAABXhwA==
Date: Tue, 1 Oct 2013 15:00:59 +0000
Message-ID: <[email protected]rDomain.com>
References: <[email protected]al>
<[email protected]rDomain.com>
<[email protected]al>
<[email protected]rDomain.com>
<[email protected]al>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [SenderIntIP2]
Content-Type: multipart/alternative;
boundary="_000_4C2FB0C9647B0140A70CEEA1B0F99FCA091F15B1LONEXH002PAprod_"
MIME-Version: 1.0
Return-Path: [email protected]
Received-SPF: Pass (edge1.ReceiverDomain.com: domain of [email protected]
designates SenderDomainIP as permitted sender)
receiver=edge1.ReceiverDomain.com; client-ip=SenderDomainIP;
helo=SENDERINTMAIL.prod.ds.SenderDomain.com;
X-WatchGuard-Spam-ID: str=0001.0A0B0204.524AE3AE.00B3,ss=1,re=0.000,fgs=0
X-WatchGuard-Spam-Score: 0, clean; 0, no virus
X-WatchGuard-Mail-Client-IP: 169.254.1.152
X-WatchGuard-Mail-From: [email protected]
X-WatchGuard-Mail-Recipients: [email protected];[email protected];[email protected];[email protected]
X-OriginalArrivalTime: 01 Oct 2013 15:01:04.0215 (UTC) FILETIME=[0CBA4670:01CEBEB7]
--_000_4C2FB0C9647B0140A70CEEA1B0F99FCA091F15B1LONEXH002PAprod_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-WatchGuard-AntiVirus: part scanned. clean action=allow
--_000_4C2FB0C9647B0140A70CEEA1B0F99FCA091F15B1LONEXH002PAprod_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-WatchGuard-AntiVirus: part scanned. clean action=allow
--_000_4C2FB0C9647B0140A70CEEA1B0F99FCA091F15B1LONEXH002PAprod_--
Exchange 2003 Tracking log
Logs from Edge Server for the emails, both the received email that generated the NDR and the email that was resent and received in full
Timestamp : 01/10/2013 15:46:49
ClientIp : SenderDomainIP
ClientHostname :
ServerIp : ReceiverDomainIP
ServerHostname : edge1
SourceContext : 08D0891A81DE4619;2013-10-01T14:46:48.159Z;0
ConnectorId : edge1\Default internal receive connector EDGE1
Source : SMTP
EventId : RECEIVE
InternalMessageId : 1348948
MessageId : <[email protected]nderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {}
TotalBytes : 48832
RecipientCount : 4
RelatedRecipientAddress :
Reference :
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 00A:
Timestamp : 01/10/2013 15:46:49
ClientIp : ReceiverDomainIP
ClientHostname : edge1
ServerIp : 10.0.0.164
ServerHostname :
SourceContext : 08D0891A81DE461A
ConnectorId : sendToExchange2003
Source : SMTP
EventId : SEND
InternalMessageId : 1348948
MessageId : <[email protected]SenderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {250 2.1.5 [email protected] , 250 2.1.5 [email protected] , 250 2.1.5 [email protected] , 250 2.1.5 [email protected] }
TotalBytes : 48832
RecipientCount : 4
RelatedRecipientAddress :
Reference : {, , , }
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 01/10/2013 15:46:48
Timestamp : 01/10/2013 15:59:23
ClientIp : SenderDomainIP
ClientHostname :
ServerIp : ReceiverDomainIP
ServerHostname : edge1
SourceContext : 08D0891A81DE4680;2013-10-01T14:59:21.660Z;0
ConnectorId : edge1\Default internal receive connector EDGE1
Source : SMTP
EventId : RECEIVE
InternalMessageId : 1348977
MessageId : <4C2FB0C9647B0140A70CEEA1B0F99FCA091F1592@LON-EXH002P
A.prod.ds.SenderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {}
TotalBytes : 61503
RecipientCount : 4
RelatedRecipientAddress :
Reference :
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 00A:
Timestamp : 01/10/2013 15:59:23
ClientIp : ReceiverDomainIP
ClientHostname : edge1
ServerIp : 10.0.0.164
ServerHostname :
SourceContext : 08D0891A81DE4681
ConnectorId : sendToExchange2003
Source : SMTP
EventId : FAIL
InternalMessageId : 1348977
MessageId : <4C2FB0C9647B0140A70CEEA1B0F99FCA091F1592@LON-EXH002P
A.prod.ds.SenderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {503 5.5.2 Need mail command., 503 5.5.2 Need mail command., 503 5.5.2 Need mail command., 503 5.5.2 Need mail command.}
TotalBytes : 61503
RecipientCount : 4
RelatedRecipientAddress :
Reference : {<cdba64fe-f673-439a-afda-136c285acdf4>, <cdba64fe-f6 73-439a-afda-136c285acdf4>, <cdba64fe-f673-439a-afda- 136c285acdf4>, <cdba64fe-f673-439a-afda-136c285acdf4>}
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo :
Timestamp : 01/10/2013 16:00:59
ClientIp : SenderDomainIP
ClientHostname :
ServerIp : ReceiverDomainIP
ServerHostname : edge1
SourceContext : 08D0891A81DE4695;2013-10-01T15:00:57.647Z;0
ConnectorId : edge1\Default internal receive connector EDGE1
Source : SMTP
EventId : RECEIVE
InternalMessageId : 1348985
MessageId : <[email protected]enderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {}
TotalBytes : 62815
RecipientCount : 4
RelatedRecipientAddress :
Reference :
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 00A:
Timestamp : 01/10/2013 16:01:01
ClientIp : ReceiverDomainIP
ClientHostname : edge1
ServerIp : 10.0.0.164
ServerHostname :
SourceContext : 08D0891A81DE4697
ConnectorId : sendToExchange2003
Source : SMTP
EventId : SEND
InternalMessageId : 1348985
MessageId : <[email protected]enderDomain.com>
Recipients : {[email protected], [email protected], eg
[email protected], SenderDomainFactsheets@FundAss
ist.com}
RecipientStatus : {250 2.1.5 [email protected] , 250 2.1.5 [email protected] , 250 2.1.5 receiver1@receiverdomain, 250 2.1.5 [email protected] }
TotalBytes : 62815
RecipientCount : 4
RelatedRecipientAddress :
Reference : {, , , }
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 01/10/2013 16:00:58
JoeEdge server 2007 to Exchange 2003
2013-11-27T10:00:53.932Z,sendToExchange2003,08D0AFC938C280EE,14,10.11.0.164:56317,10.0.0.164:25,>,MAIL FROM:<[email protected]> SIZE=62314 AUTH=<>,
2013-11-27T10:00:53.948Z,sendToExchange2003,08D0AFC938C280EE,15,10.11.0.164:56317,10.0.0.164:25,<,250 2.1.0 [email protected]...Sender OK,
2013-11-27T10:00:53.948Z,sendToExchange2003,08D0AFC938C280EE,16,10.11.0.164:56317,10.0.0.164:25,>,RCPT TO:<[email protected]>,
2013-11-27T10:00:53.948Z,sendToExchange2003,08D0AFC938C280EE,17,10.11.0.164:56317,10.0.0.164:25,<,250 2.1.5 [email protected] ,
2013-11-27T10:00:53.948Z,sendToExchange2003,08D0AFC938C280EE,18,10.11.0.164:56317,10.0.0.164:25,>,BDAT 61973 LAST,
2013-11-27T10:00:54.197Z,sendToExchange2003,08D0AFC938C280EE,19,10.11.0.164:56317,10.0.0.164:25,<,503 5.5.2 Need mail command.,
2013-11-27T10:00:54.213Z,sendToExchange2003,08D0AFC938C280EE,20,10.11.0.164:56317,10.0.0.164:25,>,QUIT,
2013-11-27T10:00:54.213Z,sendToExchange2003,08D0AFC938C280EE,21,10.11.0.164:56317,10.0.0.164:25,<,221 2.0.0 mail.Receiver.com Service closing transmission channel,
Exchange 2003 Protocol log
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 EHLO +edge1.Receiver.com 250 0 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 MAIL +FROM:<[email protected]> 250 0 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 RCPT +TO:<[email protected]> 250 0 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 BDAT <[email protected]> 250 62 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 BDAT +22244 503 0 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 QUIT edge1.Receiver.com 240 0 SMTP
Joe -
Installation of Exchange 2010 in Windows 2012 Server
Hi all,
We are planning to upgrade our current Exchange 2003 to Exchange 2010, Need some help on installation and Support of Exchange 2010 in Windows 2012 Server, as per the
https://technet.microsoft.com/library/ff728623(v=exchg.150).aspx Exchange 2010 with sp3 is supported in Windows 2012 but I am unable to find the installer of Ex 2010 with sp3
in web even in MSDN. There is only Ex 2010 with Sp1 available. I know that after installing ex2010 with sp1 version, I can install sp3 later but I found one link
http://www.petenetlive.com/KB/Article/0000785.htm where it is mentioned that insllation can be done only after doing the registry settings.
So is any one who has installed Ex 2010 in Windows 2012 Server and faced this issue and any solution.
Thanks
Mukesh
Mukesh BishtYou can easily install Exchange 2010 (SP3) on Windows Server 2012. If you are working with previous SP version’s you can easily upgrade after installing server. And registry settings
are used to fix an error which may occur during migration, so it is not mandatory to correct registry settings each time during migration.
You can find detailed information about installing Exchange 2010 (SP3) on Windows Server 2012 at this blog :http://oxfordsbsguy.com/2013/03/24/how-to-install-exchange-2010-sp3-on-windows-server-2012/ -
Exchange 2003 to 2010 Migration
Hello,
I seem to have ran into issues with Default GAL, default address lists, email address policies, OAB, etc.
Background: Exchange 2003, with one FE and one BE server with multiple domains for mail access. We decided to migrate to 2010 and have one hyper-v server with 3 VMS running AD, CAS/HT and MBX roles respectively. All the AD preparations and installation (exchange
2010 Sp2) of CAS/HT role was smooth. When I installed the MBX role it was successful but could not see Public Folder Database and was unable to create one because of AddressList errors and had to be upgraded to 2010. Since there were multiple domains, LDAP
filter were used and those had to be updated with OPATH filters and I used the "ConvertFrom-LdapFilter.ps1" script to convert and upgrade to 2010. I could do this for all the custom address lists but it did not run for "All Users", "All
Groups" "All Contacts" as it says ADObject cannot be found on exchange2003 server.
I created a test mailbox on the new server and could login using OWA but cannot see GAL or search for addresses. I could send and receive email from 2010 to both 2003 mailbox & external domain with no issues. I did configure the CAS role with legacy
URL (existing OWA URL https://myweb.domain.net/exchange) for exchange2003 and a new URL (https://mymail.domain.net/owa) for exchange 2010 and also enabled Outlook Anywhere, MS Active Sync, etc. But I cannot setup outlook using autodiscover or even manually
by providing the info. I have to start migrating users and this has become a big show stopper and would appreciate if anyone could help/guide me through this to troubleshoot/fix the issues and move the mailboxes ASAP.
Some errors:
[PS] C:\>Set-AddressList "All Users" -IncludedRecipients MailboxUsers
The operation couldn't be performed because object 'All Users' couldn't be found on 'exchange2003.domain.com'.
+ CategoryInfo : NotSpecified: (0:Int32) [Set-AddressList], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : 779DEB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.SetAddressList
+ PSComputerName : cas01.domain.com
[PS] C:\>Set-AddressList "All Groups" -IncludedRecipients MailboxUsers
The operation couldn't be performed because object 'All Groups' couldn't be found on 'exchange2003.domain.com'.
+ CategoryInfo : NotSpecified: (0:Int32) [Set-AddressList], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : 45369D2F,Microsoft.Exchange.Management.SystemConfigurationTasks.SetAddressList
+ PSComputerName : cas01.itqubate.com
[PS] C:\>Set-AddressList "All Contacts" -IncludedRecipients MailboxUsers
The operation couldn't be performed because object 'All Contacts' couldn't be found on 'exchange2003.domain.com'.
+ CategoryInfo : NotSpecified: (0:Int32) [Set-AddressList], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : 4D78E094,Microsoft.Exchange.Management.SystemConfigurationTasks.SetAddressList
+ PSComputerName : cas01.domain.com
[PS] C:\>Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'u
ser' -or ObjectClass -eq 'contact' -or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass -eq 'msExchDynamicDistribut
ionList' -or ObjectClass -eq 'group' -or ObjectClass -eq 'publicFolder'))}
You can't peform this operation on default global address list "Default Global Address List".
+ CategoryInfo : InvalidOperation: (\Default Global Address List:ADObjectId) [Set-GlobalAddressList], Inv
alidOperationException
+ FullyQualifiedErrorId : 7815D31B,Microsoft.Exchange.Management.SystemConfigurationTasks.SetGlobalAddressList
+ PSComputerName : cas01.domain.com
[PS] C:\>Get-AddressList "Default Global Address List" | Format-List Name,*RecipientFilter*,ExchangeVersion
The operation couldn't be performed because object 'Default Global Address List' couldn't be found on
'exchange2003.domain.com'.
+ CategoryInfo : NotSpecified: (:) [Get-AddressList], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : D96C5897,Microsoft.Exchange.Management.SystemConfigurationTasks.GetAddressList
+ PSComputerName : cas01.domain.com
Thanks,
SyedSFHi SyedSF,
From your problem description, it seems that you have a permission problem here. Maybe you have had Address List Segregation configured in Exchange 2003 and that is not supported in Exchange 2010.
I recommend you to use ADSIEdit to check the permissions on "All Address Lists", "All Global Address Lists" and "Offline Address Lists". Include inherited permissions should be checked and "Authenticated Users" should have the permissions read and "Open
address list".
What's more, here are some similar threads for your reference.
Exchange 2010 Migration - No Default GAL (or any lists)
http://social.technet.microsoft.com/Forums/exchange/en-US/f1b7aafa-2774-4959-94b2-4f2fbdd9fe4d/exchange-2010-migration-no-default-gal-or-any-lists
Problem with Get-addresslist when transitioning exchange 2003 to exchange 2010
http://social.technet.microsoft.com/Forums/exchange/en-US/53150d23-45cf-4708-a920-577c40998ad9/problem-with-getaddresslist-when-transitioning-exchange-2003-to-exchange-2010
Hope it helps.
Best regards,
Amy -
SPAM rules on Inbox after migration from Exchange 2003 - GFI Mail Essentials
Hello,
Few times ago, we had an Exchange 2003 server with mailboxes which were configured with "rulemgmt.exe" tool (from Microsoft ?) to manage users mailboxes and SPAM redirection in these mailboxes.
GFI MailEssentials (antispam) was installed on a mail relay and once a SPAM was detected, it was redirected in Inbox/SPAM folder on user mailbox thanks to the rule defined by "rulemgmt.exe".
Recently, we did a migration from Exchange 2003 to 2010. Unfortunately, "rulemgmt.exe" doesn't work anymore on Exchange 2010 and it's replaced by a "Transport Rule" which works fine but only to redirect SPAMs in Junk e-mail folder. However,
if I don't set up this transport rule, SPAM redirection still works from mailboxes which were created on Exchange 2003 and e-mails go to Inbox/SPAM as before... For new mailboxes on Exchange 2010, it doesn't work which is normal.
My question is: for old mailboxes from Exchange 2003, where are the SPAM redirection (Inbox/SPAM) information stored? I don't understand how SPAM can be redirected if the information is not stored in Exchange...
The aim is to use Junk E-mail folder with the Transport Rule at the end everywhere and to clean old rules used for Inbox/SPAM.
I contact GFI support but they couldn't help me.
Any idea?
Regards,
DeltaSM
Those old mailboxes probably have old rules still set. You can use the Outlook.exe /cleanrules switch to purge those old rules. This would require that you create an outlook profile for each of those impacted mailboxes.
You can also look at using MFCMapi -
http://support.microsoft.com/kb/2860406/en-us
When that is done, you might want to perform a Clean-MailboxDatabase and then look at the mailbox rules (get-inboxrule). If that does not work for you, could be something else within the mailbox and as such, I would recommend working with MS to get
more info.
DaDougInc -
Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC
I wasn't prepared for this task, and it was thrown at me to do... Eyes are bleeding from planning reading and planning, would LOVE any input from you guys. First time posting, here and have heard great things about these forums. The Company
I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
Scenario:
Old Domain/Server: (To be decommissioned)
Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
Exchange 2003 SP2 (6.5.7638.1)
Server is a domain controller and exchange server.
Migrating to:
Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality
VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
These are probably not ideal conditions, but I have to work with what I'm given.
Host server (2012 R2) is in work group mode. Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2. I had intended starting at a lower functionality level and raising
it later, but.... ya I forgot to change it. If needed I can spool up a new DC with a lower functional level.
DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain. The concern is migrating the mailboxes from Exchange 2003 on the old domain to
Exchange 2013 on the new domain. The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
I had some ideas, but I'm not sure if they will work. This is something I have never done before (Senior Engineer Quit).
My thoughts:
- Establish a two way trust relationship between the two domains.
- Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
- Create the users on the new domain
- Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013
- Link Exchange accounts to the correct user accounts on the new DC.
Can this be done cleanly? Am I going about this the correct way? Any feedback would be GREATLY appreciated.
Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)Hi,
Base on my experience, your idea is feasible.
However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link:
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
Best regards,
Niko Cheng
TechNet Community Support -
Dear all,
I know there are quite some threads regarding this issue. But I've been looking at all of them w/o any solution for my problem. Here we go...
I've followed all instructions for a Exchange 2003 to 2010 transition. All went fine to the point I'm trying to uninstall Exchange 2003 via Control Panel/Software/Remove. So far I did the following:
1. Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Powershell => successfully
2. Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010 => successfully
3. Rehome Public Folder Hierarchy on new Exchange Server 2010 Admin Group => successfully
4. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store => successfully
5. Delete Public and Private Information Stores from Exchange 2003 server => successfully
6. Delete Routing Group Connectors to Exchange Server 2003 => successfully
7. Delete Recipient Update Service agreements using ADSIEdit according to
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx => successfully
8. Uninstall all Exchange 2003 servers => fails with "Error code 0X80072030 (8240): There is no such object on the server"
I used the following articles while migrating to Exchange 2010:
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx
http://support.microsoft.com/kb/833396/en-us
http://www.simple-talk.com/content/article.aspx?article=882
and several more.
I looked into these forums regarding my problem and came up with:
http://support.microsoft.com/kb/283089/en-us
http://support.microsoft.com/kb/822931
I investigated the following possible reasons:
- homeMDB attribute (no references to my Exchange 2003 anymore)
- HomeMDBBL attribute (as described here
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/f0e3edd7-34e5-46b8-8061-1991aaffc30f) (no Information Stores available anymore as they have been successfully removed)
- msExchHomeServerName attribute (all pointing to my new Exchange 2010 server)
- the "famous" postmaster issue as described here:
http://support.microsoft.com/kb/283089/en-us (pointing to the new Exchange 2010 server)
In order to investigate all attribute related issues a utilized a VBS script resulting in an Excel sheet I was easily able to filter:
SET objRootDSE = GETOBJECT("LDAP://RootDSE")
strExportFile = "C:\temp\MyExport.xls"
strRoot = objRootDSE.GET("DefaultNamingContext")
strfilter = "(&(objectCategory=Person)(objectClass=User))"
strAttributes = "sAMAccountName,msExchHomeServerName,homeMDB,legacyExchangeDN,givenName,sn," & _
"initials,displayName,physicalDeliveryOfficeName," & _
"telephoneNumber,mail,wWWHomePage,profilePath," & _
"scriptPath,homeDirectory,homeDrive,title,department," & _
"company,manager,homePhone,pager,mobile," & _
"facsimileTelephoneNumber,ipphone,info," & _
"streetAddress,postOfficeBox,l,st,postalCode,c"
strScope = "subtree"
SET cn = CREATEOBJECT("ADODB.Connection")
SET cmd = CREATEOBJECT("ADODB.Command")
cn.Provider = "ADsDSOObject"
cn.Open "Active Directory Provider"
cmd.ActiveConnection = cn
cmd.Properties("Page Size") = 1000
cmd.commandtext = "<LDAP://" & strRoot & ">;" & strFilter & ";" & _
strAttributes & ";" & strScope
SET rs = cmd.EXECUTE
SET objExcel = CREATEOBJECT("Excel.Application")
SET objWB = objExcel.Workbooks.Add
SET objSheet = objWB.Worksheets(1)
FOR i = 0 To rs.Fields.Count - 1
objSheet.Cells(1, i + 1).Value = rs.Fields(i).Name
objSheet.Cells(1, i + 1).Font.Bold = TRUE
NEXT
objSheet.Range("A2").CopyFromRecordset(rs)
objWB.SaveAs(strExportFile)
rs.close
cn.close
SET objSheet = NOTHING
SET objWB = NOTHING
objExcel.Quit()
SET objExcel = NOTHING
Wscript.echo "Script Finished..Please See " & strExportFile
What I did find is that all my Exchange enabled users have an legacyExchangeDN attribute that is still pointing to my Exchange 2003 organization:
e.g. "/o=First Organisation/ou=First Administrative Group/cn=Recipients/cn=Administrator"
Could this cause any problems?
Now the in depth look into my "Exchange Server Setup Progress.log":
[09:33:06] Leaving ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[09:33:06] ScPRQ_ServerIsNotRUSResponsibleServerInTheNonEmptyOrg (f:\titanium\admin\src\udog\excommon\prereq.cxx:3133)
Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] CCompServer::ScCheckEVSPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:1358)
Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] CCompServer::ScCheckPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:955)
Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] === IGNORING PREVIOUS ERRORS === HrSetProblemOnInstallAction, while calling ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1399)
Der Vorgang wurde erfolgreich beendet.
[09:33:06] Ein Fehler ist beim Überprüfen der Voraussetzungen für die Komponente "Microsoft Exchange" durch Setup aufgetreten:
0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:14] CComBOIFacesFactory::QueryInterface (f:\titanium\admin\src\udog\bo\bofactory.cxx:54)
I did search for:
- Error code 0X80072030 (8240)
- ScPRQ_ServerIsNotRUSResponsibleServerInTheNonEmptyOrg
Nothing so far. In case some more information is needed just let me know.
Any help would be greatly appreciated as I absolutely don't know how to remove my Exchange 2003. Manual removal is not an option.
AlexI kept on searching and found something else:
http://www.outlookforums.com/threads/33038-cannot-uninstall-Exchange-2000
It says that the following groups need to be resided in the AD's default "Users" organizational unit:
- Exchange Domain Servers
- Exchange Enterprise Servers
- Exchange Services Group
Unfortunately I cannot find the "Exchange Services Group". Does that have something to do with my problem?
Furthermore I found out that the Exchange 2003 has been originally installed with SBS 2003 back in time. The SBS 2003 has then be migrated to a regular Windows Server 2003 infrastructure with 2 DCs. But there still is a load of stuff reminiscent of SBS
2003 within the AD.
Then I dug deeper into my AD using ADSIEdit. I found another attribute homeMTA that is pointing to a corresponding Exchange server. After adjusting my aforementioned VBS script a was able to look into that attribute as well. I found 2 users pointing to my old
Exchange server within their homeMTA attribute.
Furthermore I saw that when trying to uninstall Exchange 2003 there is no path to my installation anymore. It's empty:
Another issue?
Regards
Alex -
Configure new exchange 2010 while old exchange 2003 running ?
Hello,
I'm in the process of deploying a new fresh installation of SBS 2011/Exchange 2010 server. Currently
I have SBS2003/Exchange 2003 running. I want to retired the server and replace with the new server. No migration. By doing that, I am setting up the new server SBS2011 name/domain/ip everything the same as the old server and will replace once all the configuration
is completed.
1. Since they both using the same domainname/ip, can I setup the new server Exchange 2011 while the old
server is alive? If yes, how's the process?
2. If I export and import users email in .pst (on user outlook client) and when the new server is put in place alive does it will regenerate the database
in new Exchange 2011?
Thanks in advance =)For the 1st question, both servers are in different/isolated network. So you were saying yes i can do that correct? will not going to have any issue running both servers having all the same configuration while configuring the new server up?
the 2nd. since i am not migrating, i am planing to export/import user email from outlook client and when i replace the old server with the new server, i setup the user email client and import the .pst back. -
Outlook 2013 not compatible with Exchange 2003
Hello
Some of my customers bought SBS 2003 R2 just before SBS 2008 was released so they have systems which are only 4+ years old. SBS 2003 came with Exchange 2003 pre-installed. Outlook 2013 does not support Exchange 2003. So they cannot upgrade their Outlook
clients to 2013 version.
Microsoft, is this correct?!If this post is hard to read, it's because of Dragonsoft!! (sometimes it is like auto-correct on the phone - "I said WHAT!??")
Overall I think this is the most interesting thread that I have ever read on Microsoft.com.
As a computer for professional for over 30 years, I've always followed the context that software products are designed for a three to five-year term, to have more is a luxury.
When I was first in the industry (1983), Microsoft had a tendency to change the software versions every year to two years. As we approached the era of Windows XP there was an expected lifetime use of three years. Every two years a new product would appear.
So, when windows XP lasted well beyond the three-year term, it was pretty exciting to not have to spend money on new product, and we all enjoyed the decade of Windows XP.
The new generation of IT professionals has somehow believe that software products should live more than five years, and it just blows my mind!
The reason that I make this post, is because I've used SBS ever since Back Office Server 4.5, and the versions of small business server (now called Small Business Server) have always appeared on the market 1 to 3 years after the primary versions of
Windows for which they are named. So I always felt that there was a disadvantage to using small business server in that the products appearing inside of SBS had been on the market for a few years before being incorporated into the SBS package. It
made me feel, at first, that Microsoft was waiting on the level of maturity within the product before creating the SBS package. Now that I look back on the whole process it made me think that the SBS team had some difficulty merging the products into a install
package which could handle the intricacies of the licensing limitations on the SBS system.
SBS 2003 was a great tool when it came out, but I found that it was riddled with security holes. To say the least some of my first SBS 2003 servers had their exchange system hacked by outside influences. (These were external facing servers who had websites
and exchange server running with public domain names, even though there were firewalls!) After a few patches, DNS modifications, reverse DNS entries, and some changes in the exchange system, I was finally able to make the system secure and solid.
My first real nightmare with SBS was when upgrading to SBS 2003 R2, which, yes, appeared around 2005. You cannot simply upgrade a machine from SBS to a new version. You must purchase a new server, install the new SBS version, and migrate your
entire installation to this new host. (While running SBS 2003 for several years and making backups on a tape, I realized that the new hardware on the market would not support a restore from my tape backup!) The whole process is rather daunting as not
all of the detailed steps to upgrade work as expected. I had to call, and pay, Microsoft to complete the process because exchange had trouble during the migration.
So off we went with our new installation of SBS 2003 R2. Then along came SBS 2008! I went through the same steps again... new hardware, new software, and, yes, paid Microsoft, again, for support to migrate.
When SBS 2011 appeared on the scene I was willing to upgrade again. Having gone through this, twice now, I fully prepared the client to purchase a new system and to purchase the new software. But because I was faced with the whole entire
nightmare of new hardware, migration, and having to call Microsoft to complete the process, I decided on a new approach. This time we were going to buy server which would run VMware. (I was not going to get stuck in a hardware box that I could not replace
if I ever needed to restore the operating system due to a massive failure.) So off I went, purchasing a new box, installing VMware, and installing my favorite operating system, Microsoft SBS!
Well, to say the least, it wasn't exactly as exciting as I had expected. Had some trouble getting VMware to settle into the new hardware, as there seemed to be some compatibility issues, but was able to work it out. Eventually, I was able to get started
on the migration. Things went well up until the point that I got to the exchange migration, and ran into a similar problem as before! A call to Microsoft revealed that it was even a little daunting for the support personnel, but as I documented the things
that they modified, and even performed a little cleanup, after they performed their cleanup! I can happily say that I'm no longer worried about hardware issues, when it comes to restoring my SBS server in case of a failure!
Overall I'm pleased with having used Microsoft SBS solutions over the past 10 years, but I would never expect, nor would I lead my customer to expect, that a product should last 10 years!
Previous comments have indicated that server should last seven years because they can be depreciated that way, I believe that to be entirely false! I live in Texas, and the state of Texas DIR program has adopted standards which state that
you should replace your hardware every five years! State agencies have this as a requirement, and it is not optional! Many state agencies have gone to leasing their equipment, which is a three-year term. (Where do you think off-lease equipment comes
from, anyway?)
One of my primary clients looked at me one day, and directly ask, "Okay, if we spend the $10,000 on the new server and software, how long should it last?"
Obviously, I wanted to say, "Forever!" But, remembering something that my mother had said (always plan for the worst and you always come out on top!), I said back to them, "I believe we should plan for a three-year lifespan, and if we get
any more than that, it will be a luxury." Needless to say, there have been some upgrades which lasted well more than three years, but there have been some which have been spot on.
The SBS server is a huge savings over purchasing the individual products separately. But there have always been some drawbacks during the upgrade process which makes the entire feasibility of the installation top-heavy when it comes to support costs.
I have noticed is that the SBS servers require more labor to keep them running smooth, especially with backup procedures and backup software, as SBS always requires a third-party product to make a "real" (restorable) backup.
A client's expectations should be that you are taking care of their business without them having to worry about what takes place in the tech room. They understand, and realize, that they can pay you a specific amount of money for your support without necessarily
having to purchase new hardware. But a good, healthy relationship with your client means that they should always be willing to upgrade, whether it is a workstation or server.
If you allow a client to be painted in a corner, then it's not their fault, it's your fault! Because, they have no idea what the new technology can do, and don't realize what's on the market. It's your job to keep up with what's current and to deliver
expectations which make them realize that each year has a dollar value attached to it, whether it is spent, or not.
If you have a client is unwilling to spend money to upgrade their equipment, then there's something else wrong with their business, and you should probably consider that they may not be in business for very long. So don't make it your problem when
they are unwilling to spend money. You don't work for free.
One last, quick example of the conversation that I had with a client who was unwilling to upgrade because things seem to be working so well. I put it like this, "You pay me to make certain that your business operates in good times and in
bad. Right now, everything is fine. If your building were to burn, and the only thing we had were the backups, I cannot go out and purchase new hardware and restore your system successfully. The equipment that we have operating here is no longer
available on the market. If I were to find the equipment, it would be out-of-date, and most likely, used, and I cannot guarantee its compatibility or functionality. So, if I can't restore your system to an operational status, then what would you do?
I don't believe there are any number of man-hours you can use to recover the information lost. You would probably have to go out of business! If your business becomes my business, then I would try to move to a position where my data is safe and my business
can continue in the case of catastrophe. The only way I can do this, is to purchase new hardware, new software, and put you back in a position of compatibility with the market. One of the things I always try to do is keep your business operations at a point
where if I die, someone else can come in and take my place. The whole idea here is to keep your business going."
It didn't take them long to come back and surprise me, "Make a list of what you need. Don't give us a list of what we need to get by, tell us what we need to be productive for several years. We don't want to patch this together
and always have problems."
And just as a note, your customer can write off $10,000+ per year for new equipment purchases. I think the number may be higher now. I had one customer who purchased a $15,000 system in December and wrote off $10,000 in one year and the other $5000,
a month later, in the next year!
Maybe you are looking for
-
how do I restore all of my itunes content onto my newly installed computer drive? All my purchase are no longer in my account but I did back up the files onto an external hard drive. Now how do I get them back? Please
-
I have a white MacBook and I just changed out the hard drive with a 500GB. When I turn it on I get a file fold with a ? In the middle that flashes. What do I do next?
-
Customer Service/Care, Really?
On February 13,2014, I bought my son an Apple 5c phone and had no problems with it at. On June 20,2014, my son went to a basketball camp and came back to the dorms to find his phone smashed to pieces. When he got home, I said don't worry I will ju
-
Attach to Mail using FileUpload UI in Web dynpro Java
Hi, I need to send a file from my system as attachment with a mail in a web dynpro java application. I am trying to implement it by uploading the file to server using FileUpload UI and then sending the file as attachment using java mail api which is
-
Adaptive Portlet Causing Screen Flicker on Dropdowns
I have a Master Portlet displaying a Datagrid with a Hyperlink column in it that raises a PCC event for an Adaptive portlet. The Detail portlet has a series of DropDown list boxes. When the user clicks on the link to call the PCC and the detail rende