Categories
Who's Online
8 visitors online now
0 guests, 8 bots, 0 members
Support my Sponsor

Posts Tagged ‘Configure’

Configure Office Web App 2013 Farm with SharePoint 2013 Farm

 

Hi Friends,

 

Today we will discuss on how to configure Multi Server Office Web Apps farm with a SharePoint farm. Also the specialty of this OWA configuration is that it can work inside and outside of firewall. Normally OWA farms are setup HTTP inside the firewall network(Internal network) and HTTPS outside the network(External world) but using this configuration we will configure HTTPS for both inside and outside network. This will not only decrease additional overhead and configuration but also is recommended by Microsoft to use HTTPS for production environment.

 

We need to meet below pre-requisites before we proceed further:
1. SharePoint farm configured and ready to use
2. Two or more Office Web Apps servers with setup files
3. One certificate for Office Web App
4. If you are using Windows server 2012 R2 then you would need to install latest update for Office Web Apps
5. FQDN name for your Office web app farm e.g.(owa.domain.com) and its DNS entry with Round Robin(You can also configure Windows NLB or a Load Balancer entry for same)

Installation of Office Web App is very simple, You just need to download the installable and execute it on all OWA servers.

Install Office Web apps on all Office Web Apps servers. If you are using Office Web App on Windows Server 2012 R2, you should install latest update for Office Web Apps. You would need an Office Web app certificate imported to IIS
Now Let’s configure Office Web App, Open Windows PowerShell and execute below command
0299

Once the Office Web App farm is configured, open IIS and make sure SSL binding for site HTTP80 has proper certificate attached.
0302

From IIS binding select the certificate and export the .cer file.
You need to import it to central admin manage trust.

To Attach this Office web app farm to SharePoint farm, you need to create a WOPI connection. Open SharePoint PowerShell on SharePoint server and execute below command:

New-SPWOPIBinding -ServerName “officewebapp.domain.com”
0300

Set Wopi zone
0301

Now if you want to add other Office Web App Server to OWA farm, you need to execute below command on existing OWA server
new-officewebappsmachine -machinetojoin “owa2server.domain.com”
0303

Hope this will help you

Configure Workflow Manager 1.0 with SharePoint Server 2013

Hi Friends,

Today we will discuss on how to configure Multi Server Workflow farm with SharePoint farm. Just of your information, you need to access Workflow farm only from WFE and Application servers. This means just like your database server, even workflow servers are not exposed to end users.

We need to meet below pre-requisites before we proceed further:
A. SharePoint farm configured and ready to use
B. Two or more Workflow servers with setup files
C. If you are using Windows server 2012 R2 then you would need update KB2799752(Service bus hotfix) and KB2799754(Workflow manager hotfix)
D. FQDN name for your workflow farm e.g.(Workflow.domain.com) and its DNS entry with Round Robin(You can also configure Windows NLB or a Load Balancer entry for same)

  1. Let’s get started with installation of Workflow Manager 1.0 on Workflow servers. We need installable as shown below
    0261

  2. When you will try to install the workflow.exe file you will be asked to download and install WebPlatformInstaller.exe. Now all the updates and most components are installed through WebPlatforminstaller.

0262

0263

0264

 

  1. Once the WebPlatforminstaller is installed, you need to search for Workflow manager and Workflow manager client and install the same.

0265

0266

0267

0268

0269

0270

0271

  1. Once Workflow Manager and client is installed, I would suggest you to install the updates as well.

0272

0273

0274

0275

0276

0277

0278

  1. Now let’s configure Workflow Server farm. This is very important so please follow steps carefully.
  2. Lets execute the Workflow Manager Configuration Wizard
  3. Select “Configure Workflow Manager with Custom Settings”
    0279

  4. Now provide the SQL server instance name, Authentication, Certificate and SQL Workflow database names
    0280

  5. You need to provide the Workflow service account credentials which will be used to connect to SQL server and for workflow IIS Application pool.
    0281

  6. You would need to provide a Certificate Generation Key. It is just like Passphrase for your SharePoint farm
    0282

  7. Make sure you select “Allow workflow management over http on this computer”
    0283

  8. Along with Workflow Management, you need to configure Service Bus required by Workflow manager
    0284

  9. Make sure you select “use the same certificate generation key as provided for workflow manager”
    0285

