AndersonPatricio.ca

Set-ADSiteLink error 4003 (INSUFF_ACCESS_RIGHTS) in Exchange Server 2010/2013

Hi Folks,

I got an error this last week where the user running Exchange Server 2010 wasn’t able to configure MaxMessageSize using Set-ADSiteLink cmdlet.

At the beginning I thought was something on his environment however since I was using Exchange Server 2013 on my Windows 8/Hyper-V 3.0 I tried to run the same cmdlet and I got the same issue ! Well, I tried in a couple of different Exchange Server 2010 and I got the same issue however if you run from an Exchange 2007 Management Shell it works like a charm!

Just to make sure that we are on the same page, here is the error message:

After analyzing the issue I noticed that the attribute delivContentLenght doesn’t allow the Exchange Trusted Subsystem to perform changes (Read and Write), so the solution is to open Active Directory Sites and Services, expand Sites, Inter-Site Transports, right-click on IP and then Properties.

Click on Security Tab, and click on Advanced button. In the new permissions tab, look for the entry that has Exchange Trusted Subsystem in the Name column and also Descendant Site Link Objects in Appy to column. After selecting the entry, click on Edit..

Make sure that you allow both Read delivContLenght and Write delivContLength and click OK on all other dialog boxes.

Time to test it! Let’s go back to the Exchange Management Shell and now we should be okay to define the MaxMessageSize from our Exchange Management Shell session.

---

Note: I couldn’t find an Official document from Microsoft supporting the Active Directory permission change however as you can see our change is just for that specific attribute.

---

Windows Server 2012 Hyper-V Component Architecture Poster

This poster provides a visual reference for understanding key Hyper-V technologies in Windows Server 2012. This Hyper-V poster focuses on Hyper-V Replica, networking, virtual machine mobility (live migration), storage, failover clustering, and scalability. You can find previously published posters here: • Windows Server 2008 R2 with SP1 Hyper-V Component Architecture• Windows Server 2008 R2 Hyper-V Component Architecture• Windows Server 2008 R2 Feature Component Poster • Windows Server 2008 Component Posters

Get it here: http://www.microsoft.com/en-us/download/details.aspx?id=29189

Exchange Server 2013 Preview: Anonymous permissions behaviour on Default Frontend Receive Connector

Hello folks,

You may have notice that Exchange Server 2013 has additional Receive Connectors to support the new architecture and we are going over them in a near future post however in Today’s post I would like to show you a small but still interesting improvement on the receive connector listening on 25 port.

By default on Exchange Server 2007/2010 wasn’t able to receive Internet traffic however in Exchange Server 2013 the connector responsible for 25 has the Anonymous checked as standard value which means that any relay to an accepted domain will be received without any additional configuration.

In order to check it out, open EAC (Exchange Admin Center), click on Mail Flow and then Receive Connectors and double click on Default frontend <servername>

Here we go.. the Anonymous is selected and you can relay right away messages on that connector. Cool, isn’t it?

Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio

Installing Exchange Server 2013 on Windows Server 2008 R2– Prerequisites…

Hi folks,

As you may have read on the Internet or even on this blog (www.andersonpatricio.ca) the Exchange Server 2013 Preview was released recently and in this post I will be going over the prerequisites required to install this new release on Windows Server 2008 R2. This Preview version can also be installed on Windows Server 2012 (topic for a near future blog post here!).

The installation process is well documented in the product documentation however I will go over and try to give you some hints to speed up the process and get you to the fun part which is to explorer the new features after installation.

Note: Bear in mind that we are working on a Preview version which mustn’t be installed on production environments!

In our scenario we have a brand new Domain Controller and a member server running Windows Server 2008 R2 with the latest Windows Updates.

Installing Operating System prerequisites..

Since we are going to deploy the new Exchange Server 2013 in a member server called POAEX13 and the schema will be prepared on that server as well, and for that reason we are going to add an extra feature to support the installation and schema preparation from this member server.

Basically we can open Server Manager and pick the features up however let’s use PowerShell to do that, these commands can be used

Import-Module ServerManager

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, RSAT-ADDS

Installing software prerequisites…

Exchange Server 2013 is a preview version and most of the software requirements will be fixed before it goes RTM, for now we need to a lot of manual work and since we are deploying in Windows Server 2008 R2 we will be listing all prerequisites. Just in case make sure that you update your Operating System with the latest Service Pack and Windows Updates before getting on this stage.

1. Microsoft .NET Framework 4.5 RC
   http://go.microsoft.com/fwlink/?LinkId=225702
   
2. Microsoft Management Framework 3.0
   http://www.microsoft.com/en-us/download/details.aspx?id=29939
   
3. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
   http://www.microsoft.com/en-us/download/details.aspx?id=30349
   
4. Microsoft Office 2010 Filter Pack 64 bit
   http://www.microsoft.com/en-us/download/details.aspx?id=17062
   
5. Microsoft Office 2010 Filter Pack SP1 64 bit
   http://www.microsoft.com/en-us/download/details.aspx?id=26604
   
