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

Import Address List into Ex2013?

$
0
0

We're doing a cross-forest Ex2010->Ex2013 migration. The Ex2010 environment has some old, Ex2003 legacy Address lists that were never converted to the new OPATH format. They want the address lists in the Ex2013 Org, preferably as separate lists like they have today. For example, they have a few lists such as Miami and Chicago.

How can I get those old lists into the new Ex2013 Forest? I don't see any way to import an Address List in Ex2013.

Thanks!


Test Outlook connection to 2013 prior to Co-Existence

$
0
0

I'm trying to find out if there is a way to test Outlook (2010) connectivity to Exchange 2013 prior to moving to a co-existence state.  OWA tests out great, all certs are in and VD's/Outlook anywhere is configured on the 2013 system (NTLM authentication). I have configured the local machines hosts file to point to the autodiscover address of my 2013 CAS server.  I can communicate to the autodiscover service properly through IE receiving ErrorCode 600.  

I changed the SCP of my 2013 CAS Server to https://autodiscover.domain.com/autodiscover/autodiscover.xml - doing so did not allow outlook to connect - I received a prompt for credentials as well as error: outlook is unable to connect to the proxy server. (error code 0).  Entering credentials didn't work.

I've since changed the SCP to point to that of the 2007 Exchange server as users we're complaining they couldn't connect.

I've tried multiple avenues of manually setting up outlook with no success.  Outlook seems to be getting some settings properly as after I cancel the authentication prompt it shows me the GUID@domain.org as the exchange server its attempting to connect to.  

Further information:

Single 2007 SP3 Rollup 11 Exchange server, Server 2003 R2

Single 2013 SP1 CAS, Server 2012 R2 (fully updated 2 weeks ago)

Single 2013 SP1 MBX, Server 2012 R2 (fully updated 2 weeks ago)

Outlook 2010 SP2

Thank you.

 

Exchange 2013 Multi-Tenant and intern OOF.

$
0
0
Hi, 

I've build a Multi-tenant Exchange 2013 environment, which is working fine. But I'm still curious how everyone handles the internal OOF messages between two tenants. I read the the "Multi-Tenancy and Hosting Guidance for Exchange Server 2013". Microsoft says this about (internal) OOF:

"A more performance impacting solution would be to create multiple transport rules using groups to control the deletion of the OOF messages. Again, this means no OOF messages are delivered between tenants on the same system."

I was wondering, maybe there's a better solution?


missing server in AD

$
0
0
I appear to be missing cn=servers from my active directory for exchange causing exchange not to load. Is there any way to recreate this?

Issue with proxy settings and autodiscover

$
0
0

To give you the scenario; I have separate CAS and MBX servers for Exchange 2013. I am also using ISA 2004. The majority of my users are on Exchange 2007 still waiting to be migrated. I have tested with a couple of email accounts and have encountered a problem with Autodiscover internally. Externally, it is working fine. I have an internal address of CAS01.mycompany1.local and an external address of mail.mycompany.com.

I have discovered that Outlook needs to have the HTTP proxy set, pointing to mail.mycompany.com. If it isn't I get the error: "There is a problem with the proxy servers security certificate. The name on the certificate is invalid or does not match the name of the target site mail.mycompany.com. Outlook is unable to connect to the proxy server. (Error Code 0)." It also constantly prompts for credentials. If I cancel the credentials request, it then resolves to the GUID of the user for the Microsoft Exchange Server field and sets the mailbox to =SMTP:username@mycompany.com. I then have to cancel this and "manually configure the server settings". I choose Microsoft Exchange, click on more settings, go to the connection tab and under Outlook Anywhere, tick the "Connect to Microsoft Exchange using HTTP" and then click on "Exchange Proxy Settings". In the Connection settings, I then have to set the URL to http:// mail.mycompany.com. It then works.

Whilst I know this is not the cleanest way for this to operate, it is acceptable if I can get autodiscover to set the proxy settings automatically. I cannot expect users to manually set this.

