HideFromDelve!
Just stumbled on this buried in the middle of a Search Schema document.To hide documents from Delve you basically create a new Site Column named HideFromDelve as a Yes/No column, add it to your library and then set this column to Yes for everything you don't want to show up in Delve.
If you've not heard of Delve then start here: https://support.office.com/en-US/article/What-is-Office-Delve-1315665a-c6af-4409-a28d-49f8916878ca?ui=en-US&rs=en-US&ad=US
.
Microsoft Azure has had a pre-configured SharePoint 2013 image for quite a while, but you still had to create a SQL Server image to make it work and then run the SharePoint wizard to create the farm. Now they have a wizard approach to quickly create a ready to use three server basic farm or a nine server high-availability farm. Just click, click, click, wait a while and start playing with SharePoint! Just the thing for evaluations, demos and development.
The three server farm includes a SQL server, a DC server and a SharePoint server. The high-availability farm includes two DC servers, three SQL server servers, two application servers and two SharePoint web servers. (This one should drain your Azure budget! Remember to turn these off when not in use.)
Details on both configurations can be found here: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-sharepoint-farm-config-azure-preview/
Here's the steps to create your Azure SharePoint 2013 farm: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-sharepoint-farm-azure-preview/
A few observations:
Things you will need to do to have a complete SharePoint:
Now all we need is a volunteer to create the PowerShell scripts to do the final work for us!
.
I'll be presenting the 20488 Developing Microsoft SharePoint Server 2013 Core Solutions class in two weeks, actually a week and a half (time flies!). February 16th, 2015. We've set up this class for both local and remote students. Online students will be able to view the class and have remote access to the lab computers.
Just as a little incentive, when you register enter my code of "TTN50" and get a $50 discount on the class.
Details here: http://www.maxtrain.com/Classes/ClassInfo.aspx?Id=101693
In this 5 day instructor-led course, students learn core skills that are common to almost all SharePoint development activities. These include working with the server-side and client-side object models, developing and deploying features, solutions, and apps, managing identity and permissions, querying and updating list data, managing taxonomy, using workflow to manage business processes, and customizing the user interface.
At Course Completion
After completing this course, students will be able to:
More details at http://www.maxtrain.com/Classes/ClassInfo.aspx?Id=101693
.
Actually a few notes…
I found two interesting SharePoint 2013 search books at Amazon and ordered them. I just received them… and I'm going to return both of them. This will be the first time I have ever returned a printed book!
Self-publishing is easy, fun and very rewarding. But…
Note 1: All printed technology books must have an index! Indexes are easy to create in Microsoft Word. You can either create a busy looking, but not too useful, index using the automatic features, or invest a couple hours and manually create a very useful one. In any case be forewarned, I do not buy technical books that do not have an index!
Note 2: Do not tell me in the book's intro that all of the content in the book is straight from your blog articles. Especially don't tell me that I could have gotten it all for free from the blog. (Boy, do I feel dumb paying for that book.) Don't just copy your blog articles and call it a book. Books that build on your blog articles can really be useful. Creating the book is your opportunity to expand on the topic and rewrite the quickly written text into nice complete articles. Fix up the screen captures. Fill in the gaps. Rewrite the hastefully written text. You know… create what you would have done in the blog if you had time to do it right the first time.
Note 3: Do not fill the pages with giant screen captures so there's an average of one screen capture and only one or two sentences per page. That works for a kid's picture book, but does not deliver much value as a technical book. In any case, please, please size and crop the screen captures so they are always readable and to the point.
Note 4: Pay somebody, anybody, to proofread the book. They don't have to know the technology. They just have to know some basic English and know enough to ask if all the code really should be underlined! If you want to really do it right, find someone who has heard of the Chicago Manual of Style, At a minimum buy yourself a copy of the Microsoft Manual of Style, and give a copy to your proofreader.
Note 5: Look at some of the tech books from the big publishers. I mean, open them, look at the details, note what is there and what is not. Note the use of "front matter". Note that page numbers go on the outside edges of pages, not in the gutter. Note the use of font size and the limited use of bold and italics.
</rant>
.
