OWA 2013 (RTM & CU1 Upgrade) Virtual Directory Displays The OWA Version As Exchange 2010

ByRajith Enchiparambil May 20, 2013

A bug or typo in the code? While browsing the EAC, I noticed that the OWA virtual directory displays that the OWA Version as Exchange 2010 & not 2013. This happens in an Exchange 2013 only environment. The Shell displays the same info. MS, Is it a bug in the code or a typo? Update:…

A bug or typo in the code?

While browsing the EAC, I noticed that the OWA virtual directory displays that the OWA Version as Exchange 2010 & not 2013. This happens in an Exchange 2013 only environment.

The Shell displays the same info.

MS, Is it a bug in the code or a typo?

Update: The issue is the same in Exchange 2010 RTM and if you have moved from RTM to CU1. Fresh install of CU1 fixes the issue.

Rajith Enchiparambil

Cloud Architect & Blogger with interests in Microsoft 365, Azure, AWS & PowerShell. I am active on Experts Exchange & TechNet forums and I am a technical author for SearchExchange. Follow me on Twitter, LinkedIn, or Facebook for the latest updates. For consultancy opportunities, drop me a line.

9 Comments

Christian Schindler says:

at

Your screenshots indicate that you’re running Exchange 2013 RTM Code. RTM is Build 516.32. In CU1 this was fixed. On my CU1 System the OwaVersion is displayed as “Exchange 2013”. CU1 is Build620.29. Regards Christian

Reply
1. Rajith Jose Enchiparambil says:
  
  at
  
  Hi Christian,
  
  Post has been updated, the issue is still there if you upgrade from RTM to CU1. I think a fresh CU1 install has no issues.
  
  Thanks.
  
  Reply
  1. Jean-Luc Ch. says:
    
    at
    
    Hi Rajith,
    
    I think too. You can delete and recreate OWA virtual directories, and the shown version is correct.
    Cheers
    
    Reply
    1. Rajith Jose Enchiparambil says:
      
      at
      
      Thanks Jean-Luc.
      
      Reply
Christian Schindler says:

at

As the pictures show, obviously you’re running Exchange 2013 RTM Code. Build 516.32 is RTM. In CU1 this was fixed. CU1 Build Number is 620.29. Christian Schindler

Reply
Turbomcp says:

at

cool catch
bad for scripting:)

Reply
1. Rajith Jose Enchiparambil says:
  
  at
  
  Thanks TurboMCP
  
  Reply
shawn says:

at

Going to check mine but i think this symptom is only applicable to RTM,not CU1.

Reply
1. Rajith Jose Enchiparambil says:
  
  at
  
  Hi Shawn,
  
  Issue exists if you upgrade from RTM to CU1. Fresh install seems to be ok.
  
  Reply

9 Comments

Leave a Reply Cancel reply