Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all 7008 articles
Browse latest View live

Error when Installing Exchange 2013 in an existing Exchange 2010 organization

$
0
0

When trying to install Exchange 2013 with SP1 on a Windows 2012 R2 Standard server (member server) in an existing organization containing one Exchange 2010 server with SP3 and RU7 installed I get the following message during the Readiness Check:

Error:

All Exchange 2010 servers in the organization must have Exchange 2013 Service Pack 3 or later installed. The following servers don't meet this requirement: .......

I have confirmed that the versions and build numbers of the exchange 2010 install are correct.  I have confirmed that AD schema is at the correct version.  Thank you


Exchange 2013 Recover Server

$
0
0

Hi,

We have/had 3 Exchange 2013 servers with all roles installed.  Databases being set up in a DAG.  The servers are VM's that sit on a SAN however we have had an issue with the SAN and as such have lost all Exchange VHDs.  Our backup was only backing up mailbox databases so can only recover mail data.

I have rebuilt the 3 servers and tried to run "setup /m:recoverserver" however as we previously had a DAG this does not work.  The error points to http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.MemberOfDatabaseAvailabilityGroup.aspx and it appears that the way to get around this is to use EMS to remove the server from the DAG, run the command and then re-add to the DAG however as we don't have any available mail servers to do this we have hit a brick wall.

Is there another way around restoring the servers?  I'm not sure if there is something I can do in adsiedit to get around this (delete the server names from the databases?).

Thanks 

The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed

$
0
0

Hello Everyone,

I've been installing Exchange servers since Exchange 5.5. I'm now installing Exchange 2013 with SP1 that will coexist with one Exchange 2010 SP3 server. I'm installing it on 2012 R2 Enterprise Edition. There is a root domain and one child domain. The Exchange Server is in the child domain.  Even though I've run the .\setup PrepareSchema, AD and domain and all were successful I still get the message below when running Exchange setup. If I look at what /preparedomain does it seems like it has done what is needed. I've run the /prepareschema, /preparead and /preparealldomains in the root domain & have even run /preparedomain over and over in the child domain. Like I said everytime I run these they are successful. Oh and my account belongs to all the right groups needed to run these. Any ideas would be appreciated!

The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DomainPrepRequired.aspx


Server Planning For Exchange 2010 Sp3

$
0
0

Hi All.

If anyone has experience with deploying Exchange Server 2010 with necessary hardware requirements it would be most appreciated.

Currently we have 5 sites each with an Exchanger Server 2003 sp2 per site. 100 or less mailboxes per server (Average size of mailbox = 800 mb - 1.5 gb)

We are planning to move to Exchange 2010 SP3 but currently I am finding it challenging to plan the hardware necessary.

We can either go one Typical role server per site with 100 mailboxes roughly on each server, also maybe one slightly stronger server holding the 500 mailboxes.

We are going to be using Mimecast so mailboxes wont be too big and once they reach their size limit archiving will take place.

Mimecast will be filtering our email thus I don't see it necessary for an edge server (Your thoughts on this would be great)

If we go the one typical server per site route I was going to go with the following:

Dell t320

INTEL XEON E5-2420 1.90GHZ, 15M CACHE, 7.2GT/S QP

32 Gig Ram

4 x 900 GB SAS IN RAID 10 Setup (Probably Overkill But Drives Arent Expensive)

VMware VS non VMware deployment (Your thoughts)

IF we go the one server route I was planing on the the following:

Dell T720

INTEL XEON E5-2630 2.30GHZ, 15M CACHE, 7.2GT/S QPI

32 GIG RAM

4 x 900GB SAS IN RAID 10 Setup

Currently our WAN lines are only 2mb between sites, thus the reason I'm scared of going this route for the traffic that might be generated for remote clients connecting to the exchange server.

Any help will be really appreciated from experienced users who have deployed various scenarios.

Much Appreciated

Shaun.

Exchange Server 2013 64bit with SP1 Standard - Readiness Checks/Prerequisite Analysis

