Azure & Office 365

Archive for the ‘SharePoint’ Category

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

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

We all know that SharePoint Security update get downloaded and install with windows update. Normally these update do not change any build number so SharePoint admin were least concerned about the update. The only time a SharePoint admin would look at these update if users start facing a unknown SharePoint issue after windows update.

Since February 2015 things have changed for admins. Microsoft has started pushing cumulative update(this will change build number) along with Microsoft security update. Now every-time you install Windows update, you will have to run PSCONFIG and SharePoint build number will change.

Now SharePoint admins don’t have to schedule a different slot for SharePoint update or download and install them separately.

Windows admin has to take additional care to make sure appropriate SharePoint updates are selected while installing Windows update.

As part of normal practice, when a update is installed we need to run the psconfig wizard to seal the patch and update SQL tables. Now after every windows update, SharePoint admin needs to run this psconfig wizard to make sure patches are properly installed.

If you have a Standalone server I don’t think you should have any issues, if you have a Farm server setup I would recommend manually installing these update instead of windows update.

Lot of my friends use to make note of all the ASP.net, SharePoint security update and IIS update so that he can narrow down in case any issue occurs in future. Now he has to make note of SharePoint CU as well. Fortunately for everyone it was easy to filter out and decline the updates in our on-premises WSUS server or normal windows update.

Highlights:
1. SharePoint cumulative update is now part of windows updates
2. Run PSconfig after every windows update
3. Windows admin take extra care when installing Windows update.

Hope this will be helpful for you all.

You need to think if its additional burden on Windows Admin or heads up for SharePoint admin.

 

Microsoft has released another SharePoint 2013 Cumulative Update in February 2015. Let me help you know how we can install  February 2015 on SharePoint 2013 server.

Its per-requisites is either SharePoint 2013 SP1 or SharePoint 2013 March PU.

Now the most important part is how to install SharePoint server February 2014 Cumulative Update.

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

Here is link for all the updates:

Sharepoint Foundation 2013 has only 1 setup file ubersts2013-kb2920801-fullfile-x64-glb.exe
Download SharePoint Foundation 2013 February 2015 CU

Now here the twist starts, SharePoint 2013 update has 3 setup files ubersrv_1.cab, ubersrv_2.cab, ubersrv2013-kb2920804-fullfile-x64-glb.exe. You can download this from:
Download SharePoint Server 2013 February 2015 CU

Project Server 2013 update has 3 setup files ubersrvprj_1.cab, ubersrvprj_2.cab, ubersrvprj2013-kb2920796-fullfile-x64-glb.exe. You can download this from below
Download Project Server 2013 February 2015 CU

Office Web App server 2013 has only 1 setup filewacserver2013-kb2956101-fullfile-x64-glb.exe.
Download Office Web App 2013 February 2015 CU

The KB articles for September CU are available at the following locations:

• KB 2920801 – SharePoint Foundation 2013 February 2015 CU
• KB 2920804 – SharePoint Server 2013 February 2015 CU
• KB 2920796 – SharePoint Server 2013 with Project Server February 2015 CU
• KB 2956101 – Office Web App Server 2013 February 2015 CU

Once the updated the downloaded you need to extract all the updates in 1 folder as shown below:

• Now when you run the main setup file exe file, you will be able to extract and install the update.Do not try to extract cab file it will be extracted by exe.
• Once you install these updates, you need to reboot the server
• Now system needs to be restarted.
• Follow the same steps on all SharePoint servers in farm.
• SharePoint PSconfig wizard on all servers.
• Finally it is installed

Note : SharePoint Server 2013 update contains the SharePoint Foundation update.Where as SharePoint Server 2013 with Project Server update contains Project Server update, SharePoint Server update and SharePoint Foundation update.

For more information:
http://blogs.technet.com/b/stefan_gossner/archive/2015/02/10/february-2015-cu-for-sharepoint-2013-has-been-released.aspx

Microsoft has released SharePoint 2010 Cumulative Update in February 2015.

Its per-requisites is Sharepoint 2010 SP2. Rather I would recommend you to install September 2014 CU before installing February 2015 CU.

Note: This CU does contains all SharePoint 2010 fixes released after Service pack 2. 

All are available by clicking the same Hotfix Download Available link in the KB article for the release.

Here is link for all the updates:

For SharePoint Foundation 2010 you need setup wssloc2010-kb2910904-fullfile-x64-glb.exe
Download SharePoint Foundation 2010 February 2015 CU

For SharePoint server 2010 you need setup ubersrv2010-kb2899558-fullfile-x64-glb.exe
Download SharePoint Server 2010 February 2015 CU

For Project server 2010 you need setup ubersrvprj2010-kb2899557-fullfile-x64-glb.exe
Download Project Server 2010 February 2015 CU 

 

The KB articles for December CU are available at the following locations:

• SharePoint Foundation 2010: KB 2910904
• SharePoint Server 2010: KB 2899558
• Project Server 2010: KB 2899557

Once the updated are downloaded, you need run the main setup file ubersrv.exe file, you will be able to extract and install the update.