0286

  1. Once the Workflow Farm is created, you need to join other Workflow server to the farm. To do so execute the same Workflow configuration wizard and select “Join an Existing Workflow Manager Farm”
    0287

  2. Provide the existing Workflow Farm SQL server instance name, Workflow database name and Service Bus farm database name
    0288

  3. Provide the workflow service account and Certificate generation key used while creating workflow farm.
    0289

  4. Select “use the same service account credentials as provided for Workflow Manager”, then select next
    0290

  5. Once farm other server is joined to workflow farm you will see below
    0291

  6. Once workflow is configured, you need to attach Workflow Farm to SharePoint farm. Make sure you have DNS entry(Workflow.domain.com) for your Workflow farm. If not DNS, you should at least have Host entry for same. Try to browse http://workflow.domain.com:12291 on WFE and Application server, you might see Authentication error.
    0292

  7. Add the URL to Local Intranet and set the Local Intranet zone to “Automatically login with current username and password”
    0293

0294

  1. Now you should be able to browse the workflow farm details, this shows you can connect to workflow farm and it is working fine.
    0295

  2. Now execute below command in SharePoint Powershell
    Register-SPWorkflowService -SPSite “http://sharepointsite” -workflowHostUri “http://workflow.domain.com:12291/” -AllowOauthHttp -ScopeName SharePoint –force
    0296

  3. Now you need to activate the workflow feature on site
    Enable-SPFeature -Identity WorkflowServiceStore –Url http://sharepointsite

  4. In Central Admin > Manage Service Application > Workflow Service Application Proxy
    0297

  5. Open site in SharePoint designer – Select workflow from left pane – select new workflow
    0298
    Note:
    A. Workflow farm can co-locate on SharePoint servers
    B. As per Microsoft articles, for high availability you need to have at least 3 Workflow Server in farm. You cannot have 2 workflow servers in a farm. It has to be 1 or 3.

Configure a SharePoint server in non domain(Workgroup) environment

Hi All,

Lets try to configure a SharePoint farm in a workgroup environment. Normally if we have to configure a SharePoint on a Workgroup environment only option available for us is Standalone environment. Now lets us try to understand how we can configure a SharePoint farm environment in a Workgroup environment. We need to run below powershell commands. Make sure you update passphase and SQL server name in below powershell. We have SharePoint and SQL installed on same machine. Make sure account used during FarmAccount does have access to SQL server.

$FarmAccount = Get-Credential
$PassPhrase = “FarmPassphrase”
$FarmPassphrase = (ConvertTo-SecureString $PassPhrase -AsPlainText -force)
$FarmConfigDatabase = “Wss_config_2”
$AdminContentDatabase = “SPFarm_Admin_ContentDB_2”
$CentralAdminPort = 8080
New-SPConfigurationDatabase -DatabaseServer (SQLservername) -DatabaseName $FarmConfigDatabase -AdministrationContentDatabaseName $AdminContentDatabase -Passphrase $FarmPassphrase -FarmCredentials $FarmAccount

Now let’s move a steps ahead and try to use different server for SharePoint and SQL server. Here we created a SQL user account and updated credentials in dbcredential.
$dbcredential = New-Object –typename System.Management.Automation.PSCredential –argumentlist “SQLuser”, (ConvertTo-secureString “SQLpassword” –AsPlainText –Force)
$PassPhrase = “FarmPassphrase”
$FarmPassphrase = (ConvertTo-SecureString $PassPhrase -AsPlainText -force)
$FarmConfigDatabase = “Wss_config”
$AdminContentDatabase = “SPFarm_Admin_ContentDB”
$CentralAdminPort = 8080
$FarmAccount = Get-Credential
New-SPConfigurationDatabase -DatabaseServer “SQLservername” -DatabaseName $FarmConfigDatabase -AdministrationContentDatabaseName $AdminContentDatabase -Passphrase $FarmPassphrase -FarmCredentials $FarmAccount -DatabaseCredentials $dbcredential

0227

0228

Note: We still cannot create a Multiple SharePoint server farm in Workgroup environment. Using above script you can connect only 1 SharePoint server with a SQL server.

