It has been quite awhile since I had presented at a user group or event!  I think the presentation went very well, had plenty of material and I think plenty of demos to help give attendees an idea of what's possible with SharePoint 2013 Search.  I'd like to expand on this presentation and present it again hopefully at another event.  Ideally I'd like to add some demos about using Knockout and AngularJS.


http://www.spsevents.org/city/Philadelphia/Philly2014/home

Presentation Link : Code/Slides

 


 

This past weekend I presented at the SharePoint Satuday event in Philly.  It was another great SharePiont Saturday with over 400+ people showing up to the event.

I presented on setting up a Continuous Integration process with SharePoint.  I think overall the session went well, demo's went off smoothly and there were a lot of good audience questions which sparked some good conversations.

 

http://www.sharepointsaturday.org/philly/default.aspx 

 

Presentation Link : Code/Slides

 


What?  A new blog post? You have to be kidding me!

To have the core SharePoint search results webpart display its results as pure XML so that you can see what is being returned by the search engine, paste this in as the XSLT transform

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" />
<xsl:template match="/">
<xmp><xsl:copy-of select="*"/></xmp>
</xsl:template>
</xsl:stylesheet>


Posted in:   Tags:

For some reason I can never remember these all so I’m posting here more for my reference than yours but hopefully it will help someone else out.

STS#0 Team Site WSS
STS#1 Blank Site WSS
STS#2 Document Workspace WSS
MPS#0 Basic Meeting Workspace WSS
MPS#1 Blank Meeting Workspace WSS
MPS#2 Decision Meeting Workspace WSS
MPS#3 Social Meeting Workspace WSS
MPS#4 Multipage Meeting Workspace WSS
CENTRALADMIN#0 Central Admin Site WSS
WIKI#0 Wiki Site WSS
BLOG#0 Blog WSS
BDR#0 Document Center MOSS
OFFILE#1 Records Center MOSS
OSRV#0 Shared Services Administration Site MOSS
SPS#0 SharePoint Portal Server Site MOSS
SPSPERS#0 SharePoint Portal Server Personal Space MOSS
SPSMSITE#0 Personalization Site MOSS
SPSMSITE#0 Contents area Template MOSS
SPSTOPIC#0 Topic area template MOSS
SPSNEWS#0 News Site MOSS
CMSPUBLISHING#0 Publishing Site MOSS
BLANKINTERNET#0 Publishing Site MOSS
BLANKINTERNET#1 Press Releases Site MOSS
BLANKINTERNET#2 Publishing Site with Workflow MOSS
SPSNHOME#0 News Site MOSS
SPSSITES#0 Site Directory MOSS
SPSCOMMU#0 Community area template MOSS
SPSREPORTCENTER#0 Report Center MOSS
SPSPORTAL#0 Collaboration Portal MOSS
SRCHCEN#0 Search Center with Tabs MOSS
PROFILES#0 Profiles MOSS
BLANKINTERNETCONTAINER#0 Publishing Portal MOSS
SPSMSITEHOST#0 My Site Host MOSS
SRCHCENTERLITE#0 Search Center MOSS

 

So, you may be asking…(for example), where the hell did I get STS#0 from?  The answer is pretty easy…

STS = Site Template Name

#0 = Site Template Configuration number.

If you go to your SharePoint 12 hive (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12) and look at the template folder (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\1033\XML) you’ll see a list of XML files which tell SharePoint what templates are available to it.  Crack open WEBTEMP.XML and take a look and you’ll see all the WSS templates that are available to you.

Here is a snippet of the XML that tells SharePoint about team sites and its various configurations..

<Template Name="STS" ID="1">
    <Configuration ID="0" Title="Team Site" Hidden="FALSE" ImageUrl="/_layouts/images/stsprev.png" 
	Description="A site for teams to quickly organize, author, and share information. It provides a document library, and lists for managing announcements, calendar items, tasks, and discussions." 
	DisplayCategory="Collaboration" >    
    </Configuration>
    <Configuration ID="1" Title="Blank Site" Hidden="FALSE" ImageUrl="/_layouts/images/blankprev.png" 
	Description="A blank site for you to customize based on your requirements."
	DisplayCategory="Collaboration" 
	AllowGlobalFeatureAssociations="False" >    
    </Configuration>
    <Configuration ID="2" Title="Document Workspace" Hidden="FALSE" ImageUrl="/_layouts/images/dwsprev.png" 
	Description="A site for colleagues to work together on a document. It provides a document library for storing the primary document and supporting files, a tasks list for assigning to-do items, and a links list for resources related to the document." 
	DisplayCategory="Collaboration" >    
    </Configuration>
 </Template>

Now if you check back to my list above, I’m sure you can see now how you get STS#0, STS#1 and STS#2.

 

*** I’ll try and do a SharePoint 2010 comparison to this list above pretty soon.


Posted in:   Tags:
tony testa posted on November 19, 2009 03:45

I’ve been doing SharePoint 2007 silent installs now for quite awhile.  SharePoint 2010 beta is out and I obviously wanted to see if the same files still worked so that I can use the same processes I have in place when I do installs.  Below is what I was using before as my config.xml answer file:

