Exchange 2010 ambiguous URL'S issue while coexist with exchange 2013
Hi ,
Please correct me if i am wrong and also all of you tell me your valuable suggestions.
Like as said in the below article we are having an exchange 2010 ambiguous url's in place.
Referred
article :
http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
As said in this article, if we have exchange 2010 ambiguous url's in place we will face issues during exchange 2013 coexistence.I agree with that point .
Question : On such case why don't we use a separate namespace for internal and external outlook anywhere settings in exchange 2013 which is different from cas array name and also there is no need to disturb the existing exchange 2010
environment by changing the rpc client access attribute in exchange 2010 databases or by forcing the exchange 2010 internal outlook clients to connect via OA. Please clarify my doubt and say whether the mentioned scenario is possible or not ?
Note : Same time please consider the new namespace which is going to be utilized on exchange 2013 outlook anywhere settings is available on SAN certificate.
Regards
S.Nithyanandham
Hi ,
Please someone shed light on this case.
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham
Similar Messages
-
Remove Exchange 2010 DC from single server environment coexisting with Exchange 2013
My new Exchange server (2013) has completed all the migration steps including public folders. Mail is working well. I do not use the old DC running Exchange 2010 for any local domain logins or computer control, it is strictly for OWA as is my new Exchange
2013. I went through the uninstall of Exchange 2010 with out error but cancelled it after it said it was ready to uninstall. When I shut down Exchange 2010 server mail no longer is available. What am I missing? I am using same Public IP and different
private (192.168.1.4 new EXchange 2013, 192.168.1.7 for Exchange 2010) I changed these settings in my asa Firewall and that is working with new settings as well. Send and Receive connectors are on new while old one have been deleted. Do my MX records
need to be updated to reflect new server (ex2) as opposed to old server name (ex)?
You can come to Maui for a "Site Inspection" lol!
System AdminHi
You need to make sure all your DNS settings are correct with the new server IP as well as autodiscover. Remove any routing connectors between exchange 2010 and 2013.
Not best practice to run exchange on a DC but if you comfortable you have migrated all system mailboxes, user mailboxes and that the settings on your new server match the old one then proceed with the uninstall.
Your ISP will obviously route mail to your firewall as you are doing the NAT from there. -
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.NithyanandhamHi,
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! :) -
Outlook 2013 on 2012 RDS and Outlook/Exchange 2010 FAT client font issue
Our terminal server was changed from a 2008 RDP box with Office 2003 to a 2012 RDS box with office 2013 on it. Now if a user changes a font - or any view setting - on the 2013 copy on the terminal box, their desktop in the office which runs Outlook 2010
has the 2013 settings. Why and how - if possible - do I make that stop?
Specifically a user made her font large from home to see it better on her home monitor and when she came in to the office, her outlook here had the large font and she had to change it back...which changed her view on the terminal server back to small.
Can THAT be managed through either of the Outlook clients or Exchange 2010 server? It does NOT happen with OWA so I assume the server is ruled out.
Thanks!Hi Ms. Creant,
About this issue, I talked with Office colleagues, the issue you encountered is normal. If you change the font size from one client side, then you log in Outlook on another server, this settings
will be synchronized.
From Exchange side, we can only set OWA font settings, there is no way to prevent the synchronization of this in Outlook.
Thanks for understanding.
Best regards,
Belinda Ma
TechNet Community Support -
My Client have a Exchange 2010 Organization with Single Domain Single Forest.
They were using Internal CA Certificate and a TLS Cert.
As a POC we are doing a POC for Exchange 2010 Hybrid Office 365 Environment.
For this 3rd Party CA is Mandatory and they have bought a Geo Trust Certificate.
Now when they have installed cert on both HUB as well as EDGE servers, he was prompted to do edge subscription again.
HUB and CAS are combined on the server at both Main and DR Site.
When they try to do edge subscription again they are getting the following error.
SYED WASIL UDDIN Infrastructure Consultant/System Engineer Premier Systems (Pvt.) Ltd.I was finding out the solution and got this.
1-Certificate will import on both EDGE and HUB Servers.
2-Edge Sync will use Self-Sign Certificate (but I an unable to find how do I configure this)
3-some communication between Edge and Hub will be encrypted via 3rd party Certificate.
Could anyone suggest, which services on HUB must based in this 3rd party cert.
All the external communication must be encrypted via 3rd party CA and communication between HUB-EDGE will set on self-sign Cert. How do I do this.
SYED WASIL UDDIN Infrastructure Consultant/System Engineer Premier Systems (Pvt.) Ltd.
Hi,
Please run Get-ExchangeCertificate | fl to check your Exchange certificate settings. Also confirm if the 5E470560626E313646730C177FCA66728E2BAFF7 certificate is your trusted 3rd party cert.
Please use Enable-ExchangeCertificate cmdlet to assign SMTP service to your self-signed certificate in your Edge server.
Regards,
Winnie Liang
TechNet Community Support -
Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013
Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.NithyanandhamHi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham -
My
environment is as follows.<o:p></o:p>
We have 3 exchange 2010 servers.<o:p></o:p>
EX1, EX2, DREX1. All servers are exchange 2010 14.2 build 247.5<o:p></o:p>
EX1 and EX2 have two nics, one LAN and one for BACKUP <o:p></o:p>
The dag is configured to to communicate to all three.<o:p></o:p>
The IP for EX1 is 192.168.100.51 - LAN, switch A; 160.100.3.51 - BACKUP, switch B<o:p></o:p>
The IP for EX2 is 192.168.100.52 - LAN, switch A; 160.100.3.52 - BACKUP, switch B<o:p></o:p>
DREX1 is located in another network. It is in another building connected via vpn. The ip
for DREX1 is 192.170.100.51. There is no BACKUP network for this server<o:p></o:p>
(These are not the actual address, but the concept is similar)<o:p></o:p>
The dag network configuration is as follows.<o:p></o:p>
DAGNetworkDR has a subnet of 192.170.100.0/24; Network Interface of 192.170.100.51<o:p></o:p>
DAGNetwork01 (LAN) has a subnet of 192.168.100.0/24; Network Interfaces of 192.168.100.51
and 192.168.100.52<o:p></o:p>
DAGNetwork02 (BACKUP) has a subnet of 160.100.3.0/24; Network Interfaces of
160.100.3.51 and 160.100.3.52<o:p></o:p>
Last Friday, 3/7/14 something happened.<o:p></o:p>
To lead up to that, I noticed the issue because we have DPM 2010 making 15minute express
full backups of our exchange databases when I reviewed the backup jobs, the
exchange database backups using dpm2010 failed all weekend long starting at
11:00pm that Friday.<o:p></o:p>
The issue that occurred was that the database copies went to a status of Disconnected and
Resynchronizing, and after about 30 seconds, the status would show
Resynchronizing.<o:p></o:p>
All attempts to resolve this with the research methods failed. Deleting the
logs and reseeding failed, suspending, then rebuilding failed.<o:p></o:p>
Creating a new database worked, creating a database copy worked, but seeding the copy
failed. All with the same pattern, a status of Disconnected and
Resynchronizing, and after about 30 seconds, and the status would show
Resynchronizing.<o:p></o:p>
The database was mounted on EX2, and seeding to EX1
DREX1 has no issues.<o:p></o:p>
All the DAG networks were in a good status, all Green and all up. I could ping from
EX1 to EX2 and from EX2 to EX1 on both networks fine.<o:p></o:p>
In the middle of the week, about 3/12/14, we resolved the issue. We rebooted EX1, no
fix, but after rebooting EX2, it all resolved. It did a fail over to DREX1. I think it failed to do the failover to EX1. However, when it came back up, it was happy, it was reseeding slowly. After about an hour and a half, it
was all healthy.<o:p></o:p>
We thought it was all good EXCEPT, on Friday night at 11:00pmish on 3/14/14, the same
issue occurred; a status of Disconnected and Resynchronizing, and after about
30 seconds, the status would show Resynchronizing.<o:p></o:p>
The database was mounted on EX2 and seeding to EX1 again. I did not notice the
issue until I performed my review of the backup jobs again on Monday.<o:p></o:p>
Late Monday morning, my boss and I were looking at more articles, but all the same results,
delete the database copy and reseed. Which we knew would not work.<o:p></o:p>
I mentioned that it was strange because the networks were all up. What made us try the next
scenarios was just "luck" I guess. I made a statement about not remembering
which networks DAG replication took place over. Again, we have a LAN and
a BACKUP network. Bother were listed to use replication, so we decided to
disable replication over the BACKUP network in the EMC. Immediately, the
database copies switch to healthy and started seeding.<o:p></o:p>
Later that evening I enabled replication over the BACKUP network and it failed again with
a status of Disconnected and Resynchronizing, and after about 30 seconds, the
status would show Resynchronizing. I disabled the replication over the
BACKUP network and the database copy went back to healthy<o:p></o:p>
The last round of windows updates were pushed to these boxes the Friday before the
issues began, 2/28/14. I don't believe the updates to be the issue. <o:p></o:p>
Can anyone make any suggestions as to where to look? It worked with the BACKUP
network enabled to so long that is eluding me as to why the issues would start
all of a sudden. I am also confident that the switch configuration for the
BACKUP network has not been changed at all in at least 2-3 months. I am
still open to look at the config. Please help if you can.<o:p></o:p>
<o:p></o:p>
Lastly, this is more of a monitoring thing, if anyone can suggest a good way to monitor
the database copies so that I can be alerted when the status changes. We
use WhatsUpGold 16.2 to monitor the devices. <o:p></o:p>
Thanks for any future assistance.<o:p></o:p>
Ian
IanYou don't have to enable the Replication on Backup Network.
You should collapse your DAG network.
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
http://blogs.technet.com/b/samdrey/archive/2012/12/04/exchange-2010-dag-collapse-the-mapi-networks-in-a-dag.aspx
Post the result of Below command:
Get-DatabaseAvailabilityGroupNetwork
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. -
Exchange 2010 /hosting shared mailbox issue
Hello everyone.
I had an issue come up in our Exchange 2010 with /hosting switch deployment (currently at SP2).
We have several organizations and shared mailboxes configured and working on some. We add Full access permissions via Powershell + Send as rights and it auto configures and works just fine.
Last week though, one of several people that uses a specific shared mailbox started getting the error: "Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the
Microsoft Exchange Server computer is down for maintenance." (Error ID: 300)
The other users can still work just fine. Configuring the account in another PC shows the same problem (so it's not the local profile).
Creating 2 users, giving nr1 full access to nr2 generates the same error.
In another org though, i was able to give full access to another acount to an existing user and it worked (although the auto-mapping didn't, had to add it manually)
I'm out of ideias. Any sugestions?
EDIT: Did a couple more tests on another Org. On this one everything works with the shared folder access with old and new accounts but strangely the auto-mapping doesn't.
It seems that this is an issue with the mapping.
Hi,
From your description, I recommend you manually update or create your Outlook profile with RPC encryption and check the result. Here is the steps on Outlook 2007 for your reference:
1. Select your profile, and then click Properties, click E-mail Accounts.
2. Select the Microsoft Exchange Server account, and then click Change.
3. In the dialog box that contains your mailbox server and user name, click More Settings.
4. In the Microsoft Exchange Server dialog box, click the Security tab.
5. Click to select the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box, and then click OK.
6. Click Next, and then click Finish.
For more information, here is a kb for your reference.
Connection issues and error messages in Outlook for a mailbox on a server that is running Exchange Server 2010
http://support.microsoft.com/kb/2735060
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support -
Outlook 2013/Exchange 2010 Free/Busy access issues.
Good Day Everyone,
I am running a Win 2008 R2 environment with Win7 users, using Exchange 2010 and Outlook 2013. Last week my users started experiencing issues with being able to view Free/Busy in the Calendar for any other user. I have checked past issues with this with patches
KB 2837618 and KB 2837643. Neither patch is showing as installed and I have tried a nummber of the suggested fixes offered for that issue to no avail. OWA seems to be working just fine.
Our Outlook version is: 15.0.4605.1003
I need a fix for Outlook users and since I havve 140 users, individual fixes are a not realistic option.
Any assistance would be greatly appreciated.Hi,
Please test if Out of Office feature works well in Outlook. If Out of Office doesn't work either, it should be Autodiscover related.
Once Autodiscover has not been configured properly, the Free/Busy information may not display correctly. If you are also seeing issues with Out of Office assistant, we may assume that you haven’t correctly setup Autodiscover, since these two symtoms are
common when Autodiscover is not configured correctly.
To verify that, please test Outlook Autodiscover Connectivity:
http://technet.microsoft.com/en-us/library/bb123573.aspx
We can also learn Configure Exchange Services for the Autodiscover Service from:
http://technet.microsoft.com/en-us/library/bb201695.aspx
Regards,
Melon Chen
TechNet Community Support -
Exchange 2010 SP3 RU5 automapping issue - fixed in later RU?
Current Level: Exchange 2010 SP3 RU1
I'm planning on updating to RU8v2 but discovered
this thread indicating issues with RU5 + automapping + Office 2010 SP1. I couldn't find anyone reporting that the later RUs introduced the same issue or fixed it. So I'm just looking for anyone that may have experience with updating
past RU5 and still running Outlook 2010 SP1, did you see the same behavior with automapped mailboxes?That should have been done last October
http://blogs.technet.com/b/rmilne/archive/2014/10/14/office-2010-sp2-you-did-upgrade-right.aspx
take a peek at that post and sign up for the lifecycle status updates please.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter: LinkedIn:
Facebook:
XING:
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. -
Exchange 2010 SP3 startdagservermaintenance.ps1 issues
My Environment is as follows:
Production
Server 1 - CAS, Hub Transport (DAG witness server)
Server 2 - Mailbox (3 databases - DAG with Server 3) - Currently at SP1
DR Site
Server 3 - Mailbox, Hub Transport
I have Exchange 2010 SP3 applied to server 1 and 3. I have not been able to successfully run
StartDagServerMaintenance.ps1 on Server 2. If I am ok with downtime, is there any risk in upgrading my server without running this script? If so, would I need to power off Server 1 and 3 first? I believe my issue with the script may
be due to a journal mailbox.I assume you are talking about Updating Mailbox Server or you are just testing the script?
No you don't have to shutdown the server.
About the script, its suggestion to run it, but even if you are not running its ok.
By the way, how you are running the script? Are you running from the location where the script is residing.
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. -
Exchange 2010 SP2 RU2 - Client Issues
Hi,
I'm using Exchange 2010 SP2 RU2, Clinet Using Microsoft Office Professional Plus 2010,
facing some problem at some client side,
Problem 1. Unable to Create Subfolder in outlook and OWA
2. User able to sent mail but its showing in both folder Outbox and Sent Item
3. If recipient decline and propose new time for meeting, organizer unable to see new proposed time,
he has to reopen mail again then new time sync.
Action Taken 1. Create new Profile
2. Checked in OWA
3. Change the PC
4. Repair the MailBox
5. Moved the Mailbox to different DataBase
6. Permissions are ok ..etc....
Looking for Solution with reasons,
Thanks in Advance.
Hassan
Hassan TechnetExactly. Break this down into discrete items.
Also what build of Outlook? Is that patched?
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
And While Exchange 2010 SP2 is supported, you are well behind where I would like to see you. For a start you are missing several security updates in Exchange that can only be resolved by installing a newer RU
http://blogs.technet.com/b/rmilne/archive/2013/12/10/exchange-security-update-available-for-ms13-105.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter: LinkedIn:
Facebook:
XING:
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. -
Exchange 2010 SP3 Rollup 6 issue with Forefront
This rollup, 2936871, when installed on a server having Forefront Protection for Exchange Server integrated with Exchange services, causing Information Store not starting. For this we have to disable the integration and start the services. When again you
try to integrate and start the services, Exchange services will not start. So you should not integrate Forefront with Exchange services at all, finally.
Has anybody already in this soup?
Whether Microsoft has checked this? Any solution?
The error events are the below two:
Log Name: Application
Source: MSExchangeIS
Event ID: 9581
Task Category: Virus Scanning
Level: Error
Keywords: Classic
Description:
Error code 1 returned from virus scanner initialization routine. Virus scanner was not loaded.
Log Name: Application
Source: MSExchangeIS
Event ID: 9564
Task Category: General
Level: Error
Keywords: Classic
Description:
Error 0x1 starting the Microsoft Exchange Information Store.
Failed to start virus scan.Hi,
Hotfix Rollup 3 for Microsoft Forefront Protection for Exchange can address the issue that the Exchange Information store crashes with Forefront Protection for Exchange installed. I recommend you install Hotfix Rollup 3 for Microsoft Forefront Protection
for Exchange to check the result.
Here is a related article for your reference.
Description of Hotfix Rollup 3 for Microsoft Forefront Protection for Exchange
http://support.microsoft.com/kb/2538719/en#Fix4
Best regards,
Belinda
Belinda Ma
TechNet Community Support -
Exchange 2010 and Powershell v3 Issue
I decided to take the plunge pray and install powershell v3. I like it so far but I am having a few problems. One problem occurs when running the search-mailbox cmdlet. It starts to run and as soon as it seems like it's finished my powershell windows closes
arbitrarily. Event ID 4999 show in the application log. Same with ISE.
Watson report about to be sent for process id: 3480, with parameters: E12, c-buddy-RTL-AMD64, 14.02.0247.005, PowerShell_ISE, unknown, M.E.D.S.N.PropertyDefinitionSets.BuildWellKnownSets, System.TypeInitializationException, b3a, unknown.
ErrorReportingEnabled: False
- System
- Provider
[ Name] MSExchange Common
- EventID 4999
[ Qualifiers] 16388
Level 2
Task 1
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2012-10-03T18:07:40.000000000Z
EventRecordID 31189
Channel Application
Computer computer.domain.local
Security
- EventData
3480
E12
c-buddy-RTL-AMD64
14.02.0247.005
PowerShell_ISE
unknown
M.E.D.S.N.PropertyDefinitionSets.BuildWellKnownSets
System.TypeInitializationException
b3a
unknown
False
Another problem im having is warning messages that show when running some cmdlets before they actually run. They are always the same so far.
below is the warning...
WARNING: The cmdlet extension agent with the index 0 has thrown an exception in OnComplete(). The exception is:
System.TypeInitializationException: The type initializer for
'Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary' threw an exception. ---> System.NotSupportedException:
Not supported field(MailEnabled) type(Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition).
at Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary.PropertyDefinitionSets.BuildWellKnownSets()
at Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary..cctor()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition.TryFindEquivalentDefinition(PropTagKey key, Boolean
isCustom, PropType type, TypeCheckingFlag typeCheckingFlag, PropertyTagPropertyDefinition& definition, Boolean&
createNewDefinition)
at Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition.InternalCreate(String displayName, PropTag propertyTag,
PropertyFlags flags, TypeCheckingFlag typeCheckingFlag, Boolean isCustom, PropertyDefinitionConstraint[] constraints)
at Microsoft.Exchange.Data.Storage.PropertyTagCache.InternalPropertyDefinitionsFromPropTags(TypeCheckingFlag
propertyTypeCheckingFlag, MapiProp mapiProp, StoreSession storeSession, PropTag[] propTags, Int32& resolvedPropertyCount)
at Microsoft.Exchange.Data.Storage.RecipientTable.GetRecipientPropertyDefinitionsFromMapiTable(Boolean&
originalColumnsChanged)
at Microsoft.Exchange.Data.Storage.RecipientTable.BuildRecipientCollection(Action`2 recipientCollectionBuilder)
at Microsoft.Exchange.Data.Storage.CoreRecipientCollection..ctor(ICoreItem coreItem)
at Microsoft.Exchange.Data.Storage.CoreItem.Microsoft.Exchange.Data.Storage.ICoreItem.GetRecipientCollection(Boolean
forceOpen)
at Microsoft.Exchange.Data.Storage.CoreItem.GetRecipientCharsetDetectionData(StringBuilder stringBuilder, Boolean
isComplete)
at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.BuildCodePageDetector(MemoryStream& cachedHtmlBody)
at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.DetectCpidWithOptions(Charset userCharset, MemoryStream&
cachedHtmlBody)
at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.SetCachedBodyDataAndDetectCharset(Char[] cachedBodyData, Charset
userCharset, BodyCharsetFlags charsetFlags)
at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.CalculateCharset()
at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.OnBufferFull()
at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.CloseDetectorConversionStream()
at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.Flush()
at Microsoft.Exchange.Data.TextConverters.ConverterEncodingOutput.Flush()
at Microsoft.Exchange.Data.TextConverters.Internal.Text.TextCodePageConverter.Run()
at Microsoft.Exchange.Data.TextConverters.Internal.Text.TextCodePageConverter.Flush()
at Microsoft.Exchange.Data.TextConverters.ConverterWriter.Flush()
at Microsoft.Exchange.Data.TextConverters.ConverterWriter.Dispose(Boolean disposing)
at System.IO.TextWriter.Close()
at Microsoft.Exchange.Data.Storage.BodyTextWriter.<CloseWriter>b__11()
at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, LocalizedString exceptionString,
CtsCall ctsCall)
at Microsoft.Exchange.Data.Storage.BodyTextWriter.CloseWriter()
at Microsoft.Exchange.Data.Storage.BodyTextWriter.Dispose(Boolean disposing)
at System.IO.TextWriter.Dispose()
at Microsoft.Exchange.ProvisioningAgent.MailboxLoggerFactory.XsoMailer.Log(AdminLogMessageData data, LogMessageDelegate
logMessage)
at Microsoft.Exchange.ProvisioningAgent.AdminLogProvisioningHandler.OnComplete(Boolean succeeded, Exception e)
at Microsoft.Exchange.Provisioning.ProvisioningLayer.OnComplete(Task task, Boolean succeeded, Exception exception)
Exchange 2010 Version 14.02.0318.002
Problems occur on a Win7 client. The only thing that has changed was a powershell v3 install.
current powershell version shows version 3
any ideas?Powershell v3 is not (yet) supported with Exchange 2010:
http://technet.microsoft.com/en-us/library/ff728623.aspx
Alexei -
Lion, Exchange 2010. Mail loses all emails in an exchange account
I am running Lion on an new 2.0 GHz i7.
We are using Exchange 2010 SP1 and I have 2 exchange accounts setup in Mail. Every two weeks or so Iose all the emails in one of the accounts. After a few minutes Mail seems to realise, and startes resyncing all my emails. The mailbox is 2GB in size so this takes about an hour time during which Ihave no emails.
Fortunatly so far this has only happened while I'm working in the office but if it happened while Iwas work off-site it could take a lot longer to sync
The other exchange account has not had this problem.Since posting this Ihave archived my mailbox which has reduced it from 2GB to about 800 MB. I did have growlmail and dockstar addons running so I uninstalled them.
It seemed ok for 4 days, and I installed herald which is a notification addon (hate the fact that mac mail doesn't have any kind of notification of new emails) and guess what the issue has occurred again.
All emails dissappear and the whole mailbox has to re-sync.
I'm getting really frustrated with this and am being forced to consider using Outlook Mac 2011, something Ireally don't want to do.
Does apple actually look at these posts, can someone please help I really don't want to use Outlook
Maybe you are looking for
-
Input Seriously Needed - iMac G5
Let me start out by saying I have a VERY HARD TIME parting with my Macintosh computers. I use them until it simply is no longer feasible. I'm wondering if I am now at that point with my current Mac. Over the last few weeks, I've seen my G5 iMac slow
-
i need help with my imessage i am using a Iphone 4 ios 6.1.3 but when i go to settings>message>send and reecieve. i only get the options Apple ID: and You can be reached by iMessage at: my current email and add another email. my question is how do i
-
Can not log in to Creative Cloud. Repeatedly get "You've been signed Out" ... Rebooted, reinstalled, changed password. God, I am reallly starting to hate this... [ Private information removed by moderator ]
-
Change of boot screen resolution after projector connecting
Hi Guys, My boot screen's resolution was changed to 800 x 600 when connected to a projector and the screen resolution was returned to the previous set resolution at 1680 x 1050. However, the resolution of my dock icon was messed up (this can be confi
-
How to include DMS in module pool?
hello, i want to incorporate DMS[]Document data] in my module pool program, the same is there in MM03 transaction(document data).How can we do this? below is the syntax tht i have used. PROCESS BEFORE OUTPUT. *&SPWIZARD: PBO FLOW LOGIC FOR TABSTRIP