What (and where) is SharePoint Server 2009?

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I came across an interesting dialog box last week whilst trying to connect to a Microsoft Office SharePoint Server 2007 site with the SharePoint Designer 2010 technical preview.

Microsoft Office SharePoint Designer cannot be used to edit web sites on servers prior to Microsoft SharePoint Server 2009. To edit these sites, you need to use SharePoint Designer 2007.The dialog told me that Microsoft Office SharePoint Designer 2007 is needed to work with older versions of SharePoint Server but interestingly it referred to the version it wanted as SharePoint Server 2009… I’ve never heard of this (there is a new version of SharePoint for 2010, and presumably a new WSS 4.0 at the same time) but I guess no-one got around to changing the error message before the bits were shipped for the Office 2010 technical preview.

In the meantime, Bjørn Furuknap raises an interesting point… where’s the value in a technical preview of a product that doesn’t work with the existing server platform? There is a Technical Preview for SharePoint Server 2010 – but until that opens up to a wider audience it does seem a little strange that SharePoint Designer is part of the Office Technical Preview instead of the SharePoint Server one!

Linking to filtered Document Library views in SharePoint

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’ve been doing a lot of work in SharePoint recently – nothing very technical, just Site Administrator stuff customising the basic SharePoint site structure to meet the requirements of my particular project. One of the things that my team wanted to do was to create a diagram with clickable links to views on the document library (it’s taken some time to “educate” them that folders are not a good way to go and that they need to think about searches with appropriate views and filter – think Google, not file share – but in some cases the same document was filed three times in different folders so that it appeared in a logical hierarchy!).

I was playing around with this and noticed that the URL structure for a given filtered view was petty easy to work with. So, for example:

http://servername/sites/site/Document%20Library/Forms/viewname.aspx?FilterField1=columnname&FilterValue1=value

We can even extend it further if required with &FilterField2 and &FilterValue2 (&FilterField3 and &FilterField3, etc.).

Using this we can link directly from documents and external applications/sites to a filtered view on the entire document library, giving the equivalent of a folder view (i.e. just a small group of documents) but generated dynamically and avoiding the creation additional views that need to be maintained.

SharePoint designer speeds up the process of checking in multiple files

This content is 16 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Another day of playing with SharePoint which varied between quite interesting and extremely tedious, I thought I’d share a little tip that my colleague, Alan Dodd, gave me tonight.

After copying a load of files to SharePoint in Explorer view, it’s a lot quicker to check them in using SharePoint Designer which, incidentally, is now a free download (although registration is required).

Fast(er) entry of person/group names in SharePoint

This content is 16 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Together with my colleague, Alan Dodd, I’ve spent a considerable amount of time this week cleansing data in a SharePoint list. Quite why I can’t import e-mail addresses from an Excel spreadsheet to a column of type “Person or Group” I don’t know, but we couldn’t seem to make it work…

Checking names or browsing the directory was tediously slow; then I found that if I pasted the e-mail address, rather than the person’s name, SharePoint immediately resolved that address to a name and let me move on to the next record… might be a timesaver for someone?

An introduction to business intelligence for IT Managers

This content is 16 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few weeks ago, I caught one of the IT Manager series of webcasts that Microsoft is running, where Andrew Fryer was introducing Business Intelligence for IT Managers (I’ll steer clear of the obvious joke about IT managers and intelligence there… I might want a job as an IT Manager one day…). This was an interesting presentation for a couple of reasons: it’s not a topic that I know well; and Andrew presented 290 slides in less than an hour (which sounds a lot, but it wasn’t – he used slides with just a few words or a picture, in rapid succession – and I like that style).

I can’t find the recorded version of the presentation online but this blog post attempts to capture the main points.

According to Wikipedia, Business Intelligence (BI) can be defined as follows:

“Business intelligence (BI) refers to skills, technologies, applications and practices used to help a business acquire a better understanding of its commercial context. Business intelligence may also refer to the collected information itself.”

That’s a bit of a mouthful, but basically it makes BI seem hard. So, let’s think about intelligence without the business context – is it: knowledge and understanding (we used to think the world was flat!); about meaning and context (some information can seem obvious without context); about foresight (to predict future events); the ability to solve complex problems; or the ability to make decisions?