<Configuration>
    <Package Id="sts">
        <Setting Id="LAUNCHEDFROMSETUPSTS" Value="Yes"/>
        <Setting Id="REBOOT" Value="ReallySuppress"/>
        <Setting Id="SETUPTYPE" Value="CLEAN_INSTALL"/>
    </Package>
 
    <Package Id="spswfe">
        <Setting Id="SETUPCALLED" Value="1"/>
        <Setting Id="REBOOT" Value="ReallySuppress"/>
        <Setting Id="OFFICESERVERPREMIUM" Value="1" />
    </Package>
 
    <Logging Type="verbose" Path="%temp%" Template="Office Server Setup(*).log"/>
    <Display Level="none" CompletionNotice="Yes" />
    <PIDKEY Value="{MSDN KEY FOR EDITION OF SHAREPOINT 2007}" />
    <Setting Id="SERVERROLE" Value="APPLICATION"/>
    <Setting Id="USINGUIINSTALLMODE" Value="0"/>
</Configuration>

If your not familiar, config.xml comes from the templates that Microsoft gives you in the installer disc.  If you mount the SharePoint 2007 installer disc and dig into the install directory, you’ll see a “Files” directory.  If you poke in there you should see the following:

image

If you drill into one of those SharePoint 2007 Files folders you’ll find a config.xml file which is the shell of what you’ll need to do a silent install.  Below is what the SetupFarmSilent config.xml looks like

<Configuration>
    <Package Id="sts">
        <Setting Id="LAUNCHEDFROMSETUPSTS" Value="Yes"/>
        <Setting Id="REBOOT" Value="ReallySuppress"/>
        <Setting Id="SETUPTYPE" Value="CLEAN_INSTALL"/>
    </Package>
 
    <Package Id="spswfe">
        <Setting Id="SETUPCALLED" Value="1"/>
        <Setting Id="REBOOT" Value="ReallySuppress"/>
        <Setting Id="OFFICESERVERPREMIUM" Value="1" />
    </Package>
 
    <Logging Type="verbose" Path="%temp%" Template="Office Server Setup(*).log"/>
    <Display Level="none" CompletionNotice="no" />
    <PIDKEY Value="Enter PID Key Here" />
    <Setting Id="SERVERROLE" Value="APPLICATION"/>
    <Setting Id="USINGUIINSTALLMODE" Value="0"/>
</Configuration>

The only real difference from the config.xml at the top and the one right above is that I changed CompletionNotice="Yes" which tells the installer to let me know when the install is done.

 

Ok, so now that your armed with this silent install config file, how do i run it?  Easy!

setup.exe /config c:\{location of your config file}\config.xml

 

Now your probably asking yourself what’s the story with SharePoint 2010?  Is it the same process or different?

Well, here is what the installer Files directory looks like for SharePoint 2010:

image

As you can see nothing really different here other than its 1 folder less than the 2007 version, the “SetupFarmSidebySide”.

Here is what the SharePoint 2010 config.xml looks like for the “SetupFarmSilent”

<Configuration>
    <Package Id="sts">
        <Setting Id="LAUNCHEDFROMSETUPSTS" Value="Yes"/>
    </Package>
 
    <Package Id="spswfe">
        <Setting Id="SETUPCALLED" Value="1"/>
        <Setting Id="OFFICESERVERPREMIUM" Value="1" />
    </Package>
 
    <Logging Type="verbose" Path="%temp%" Template="SharePoint Server Setup(*).log"/>
    <!--<PIDKEY Value="Enter Product Key Here" />-->
    <Display Level="none" CompletionNotice="no" />
    <Setting Id="SERVERROLE" Value="APPLICATION"/>
    <Setting Id="USINGUIINSTALLMODE" Value="0"/>
    <Setting Id="SETUP_REBOOT" Value="Never" />
    <Setting Id="SETUPTYPE" Value="CLEAN_INSTALL"/>
</Configuration>

Lets compare a 2007 and a 2010 config.xml

image

The file on the left is the 2007 config.xml and the file on the right is the 2010 config.xml.  As you can see they are basically the same, the only real difference I can see is that the 2010 config.xml moved 1 or 2 of the settings around, but essentially the files contain the same information.

Now that we’ve compared the files, does the same command to setup SharePoint 2007 silently from a config.xml file still work in 2010?

I ran the following command against the SharePoint 2010 installer (after installing all the SharePoint 2010 prereq’s of course.  See http://technet.microsoft.com/en-us/library/cc262485%28office.14%29.aspx).

setup.exe /config c:\{location of customized config}\config.xml

After about 7 or 8 minutes I got the following message back

image

So as you can see, doing a silent install in SharePoint 2010 is pretty much the same as it was in 2007.  Now that you’ve got SharePoint 2010 installed, its time to do a scripted configuration of the farm.  Look for a blog posting soon on doing so because I’ll be going through the steps personally and will certainly share the info for all.


Posted in:   Tags:
Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2014 Tony Testa's World