Quantcast
Viewing all 7008 articles
Browse latest View live
↧

Exchange 2007 to 2013 migration - Edge Transport question

February 22, 2016, 2:43 am
$
0
0

Hi,

I'm currently planning out an Exchange 2013 migration from an existing 2007 environment. The current environment has 2 Edge 2007 servers with edge subscriptions in place.

After I have installed 2013 MBX+CAS and then installed the Edge Transport servers the Exchange Deployment Assistant talks about creating new Edge Subscriptions to the 2013 Edge and the 2013 MBX+CAS boxes. If I do this will this have any effect on current email routing? Will this cause outbound email to start going out via the 2013 Edge Servers?

I'm thinking it probably wont unless the user has a mailbox on 2013 but I'm not 100% sure as I haven't encountered this before and would like to know so I can plan whether to do this activity during a downtime window so as not to disrupt mail flow.

Thanks

↧
Search

Exchange 2013 CU12 breaks OWA

April 14, 2016, 5:40 am
$
0
0

Hello,

We have 4 Exchange 2013 servers running Windows Server 2012 R2

I have upgraded all of the servers from Exchange 2013 CU11 to CU12 this week, and also installed the latest Windows updates.

I have found that OWA no longer works following the install of CU12 on all servers.

As per any CU install I always run the "UpdateCAS.ps1" script following the installation on all servers, and also the"UpdateConfigFiles.ps1" script. This has not fixed the problem.

I can navigate to the following URL on all servers https://localhost/owa and be presented with the OWA logon page, however once I have entered my credentials and hit enter I get the following response:

"HTTP 400 Bad Request - The webpage cannot be found"

This is the same from Windows client machines - tested with IE11, Chrome and Firefox browsers.

If I access OWA from Chrome on my android phone, I can log in to OWA without issue, and I receive the OWA "light" interface - which is normal.

Has anyone else seen this issue since upgrading to CU12?

Regards

Matt

Matt

↧
↧

Public Folder Connection Limits (mapi)

March 30, 2016, 4:09 am
$
0
0

I've migrated the public folders from exchange 2010 to exchange 2013 and I'm using the newer mapi connection method for outlook clients but now I get this error message

"Cannot display the folder. You server administrator has limited the number of your items open simultaneously...."

and also I see this error on the exchange server, event ID 9646

"Mapi session /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=xxx with client type MoMT exceeded the maximum of 32 objects of type Session"

how can I fix this?

↧

Introducing Exchange 2013 into 2010 Org for Hybrid

April 14, 2016, 2:04 pm
$
0
0

Hello,

I would like to clarify the guidance detailed in the Exchange Server Deployment assistant.  If selecting the scenario "I currently have an Exchange 2010 deployment but would like to implement Exchange 2013 Hybrid" the resulting configuration details namespaces to apply to the Exchange 2013 servers.  The example namespace is hybrid.contoso.com.

I have customers referring to this documentation and believe that there is a requirement for a "hybrid namespace".  My understanding is that while you could deploy with a hybrid namespace this is not best practice and should not be implemented. 

Is anyone aware of documentation which states that you should implement Exchange 2013 and move your Exchange 2010 internet facing namespace to the 2013 servers, and not create an additional namespace for hybrid purposes?

This is an extract from the deployment assistant, it mentions hybrid.contoso.com.  Surely this should be mail.contoso.com? or the internet facing namespace of the 2010 servers?

(On the Configure external access domain page, enter the externally accessible FQDN of your Exchange 2013 Client Access servers in theEnter the domain name you will use with your external Client Access servers text box. For example, hybrid.contoso.com.)

In the prepare for deployment section of the deployment assistant the following namespaces are displayed:

External Exchange 2010 server FQDN

mail.contoso.com

 

External Exchange 2013 server FQDN

hybrid.contoso.com

Can anyone explain why the deployment assistant is advising these namespaces should be implemented.  All of the technet documentation states autodiscover, EWS, OWA etc should be pointing at the most recent version, which in this scenario is 2013.

Many Thanks

J



↧

Question on Exchange 2013 Configuration

October 30, 2015, 9:58 am
$
0
0