$
0
0

I'm trying to install Exchange 2013 with SP1 on Windows Server 2012 R2 Standard, at the Readiness Checks setup, I get 25 errors. Before the Readiness Checks setup, I had selected 'Automatically install Windows Server roles and features that are required to install Exchange Server'. How come they are not automatically installed? Do I have to manually install these 25 items? That's a lot of work.

The Readiness Checks - Prerequisite Analysis produces this:

Error:

This computer requires Windows Media Audio Voice Codec. Install the Desktop-Experience component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornWmspdmoxNotInstalled.aspx

 

Error:

The World Wide Web (W3SVC) service is either disabled or not installed on this computer. You must exit Setup, install the required component, and then restart Setup.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.W3SVCDisabledOrNotInstalled.aspx

 

Error:

The 'IIS 6 Metabase Compatibility' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS6MetabaseNotInstalled.aspx

 

Error:

The 'IIS 6 Management Console' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS6MgmtConsoleNotInstalled.aspx

 

Error:

The 'IIS 7 Dynamic Content Compression' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7HttpCompressionDynamicNotInstalled.aspx

 

Error:

The 'IIS 7 Static Content Compression' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7HttpCompressionStaticNotInstalled.aspx

 

Error:

The 'Windows Process Activation Service Process Model' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornWASProcessModelInstalled.aspx

 

Error:

The 'IIS 7 Basic Authentication' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7BasicAuthNotInstalled.aspx

 

Error:

The 'IIS 7 Windows Authentication' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7WindowsAuthNotInstalled.aspx

 

Error:

The 'IIS 7 Digest Authentication' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7DigestAuthNotInstalled.aspx

 

Error:

The 'IIS 6 WMI Compatibility' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS6WMICompatibility.aspx

 

Error:

The 'ISAPI Filter' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornISAPIFilter.aspx

 

Error:

The 'Client Certificate Mapping Authentication' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornClientCertificateMappingAuthentication.aspx

 

Error:

The 'Directory Browsing' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornDirectoryBrowse.aspx

 

Error:

The 'HTTP Errors' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpErrors.aspx

 

Error:

The 'HTTP Logging' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpLogging.aspx

 

Error:

The 'HTTP Redirection' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpRedirect.aspx

 

Error:

The 'Tracing' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornHttpTracing.aspx

 

Error:

The 'Request Monitor' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornRequestMonitor.aspx

 

Error:

The 'Static Content' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornStaticContent.aspx

 

Error:

The 'Web-Mgmt-Service' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ManagementServiceInstalled.aspx

 

Error:

This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from http://go.microsoft.com/fwlink/?LinkId=260990.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx

 

Error:

The 'IIS Management Console' component is required. Install the component via Server Manager.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornIIS7ManagementConsoleInstalled.aspx

 

Warning:

Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx


Thanks


Error: Create PartnerApplication "Exchange Online" in DC and On-Premise

$
0
0

Hello,

i get this error when i  Prepare Active Directory for Exchange:

[01/12/2013 10:11:27.0640] [1] [ERROR] The following error was generated when "$error.Clear();
          #
          # O15# 2844081 - Create PartnerApplication "Exchange Online" in DC and On-Premise
          #
          $exch = [Microsoft.Exchange.Data.Directory.SystemConfiguration.WellknownPartnerApplicationIdentifiers]::Exchange;
          $exchApp = Get-PartnerApplication $exch -ErrorAction SilentlyContinue -DomainController $RoleDomainController | Where { $_.UseAuthServer };
          if ($exchApp -eq $null)
          {
              $exchAppName = "Exchange Online";
              $exchApp = New-PartnerApplication -Name $exchAppName -ApplicationIdentifier $exch -Enabled $RoleIsDatacenter -AcceptSecurityIdentifierInformation $false -DomainController $RoleDomainController;
          }

          # Create application account for Exchange
          $appAccountName = $exchApp.Name + "-ApplicationAccount";
          $appAccount = Get-LinkedUser -Identity $appAccountName -ErrorAction SilentlyContinue -DomainController $RoleDomainController;
          if ($appAccount -eq $null)
          {
            $appAccountUpn = $appAccountName.Replace(" ", "_") + "@" + $RoleFullyQualifiedDomainName;
            $appAccount = New-LinkedUser -Name $appAccountName -UserPrincipalName $appAccountUpn -DomainController $RoleDomainController;

            New-ManagementRoleAssignment -Role "UserApplication" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "ArchiveApplication" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "LegalHoldApplication" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "Mailbox Search" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "TeamMailboxLifecycleApplication" -User $appAccount.Identity -DomainController $RoleDomainController;
            New-ManagementRoleAssignment -Role "MailboxSearchApplication" -User $appAccount.Identity -DomainController $RoleDomainController;

            Set-PartnerApplication -Identity $exchApp.Identity -LinkedAccount $appAccount.Identity -DomainController $RoleDomainController;;
          }
        " was run: "Couldn't find object "mydomain.local/Users/Exchange Online-ApplicationAccount". Please make sure that it was spelled correctly or specify a different object.".
[01/12/2013 10:11:27.0640] [1] [ERROR] Couldn't find object "mydomain.local/Users/Exchange Online-ApplicationAccount". Please make sure that it was spelled correctly or specify a different object.
[01/12/2013 10:11:27.0640] [1] [ERROR-REFERENCE] Id=CommonGlobalConfig___907E0EE000AB4117A05F237A81E53AA2 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/12/2013 10:11:27.0640] [1] Setup is stopping now because of one or more critical errors.
[01/12/2013 10:11:27.0640] [1] Finished executing component tasks.
[01/12/2013 10:11:27.0671] [1] Ending processing Install-ExchangeOrganization
[01/12/2013 10:34:25.0119] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[01/12/2013 10:34:25.0119] [0] End of Setup

Exchnage 2003 to Exchange 2013

$
0
0

Instead of going from Exchange 2003 to 2010 to 2013. I have decided to remove Exchange 2003 from the organization and install 2013 since I don't have too many users.

