Can IDM 8.1 support MS Exchange 2010 ?

Hellos
Is there ANY way we can introduce Exchange 2010 support into our IdM solution?
Customers are migrating directly from Exchange 2003 to Exchange 2010.
What is the status re Active Directory "connectors" is there any sort of IdM migrating tool to switch from AD Gateway approach to AD Connector.
What we are faced with is the sudden REWRITE of ALL AD provisioning.
a pissed off GF

Hi everyone.
I did a little bit more digging and found the following piece of information that I think you'll all find beneficial.
A few months ago one of my customers asked the following:
If a customer is planning on using the Active Directory connector with Exchange 2007 support
enabled, how will that affect IDM provisioning to Exchange 2010? Is that a configuration that's
supported?
I then received the following answer:
The connector provides the same functionality for Exchange 2010 that it did for Exchange 2007 (no
more, no less).
See the connector documentation for specifics: http://wikis.sun.com/display/IdentityConnectors/Exchange+Connector
What is doesn't do is support specific 2010 functionality (such as the ability to set Out of Office
Messages, that used to exist pre Exchange 2007 and was added back in for Exchange 2010).
Having said that, there is still the issue of the 8.1.1 release notes not stating specific support for Exchange 2010.
But for all intents and purposes, I've seen a few indications that it should work without issue. I am currently awaiting clarification on the subject, which I will be sure to post once I receive it.
I hope this helps.
Regards,
Alex

Similar Messages

Is WMF3 or WMF4 supported in Exchange 2010 SP3 UR5 installed on Server 2008 R2 SP1?

We'd like to upgrade WMF (aka powershell) on our Exchange 2010 servers but I haven't been able to find any updated information on support with the most recent servicepack/update rollup.
Is installing WMF3 or WMF4 supported on Server 2008 R2 SP1 w/ Exchange 2010 SP3 UR5?

WindowsPowerShell 3.0 is supported. Haven't seen 4.0 running for exchange 2010 on 2008 R2
http://blogs.technet.com/b/heyscriptingguy/archive/2013/11/30/weekend-scripter-wmf-powershell-and-exchange-server-compatibility.aspx
http://blog.crayon.no/blogs/janegil/archive/2013/11/17/how_2D00_to_2D00_install_2D00_windows_2D00_powershell_2D00_4_2D00_0.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Gulab,
Where did you read that WMF3 is supported on Exchange 2010 SP3 on Server 2008 R2?
Neither of the links you pasted suggest that and in fact explicitly say "There has been no testing with ExchangeServer 2010 SP3 and WMF 3.0 installed on Windows Server 2008 R2."
My Bad, that was TYPO...
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

How can I display my MS Outlook/Exchange 2010 Calendar events on my web application's calendar?

I'm building a web (client) application (built in html/JavaScript/jQuery) that has a built-in calendar. I would like to pull in my Outlook/Exchange Calendar events
and display them in my web application's calendar. What is the best way to do that from a JavaScript/jQuery environment? I've been searching all over for plugins or examples of how to talk to Exchange/Outlook and retrieve Calendar events but I haven't found
a solution yet. We are currently using MS Office/Outlook/Exchange 2010. I don't need to modify the calendar events, just read them. (Note that I can't use an OWA Web Parts link
to display the calendar in an iframe; I need to have access to the actual event data so I can include other UI elements that I need for my application.) Thanks
in advance for the help!

Hi,
There's an old Java API for EWS, and you can access EWS with direct soap request to retrieve the data you want.
Cheers,
Fred
There's no place like 127.0.0.1

CUP 8 Support for Exchange 2010 Calendaring

Will Unified Presence 8.5 support Exchange 2010 calendaring?
Thanks!
Jeff

That's the plan. Nothing is guaranteed until it reaches FCS though.

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

I can't either mount for remove Exchange 2010 mailbox database file

Yesterday I proceeded with moving Exchange 2010 database file to a newly installed hard drive because my "C" drive was running out of space. After dismouting both the mailbox database and the public folder database, I used EMC's "move
data path" wizard to move both the mailbox database and public folder database to "mailbox" folder in "D" drive. The move was successful without an error, but when I opened "mailbox" folder in "D" drive, both
the database file and public folder database files weren't there. All the other files were moved, but the mailbox database file was gone.
Luckily I manually copied entire mailbox folder to another folder in "D" drive. So I manually copied mailbox database file (it is about 20GB) to "d:\mailbox". When I try to mount, I received the following error message.
Microsoft Exchange Error
Failed to mount database 'Mailbox Database 1658107303'.
Mailbox Database 1658107303
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database 1658107303; Error code: An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC
error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3..
An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3.
Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3
When I try to move the database path back to the original path, I received the following error message.
Mailbox Database 1658107303
Failed
Error:
There are no source files under the path:d:\emailbox\Mailbox Database 1658107303. Use the command Move-DatabasePath -ConfigurationOnly in the Exchange Management Shell to set the new path in Active Directory only.
Exchange Management Shell command attempted:
move-DatabasePath -Identity 'Mailbox Database 1658107303' -EdbFilePath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox database 1658107303\Mailbox Database 1658107303.edb' -LogFolderPath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox
database 1658107303'
EMC would not even delete the database file.
I need help. I need to mount my mailbox database file. Please help.

