Discussion Board migration issue, solved using Powershell

I recently had the following issue.

A customer is migrating NNTP (news) groups from Exchange to SharePoint. The Exchange newsgroup will be migrated to SharePoint discussion boards. It’s possible for a (power) user to open the SharePoint list in outlook and “copy” the items to the SharePoint (discussion board) list. They have to keep in mind to start with the oldest item (to keep to messages in the right order) and they can only copy 500 items at once.

That was no problem, but ….. the newly created messages on SharePoint are the owned by the person that is copying the items (off course).

As a SharePoint enthusiast is immediately said i thought this could be solved using powershell. So i did some investigating, and indeed powershell was able to update the requested field (Author).

But, and now we come to the essence of this post, there was some unwanted side-effect.

Normal behavior of a discussion board, is that every reply has a folded quote of it’s parent item. It’s a hyperlink you can click to see the parent message.

What happened was that the post that had been updated by powershell, didn’t have this functionality anymore. The parent message was fully displayed in every edited post, and couldn’t be collapsed.

So what was causing this? Guess what, if the [Created] and [Modified] are not equal, this is what happens. I updated my script to not only adjust the Author, but also (at the end) synchronize the Created and Modified field.

Problem Solved !

SP2 bug solved

remember the bug/issue with sp2.

after installing sp2 your MOSS installation would revert to a 180 days trial version.

today, microsoft released the solution for this problem.

Attention: Important Information on Service Pack 2

We take product quality seriously and make every effort to avoid and resolve issues that adversely impact our customers.  Unfortunately, we have recently discovered a bug with Service Pack 2 (SP2) that affects all customers that have deployed it for SharePoint Server 2007.

During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users. Continue reading

Bug? When you install the 2007 Microsoft Office servers Service Pack 2, the product expiration date is activated incorrectly

Source

During the installation of the 2007 Microsoft Office servers Service Pack 2, a product expiration date is activated incorrectly. This means that any of the products that are listed in the “Applies to” section will expire 180 days after Service Pack 2 is deployed, as if it were a trial installation. The activation of the expiration date will not affect the regular function of these products until the expiration date passes, 180 days after Service Pack 2 is deployed. If the product expires, it will not affect data, configuration, or application code. However, it will make the Office Server product inaccessible for end-users.

Office SharePoint Server Trial with Enterprise Client Access License, or a similar product, is displayed on the Convert License page.

CAUSE

This issue occurs because of the installation of the 2007 Microsoft Office servers Service Pack 2. All installations of this service pack will result in this issue.

Resolution

To resolve this issue manually, type the product key on the Convert License Type page. To do this, follow these steps:

  1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
  2. Click the Operations tab.
  3. Click Convert License Type.
  4. In the Enter the Product Key text box, type your product identification number, and then click OK.
  5. The License Synchronizer Job will run on all computers in the farm after a few moments. After all the computers have updated their license from the timer job, the Convert License Type page will reflect the correct license.

April Cumulative Update Packages Ready for Download

You may already read from blogs about April Cumulative Update for separate components in SharePoint. Now, the server-packages (also known as “Uber” packages) of April Cumulative Update for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 are ready for download.

Download Information

Windows SharePoint Services 3.0 April cumulative update package
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=968850

Office SharePoint Server 2007 April cumulative update package
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=968851

Detail Description

Description of the Windows SharePoint Services 3.0 April cumulative update package
http://support.microsoft.com/kb/968850

Description of the Office SharePoint Server 2007 April cumulative update package
http://support.microsoft.com/kb/968851 (Link not live yet)

Installation Recommendation for a fresh SharePoint Server

To keep all files in a SharePoint installation up-to-date, the following sequence is recommended.

  1. Service Pack 2 for Windows SharePoint Services 3.0
  2. Service Pack 2 for Office SharePoint Server 2007
  3. April Cumulative Update package for Windows SharePoint Services 3.0
  4. April Cumulative Update package for Office SharePoint Server 2007

Please note: Start from April Cumulative Update, the packages will no longer install on a farm without a service pack installed. You must have installed either Service Pack 1 (SP1) or SP2 prior to the installation of the cumulative updates.

After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed.

The version of content databases should be 12.0.6504.5000 after successfully applying these updates.

For more in-depth guidance for the update process, we recommend that customers refer to the following articles. These articles provide a correct way to deploy updates, identify known issues (and resolutions), and provide information about creating slipstream builds.

Deploy software updates for Windows SharePoint Services 3.0
http://technet.microsoft.com/en-us/library/cc288269.aspx

Deploy software updates for Office SharePoint Server 2007
http://technet.microsoft.com/en-us/library/cc263467.aspx