We make decisions all the time – and some of those decisions are poor ones – so if intelligence is about making decisions (and decisions require people), what makes a good decision? The answer is information. The information provides the meaning and context together with the background information (knowledge and understanding, likelihood of a given event occurring, etc.) to allow someone to make the right decision.

Information has been used throughout history to share stories, to learn and to discover things. Over time, information has helped to provide answers and to unlock secrets, which allowed innovation. Information has provided answers – and answers have allowed people to make decisions.

In a business context, the information is derived from data (about people, products, places, etc.). Where there are questions (which products are best? how are the sales figures looking? how are my people?), some insight is required to provide meaning and to convert raw data to information.

That data needs to be stored – originally it was stored in paper files and later on computer disks and tapes – but it also needs to be managed. The advent of databases provided a means for data to be stored and managed but business applications were needed to abstract the management of the database from business end users. These business applications provided a better way to collect data, easing the process of data entry and managing access, to ensure that those who needed access were able to find answers to business questions. But is wasn’t easy – the data was sourced from many locations. Reports were one approach, but they were one-dimensional and siloed, fragmented and lacking insight.

The advent of data warehouses allowed data from multiple locations to be organised, managed and accessed – or consumed. Now the business applications could analyse as well as report and the term “Business Intelligence” was born. Promising more access, from more locations, BI vendors created demand for more data. This led to businesses wanting faster access to data (improved performance). But as the volume of data exploded, so did the use of personal computers, and most data ended up in desktop productivity applications like Microsoft Excel, and Access. There was no single version of the truth upon which to base decisions, the data was hard to maintain and the BI tools cost a lot of money, so vendors had to find a way to reduce costs and offer increased functionality. The result was a period of vendor consolidation in the BI tools space and the formation of a few BI platforms, from companies like Oracle, SAP, IBM and Microsoft, offering more tools and more functionality, for both online and offline access.

But, for all the promises, BI tools were still not working. Business users were still confused and the business couldn’t get the answers that were needed. It wasn’t about people – it was still about disparate systems, with access to data controlled by the IT department. An overstretched IT department. So business users started to circumvent IT departments, but the BI tools were not intuitive and the users didn’t have the time to be IT administrators. Suddenly BI was about usability, and turning data into the right format to be easily consumed by people, with that data managed by IT.

There’s not just the data in the databases to consider either – there is unstructured data too. That unstructured data comes from places like blogs, wikis, e-mail messages, documents, presentations, and videos – at one point analysts considered that 80% of business was conducted based on unstructured data.

So BI is about the right person, accessing the right data, at the right time – and it needs to be people-centric because it’s generally people that make decisions, not computers. Businesses need to do more to collaborate, search, and communicate about questions and answers in order to drive innovation. Even in today’s times of economic uncertainly, BI is still a priority at CxO level in order for businesses to do more with less, to provide better insight for better decision-making, for more people.

Reporting and scorecards are important components of the BI toolset, along with dashboards to display key performance indicators, for analysis. On the desktop we still use applications like Excel but the data lives in the warehouse. Other BI features include data mining (e.g. the shopping basket analysis that supermarket chains carry out using our loyalty cards). For unstructured data, we have portals for collaboration.

In today’s BI implementations the critical success factors are sponsorship (at a senior level in the company), a compelling need, a culture of analysis (rather than looking for divine inspiration) and, most importantly, partnership between the IT department and business users.

I don’t pretend to know anything about any of the specialist BI tools but, on the Microsoft infrastructure side, we already have some useful tools. Office gives us desktop applications like Excel, there are collaboration services in the form of SharePoint products and technologies, and we have a scalable database engine in SQL Server – there’s more information on Microsoft’s BI blog and learn more about the products on Microsoft’s BI website. There’s also advice on planning for BI in the SharePoint Server TechCenter, webcasts, videos, virtual labs and podcasts and more advice for IT Managers and their teams on the TechNet website. Finally, if you just want the highlights and a bit of technical analysis, Andrew Fryer’s “Insufficient Data” blog is worth a read.

Controlling the view on diagrams generated with Visio 2007’s Save As Web feature

This content is 16 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’ve been doing some work recently with a “taxonomy” of technology “building blocks”. Even though a taxonomy is technically expressed as a hierarchy, technology terms do not really fit into a hierarchical structure – what we really need is a network diagram but management want it to look like an organisation chart (some cynical people might say that’s all they understand)!

