Exchange 2010 and Avamar Granular Restore (GLR)

Make sure you have the latest software;
- AvamarClient-windows-x86_64-Latest-Version.msi
- AvamarExchangeVSS-windows-x86_64-Latest-Version.msi
- Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

Create a new User called AvamarBackupUser and create a mailbox; test that the mailbox can receive and send emails.

Add the AvamarBackupUser to the following Groups;
- Domain Admins
- Backup Operators
- Exchange Servers
- Organisation Management

Give the AvamarBackupUser the appropriate Permissions on your mailboxes

get-ExchangeServer exchangeserver | Add-AdPermission -user AvamarBackupUser@comain.com -extendedrights Receive-As, Send-As

- Install the software listed above onto your Exchange Servers.
- Set the Logon Account for the Avamar Backup Client and Avamar GLR Service to use the AvamarBackupUser and restart the services.

In the Avamar Folder “C:\Program Files\avs\var” you need to create a file called avexchglr.cmd with the following text.

--cas_override=anycasserver.domain.com

(please note the two dashes –)

This is important; if you are using a CASArray you need to add the following into your HOSTS file to point Avamar to your CAS Server; in my case our CasArray was called Outlook.domain.com and our CAS Server was on IP 192.168.100.100

HOSTS File
192.168.100.100        outlook.domain.com    outlook

The reason the HOSTS file needs poisoned is so Avamar will use the CAS Server rather than in my case a Load Balanced CAS Array where the Load Balancer was blocking the dynamic ports required for the restore.  You can choose not to poison the HOSTS file but you will need to punch extra holes into your Load Balancer to allow the Restore to take place.

*Make sure that IPv6 is disabled.

Exchange 2013 RTM CU2 Part Deux!

FIX for loss of public folder permissions when the public folder mailbox is moved between Exchange 2013 databases.

The new build number of Exchange 2013 RTM CU2 is 15.0.712.24.

The previous build number of Exchange 2013 RTM CU2 was (15.0.712.22)

More information can be found here; as always please check the comments prior to installation!

System Center 2012 Service Pack 1 Update Rollup 3

Issues that are fixed in this update rollup…
- App Controller Update (KB2853227)
- App Controller Setup Update (KB2823452)
- Data Protection Manager Update (KB2853210)
- Operations Manager Update (KB2852565)
- Operations Manager - UNIX and Linux Monitoring (Management Pack Update)
- Virtual Machine Manager Administration Console Update (KB2858509)
- Virtual Machine Manager Server Update (KB2858510)
- Virtual Machine Manager Guest Agent Update (KB2858511)

More information can be found here;

Now you c: me now you don’t

Could the latest iteration of SkyDrive that is baked into Windows 8.1 do away with the c: drive as we we know it?

Placeholder files look and feel like normal folders and files. You can tap or click a folder and see all the folders and files inside it. You can move, delete, copy, or rename placeholder files just like you would any folder or file. SkyDrive only downloads the full file when you access it. Placeholder files contain a thumbnail image along with some basic properties and file content. This means that the placeholder file is significantly smaller in size that the file in SkyDrive, so when you need to use it only then will the file be downloaded.

 

Offline Access with the SkyDrive app allows you to mark any folders or files you want for offline access. Edits on this device or another device will be synchronized so that you’re always working with the latest file.

Any Windows Store app can use the Windows file picker to let you open, edit, and save any kind of file. In Windows 8.1, SkyDrive is built into the file picker – so every Windows Store app can save files directly to SkyDrive without any extra work. And the files will quietly get uploaded in the background so you don’t have to wait around. For example, if someone shares pictures with you in an email, you can save them to SkyDrive from the Mail app.

More information can be found here;

Reverse Proxy for Exchange Server 2013 using IIS

The Windows team have added an additional component called Application Request Routing 2.5 to the Internet Information Service (IIS) role, which enables IIS to handle reverse proxy requests.

By using the URL Rewrite Module and Application Request Routing you can implement complex and flexible load balancing and reverse proxy configurations.

There are three options when implementing this solution and each have their pro’s and con’s.

Full article can be found here;

