As with one of my previous posts for Microsoft Lync Server 2010 where I documented the permissions for the databases created on the back-end server for a Lync Server 2013 pool: Microsoft Lync Server 2010
As most VMware View administrators know, VMware’s Windows 7 Optimization Guide: VMware-View-OptimizationGuideWindows7-EN.pdf … suggests that the Windows Search service should be disabled and executing any of the provided scripts will do so: What happens when
I recently had to migrate a small office off of Microsoft Office 365 to a different hosted Exchange environment and had to find a way to extract their existing mail stored in Office 365 into
One of the semi new features I’ve been interested in since Lync Server 2013 was initially announced was the new Persistent Chat Server that replaces the Group Chat server. Those who have worked with the
I’ve noticed that I’ve been asked several times about why federated contacts are no longer reachable after a user is moved from a Lync Server 2010 pool to a Lync Server 2013. The following are
I’d like to first state that I’m in no way a WDS (Windows Deployment Services) expert as desktop deployment was always a realm that I never really got into. With that being said, I get
Problem You have just attempted to deploy a new enterprise pool but the Publish Topology process fails to deploy the databases properly and the only option is to delete the failed deployment’s pool. You proceed
Problem You attempt to move a user from a Lync Server 2010 pool to Lync Server 2013 pool: … but the operation throws the following error: Failed while updating destination pool. Solution This is actually
First off, I’ve been asked by a few ex-colleagues about where the Office Web Apps documentation is because it doesn’t look like it’s included in the Lync Server 2013 RTM documents and the answer to
Problem You attempt to publish a new enterprise pool from Topology Builder but notice that it fails with the following: Creating Database SQL-Server-FQDNInstance… Completed with errors Reviewing the logs show the following errors: InstallDatabaseInternalFailure: An