My colleague, Alan Dodd, who understands TOGAF (I’m not an enterprise architect) has been instrumental in defining a structure that we can slice many different ways, generating views based on particular metadata and he’s also the one who came up with the idea of using Visio 2007’s Organisation Chart Wizard to import data from an Excel spreadsheet and use the column headings as metadata. Excel data for importing into Visio with the Organization Chart WizardFor example, if I have columns of: Item; Parent Item; Vendor; and URL, I can build the hierarchy using the Item and Parent Item columns and the Vendor and URL columns can be defined as metadata on the shapes in Visio, from where I can save the whole diagram as a web page (and the URL data will actually work as a link). Add a bit of conditional formatting and we have something that’s actually quite usable as a navigational tool for linking to the various technology building blocks.

The problem I had was that my diagram was huge and needed to be zoomed it to 500% in order to be legible. Increasing the font size didn’t help either, as that just needed larger shapes, making the overall diagram larger (and so the default, whole page, view was just as tiny). What I needed was a way to adapt the zoom factor on the diagram… for instance to set the initial view to 500%.

It turns out that’s perfectly possible using ?zoom=500 on the end of the URL to load the diagram. After a brief conversation on the Microsoft Discussion Groups, John Goldsmith has helpfully posted the four basic URL parameters accepted by Visio-generated diagrams served via HTTP.

The next steps will be to make the diagram zoom closer than 500% and then the big one… to automatically generate the Excel data from a SharePoint document library. Answers on a postcard…

Installing Windows SharePoint Services on Windows 7 (or Vista)

This content is 16 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Windows SharePoint Services (WSS) is not supported on a client operating system, but that’s not to say it shouldn’t run – right? After all, Windows client releases include a web server and can run a database service – that should pretty much cover the basics (back in the days of Windows NT it was generally reckoned that the differences between the Workstation and Server releases were just a few registry entries – but even if that was true then, there are a few more differences today)! In response to this, the guys at Bamboo Nation came up with an installer for SharePoint on Vista and, even though it’s been around for a while (thanks to Garry Martin for alerting me to this), last week I finally got around to trying it out on Windows 7.

It seems to work well but, having never installed SQL Server 2008 Express Edition (WSS needs access to a SQL database) I needed to combine two very good resources (the Jonas Nilsson’s installation guide for Windows SharePoint Services 3.0 SP1 on Windows Vista and Symantec’s article on installing and configuring SQL Server 2008 Express) – the result is my installation notes (repeated in full here in case either of those articles ever disappears but for screen shots, refer to the originals – or to Jim Parshall’s video tutorial):

  1. Gather together all the resources that will be required. Assuming that Windows is already running, the remaining components are:
  2. Install and configure SQL Server 2008 Express Edition:
    • SQL Express may be downloaded with or without tools – I went for the “without” option but the tools may be useful for troubleshooting purposes. If you’re installing on an older platform, there are some pre-requisites (.NET Framework 3.5 SP1, Windows Installer 4.5 and Windows PowerShell 1.0) but my Windows 7 client already had these (or later versions).
    • Run the SQL Server Express installer and follow the wizard. It’s fairly straightforward but there are a couple of things to watch out for:
      • For the instance configuration, specify MSSQLSERVER as both the named instance and the instance ID.
      • For the server configuration, use NT AUTHORITY\SYSTEM (no password) as the SQL Server database engine account name and set the SQL Server Browser startup type to Automatic.
      • For database engine configuration, either Windows or mixed mode authentication may be used (I stuck with the defaults) but the installer will not continue until users or groups are specified for unrestricted access to the SQL server. SQL DBAs and security guys will probably have lots of best practice advice here for use with production servers but I took the view that it’s probably nothing too much to worry about on a developer workstation and simply gave the necessary rights to the account I was running as.
  3. Install and configure Internet Information Services in Control Panel, Programs and Features by clicking the option to turn Windows features on or off and enabling:
    • Internet Information Services
      • Web Management Services
        • IIS 6 Management Compatibility
          • IIS 6 Management Console
          • IIS 6 Scripting Tools
          • IIS 6 WMI Campatability
          • IIS 6 Metabase and IIS 6 configuration capability
        • IIS Management Console
      • World Wide Web Services
        • Application Development Features
          • .NET Extensibility
          • ASP.NET
          • ISAPI Extensions
          • ISAPI Filters
        • Common HTTP Features
          • Default Document
          • Directory Browsing
          • HTTP Errors
          • HTTP Redirection
          • Static Content
        • Health and Diagnostics
          • HTTP Logging
          • Request Monitor
        • Performance Features
          • HTTP Compression Dynamic
          • Static Content Compression
        • Security
          • Basic Authentication
          • Request Filtering
          • Windows Authentication
  4. Install the WSS on Vista setup helper application by running wssvista.msi.
  5. Install WSS by:
    • Locating the WSS on Vista helper application files in %programfiles%\WSSonVista\Setup and running setuplauncher.exe.
    • Pointing the setuphelper to the WSS installer (sharepoint.exe)
    • Following the WSS installation wizard, selecting an advanced installation for a web front-end server, creating a new server farm, and supplying the details for the local SQL database (including the account details).
  6. At the end of the WSS installation, take a note of the port number used, and then navigate to http://localhost:portnumber/. If all goes well, then you should see the SharePoint Central Administration site in your browser:
    Windows SharePoint Services running on Windows 7

