OWA Configuration for SharePoint 2013.

Install the OWA server set up first. Once done open the Windows power-shell with elevated permission (Run as administrator)

The below command will create new farm structure of OWA and you can use this in your application such as SharePoint, Lync and etc. Here I used the OWA with my SharePoint application.

> New-OfficeWebAppsFarm –InternalURL "http://owa" -ExternalURL "http://owa.scshiva.com" –AllowHttp -EditingEnabled

the above command will show the below as output:

FarmOU                           :
InternalURL                     : http://owa/
ExternalURL                     : http://owa.scshiva.com/
AllowHTTP                       : True
SSLOffloaded                     : False
CertificateName                 :
EditingEnabled                   : True
LogLocation                     : C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS
LogRetentionInDays               : 7
LogVerbosity                     :
Proxy                           :
CacheLocation                   : C:\ProgramData\Microsoft\OfficeWebApps\Working\d
MaxMemoryCacheSizeInMB           : 75
DocumentInfoCacheSize           : 5000
CacheSizeInGB                   : 15
ClipartEnabled                   : False
TranslationEnabled               : False
MaxTranslationCharacterCount     : 125000
TranslationServiceAppId         :
TranslationServiceAddress       :
RenderingLocalCacheLocation     : C:\ProgramData\Microsoft\OfficeWebApps\Working\waccache
RecycleActiveProcessCount       : 5
AllowCEIP                       : False
ExcelRequestDurationMax         : 300
ExcelSessionTimeout             : 450
ExcelWorkbookSizeMax             : 10
ExcelPrivateBytesMax             : -1
ExcelConnectionLifetime         : 1800
ExcelExternalDataCacheLifetime   : 300
ExcelAllowExternalData           : True
ExcelWarnOnDataRefresh           : True
OpenFromUrlEnabled               : False
OpenFromUncEnabled               : True
OpenFromUrlThrottlingEnabled     : True
AllowHttpSecureStoreConnections : False
Machines                         : {OWAServer}



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Now login to SharePoint 2013 server:

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

1. Open the SharePoint Powershell with elevated permission (Run as administrator).

2. Execute the below command one by one.



> New-SPWOPIBinding -ServerName OWAServer.scshiva.com  -AllowHTTP

The above command will give multiple line as a output. Then execute the below commands one by one.


> Get-SPWOPIZone
OutPut: internal-https

If the above shows the https then need to execute the Set-SPWOPIZONE command. If the above out put is http then skip the next 2 steps.

> Set-SPWOPIZone -zone "internal-http"
> Get-SPWOPIZone
internal-http

