Deploying the Lync 2013 Client On Mismatched Windows/Office Architecture

Just a quick note when dealing with deploying the Lync 2013 client when the Windows architecture doesn't match the currently installed flavor of Office.

Lync 2013 x64 can only be installed on 64-bit Windows, but what if 32-bit Office is installed on that 64-bit Windows machine? Since a lot of organizations upgrade Office in steps according to budgets, you'll see this quite often.

In order for Lync to install and not throw an error; you have to first uninstall Office, then install Lync, then re-install Office. It's a pain, but there's no way around it.

If you're running something like SCCM, you can create scripts that will roll off Office, install Lync and then re-install Office, silently.