Hi all,

Windows 2012, single Exchange 2013 CU2 environment, fresh install.

I have been unable to get the Exchange toolbox to load in mmc either locally on the Exchange server or from a Windows 8 system with the Exchange management tools installed. The error I get is: 

FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}

Type is not resolved for member
'Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataAdapterInvocationException,Microsoft.Exchange.Configuration.ObjectModel,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Exception Type:

System.Runtime.Serialization.SerializationException

I am unable to run the Exchange Management shell either.

I have found a number of forum threads here that mention this or similar error situations and have tried the advice given, but so far no luck. 

The reason I am particularly interested in the toolbox is that I am troubleshooting a problem for a user who is complaining about delayed mail delivery.

George

George Merriman gwm@gsi-bkln.com Gravesend Systems Inc. Brooklyn NY USA

Hi I'm new to PowerShell and I've been attempting to migrate an Exchange 2010 SP3 Public folder to Exchange 2013. I'm following the directions found athttp://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx .

I have gotten to Step 3 .\Export-PublicFolderStatistics.ps1 <Folder to size map path> <FQDN of source server>

It runs the command but when it attempts to write the CSV to the drive I get:

Export-csv : Access to the path '\\servername\sharename' is denied

I am running the Exchange PowerShell in Administrator mode

Within File Manager I have given:

the share Everyone Full permissions

NTFS Full permissions to:

Everyone, Domain Admins, Domain Users, Exchange Servers, Exchange Organization Admins,

PS] C:\Windows\system32>C:\ps_scripts\Export-PublicFolderStatistics.ps1 "\\server\sharename" server.domain.local
[11/21/2013 9:59:42 AM] Enumerating folders under NON_IPM_SUBTREE...
[11/21/2013 9:59:50 AM] Enumerating folders under NON_IPM_SUBTREE completed...25 folders found.
[11/21/2013 9:59:51 AM] Retrieving statistics from server SERVER
[11/21/2013 9:59:52 AM] Retrieving statistics from server SERVER complete...45 folders found.
[11/21/2013 9:59:52 AM] Total unique folders found : 45.
[11/21/2013 9:59:52 AM] Exporting statistics for 45 folders
[11/21/2013 9:59:52 AM] Exporting folders to a CSV file
Export-CSV : Access to the path '\server\sharename' is denied.
At C:\ps_scripts\Export-PublicFolderStatistics.ps1:221 char:70
+ $script:ExportFolders | Sort-Object -Property FolderName | Export-CSV <<<<  -Path $ExportFile -Force -NoTypeInformati
on -Encoding "Unicode";
    + CategoryInfo          : OpenError: (:) [Export-Csv], UnauthorizedAccessException
    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.ExportCsvCommand

[PS] C:\Windows\system32>

We attempted a exchange 2013 install in a coexistence scenerio. Getting the following error during the install process. Any ideas?

Cesar Contreras | Network Administrator | CCNA

Anand_N

Hey all,

I have begun migrating our exchange 2010 setup over to 2013, I have setup two CA servers with live IP addresses and one MD server on a local range, both CA servers are loadbalanced, external and internal URL's are setup to go to  the external load balanced url (for now call it owa.bla.com) a wild card SSL has been installed onto the servers and OWA is accessible via https  with the correct ssl.

imap and pop3 are another matter all together, when assigning the ssl to the system it says I need to use powershell it says this:

 This certificate with thumbprint XXXX and subject '*.blah.com' cannot used for POP SSL/TLS connections because the subject is not a Fully Qualified Domain Name (FQDN). Use command Set-POPSettings to set X509CertificateName to the FQDN of the service.

pushing forward I went to the CLI and used set-popsettings -x509certificatename "owa.blah.com" which was successfully completed. going back to ECP I attempted to run this again with no love.

digging further into it I ran a get-popsettings |fl  and get the following information:

seeing this I tried to change the ExternalConnectionSettings to match the certificate name (also tried the internalconnectionsettings)

and got this:

any thoughts?

servers are setup like so:

ca-1.blah.net (live ip) 

ca-1.office.blah.net(internal server)

ca-2.blah.net

ca-2.office.blah.net

both of these are load balanced onto owa.bla.com

Let me know if you need any more information.

I'm interested in peoples views on if there is a standard setup for my particular scenario or any methods you could recommend.

High level overview is a Main office and a branch office, around 30 people in each. Currently 1 exchange 2007 server at the main office and a 2003 server at the remote office - 2 different domains and namespace. Plan to bring these together under one domain with VPN links for the  2 sites.

Whats the recommendation for Exchange - 2 exchange servers with a mailbox role at the branch office or just one exchange server at the main office accessed over the VPN.

I would be interested to hear peoples opinions.

Thanks

Dear All,

I'm trying to install Exchange Server 2013 in the windows server 2012 (PC2) that already join a domain in another windows server 2012 (PC1) as a DC.

