Hi team,
We are facing issue with ms exchange 2010 SP2.
We've configured the OWA for external url also open all the required port but cant access OWA from the outside of my network, please help
NA
Hi team,
We are facing issue with ms exchange 2010 SP2.
We've configured the OWA for external url also open all the required port but cant access OWA from the outside of my network, please help
NA
Gents, I'm a bit confused.
I don't see anywhere on TechNet description of 'Default' and 'Anonymous' accounts on permission tab for Public Folders.
There is some words for Anonymous account in Exchange 2003: http://technet.microsoft.com/es-es/library/aa996122(v=exchg.65).aspx
If you modify the default client permissions and roles on a mail-enabled public folder, make sure you maintain the Contributor role for the Anonymous account. Otherwise, mail sent to the public folder will be returned as undeliverable. When the public folder receives e-mail from a user who has no permissions on the folder, it treats the mail as a message posted using the Anonymous account.
But it's not true!
I added Contributor role for Anonymous account. 'Default' account has None rights.
I can send mail to PFs from external system, the message will be created in the PF.
But mail from internal user can't be delivered, I see NDR. There is no any domain [internal] Groups or users on permission tab on Public Folder, except my admin account.
I added CreateItems right for 'Default' account. Now I can send mail to this PF from any internal user.
Can anyone shed a light, what does mean 'Default' account on permission tab in Exchange 2010 SP2 ? How this user plays in the permission rights ?
Would be nice to see links to MS documentations/articles.
Thanks
mcse^4
Hi Folks,
Been struggling with getting autodiscover to work in our test lab. Lab is configured like our environment. Migrating from Exchange 2003. Have CAS role installed. OWA redirection works fine. Autodiscover internally works... I guess because of the SCP. But externally (through firewall) autodiscover does not work. I have done the following:
I am really stumped. Don't know what else to do. Any ideas will be greatly appreciated!
Thank you
What is involved with this?
We are still in coexistance with 2007.
We stood up a temporary mailbox db server before we purchased our 2 permanent mailbox servers that are in a HA DAG setup.
Now that we have added them into the environment, we want to transfer any public folder roles to a new DAG setup.
What is involved here?
Does it all have to be done through the public folder management console?
What ensures that the system public folders are :
1) moved completely off the legacy exch. 2010 db server.
2) replication for system public folder dbs for the 2 target mbx servers in DAG.
3) anything else to consider?
Josh
Hi,
Has anyone come across this issue? I am using EWS Managed API 1.2 to connect with Exchange Server 2010, when I try retreive a contact with email address having special characters I'll get the EmailAddress object but with null email in the Address property although if you look at Name property the value is there which is also in special characters. Please can you advise?
Thanks,
Rafeeq
12345
Hi all, in Exchange 2003 and 2010 mixed environment . Recently installed Exchange 2010 and migrated majority of users.
We have received several reports that Japanese character are not displayed correctly when reply or forward message.
I have found MS KB articles 95258 and 2642153.
http://support.microsoft.com/kb/952583 (Exchange Server 2007 SP1, Exchange Server 2010, or Exchange Server 2010 SP1 environment)
Our Exchange 2010 already has SP2 Ru4v2 applied, but when I open the 'EdgeTransport.exe.config' file,
the line <add key="PreferredInternetCodePageForShiftJIS" value="50220" />does not exist.
As KB2642153 states that this line should be added when you apply Sp2 RU2, I'm confused as to whether to add the line manually as stated in kb952583 which is intended forpre SP2RU2 Exchange2010?
Any help would be much appreciated.
cheers,
I'm trying to setup a hybrid connection with Office 365, but working through the wizard I keep getting stuck at the same point. The error message I see is:
Update-HybridConfiguration
Failed
Error:
Updating hybrid configuration failed with error 'Subtask ValidateConfiguration execution failed: Configure Mail Flow
at Microsoft.Exchange.Management.Hybrid.Engine.ExecuteTask(ITask taskBase, ITaskContext taskContext)
'.
I've seen other errors similar which seem to related to certificates but they had more info after "Configure Mail Flow", this doesn't and I'm stuck with how to resolve it.
Can anybody shed some light on why it's not working?
I am currently on SP2 RU5 V2. I had been looking into installing SP3, but am questioning if this is a smart move in my environment. We moved to Exchange 2010 about a year ago from 2003, and do not plan to move to 2013 in the near future.
From what I see, SP2 Ru6 includes all the same updates as SP3, with the exception of compatibility with Exchange 2013. Is that pretty much the case?
I have been reading some issues in general with RU6 and SP3, such as the inability to soft delete emails in some cases. Uninstalling a RU is not a big deal, but it looks like SP3 is an all in proposition, and there is no going back once you start without recovering servers.
I realize that in about a year, updates for SP2 will no longer be released, but at that point I would imagine a much more mature SP3 will be out there.
So is there any compelling reason at this time for me to go to SP3 and take on all the additional risk, or does it make more sense to just go with SP2 RU6 in this case.
In fact, with some of the issues with SP2 RU6, and no compelling security reason to update, I am thinking of skipping it all together and waiting for SP2 RU7 or SP3 RU1.
Any thoughts / experiences on this?
Hello all,
I hope that you are well !
I have a question for one of our customers.
I already completed Exchange migration in the future (2003-2010).
But I always wondering if a customer access is OWA with https://mail.abc.com/owa when is on Exchange 2003.
If we want to keep the same URL when we install Exchange 2010 in co-existence with Exchange 2003...is this possible.
I use to chose another URL for the migration so, instead of using https://mail.abc.com/owa we use https://webmail.abc.com/owa so it's much easier I think for certificate and so on...but maybe I am wrong.
Can anyone point me to correct configuration so I can retain mail.abc.com on a migration of Exchange 2003 to 2010.
Best regards,
Stephane
Hi,
I have an Exchange 2010 SP2 with MAILBOX+CAS+HUB and another server with EDGE role.
My problem is a user can only send(outside+inside) and cannot recive(outside+inside).
When I go to the Message Tracking the RecipientStatus of DELIVER is BONY...
I cannot find anything strange in EventVwr, User config....
Anyone can help me?
Thanks,
Xavier Parés | System Engineer | My Blog: http://microsoft-system-center.blogspot.com/
HI I am trying to do a cross forest migration of mailboxes. I have everything ready to move the mailboxes and it does it's prepare and addx the x500 to the source and the linked mailbox as a test i created the same distribution group at the destination forest and saw it put the user in the right group on the forest but anyone that is still left in the source organization can't send to those distro groups it bounces back since it doesn't know how to route to that distro group. what is the best way to handle this in the period of the mailbox moves
Thanks,
We were importing a PST into a user archive, and it failed part way through. We want to delete those PST emails that were successful from the archive, so we can import the entire PST again without duplication.
What is the best way to do this?Hello,
I have an Exchange 2010 SP1 where user A's e-mail address was requested by user B. I removed user A's e-amil address, changed their e-mail, and I gave that e-mail to user B.
User B can now receive e-mail fine from outside the network or from Webmail, but local Outlook clients who send to that e-mail are getting their e-mails sent to user A's mailbox.
I update the GAL on an Outlook client and checked to make sure that the GAL reflected the new user and it does. Still, local Outlook clients are still sending to the old mailbox.
Any ideas?
Hi,
I keep receiving an error message in the Event Logs for Exchange 2010:
The Module DLL D:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll failed to load. The data is the error.
Event ID: 2280 - IIS-W3SVC-WP
OWA is working.
In IIS- HTTP Redirect is Disabled On the Default Website.
we use Exch2003Org.
I saw the received MSG file by MFCMAPI.
Which property of MSG file,the legacyExchangeDN value is saved when receiving mail ?
We have a newer Exchange 2010 installation and I've got several mailboxes migrated. My mailbox is migrated and my iPhone 4S is syncing just fine. However, I just migrated two additional IT Dept mailboxes and neither user can access their mail from their smartphone. One has an Android and one has an iPhone 4. I see our firewall passing the traffic successfully. The android is getting a bad username or password error, despite using the correct username and password and the other iPhone is getting a cannot connect to mail error. Any idea where to begin troubleshooting when I know it is not a problem with the whole system since mine is working? In addition, I've made sure we are all not members of the AD Domain Admins group.
Hi all
I am currently trying to disable ActiveSync by default when creating new users
Here is my scriptingagentconfig.xml file:
<?xml version="1.0" encoding="utf-8" ?>
<Configuration version="1.0">
<Feature Name="MailboxProvisioning" Cmdlets="new-mailbox">
<ApiCall Name="OnComplete">
if($succeeded) {
start-sleep -s 10
$DC = [string]($readOnlyIConfigurable.originatingserver)
$newmailbox = $provisioningHandler.UserSpecifiedParameters["Name"]
set-casmailbox $newmailbox -activesync $false
}
</ApiCall>
</Feature>
</Configuration>
Here is the error:
Summary: 1 item(s). 1 succeeded, 0 failed. Elapsed time: 00:00:11 Ronnie5 Test5 Completed Warning: The cmdlet extension agent with the index 5 has thrown an exception in OnComplete(). The exception is: Microsoft.Exchange.Provisioning.ProvisioningException: ScriptingAgent: Exception thrown while invoking scriptlet for OnComplete API: Cannot bind parameter 'ActiveSyncMailboxPolicy'. Cannot convert value "False" to type "Microsoft.Exchange.Configuration.Tasks.MailboxPolicyIdParameter". Error: "Invalid cast from 'System.Boolean' to 'Microsoft.Exchange.Configuration.Tasks.MailboxPolicyIdParameter'.". ---> System.Management.Automation.ParameterBindingException: Cannot bind parameter 'ActiveSyncMailboxPolicy'. Cannot convert value "False" to type "Microsoft.Exchange.Configuration.Tasks.MailboxPolicyIdParameter". Error: "Invalid cast from 'System.Boolean' to 'Microsoft.Exchange.Configuration.Tasks.MailboxPolicyIdParameter'." ---> System.Management.Automation.PSInvalidCastException: Cannot convert value "False" to type "Microsoft.Exchange.Configuration.Tasks.MailboxPolicyIdParameter". Error: "Invalid cast from 'System.Boolean' to 'Microsoft.Exchange.Configuration.Tasks.MailboxPolicyIdParameter'." ---> System.InvalidCastException: Invalid cast from 'System.Boolean' to 'Microsoft.Exchange.Configuration.Tasks.MailboxPolicyIdParameter'. at System.Convert.DefaultToType(IConvertible value, Type targetType, IFormatProvider provider) at System.Boolean.System.IConvertible.ToType(Type type, IFormatProvider provider) at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider) at System.Management.Automation.LanguagePrimitives.ConvertIConvertible(Object valueToConvert, Type resultType, Boolean recursion, PSObject originalValueToConvert, IFormatProvider formatProvider, TypeTable backupTable) --- End of inner exception stack trace --- at System.Management.Automation.LanguagePrimitives.ConvertIConvertible(Object valueToConvert, Type resultType, Boolean recursion, PSObject originalValueToConvert, IFormatProvider formatProvider, TypeTable backupTable) at System.Management.Automation.LanguagePrimitives.ConvertTo(Object valueToConvert, Type resultType, Boolean recursion, IFormatProvider formatProvider, TypeTable backupTypeTable) at System.Management.Automation.LanguagePrimitives.ConvertTo(Object valueToConvert, Type resultType, IFormatProvider formatProvider) at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue) --- End of inner exception stack trace --- at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue) at System.Management.Automation.ParameterBinderBase.BindParameter(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, ParameterBindingFlags flags) at System.Management.Automation.CmdletParameterBinderController.BindParameter(CommandParameterInternal argument, MergedCompiledCommandParameter parameter, ParameterBindingFlags flags) at System.Management.Automation.CmdletParameterBinderController.BindParameter(UInt32 parameterSets, CommandParameterInternal argument, MergedCompiledCommandParameter parameter, ParameterBindingFlags flags) at System.Management.Automation.CmdletParameterBinderController.BindParameters(UInt32 parameterSets, Collection`1 arguments, CommandMetadata commandMetadata) at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParametersNoValidation(Collection`1 arguments) at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParameters(Collection`1 arguments) at System.Management.Automation.CommandProcessor.BindCommandLineParameters(CommandParameterInternal[] parameters) at System.Management.Automation.CommandProcessor.Prepare(CommandParameterInternal[] parameters) at System.Management.Automation.CommandProcessorBase.DoPrepare(CommandParameterInternal[] parameters) at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream) at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) --- End of inner exception stack trace --- at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentHandler.OnComplete(Boolean succeeded, Exception e) at Microsoft.Exchange.Provisioning.ProvisioningLayer.OnComplete(Task task, Boolean succeeded, Exception exception) Exchange Management Shell command completed: New-Mailbox -Name 'Ronnie5 Test5' -Alias 'Ronnie5' -UserPrincipalName 'Ronnie5@ad.DNSArrow.co.uk' -SamAccountName 'Ronnie5' -FirstName 'Ronnie5' -Initials '' -LastName 'Test5' -Password 'System.Security.SecureString' -ResetPasswordOnNextLogon $false -Database 'DB01' Elapsed Time: 00:00:11
Any ideas?
Regards
ronnie.jorgensen systems engineer
My blog
Hi,
We have several exchange 2010 servers with SP1 (and latest rollup-updates) located in several countries. Each Exchange server have their own administrator. Countries represented in separate Organization Units in Active Directory. It is Windows 2008 R2 DCs, single AD domain.
I have an intention to upgrade my Exchange 2010 SP1 to SP2, while the other remain in SP1 (since they all not maintained by me).
Additional note: i had just migrated exchange 2003 to exchange 2010 (new box). All mailboxes had been successfully moved to exchange 2010.
The questions:
a. Any issue may rise to other Exchange 2010 SP1 servers?
b. Any reference from Microsoft?
thanks in advance.
regards.
email address: TMeadows@domain.com
username/UPN: tim.meadows@domain.com
When I use outlook 2007, autodiscover works. I'm prompted to login during autoconfig.
I provide "tim.meadows@domain.com" and password. Works.
If I set it up with Outlook 2010 with autoconfig, it doesn't even prompt me for credentials.
Just goes to this page:
Not sure why its like that.
Here's what the exchange perms are on autodiscover Virtual Dir. on BOTH front end (CAS/HUB) servers:
· Anonymous Authentication: Enable
· ASP .NET Impersonation: Disabled
· Basic Authentication: Enabled
· Digest Authentication: Disabled
· Forms Authentication: Disabled
· Windows Authentication: Enabled
We use redirected autodiscover, and our testing on testexchangeconnectivity.org checks out.
Josh