Once updates are installed, run SharePoint Products and configuration wizard to seal the update on the server.

Follow the same steps on all SharePoint servers in farm. Now run SharePoint PSconfig wizard on all servers.

For more information:

http://blogs.technet.com/b/stefan_gossner/archive/2015/02/10/february-2015-cu-for-sharepoint-2010-has-been-released.aspx 

 

Hi All,

Just a head-up on SharePoint 2016 release details. This dates are not yet confirmed but good for initial guidance.

SharePoint Beta 5th June 2015

Some Highlights for the SharePoint 2016:
The next version of SharePoint is not the last version of SharePoint server that Microsoft will SHIP. So thats a very good news for the SharePoint On-premises community.
You can still use Infopath Forms 2013 with SharePoint 2016. Forms for SharePoint library seems dropped from the list.
More integration features with Office 2016.
Delve and yammer still does not have much of clarity on integration with SharePoint 2016.
Lot more site and list templates to use from.
Hybrid mode of SharePoint is also given some extra consideration.
Improved Business Intelligence features.

Hope this head-up is helpful for you.

• Install SQL, SharePoint. etc. labs as part of this domain

Once we are confirmed using script we are able to add new Virtual Machine to domain, we can use the ready to use SharePoint, SQL, etc. VM’s as part of our Lab environment. Let’s see an example of SharePoint server.

1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
2. Select “Virtual Machines” from left menu and select “Create a Virtual Machine”

3. Under “Virtual Machine” select “From Gallery”

4. On the Choose an Image screen select SharePoint server 2013 Trial. This trial works for 180 days.

5. Type the Machines necessary details like Hardware configuration, Machine name, username and password
6. Now we have an important step in the process. Select the DEMONETWORK you created in Region/Affinity Group/Virtual Network. Make sure our Virtual network name is selected in Virtual Network Subnet. Click on Next

7. Now comes the most important step, we need to select Custom Script on this page and select the Join.ps1 script we just created. Click Finish

8. Now you can see that even SharePoint server is ready within few minutes
9. Advantage here is that you have a single credential stored on Active directory using which you manage all the Virtual Machine and work on your lab.
10. Below you can see that I have created SQL server, SharePoint server and started using them in just couple of minutes.

• Create a server on Azure in the Virtual Network

If you have worked on Hyper-V or any other Virtual server environment, this process is pretty simple for you. Here we will create our Virtual Machines. First machine would be our Domain Controller also known as DC. This server manage DNS, AD Users, etc. and normally the 1^st and most important server in a company.

1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
2. Select “Virtual Machines” from left menu and select “Create a Virtual Machine”

3. Under “Virtual Machine” select “From Gallery”

4. On the Choose an Image screen select “Windows server 2012 R2” and select Next
5. Type a unique name for the Virtual Machine. Select a username and password which you will never forget.(Selected a Low configuration because I won’t be using it much)

6. Now we have the most important step in the process. Select the DEMONETWORK you created in Region/Affinity Group/Virtual Network. Make sure our Virtual network name is selected in Virtual Network Subnet. Click on Next.

7. Now Select Finish.
8. Once the Machine is created, you will get a Connect button at bottom of screen.

• Create a Virtual Network in Azure.

Now let’s create a Virtual Network in Azure like we do in our Hyper-V servers. We need this Virtual network so that all the new and old Machine are in same IP range and can communicate with each other. You don’t need to be a Networking expert to do so. Just follow steps mentioned below.

 

1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
2. Select “Network” from left hand menu > Select “New” on left bottom corner
3. Now in the Menu select “Custom Create”
4. Now type the network name and select the data center for that network(note all computers should be in the same datacenter)

5. For now we will keep this DNS server empty (We should have our Domain controller DNS IP here. Our DC is not yet created so we keep it blank). Click on Next

6. On “Virtual Network Address Spaces”, provide name of your network and Subnet count (I won’t have more than 256 machines so selected same). Click on “Add Subnet”. Click on Finish

Here we have our Virtual Network created. Note this Network will then be used while creating our Virtual Machine. The very first machine we will create is our Domain controller. Once the domain controller is created we will update it in DNS server records used above.

Recently when I got access to Azure I wanted to create my lab on Azure which took me days to figure out the process. It is similar to what we do on our Hyper V machines but a bit complex in nature because we are working on cloud

 

We follow the same process on our local machine to create a Lab environment but normally we are short of resources like  Disk Space, RAM, CPU which is the taken care by Azure. Biggest dis-advantage for our local system environment is when you buy these resources, you don’t use it all the time which we have already paid for. In Azure we pay only when you use it.

 

Today we will understand how we can create our own Lab environment on Windows Azure. The whole process is lengthy to explain so I have divided it in 8 different parts listed below. Hope you will enjoy learning it.

 

• Connect to your Azure Subscription using PowerShell.
• Create a Virtual Network in Azure
• Create a server on Azure in the Virtual Network
• Create a new domain
• Update Domain setting on Virtual Network and bind it to Private IP on DC
• When creating a new server it should be part of this domain
• Install SQL, SharePoint. labs as part of this domain
• Troubleshoot common issue during this process

 

 

