Hi

Ok I have tried in past to renew Exchange Cert using Shell, and I was confuesed , SO I am trying to new one today using Console.

I go to Server Configuration, and right click on my expired Cert(local Cert), and click on renew,

it goes through and creates one for me , Did not ask me what services, but I got the .Reg file. (completed fine)

now I have two Cert showing with the same names. New one is wanting to finish Pending(complete Pending Request), ,

where do I go from here?

I am reading about converting the REG file to 64 bit , and when I click on Complete Pending would I assign services, and after that del the old one.?

any help would be grate,

Thanks

Freddie

Hi all,

Exchange 2010 SP1

We set up the moderation mailbox for approval about 200 messages and unfortunately, the approver is out of office and got all expired messages which it says that it expired in two days.

Can anyone tell me where I can configure the approval time to more than 10 days?

Thank you.

I've seen some older posts about this so I thought I'd start a new one.

Currently running Active Directory 2003 with Exchange 2010 SP1 Rollup 3. I need to get AD current to support GPO options for Win 7 and Win 8 and would like to skip AD 2008 and go right to 2012.

Has anyone done this? Problems/Issues? Is it supported?

Thanks

Hi,

On the hub transport server exchange 2010 I am running out space on c: drive. I have notice that on C:\inetpub\logs\LogFiles\W3SVC1log files are getting very large. Can it be deleted or move some where else?

What is the best practice?

Cheers,

Hi, I am trying to add another email address to the default policy and it is not applying. I even tried creating a new policy which adds the new email address, but it is still not adding the address. Have you heard of this issue before? I'm not sure where to go from here.

Thanks

Hello,

we have Exchange 2010 SP2 Update Rollup 5 v2 with DAG installed. After having created a new user we try to set the mailbox regional configuration. 

1. Brand new user nothing changed:

Get-MailboxRegionalConfiguration newuser -DomainController DC01 | fl

Output:

RunspaceId                            : ae1e80db-0c12-45d5-9cc0-99f415e7357e

DateFormat                            :

Language                              :

DefaultFolderNameMatchingUserLanguage : False

TimeFormat                            :

TimeZone                              :

Identity                              :

IsValid                               : True

2. Setting the regional settings.

Set-MailboxRegionalConfiguration -Identity "New User" -Language pt-br

3. Checking the configuration

Get-MailboxRegionalConfiguration newuser -DomainController DC01 | fl

RunspaceId                            : ae1e80db-0c12-45d5-9cc0-99f415e7357e

DateFormat                            : d/M/yyyy

Language                              :

DefaultFolderNameMatchingUserLanguage : False

TimeFormat                            : H:mm

TimeZone                              :

Identity                              :

IsValid                               : False

WARNING: The object contoso.com/Users/New User has been corrupted, and it's in an inconsistent state. The following validation errors happened: WARNING: Neither DateFormat nor TimeFormat can be set before a language is selected.

When doing the same on Exchange 2010 SP2 UR2 or Exchange 2013 (both in seperate testing environment) we do not get any failure.

Thanks in advanced for your help.

I have a user when she replies to an outside email, the recipient email address gets changed to the local smtp addressing and it tries to deliver it locally.  Of course, the mailbox is not local so she gets an NDR.  It doesn't matter if the recipient is listed in our GAL or not. She seems to be the only person this is happening to, or that has reported it.  I've tried looking through the event logs but not really sure what to be looking for.

We are Exchange 2010, user is Outlook 2010.  All service packs and updates have been applied to both

Hi there,

I have recently transitioned to Exchange 2010. However, all the mailboxes are still on the Exchange 2003.

The email is flowing, OWA is working. Exchange 2010 seem to redirect in and outboud emails properly (to, from Exchange 2003)

The one thing I've noticed since "flipping" the switch (pointing my mail.domain.com to Exchange 2010 instead of 2003) all my mobile phones (IPhones, Androids, ) have lost connection to email. Now, if i switch the mail server on the mobiles to: "legacy.mydomain.com" the connection is re-established. Unfortunately, I have way too many mobiles to do this manually on every single one. Additionally, once the transition is complete, I'll have to re-do this process again (mail server back to mail.riddell.ca). I am sure I am missing something simple here.

Any idea as to why Exchange 2010 is not proxying / redirecting ActiveSync to 2003?

PS I did apply KB937031 patch on the Exchange 2003 server and enabled Integrated Windows Authentication (Image).

Thank you,

I have a group of 4 users that manage a shared mailbox. The mailbox is fairly busy with 300 sends/recieves per day. It is also 10 GB in size. We migrated them from Exchange 2003 to 2010 and they started to experience Outlook issues, such as freezing and lockup.

We migrated back to a 2003 server and the issues went away. Also, they never had any of these issues while on 2003.

We have SCOM and have no performance issues with our 2010 servers. I have also monitored with perfmon and not found an issue.

My questions are, is Exchange 2010 inherently slower in managing shared mailboxes?

Has anyone else experienced slowness with shared mailbox upon migrating from 2003?

Thanks,

Paul

Hello,

I have been asked to look at a clients exchange environment, this environment has been a bit of a nightmare, all in all they had 3 different consultants configure different parts of the environment and things are a little on the messy side.