I am looking for some feedback on whether this is the correct setup for Exchange 2013. Current setup with Exchange 2010 is ....

Site A

2 Cas Servers (in casarray)

2 mbox Server (in DAG to Site B)

Site B

2 Cas Servers (in casarray)

2 mbox Servers (in DAG to Site A)

Moving to Exchange 2013, this is what the plan is ...

3 Servers in each location

Site A

2 Servers with CAS and MBOX Role (with DAG to Site B)

1 Server with just CAS role for redundancy (not sure if this is needed?)

Site B

2 Servers with CAS and MBOX Role (with DAG to Site A)

1 Server with just CAS role for redundancy ( not sure if this is needed?)

Does this sounds like a good solution or is the 3rd CAS server not necessary?

Any feedback would be great.

Thanks,

Gavin

↧
↧

Windows Server 2012 R2 with Exchange Server 2013 SP1 Completely fresh install giving errors signing into EAC

May 29, 2014, 2:55 pm
$
0
0

Hi,

I am struggling with a completely clean installation of Server 2012 R2 and Exchange 2013 SP1.  I followed these steps:

  • Installed Server OS
  • Windows Updates
  • Added Active Directory Role (This is a single standalone server that would have been SBS until it was dropped)
  • Added DHCP & DNS
  • Added Certificate Services
  • Added Windows Server Update Services (WID Database & WSUS Services)
  • Windows Updates
  • Added Media Foundation
  • Added File Server Resource Manager and Work Folders
  • Added Windows Server Backup
  • Windows Updates
  • Checked all running without errors in Server Manager and performed a full bare bones backup.
  • Ran Setup.exe from Exchange 2013 SP1 disc.
  • Installed Pre-requisites and then rebooted
  • Windows Updates
  • Ran Setup.exe from Exchange 2013 SP1 disc.
  • Installation completed without errors
  • Rebooted
  • Checked all running without errors in Server Manager.

I Launch Exchange Administrative Center and get "problem with website's server certificate error" (normal on machine with self-assigned certificates).  Click Continue to Website and get:

Windows Security dialog box:

iexplore - "The server localhost is asking for your username and password.  The server reports that it is from Digest"

however no username and password combination will work:  have tried [Administrator]; [Domain\Administrator] even created a user to no avail.

I believe the issue is somewhere in the IIS configuration because I also get the same error when trying to log into the server website from either the server or another machine on the network.

I have tried the complete installation three times now:  (full disclosure not all of the same features/roles each time).  On the first attempt I got this error immediately and on try number 2 was able to get into the EAC and created the mailboxes but then it started giving the same error.  The above steps are try number 3.

Any ideas?

Thanks in advance.

Andy Halford


P.S. A Follow up which might be significant:  The Default Web Site is not running and will not start (it was previously running before the Exchange installation) and when I try I get the message that Another Website may be using the same port however none of the others (Exchange Back End or WSUS Administration) are using ports 80 or 443 and I still get the error when they are both stopped.
↧

Can't access migrated public folder from a single user

April 7, 2016, 3:43 am
$
0
0

Hello,

I've succesfully migrated all mailboxes and legacypublicfolders to new pfmailbox from Exchange 2003 to 2010 and then to Exchange 2013, and removed the old servers. All is now on a single Exchange 2013 server.

All seem's to work for all users except for a single user, who can access his personal mailbox but cannot access public folder hierarchy.

I've recreated the Outlook profile on his pc and tried a completly new profile on another pc, but it's impossibile for him to access the pf hierarchy on the Exchange 2013.

Via the Outlook Test Automatic Config and looking in the mailbox properties via get-mailbox cmdlet, I've seen that ONLY this user still has the old ExchangeGuid 4f34f807-37e0-401a-901d-8a6af0436f86@.....it  instead of the new one.

Probably that was the ExchangeGuid of the intermediate Exchange 2010 server that doesn't exists anymore...

What can I do?

Albey

↧

Mailbox Move: Version error with 2010 SP3 and 2013 CU1

April 6, 2013, 4:06 am
$
0
0

Hey there