Create an installation source that includes software updates (Windows SharePoint Services 3.0)
http://technet.microsoft.com/en-us/library/cc287882.aspx

Create an installation source that includes software updates (Office SharePoint Server 2007)
http://technet.microsoft.com/en-us/library/cc261890.aspx

FAQ

Q: What’s the difference between April CU and SP2?
A: Office Sustained Engineering team explained the difference on their blog: FAQ concerning Service Pack 2 and the Cumulative Updates for April 2009 for the 2007 Microsoft® Office System and Microsoft Office Servers. To be simple: April CU contains fixes that are not part of SP2. But it includes only a subset of all the files. So if you want to get everything in your farm up-to-date, you need to apply SP2 first, then apply April CU.

Q: Do you have a timeline on the updates? I’m confused.
A: Here’s an example timeline to help you understand the update schedule during 2007~2009. Cumulative Updates are released every two months. Start from April 2009, cumulative updates cannot be applied directly on RTM version of SharePoint installations. SP1 is the minimum requirement, while SP2 is recommended.

updatetimeline

Announcing SharePoint Server 2010 Preliminary System Requirements

Source

We’ve heard loud and clear that you want system requirements information as early as possible to assist in your budgeting and planning, so today we’re happy to announce (and confirm) some preliminary system requirements for SharePoint Server 2010:

  1. SharePoint Server 2010 will be 64-bit only.
  2. SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
  3. SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.

In addition to the requirements listed above we also wanted to share with you some preliminary detail about SharePoint Server 2010 browser compatibility.

To ensure the best possible experience across multiple browsers we’re focusing our SharePoint 2010 engineering efforts on targeting standards based browsers (XHTML 1.0 compliant) including Internet Explorer 7, Internet Explorer 8 and Firefox 3.x. running on Windows Operating Systems.  In addition we’re planning on an increased level of compatibility with Firefox 3.x and Safari 3.x on non-Windows Operating Systems.  Due to this focus Internet Explorer 6 will not be a supported browser for SharePoint Server 2010.

So, what can you do today to get into the best shape for SharePoint Server 2010?

  1. Start by ensuring new hardware is 64-bit.  Deploying 64-bit is our current best practice recommendation for SharePoint 2007.
  2. Deploy Service Pack 2 and take a good look at the SharePoint 2010 Upgrade Checker that’s shipped as part of the update.  The Upgrade Checker will scan your SharePoint Server 2007 deployment for many issues that could affect a future upgrade to SharePoint 2010.
  3. Get to know Windows Server 2008 with SharePoint 2007, this post is a great starting point.
  4. Consider your desktop browser strategy if you have large population of Internet Explorer 6 users.
  5. Continue to follow the Best Practices guidance for SharePoint Server 2007.
  6. Keep an eye on this blog for updates and more details in the coming months.

Below are a few common Q&A’s (which we’ll add to as required)

Q: What about Internet Explorer 6 and SharePoint 2010 publishing sites?
A: The Web Content Management features built into SharePoint 2010 will provide a deep level of control over the markup and styling of the reader experience.  These features will enable customers to design pages that are compatible with additional browsers for viewing content, including Internet Explorer 6.  A standards based browser such as Internet Explorer 7, Internet Explorer 8 or Firefox 3.x will be required to author content.

Q: Is Internet Explorer 6 officially supported by Microsoft?
A: Official Microsoft Product Support for Internet Explorer 6 will expire in July 2010. You can find additional information on Microsoft’s Support Lifecycle Policy including specific dates, product information and support offerings here: http://support.microsoft.com/gp/lifepolicy.

Q: Why are you only supporting the 64-bit versions of SQL Server 2005 or 2008 for SharePoint Server 2010?
A: This decision was based on our current test data for SharePoint Server 2010 and real world experience from customers running SharePoint Server 2007 with 32-bit SQL Server.  SharePoint performance and scalability can benefit significantly from 64-bit SQL Server and the throughput increases are significant enough for us to make the difficult decision to only support SharePoint Server 2010 on 64-bit SQL Server 2005 or 2008.  It has been our strong recommendation for some time that SharePoint Server 2007 customers take advantage of 64-bit SQL Server due to the inherent performance and scale benefits it can provide.

Announcing Service Pack 2 for Office SharePoint Server 2007 and Windows SharePoint Services 3.0

Source : Microsoft Sharepoint Team Blog

We are happy to announce that Service Pack 2 for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 has been released to the Microsoft Download Center.  It includes all the fixes prior to SP2, and also several enhancements to improve server farm performance, availability and stability. Plus, a new stsadm operation has been added to help customers prepare for the upgrade to the next version of SharePoint. We recommend installing this new service pack and to help, I’ve assembled links to the KB articles, downloads, install steps and benefits.

