Category Archives: SharePoint 2013

Certified Solutions Australia.com - SharePoint 2013

How SharePoint 2013 Licensing Works.

Microsoft SharePoint Server 2013 Licensing Microsoft licenses SharePoint Server 2013 under the Server/Client Access License (CAL) licensing model. The Server/CAL licensing model requires both a server license for each copy of the server software a customer installs and uses and CALs for the users (or devices) that access that software.

Use Scenarios

This document also illustrates common deployment scenarios to further explain the licensing requirements of SharePoint Server 2013. Users can license these same deployment scenarios under device-based CALs.

Scenario A:

Intranet Description

Internal users accessing content, information, or applications inside the firewall through a local area network (LAN) or the Internet. No other users have access.

Example:

A professional sports team sets up an intranet site that the manager, coach, and players access. It is also used for support staff such as the physiotherapist who is an on-site contractor rather than an employee, and for CAL requirements, an internal user. A news reporter trying to access the SharePoint Server site is denied access.

Licensing

Server: One SharePoint Server 2013 license per running instance of the software. 

Internal Users: One CAL/user.

 

Scenario B:

Extranet Description

An organization extends access to otherwise restricted content inside the firewall to a limited number of identifiable external users.

Example:

The Elm University publishes research papers that are available to specific educators from other universities (external users). This situation is an intranet plus extranet scenario.

Licensing

Server: One SharePoint Server 2013 license per running instance of the software. 

Internal Users: One CAL/user. 

External Users: SharePoint CALS are not required; the server license permits external user access.

 

Scenario C:

Internet Description

Internal users make content, information, and applications publicly available to users via the Internet (for example, on a public-facing company website). A mix of internal and external users anonymously accesses the site, including employees. No SharePoint CALs are required. External user access is permitted under the server license, and SharePoint CAL requirements for internal users are waived for access to content, information, and applications made publicly available via the Internet.

Licensing 

Server: One SharePoint Server 2013 license per running instance of the software. 

Internal Users: CALs are not required. 

External Users: CALs are not required.

 

Simplifying Licensing

SharePoint Server 2013 simplifies SharePoint access and use. This is because SharePoint Server 2013 collapses internal and external use under a single licensing offering/model. Customers no longer need to look to SharePoint for Internet Sites to license anonymous access. Additionally, SharePoint Server 2013 integrates functionality that was previously available separately under FAST Search Server for SharePoint.

InfoPath 2013 Add Colour Coding to the Status of a Form

  • Edit your Form Library page.
  • Add a Content Editor web part to the page and move it below the form library.
  • Open the properties for the Content Editor web part and add the path to the StopLight.txt file. Make sure you upload this file to the Site Assets library in the same site where your form lives.
  • Set the Content Editor Appearance property to hidden and click OK to save the changes.
  • Add a new calculated field column to the Form Library and call it Overall Status (you can call it anything you like).
  • In the formula section add the following: StopLight Formula
  • Save the new column and return to the Form library.
  • Make any additional changes to the form library, for example set the Style to Newsletter to give it a neat professional look.

Download the StopLight.txt file here.

Any questions, let us know in the comments section below.

InfoPath 2013 Moving a Form from an Existing Form Library to a New Form Library

  • Create a document library to store the InfoPath form content type.
  • Publish the form as a content type to the site, save it in the new library created in step 1, then promote any new columns as site columns.
  • Create a new form library and add the new content type as the default.
  • Save a form from the old library by ‘downloading a copy’, then upload it to the new form library.
  • Relink this form in the new library.

It should open and function as normal.

SharePoint 2013 Code Packaging Scenarios Explained

What SharePoint 2013 deployment scenario you choose to host your SharePoint 2013 farm dictates how you develop your code and deploy it. SharePoint 2013 offers three deployment options when it comes to code packaging. See SharePoint 2013 Deployment Scenarios Explained for more details here.

Full Trust Farm Solution

This code packaging option is only available in the on-premise deployment scenario and some dedicated Cloud hosting options. Solutions contain code and customizations that are deployed across the entire farm and are deployed specifically to the \BIN directory or the Global Assembly Cache (GAC). A SharePoint Administrator with farm administrator rights deploys the solution to the farm but the solution itself can be added by a Developer with console access.

Sandboxed Solution

These are partial trust and are available in all types of SharePoint 2013 deployment scenarios. These sandboxed solutions are available to all sub sites of a site collection to where they are deployed. You do not have to be a Farm Administrator to deploy a sandboxed solution, however there are restrictions on solution development if you are a Developer.

SharePoint 2013 Apps

This is a new packaging option introduced in SharePoint 2013 and is based on the idea of small widgets or apps very similar to the apps on your smartphone. However, SharePoint apps are different to smartphone apps as the actual execution of SharePoint apps does not take place in SharePoint, instead it takes place in the browser and communicate with SharePoint via OAuth over SharePoint 2013 CSOM APIs.

What code packaging option do you currently use?

SharePoint 2013 Deployment Scenarios Explained

