Adding a new forest to Exchange 2007
Hello,
I currently have an exchange 2007 cluster server (EX01.love.corp) where I can make email addresses for accounts in my Love.corp domain AD. We are going to migrate all the users to the Hate.local domain, as such a domain that is not yet defined in the Exchange
server EX01.
When I try to define a different resource AD i can only see the DC in the love.corp domain. I want to add the Hate.local domain so I can use that AD as a second resource, eventually removing the AD resource from the love.corp domain.
Question: How do I add the DC01.hate.local in the server configuration of the EX01.love.corp (hub transport) Domain controllers and Global catalog servers used by exchange?
thanks,
Robert
Hello,
According to your description, I understand you want to migrate AD users to a new forest(Hate.local）.If so, I consider you can do it. But I'm afraid that you can't specify Ex01 will use DC01.hate.local in the server configuration.
Cara Chen
TechNet Community Support
Similar Messages
-
Exchange 2013 SP1 database missing?? New install of Exchange 2007 co-exist
Hi all,
Finally got Exchange 2013 SP1 installed except I am not so sure I have a database. This is installed on a Server 2008 system and is co-existing with Exchange 2007.
When I go to SERVERS and DATABASES I don't have anything listed. When I click SERVERS on the left hand pane and SERVERS at the top I see both servers, 2007 and 2013. But when I double click my new Exchange Server 2013 name I get the error:
The operation couldn't be performed because object '*\ExchangeServerName' couldn't be found on 'FirstDCName.mydomain.com'
Why would I get this error? The install itself was problematic so I am concerned something is broke.
Thank you in advance.Hello,
Firstly, I recommend you check if the server name "*\ExchangeServerName" exists on DC via ADUC (select Computers).
Secondly, please run the get-exchangeserver | fl name cmdlet to check your exchange server name.
And then please check the exchange setup log to check if the exchange 2013 server is installed successfully. If not, please check if there is any error in setup log.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support -
Intermittent OWA authtication issue for new users on Exchange 2007
Hi
We are experiencing a strange issue with OWA authentication and its happening with new users only including me. We are a small organization with approx. 70 users. Issue is with
new user accounts only.
Access to OWA stops working from any machine for the new users also they get authentication error on their phones. I have checked permissions on Virtual Directory on exchange server,
all seems to be in place. I have checked event viewer but it doesn't have any event for auth. failure.
IIS logs have the following Message,
2014-02-05 09:37:28 W3SVC1 (EXCHANGE SERVER IP) GET /owa/ - 443 myusername 77.88.97.134 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko
401 1 1326
Server details
Server 2003 Ent. x64 R2
Exchange Server 2007 Version: 08.03.0342.000
IIS 6.0
Rebooting the exchange server resolves the issue sometime for 2 days sometime for 3-4 weeks.
Please advise.
Best Regards
PrabhashHi,
According to your description, new users cannot login OWA .
And to narrow down the cause, I recommend the following troubleshooting:
1. Check if the option"User must change password on next login" has been selected for the new users.
2. Check if the new users can login Outlook when the issue happens.
3. Check if it’s configured to use Integrated Windows authentication for OWA web site:
http://support.microsoft.com/kb/871179
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support -
AutoDiscover is a new feature in Exchange 2007, to provide access to Microsoft Exchange features (OAB, Availability service, UM) for Outlook 2007
clients or later.
We can determine whether problems related to AutoDiscover via OWA.
For example:
OOF is not working in Outlook Client but it is working in OWA.
When we realized this issue is not related to Outlook Client side and network side after performing some troubleshooting steps, it should be something
abnormal on AutoDiscover.
There is a common tool to check AutoDiscover in Outlook, Test E-mail AutoConfiguration.
Today, we will introduce AutoDisocver and “Test E-mail AutoConfiguration” in details. Hope it is helpful for AutoDiscover troubleshooting and self-learning.
1. Differences between “Test E-mail AutoConfiguration” and other tools
The “Test-OutlookWebServices” cmdlet allows us to test the functionality of the following services:
Autodisocver
Exchange Web Services
Availability Service
Offline Address Book
When we run “Test-OutlookWebServices”, it returns all the web services’ states.
However, some information are useless for some scenarios.
For example:
We just want our Exchange 2010 Server working internally. So it is unnecessary to enable Outlook Anywhere.
However, when we run “Test-OutlookWebServices”, it returns Outlook Anywhere errors because the Outlook Anywhere does not need to been enabled.
In contrast, using “Test E-mail Autodiscover” is more intuitive.
If there is any problems, it will return error code from the test result, like 0x8004010F etc. We can do some research from TechNet articles or MS
KBs.
Although it is difficult to say where the specific problem is just via the error codes, we can combine with IIS logs to perform troubleshooting and
find the root of problem.
2. How to use “Test E-mail AutoConfiguration” Tool
a. Open Outlook, we can find there is an Outlook Icon at the right bottom of System tray. Holding down “Ctrl” button and right click the Outlook Icon, we will see “Test E-mail
AutoConfiguration” option. Please see Figure 01.
Figure 01
b. Click “Test E-mail AutoCofiguration” and input user name, uncheck the “Use Guessmart” and “Secure Guessmart Authentication” checkboxes, then click “Test”. Please see
Figure 02.
Figure 02
c. “Test E-mail AutoConfiguration” result panel and log panel. Please see Figure 03 and Figure 04.
Figure 03
Figure 04
3. How to understand “Test E-mail AutoConfiguration” result
According to the Figure 03, we found there are many URLs in the “Test E-mail AutoConfiguration” result panel. Let us understand the details of these
URLs.
If we these URLs are not the correct ones, we can re-setting or re-creating them via commands.
- Internal OWA URL:
https://vamwan310.vamwan.com/owa/
OWA internal access.
- External OWA URL:
https://mail.vamwan.com/owa/
OWA external access.
- Availability service URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Free/Busy, OOF and meeting suggestions.
- OOF URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Out of Office access.
- OAB URL:
https://vamwan310.vamwan.com/OAB/023ef307-b18a-4911-a52c-de26700f6173/
OAB access.
- Exchange Control Panel URL:
https://vamwan310.vamwan.com/ecp/
ECP access.
4. AutoDiscover Tips
- AutoDiscover Service itself is a web application running on the AutoDiscover virtual directory (not a server service) designed to provide connection information to various
clients.
- The AutoDiscover service is automatically installed and configured when CAS role is added to any Exchange Server.
- AutoDisocver virtual directory is created in IIS within the Default Web Site.
- A Sercive-Connection-Point (SCP) object is created in AD.
- The SCP contains a URL to the AutoDiscover service. This is for intranet clients so they do not have to use DNS to locate the AutoDiscover service.
- In AD this object is located at the following location:
DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative
Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name>
- Setup creates the AutoDiscover URL based on the following structure:
<CASNetbiosName>.domain.com/AutoDiscover/AutoDiscover.xml
If a PKI certificate is not already present, a self-signed certificate is installed on the Default Web Site.
To help allow this certificate pass the Issues to test it is set up with a Subject Alternative Name containing urls.
If a PKI certificate is present, that certificate is utilized and configured for use in IIS.
The Outlook Provider is used to configure separate settings for the Exchange PRC protocol (internal to network), Outlook Anywhere (Exchange HTTP protocol), and WEB:
EXCH, EXPR, WEB
The
EXCH and EXPR setting are vital for the proper configuration of Outlook.
5. AutoDiscover Workflow
General Process flow:
There are various components surrounding the AutoDiscover Service and all are necessary to complete a request. Including IIS, AutoDiscover service
itself, the provider, and AD.
a.
Client constructs service URL and submits Autodiscover Request. First attempt to locate the SCP object in AD. So, DNS is not needed.
b.
IIS Authenticates User.
c.
Is the Autodiscover service in the appropriate forest?
+ If YES.
1)
Parse/Validate Request
2)
Is there a provider that can service the Request?
++ If YES
a)
Config provider processes request and returns config settings.
b)
Return config setting to client
++ If NO
Inform client we cannot process request
+ If NO.
Redirect client to Autodiscover service in the appropriate forest.
Methods to find Autodiscover services: SCP and DNS
Domain-joined
a. Find SCP first.
The SCP contains the URL to the AutoDiscover service.
URL: https://CAS01.contoso.com(CAS’ FQDN)/AutoDiscover/AutoDiscover.xml
If more than one SCP object is found in AD (it means there are multiple CAS servers in the Exchange organization), Outlook client will choose one of the SCP entries that
are in the same site to obtain the AutoDisocover URL.
b. If we cannot find SCP object, then Outlook client will use DNS to locate AutoDiscover.
Outlook parses out the domain (SMTP suffix) via your EmaiAddress, then attempts to connect to the predetermined order of URLs via the suffix.
For example: If my email address is
[email protected]
Outlook tries POST commands to the following order of URLs:
https://contoso.com/autodiscover/autodiscover.xml
https://autodiscover.contoso.com/autodiscover/autodiscover.xml
NOTE: The URLs above is by design, hardcode
and cannot be changed.
c.
If those fail, Outlook tries a simple redirect to another URLs in IIS:
http://contoso.com/autodiscover/autodiscover.xml
http://autodiscover.contoso.com/autodiscover/autodiscover.xml
If none of these URLs work then DNS is most likely not set up correctly.
We can test that by pinging one of the above URLs.
If that is successful, we must ensure the URLs contoso.com or autodiscover.contoso.com are actually pointing to the CAS server.
If the ping fails then there is a chance that DNS is not set up correctly so be sure to check that the URLs are even registered.
NOTE: If contoso.com is a non-CAS server,
we should add a Host record with just AutoDiscover. And point that entry to your CAS server that is running AutoDiscover.
d.
If still failed, we can use DNS SRV lookup for _autodiscover._tcp.contoso.com, then “CAS01.contoso.com” returned. Outlook will ask permission from the user to continue
with AutoDiscover to post to https://CAS01.contoso.com/autodiscover/autodiscover.xml
Non-Domain-joined
It first tries to locate the Autodiscover service by looking up the SCP object in AD. However the client is unable to contact AD, it tries to locate
the Autodiscover service by using DNS.
Then, same as step b, c, d in
Domain-joined scenario.
6. How to change the AutoDiscover
service location order forcibly?
By default, Outlook client locates AutoDiscover service in that order above.
We can also change the order forcibly.
a.
If we want to locate AutoDiscover service via one of the autodiscover URLs, please running following command in EMS:
Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml(URL
that you want)
b. If we want to locate AutoDiscover service via
SRV record, please follows this KB to set up SRV:
http://support.microsoft.com/kb/940881
7. How to check AutoDiscover Healthy
a. We should make sure the AutoDiscover
is healthy before using AutoDiscover to perform troubleshooting.
b.
We can browse following URL in IE explorer:
https://autodiscover.vamwan.com/autodiscover/autodiscover.xml
If it returns “code 600”, that means AutoDiscover is healthy.
Screenshot as below:
c. AutoDiscover itself returns errors to the requesting client if the incoming request does not contain the appropriate information to complete a
request.
The following table explains the possible errors that could be returned.
Error Value
Description
600
Mailbox not found and a referral could not be generated.
601
Address supplied is not a mailbox. The provided email address is not something a client can connect to. It could
be a group or public folder.
602
Active Directory error.
603
Others.
The 600 “Invalid Request” error is returned because a user name was not passed to the service. That is OK for this test because this does confirm
the service is running and accepting requests.
d.
If AutoDiscover service is not working well, I suggest re-building the AutoDiscover Virtual Directory for testing.
Steps as below:
1) Running following command in EMS to remove the AutoDiscover VD (we cannot delete it via EMC):
Remove-AutodiscoverVirtualDirectory -Identity "CAS01\autodiscover(autodiscover.contoso.com)"
Please refer:
http://technet.microsoft.com/en-us/library/bb124113(v=exchg.141).aspx
2)
Running following command in EMS to verify whether we have removed the AutoDisocver VD successfully:
Get-AutodiscoverVirtualDirectory | FL
Please refer:
http://technet.microsoft.com/en-us/library/aa996819(v=exchg.141).aspx
3)
Running following command in EMS to re-creating a new AutoDiscover VD:
New-AutodiscoverVirtualDirectory -Websitename <websitename> -BasicAuthentication:$true -WindowsAuthentication:$true
Please refer:
http://technet.microsoft.com/en-us/library/aa996418(v=exchg.141).aspx
8. Common issues
a. Outlook Disconnection
Issue and Troubleshooting
Issue:
Sometimes the Outlook clients cannot connect to the Exchange server after migrating to a new Exchange server or changing to new CAS. The Outlook clients
always connect to the old CAS server.
Troubleshooting:
To solve this issue, we should change the SCP via following command:
Set-ClientAccessServer -Identity
<var>CAS_Server_Name</var> -AutodiscoverServiceInternalUri
https://mail.contoso.com(newCAS’FQDN)/autodiscover/autodiscover.xml
b. Autodiscover
Certificate issue
Tips on Certificate:
Exchange requires a certificate to run an SSL protocol such as HTTPS. We can use the certificate that supports subject alternate names (SAN) in Exchange.
This is to allow the certificate to support resources that have different names, such as Outlook Anywhere and the Autodisocver Web application.
Issue and Troubleshooting
Issue:
We receiver the Certificate Principal Mismatch error when we use a SAN certificate.
Troubleshooting:
1) Please determine the FQDN that the client
uses to access the resource. Steps as below:
OutlookàToolsàAccount
SettingsàE-mailàclick
the Exchange accountàChangeàMore
SettingsàConnectionàExchange
Proxy Settingsànote the FQND that list in the
Only connect to proxy servers that have this principal name in their certificate box.
2)
Please using EMS to determine the value for the CerPrincipalName attribute: Get-OutlookProvider
This command returns the result for the EXPR name.
3)
Please re-setting the CertPrincipalName attribute to match the FQDN via following command:
Set-OutlookProvider EXPR –CertPrincipalName: “msstd:<FQDN the certificate is issued to>”
9. Resource for reference:
Autodiscover and Exchange 2007
http://technet.microsoft.com/en-us/library/bb232838(v=exchg.80).aspx
White Paper: Understanding the Exchange 2010 Autodiscover Service
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx
Certificate Principal Mismatch
http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.HI,
I get following? when run the test? user is login to Domain A but accessing exchange in Domain B? -
Migrating to Unified communications exchange 2007
we are currently using unity 5.0 and it is in its own active directory domain and forest as well as the exchange 2003..we want to move to exchange 2007 unified communications and this is in a different domain/forest as well...what would be the proper steps to migrate over in a situation like this from untiy 5.0 in one seperate forest than exchange 2007 thats in another forest?
Hi,
This is really more of an MS question.
But I take it you are using Unity VM only for exchange? If it is a separate AD then the only info in that AD is used for Unity so you dont really need to keep any of it.
If it's in a separate AD then why not just configure your exchange 2007 for UM in parallel.
In CallManager you can configure a separate voicemail profile for Exch UM and assign it to certain users.
Have you piloted this yet? There are some limitations with UM for Exch 2007.
You can export subscriber information from SQL database on unity, and use it with powershell script for exch 2007 to actually get the users across.
I'd say when people move, they are going to have to re-record greetings, and lose their old voicemail etc.
Cheers,
Tim -
Adding a new FFL 2012 trusted domain to a Exchange 2007 domain with a FFL 2003 domain
My organization has decided to create a new forrest and domain. We will be creating a two way trust between the current 2003 forrest & domain and the new 2012 forrest & domain. For now, only a few of our users will
log into the new domain, but we still want them to be able to access their email in the 2003 domain and have their emails come from the 2003 domain. There are no Exchange servers in the new domain, users will just authenticate to the
new domain.
Besides creating the accepted domain policy and new email policy, is there anything else that will be required?
Thanks in advance
MikeV
Thanks, MikeV MCSE 2012In Exchange 2003 there is no "accepted domain policy" or "email policy", just recipient policy. And you only need to do that if you're adding a new e-mail domain. Further, in many cases you can probably just modify the existing policy.
A one-way trust with the server domain trusting the account domain is all that should be necessary. You will have to grant full mailbox rights and send as rights on each mailbox to the corresponding user account.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
We added the trust, but Exchange doesn't see the new domain. I've tried both the EMC and powershell (add-mailboxpermission useralias -user"newdomain\alias" accessrights-fullaccess) error says "user or group not found please make sure you
have typed it correctly"
What else needs to be done for Exchange to see the new domain and users?
Thanks, MikeV MCSE 2012 -
Exchange 2007 to Exchange 2010 Cross Forest
Hi
We have a scenario where we have an Exchange 2007 organization (Org A - Source) and a separate Exchange 2010 organization (Org B - Target). Both the organizations (AD Forests) have two way trusts between them.
We want to have our Exchange 2007 users have their mailboxes hosted on Exchange 2010 organization. Meaning that the user (AD) accounts of Org A will remain in Forest A but there mailboxes will be available on Exchange 2010 servers in Org B. So we don’t need
a user / group migration stuff here and mailbox data on Exchange 2007 servers is also not critical (not required to be migrated) so we will be creating new disabled accounts and mailboxes in Org B for each user in Org A and connect the mailboxes. There will
be a brief period of co-existence between two Orgs (to enable mail-flow) until all the users have their mailboxes active in Org B. Need to figure out a way to achieve this.
We are planning to follow the steps below:
Setup name resolution between the forests (although basic connectivity is there and we can ping servers in one forest using IP Addresses from other forest) –
Please suggest if this is necessary or we can get away with it?
Setup SMTP namespace sharing for Exchange 2007 SMTP Domain name
Add Exchange 2007 SMTP domain as authoritative domain to E2K10
Create EAP for new SMTP Domain
SMTP Connector Creation for Direct E-mail Routing (Co-exist) Between Forests
Create disabled Mail Enabled (not Mailbox Enabled) User or Mail Enabled Contact in Org B.
Can we use Prepare-MoveRequest.ps1 script to create these?
Once a mail enabled user / contact is created in Org B for all the users, change incoming traffic from Internet for Org A SMTP domain to hit HT server in Org B
Make changes to Exchange 2010 certificate and install new certificate
Select a batch of users every day, create new mailbox for them using scripts in Org B and delete the corresponding contact in Org B
Can someone please confirm if this is correct and point out something I am missing?
Is there any other way to achieve the same goal?
Thanks
Taranjeet Singh
zamnHi Everyone
Thanks for the inputs so far. I need to confirm some steps to establish direct email flow unless all the mailboxes are created in target organization, can somebody have a look at the steps below and confirm if they are correct or add something that
I missed here:
Setup source Exchange organization:
a) Add unique SMTP domain for source organization, like @source.local. This domain will be added to all mail enabled objects in this organization and will be used for internal routing only
i) Add to Accepted Domains list
ii) Create EAP to add domain to existing objects
b) Use manual means to stamp SMTP domain to objects in source organization on objects that don’t have EmailAddressPolicyEnabled set to False
c) Create Send Connector to target forest. The target domain should also have a unique e-mail address, like @target.company.com (in our case 19 SMTP domains including JUBL.COM)
i) Include the valid SMTP domains and the unique one for internal routing
(source.local)
ii) Point to a smart host in the target forest
d) Set existing SMTP domain (JubilantRetail.com) as “Internal Relay Domain”. The target Exchange org will be authoritative for this domain
Setup target Exchange organization
a) Create Send Connector to unique SMTP domain in source forest. Includes shared name space (source.local) and @JubilantRetail.com
b) Set Default receiver connector, being used by source forest, to allow anonymous connections
c) Add shared SMTP domain (source.local) to Accepted Domains list as authoritative
d) Create EAPs to replicate the SMTP domains (e:g JubilantRetail.com and source.local) in the source environment
Thanks
Taranjeet Singh
zamn -
Cross Forest Migration from Exchange 2007 to Exchange 2013
Hi
Could anybody advice me the steps also the pros and cons for below mentioned environment if we are going for the cross forest migration.
Source
Domain - test.local
Active Directory - Windows 2003
Exchange Server - 2007
Target
Domain - test.net
Active Directory - Windows 2012
Exchange Server - 2013
Also if it is possible ,
How could I remove the source environment including the exchange servers. after the migration ?
Regards
MuraleeHi Oliver ,
Please suggest us.
In my environment we are in a plan to migrate from exchange 2007 to exchange 2013 (cross forest migration).
Source : Exchange 2007 with sp3 ru 10
Target : Exchange 2013 with cu2 ( new environment yet to be created).
Trust : Forest trust in place (two way )
Domain and forest functional level : 2003 in both target and source
Migration Steps :
Step1 :
We are in a plan to execute 'preparemoverequest.ps1' first in the target forest ,so that we will get the disable MEU
in the target forest.
Step2:
Then we are going to use ADMT to migrate users SID'S and password .
Step3:
Then we are going to move the mailboxes with New-moverequest
Please have a look in to our steps and suggest us ,whether we are going to proceed the migration in a right way or not
.Is anything needs to be changed please intimate me .
Thanks
S.Nithyanandham
Hey there,
Sorry for taking a little while to get back to you, i've been busy working on Hosted Lync deployments!
Use ADMT first, then when using preparemoverequest.ps1 script using the -uselocalobject cmdlet. This will then tie it up to the ADMT migrated account.
More info in this thread here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2916e931-36a0-4ba4-8c04-196dbe792b44/preparemoverequestps1-and-admt?forum=winserverMigration
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,MCITP:Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi -
Outlook 14.4.8 on iMAC Retina and Yosemite 10.10.2 is not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox".
Accessing Mails with Webbrowser and from Windows Outlook is working correctly.
All Macs (also the ones with OS 10.6.8) do not anymore show any new messages in inbox.
Restarted Server, tried to disable autodiscover on macs and deleting/adding account and repairing database does not fix the problem. Also restarted server several times.
We have the same problem on 2 imacs retina with yosemite and on 2 mac pro with 10.6.8 and different office 2011 versions.
i tried to configure the exchange account in apple mail on yosemite and it also states "connected" and does list some folders but no new mails are getting in.
Windows clients and outlook on them works and syncs fine, and also when connecting via webbrowser at owa it must be a mac-specific/webdav issue.
exchange 2007 Sp3 Version 8.3 (bild 83.6) and Update Rollup 15 for sp3 (automatic updates "HIGH" for server and clients)
there is one update popping up again and again even after everytime successull installation: Windows Mlicious Software Removal Tool x64 - October 2010.
i tried to configure a new user with empty mailbox and configured it with microsoft mail (mac - yosemite) as exchange and was able to send a mail from there (even if quite delayed).
but there are not coming in any mails.
same exchange accounts triggered by imap do work and also via owa.
Exchange Accounts in Outlook for MAC and also in Mail (Yosemite) do show the folder structures but there is no mails showing up. I can send mails from the exchange accounts created but they seem to be processed with a delay of like 15minutes and outlook
is giving error "end of file reached" but messages are send after some time.
Does seem like EWS is extremely slow, to slow perhaps to sync and therefore ending in timeout.
Also i cannot reach the server from externally over ssl https 443. if testing port 443 of exchange from outside the port seems closed even firewall settings of sbs 2008 and sonicwall ports are correctly open.
could it be there is something in regarding webdav which is very slow and leading to timeouts ?
in application log i do have the following two information events every few minute:
The Exchange Web Services started successfully. Event ID 1
and
Process STORE.EXE (PID=3688). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
SERVER.org.local CDG 1 7 7 1 0 1 1 7 1
Out-of-site:
Errors in Application log:
The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section
The entry <C:\WSUS\WSUSCONTENT\CONTENTFOLDERACLSCHECK.TXT> in the hash map cannot be updated.
An exception Microsoft.Exchange.Data.Storage.ConversionFailedException occurred while converting message Imap4Message 69447
Also outlook 2011 clients are asked by time to time to reenter pwds and errors like "connection is closed. 13"
Faulting application taskeng.exe, version 6.0.6002.18342, time stamp 0x4cd34898, faulting module ntdll.dll, version 6.0.6002.18881, time stamp 0x51da3d16, exception code 0xc000071b, fault offset 0x0000000000082445, process id 0x3288
Certificate Services Client Provider pautoenr.dll raised an exception. Exception code 3221225477.
Backup Exec:
FULL_BACKUP -- The job failed with the following error: A failure occurred querying the Writer status.
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The
error returned from CoCreateInstance
Exchange VSS Writer (instance 2d932ef8-6319-4ab8-a45f-1242480b44ad:15) failed with error code 1295 when processing the backup completion event.Hi,
Since Outlook running on Windows works well, it seems an issue on the Mac side. I suggest ask Mac for help so that you can get more professional suggestions.
More information for your reference:
Please try to verify whether there is any expired certificate from the computer personal store.
If it is the case, please remove them.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support -
Need help on Cross Forest Exchange 2007 - 2013 with Linked Mailboxes
Hey all,
So I'm in a bit of a pickle with my Exchange design and am trying to figure out if there's a way to migrate mailboxes across forests where Linked mailboxes are being used. I've done a bit of reading and have noted stuff like preparing the move request in
AD, etc. But I'm wondering if someone can break it down for me.
http://1drv.ms/1lWjLqG
The above is a OneNote diagram of how we have moved over time. Please forgive my sloppy handwriting but I hope it gets the point across. I will text it out here as well:
Original Design
The original design of the domains when I joined the company were fabrikam and contoso. Contoso is a domain that sits entirely in the "DMZ". Fabrikam was the internal AD forest where most services and users authenticated to. In Contoso, there
are 2 domain controllers, the "Front End" Exchange Server (Edge Transport), and the "Back End" server, which is CAS/Mailbox.
There is a forest trust between contoso and fabrikam where "Linked Mailboxes" are created in Contoso, and then the LinkedMasterAccount is set to Fabrikam.
Migration/Hybrid Design
Due to the fact that these two domains were configured massively inappropriately, riddled with security holes as well as strange permissions configurations, the decision was made to create a new internal AD domain. In my OneNote, I've labeled this 'specialbank.com'.
A long while ago we migrated users from Fabrikam to SpecialBank via trusts. To facilitate access to Exchange, a new trust was created between Contoso and SpecialBank to allow us to update the LinkedMasterAccount parameter to the new Specialbank domain.
We have most of our users authenticating to their mailboxes via SpecialBank, while the mailboxes still reside in Contoso.
Migration from Exchange 2007 to Exchange 2013
I am attempting to now figure out the best way to migrate the mailboxes from Contoso to a new set of Mailbox servers in SpecialBank. This will also be an upgrade from Exchange 2007 (Current) to an Exchange 2013 installation.
The latest Service Packs and CUs are installed in both.
What would be the best procedure to move these mailboxes? To my knowledge, the current best practice/recommended way is to perform a user/SID migration from Contoso to SpecialBank. But I already have accounts in
SpecialBank that users are actively using.
I'm not opposed to doing a simple PST export from Contoso to SpecialBank, but we're looking at around 120 mailboxes. So I'm trying to make my life a little easier instead of spending a weekend here.
If I try to do it in batches, I need to figure out how to handle autodiscover and CAS. Since I'm creating an entirely new Exchange environment, I'm trying to limit what I place in the existing configuration. But I'm not opposed to setting up something temporarily
if I need to in order to make the migration transparent to users.
Can anyone help?Hi ,
From you description i came to know contoso is the resource forest and special bank is the account forest .
You just wanted to migrate the linked mailboxes from resource forest to account forest and also you would want the migrated mailboxes to get merged to the respective user accounts in the account forest to become as a normal user mailbox.Am i right ?
Please correct me if i am wrong . I have found some blogs in internet please have a look in to that especially the first one.
http://www.outlookforums.com/threads/60210-cross-forest-mailbox-move-and-linked-mailbox/
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27974905.html
Regards
S.Nithyanandham
Thanks S.Nithyanandham -
New CAS for Load Balancing Exchange 2007
I want to add a new CAS to an existing Exchange 2007 environment (there is already one CAS and it functions properly) to allow for load balancing. After adding the new server I wanted to do some testing (before I actually set it up for load balancing).
If I try to log in to a mailbox using OWA I get an error stating that "Exception type: Microsoft.Exchange.Data.Storage.ConnectionFailedTransient ExceptionException message: Cannot open mailbox". I am sure I am missing something simple, but cannot
figure it out. Could someone point me in the right direction?Is your new CAS in the same Windows site as the rest of your Exchange servers? In Exchange 2007 and 2010, the CAS needs to be in the same Windows site as the mailbox it is servicing (unless you are accessing from the Internet and the other site has
no externally accessible CAS). -
New User cannot access OWA after migrate from Exchange 2007 to Exchange 2013
Dear all,
I recently migrate the Exchange server from Exchange 2007 on Windows Server 2003 to Exchange 2013 on Windows 2012 R2. I can open the mailbox moved from Exchange 2007 without any problem. However when I created a new user in Exchange 2013, the user cannot
login the OWA, the browser will throw out following screen. Can anyone help me in this case. Thanks a lot!Hi Winnie,
Thank for your reply. Below is the result, please note there has four exchange servers, HKAD and HKEX are the existing Exchange 2007 server. HKCAS1 and HKCAS2 are the new Exchange Server 2013 - both of xchange server 2013 are using owa.ksi.com.hk
as the external URL.
Identity : HKAD\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url : {}
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
https://hkad.ksi.com.hk/owa
ExternalUrl :
Identity : HKAD\Exchange (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKAD\Public (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKAD\Exchweb (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKAD\Exadmin (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKEX\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url : {}
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
https://hkex.ksi.com.hk/owa
ExternalUrl :
Identity : HKEX\Exchange (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKEX\Exadmin (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKEX\Public (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKEX\Exchweb (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKCAS2\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url : {}
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
https://hkcas2.ksi.com.hk/owa
ExternalUrl :
https://owa.ksi.com.hk/owa
Identity : HKCAS1\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url : {}
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
https://hkcas1.ksi.com.hk/owa
ExternalUrl :
https://owa.ksi.com.hk/owa -
SBS2008: Move email from Exchange 2007 to new server with Exchange 2013
We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server.
Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one?
Old Server:
SBS2008 running Exchange 2007
New Server:
Server 2012
Exchange 2013
Any help is appreciated!Hi Dave,
It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
you in the past).
For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model. In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
up to 2 Virtual Machines on same host).
There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration.
You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration. But the high points are in here. If it looks
like something you would be comfortable with then you should research more.
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
and migrate your workstations out of old domain into new domain. Whether this is more or less work at your workstation count is dependent upon a lot of variables.
If you have more questions about the process, update the thread and we'll try to assist.
Hopefully this info answered your original question.
Cheers,
-Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP -
When opening my Outlook 2010 with new added e-mail account with Exchange Server supplied by my employer, I have to click manually on my standard e-mail account for checking mail. Do I have to upgrade my Microsoft Office 2010 or how can I make my Outlook
2010 check all my four e-mail accounts without manually click on my accounts?
Sincerely
Ketil HothorpHello Ketil,
Good Day...
Seems to be the Issue is Syncing emails, now I would recommend you to Remove and Add the Account and try and check if the emails are getting synced automatically.
Hope this is with Single User. If it is with Multiple Users then we need to check the permissions assigned.
Regards,
Praveen -
Hi All. I am currently at the later stage of provisioning a new CCR Exchange 2007 migration (to
virtualise old Exchange 2007 hardware) for 5,000 users & have a quick question.
I have created around 15 newly named storage groups, & have named 1 new DB per group, with the same name (let's say New-DB-1), residing within them. The problem I have, is the old legacy DB's have different names (let's say Old-DB-1) & I need
to import them into the new storage groups, to match the new names. So far I can import/export between old & new OK if both old & new DB names\folders etc. names marry up perfectly, but are unable to if there not the same. Does anyone have any thoughts
on how best to tackle this, as this is one of the final hurdles stopping the migration? Many Thanks, JohnHi All
Many Thanks for the feedback.
The terminology 'migrate' was used based around the fact I will be decommissioning the old 2007 physical environment. This is after moving all DB's over to the new newly created Virtual environment that will host all roles.
The solution I ended up using yesterday, was the following:
1) Dismounted the relevant named DB (NEWDB) in the new environment.
2) I then ticked the 'This database can be overwritten by a restore option' box.
3) Copied over the old named DB (OLDDB) to the same location, & overwrote using the new name (NEWDB).
4) Re-mounted the (NEWDB).
5) Ran the following 2 PowerShell commands:
Get-mailbox –database OLDDB | move-mailbox –targetdatabase NEWDB -configurationonly:$true
Get-MailboxDatabase NEWDB | ResetSearchIndex.ps1 -force
6) Checked to make sure the clients were working ok, in the now the new (NEWDB) environment.
Rich: Many thanks for your PS script, which I will test with future DB moves & provide feedback
J
John.
Maybe you are looking for
-
i currently have a calendar synced that has events scheduled in perpetuity, scheduled as individual events. I would like to delete all events with the same title. I do not want to delete the entire calendar nor do I want to go into every event and
-
SSO to Web Application from Portal
Hi, I am working on a scenario where I need to access a Web Application from the Portal. I read about the Application Integrator that is provided by the Portal . I wanted to know that can I only have SSO to those Web Application that acce
-
Disk Utility not showing same disk space as get info on HD
Hi, My Macbook Pro was really slow and i did Repair Disk and it seems to work much better. the problem is that when i get info on my HD it shows me that there is 200 GB free but when i go to Disk Utility it only shows me that there is 73 GB free??? H
-
Help, am I missing an index page?
Hey everyone, I just created a site, very simple splash page for one of my bands, with rollover image buttons to forward the public off to other websites. I've connected to my site via FTP, using CS4 to upload all the files in my site's home folder o
-
SFV file association in KDE trouble getting it setup properly
Im having trouble getting parano the program I use to check sfvs to actually associate with sfv files. If right click on a sfv file and go to properties and change it to parano it changes it for all txt files and everything. Then when tinkering I del