• Connect to your Azure Subscription using PowerShell

You cannot create your lab with just Azure User Interface. It’s said that “Well planned is half done”. So let’s plan and prepare our self with Azure PowerShell.  Go to below link and download Microsoft Web Platform installer.

 

1. You can use it download and install Azure PowerShell

2. Once the PowerShell is downloaded and installed, we will get below message

3. Now we will download the Azure Setting file to connect to our Azure subscription. In the Azure PowerShell, type below command.

Get-AzurePublishSettingsFile

 

4. Once you login to your Azure website, you will get a file named “Visual Studio Premium with MSDN-date-credentials.publishsettings”.

Note: File name may change based on your subscription. Save it to a secure location. This file contains secure credentials and additional information about subscriptions that you can use in your Azure environment.

 

5. Now Import the Azure Settings file to PowerShell. Run “Import-AzurePublishSettingsFile” and then type path of the file we just downloaded as shown in below image.

6. To check Subscription details run below command

Get-AzureSubscription

Hi Friends,

Today we will try to understand how to configure RBS(Remote Blob Service) on single or multiple content databases in SharePoint 2013 with SQL server 2012 or 2014. Steps are nearly same with both SQL server but make sure you use the correct msi file. For SQL serve 2012 size of msi file would be 5120 kb which can be downloaded from here .  For SQL serve 2014 size of msi file would be 4380 kb which can be downloaded from SQL server 2014 feature pack here 

 

Once you have downloaded the file save it on empty folder on c: or d: drive

1. Once database is created from SharePoint server, execute below command on SQL server

EXEC sp_configure filestream_access_level, 2
RECONFIGURE

1. Then we need to select the content database from top and execute below command(password can be changed)

if not exists (select * from sys.symmetric_keys where name = N’##MS_DatabaseMasterKey##’)create master key encryption by password = N’Admin Key Password !2#4′

1. Now you need to execute below command on content database(wss_content5 database name needs to be changed)

if not exists (select groupname from sysfilegroups where groupname=N’RBSFilestreamProvider’)alter database [WSS_Content5] add filegroup RBSFilestreamProvider contains filestream

 

1. Now we will add the physical path of RBS datafiles to content database. You can change the database name and filepath

alter database [WSS_Content5] add file (name = RBSFilestreamFile, filename = ‘C:\Blobstore5’) to filegroup RBSFilestreamProvider

 

 

1. Now you need to run below command on Windows Powershell (run as admin). Go to folder which has the rbs.msi file we downloaded.(Make note of FilestreamProvider name. Change SQL servaer and content databasename)

msiexec /qn /lvx* rbs_install_log_db5.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME=”WSS_Content5″ DBINSTANCE=”SQLservername” FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider

If you see the rbs_install_log_db5.txt file to be less then 1000 kb, e.g. 482 kb, it means it didn’t work. If this has worked fine you will see above 1000 kb e.g. 1218 kb.

You can also validate that rbs related tables are added to database as shown below.

Note: if you face issues while running command, try to reboot both SQL and SharePoint server. I know this is not a solution but a workaround to the known issue you might get. You can also try SQL service restart and iisreset on sharepoint server. You may also check eventviewer log to find symptoms of the issue.

6. On SharePoint server run below command on windows powershell:
msiexec /qn /lvx* rbs_install_log.txt /x RBS.msi DBNAME=”WSS_Content5″ DBINSTANCE=”SQLservername” ADDLOCAL=”Client,Docs,Maintainer,ServerScript,FilestreamClient,FilestreamServer”

Note: if you face issues while running command, try to reboot both SQL and SharePoint server. I know this is not a solution but a workaround to the known issue you might get. You can also try SQL service restart and iisreset on sharepoint server. You may also check eventviewer log to find symptoms of the issue.

 

1. Now run below command 1 by 1 in SharePoint powershell and update the active providername and enable the RBS on content DB.

$cdb = Get-SPContentDatabase –WebApplication http://testspimgweb01
$rbss = $cdb.RemoteBlobStorageSettings
$rbss.Installed()
$rbss.Enable()
$rbss.SetActiveProviderName($rbss.GetProviderNames()[0])

To migrate existing content (Make sure you run this even if you don’t have any existing data.)
$rbss.Migrate()

Note:  Also every database in web application needs RBS to be enabled or above command will fail.

1. Now if you create site collection and upload a file, you will observe it is moved to this folder you created with SQL command in step 4.

 

Note: You need to run these command for every content database you want enable RBS on.

 

Troubleshooting:  When you run these command, you might face permission issues. To resolve these issue make sure you have full access on C:\Program Files\Common Files\microsoft shared and registry. When you run these command, you may not find the error in the log file so run the rbs.msi file and make sure you find all the permission issue in GUI. Many a time when you assign permission on root folder on drive or key in registry, it will not be inherit to subfolder. Make sure you go to the folder shown in error and assign owner permission.

 

Hope this was helpful.