I have removed Exchange 2003 from the Organization (http://tutorial.programming4.us/windows_server/Removing-an-Exchange-Server-2003-Server-from-an-Organization.aspx).

When I install Exchange 2013, it doesn't ask me for the organization name. Is it using the data that was left in Active Directory from Exchange 2003? I ran the setup to uninstall Exchange 2003, doesn't that remove the Exchange 2003 data in Active Directory as well?

Thanks

Legacy Exchange auto-complete issue

$
0
0

Hi,

We are a hosting exchange provider company. We recently migrated a company from rackspace to our hosted Exchange. All users are successfully migrated and are sending and receiving emails.

The issue is that external users have autocomplete email addresses of rackspace's users in their outlook. Now that users are migrated to our exchanage, if someone tries to send an email using autocomplete address from outlook then email bounced back.

I also tried to send an email using autocomplete and email bounced. Bounced email shows rackspace's server name in the rejection message.

Is there any permanent solution to this issue? I have read about X500, but we migrated 5000 users. How can we create x500 for 5000 users?

 Any help will be highly appreciated.

Regards,

Anees


Fresh Install Exchange 2013 on Hyper-V- driving me MAD!

$
0
0

Install Error " A Restart from a Previous Installation is Pending"- How- This is a brand new Hyper-V??

Fix= delete/ amend values under;

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

PendingFileRenameOperations doesn't exist and NO entry under UpdateExeVolatile!!

This error therefore makes no sense . Also checked under currentcontrolset001 .

Does anyone know about this I know others have had this problem too.

Thanks



Exchange 2013 Unexpected reboot by MSExchangeHMWorker

$
0
0

I have an Exchange 2013 server installed and noticed that the server unexpectedly rebooted itself. It created a dump file and within the dump file it states that it was caused be the MSExchangeHMWorker. 

I know that Exchange 2013 has the Managed Availabilty concept and will attempt to "fix" itself if there is an issue however I would like to know why or what prompted exchange to do this so i don't have this in the future.  Is there any known logs that records why this happened?  I am not seeing anything in the event logs.

Thanks


Memory dump info below:

5: kd> !analyze -v 
******************************************************************************* 
* * 
* Bugcheck Analysis * 
* * 
******************************************************************************* 

CRITICAL_PROCESS_DIED (ef) 
A critical system process died 
Arguments: 
Arg1: ffffe001d1930900, Process object or thread object 
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died. 
Arg3: 0000000000000000 
Arg4: 0000000000000000 

Debugging Details: 
------------------ 

----- ETW minidump data unavailable----- 

PROCESS_OBJECT: ffffe001d1930900 

IMAGE_NAME: wininit.exe 

DEBUG_FLR_IMAGE_TIMESTAMP: 0 

MODULE_NAME: wininit 

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME: MSExchangeHMWo 

BUGCHECK_STR: 0xEF_MSExchangeHMWo 

CUSTOMER_CRASH_COUNT: 1 

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER 

CURRENT_IRQL: 0 

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre 

LAST_CONTROL_TRANSFER: from fffff8011bc89dcc to fffff8011b7cdfa0 

STACK_TEXT: 
ffffd000`2b8a79a8 fffff801`1bc89dcc : 00000000`000000ef ffffe001`d1930900 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx 
ffffd000`2b8a79b0 fffff801`1bbac23e : ffffe001`d1930900 00000000`00000000 00000000`00000000 fffff801`1b7e353c : nt!PspCatchCriticalBreak+0xa4 
ffffd000`2b8a79f0 fffff801`1ba090e9 : ffffe001`d1930900 ffffe001`d8eb6900 ffffe001`d1930900 ffffe001`d1930900 : nt! ?? ::NNGAKEGL::`string'+0x7bce 
ffffd000`2b8a7a50 fffff801`1ba08e76 : ffffffff`ffffffff ffffe001`d8eb6900 ffffe001`d1930900 ffffe001`d9d89880 : nt!PspTerminateProcess+0xe5 
ffffd000`2b8a7a90 fffff801`1b7d97b3 : ffffe001`d1930900 ffffe001`d9d89880 ffffd000`2b8a7b80 00000000`ffffffff : nt!NtTerminateProcess+0x9e 
ffffd000`2b8a7b00 00007ffc`4bc5afca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 
00000000`2d58e3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`4bc5afca 


STACK_COMMAND: kb 

FOLLOWUP_NAME: MachineOwner 

IMAGE_VERSION: 

FAILURE_BUCKET_ID: 0xEF_MSExchangeHMWo_IMAGE_wininit.exe 

BUCKET_ID: 0xEF_MSExchangeHMWo_IMAGE_wininit.exe 

ANALYSIS_SOURCE: KM 

FAILURE_ID_HASH_STRING: km:0xef_msexchangehmwo_image_wininit.exe 


WWT IT


New Install - Corrupt Admin

$
0
0

Hi All,

We have done a fresh install of Exchange Server 2013 sp1, on server 2012r2. I am getting an issue on the Administrator account after logging in.

warning

The object abceuk.com/Users/Administrator has been corrupted, and it's in an inconsistent state. The following validation errors happened:

Database is mandatory on UserMailbox

Any step-by-step guide on how to resolve this would be much appreciated. Although it's affect on the program seems to be negligable as far as we can tell.

Kind Regards

Richard



Resource mailboxes and contacts move during transition to Exchange 2013?

$
0
0

Hello,

I have not found much information about moving Resource mailboxes and Contacts to Exchange 2013 (from Exchange 2007 or 2010).

How this is done? There is nothing in EAC. Is that done by using EMS with New-MoveRequest?

Or do we have to create those from scratch?

-RJ

X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException can't access 2007 mailbox from 2013 server

$
0
0

This one is driving me absolutely crazy,  hours and hours spent on this with no luck.  This is 2007/2013 env.  The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server.  yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302.  Yes, I've ruled out 2007 servers, it's 2013.  If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears.  Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything.  Yes, I've rebooted servers.  Yes this happens with multiple mailboxes.

In fact I have this example right now makes no sense.  I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors.  I'd love to hear suggestions.. I'm at the end of my rope

 

default certificate update

$
0
0

Exchange 2013 CU6

When i first setup my 2013 servers, it looks like exchange went to my internal CA for each exchange server and got a cert for its self.

On the mailbox servers the cert has its self set for IMAP,POP,IIS,SMTP and it doesn't really appear to be editable.

On the cas servers this cert seems to have IMAP,POP,SMTP and it doesn't look like i can unselect those services.

These certs are going to expire soon and im not sure how to go about renewing/replacing them... since it looks a little different then doing the cert for OWA/ActiveSync.

Any help would be great.

Thanks


Systems Administrator

Exchange Server 2013 Database Content Index Status = Failed

$
0
0

Hi

I have a Exchange 2010 SP3 Server where I have about 70 Users. I have recently rolled up a Exchange 2013 SP1, Initial configuration went fine. I am able to see both Exchange Server from the 2013 EAC. I done 2 Mailbox move which completed successfully. During the 3rd mailbox move I noticed that the batch was stuck for a while. I looked at the Event and found that All database content index was showing Failed.

I followed Microsoft recommendation and created a Contentsubmitter security group and gave the networkservice and administrator full permission. then stopped the MSExchange search service and search service host controller, deleted the index file and started the services, the mailbox content index status went from unknown to crawling and then back to failed again. The setup is a non DAG setup so I am unable to sync from another good copy. I have made sure all the services are up and running . Several restart has been carried out aswell. but nothing seem to be working.

Any thing else I can try?


I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

$
0
0
I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

$
0
0
I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

owa redirecting to wrong URL in 2013 / 2007 coexistence

$
0
0

Hello,

I'm trying to get Exchange 2007 and 2013 CU6 to live in harmony for a transition period until we get fully migrated to 2013.  I need to get it to where the end users will experience NO disruption in either on or off presence Outlook, ActiveSync and OWA.

I'm having an issue during the test using a modified HOSTS file before changing DNS.

An existing fleet of mobile devices and users already know the url webm.domain.com for OWA/Activesync.  So this needs to remain the same.  Issue is when I change my hosts file so that this URL points to the NEW Exchange 2013 server, If I log on with my account which has a mailbox on the OLD 2007 server, the redirection is NOT working properly.  Instead of redirecting to https://legacy.domain.com/OWA (which I DO have an Internal AND External DNS pointed to the appropriate IP of the 2007 server) ... It is redirecting to https://www.webm.domain.com/owa/auth/owaauth.dll.

First of all, the site is webm.domain.com.

Second, the redirection is adding a www. in front of the original URL after submitting the username and password.

Third, the redirection is wrong.  Shouldn't it be passing those credentials to https://legacy.domain.com?

Where should I be checking for this?  I did not see www. in front of any urls in the virtual directory pointers.

Thank you!

Exchange 2003 to Exchange 2013

$
0
0

Instead of going from Exchange 2003 to 2010 to 2013. I have decided to remove Exchange 2003 from the organization and install 2013 since I don't have too many users.

I have removed Exchange 2003 from the Organization (http://tutorial.programming4.us/windows_server/Removing-an-Exchange-Server-2003-Server-from-an-Organization.aspx).

When I install Exchange 2013, it doesn't ask me for the organization name. Is it using the data that was left in Active Directory from Exchange 2003? I ran the setup to uninstall Exchange 2003, doesn't that remove the Exchange 2003 data in Active Directory as well?

Thanks


Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

$
0
0

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)



Viewing all 7008 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>