Gartner: Magic Quadrant for x86 Server Virtualization Infrastructure

More information can be found here;

Exchange 2013 RTM CU2 Issues with Public Folders

This issue only occurs within native Exchange 2013 environments that are leveraging Modern Public Folders. The issue exists when you move public folder mailboxes. The specific issue is that if you move a public folder mailbox, there is the potential for the permission structure on some public folders to be lost. Specifically:

1. If you move (via New-MoveRequest) a secondary public folder (PF) mailbox, the permissions on any public folder (including well known folders) not stored in the secondary PF mailbox would be lost from the secondary PF mailbox and replaced by the default ACL. The original ACLs can be restored via a full synchronization event by executing Update-PublicFolderMailbox -InvokeSynchronizer <Public Folder Mailbox> -FullSync.
2. If you move (via New-MoveRequest) the primary PF mailbox, the permissions on any public folder (including well known folders) not stored in that public folder mailbox are lost and replaced by the default ACL.

The default ACL gives Author permissions to Default authenticated users.

Recommendation

If you have already deployed Exchange 2013 RTM CU2 (712.22) and have Modern Public Folders in your environment, we recommend you do not move public folder mailboxes so that you do not experience this issue. We will be releasing an IU that will address this issue in the near future.

If you are in the midst of a migration to Exchange 2013 and will not be deploying Modern Public Folders for some time, you can proceed with installing Exchange 2013 RTM CU2 (712.22). Once you are ready to deploy Modern Public Folders ensure you have deployed the soon-to-be-released Interim Update or the latest available Cumulative Update.

More information can be found here; please read comments prior to installing Exchange Updates as history has shown a litany of foobars!

One Microsoft: Company realigns to enable innovation at greater speed, efficiency

From: Steve Ballmer
To: Microsoft - All Employees
Date: July 11, 2013, 6 a.m.
Subject: One Microsoft

Today, we are announcing a far-reaching realignment of the company that will enable us to innovate with greater speed, efficiency and capability in a fast changing world.

Today’s announcement will enable us to execute even better on our strategy to deliver a family of devices and services that best empower people for the activities they value most and the enterprise extensions and services that are most valuable to business.

This company has always had a big vision — to help people realize their full potential. In the earliest days, it was by putting a PC on every desk and in every home. We’ve come farther than we could have imagined. The impact we have collectively made on the world is undeniable, and I am inspired when talented new hires say they chose Microsoft because they want to change the world — that’s what we do today, and that’s what we’ll do tomorrow.

More information can be found here;

A picture paints a thousand words …

Exchange Server 2013 RTM Cumulative Update 2

Servicing Model Update

In the new Exchange servicing model customers will continue to receive assistance from Microsoft Support for the lifecycle of the Exchange server product - a customer is not required to be at the most current CU to receive assistance. There are two scenarios that we would like to clarify though:

(1) If during the course of a support incident it is determined that the solution is available in a published CU (e.g., CU2), the customer will be required to install the update that contains the fix. We will not be building a new fix to run on top of a CU published earlier (e.g., CU1).

(2) If during the course of a support incident it is determined that you have discovered a new problem for which we confirm a fix is required, that fix will be published in a future CU that you can then install to correct the problem reported.

Changes in Exchange 2013 RTM CU2
In addition to bug fixes, Exchange 2013 RTM CU2 introduces enhancements in the following areas:

Per-server database support
OWA Redirection
High Availability
Managed Availability
Cmdlet Help
OWA Search Improvements
Malware Filter Rules

The final build number for Exchange 2013 RTM CU2 is 15.0.712.22.

More information can be found here; download and release notes.

As always please read the comments here just in case!

TechNet Subscriptions Sayonara

Microsoft is retiring the TechNet Subscriptions service to focus on growing its free offerings, including evaluation resources through the TechNet Evaluation Center, expert-led learning through the Microsoft Virtual Academy, and community-moderated technical support through the TechNet Forums to better meet the needs of the growing IT professional community.

The last day to purchase a TechNet Subscription through the TechNet Subscriptions website is August 31, 2013. Subscribers may activate purchased subscriptions through September 30, 2013.

More information can be found here;