This script works for both SharePoint 2010 and SharePoint 2013

Create a Active Directory Forest on a Windows Azure VM

  • Create a new domain

Now let’s configure this server to be a Domain Controller. As discussed earlier Domain controller manage DNS, AD Users, etc. and are normally the 1st and most important server in a company.

 

  1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
  2. Select Virtual Machine from left Menu
  3. Select the Virtual Machine we just created and click on Connect at bottom
  4. Now RDP to the Virtual Machine we created and click on Server Manager

0123

  1. Select Manager > Add Roles and Features

0124

  1. Select “Next” on Installation Type screen

0125

  1. Select “Next” on Destination Server screen

0126

  1. Check Box “Active Directory Domain servers”

0127

  1. Click on “Add Feature” on pop-up screen

0128

  1. Select the check box “Restart the destination server if required” > Click OK

0129

  1. Once it is installed, Click on Close

0130

  1. Open the Server Manager again, Click on Flag at top and select “Promote this server to a Domain Controller”

0131

  1. Select “Add a New forest”, type domain name
  2. Type the DSRM password and click “Next” (Note: this is required when you try to recover your active directory)

0132

  1. Now you will have to select your domain name. For example. Demo.com
  2. The NetBIOS Name screen will remove .com and you will see only demo.
  3. Select the Default location of installation and click “Next”
  4. Click on “Install”

0133

  1. Once the Computer is restarted, your Domain Controller would be ready.

Note: From now on when you logon to server you need use your domain name along with username we just created to authenticate to server. Example: demo\user1

Configure App service Application \ App catalog in SharePoint 2013

App service Application is a new Service Application in 2013 required to download and use APPS from SharePoint App store. To do so we will follow below

  1. New New DNS zone OR if you using same DNS namespace you can just create new wildcard(*) DNS entry as shown below:

119

Create new Zone

  1. Under your DNS management console, first create a forward Lookup zone for the app domain name
    118

  2. Now Click on DNS on top > Right click select new Zone

113

 

  1. Now Select Primary Zone and click Next

114

 

  1. Add new Zone URL  here.

115

  1. Select the default option

116

 

  1. Review the details and hit Finish

117

 

  1. Now create the Host entry for APP URL

118

8.

119

 

 

Now we will create Subscription Settings Service Application using Powershell (This option is not available in GUI).

  1. Open Powershell as Admin.

120

  1. Lets pull managed account into a variable $account:
    $acc = Get-SPManagedAccount domain\user

  2. Now we will create application pool for Subscription Settings service application
    $appPool = New-SPServiceApplicationPool -Name SettingsServiceApp -Account $acc

  3. Create Subscription Settings service application using the variable to associate it with the application pool that was created above
    $appSubSvc = New-SPSubscriptionSettingsServiceApplication –ApplicationPool $appPool –Name SettingsServiceApp –DatabaseName SettingsServiceDB

  4. Creates proxy for Subscription Settings service application
    $proxySubSvc = New-SPSubscriptionSettingsServiceApplicationProxy –ServiceApplication $appSubSvc

121

 

Now we will create App management Service Application using Powershell
1. Create Instance name to be used in future.
$appsInsName = “AppManagementServiceInstance”

  1. Lets pull managed account into a variable $account:
    $acc = Get-SPManagedAccount domain\user

  2. Now we will create application pool for App management service application
    $appPool = New-SPServiceApplicationPool -Name AppservicePool -Account $acc

  3. Create App management service application using the variable to associate it with the application pool that was created above
    $appAppSvc = New-SPAppManagementServiceApplication -ApplicationPool $appPool -Name “App Management Service” -DatabaseName AppManagementDB1

  4. Creates proxy for App management service application
    $proxySubSvc = New-SPAppManagementServiceApplicationProxy -ServiceApplication $appAppSvc -Name “App Management Service proxy”

123

Configure App Domain
Set-spappdomain -appdomain “apps.itfreesupport.com”
Set-spappSiteSubscriptionName -Name “prefix”

Or
Go to “Configure app URLs” on Apps menu and update details accordingly

124

128
In Manage App Catalog, you will be asked to create a Apps Site collection. Please create a new site collection.

126

 

125

 

Now you will be able to download and use APP from APP store.. Enjoy……………….

127