But always it's appear the below error on step 7 of 14:

Error:

The following error was generated when "$error.Clear();

                set-ExchangeServerRole -Identity $RoleFqdnOrName -IsHubTransportServer:$true -DomainController $RoleDomainController" was run: "The domain is invalid. Property Name: Domain".

i have checked if the server has SPN setup correctly as the below steps, and it's looks fine to me without any problem.

a. On the domain controller, open adsiedit

b. Expand to Domain,CD=Computer,

c. Right-click CN=<var>serverName</var>, and then clickProperties.

d. In the Attributes list, click servicePrincipalName, and then clickEdit.

e. Under Values, make sure that it contains the following Value: HOST/ServerNetBiosName

so please i need your help.

Thanks

I'm on one of my last steps in migrating from 2010 to 2013.  When I issue the command to  Resume the migration request after the Autosuspend happens, I get a StalledDueToMailBoxLock, and it retries but never completes.  I've removed the request and tried it again, but I get the same thing.  The requests were 24 hours apart.  I have no clients that are connecting to the 2010 server anymore, and all the user mailboxes have been migrated to 2013 successfully.  I haven't found much online about this status, so I'm at a loss.  By the way, this is during my Public Folder migration process.  Sorry for leaving that out.

Thank you.

Dear all

During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :

 The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
;
          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;" was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
wa' on 'MONAMBX2'.".

     The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
;
          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;" was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
und on 'MonaDc1.mona.local'.".

Any advice please !!

I have exchange 2013 with TMG 2010.

Running Autodiscover test on testexchangeconnectivity.com shows

	The Microsoft Connectivity Analyzer is attempting to test Autodiscover for erik@contoso.com.
	Autodiscover was tested successfully.
	Additional Details
	Test Steps

I created the TMG Outlook Anywhere rule as per http://www.microsoft.com/en-us/download/details.aspx?id=8946 and also a OWA TMG rule all on the same listener with FBA 

When i start Outlook 2013 on my home pc (non-domain joined) and add an account and fill in the Outlook Wizard my name and mail erik@contoso.com with password i click next and i receive error 

Looking on TMG error&logs i see:

TMG Log type: Web Proxy (Reverse) Status: 12309 The server requires authorization to fulfill the request. Access to the Web server is denied. Contact the server administrator. Source: 68.144.93.168:63357 Destination: 10.1.250.5:443Request: POST http://autodiscover.contoso.com/autodiscover/autodiscover.xml Filter information: Req ID: 0fd0e583; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=no, logged off=no, client type=unknown, user activity=yes Protocol: https User: anonymous

 &

TMG Log type: Web Proxy (Reverse) Status: 0x80004005 Source: 68.144.93.168:63357 Destination: 10.1.250.5:443 Request: POST http://autodisover.contoso.com/autodiscover/autodiscover.xml Filter information: Req ID: 0fd0e584; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=no, logged off=no, client type=unknown, user activity=yes Protocol: https User: anonymous

We are currently used a non-named hosting provider and want to bring Exchange in house. 

I am considering the pro's and con's of utilizing a Split Domain scenario, with the hosted server as teh primary, my question is once you go down that route and then want to un-do the split domain - is it possible to do this and only have the internal mail server?

I see that my internal server will become a sub-domain, what are the implications for my mailboxes - can I easily move the content from one to the other? 

If this is not advised, what would you suggest?

Thank-you

Hi,

I am performing a migration to a hybrid exchange deployment.

I have looked on the deployment assistant for autodiscover dns information but it just says I need autodiscover.domain.com externally pointing to my on premise CAS which I already have from my current deployment.

My question is... If a user mailbox gets moved to office 365 how does autodiscover work to redirect them to the cloud service for their URL's?

Can someone give me a high level description for internal and external outlook users?

i.e. external user: connect to cas using public autodiscover.domain.com A record, on premise CAS provides alternative autodiscover URL??

***Don't forget to mark helpful or answer***

Hi!

Fresh 2013 install.
Default web site is set to redirect requests to https://server/owa. 
SSL is required.
Custom error for 403.4 is redirect to https://server/owa

Opening http://server redirects fine to https://server/owa but once the user is logged in, the site redirects back to https://server (no OWA in the URL)

This causes the site to look like the attached picture, because all the file paths are wrong. https://server/14.3.123.3/themes/resources/clear1x1.gif does not exist, the OWA part is necessary.

Any ideas why it redirects out of the OWA directory and to the root after login? If I type in OWA manually the themes are OK. But for some reason everything except the themes load even without the OWA part.

I was unable to access Exchange via Exchange Management Shell.
Below is the error message:
VERBOSE: Connecting to exchange.domain.com.
New-PSSession : [exchange.domain.com] Processing data from remote server exchange.domain.com failed with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
VERBOSE: Connecting to exchange.domain.com.
New-PSSession : [exchange.domain.com] Processing data from remote server exchange.domain.com failed with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
.
.
.