Because ISA 2004 does not understand NTLM, I have set all the security to basic. I have also tried setting the Internal and External Hostname to mail.mycompany.com. With the internal set to CAS01.mycompany1.local it makes no difference. I can resolve the internal name and external name using nslookup. autodiscover is set to point to the CAS. The certprinciplename is set to *.mycompany.com (we are using a wildcard certificate) for both EXPR and EXCH. There is a certificate set on the CAS from our internal CA with CAS01.mycompany1.local as the primary name and then our other domains set as SAN's.

I am now out of ideas on getting this working. In an ideal world, outlook would just point directly to the CAS and pickup the settings. I find it strange how it can resolve the mailbox guid but then cannot connect. It suggests that there is some problem with authentication. Any ideas on how to resolve this would be appreciated. Thanks in advance.

Anti malware / anti spam / virus protection

$
0
0

Greetings,

With the introduce of Exchange Server 2013 along with its architecture, Microsoft has moved Transport services / roles to Mailbox Server Role. well, when it comes to anti malware / anti spam and viruses , Microsoft recommends deploying them on Mailbox Server role, while on CAS, not necessarily be deployed as long as messages are not inspected on CAS Servers.

While some articles say the opposite, and mention configuration of Anti malware ,etc.. on CAS Servers.

What is the best practice for deploying anti malware / spam / virus  Software on CAS, and what is the best recommended software for messaging and OS level protection, say Symantec for example.

Thanking you

Jamil

send and receive connector

$
0
0

Hi Everyone, I have 2 send connectors and 4 receive connectors configured on exchange server 2007.How do i know which send or receive connector i am using for my exchange 2007.I am doing the transition to exchange server 2013. If i  create a new send and receive connector in exchange 2013 without looking back to exchange 2007 will i face any issue.Do guide me how to create it in exchange 2013.

Exchange 2013 Two Questions

$
0
0

I have two quick questions in regards to Exchange 2013

1) Is it possible to do an in-place upgrade from Exchange 2010 to Exchange 2013? I know the recommended way is a co-existence scenario, but what if that is not an option. This would be in a single Exchange 2010 environment for example

(1 server Domain/FP, one server Exchange)

2) is it possible to integrate the latest CU update for Exchange 2013, so that the install is fully up to date, there by reducing the time to deploy?


Office 365/Exchange PST Capture Tool not finding mailboxes

$
0
0

I am trying to use this utility to move the emails/contacts/etc. in some of my local PST files into an email account on Exchange Online (the cloud) through Office 365.

I have set up the "Online Connection Settings" and have connected successfully using the "check" button to my Office 365 global administrative account.

Next I added my PST file using the  "Add from Folder..." button.

The problem is that when I click on "Set mailbox..."( to direct the emails/contacts/etc. to be added to the correct email address in my company) the list never loads, it simply says "The Central Service is retrieving the mailbox data, try again in a moment".

It has been like this for several hours and shows no signs of change.

I need to be able to load .pst files from my old domain into the exchange cloud and NEVER USE THEM AGAIN. This means actually importing the emails, not just adding the .pst file to Outlook.

Please advise why the tool cannot find my company's email addresses and how to fix.

-Joe

P.S: I have already posted this in the Office 365 forums, they gave me the "not officially supported" nonsense and sent me here.



configure OAB

$
0
0

As i am doing transition from Exchange 2007 to Exchange 2013, i am not able to configure OAB

ON my EXchange 2013 i ran the following powershell commands


[PS] C:\Windows\system32>Get-OfflineAddressBook

Name                                    Versions                                AddressLists
----                                    --------                                ------------
Default Offline Address List            {Version2, Version3, Version4}          {\Default Global Address List}
Default Offline Address List (Ex2013)   {Version4}                              {\Default Global Address List}


[PS] C:\Windows\system32>Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address List (Ex2013)"


On my Exchange 2007 Server i am trying move OAB but i am getting error( mail is my exchange 2007, mail1 is my exchange 2013)


[PS] C:\Users\Administrator\Desktop>Move-OfflineAddressBook -Identity "Default offline Address List" -Server mail1

Confirm
Are you sure you want to perform this action?
Moving Offline Address Book "Default offline Address List" to Server "mail1".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): Y
Move-OfflineAddressBook : Failed to create the 'ExchangeOAB' folder on the target server 'MAIL1'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform this operation. Error message : 'Catastrophic failure (Exception from HRESULT: 0x8000FFFF
 (E_UNEXPECTED))'.