If the database was fine pre move I doubt it needs a repair, however if you want to validate do an eseutil /mh ReplaceWithYourDatabaseName.edb and post the results here
did you move the logs as well or are they still in same location
I have seen this before if everything is where its supposed to bea restart fixed it so I would recommend that you put the DB back into the NEW D path and do a restart to see if that resolves the issue
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003
--> 2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Can not connect smart phones to exchange 2010

Exchange appears to be work OK. I can set up a smart phone and connect it to the exchange server, but when I try to look at the inbox, or for that matter any other folder, all I see is that small circle spinning and will never display any folder or
mail box. I have a Godaddy SSL certificate, in bound and out bound mail using outlook 2007-2010 works good with pc's on network. OWA works perfect off site. Just having trouble with smart phones. Not sure where to look or what to do.
Any help would be greatly appreciated.
Brent Adkison
[email protected]

I suggest checking out the following tools / techniques:
the ActiveSync tests here: https://testconnectivity.microsoft.com/
within OWA options (ECP) use and review the "start logging" feature: http://blogs.technet.com/b/jasonsla/archive/2013/03/19/exchange-activesync-mailbox-logging.aspx
test with another user to determine if the issue is limited to a single account
Mike Crowley | Exchange MVP
Baseline Technologies

Can you help with this problem Exchange 2010

Exchange Mail Error
1-
imta31 #550 Sender domain must exist
2- This message has not yet been submitted.
Transmission will continue to be tested.
Server, the next 1 day, 19 hours and
55 minutes to deliver this message
will continue to work. During this time,
the message can not be delivered, you are notified.
Thank.

Hi izzet OZGEN,
You could use Exchange Remote Connectivity Analyzer Tool to troubleshoot your problem by following link:
https://testconnectivity.microsoft.com/
This tool is web-based, and is designed to help IT Administrators troubleshoot connectivity issues that affect their Exchange Server deployments. The tool simulates several client logon and
mail flow scenarios. When a test fails, many of the errors have troubleshooting tips to assist the IT Administrator to correct the problem.
Hope it can be helpful.
Best regards,
Eric

Can you have multiple databases on the same LUN in Exchange 2010?

I'm sure you can but is it possible with exchange 2010 to have multiple databases on the same LUN. We currently have 8 DB's all writing to their own DB drive and separate log drive so 16 drives in total. I need to spin a new DB up this week and
wanted to double check this is possible. I've looked online and cant find anything that I've seen before that says this is possible.
Thanks.

Hi,
Yes, multiple databases could be placed on the same LUN, but it's not recommended.
If you have 2 drives fail at the same time (it happens more than you think), then losing 100% of your DBs is a lot worse than losing one of them or some of them depending on where the failures are.
Here is a similar thread for your reference:
Multiple databases on the same LUN in Exchange 2010
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Can EXCHANGE 2010 USE default app pool - v4?

Hi guys.
I had a problem on Exchange 2010 SP3 with latest cumulative update that I needed to change Default App Pool from 4 to 2.
I don't know what caused changing those numbers to 4, but I'm curious is there any official statement about it, that it should have number 2 and not 4?
Because if I look in this address:
http://technet.microsoft.com/en-us/library/ff728623.aspx
under Microsoft .NET Framework I see table where it's written that
.NET Framework 4.5
is supported in
Exchange 2010 SP3
so I'm a little bit confused/amused.
bostjanc

Hi,
What version of IIS are you using?
I find a related information about Default App Pool for your reference:
http://www.iis.net/configreference/system.applicationhost/applicationpools/applicationpooldefaults
Version
Notes
IIS 8.0
Another value ("v4.0") was added to the
managedRuntimeVersion attribute in IIS 8.0, and its default value was changed to "" instead of "v2.0".
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2010 coexist with exchange 2013

Hi All ,
Planning to have a coexistence scenario in my environment which is mentioned below
Exchange 2010 - ambiguous url in place - OA enabled
For mapi/rpc traffic - mail.domain.in - exchange 2010
For https traffic - mail.domain.in - exchange 2010
mail.domain.in will get resolved in to cas array in exchange 2010 .
After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
Note :
On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
exchange server via exchange 2013 server.
question : I would like to know above mentioned scenario is possible or not ?
On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
All of you tell me your valuable suggestions.
Regards
S.Nithyanandham