KB Article Links

Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2
http://support.microsoft.com/kb/953338
Description of 2007 Microsoft Office servers Service Pack 2 (SP2) and of 2007 Microsoft Office servers Language Pack Service Pack 2 (SP2)
http://support.microsoft.com/kb/953334

Download Links

Service Pack 2 for Windows SharePoint Services 3.0, x86 & x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en

Service Pack 2 for Office SharePoint Server 2007, x86 & x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en

Slipstream Builds For Windows SharePoint Services 3.0

Windows SharePoint Services 3.0 with SP2, x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en
Windows SharePoint Services 3.0 with SP2, x86
http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en

Installation Steps

To keep all the files in a SharePoint installation up-to-date, the following packages need to be applied on all servers in the farm. Service Pack 2 contains all fixes released through February of this year, so customers can install it directly on RTM build of the products.

  1. Service Pack 2 for Windows SharePoint Services 3.0
  2. Service Pack 2 for Windows SharePoint Services 3.0 Language Pack (if applicable)
  3. Service Pack 2 for Office SharePoint Server 2007
  4. Service Pack 2 for Office SharePoint Server 2007 Language Pack (if applicable)

After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed.  The version of content databases should be 12.0.0.6421 after successfully applying these updates.

For more in-depth guidance for the update process, we recommend that customers refer to the following articles. These articles provide a correct way to deploy updates, identify known issues (and resolutions), and provide information about creating slipstream builds.

Deploy software updates for Windows SharePoint Services 3.0
http://technet.microsoft.com/en-us/library/cc288269.aspx
Deploy software updates for Office SharePoint Server 2007
http://technet.microsoft.com/en-us/library/cc263467.aspx

Create an installation source that includes software updates (Windows SharePoint Services 3.0)
http://technet.microsoft.com/en-us/library/cc287882.aspx
Create an installation source that includes software updates (Office SharePoint Server 2007)
http://technet.microsoft.com/en-us/library/cc261890.aspx

Benefits

Customers can be benefited from the following enhancements with Service Pack 2.

  • Performance and Availability Improvements

Service Pack 2 includes many fixes and enhancements designed to improve performance, availability, and stability in your server farms, including:

    • New Timer job automatically rebuilds content database index to improve database performance.
    • When a content database is marked as read-only, the user interface will be modified so users cannot perform tasks that require writing to the database.
    • Performance enhancement across nearly all the components.
  • Improved Interoperability