6. Microsoft KB 974405 (Windows Identity Foundation)
   http://www.microsoft.com/en-us/download/details.aspx?id=17331
   
7. Microsoft KB 2619234
   http://support.microsoft.com/?kbid=2619234
   
8. Microsoft KB 2533623
   http://www.microsoft.com/en-us/download/details.aspx?id=26755

In order to keep track of the changes you can save each one of the packages above and assign a number based on the download order, the result will b similar to the one show in the figure below.

After installing all of them we need to remove (Yes, that is right!) the Microsoft Visual C++ 11 Beta Redistributable, as shown in the figure below.

We are good to go to start the installation process, tomorrow we will see how to deploy the first Exchange Server 2013 in a new forest. Stay tuned!

Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio

Download Microsoft Lync Server 2013 Preview

Microsoft® Lync® 2013 is an enterprise-ready unified communications platform. Lync connects people everywhere, on Windows 8 and other devices, as part of their everyday productivity experience. Lync provides a consistent, single client experience for presence, instant messaging, voice, HD video, and conferencing, and eliminates the need to use a VPN for encryption. Lync 2013 supports HD video conferencing and takes advantage of Windows 8 “touch first” capabilities to provide fast, natural, hands-on control of communications.

To evaluate Lync Server 2013 Preview’s new features, you need the Lync 2013 client application. Download Lync 2013 Preview as part of Office 365 ProPlus Preview or Office Professional Plus 2013 Preview.

Get it here: http://technet.microsoft.com/en-US/evalcenter/hh973393

Download Microsoft Exchange Server 2013 Preview

Hi folks,

It’s finally here the new Exchange Server is available and you we can start testing! Have fun!!

Microsoft Exchange Server 2013 enables you to maintain control, increase user productivity, and keep your organization safe. You can move to the cloud on your terms with flexible migration options. Your users can do more on any device, helping them manage increasing volumes of email and work together more effectively as teams. You can also protect your business communications and sensitive information, while meeting internal and regulatory compliance requirements. With Exchange Server 2013, you can work smarter, anywhere.

• Remain in control, online and on-premises.
  Exchange Server 2013 enables you to tailor your solution based on your unique needs and ensures your communications are always available while you remain in control, on your own terms - online, on-premises, or a hybrid of the two.
• Do more, on any device.
  Exchange Server 2013 helps your users be more productive by helping them manage increasing volumes of communications across multiple devices and work together more effectively as teams.
• Keep your organization safe.
  Exchange Server 2013 keeps your organization safe by enabling you to protect business communications and sensitive information to meet internal and regulatory compliance requirements.

Get it here: http://technet.microsoft.com/en-us/evalcenter/hh973395

Grande Abraco,
Anderson Patricio
http://andersonpatricio.wordpress.com
http://www.andersonpatricio.org
Twitter: @apatricio

Autoconfiguration was unable to determine your settings!

Hi folks,

One of my customers was saying that some machines were not able to retrieve the Autodiscover settings in Outlook internally with the following error message:

Before doing a deep drive on the server side I asked the guy a couple of simple questions, such as:

• Do you have success in different computers? The answer was yes.

• If you log on with a different windows profile on the same machine, does it work? the answer was Yes.

At this point the odds are that is an issue on the client side, just to be safe I went ahead and made sure that all Webservices URLs on the CAS servers on the site where the client was located had the same configuration and after some research I found out that there is a Registry Key that allows to change the Autodiscover behaviour on the client side.

Let’s open the regedit on the affected user and go to HKEY_CURRENT_USER\Software\Microsoft\Office\<OfficeVersion>\Outlook\AutoDiscover and on that key you may have the following entries:

• PreferLocalXML
• ExcludeHttpRedirect
• ExcludeHttpsAutodiscoverDomain
• ExcludeHttpsRootDomain
• ExcludeScpLookup
• ExcludeSrvLookup
• ExcludeSrvRecord

When the value of those keys are set to 1 you disable such feature, in my client I had all of them set to 1 and that was the reason for the issue. You can safely delete those or set them to 0 and then close and open Outlook and voilà Autodiscover is working like a charm again.

Note: The root cause of this issue (and that was on my case) was the Office 365/BPOS installed on the client however different applications/providers can take advantage of this registry key in your environment.

Establishing Exchange Content Index Rebuild Baselines

Hi Folks,

ExchangeTeam created a series of posts about Exchange Content Index Rebuild Baselines, here are the complete series, really good stuff!

• Establishing Exchange Content Index Rebuild Baselines – Part 1
  http://blogs.technet.com/b/exchange/archive/2012/06/25/establishing-exchange-content-index-rebuild-baselines-part-1.aspx
• Establishing Exchange Content Index Rebuild Baselines – Part 2
  http://blogs.technet.com/b/exchange/archive/2012/06/27/establishing-exchange-content-index-rebuild-baselines-part-2.aspx
• Establishing Exchange Content Index Rebuild Baselines – Part 3
  http://blogs.technet.com/b/exchange/archive/2012/07/02/establishing-exchange-content-index-rebuild-baselines-part-3.aspx