At line:1 char:24
+ Move-OfflineAddressBook <<<<  -Identity "Default offline Address List" -Server mail1
    + CategoryInfo          : InvalidResult: (Default offline Address List:OfflineAddressBookIdParameter) [Move-OfflineAddressBook], LocalizedException
    + FullyQualifiedErrorId : BC0D046F,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveOfflineAddressBook

all my exchange services are up and running.and then i used the below three commands in exchange 2007 and tried to move OAB but still same error



[PS] C:\Users\Administrator\Desktop>Get-MailboxDatabase | Where {$_.OfflineAddressBook -eq $Null} | FT Name,OfflineAddressBook -AutoSize
[PS] C:\Users\Administrator\Desktop>Get-MailboxDatabase | Where {$_.OfflineAddressBook -eq $Null} | Set-MailboxDatabase -OfflineAddressBook (Get-OfflineAddressBook | Where {$_.IsDefault -eq $True})

[PS] Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "Default Offline Address List"
The command completed successfully but no settings of 'MAIL\First Storage Group\Mailbox Database' have been modified'

PS] C:\Users\Administrator\Desktop>Move-OfflineAddressBook -Identity "Default offline Address List" -Server mail1
same error as above










Exchange and UAG service pack compatibility

$
0
0

(this relates to Exchange 2010, but could not find the forum for that version)

We are currently on Exchange 2010 SP2 and UAG 2010 SP1.  I want to upgrade Exchange to SP3, and later on UAG to SP4, but not all at the same time due to scheduling.  Ideally we'd like to do Exchange first, then a week later update UAG.  Will Exchange 2010 SP3 be supported (function) on UAG SP1?  Should we update UAG to SP4 first, then later update Exchange 2010 to SP3 later?

Migrating from Exchange 2003 to 2013

$
0
0

I know there isn't a migration path for Exchange 2003 but has anyone tried any type of work around?  I'm thinking about moving one of my customers users mailboxes to PST files and them importing them into Exchange 2013 on a 2012 server.  Has anyone had any experience doing this?  Below are the details of what I have and what I was thinking about doing:

Small Network - approx. 10 users

Server 2003 Sp3 standalone AD DC with Exchange 2003

Would like to move straight to Server 2012 with Exchange 2013

If I export the mailboxes and uninstall Exchange from the 2003 server will Server 2012 join the domain and upgrade the existing AD schema (forest and domain)?  If it would, could I then install Exchange 2013 on that server, create the mailboxes for the users and import the PST files?

Just wondering if anyone has tried this, or something similar.  They don't have an extra server to move everything to 2010 first so it's either a workaround or move them to Exchange 2010 (which Microsoft has quit selling).  I'm sure this will put a lot of small business VARs in a bad situation. 

(Just as a side note) Is it true that Dell and HP have quit selling Windows 7 Pro? My vendor still sells it and will for 18 more months.

Exchange 2013 P2V VMM 2012

$
0
0

Hello,

I have a single server Exchange 2013 installation on Windows Server 2012.  I need to virtualize this server onto new hardware using Hyper-V and VMM.  Could someone please give me guidance as too the best way to accomplish this.  Somewhere I am doing something wrong.  I tried Disk2VHD but when I created a new VM and added this vhd the virtual machine would not start.  When trying both online and offline P2V within VMM the process fails along the way.

Someone please point me in the right direction as I am under the gun to get this migration done.

Your help is greatly appreciated.

Thanks,

Kevin

Error Preparing Schema for Exchange 2013

$
0
0

I recive this error when running the preparing AD for exchange 2013 on a 2012 r2 server. 

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 a user with the identity "ESL.LOC/Users/Exchange Online-ApplicationAccount".".

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 a user with the identity "ESL.LOC/Users/Exchange Online-ApplicationAccount".".

Design question regarding Exchange 2013 in a hybrid configuration with Office 365 and partner integration for emails and extranet

$
0
0

I hope this is the right forum to ask this design question.  We are currently running Exchange 2007 and looking to migrate to Exchange 2013 in a hybrid approach so we can also leverage Office 365 for some mailboxes.