I have a Small Business Server 2011 with Exchange 2010 SP3 installed. As with the release of Exchange Server 2013 CU1 I want to migrate to 2013. I am following a technet blog post (http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx) to migrate Cross Org and Cross Forest. This is what I do:

Prepare-MoveRequest: works like a charm, user gets created in target forest and shows up in 2013 Mailbox Migration Console ("Migrate to this forest") in ECP.

Second I try to migrate the mailbox:

New-MoveRequest -Identity "DN or UPN of User in Target Forest" -RemoteLegacy -TargetDatabase "Mailbox Database Name" -RemoteGlobalCatalog"FQDN of Source DC" -RemoteCredential $remote -TargetDeliveryDomain "Target domain name"

The output is the following:

RemoteLegacy moves must involve Exchange 2010 or lower versions only.

I understand that this used to happen without SP3 and CU1, but why would I still get this message after upgrading? I also tried to move the mailbox from the other side (legacy exchange server):

New-MoveRequest -Identity "UPN" -Outbound -Remotehostname "TargetMailServer" -RemoteTargetDatabase "DB"  -RemoteCredential $remote -TargetDeliverydomain "domain"

Output is the following:

The remote server doesn't support client 'legacy exchange fqdn' version (14.3.123.2 caps:05FEFF). Missing functionality: 'TenantHint'.

This confuses me. SP3 should be 14.3.123.4 (which is the version for all server roles in EMC).

Any idea why this happens?




↧
Search

Installation without schema update

April 14, 2016, 6:56 pm
$
0
0

Hi All ,

 In our exchange orgrazination we have exchange 2010 sp3 in one AD site and We are planning to install Exchange 2013 in another AD site.

My question is:
I don't want to extend Schema. Please let me know without extending schema how can i proceed the installation and which account group my account needs to be member ?

 
↧
↧

Powershell Export-CSV Access to the path \\servername\sharename is Denied

November 21, 2013, 7:21 am
$
0
0

Hi I'm new to PowerShell and I've been attempting to migrate an Exchange 2010 SP3 Public folder to Exchange 2013. I'm following the directions found athttp://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx .

I have gotten to Step 3 .\Export-PublicFolderStatistics.ps1 <Folder to size map path> <FQDN of source server>

It runs the command but when it attempts to write the CSV to the drive I get:

Export-csv : Access to the path '\\servername\sharename' is denied

I am running the Exchange PowerShell in Administrator mode

Within File Manager I have given:

the share Everyone Full permissions

NTFS Full permissions to:

Everyone, Domain Admins, Domain Users, Exchange Servers, Exchange Organization Admins,

PS] C:\Windows\system32>C:\ps_scripts\Export-PublicFolderStatistics.ps1 "\\server\sharename" server.domain.local
[11/21/2013 9:59:42 AM] Enumerating folders under NON_IPM_SUBTREE...
[11/21/2013 9:59:50 AM] Enumerating folders under NON_IPM_SUBTREE completed...25 folders found.
[11/21/2013 9:59:51 AM] Retrieving statistics from server SERVER
[11/21/2013 9:59:52 AM] Retrieving statistics from server SERVER complete...45 folders found.
[11/21/2013 9:59:52 AM] Total unique folders found : 45.
[11/21/2013 9:59:52 AM] Exporting statistics for 45 folders
[11/21/2013 9:59:52 AM] Exporting folders to a CSV file
Export-CSV : Access to the path '\server\sharename' is denied.
At C:\ps_scripts\Export-PublicFolderStatistics.ps1:221 char:70
+ $script:ExportFolders | Sort-Object -Property FolderName | Export-CSV <<<<  -Path $ExportFile -Force -NoTypeInformati
on -Encoding "Unicode";
    + CategoryInfo          : OpenError: (:) [Export-Csv], UnauthorizedAccessException
    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.ExportCsvCommand

[PS] C:\Windows\system32>

  

↧

Exchange 2010 Shema Removal

March 8, 2016, 5:10 pm
$
0
0

Hi,

I installed Exchange Server 2010 on Windows server 2012 Essentials.  I demoted the 2012 server and made it a member server to the Domain Controller, Windows 2012 and Installed Exchange 2010.  I prepared and did the pre-requirements and the schema was updated.