-    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:

I tried to access the Exchange using browser, https://localhost/ecp or https://192.168.1.10/ecp, i able to login. But after login the browser displays blank.

The last thing i did was re-create a self-sign certificate.

Anyone can help?

Hello. 

I want to uninstall an exchange server, but because there are mailboxes I can't. I also can't delete the mailboxes because I cannot gain access either to the ecp or managment shell. 

ecp returns a 404 error and the managment shell gives this error: 

VERBOSE: Connecting toexchange.domain.local.
New-PSSession : [exchange.domain.local] The WinRM service cannot process the request because the request needs to be sent
to a different machine. Use the redirect information to send the request to a new machine.  Redirect location reported:
 https://exchange.domain.local/owa . To automatically connect to the redirected URI, verify "MaximumConnectionRedirectionCount" property of session preference variable "PSSessionOption" and use "AllowRedirection" parameter on the cmdlet.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportRedirectException
    + FullyQualifiedErrorId : RedirectInformationRequired,PSSessionOpenFailed.

Any help would be greatly appreciated. 

I'm getting ready to create my first DAG adn see I need to create a disabled user account. Our Exchange servers reside in a child domain, but i see all the systemmailboxes reside in the forest root domain.

Should the DAG accoutn be created in the forest root, or the Exchange server domain?

Tom

Hi all.

I've been working on setting up Exchange 2013 in our Exchange 2007 environment.  I've managed to install it, configure it, move a handful of mailboxes, and fix several issues (2013 users being asked to login, free/busy maximum settings mismatch, Autodiscover not really updating the settings in Outlook clients...).  However, I'm stuck on getting Exchange 2013 users to access Exchange 2007 public folders.  Because the new server is very much in a development stage, I can't migrate the public folders over and won't until the mailboxes are thoroughly tested and fully migrated.

According to the public folders FAQ at http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx, it's both possible and impossible to get new users to access legacy folders.

From "Considerations:"

Exchange 2013 no longer supports public folder databases. Therefore, there’s no coexistence with legacy public folders. As a result, Exchange 2013 is unable to read from the hierarchy stored in a public folder database on Exchange 2010 or Exchange 2007 servers.

From "Migrate public folders from previous versions:"

...However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously....

I did originally start to build the master hierarchy in 2013 before finding this page, but I have since deleted the hierarchy from Exchange and from AD via ADSIEdit.

When a 2013 user tries to access a 2007 public folder, they are met with "Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems of the Exchange server is down for maintenance. (<correct info about the the legacy 2007 server's DN>)"

I've reviewed the RPC logs from the new server and am seeing what looks like a proper redirect command to the Outlook client.  But the Outlook client can't connect to the public folders.

I've tested public folders in OWA and they don't work there.  I've verified that the services are started on both the new and old servers.  And I've used the Outlook Connection Status tool to observe how Outlook seems stuck in a perpetual "connecting" state to the old mail server, even when I'm not trying to access a public folder.

So my question then, is using Exchange 2013 to access Exchange 2007 public folders actually possible or not?  If so, what else can I check to find out why I can't open legacy public folders?  We need to access some of the shared folders for collaboration, and I'm trying to avoid moving the upgraded users back into Exchange 2007.  This seems to be about the last major problem I have before I can start migrating all of the other users.

Thanks!

Alan

PS - Microsoft, please update your Exchange 2013 Public Folders FAQ to clarify if this is possible or not.  You state both in two adjacent sections.

Hi, I am having an issue with Autodiscover not passing EXPR attributes which is causing Outlook client connection issues.  My auto discover repsonse looks like this:

Autodiscover Account Settings

Basically the response isn't passing EXPR settings at all.  I have tried running Remove-OutlookProvider EXPR and then New-OutlookProvider EXPR, Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.domain.com

When I run Get-OutlookProvider everything looks normal with the EXPR settings but they are still not being passed via auto discover.  Any ideas on how to resolve this?

Hi, I couldn't find a separate forum for Exchange 2003 / 2010 so I hope it's OK to ask here.

We have several sites that have single servers that are both Domain Controllers (2003 Server) and Exchange Servers (Exchange 2003).  I am involved in migrating these to separate virtual Windows 2008 R2 servers in Hyper-V.  The DC roles get transferred to one virtual 2008R2 server, and Exchange 2003 gets migrated to Exchange 2010 running on the other virtual 2008R2 server.

What's the correct way to do this ?  We've tried a couple of different ways but everything we've done so far seems to break Exchange once AD is transferred to the new DC.  The last time we migrated Exchange over fine, then made the new DC virtual machine into an additional DC, transferred roles then demoted the original physical DC and Exchange 2010 broke (presumeably something to do with the DC name changing, even though the domain is unchanged).

Any tips or pointers would be great !

Thanks !