Service Pack 2 continues to improve SharePoint interoperability with other products and platforms.

    • Broader support of browsers
      Internet Explorer 8 is added into Level 1 browser support.
      FireFox 2.0/3.0 is added into Level 2 browser support.
    • Provide improved client integration user experience with Form Based Authentication. Now the client application can store user credentials instead of asking for them every time. For more technical details please refer to the updated articles on TechNet.
      Configure forms-based authentication (Office SharePoint Server
      http://technet.microsoft.com/en-us/library/cc262201.aspx
      Configure forms-based authentication (Windows SharePoint Services)
      http://technet.microsoft.com/en-us/library/cc288043.aspx
  • Getting Ready for SharePoint Server 2010

A new preupgradecheck operation is added to stsadm tool. It can be used to scan your server farm to establish whether it is ready for upgrade to SharePoint Products and Technologies “14”. It identifies issues that could present obstacles to the upgrade process. It checks for several SharePoint Products and Technologies “14” system requirements, including the presence of Microsoft® Windows Server® 2008 and a 64-bit hardware, and provides feedback and best practice recommendations for your current environment, together with information on how to resolve any issues that the tool discovers.

The full explanation of SP2 benefits can be downloaded here:
http://go.microsoft.com/fwlink/?LinkId=148551

Related Technical Resources

Service Pack 2 Overview
http://go.microsoft.com/fwlink/?LinkId=148374

Updates Resource Center for SharePoint Products and Technologies
http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx

The full list of changes can be found here: (Excel 2007 format)
Windows SharePoint Services 3.0 SP2 Changes
Office SharePoint Server 2007 SP2 Changes

Customers can also go to this KB article for a full list of downloads for Office System 2007 SP2.
http://support.microsoft.com/kb/968170

Last but not the least important: the issue with mergecontentdb stsadm operation is fixed in SP2.

Microsoft SharePoint 14 is now Microsoft SharePoint 2010

source: Microsoft Sharepoint team Blog

You have probably seen the news announcement today where we announced the public beta for the new Microsoft Exchange Server 2010. As part of that announcement, we also talked about some of the names for the “14” wave of products including Microsoft Office 2010 and Microsoft SharePoint Server 2010. I wanted to answer some questions that I think will inevitably pop to the top of your mind:

What happened to the Office piece of the name? We love MOSS. . . .

The first thing you’ll notice is that the MOSS acronym goes away with the new name since Office is no longer in the SharePoint official name. No one should worry that SharePoint doesn’t work great with Office 2010 since we removed Office from the name, just like people didn’t worry whether SharePoint was a great portal product when we removed Portal from the 2007 name.

The primary reason why we took Office out of the name – lots of folks associate the name Office with the Office client. We wanted to take the opportunity to reestablish the Office name and brand to be synonymous with the client suite. I say “Give the people what they Want” so everyone should immediately think of Microsoft Office = Office apps.

Don’t try to acronym Microsoft SharePoint Server to MSS since MSS is already taken by Microsoft Search Server. Just remember, SharePoint is SharePoint is SharePoint.

What about Windows SharePoint Services?

When you read through the announcement, you may be wondering what happened to Windows SharePoint Services. While we didn’t announcement anything new for WSS, and I want to assure you that we’re definitely working on a new v4 version of the product. It’s too early to drill into any of the details but WSS is getting a lot of new features and will be a great release. We’ll talk more about WSS at a later date.

So, what was announced?

Here are my key takeaways from the interview with Chris Capossela:

• Exchange 2010 will lead the way for the 2010 (previously referred by its codename “14”) wave of technologies and it will be available in the second half of 2009. You can download a beta today.

• Using Office Web applications, customers will be able to create, edit and collaborate on Office documents through a browser.

• IT professionals will be able to choose to either deploy and manage on-premises or hosted as a service.

• For developers, we are working on Open APIs, deep support for industry standards and developer tool support with Visual Studio 2010

Service Pack 2 for 2007 Microsoft Office System due April 28th

source : Microsoft Update Product Team Blog

Last October, Microsoft announced the upcoming release of the 2nd service pack for the 2007 Microsoft Office System and the 2007 Microsoft Office. Today, we’re happy to provide both a formal release date, and more details on what you should expect to see in SP2.

A fair amount has been said about SP2 already, but there is a lot more to share. We’ll cover the highlights here, but please check back on April 28th when all of our documentation will be published. It is important to remember that the information provided today is by no means a comprehensive list. We worked with the individual teams in Office to come up with a list of changes that they were most proud of and felt would be most beneficial to you, our valued customers.

Continue reading

Announcing Service Pack 2 (SP2) for the 2007 Microsoft Office System

source

We’re pleased to announce that Service Pack 2 (SP2) for the 2007 Microsoft Office system is expected to be released in the near future.  Although we aren’t yet announcing the exact release date, it will fall between February and April of 2009.

Historically, we have waited to communicate details about service packs until their release (or very shortly before).  As we communicated with SP3 for Office 2003 and SP1 for the 2007 Office System, we will be taking steps to increase transparency and visibility into the Office servicing model at the request of our customers.  To that end, we would like to start sharing some details into what will be included in SP2 for the 2007 Office system.  This is by no means an exhaustive list of everything included in this service pack and we will share more details prior to the final release, but we want to start communicating to customers what they should be aware of at a high level.

To be fair, this is not the first time we have talked about SP2.  Several months ago, we announced that we’ll be further demonstrating our increased commitment to interoperability by including support for Open Document Format (ODF), XML Paper Specification (XPS), and Portable Document Format (PDF) in SP2.  In addition to those file format additions, some other highlights that you’ll find in SP2 include:

For Office Desktop Programs:

· Improved Outlook Calendaring Reliability

· Improved Outlook Performance

· Enabling Object Model support for Charts in PowerPoint and Word

· Improved cryptographic functionality by supporting all cryptographic algorithms offered by the operating system

· Improved functionality in Excel’s charting mechanism

· Ability to ungroup SmartArt graphics (and as a result, the ability to add animations to them in PowerPoint)

· Ability for Visio to export UML models to an XML file compliant with the XMI standard

· Tool that enables the uninstall of Office client Service Packs

For Servers:

· Performance and manageability improvements to variations in Enterprise Content Management (ECM) including STSADM commands for repairing links between source and target pages

· Improvements around processing status approvals from Office Project Web Access into Office Project Professional 2007

· Improvements to read-only content databases and index rebuild timer jobs in Windows SharePoint Services 3.0

In the coming weeks, individual product teams across Office will begin updating their blogs and highlighting some of the specific work that they’ve included in SP2.  You can find the links to some of the blogs at the end of the post.

In the next few days we will also invite a select set of Office enterprise customers to a private SP2 beta.  From these customers we hope to gather great feedback about the service pack, including areas that we’ll need to improve upon before we release it to the general public.  Based on the success of the SP2 beta program and customer needs, we will certainly evaluate whether to expand this in the future.