Upgrade from Exchange 2000 STD to 2003 Enterprise

TheMSsForum.com: The Microsoft Software Forum

The MSS Forum ‹ Exchange Setup
- Archive
  - Biz
  - MCSE
  - CRM
  - Drivers
  - Framework
  - ADO
  - ASP
  - Compact
  - Forms
  - Dotnet
  - C#
  - VB
  - FontpageGen
  - Excel
  - WorkSheet
  - Exchange
  - Setup
  - Fox
  - Fontpage
  - ASP
  - IIS
  - Entourage
  - Money
  - Messanger
  - PocketPC
  - Powerpoint
  - Project
  - Publisher
  - Excel
  - VB
  - Security
  - Portal
  - Services
  - SQLServerDev
  - SVCS
  - SQLServer
  - VB
  - VC
  - MFC
  - ExcelGen

- Previous
  - 1
    - EXCH 2007 SP1 Does anyone know a release date for the Service Pack? Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160087
  - 2
    - Transfer licenses to new Exchange 2007 Server I'm going to be installing Exchange 2007 this coming weekend and then decomissioning our Exchange 2003 Server at the end of the transition. What I'd like to know is how can the licenses that we currently have on the Exchange 6.5 box be transferred over to the new server? Thanks! J Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160082
  - 3
    - Problems Reinstalling on a cluster Hello, hopefully someone will be able to help me, I'm stuck on a problem. I have a cluster of 2 2000 advanced servers, running e2k3. The problem is the http service has never run properly on one of these, so I tried to fix it (I inherited this site just a few months ago, so no one really knows whats going on!). Long story short I tried a few fixes to get this up and running, so as a last resort I tried to reinstall iis and exchange on the box (I said I'd try it first without removing the common IIS files, so it wouldn't affect the cluster service). Things were going to plan, until I tried to reinstall exchange, thats were the really messy problems come in! When I try to reinstall it prompts me for a 5.5 site, but there is no 5.5 site, its a native 2000 - 2003 exchange organistaion. As a drastic measure i tried to uninstall exchange from the server, bu then i get a 80005000 error when it tries to uninstall acitvesync (an invalid adsi pathname was found). From trawling through the web it looks like a probelm with the ad schema, so i tried running forestprep and domainprep, but the logs report back that they had already been run (of course, but i thought they might have repaired something corrupt). Any advice would be greatly appreciated before I go any further, Michael Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160081
  - 4
    - Connect to primary exchange Here's my scenario, from my branch office exchange 2003 server how can i connect to my HQ Exchange 2003 smtp server and retrieve our mail from their server which is in different location and both exchange are different organization. Daniel Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160078
  - 5
    - Emergency repair on small business server 2003 I did a repair install on a small business 2003 server. Is it necessary to complete the domain setup part? On the original install we did not setup the domain portion and within seven days I was forced to promote the server to a domain server. Where it is already setup dan I delete the icon or remove the install action? Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160075
  - 6
    - Exchange SMTPSVC log files - how do I get them to display timestamps in my local time zone? Why does MS Exchange 2003 SMTPSVC# log files display times in UTC? Is there a way to force it to convert all time stamps to the computer's local time zone setting? WHY would admins ever want to see it in another time zone? Call me silly :) Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160073
  - 7
    - Wildcarding part of an address Hi, We have an application that sends email through exchange. It is essentially a specialist document management system. it sends email to other organisations and they reply. The system has a number of projects which have email addresses eg project121@mydomain.com, project3321@mydomain.com When mail replies come to these projects they have to be filed which is quite annoying if a specific person invoked the first email sent out and wants to see the reply but also have it filed. I would like to be able to set up wildcards so that we can send out email in the form: userid.projectid@mydomain.com and have the reply come back to the mailbox projectid@mydomain.com at which point our system could see what userid this was sent to and present the message appropriately. We only want one exchange mailbox per project, we dont want to set up aliases to those mailboxes for every user who works on that project we just want one. So I would like to set up *.project121@mydomain.com -> project121@mydomain.com so that mikem.project121@mydomain.com gets filed in the box project121@mydomain.com Any ideas? I am not fixed on having . as the delimeter, some systems support # and + with special meaning. cheers Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160070
  - 8
    - HELP! Lost internet , need to move exchange to another location Please help! AT&T fiber lines were cut in the area, no internet for up to 7 days or more. What is the best way to be able to get email (send & rec). We have a customer with an exchange server close by, is there a way to configure this to add our domain and connect with wi-fi ( Sprint wireless & Laptop) and OWA to collect/send email temporarily? Any help is greatly appreciated. -- Thanks, Dan Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160069
  - 9
    - Installation error 1603 for Unified Messaging Role Installing E2007 from product CD on Win2003 R2 x64 SP2 server, with all roles except the Edge Transport. Logged in as the domain administrator. Everything else installed fine, but the Unified Messaging Role fails with the following event log error: Event ID: 1002 Source: MSExchangeSetup Exchange Server component Unified Messagin Role failed. Error: Error: Installing product D:\Setup\ServerRoles\UnifiedMessaging\es.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by MSI package is 'There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. '. The Unified Messaging install log follows: # Default Install steps for UnifiedMessagingRole. # Programmatically generated on 8/8/2007 5:34:27 PM. # # Variable Declarations # $RoleIsClusterNode = $False $RoleSourcePath = "D:\\" $RoleLogFilePath = "C:\ExchangeSetupLogs\add-umlang-en-us.msilog" $RoleIsBridgeheadRoleInstalled = $True $RoleNoSelfSignedCertificates = $False $RoleInvocationID = "20070808-1734270543" $RoleInstallPath = "C:\Program Files\Microsoft\Exchange Server\" $RoleInstallationMode = "Install" $RolePreviousVersion = "" $RoleIsMailboxRoleInstalled = $True $RoleBinPath = "C:\Program Files\Microsoft\Exchange Server\Bin" $RoleSetupLoggingPath = "C:\ExchangeSetupLogs" $RoleFqdnOrName = "mail.scdl.local" $RoleTargetVersion = "8.0.730.1" $RoleUpdatesDir = "D:\Updates" $RoleIsClientAccessRoleInstalled = $True $RoleLanguage = "en-US" $RoleRoleName = "UnifiedMessagingRole" $RoleDomainController = "dc1.scdl.local" $RoleProductPlatform = "amd64" $RolePackagePath = "D:\\Setup\ServerRoles\UnifiedMessaging\umlang-en-US.msi" $RoleNetBIOSName = "MAIL" $RoleLoggingPath = "C:\Program Files\Microsoft\Exchange Server\Logging" # # Component tasks # # Tasks for 'Speech Server Configuration' component # [ID = bf2bfa96, Wt = 1, isFatal = True] "Configuring the server." install-MsiPackage -PackagePath ($RoleSourcePath + "Setup\ServerRoles\UnifiedMessaging\es.MSI") -LogFile ($RoleSetupLoggingPath + "\InstallEs.msilog") -PropertyValues ("INSTALLDIR=`"" + $RoleInstallPath + "\UnifiedMessaging`" ESE=1") -UpdatesDir $RoleUpdatesDir Does anyone know what is causing this or how to resolve it? TIA Rick Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160068
  - 10
    - Exchange 2007 When trying to uninstall Exchange 2007, I cannot delete the public folder to remove the mailbox role. I have tried everything in the shell and console. Where are these replicas to the Public Database located and how can I delete them in order to remove the public database store? Any help would be appreciated... Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160067
  - 11
    - Synchronize 2 Exchange 2003 servers I was wondering if it is possible to keep 2 exchange 2003 server in sync with each other? I have one here at the main office and I want to setup one at a remote site and have a VPN tunnel between sites and keep the 2 server exchange information in sync or replicated. I want to be able to use the remote on in case the main site goes down and I want to have everyone email, contacts, calendars etc available on the remote one. I know there are products like double-take that can do this, but can I do this using exchange? If so, how? thanks Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160062
  - 12
    - removing Exchange 2003 I recently migrated my mailboxes from one 2003 server to another. I'm now ready to get rid of the old server. I'm doing the Exchange uninstall and selected "Remove" for the components installed and it's been sitting at "Stopping the server IISADMIN" for about an hour now. I'm assuming this isn't normal. Should I stop it and try removing Exchange manually or is this normal? Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160050
  - 13
    - Sending mail out from 2 domains to 2 smart hosts Hi there I have a requirement to allow messages sent out via my exchange server to go to 2 different smart hosts based on the domains they come from, ie users on domain 1 send out via smart host 1 and users on domain 2 via smarthost 2. A little strange, yes but that is what we want ! Anyone have any idea if it can be done on Exchange 2003 and if so how? thanks Andy Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160047
  - 14
    - Exchange disaster I have been planning replacing our Exchange server for a few weeks now, I have already purchased and recieved the new box and had everything ready for a transfer this weekend. Yesterday, the existing box died corrupting the current backup with it. The next most recent back I have avaliable is in archival storage off site, it is being retieved as we speak. The problem that I have is that the powers that be want the new server up ASAP. Is there anyway to bring a new box online, while maintaining the same name, e-mail address, etc without having the existing mailstore to work from? Also, is there a way to do this and still be able to restore my e-mails from my mailboxes in the back up when I receive it? -- Brian Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160046
  - 15
    - Create Alia for default OWA url I am new to Exchange 2007 and could use some guidenace. I am looking for the best\recommended way in allowing our user community to be able to access OWA via <owa.domain.com? vs the default <servername.domain.com/owa> Based on what I have read it looks like they no longer recommened creating multiple virtual directories. Thank You in advance, Kahlan Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160045
  - 16
    - Installing Exchange 2003 after buying 2007 >From what i've been told, if you buy Exchange 2007 + CALs you can legally install Exchange 2003 instead. Is this true, and if so, what license key would you enter? We ordered Exchange 2007 and CALs, and the 2003 media and got an eOpen authorization # and agreement #, but i'm assuming the 2007 product key wont work when we install 2003? Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160031
  - 17
    - Unsupported virtual machine configuration We a have a test environment setup on Vitual Server network: 2 x Windows Server 2003 SP1 Domain Controllers in separate sites. 2 x Windows Server 2000 SP4 Member Server / Exchange 2000 Servers in separate sites 1 x Windows Server 2003 SP1 Member Server / Exchange 2007 Server 1 Windows XP client running Outlook 2007 Everything has worked fine with connectivity and message flow between 2000 servers & clients. Exchange 2007 was intalled on the new server. All conditions were met for intallation, and no erros were reported. However on running the Best practices analyser (Health Check), we are receiving the following error: Unsupported virtual machine configuration - Exchange Server 2003 Service Pack 2 or later not detected http://technet.microsoft.com/en-us/library/d2739100-7206-43e7-a01f-ecb80ce243a2.aspx There is no mention of Exchange 2000 in the article, and we assume from the fact that our setup is not running Exchange 2003 SP2, then Exchange 2000 is not supported either. 2007 mailbox Users from the XP client (running Outlook 2007) are able to connect to the 2007 server (though abnormally slow), but cannot send or receive mail. The article recommends to either upgrade servers to specified requirements or decommision them. Neither solution allows us to test the coexsitence environmet that we would have in produvction with 2000 and 2007 Exchange servers. Are the connectivity / mail flow issues because of the fact that the configuration is unsuppored (as per article), or could this be due to other reasons..? We would gratefully receive any suggesstions to resolve the issue. Thanks, John. Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160030
  - 18
    - Migrate to Exchange 2007 or 2003? I need to Install/Migrate to Exchange 2007 or 2003 - but I have complications: CityA Server01 Windows 2000 Domain controller/GlobalCatalog Server Server02 Windows 2000 Server w/Exchange 2000 server CityB VPN to trusted domain to CityA (not a site) Windows 2000 Server (Domain Controller) CityC VPN to trusted domain to CityA (not a site) Windows 2000 Server (Domain Controller) We have purchased a box for an Exchange server. We were about to purchase Exchange 2007 but it has requirments that complicate our lives too much. It requires a 64 Bit OS (we are not sure if the computer has 64bit drivers) and the biggest pain - it requires a global catalog server that has windows 2003 server. We are forced to either buy a new computer with windows 2003 and make it the global catalog server OR make the box we have presently for Exchange the global catalog server. We are having problems purchasing Exchange 2003 - which is preferable since it's requirments will no cost us money. Questions: 1. Can we downgrade from Exchange 2007 to Exchange 2003? 2. If we must go to Exchange 2007 - what is the best configuration that we can go to that will not cost another computer? 3. If we can drop the trusted domains - Is SBS 2003 R2 a viable solution? Richard Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160029
  - 19
    - Changing Email Display Name Help!, I've got myself in a bit of a mess.... My customer has asked me to change the Email display name on outgoing messages in Exchange on SBS 2003... We have three users... Bob Jones, John Smith , Eric Turner.... The display name of each user was set to MYCOMPANY LTD... If I look at the users in the GAL, I can see them as Bob Jones, John Smith and Eric Turner... I found this document on the web and followed it... http://www.umich.edu/~lannos/exchange/docs/DisplayName.pdf What I now have in my GAL is three users all with the same name, MYCOMPANY LTD.... I think it is the "DoNotUpdateDisplayName" that has messed it up, but I don't know how to undo it... Can anyone tell me how I can get them back to where they were...? Really, really would apprciate any help on this one... Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160023
  - 20
    - Exchange 5.5 standard to enterprise ASAP Hi I Have Exchange 5.5 standard edition, I upgrade it to Exchange 5.5 Enterprise edition. My problem is that after the upgrade and reapplying SP4. All the mailboxes in exchange manager show Mailbox size 0. and the number of items ok. If I logon to the mailboxes I can see all the emails. Any idea? Than'x Shay ASAP Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160017
  - 21
    - Modifying Default GAL Hello, On our campus, Exchange 2003 is the official calendaring solution but not everyone uses Exchange as their exclusive mail server. There are two distinct mail systems, an Microsoft Exchange 2003 organization and Sun Mail. Likewise, there are two different authentication sources, LDAP and Active Directory 1.1. The LDAP accounts (along with passwords) are pushed into AD. Recently, we created an address list in Exchange System Manager under Recipients -> All Address Lists to show those individuals without Exchange mailboxes. The address list displays all the user accounts just fine and the email address field looks great in Outlook 2007. However, when we email individuals without an Exchange mailbox, the email comes back right away with an NDR that â??The message could not be delivered because the recipient's destination email system is unknown or invalidâ??. After looking at the address list entries in Outlook 2003, which shows the Exchange address, I see that the accounts without Exchange attributes show up like /o=NT5/OU=839DABâ?¦ instead of /o=Illinois State University/ou=â?¦ So weâ??d like to Exchange email address enable all AD accounts without Exchange attributes so that Exchange customers can easily email users of the Sun Mail. Thatâ??s easy enough to do. However, the Sun Mail handles the mail needs of our students so departments created AD accounts for student workers so we can give them an Exchange mailbox. When we email-address enable all accounts, then students will appear twice in the GAL and we think that will lead to some confusion. So I had the idea of modifying the GAL to exclude accounts that have just been email-address enabled and asking customers to use the default â??All Usersâ?? list to look up those individuals without Exchange mailboxes. Iâ??ve modified the LDAP query for the Default GAL and created a proposed Default GAL which does what I want and which several individuals have checked out as ok. The ESM GUI has the modify button for the Default GAL grayed out even when after I disabled the inheritance of permissions (copying the previous permissions) and removing the deny permission that my admin account had. It appears to me that I will have to modify the attribute purportedSearch of the Default GAL with ADSI edit in order to change the LDAP query of the Default GAL. Has anyone else been in a similar situation? How did you overcome it? Has anyone modified the LDAP query for the default GAL in an Exchange 2003 organization? Is this something I should be doing? Please let me know if I can clarify something or provide more information. Thanks, Bill Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160016
  - 22
    - Existing W2k3/Exchange2k7 pulling in a SBS2k3/Exch2k3 domain. Hello all! I am gathering information on migrating a SBS domain into an existing W2k3/Exch2k7 standard environment. Has anyone seen any "official/and good" documentation on a supported transition/migration path? I have been through several Technet sites that outline "Standard/Enterprise" level migrations, but these involve creating trusts and to the best of my knowledge SBS domains cannot create the trusts required to do those types of migrations. At this time I am sure I can migrate the AD domain User/Computer accounts using ADMT v2.0, but I am not sure if this version of the ADMT tool can do the Exchange2k3 to Exchange 2k7 mailbox migration. Has anyone tried this approach? Or am I missing something... I guess I can always exmerge the mail from Exchange2k3 into .pst(s) and import them manually using Outlook back into Exchange2k7, but this will be rather cumbersome because of downtime and the physical distance between the respective servers. On another not does anyone know of a "good way" to support migrated Exchange 2k/2k3 Public Folders in a Exchange 2k7 environement without using a legacy Exchnage2k3 server? I have heard you can leave just the Exchange2k3 ESM behind, but I am not psoitive this is really supported. This is also a troublesome and relativley undocumented from a "real world" point of view. Any feedback would be greatly appreciated. Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160011
  - 23
    - KB911829 Fix: Two New Issues Hi there, I'm working on an Exchange server where people use OWA to send/receive emails. A few people are on Vista as of Monday, so I installed Microsoft Update KB911829 to get them to be able to send/receive. However, two new issues have arisen since then: 1) We're running Exchange through Dynamic DNS (this is how it was set up before I got here), and as such we don't have an SSL. However, we do have graphic signatures of the form <img src="http://www.site.com/ image.gif" ... /> . Since these images aren't on an SSL, users get prompted to ask them whether or not they want to download non-secure items each time. I suspect we're going to have to get an SSL, due to the nature of the iframe mentioned in KB911829, but I just wanted to know if there's anything else I might be able to do in the meantime. 2) Some of the signatures have started to show up twice when composing a new message. This only affects maybe half a dozen people, but it didn't happen before KB911829 and it does now. Is there something I need to change, or a patch I need to download, for this issue? Thanks very much. Adam Senour http://www.walkonmypath.com/ Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160007
  - 24
    - I'm guessing Exchange can do this but have no idea where I'd start... Can Exchange servers from different businesses at different sites be configured to see each other? Like can one company see the others schedules for instance? Our parent company has Exchange and us as a deal would like them to be able to see calendars etc..... Can this be done and what would the connection be called? Thanks Kelvin Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160004
  - 25
    - Emails to domain not routed to external Server Good Morning Everyone, I hope everyone is doing well today. We are hosting our website internally BUT the email is on an external server outside of our office. I set up the DNS records to point the website to our internal webserver(DMZ) BUT I set up an MX record to point to our external mail server. Users can access the website ok, www.ourdomain.com, but when sending an email to anyone@ourdomain.com comes back 1-2 days later as non-deliverable. It doesn't come back immediately but about 1-2 days later it doesn't show up. What didn't I set up correctly in DNS. I thought all I needed to set up mail on the domain was the MX record pointing to the external server? We're running SBS2003 SP1 Premium with ISA 2004. Thanks! Sincerely, Anthony Smith In God We Trust! Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 160000
