Checkout my latest blog post exploring how to deploy Matter Center for Office 365 and what I’ve learned from many deployments.
Check out my latest blog post as I provide my thoughts into Azure Automation and how it could be useful for your organisation.
As Office 365 but specifically in this case SharePoint Online continues to develop and grow you may be missing out on the latest updates;
Microsoft released a configuration change a little while back that allows you to turn on ‘Preview Features’, Preview Features are the latest changes that haven’t been released to all tenants yet so it really in my opinion should be used in dev environments only to test and release changes before arriving at a production environment
So How do I enable the preview features?
Easy, navigate to your admin tenant (https://yourtenant-admin.sharepoint.com)
Click Settings, scroll most of the page down and you will see a section called ‘Preview Features’ .
Enable the feature and click OK
Once done the latest Preview features should be available to you.
Learn more about Preview Features here
Ever had this situation where you need to bulk update a specific column in a list or library, you have 100’s or even 1000’s of items and need to set the same information for all the items, although rare I’ve seen it needed and while there may be a couple of way’s to do it here is a little application I have put together to do so.
I have this test library in my site collection, I’d like to update the title column to all be the same, let’s now use the Bulk Updating Column Console App to do so.
You can find the Application uploaded to the TechNet Gallery here , which has the source code for those wanting to see the nuts and bolts to it all ( there isn’t whole lot to it!
Please note you will need the SharePoint Online Management Pack installed or else the App will error
1. Open the Console Application Executable;
2. Enter in the following info:
- Your site collection URL
- Your username
- Your Password
- The List Title you would like to interact with
- The Column Name you would like to update
- The columns new value
The App will begin to run and update the specified column for all List Items,
The Application will run and update the Column accordingly –
And we’re done 🙂
In order to setup records management and the ability to create send-to connection and rules there is a few steps you will need to follow, it can be confusing initially but once you wrap your head around the different configuration location it starts to make sense.
- Activate the Content Organizer site feature, the Content Organizer feature is a very important feature that should be enabled on any site where Send to connections are to be used, without this feature enabled any attempt to create the send to connection will fail with a correlation ID which on SharePoint Server is easy to work out but a little more difficult to work out in SharePoint Online.
Be sure to activate this feature not only at the from location but the destination as well as the send to connection will error if it is not enabled.
- Once the feature is activated you will need to head to your Site Admin page for those new to O365 and SharePoint online it’s https://yourtenantname-admin.sharepoint.com
Once you are on the Send to connection page you will need to fill in a few of the details necessary to start routing the documents
Display Name – is the field that on the send to connection in the SharePoint ribbon this will be seen to the end user
Send To URL – this field is very important to enter in correctly you must enter the site url along with “/_vti_bin/officialfile.asmx” or else the send to connection will error on creation.
Click Add Connection
Now when I select a document in my document library my newly created send-to connection comes available as shown below, so what happens if we try to move this document now?
The Page will refresh with Operation completed successfully message along with the new url of the document, by default the documents are routed to the ‘Drop off library’ in Part 2 I will take you through setting up rules to have the documents moved to a specific document library at your selected destination site.
Recently Microsoft released SharePoint Server 2013 SP1(February 25th 2014 to be precise) full of new features and bug fixes SP1 will be a critical update to SharePoint Server Farms over the next coming months… so what exactly is fixed and new to SP1? Click here to find out the full list
Now that we know the changes and fixes involved with SP1, let’s install SP1.. this how to guide will cover end to end Installing and configuring SP1, but I strongly advise you to run the Service Pack on a dev environment first.
Installing SP1 Binaries
First you will need to download the SharePoint Server 2013 Service Pack 1 package
What Servers should I Install Service Pack 1 on? Which Server(s) first?
This is a very important step and can be detrimental to your end result, make sure you run SP1 on your App Servers or the server(s) that run Central Administration first before installing on any other server, it is also important to note that Service Pack 1 will need to be installed on any Server that has SharePoint Installed and is connected to your farm or the consequences being that server will be no longer of use until it is upgraded.
Once downloaded and copied onto each SharePoint Server,
Accept the Microsoft Software License Terms & click Continue
Your Installation will to detect your current Installation & begin to install the Service Pack 1 files.
Once the Installation is complete on your SharePoint Servers I generally reboot each server, it’s something that I found has worked in the past but I do recognize it’s probably me over analyzing, so feel free not to reboot the servers.
If I check my Servers farm status now you will recognize my database version is still 15.0.4420.1017 (RTM SharePoint Server 2013)
You will also recognize that the Status of each of my SharePoint servers have a status of ‘Upgrade Required’ which brings us to the second part of the article… and the place where most Upgrades go wrong!
SharePoint Products Configuration
So now we are up to running the SharePoint Products Configuration Wizard to upgrade each SharePoint Server in the farm, again I suggest that the server running Central Administration is upgraded first and only run one sever upgrade at a time, this may be an old tale but it’s certainly a rule I apply.
If you receive a prompt around not being logged in as the right user you should use the account that was used for farm configuration originally.
Run ‘SharePoint Products Configuration Wizard’
If you receive a prompt click Yes
Done, My Server has now been upgraded – now to rinse and repeat on the rest of my SharePoint Servers in the farm
Once Successful you will notice your Config Database version has now changed to 15.0.4569.1000 (SP1) and that all servers in the farm status is ‘no action required’… now you need to test, test, test every little bit of functionality in the farm J
Today I successfully passed the PRO: Microsoft SharePoint, Administrator (70-668) exam which gives me the fancy title of MCITP SharePoint 2010.. which I must admit I am more proud of then I let show…. although it’s taken me a few years to get the time to study and sit the exam it has been all worth it not only for the nice fancy new title but since I passed the SharePoint 2013 Core Solutions exams, I am now on an upgrade path to my MCSE leaving me two exams to go 🙂
Advice to all that are aiming to achieve the SharePoint Administrator PRO Certification before it’s discontinued… it’s worth it don’t let anyone stop you !