> (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
OutPut: False

If the above output is "False" the run the next set of command.
> $config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()

Run the below command to confirm the status is True.
> (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
OutPut: True

Post your quires in the below. :-)

Administration on HNSC URL

Earlier we discussed about HNSC Concept and How to create HNSC in SharePoint. To know that click here

In this post I am explaining how to manage(Add/Remove) the URL of HNSC.

Add URL for HNSC site.

To view the existing URL's and its zone use the below command.

Get-SPSiteURL -Identity "http://FirstSiteCollection.SharePointShiva.com"

Note the output and Use the below command to add the new URL in existing site collection

Set-SPSiteURL -Identity "http://FirstSiteCollection.SharePointShiva.com" - Url  http://addingnewurl.SharePointShiva.com -Zone "custom"

The above command will add the new url called addingnewurl.sharepointshiva.com to the existing site collection which contain the url called firstsitecollection.sharepointshiva.com

Don't forget to mention the ZONE.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Remove the URL of HNSC.

Remove-SPSiteURL -Identity http://firstsitecollection.sharepointshiva.com

Post your query in comment.

Host Name Site Collection Concept (HNSC) - SharePoint

In the post we are going to know about Host Name Site Collection concept.

What is Host Name Site Collection?
Host Name is referring a identity for the computer in general. The URL of web application in SharePoint will be "<http(or)https>://HOSTNAME:PORT" eg: http://sharepointwebserver:2204.

In this web application we can create one site collection in root level and that can access using the above mentioned URL or some other alternate access mappings url in SharePoint.

In my scenario I need to have 9 site collections in one web application and each site collection should have its unique url (No Managed Path).

Then my minds arise a question I can have 5 URL's in SharePoint but all the 5 will access the one site collection which I created in ROOT. To achieve the requirement we need to choose the HNSC concept in SharePoint. The below example and syntax shows how to create a site collection using HNSC concept.

For getting the syntax and description for options in the syntax click here

Example: New-SPSite -Url "http://FirstSiteCollection.SharePointShiva.com" -OwnerAlias SharePointShiva\SPHNSCAdmin -ContentDatabase WSS_Conent_HNSC1stSC -HostHeaderWebApplication http://sharepointwebserver:2204 -Name FirstSiteCollectionUsingHNDCConcept -Template STS#0

In the above mentioned powershell command have list of option and check the description below.

-URL : Provide the SiteCollectionURL which required this will be similar to ROOT.
-HostHeaderWebApplication : Provide the WebApplication URL in this Option so that that the site collection will create under the web application.
-Template : Mention the template code here to create the SC with the corresponding template to know more template click here

Soon I will post about how to set the another URL for the HNSC and how to remove the URL.. Stay Tuned.

Changing the Recovery model to SIMPLE for multiple database in a single Query: MSSQL Server

If you executed the below query then you will get the output of another query which you need to execute to change the Recovery model from Full to Simple.

Query:
set nocount on go select 'ALTER DATABASE [' + name + '] SET RECOVERY SIMPLE' from sys.databases where database_id > 6 and recovery_model_desc = 'FULL'

Output:
ALTER DATABASE [DB1] SET RECOVERY SIMPLE
ALTER DATABASE [DB3] SET RECOVERY SIMPLE
ALTER DATABASE [DB6] SET RECOVERY SIMPLE
ALTER DATABASE [DB7] SET RECOVERY SIMPLE
ALTER DATABASE [DB9] SET RECOVERY SIMPLE

Note:  The SQL Server have around 15 database and the DB 1,3,6,7,9 only running in Full recovery model. So that you will got the above output copy it and executed like the below.

Query:
Use Master
ALTER DATABASE [DB1] SET RECOVERY SIMPLE
ALTER DATABASE [DB3] SET RECOVERY SIMPLE
ALTER DATABASE [DB6] SET RECOVERY SIMPLE
ALTER DATABASE [DB7] SET RECOVERY SIMPLE
ALTER DATABASE [DB9] SET RECOVERY SIMPLE
Once the above executed successfully please cross verify it randomly by manual check. Now all the database in the SQL server will set to Simple recovery model.

Note:
If the recovery model is in Simple mode then you can't recover the database fully.

Thanks!!!

Authentication window is continuously appear and not accepting the credentials, FMI: Event ID: 6037

Source: LsaSrv

Type: Error

Description: The program svchost.exe with the assigned process ID 4224 could not authenticate locally by  using the target name HTTP/website.domain.com  The target name used is not valid. A target name should refer to one of the local  computer names for example the DNS host name. Try a different target name. The below settings should fix the above issue. Go to Run and type "REGEDIT" It will open the registry editior. and add the below value in the corresponding location. HKLM\system\CurrentControlSet\Services\Lanmanserver\parameters DisableStrictNameChecking:DWORD=1 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa DisableLoopbackCheck:DWORD=1 The server must be restarted for the settings to take effect. See ME896861 for details about these  registry settings.

Install Workflow Manager 1.0 Offline

If you want to install Workflow Manager 1.0 on servers without internet connectivity, you will run into problems with the Web Platform Installer, the only tool Workflow Manager 1.0 can be installed with.

The good news is, there is a command line tool of Web Platform Installer, where you can download the installation files and all of its dependencies to a internet accessible machine, move it over to one of your servers and install it in offline mode.

Take the following steps to do so:

1. Download the WebPICMD.exe Package from the MS Downloadcenter and unzip it to a folder (C:\WebPICMD\WebPICMD.exe in our case)
2. Open a Command Prompt, navigate to the folder you extracted the tool and execute the following command:
   
   "WebpiCmd.exe /Offline /Products:WorkflowManager /Path:D:\Temp\WorkflowManager\"This will initiate a download with all the related components into the provided folder.
3. Copy the WebPICMD.exe to the server where you want to install the WorkflowManager 1.0, in our example to D:\Temp\WebPICMD\WebPICMD.exe
4. Copy the downloaded files to your server where you want to install the WorkflowManager 1.0, in our example to D:\Temp\WorkflowManager 
5. Open a Command Prompt, navigate to the folder you copied the WebPICMD.exe tool and execute the following command:

WebPICMD.exe /Install /Products:WorkflowManager
/AcceptEULA /SuppressReboot
/Log:./WorkflowManager.log /Xml:file:///D:\Temp\WorkflowManager\feeds\shadow-webproductlist.xml

This will initiate the installation of the Workflow Manager 1.0 and its dependencies. The outcome of the installation will be logged to the WorkflowManager.log file. The above line will suppress reboots and will accept the license terms automatically.

A log file will be created at the following path, where you can see the process and the warnings/errors/information about the installation:

%localappdata%\microsoft\web platform installer\logs\webpicmd

Stay tune to catch the configuration wizard of Workflow Manager. (Standalone and Farm).

Thanks.

Install and Download SharePoint 2013 prerequisites offline (manually)

This article applies in a situation when you don’t have internet access in your SharePoint server.

I have placed all the direct download links for the installers you might need.

This article assumes you are having a new fresh installation of windows server 2008 R2 SP1

If you tried to run the installer , The following should be installed (but you cant install them directly from here since you don’t have internet)

in this case  you can download and install SharePoint 2013 Prerequisites offline and run them manually as below:

I have placed what needs to be installed on a clean Window server 2008 R2 SP1 , you should not need more than this:

Click the each prerequisite it will redirect you to the page where the software need to Download.

Prerequisite:

1. Microsoft .NET Framework 4.5
2. Windows Management Framework 3.0
3. Microsoft SQL Server 2008 R2 SP1 Native Client
4. Windows Identity Foundation (KB974405)
5. Windows Identity Extensions
6. Microsoft Sync Framework Runtime v1.0 SP1 (x64)
7. Windows Server AppFabric
8. Microsoft Information Protection and Control Client
9. Microsoft WCF Data Services 5.0
10. Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB2671763)

