Serve's talking about Records Management in 2007

Servé, who is a dear collegue of mine, has a nice little introduction about the new functionality in 2007 that's called "Record Management". Go ahead and read.. read I say!

Customizing 2007 by Liam

I stumled upon Liam's blog by accident really and I noticed his post about customizing MOSS 2007 via Sharepoint Designer. Basically he explains the difference between customizing 2003 and 2007.. and especially for me he posted a lot of screenshots ;)

Before customizing:

After customizing :

You have to look good, I know, but there is a significant difference!

Check the whole story @ Liam's Blog!

Just when I wanted to begin with defining a custom workflow, Joris posted a nice introduction with very useful links! God bless those belgians :)

A good starting point is the white paper – Walkthrough : Creating Office SharePoint Server 2007 workflows with Visual Studio but there are still some things you should really now before starting developing your own workflows on top of the SharePoint 2007 platform. This is the first of a series of postings about workflow in SharePoint 2007. InfoPath 2007 is used in a couple of places in a SharePoint driven workflow: In the workflow initiation and association forms which are used to set workflow parameters before a workflow starts In a workflow modification form which enables users to alter the workflow while it is running In the workflow task forms which is opened when a user clicks the task link which is assigned within the workflow process. When you want to develop a SharePoint workflow with Visual Studio 2005 you will first need to install the SharePoint workflow project templates. These Visual Studio project templates are installed when you install either the ECM Starter Kit (for Microsoft Office SharePoint Server ) or the Workflow Developer Starter Kit for Windows SharePoint Services 3.0... Read more @ JOPX blog

Release dates Office 2007 in November confirmed

From Marten and Amanda:

Release dates Office 2007 in November confirmed Darren tells us that Office 2007 is added to the November pricelist, which means the release is still on schedule. Exact dates to be announced... "An internal email from Chris Capposela (head of IW) to field sales confirms that 2007 will get added to the price list in November. This is excellent news and a strong indicator of our confidence. That said, usual caveats apply about how product performance and quality will ultimately dictate availability. Our development schedule remains on track to deliver the 2007 Microsoft Office system by the end of 2006, with broad general availability in early 2007. Feedback on quality and performance will determine the exact dates."

Workspaces don't migrate very well

I'm getting errors while migrating workspace teamsites. The error I'm getting is : RENDER FAILED! So none of my tabs are visible, also items within document libraries are also not visible and do contain the same error. The strange thing is that all the 'normal' teamsites don't give any errors (besides the fact that some custom webparts cannot be displayed properly)

Sharepoint 2007: compatibility pack for Office XP 2003

From Servé :

If you have installed Office XP or Office 2003 you cannot work with the new Office 2007 file formats unless you install the compatibility pack from Microsoft..

?contents=1 still works in 2007!

Well since i'm busy with the migration options, I now regurarly come accross some sites that won't open since I didn't migrate custom webparts. To close this webparts you must access the webparts maintenance page which is not accessible via a link right now. But it still works like the 2003 way. You just paste "?contents=1" at the url (so you're link looks like this : "http://server/sites/site/default.aspx?contents=1") Pretty neat :)

2003 to 2007 migration

As I blogged earlier, I'm trying to migrate existing 2003 sites to a 2007 environment. The only solution here is (because the 2007 environment is set on a single test machine without a 2003 installation) to migrate the content databases. Things I'm running into are : - large content databases causes the 'migration wizard' to fail, although I can resume the conversion after the failure, this is not what I want to see. I reckon that the failures are due the lack of memory on my testmachine - small content databases (made especially for this migration due to site backups from production environment to a acceptation environment in a new content database) are relatively easy to convert and no errors are given. Now I should specify that a large content database in this context is about 10gb big and a small content database is around 60mb. So there is quite a big gap to be covered :)