- Next
  - 1
    - Install Exchange 2003 error Hi all, I'm having trouble installing Exchange 2003 on to a Windows Server 2003 machine in a test environment. The Server is a clean install set up to be domain controller, DNS, no- DHCP. I am trying to run setup from the Exchange Deployment Tools (Deploy the first Exchange 2003 Server>>New Exchange 2003 Installation). All services seem to be installed ok, netdiag and dcdiag look ok, but I've not really used them before so I'm not 100%. When I try to run Setup (or domainprep or forestprep) it copies files quickly then I get the error message: "The application or DLL C:\Documents and Settings\Administrator\Local Settings\Temp\SIT10511.tmp\exsetdata.dll is not a valid Windows image. Please check this against your installation diskette." I'm have a reasonable knowledge of Server, so go easy. ;-} All help appreciated. Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159992
  - 2
    - Outlook Web Access I am attempting to set exchange up in our domain. exchange with outlook is working great. I am having real problems with OWA though. Here are the scenario's so far As a domain admin I can log in to OWA but only by doing URL/exchange/MailBoxName As a normal authenticated user i get one of two results either Access Denied after the username and password box comes up 3 times. the account is not being locked out or The Local Security Authority cannot be contacted again the account is not being locked out. The latter one happens on a new user account the former on an established user account. Any advice on this would be greatly appreciated i have tried forms authentication but no matter what itry i alwats get error 440 timeout, even though i get this page instantly. Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159983
  - 3
    - imap on EXCH2007 Hello, Some clients on my network use IMAP4 protocol to read there mails on my exchange 2007 server. Everything was working fine, but now there is a problem, they cannot make a connection anymore to the server ( nothing changed on the configuration) I enabled logging for the imap4 protocol. This is the result, wat does this mean? Tx, OK Microsoft Exchange Server 2007 IMAP4 service ready, 2007-08-06T13:04:13.415Z,,0000000003F933D5,2,192.168.100.87:143,192.168.104.167:3156,<,1 capability, 2007-08-06T13:04:13.415Z,,0000000003F933D5,3,192.168.100.87:143,192.168.104.167:3156,>,* CAPABILITY IMAP4 IMAP4rev1 LOGINDISABLED STARTTLS IDLE NAMESPACE LITERAL+, 2007-08-06T13:04:13.415Z,,0000000003F933D5,4,192.168.100.87:143,192.168.104.167:3156,>,1 OK CAPABILITY completed., 2007-08-06T13:04:13.430Z,,0000000003F933D5,5,192.168.100.87:143,192.168.104.167:3156,<,2 STARTTLS, 2007-08-06T13:04:13.430Z,,0000000003F933D5,6,192.168.100.87:143,192.168.104.167:3156,>,2 OK Begin TLS negotiation now., 2007-08-06T13:04:13.430Z,,0000000003F933D5,7,192.168.100.87:143,192.168.104.167:3156,-,,Local Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159981
  - 4
    - Problem with 2007 send connector Background: Small domain. Previously exisiting exchange 2003 server, stable and no apparent problems. Email to external recipients is directed to corporate email servers, non exchange, for delivery. New 2007 exchange server installed. New and old servers are running and will deliver internal mail to each other. The problem is the outbound email to external addresses from the 2007 server. I've setup a send connector to the same external smart host but the 2007 server does not seem to recognize it exists. The 2003 external connection still functions so I know the external host is OK. When I attempt to send email to an external account, I get an immediate undeliverable notice, error message follows. #550 5.1.1 RESOLVER.ADR.RecipNotFound Message tracking indicates it never left the server so it's not a rejection at the corporate end. The system seems to be acting as if the send connector does not exist. I've seen a technet article on how to set up the system to use the 2003 send connector from the 2007 machine but that's not what I want. The 2003 box is going to be removed once the new system is running and reliable. Any suggestions on how to get it working. Jerry Wright Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159977
  - 5
    - Incoming messages to two Exch Servers. Hi, o I have an Exchange 2003 running in co-existence with Exch 2007. o Both servers are on the same router. o I have the router's port 25 directing incoming messages to Exch 2003. o For those mailboxes moved over to Exch 2007, the routing group connector passes it over to Exch 2007. The procedure I have tells me to redirect port 25 over to Exch 2007 once all the mailboxes have been moved over and just before I decommission the Exch 2003 server. However, I'm wondering if it is possible to redirect port 25 to Exch 2007 now, while I still have my mailboxes split between the servers? Will the routing group connector pass messages destined for mailboxes on Exch 2003 over to the Exch 2003 server? If the answer to the above question is yes, what would happen if I configured my router to send port 25 traffic to both Exchange servers? p.s. Because I won't be using an Edge Transport server, I have changed the Permission Groups settings to allow Anonymous users on Server Configuration >> Hub Transport >> Receive Connectors >> Default server. Thanks! --- Bob Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159976
  - 6
    - Exch 2007 - Accepted Domains Hi, I'm running in coexistence (2003 & 2007). I see in 2007 in Organization Configuration >> Hub Transport >> Accepted Domains tab that I have three accepted domains listed as being authoritative. I can't remember entering these and I presume they somehow came over from Exch 2003. Where in Exch 2003 are the equivalent entries located? Thanks! --- Bob Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159973
  - 7
    - Upgrade from 2000 to 2003 Hi All, I plan to upgrade from Exchange server 2000 to EX server 2003. I have EX 2k installed on an old PIII box. I am buying a new Dell server. I plan to build the new Dell server as a win 2k server and install EX 2k on it then restore all of the old data from a tape backup. Once this is done i plan to upgrade Exchange 2k to Exchange 2003, then upgrad the OS from Server 2k to Server 2003. Does anybody see an easier or better way to do this. Any comments or suggestions would be greatly appreciated. Thanks Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159972
  - 8
    - Exchange 2003 ActiveSync Front/Back End question I have an Exchange 2003 server. Last year I migrated everything from my Exchange 2000 server to the 2003 server successfully. The Windows 2000 server w/ Exchange 2000 is still in my Active Directory but all the mailboxes have been moved to the new server. It's been sitting ther "idle" for a couple years now. Recently, some employees got some "smart phones" and I have been trying to get activesync working. I can not get it to work properly and I found a MS support article about Exchange being a front end server. If I go into my new Exchange 2003 server and try to click the option to make it a front end server I get an error message (sorry I don't know what it says.) Could my new server, in fact be a back end server? and the 2000 server be working as a front end server? I would eventually like to get rid of the 2000 server. Should I just uninstall Exchange 2000 on the old server? Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159971
  - 9
    - Vista x32 and Management Tools error. I am on Vista Business x32 and I downloaded the Exchange 2007 Management Tools x32 bit from Microsoft and ran the setup.exe I got to the Readiness Checks and get the error below. I installed IIS and PowerShell 1.0 for Windows Vista, or I would not have gotten this far. I am not sure why I am having this problem. I ran as administrator. Summary: 1 item(s). 0 succeeded, 1 failed. Elapsed time: 00:00:09 Management Tools Prerequisites Failed Error: Exchange 2007 cannot be used with the version of Windows operating system running on this computer. Elapsed Time: 00:00:10 Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159969
  - 10
    - Exchange 2007 - Send Connectors Hi, Is it possible to do the following with send connectors in Exchange 2007? 1) Have high priority email use connector "a" and low priority to use connector "b" and normal to use connector "c"? 2) Prevent an individual user from accessing connector "a"? 3) Prioritize connectors to use "a" before "b"? 4) Schedule connector "a" to be available in the evening and "b" to be available in the day time? Thanks! --- Bob Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159966
  - 11
    - OPT OUT List Is there any way to set up an OPT OUT list in Exchange or does this require third party software? Thanks. Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159965
  - 12
    - New exchange server My exchange serverâ??s hardware needs replacing, I have the following plan but thought I share my plan with someone experienced to make sure I am taking the correct approaches and to learn if I am missing aything. Existing Exchange2003 server is currently installed on a windows 2000 server that is also a DC. Single domain no other exchange or mail servers exist except the one I plan to remove. My action plan is; to Install exchange on a windows 2003 R2 server as additional exchange to the domain, then move all mail boxes and public folders, then make it frontend server, Change NAT address at the firewall to point to new server that has new name and IP address. DCpromo the old server, uninstall exchange, remove the server from domain. Please someone experienced, let me know what you thinkâ?¦..Will OWA be automatically point to new server? Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159962
  - 13
    - 2 Mailbox Size Policies? Hello Is it possible to have 2 policies for Mailboxes - i.e. one at 50 MB and 1 at 30 MB or do I just have to have the default set to 50 MB and set the users who require 30 MB manually? Thank you Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159959
  - 14
    - Install Order - Server Roles - E2007 I know the install order is: Client Access Server Hub Transport Mailbox server UM We do not have enough money to split the CAS & MB role; so, I plan to install CAS & MB on one server and then I will have a separate Hub Transport server. Question: Using the above scenario, do I install the CAS & MB server and then do the Hub Transport immediately after? thanks -Harri Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159953
  - 15
    - OWA Self signed certificate and Outlook 2007 Hi too all, i'm new to this group, I hope you can help me. I use OWA to access my mail on a https:// server but the certificate was self signed, as you can see on: http://clientes.netvisao.pt/mferra/4.png I have tried to import the certificate into Internet Explorer's Trusted Root Certification Authorities (under Tools, Internet Options, Content), but that warning always appears. The problem is that that I'm trying to use Microsoft Outlook 2007 to access, through RPC I think, the OWA site. But, because of the certificate, I get this error: http://clientes.netvisao.pt/mferra/3.png How can I access my mail in Outlook 2007 and how can import the certificate? Sincere regards and thanks in advance, Marco Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159952
  - 16
    - OWA Login Screen Doesn't Load Hello, We currently use Exchange 2000 and it is working fine. However, the OWA won't load properly. The authentication screen comes up, but no matter what username and password I use it comes back with this message: HTTP 401.1 - Unauthorized: Logon Failed Internet Information Services Sometimes it will load, but only show the directory on the server. It will never show the regular OWA screen. The Inbox, Deleted Items and other folders will show, but not the default screen. Any help would be greatly appreciated. Thanks, Tom Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159950
  - 17
    - exchange 2007 installation deathlock... Hi group, i had install ex2007 in an existing ex2003 domain (single). there are 2 ex2007 server one in the perimeter (CA und HT role) and one in the internal net (MB role). For the time of setup der FW rule is any2any. the CA and HT server works fine. The MB server ist reachable via console, i can create users and mailboxes, sending- receiving mails inside the ex2007s but sending mail from the 2003 to 2007 fails. the best practices analyser report that the mailbox role is configured partially and suggest to rerun setup. rerun setup causes the following errors: "Unexpected Error" and "Service 'MSExchangeTransportLogSearch' is not installed on this server". Uninstalling the hole ex2007 will result in the following error: "Process execution failed with exit code 5". Once runnig the uninstallation setup prevents installing any role on the system... any ideas to solve this mess? josh Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159942
  - 18
    - EXTERNAL MAIL PROBLEM Hello; My exchange 2007 server ( standard install, no edge server) is working fine for 2 months. Since yesterday evening i cannot receive external mails anymore. (no configuration is changed) Internal mail and sending mail out is no problem. The senders receiving this error : 550 5.7.1 External cli ent does not have permissions to submit to this server (in reply to MAIL FROM command)) ... Please help, Tx,, Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159936
  - 19
    - Exchange 2003 front-ends in mixed mode Can anyone tell whether one Exchange 2003 front-end server would be sufficient in a mixed-mode environment with Exchange 2003 and Exchange 5.5 servers with several sites (read: administrative groups)? I am talking only about technical functionality, not load handling etc. There are about 15 sites, of which some sites have Exchange 5.5 servers, some both 5.5 and 2003 and some only Exchange 2003 servers. The front-end server would be used to access ActiveSync for users that have their mailbox on 2003 servers. The main question is that is it enough to have only one front-end server in one site, or should each site to be accessed have its own front-end server? Again, only mails on 2003 servers would be accessed, there's no need to access 5.5 servers through front-end servers. The 2003 servers reside in different sites. Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159935
  - 20
    - Exhchange migration and old server decomission Hi, I am nearing the completion of an exchange migration. The old server is exchange 2003 standard (DC), the new on Exchange 2003 standard (not DC). I have added the server to the organisation and migrated across all user accounts to the new server, and moved the public fodlers. I am now wondering the following regards to steps i need to take to decomission: - do i migrate the system accounts - System Attendant, System Mailbox, SMTP (<old Server) or do i leave these on the old server for when i decomission it. - do i need to do anything to the new server to make it the primary server in the organisation. - how do i actually take the exchange server out of the organisation. The server will actually remain on the network performing DC roles for the time being, and also some other bits and piecies. I want to remove its exchange role before removign its other roles Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159931
  - 21
    - Query-based Distribution Groups Hi, In Exchange 2003, I created Query-based Distribution Groups using the AD fields Company and Street Address. In 2007, I see these were copied over to Recipient Configuration >> Distribution Group and renamed Dynamic Distribution Group. However, I am unable to edit the conditions. But seeing how I only have a few of these, I thought I would recreate them in 2007. I find that when I create a new Dynamic Distribution Group, I only have three conditions to choose from. Company is available, but Street Address is not (I suppose this needs to be created with the shell!). So I skipped the Street Address and used only "Recipient is in a Company". I copied/pasted from an Exchange 2007 Mailbox user's "Organization - Company" field, so there can't be any typo's. I also change the filter to "All recipient types". When I click Preview, nothing displays. Is there some trick in 2007 that I need to know about to make Dynamic Distribution Groups work? Thanks! --- Bob Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159930
  - 22
    - Exchange 2007 - Recipient Policies Hi, In Exchange 2003, I had two E-Mail Addresses recipient polices that migrated over to Exchange 2007 Organization Configuration > Hub Transport > E-Mail Address Policies tab. When I try to edit them, a message displays that they must be upgraded using the 'Set-EmailAddressPolicy' task with the Exchange 2007 Recipient Filter specified. Is this something I can do now, or should I wait until after I'm no longer in co-existence mode with Exchange 2003? Also,in Exchange 2003, I had one Mailbox Manager Settings recipient policy. Where is this located in Exchange 2007? Thanks! --- Bob Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159929
  - 23
    - Exchange 2007 - Hub Transport Hi, In Exchange 2003, I had the following options in its SMTP Connectors that I can not find in Exchange 2007 that doesn't have an Edge Transport server. Content Restrictions - Allowed priorities (High, Normal and Low) Delivery Options - Connection time Address Space - Cost (where I can configure which connector to use before another) Delivery Restriction - (where I could restrict particular users from using certain connectors. I used this to restrict a user that sent tons of solicitations (spam like), to use a connector that wouldn't block her after 500 emails/hour. I never could get it to work however). I do not see these options available in 2007 under Organization Configuration > Hub Transport > Send Connector tab. Both servers are running in transition mode so all these settings came over from Exchange 2003. Any idea where these settings are now located? Thanks! --- Bob Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159928
  - 24
    - Autodiscover 403 forbidden error I am having troubles getting autodiscover to work for those users not currently joined to the domain (Internal). The internal domain is a .local (exa mydomain.local) w/ the external being a .edu (exa mydomain.edu). We have followed method 1 of http://msexchangeteam.com/archive/2007/04/30/438249.aspx and have a valid certificate, and seperate website/web virtual directory on the same CAS server, for email.mydomain.edu and autodiscover.mydomain.edu. This was done to ease IAG 2007 Exchange certificate setup. When I run Test-OutlookWeb Service | fl it returns the following: Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address Administrator@mydomain.edu. Id : 1007 Type : Information Message : Testing server cas1.mydomain.local with the published name https://email.mydomain.edu/EWS/Exchange.asmx & https:// email.mydomain.edu/EWS/Exchange.asmx. Id : 1019 Type : Information Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://autodiscover.mydomain.edu/autodiscover/autodiscover.xml. Id : 1013 Type : Error Message : When contacting https://autodiscover.mydomain.edu/autodiscover/autodiscover.xml received the error The remote se rver returned an error: (403) Forbidden. Id : 1006 Type : Error Message : Failed to contact AutoDiscover Those machines not joined to the domain recieve a pop asking them to login into autodiscover.mydomain.edu which if they provide lets them setup their outlook 2007 accounts normally. How do a fix this? Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159927
  - 25
    - Retrieve email from Exchange 2003 with AD corrupted Hi All, I need a help. I have a 2003 server with Exchange 2003 installed. However, the AD file ntds.dit is corrupted is can't be recovered. So, I decide to reinstall AD and server. My email server data is saved in external HD and seems ok. Can anyone teach me how to retrieve the email back after a new server install? Regards, Berthold Tag: Upgrade from Exchange 2000 STD to 2003 Enterprise Tag: 159924

We are going to be upgrading from 2000 STD to 2003 Enterprise with new
hardware (BL460C Blades). Do you have any documents on how to accomplish this?

Top

Re: Upgrade from Exchange 2000 STD to 2003 Enterprise by Mark

Mark
Thu Aug 09 10:39:25 CDT 2007

On Thu, 9 Aug 2007 07:36:05 -0700, Greg
<Greg@discussions.microsoft.com> wrote:

>We are going to be upgrading from 2000 STD to 2003 Enterprise with new
>hardware (BL460C Blades). Do you have any documents on how to accomplish this?

You're not upgrading, you are migrating.
http://www.msexchange.org/tutorials/Migrating-Exchange2000-Exchange-2003-Hardware.html

Top