Once you downloaded all the above mentioned prerequisites, Install the .Net Framework 4.5 and Windows Management Framework 3.0 Manually.

Yes you can install all the above prerequisites manually except AppFabric. If you are installing manually it required do some configuration. That is not required for SharePoint.

So once the First 2 prerequisites installed successfully now you need to follow the below simple steps.

My SharePoint 2013 software dump is available in the following path for an example.D:\Software\split\SharePoint\.

Place the downloaded software to prerequisiteInstallerFiles folder which present inside the SharePoint dump.

Then open the Windows PowerShell with elevated permission (Run As Administrator).

Execute the below powershell command. It will install all the softwares including appfabric without an issue.

$SharePoint2013Path = "D:\Software\split\SharePoint\"

Start-Process "$SharePoint2013Path\PrerequisiteInstaller.exe" –ArgumentList "/SQLNCli:$SharePoint2013Path\PrerequisiteInstallerFiles\sqlncli.msi /IDFX:$SharePoint2013Path\PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu /IDFX11:$SharePoint2013Path\PrerequisiteInstallerFiles\MicrosoftIdentityExtensions-64.msi /Sync:$SharePoint2013Path\PrerequisiteInstallerFiles\Synchronization.msi /AppFabric:$SharePoint2013Path\PrerequisiteInstallerFiles\WindowsServerAppFabricSetup_x64.exe /KB2671763:$SharePoint2013Path\PrerequisiteInstallerFiles\AppFabric1.1-RTM-KB2671763-x64-ENU.exe /MSIPCClient:$SharePoint2013Path\PrerequisiteInstallerFiles\setup_msipc_x64.msi /WCFDataServices:$SharePoint2013Path\PrerequisiteInstallerFiles\WcfDataServices.exe"

Thanks.