Installing .NET 3.5.1 on Windows 2012 – Error 0x800F081F

Recently, when trying to install Office 365 Dirsync, I ran into an issue with the installation of .NET 3.5.1 as a feature.  I received the error:

Error: 0x800F081F

The Source files could not be found

Since this was a newly installed server, it was baffling as to what the issue was.  After some troubleshooting, I determined there were two causes:

  1. The windows Component Store was damaged
  2. A hotfix KB2966827 had already been installed that causes this issue.

To resolve these issues, I did the following:

  1. I ran DISM /Online /Cleanup-Image /RestoreHealth to repair the Component Store. (http://blogs.technet.com/b/joscon/archive/2012/11/30/how-to-troubleshoot-error-0x800f081f-when-installing-roles-and-features.aspx)
  2. I determined if KB2966826, KB2966827, or KB2966828 were installed, and uninstalled them until after .NET 3.5.1 was installed. (http://www.askvg.com/fix-0x800f0906-and-0x800f081f-error-messages-while-installing-net-framework-3-5-in-windows-8/) After installing .Net 3.5.1, you can safely re-install the hotfixes.
Posted in Uncategorized | Leave a comment

Exchange 2013 – Outlook Online Mode – Search Folders Break!

I ran into a new issue that I wasn’t aware of until now.  When Exchange 2013 was RTM’ed, it was known that OWA no longer supported Search Folders.  Those are the folders you can create in Outlook that show a specific filtered view of your mailbox.  Those can contain items like UnRead Items, Missed Conversations, Call Logs, Flagged Email, Categorized Email, etc…  I personally don’t use Search Folders, but I know that many people do.  I also know a few organizations that have standardized their desktop infrastructure using one brand or another of VDI.  Within their VDI solution, they have chosen to deploy Outlook 2010 or 2013 in Online mode and their internal Exchange 2013 servers have been scaled to support Online Mode.  

This lays the groundwork for the problem.  Outlook cached mode, along with many other features, is this mode that maintains the finder info on the local PC. Since the finder information is no longer synchronized to the Exchange 2013 server store, the server doesn’t store finder information any longer (which indecently is one of the reasons why Search Folders are no longer offered in OWA).  In Online Mode, the users still can try to use Search Folders, and they appear to work until they try to interact with the messages shown in the Search Folder.  Actions like Delete will produce an error message that tells the user (depending on Outlook version) that either the message can’t be found, or better yet, “Unknown Error”.  

The solution is to enable Cache Mode, full stop.  I have not yet confirmed this with the Exchange Product Team but it is my belief that since Office 365 utilizes Cache Mode exclusively and since cache mode is now supported in VDI deployments, that this is by design.  

Posted in Cache Mode, Exchange 2013, Online Mode, Outlook, Search Folders | Tagged , , , , , | Leave a comment

Exchange 2013 – Outlook Online Mode – Search Folders

I ran into a new issue that I wasn’t aware of until now.  When Exchange 2013 was RTM’ed, it was known that OWA no longer supported Search Folders.  Those are the folders you can create in Outlook that show a specific filtered view of your mailbox.  Those can contain items like UnRead Items, Missed Conversations, Call Logs, Flagged Email, Categorized Email, etc…  I personally don’t use Search Folders, but I know that many people do.  I also know a few organizations that have standardized their desktop infrastructure using one brand or another of VDI.  Within their VDI solution, they have chosen to deploy Outlook 2010 or 2013 in Online mode and their internal Exchange 2013 servers have been scaled to support Online Mode.  

This lays the groundwork for the problem.  Outlook cached mode, along with many other features, is this mode that maintains the finder info on the local PC. Since the finder information is no longer synchronized to the Exchange 2013 server store, the server doesn’t store finder information any longer (which indecently is one of the reasons why Search Folders are no longer offered in OWA).  In Online Mode, the users still can try to use Search Folders, and they appear to work until they try to interact with the messages shown in the Search Folder.  Actions like Delete will produce an error message that tells the user (depending on Outlook version) that either the message can’t be found, or better yet, “Unknown Error”.  

The solution is to enable Cache Mode, full stop.  I have not yet confirmed this with the Exchange Product Team but it is my belief that since Office 365 utilizes Cache Mode exclusively and since cache mode is now supported in VDI deployments, that this is by design.  

Posted in Cache Mode, Exchange 2013, Online Mode, Outlook, Search Folders | Tagged , , , , , | Leave a comment

Exchange Server 2010 SP1 RTM!!

So, I have been working with the Exchange TAP and Product Group for months now waiting to make this announcement.  Finally, after months of testing and Microsoft making many improvements, Service Pack 1 for Exchange Server 2010 is officially here and publically available! 

You can see the RTM blog post here.

You can get more information what is in SP1 on my blog as well as TechNet.

The official SP1 bits can be downloaded here.

All I can say is go forth and download as this is the icing on the Exchange 2010 cake…

Posted in Exchange 2010 | Leave a comment

Load Balancing Exchange 2010

In this article, I want to discuss the reasons why Load Balancing is important to Exchange 2010 and what you can do about it.  There seems to always be a big discussion with the customers I work with on why this is necessary, what needs to be balanced, and how to do it. 

So, why is this needed? 

Load balancing is a way to manage which of your servers receive traffic. Load balancing provides failover redundancy to ensure your users continue to receive Exchange service in case of computer failover or switchover. It also enables your deployment to handle more traffic than one server can process while offering a single host name for your clients.

Several changes in Exchange 2010 make load balancing important for your organization. The Exchange RPC Client Access service and the Exchange Address Book service on the Client Access server role improve the user’s experience during Mailbox failovers by moving the connection endpoints for mailbox access from Outlook and other MAPI clients to the Client Access server role instead of to the Mailbox server role. In earlier versions of Exchange, Outlook connected directly to the Mailbox server hosting the user’s mailbox, and directory connections were either proxied through the Mailbox server role or referred directly to a particular Active Directory global catalog server. Now that these connections are handled by the Client Access server role, both external and internal Outlook connections must be load balanced across the array of Client Access servers in a deployment to achieve fault tolerance.

A load-balanced array of Client Access servers is recommended for each Active Directory site and for each version of Exchange. It isn’t possible to share one load-balanced array of Client Access servers for multiple Active Directory sites or to mix different versions of Exchange or service pack versions of Exchange within the same array.

Key Concept for Load Balancing Exchange 2010

Understand the key technology differences in load balancing solutions.  These can affect the Performance, Manageability, Failover detection and automation, and Affinity options available.

So why can’t I use Windows NLB? 

There are a few scenarios in which you will not want to or cannot use WNLB.

  • WNLB can’t be used on Exchange servers where mailbox DAGs are also being used because WNLB is incompatible with Windows failover clustering. If you’re using an Exchange 2010 DAG and you want to use WNLB, you need to have the Client Access server role and the Mailbox server role running on separate servers.

  • Due to performance issues, we don’t recommend putting more than eight Client Access servers in an array that’s load balanced by WNLB.

  • WNLB doesn’t detect service outages. WNLB only detects server outages by IP address. This means if a particular Web service, such as Outlook Web App, fails, but the server is still functioning, WNLB won’t detect the failure and will still route requests to that Client Access server. Manual intervention is required to remove the Client Access server experiencing the outage from the load balancing pool.

  • WNLB configuration can result in port flooding, which can overwhelm networks.

  • Because WNLB only performs client affinity using the source IP address, it’s not an effective solution when the source IP pool is small. This can occur when the source IP pool is from a remote network subnet or when your organization is using network address translation.

    • Your organization has a reverse proxy server that communicates directly with the Client Access server and not through the WNLB virtual IP address. The reverse proxy server hides the client IP addresses from the Client Access server array. Therefore, source IP affinity won’t work as expected. However you may still want to use WNLB to load balance internal traffic.

    • Your organization has many clients accessing your Client Access servers through a very small set of IP addresses. WNLB tends to affinitize an entire class C subnet to one Client Access server.

Ok, so I want to use a Hardware Load Balancer.  Now what…

You need to review what capabilities, as mentioned above your solution has.  Is it a reverse proxy based solution such as Forefront Threat Management Gateway or Unified Access Gateway?  What Affinity options does it support?  These could be (more details are available at http://technet.microsoft.com/en-us/library/ff625247.aspx) :

  • Cookie Based Affinity
  • SSL Session ID
  • Source IP
  • or No Affinity

Microsoft has published at summary of Load Balancer Options which you will want to review prior to making your decision. 

Solution Client to Client Access server affinity Failover method Capacity Cost

Hardware load balancer

Depending on the protocol and client, fall back between the following:

  1. Existing cookie
  2. Load balancer-created cookie
  3. SSL ID
  4. Source IP

Automatic failover with minimal client downtime. Hardware load balancers also are able to provide failover for a specific protocol.

++++

$$$

Software load balancer in a separate server layer

Note: TMG and UAG are the only workable solutions for external traffic.

Either load balancer-created cookie or source IP, depending on the protocol and client.

Automatic failover with minimal client downtime.

++

$$

Software load balancer in the same server layer as the Client Access server (WNLB)

Source IP.

Automatic failover with minimal client downtime.

+

$

DNS round robin

Each client gets a random Client Access server IP address.

Manual steps to detect issues and failover. Client DNS caches cause slow failover. This solution breaks affinity for some protocols such as Outlook Web App, Exchange Web Services, and Exchange Control Panel.

+++

$

No load balancer

Separate host names are manually assigned for each Client Access server.

Manual steps to detect issues and failover. Client DNS caches cause slow failover.

+

N/A

 

 

If you need help finding hardware load balancer options, Microsoft has a qualification program for vendors to signup for which then gets their product listed on the Microsoft site for Unified Communication Load Balancers.  This list is available at http://technet.microsoft.com/en-us/office/ocs/cc843611.aspx

Posted in Uncategorized | Leave a comment

What’s new in Outlook 2010

Well, Microsoft has published an detailing all of the new features in Outlook 2010.  There is a lot of new or improved features in this version, and as I said , this release of Outlook and Office 2010 for that matter are a fantastic example of when Microsoft listens to customers and responds with much needed updates.

Some of the changes detailed in the article are:

  • 64 bit and 32 bit versions
    • Just be careful that your add-ins will work with the 64 bit version.
    • Also, you must install the entire Office Suite in the same “bitness”, no intermixing of 32 and 64 bit.
  • Calendar preview in the meeting request
    • You no longer have to click on view calendar to see what in the world is conflicting with that new meeting request you just got.
  • Conversation view and Conversation cleanup
    • This enables you to see the entire conversation even if parts of it are not in the same folder and you can have Outlook delete parts of the conversation you have in newer messages.
  • Multiple Exchange Accounts
    • Currently, I have 4 mailboxes open against 3 different Exchange Orgs, all using Outlook Anywhere.  How cool is that!
  • Tighter integration with OCS and Communicator
  • Roaming Auto Complete (Nicknames)
    • Remember the fun NK2 files, they are now a thing of the past.  Your personal auto-complete list (Nicknames) are now stores in Exchange and go where you go.
  • And if you have Exchange 2010 to boot, you also get these:
    • Call answering and routing rules
    • Centralized Rights Management
    • Integrated Email Online Archive
    • Mailtips
    • Text Messaging through Exchange Activesync
  • Many many more…

Some of the items that have been removed are:

  • ANSI OST File creation support (Unicode will be used only)
  • Calendar rebasing tool (to fix DST issues)
  • WebDav protocol
  • Exchange 2000 and earlier server version connections
  • Most Recently Used list (this was the list of last opened “Other User’s Folders).
  • ScanOST.exe
  • Postmarking of email to signify it isn’t junk email.
  • Quick View (this was the file viewer in Windows 95, 98, and NT4)
  • Remote Mail (now replaced fully with Cache Mode)
Posted in Outlook | Leave a comment

Tests Prove: Windows 2008 R2 Much Better for Exchange 2010!

Well, Microsoft has just released a new blog post showing their test results comparing Windows 2008 SP2 and Windows 2008 R2 and Exchange 2010 when under an Outlook Anywhere load.  Lets face it, Outlook Anywhere is the way of the future!  I know for me, I have to be able to work anywhere, anytime, and I don’t want to worry about VPN solutions and firewalls, so Outlook Anywhere is the answer. 

So, how does R2 help you say?  It provides 10 times smaller CPU usage for the same number and type of OA users, thanks how.  This appears to be due to the significant performance improvements made to the RPC/HTTP feature in R2.  And in case your wondering, this should also benefit Exchange 2007 SP3 (when it becomes publicly available). 

Another way to look at this, as pointed out by the Microsoft blog post is that using identical hardware for both OS versions, R2 supported 14,000 OA users, while SP2 only supported 6,500!

 

Check out the source at: http://msexchangeteam.com/archive/2010/04/30/454805.aspx

 

Posted in Client Access Server, Exchange 2010 | Leave a comment