Deploy & Configure Office Web Apps Server for SharePoint 2013 on Windows Server 2013

Step 1: Install prerequisite software for Office Web Apps Server:

1. Open the Windows PowerShell prompt as an administrator and run this command to install the required roles and services.

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features,NET-Framework-Core 

Step 2: Install Office Web Apps Server:

1. Download Office Web Apps Server from the http://www.microsoft.com/en-eg/download/details.aspx?id=35489
2. Open the .img file directly and run Setup.exe.
3. On the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and click Continue.
4. On the Choose a file location page, select the folder where you want the Office Web Apps Server files to be installed (for example, C:\Program Files\Microsoft Office Web Apps) and select Install Now. If the folder you specified doesn’t exist, Setup creates it for you.
5. When Setup finishes installing Office Web Apps Server, choose Close.
6. Download and install the Office Web Apps Server update KB2810007.

Step 3: Install language packs for Office Web Apps Server:

1. Download the Office Web Apps Server Language Packs from the http://www.microsoft.com/en-eg/download/details.aspx?id=35490
2. Run WebAppsServerLP_en-us_x64.exe.
3. In the Office Web Apps Server Language Pack 2013 Wizard, on the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and select Continue.
4. When Setup finishes installing Office Web Apps Server, choose Close.

Note: 

• To install language packs after the Office Web Apps Server farm is created, you must remove a server from the farm, install the language pack on it, and then add the server back to the farm.
• For a language pack to work correctly, you’ll need to install it on all servers in the farm.

Step 4: Deploy the Office Web Apps Server farm:

New-OfficeWebAppsFarm –InternalURL "http://servername" -AllowHttp 

Parameters–InternalURL is the name of the server that runs Office Web Apps Server, such as http://servername.
–AllowHttp configures the farm to use HTTP. 
–EditingEnabled enables editing in Office Web Apps when used with SharePoint 2013. This parameter isn't used by Lync Server 2013 or Exchange Server 2013 because those hosts don't support editing


Note

If Windows PowerShell doesn’t recognize the New-OfficeWebAppsFarm cmdlet when you runit, you may need to import the OfficeWebApps module. Use this command:
Import-Module -Name OfficeWebApps
Step 5: Open an elevated SharePoint 2013 Management Shell:

Right-click SharePoint 2013 Management Shell to display the app bar.
In the app bar, click Run as administrator.


Step 6: Create the binding between SharePoint 2013 and Office Web Apps Server:

Run the following command, where <WacServerName> is the fully qualified domain name (FQDN) of the URL that you set for the internal URL. This is the point of entry for Office Web Apps Server traffic. For this test environment, you need to specify the –AllowHTTP parameter to allow SharePoint 2013 to receive discovery information from the Office Web Apps Server farm by using HTTP. If you don’t specify –AllowHTTP, SharePoint 2013 will try to use HTTPS to communicate with the Office Web Apps Server farm, and this command won’t work.

New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP

Step 7: View the WOPI zones for the SharePoint bindings:

Office Web Apps Server uses zones to determine which URL (internal or external) and which protocol (HTTP or HTTPS) to use when it communicates with the host, in this case, SharePoint 2013. By default, SharePoint Server 2013 uses the internal-https zone. Run the following command to see what your current zone is.

Get-SPWOPIZone

Step 8: Change the WOPI zone to internal-http

If the result from Step 3 was internal-https, run the following command to change the zone to internal-http. You need to make this change because the zone of SharePoint 2013 must match the zone of the Office Web Apps Server farm.

Set-SPWOPIZone –zone “internal-http”

Verify that the new zone is internal-http by running Get-SPWOPIZone again. 