Finally, a couple of additional notes:

  • I ran all of this as a standard user, answering just a few UAC prompts at the appropriate points to elevate my privileges).
  • These instructions will allow access to SharePoint site from the local machine; however it will be necessary to create some firewall exceptions if remote client access is required.

Groove, SharePoint or OCS Group Chat – which works for you?

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Earlier today I was in an interesting session at the Microsoft UK user groups community day when Art Ho gave a presentation on group chat and discussion forums. What became apparent in Art’s presentation is that Microsoft has a number of products which, on the face of it, offer similar features and functionality, but each has its own strengths and weaknesses:

Groove Discussions SharePoint Discussions Groove Chat OCS Group Chat*
Persistent Yes Yes Yes Yes
Federation Yes Yes Yes Yes
Integrated Sort of Yes No no
Search Yes Yes (strong) No Yes
Realtime No No Yes Yes
Collaborative Yes Yes No No
Offline Yes No Yes No

* OCS Group Chat is still a beta product at this time and was formerly Parlano MindAlign (Parlano were acquired by Microsoft last year)

Basically, it breaks down like this. Think about the purpose of the collaboration and what end users need. Do they need search? If so, then SharePoint is the clear leader. Are you looking for one product, or can a mixture of products meet the requirements (e.g. collaborate using a Groove workspace and publish the final document to a SharePoint document library)? Finally, you can have real-time or collaborative working, but it seems you can’t have both (at least with this technology selection).

(Note that other solutions are available, this just compares three Microsoft products that all seem to compete in the same space.)

Free SharePoint enterprise search training

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Last autumn, I attended some technical training on Microsoft Office SharePoint Server (MOSS) 2007 Enterprise Search, led by Martin Harwar. I just got an e-mail from Martin to say that he has recorded over 18 hours of free technical training about enterprise Search with SharePoint technologies. Based on my experiences of attending the course, it’s worth checking out for anyone looking to learn (or refresh) their MOSS knowledge.

SharePoint, Workflow and Microsoft Search Server

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Earlier this week, I headed into Microsoft’s offices in London for an evening meeting of the SharePoint User Group UK.  I’m not a SharePoint expert by any stretch of the imagination (I’ve looked at various SharePoint products over the years but have no implementation experience) but I am interested in the product’s development – particularly as it seems to me that it is finally starting to gain some traction with customers.

The first session was a deep dive into developing Workflow with SharePoint and InfoPath, presented by Chris O’Brien.  To be perfectly honest, this went a little too deep into developer concepts for me to follow, but Chris has written about it on his blog for anyone who wants the details.

The second session was presented by Andrew Woodward, who looked at Microsoft Search Server 2008.  I’m particularly interested in this as it’s only a few months since I spent some time learning about implementing enterprise Search using Microsoft Office SharePoint Server (MOSS) 2007 and the replacement of MOSS for Search with Search Server provides many new options for federated search that will be eventually be backported into the main MOSS product (initially via Microsoft Update and then as part of MOSS 2007 service pack 2).  What’s particularly interesting is the positioning of Microsoft Search Server 2008 Express as a free product – meaning that even small businesses can afford to implement SharePoint for enterprise search (and also potentially allowing for the creation of SharePoint appliances, much like the Google Search Appliance).  There’s more about Microsoft’s enterprise search products (including Search Server) on the Microsoft website.

Overall, the evening was interesting (and well attended) – for future events, check out the SharePoint User Group UK website.