After the install of Ex2010 I installed service pack 3 and that's when everything went to hell.  The Exchange Management shell would initialize and open and I can see the roles.  I just can't expand the roles.  I researched some of the things suggested and didn't work.

Trying to fix the problem solved nothing and the server became slow, almost unstable.  I tried to use the recover switch and didn't fix nothing.  So I decided, if this doesn't work then I will uninstall Exchange 2010 and start over.  There was error, said there was a mailbox in the database.

I found the tech article to remove the mailbox. Turns out there was two of them. I was able to delete one, but not the other one. I tried to figure out why, but was unsuccessful.

I ended up using the restore to default factory on the server as the last resort.  I forgot about the schema and it's still in the domain controller.  I did try to install Exchange 2013 and I get an error that tells me to remove the 2010 exchange server.

So how do I fix this on a live production server to remove the Schema.  The DC servers only purpose is for file storage and user authorization and 1 program that looks at a flat database file for the software that runs on the clients computers.  Only 3 computers have access to this flat database file.

Please help.  I know I might be missing some information that you may need to know.  Just ask, I hope what I explained helps.

↧

winmail.dat, PDF files are not delived.

April 11, 2016, 2:58 am
$
0
0

Dear All,

I've  Exchange 2013 on Windows 2012 server  and external internet users have been reporting that attachments they receive from internal users are showing only as winmail.dat .

When I use this command "Set-RemoteDomain -Identity * -TNEFEnabled $false" , it solved my issue with the winmail.dat sending with attachments and PDF files etc delivered.

However, once this was enabled we were having delivery failure notifications and having large number of emails (going to external users) that would get stuck in the submission queue.  I had to enter following command "Set-RemoteDomain -Identity * -TNEFEnabled $true" to solve the problem and winmail.dat issue came back and attachments were not delivered.

When users report attachment winmail.dat issue, I have to create new remote domain and specify -TNEFEnabled $false everytime like below for the failed domains (They are usually non Microsoft clients, I think).

New-RemoteDomain -Name xxxx -DomainName xxxx.com

Set-RemoteDomain -Identity xxxx -TNEFEnabled $False

Setting client`s Outlook mail format to Plain Text or HTML doesn`t help.