SharePoint 2013 offers four different deployment scenarios namely:

      On-premise
      Office 365
      Hosted
      Hybrid

On-premise deployment

This form of deployment scenario involves having your SharePoint 2013 farm servers sitting behind the corporate firewall and is administered by the IT team and the SharePoint Administrator. With this option you have full control of the SharePoint environment including the Development environment and the how you deploy your applications.

Office 365 deployment

In this form of deployment, your SharePoint 2013 farm is hosted in the cloud and managed by Microsoft. You have access to all the development options as in the On-premise scenario except for running server-side code in apps.

Hosted deployment

In this deployment scenario your virtualised SharePoint 2013 farm is hosted in the cloud by third party providers which may or may not be Microsoft. Companies like Amazon EC2, CloudShare and more offer opportunities to host your virtual machines but have varied options when it comes to development. Some hosting companies will offer you your very own dedicated cloud which gives you more options as you do not have to share it with anyone else.

Hybrid deployment

This is a combination of servers hosted On-premise as well as in the Cloud. Some SharePoint 2013 servers are managed by the IT team and SharePoint Administrator on site while some applications are deployed to the Cloud.

Wondering what code packaging options are available in SharePoint 2013? Check out this link.

What are some of the options you have selected for your SharePoint farm? Share your suggestions with the community below.

What is Azure?

Get started with Windows Azure

Azure is Microsoft’s cloud computing platform that provides a powerful way to transform business and applications.

Ability to move really fast.
On premise might take weeks or days to stand up, but azure instantly spins up the resources you need to set up websites and servers.

You can save money with windows azure.
On premise servers, CPU utilization is 10 to 15% as there are times in the day when the servers are not busy or staff are away. Servers are built to run at peak no matter what time of the day it is. You end up having to pay for that peak usage even when it is not being leveraged.
In the cloud world you can dynamically spin up and spin down resources based on only what you need so you only pay for what you use. During off peak times you can cycle down the servers or run them at lower utilization and pocket that money. For most applications that will lead to a tremendous cost saving.
Another great thing about Azure is that it maintains hybrid consistency, this allows you to use the same programming models, the same core tools and the same languages with windows servers, SQL and .NET.
You can build applications that will run on both on premise as well as in the cloud. You can also build applications that can span both on premise and the cloud.

Where does Windows Azure run?

It runs in Microsoft Datacentres that are distributed around the world. Some regions consist of multiple datacentres that are close together. You can choose to run and deploy your applications to any of these regions around the world. The regions include North and South America, Europe, Japan, Australia and more in Asia. You simply point to where you want to deploy and run your application regardless of where you are in the world while maintaining full control over the deployment.
Each region is at least 500 miles away and so there are a cluster of regions around the world. You can then choose to run your application either in one of the regions or both. The benefit of running them in both regions is so that you can maintain disaster isolation during a natural disaster. So if one region goes down you can switch to the other region and continue running your applications. This gives you peace of mind knowing that in the event of a natural disaster you can still continue to run your applications. So you always have choice and flexibility.

Saving money

You only pay for what you use, only for the minutes that you use. There is no upfront cost, there is no need to buy Windows or SQL licenses. You simply log on to the Azure website, sign up and immediately start deploying assets. Billing is done per minute only, so you only pay per minute you use Azure. So if you spin up a new virtual machine and use it for 10 minutes you only pay for 10 minutes. You are not paying by the hour or per server, so that saves you a lot of money. There is no charge for stopping virtual machines, so if you stop your VMs for maintenance or for upgrade, the billing will also stop.

More cool features

Virtual Machines

When it comes to Azure capabilities you can run both Windows and Linux virtual machines and there is no restriction on what software you use with the VMs. You can install any database, any application server, and any framework in any language. You can also run these machines as standalone machines with their own unique IP address on the internet or you could take advantage of the ‘Virtual Private Networking’ feature. What this feature does is it allows you to take multiple VMs and put them together and have an application that consists of multiple machines with some very cool options like the ‘Load Balancing and High Availability’ feature in an Availability Set.
The Availability Set (19:00)

This allows you to deploy your VMs on Azure and run each of those VMs on separate fault domains or isolation units. For example if you have two or three VMs, you can make sure that they are each running on separate physical servers so that in the event of a server failure you wouldn’t lose all your VMs all at once.
To break it down, you simply create two or more virtual machines in an Availability Set and Azure will make sure that they are isolated on separate physical machines with two separate top rack routers available. So in the event of a network failure you can rest assured that at least some of the VMs will be still be running and your applications will remain unaffected.
There is also load balancing support so you can configure a single IP address to the outside world and make sure that the traffic to that IP address is distributed across the virtual machines, across the availability set or across your Azure regions. The advantage of having load balancing is that if one of the server fails the load balancer will automatically take it out of rotation and stop sending traffic to it and the other VMs can continue to handle the load. Azure will then spin up another instance of the virtual machine automatically on a completely separate server and bring it back into the network rotation. This is all done automatically which is built into the features which allows you to build much more available and reliable systems.