2 CAS servers EXCAS1 and EXCAS2 in an array named CASARRAY. Two mailbox servers EXMBX1 and EXMBX2 in a DAG.

They are not using Outlook Anywhere, their remote users VPN into the network.

OAB down

Autodiscover succeeds as follows:

SMTP=admin@example.com

Attempting URL https://casarray.contoso.com/autodiscover/autodiscover.xml found through SCP

Autodiscover to https://casarray.contoso.com/autodiscover/autodiscover.xml starting

getlasterror=0; httpstatus=200.

Autodiscover to https://casarray.contoso.com/autodiscover/autodiscover.xml Succeeded (0x00000000)

Symptoms :

Password prompt when opening outlook, at first cancelling this would occasionally lock out the user account. I have since deployed kerberos and this can now be cancelled without affecting outlook usage.

Password prompt when clicking on public folders before kerberos you could not access the folders if this was cancelled, now even if cancelled it functions fine.

If a computer is rebooted, the credentials cleared (credential manager), klist purge and outlook profile repaired. The machine runs perfectly with no password prompts for approximately half an hour and then the issue begins to recurs. 

What I have done so far......

Confirmed all virtual directories are set to windows authentication with ignore SSL. I also recreated the autodiscover directory from scratch.

Deployed Kerberos to the CAS array - since this has been done the password prompts no longer affect access or lock out accounts but they are still a major annoyance.

Set the CASARRAY RPCclientaccess to encryption required and restarted the RPC and AB services.

The addressbook logging shows kerberos as the authentication method but I found it unusually that some log entries were from contosogroup/contoso/recipients and some were from contosogroup/exchange administrative group/recipients .

Now I know that there was a botched outlook 2003 decommissioning by a previous consultant and I have attempted to remedy to the best of my abilities, (ADSI, Registry, Manual Removal, etc etc) but I believe something may still remain somewhere.

If anyone has any questions I am ready and willing to try pretty much anything to get this resolved.

I really appreciate any input anyone has on these issues as I am rapidly running out of ideas.

Regards,

Adam Cooperman - MCP - MCSA - MCSE - MCTS x 4

I have several users who are missing sent items

Case in point

A user sent an email to a fellow employee who in turn replied to the email, however the senders original is nowhere in the sent items folder. I then had the user to log on to OWA to see if it was in the sent items on the server(wondering if its an outlook or exchange issue) and it wasnt there either. His sent items contained the message before and a message after this one. We know it was sent because the user replied to it.

Hi, according to http://technet.microsoft.com/en-us/library/ee681659%28v=exchg.141%29.aspx, "You can add new configuration options".

I tried this with a simple <testoption></testoption> in the configuration section and the transport service failed to restart. So, how does one go about adding a new configuration option?

Hi,

I have recently renewed the certificates installed on the Exchange Server. After renewing the certificates, the operations manager has started raising alerts for Test-PopConnectivity and Test-ImapConnectivity.

The test cmdlets executed by Operations Manager is as follows.

[PS] C:\Windows\system32>Test-ImapConnectivity -MonitoringContext:$true -ConnectionType:2 -TrustAnySSLCertificate:$true
-LightMode:$true | fl

RunspaceId : f8c188ad-c51a-456c-ab20-cbb866f182d5
LocalSite : site1
SecureAccess : False
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 993
ConnectionType : Ssl
ClientAccessServerShortName : EXMB
LocalSiteShortName : Site1
ClientAccessServer : EXMB.domain.local
Scenario : Test IMAP4 Connectivity
ScenarioDescription : Connect to server using IMAP4 protocol, search for the test message, and delete it along
with any messages that are older than 24 hours.
PerformanceCounterName : ImapConnectivity-Latency
Result : Failure
Error : Microsoft.Exchange.Monitoring.ProtocolException: Authentication failed. The connection is
being closed.
The handshake failed due to an unexpected packet format.Server response while making conn
ection:[]. ---> System.IO.IOException: The handshake failed due to an unexpected packet f
ormat.
UserName : extest_f10dfb492f884
StartTime : 1/28/2013 5:41:04 AM
Latency : 00:00:00.0030756
EventType : Error
LatencyInMillisecondsString :
Identity :
IsValid : True