I don`t mind create every time but users have to experience this issue and then I can add remote domain and solve the issue but it is creating inconvenience. Do you have any permanent solution for this problem?

Kind regards,

Itech



↧

What is the meaning of 'The long running job has been temporarily postponed. It will be retried again when resources become available.'

April 8, 2016, 12:39 am
$
0
0

Hello,

We are migrating from Exchange 2010 to 2013.

During the night we get sometimes the message ''The long running job has been temporarily postponed. It will be retried again when resources become available' in the migration report.

This is usually done for all move-requests on a server.

After that message the move-requests continue, but at a very slow speed.  suspending/resuming the move-requests, Set-moverequest -priority high does not help, neither a restart of the MRS.  If we suspend, fail-over to a passive node and back, resume, then the migrations continue at normal speed.

When this happens there is nothing special (backup, maintenance, ...) on the server.

How can this be debugged further?

Herman Van Uytven


↧
↧

Exchange 2013 Server Readiness Checklist

April 18, 2016, 3:12 am
$
0
0

Hi, Guys.

Need your assistance on this.

Do you have any documentation/checklist to be checked against an Exchange 2013 server before you manage/administer or put it in production? Please advise.

Thank you.

↧

Exchange 2010 Hybrid Migration

April 18, 2016, 10:04 pm
$
0
0

Hi All,

In my organization have single forest with one child domain. Forest root domain has Exchange 2013 configured with Hybrid on 0365 with ADFS proxy, ADFS and DirSync and is working fine without any issue.

In my child domain have single Exchange 2010 which I want to move all my mailboxes in 0365 Hybrid scenario.

Kindly guide the process and the best practices to adopt for smooth migration of my child domain users to 0365.

Thanks

↧
Search

Exchange 2013

April 19, 2016, 2:46 am
$
0
0

Hi,

Just have a quick question:

We have a 2013 DAG environment, with a 2010 Edge transport server.  Now we are installing a 2013 SP1 edge server to replace this 2010 version.  Atm we are at the step of creating the subscription for this 2013 server, however we have no idea what the impact will be of the working 2010 server. anyone who has experience with this migration/upgrade?

1) creating a new subscription-  will this new subscription will be visible as a second Edgesync - default-first-name to internet? (since there is already an active 2010 in our environment).  what will actually happen when we do this step?

2) can this be created/configured together with the existing subscription without impact/downtime ?

Some help would be appreciated.

greetings

↧

Unable to migrate some users - 2007 to 2013

April 19, 2016, 7:05 am
$
0
0

Got a few users who just won;t migrate.

Create migration batch, it runs for a while and then says 0 mailboxes. It seems there must be some sort of flag on the mailbox.

There are no outstanding move requests - cleared all of these.

I guess there is something in a log file somwehere that can help with this?

↧
↧

Outlook disconnected after mailbox migration

April 19, 2016, 9:20 am
$
0
0
Hi,

I found lot of resources but not exactly for my problems.
I hope you can help me !
I translated all errors messages from french for you.

I moved 300 mailbox from Exchange 2007, only for internal use (no internet usage), to Exchange 2013 CU 11.
The first batch (180 accounts only OWA-users, to the first database) finished with no errors. I can open their mailboxes with OWA 2013.
The second batch (70 accounts some outlook-users, to the second database) finished with no errors. I cannot open their mailboxes with OWA neither with outlook.

For the second batch :

- In OWA, i get the error 500  try again in 30 sec and sometime the mailbox open successufly for 5 minutes, and after i get the errorMicrosoft.Exchange.Data.Storage.NotSupportedWithServerVersionException

- In Outlook 2007 or 2013, i get the message your administrator has made a change and requires you to restart outlook as expected, but infinite times. If i create a new mail-profile (config pannel>mail), so outlook don't open and shows the errorYou must connect with the current profile before you can synchronize your folders with your outlook data file (.ost) (2013) or...your offline folder file (2007).

In powershell exchange 2013, Get-Mailbox | Get-MailboxStatistics shows the warningThe user hasn’t logged on to mailbox so there is no data to return. After the user logs on, this longer appear for all users from the second batch. I get the same warning on ECP > mailboxes > the user > usage.

So i tried to move their mailbox again from exchange 2013, but a get the error The mailbox of user that is located on a server that is running version 8 can't be opened on a server that is running version 15 orthe mailbox is in not in the expected mailbox database.

At this point, sometimes, Get-Mailbox -database <second> returns nothing (-database <first> is ok), causeGet-Mailbox <user.from.second.db> | select servername,database returns the name of the original Exchange 2007 and database before migration.

The same cmdlet on Exchange 2007 shows the mailbox in Exchange 2013 and the target database as expected after migration.

ECP (2013) shows the same as Exchange 2007, not 2013... iisreset temporary resolve the problem : mailboxes are in Exchange 2013...

I haven't decommissioned Exchange 2007 because i have 150 account left (they are working successfully), and i'm afraid to migrate them.

Exchange 2007 are in Windows Server 2003 x64.
Exchange 2013 are in Windows Server 2012 R2 x64 (french).
Domain are Windows 2003 level.
No error in eventlog (exchange, DC).

What can i do ? Thank you.
↧

Setting up Exchange/Keeping current Domain name

April 19, 2016, 12:06 pm
$
0
0

Hello,

I need a little clarification as I have been given the run-around with Microsoft information line.

We are looking to change our email server from a POP server to Microsoft Exchange. I know Exchange has the ability to migrate emails and keep the domain name. They are telling me I have to go through a field partner and pay thousands of dollars for this to happen. I am pretty computer literate, and I think I could do this work on my own. Is this something anyone has done before? Migrating, keeping domain name, and setting up our business emails on the Exchange server?

Any guidance or help would be greatly appreciated!

Thanks,

Sarah

↧

Recommended ports to open for Exchange 2013

April 19, 2016, 12:30 pm
$
0
0

Hi,

What are the recommend ports to open for Exchange server 2013

Regards,

Tarek

↧
Viewing all 7008 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>