Step 9: Change the AllowOAuthOverHttp setting in SharePoint 2013 to True
To use Office Web Apps with SharePoint 2013 over HTTP in a test environment, you need to set AllowOAuthOverHttp to True. Otherwise Office Web Apps won’t work. You can check the current status by running the following example.
(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()
Run the following command again to verify that the AllowOAuthOverHttp setting is now set to True.
(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
That is set, Good Luck :)
Refernces:
http://technet.microsoft.com/en-us/library/jj219455.aspx
http://technet.microsoft.com/en-us/library/ff431687.aspx

Update Polycom CX700 version 3

Jiff has mentioned all required steps in the following articles:

Updating Lync Phone Edition Devices:

http://blog.schertz.name/2011/01/updating-lync-phone-edition-devices/

Updating Lync Phone Edition Devices for Lync 2013:

http://blog.schertz.name/2013/05/updating-lync-phone-edition-devices-lync-2013/

Hide users from the Lync Address Book

First, on one of your Lync Front End servers, install the Lync Server 2010 Resource Kit. You can download it here.

Next, on the server using Windows Explorer, browse to C:Program FilesMicrosoft Lync Server 2010ResKit and double click the application named ABSConfig. You’ll be presented with the UI below.

Firstly, you’ll see a list of AD Attribute Names. To achieve this, we need to create a new one and specify the AD Attribute we want to use to filter accounts. Here I’ve specified the AD Attribute comment, but you can use whatever takes your fancy.

Next, you need to specify where it says Which users do you want to include in the ABS files? whether you want to:

1. Only include users that have a value for the AD attribute you specify or;
2. Exclude all users who have a value for the AD attribute you specify.

For this blog post, we’re going to select Exclude all users who have a value for this AD attribute. In the field next to this, we’re going to type the name of the AD attribute (comment) that we specified above. In each user account we want to hide, we will use this AD attribute to populate with a data value.

Once you’re done, hit Apply changes and you’re good to go. Changes will take affect next time the Address Book processes do their thing (by default, this happens at 1:30am each night).

Now, whenever the Lync User Replicator process sees a user with a value for the attribute you specified, it will exclude it from the Address Book and that user will not appear when you search for them in the Lync client.

See more at:
http://www.justin-morris.net/how-to-hide-users-from-the-lync-address-book/#sthash.zJBhSDpa.dpuf
http://www.justin-morris.net/how-to-hide-users-from-the-lync-address-book/

CRM 2011 installing error (The full-text component is not installed on SQL Server, Word Breaker Not Installed)

To resolve it:
1- Modify the existing SQL server installation. From Control panel
2- Click add/remove programs, click on SQL Server installation
3- Change/ add features. You will be prompted for the original install media so make sure you have it mounted and available
4- Select add new features to SQL instance
5- Choose instance that CRM was installed on
6- Check the box for Full-Text indexing
7- Once completed, Now start and stop SQL service, and make sure to turn back on the SQL Agent
8- Re-run your CRM setup

Good Luck :)

Lync 2013 Monitoring Dashboard Error

When you click on Dashboard in your lync reports you get the following errors: 

Report processing stopped because too many rows in summary tables are missing in the call detail recording (CDR) database. To resolve this issue, run dbo.RtcGenerateSummaryTables on the LcsCDR database.

Report processing stopped because too many rows in summary tables are missing in the Quality of Experience (QoE) database. To resolve this issue, run dbo.RtcGenerateSummaryTables on the QoEMetrics database.

To solve this issue:

logon to the SQL Server Management Studio
Browse to Databases > QoEMetrics > Programmability > Stored Procedures
Rightclick dbo.RtcGenerateSummaryTables and choose Execute Stored Procedure...

Do this steps for both the QoEMetrics and LcsCDR databases.

KB2592525 Installation failed (This update is not applicable to your computer)

Description:
When you try to install Lync WAC server (Office wen apps server 2013) on Microsoft Windows server 2008 R2 SP1 you may have this error while installing KB2592525 required update (This update is not applicable to your computer).

Resolution:

1. Download KB2592525  to folder on your system
2. Create a new folder called “files”
3. Extract the MSU: expand Windows6.1-KB2592525-x64.msu –F:* .\files
4. go to files
5. Install using Pkgmgr: pkgmgr /ip /m:Windows6.1-KB2592525-x64.cab

import photos to AD for Lync

Method no.1:

There is a minor schema change required to enable use of photos in AD. The change is to flip the thumbnailPhoto attribute to make it replicate to the Global Catalog. Exchange 2010 Service Pack 1 (SP1) automatically performs this schema change, so if you have deployed Exchange 2010 SP1, you do not need to make a schema change. Otherwise, you do need to follow these steps:

1. If you haven’t registered the Schema MMC snap-in on the server you want to make this change on, go ahead and do so using the following command: Regsvr32 schmmgmt.dll
2. Open an MMC console (Start | Run | MMC) and add the Schema snap-in.
3. In the Active Directory Schema snap-in, expand the Attributes node, and then locate the thumbnailPhoto attribute.
4. In the Properties page, select Replicate this attribute to the Global Catalog, and click OK.

Then you are ready to import photos into AD. This is done with a Powershell command, for example:

Import-RecipientDataProperty -Identity "Dollie Madison" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\DollieMadison.jpg" -Encoding Byte -ReadCount 0))

Method no.2: 3rd party tool i have tried and it is helpful

http://www.cjwdev.co.uk/Software/ADPhotoEdit/Info.html