RunspaceId : f8c188ad-c51a-456c-ab20-cbb866f182d5
Events : {Source: MSExchange Monitoring ImapConnectivity
Id: 1011
Type: Success
Message: The Client Access server configuration check succeeded., Source: MSExchange Monitoring I
mapConnectivity
Id: 1007
Type: Success
Message: Credentials were successfully loaded for all test mailboxes in the local site., Source:
MSExchange Monitoring ImapConnectivity
Id: 1006
Type: Success
Message: There were no errors loading credentials for the test mailboxes that exist on mailbox se
rvers in the local site., Source: MSExchange Monitoring ImapConnectivity
Id: 1001
Type: Error
Message: IMAP4 connectivity transaction has failed. Detailed information:
Target: EXMB.domain.local|Site1

Error: Microsoft.Exchange.Monitoring.ProtocolException: Authentication failed. The connection is
being closed.
The handshake failed due to an unexpected packet format.Server response while making connection:[
]. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.

Details:

Client Access server: EXMB.domain.local
Mailbox server: exmb
Mailbox database: Mailbox LA-TX
Mailbox: extest_f10dfb492f884@domain.local
Port: 993
Connection type: Ssl
TrustAnySSLCertificate: True.
Connecting to server
Disconnecting from the server.
Client Access Server Name: EXMB.domain.local
Scenario: Test IMAP4 Connectivity
Scenario Description: Connect to server using IMAP4 protocol, search for the test message, and de
lete it along with any messages that are older than 24 hours.
User Name: extest_f10dfb492f884
Performance Counter Name: ImapConnectivity-Latency
Result: Failure
Site: Site1
Latency: 00:00:00.0030756
Secure Access: False
ConnectionType: Ssl
Port: 993
Latency (ms): 3.0756
Virtual Directory Name:
URL: null
URL Type: Unknown
Error:
Microsoft.Exchange.Monitoring.ProtocolException: Authentication failed. The connection is being c
losed.
The handshake failed due to an unexpected packet format.Server response while making connection:[
]. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.

PS: I haven't restarted my server after renewing the certificate. Similar alert is generated for Test-ImapConnectivity also.

I have checked and confirmed that a certificate is already assigned to the service POP, IMAP and IIS. But, note that the name of the server in the certificate is not the same as that of the internal hostname of the server. The event viewer also has entries similar to the following.

Log Name:      Application
Source:        MSExchangeIMAP4
Date:          1/29/2013 6:48:10 AM
Event ID:      1102
Task Category: (1)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      exmb.domain.local
Description:
The IMAP4 service failed to connect using SSL or TLS encryption. No valid certificate is configured to respond to SSL/TLS connections. Check the configured host name as well as which certificates are installed in the Personal Certificates store of the computer.

Please do tell me if any one requires any further information which will help for a conclusion.

Thanks in advance.

Tom Jacob

Hello,

My friends i have problem with exchange the memory utilization 83% i have Server with specification :

Exchange server 2010 Standard   installed in windows server 2008 Standard 

HP proliant DL 380 G7

intel xeon cpu E5645 2.4GHz (12 CPU)

RAM 12GB

The size of Storage 12 Giga Byte 

Number of users : 41  users

Note: some times the exchange have delay 

i wait for your helping

Hi<o:p></o:p>

We've recently had a fail-over event with out 3 node Exchange 2010 DAG, where our primary mailbox server went offline.<o:p></o:p>

Technically everything worked, with one small exception. When the fail-over occurred  the Databases associated with the server moved to the correct node, based on the activation preference ID. The actual DAG name space, however, started to reference the other node in the setup.<o:p></o:p>

Essentially Node1 went down, Databases activated on Node2 but when I RDP to the DAG namespace it connects to Node3. The reason this is an issue, is because our mailbox backup jobs target the DAG namespace, and Node3 doesn't have a backup agent installed. Obviously, because of this, backups didn't go through last night. <o:p></o:p>

Is there any way to control the order of namespace fail-over similar to activation preference for databases in exchange 2010?<o:p></o:p>

Thanks,<o:p></o:p>

Hello All-

We have an environment with an Account forest and and Exchange 2003 forest.  Up until now, there were no trusts between these environments, and users would need to authenticate to Outlook separately.  The idea is to upgrade to Exchange 2010, and then subsequently convert the mailboxes to linked mailboxes, and connect them to their Account forest object, thereby removing that second authentication.

My question revolves around the Outlook profile piece.  It seems to me that after the conversion to a linked mailbox, Outlook would simply connect to Exchange, with out credential prompts and without a need to reconfigure the Outlook profile (mailboxes are the same, just now the currently logged in user has required permissions) - but I was hoping to see if anyone has done this and what the typical client behavior is.

Thanks in advance!

roc

Hello,

We recently configured a NEW Exchange 2010 server that performs all basic exchange functions. We are not using a Microsoft Edge service/program. This server is on a dedicated fibre line and has exceeded all minimum requirements to run on our domain. We are also using a Barracuda Spam and Virus Firewall 300 for our SPAM/AV solution.

We have noticed that a large portion of our "Off Domain" users (Outlook Anywhere) are experiencing issues with connections to the Exchange Server on startup. This connection issue can last anywhere from 2-15 minutes before Outlook connects to Exchange. In addition to this issue, ALL Outlook Anywhere users are prompted for their passwords on Outlook startup. After they enter in their passwords, it does not prompt them until they close and reopen the program. This is not happening with users connected via VPN.

For troubleshooting, we have:

-Tested cached credentials in the Credential Manager - Did not resolve

-Configured both BASIC and NTLM authentication on IIS

-Set NTLM as the default Auth method and Negotiate as the secondary

-Ran MS Connectivity tests on TestExchangeConnectivity. We continually get  the same error when testing RPC/HTTP connectivity with a fail on Attempting to log on the the Exchange Information Store. The error shown is "The Store logon failed with unknown error 1003"

We have tried other things but I cannot remember all actions at this point. Can anyone help as I am pulling out the last of my hair.. lol