In the near future we want to setup some type of new email and sharepoint infrastructure for our partners (600+ users) to use and of course single sign on for all other services that we may provide.  There's nothing in place for them as of now.

Internally, we are a single forest 2008R2 mode (2012 in the near future), with multiple child domains. 

Should we setup another child domain for the partner accounts or should we setup a totally separate forest. ADFS?

Ideally, we would like to put all the partner mailboxes/sharepoint access in O365 but have a single pane of glass to manage both partner mailboxes/sharepoint and our corporate users that we decide to migrate to O365. 

Are there any design guides, case studies out there from MS that kind of touches base on what I'm asking.  Thanks for any feedback.

Dan


hardware setup with JBOD

$
0
0

My servers and direct attach storage hardware have arrived, the first server is setup and attached to the DAS but how do I setup JBOD, I see the drives in Open Manager but I can only use RAID 0 their, I see them in the server startup H810 adapter utility but how do I set them up as JBOD? I want to take advantage of the new Exchange 2013 features that can automatically recover a failed drive.

Installed Exchange 2010 Service Pack 3 Roll Up4 but Management console end up with different versions?

$
0
0

Hi,

We installed Exchange 2010 Service Pack 3 update roll up 4 in our two CAS servers using the same installers.  Both were at the same version prior to changes: 14.02.0318.001.  However, after  installation of SP3 + Rollup4, one CAS server ends up with version 14.03.0174.001, while the other one had 14.03.0123.003. 

I see this version when I open Exchange management console --> About Exchange.  But if I use the command: Get-Exchangeserver | fl name,edition,admindisplayversion both servers get same version like below:

Edition             : Enterprise
AdminDisplayVersion : Version 14.3 (Build 123.4)

Should I be concerned that on the management console they are slightly off versions? And can anyone explain to me why they end up in different versions but if I use the command line, they appear to be the same?

Thanks!

old user can still access mailbox after removing msexch-masteraccountsid

$
0
0

Hi,

I've changed the user mailbox and user by running the following command on the linked mailbox

Set-User -Identity "alias" -LinkedMasterAccount $null

Issue is that the previous user (the msexchmasteraccount) still has access, and yes, that user is still enabled. 

My question is - how can I remove that access to the mailbox? The msexchmasteraccount is empty in adsiedit. 





Can not install exchange 2013

$
0
0

Hai

I try to install exchange 2013 but there is a problem showed at below:

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.

Finally I follow it to install the Microsoft Unified Communications Managed API 4.0, but i got error like this:

Microsoft Unified Communications Managed API 4.0, Runtime cannot be installed side by side with the following components. Installation cannot continue.
Microsoft Server Speech Platform Runtime (x64)

I already uninstall the Microsoft server speech, but i still got the same error. 

How can I solve this problem, installing MUCM API 4.0 without error?

Thank you


Exchange 2013 coexistence, outlook fails to connect to new server

$
0
0

Hi all. 

I encounter an issue in my migration from Exchange 2007 to Exchange 2013 server. 

My Exchange 2007 infrastructure is (2007 Server SP3 rollup 12): 

- Server1 : cluster of 2 Exchange 2007 mailbox server nodes

- Server2 : CAS Server

I have a new Exchange 2013 infrastructure : 

- Server 3 and 4 : Multirole servers, configured in a DAG. I use round robin to point to these 2 servers with the mail.domain.org name. I created a self-signed cert with new names. 

Actually, users have mailboxes on Exchange 2007 platform. Everything is working fine. 
Now, I want to migrate users to Exchange 2013. I test my own mailbox. OWA is working fine with https://mail.domain.org/owa, I can send and receive mail. 
But, on a new computer, I cannot create a profile on Outlook with my adress. 
When I do this, I have a cert accept request from the OLD CAS server. I accept. Then, I have another request for the domain.fr. Then, Outlook says that Exchange Server is not reachable and must be online to create profile. 
I cannot go further. 

This is the same result if I manually configure the profile. It's not possible. 

Did someone have this kind of configuration? I'm lost and situation begins to be very critical for the projet. 

Thanks a lot. 

Viewing all 7129 articles
Browse latest View live


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