Hi,
Going Straight to the point... and answering your question...
The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
As per Exchange Team...
In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
their DNS cache expires after the shared FQDN is moved to CAS 2013.
As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
fix existing Outlook clients with the old value in the server field.
So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
Outlook 2013: 15.0.4420.1017 (RTM or later)
I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx>
Hope it can help you!
Cheers,
Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

Installation of Exchange 2010 in Windows 2012 Server

Hi all,
We are planning to upgrade our current Exchange 2003 to Exchange 2010, Need some help on installation and Support of Exchange 2010 in Windows 2012 Server, as per the
https://technet.microsoft.com/library/ff728623(v=exchg.150).aspx Exchange 2010 with sp3 is supported in Windows 2012 but I am unable to find the installer of Ex 2010 with sp3
in web even in MSDN. There is only Ex 2010 with Sp1 available. I know that after installing ex2010 with sp1 version, I can install sp3 later but I found one link
http://www.petenetlive.com/KB/Article/0000785.htm where it is mentioned that insllation can be done only after doing the registry settings.
So is any one who has installed Ex 2010 in Windows 2012 Server and faced this issue and any solution.
Thanks
Mukesh
Mukesh Bisht

You can easily install Exchange 2010 (SP3) on Windows Server 2012. If you are working with previous SP version’s you can easily upgrade after installing server. And registry settings
are used to fix an error which may occur during migration, so it is not mandatory to correct registry settings each time during migration.
You can find detailed information about installing Exchange 2010 (SP3) on Windows Server 2012 at this blog :http://oxfordsbsguy.com/2013/03/24/how-to-install-exchange-2010-sp3-on-windows-server-2012/

Direct File access feature supported in OWA 2010 ?

Is the direct file access feature supported in exchange 2010 ?
If not, why is there still an option to enable and customize it in 2010 ?

Is the direct file access feature supported in exchange 2010 ?
If not, why is there still an option to enable and customize it in 2010 ?
It is an orphan that will be removed from EMC is a future update. The feature itself has been removed from 2010, you can no longer access SharePoint or file servers through OWA. There is still "direct file" access in OWA, but in the spirit of being able to directly open an attachment without being forced to use the web viewer.Brian Day, Overall Exchange & AD Geek
MCSA 2000/2003, CCNA
MCTS: Microsoft Exchange Server 2010 Configuration
LMNOP

Exchange 2010 - Exchange 2013 permanent coexsistence to avoid migration of Public Folders

Hi Guys,
I was hoping to get some opinions/ advices regarding the case explained below.
The company I work for has a medium-sized Exchange 2010 infrastructure that consists of several geographically dispersed 2-node DAGs and corresponding CASArrays. It hosts about 1000 mailboxes in total and large public folder database that is replicated on
every mailbox server in the environment. All users are using Outlook 2010/2013.
There is a business drive to perform migration to Exchange 2013. However, migration of the Public Folders is not feasible because of the lack of multimaster replication, the complicated migration process and several other limitations in Ex2013 PFs.
To work around this issue while still performing the migration I am considering the following scenario:
Deploy Exchange 2013 servers in the organization
Migrate all mailboxes to Exchange 2013 servers
Don't ever start migration of Public Folders (leave one Exchange 2010 mailbox server in every location for hosting the Public Folder database)
Keep the coexistence permanently (with mailboxes on 2013 and public folders on 2010)
What do you think of this setup? Do you see any issues with such long-term coexistence?
Thanks.

Hi,
You can leave the public folders on Exchange 2010 if you can’t migrate them to Exchange 2013. Exchange 2013 users can access public folders on Exchange 2010, but Exchange 2010 users can’t access public folders on Exchange 2013.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2013 and Exchange 2010 coexistense

We have a and exchange 2010 organization with SP3 on most servers except for one 2010 CAS server that still requires SP1 for the purpose of legacy application compatibility. Can we introduce exchange 2013 in the org or will the setup detect
that there is an exchange 2010 server still with SP1 and fails to continue?

Hi,
For Exchange 2013 coexistence with Exchange 2010, the mininum version of Exchange server is Exchange 2010 SP3 on all Exchange 2010 servers in the organization. For more information about it, please refer to the Coexistence of Exchange 2013 and earlier versions
of Exchange server part in the article below:
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Personal suggestion, please upgrade your legacy application to the latest version which is supported with Exchange 2010 SP3 or higher Exchange version.
Regards,
Winnie Liang
TechNet Community Support

Can IDM 8.1 support MS Exchange 2010 ?

Similar Messages

Maybe you are looking for