using the new SharePoint 2010 Mount-SPContentDatabase PowerShell cmdlet in the SharePoint 2010 Management Shell, you will be attaching and upgrading your old 2007 content dbs following the straight forward TechNet documentation …

…but how do you migrate your Shared Service Provider user profiles and your MySites to SharePoint 2010 in the database attach scenario now that the SSP has been replaced by service applications?

The documentation is there, but is not explicit, on TechNet(!)  Here are some more detailed steps on how to migrate your old MOSS 2007 SSP User Profiles and MySites to your new SharePoint 2010 farm:

1. Backup your existing MySites content database(s) on your MOSS 2007 farm SQL Server
2. Back up existing SSP database on MOSS 2007 farm SQL Server
3. Move both database .BAK files to the new SQL Server
4. Restore the SSP database from .BAK as database named Profile_DB on your new SQL Server
5. Restore the MySites database from .BAK as database named WSS_Content_MySites on your new SQL Server
6. Create a new Web Application in your SharePoint 2010 Central Administration site to host your migrated MySites content (e.g. http://mysites)
7. Attach and upgrade the restored 2007 MySites database (i.e. WSS_Content_MySites) using the SharePoint 2010 Management Shell
1. SP-MountContentDatabase –Name WSS_Content_MySites –WebApplication http://mysites
8. Turn off the following services in your SharePoint 2010 Central Administration site 
   1. User Profile Service
   2. User Profile Synchronization Service
9. Delete existing User Profile Service Application(s) if they already exist [Central Administration -> Application Management -> Manage Service Applications]
   1. Make sure to check the box for delete associated data/content
10. Reset IIS
11. Create a new User Profile Service Application in Central Administration [Central Administration –> Manage Service Applications –> New]
    1. Name = User Profile Service Application
    2. Create New App Pool
       1. “User Profile Service Application”
       2. DOMAIN\farm_account
    1. Use the restored 2007 SSP database as the "Profile Database Name" (Profile_DB)
    2. Accept all other default database names
    3. Enter the newly created MySites web application url (e.g. http://mysites) as the default MySites location for the new User Profile Service Application
12. Go to "Administrators" in the ribbon menu for the User Profile Service Application and verify that DOMAIN\farm_account has "Full Control" rights
13. Start the User Profile Service in Central Administration [Central Administration –> Application Management –> Manage Services on Server]

14. Start the User Profile Synchronization service in Central Administration [Central Administration –> Application Management –> Manage Services on Server]

    1. Use DOMAIN\farm_account credentials
1. This will take a few minutes…
2. Follow progress in ULSViewer.exe if you are concerned it is failing & filter by Category="User Profile"
15. Reset IIS
16. In service.msc on your Central Administration host server (i.e. “App Server”), verify the two ForeFront Identity Management Windows services
    1. Services are started
    2. set to startup "Automatic"
    3. Running as DOMAIN\farm_account
17. Setup Profile Import [Central Administration -> Manage Service Applications -> User Profile Service Application - click on title]
18. Click on the link to "Add New Synchronization Connection” [see examples below]
    1. Name = DOMAIN
    2. Forest Name = sub.domain.local
    3. Specify a DC = dc.sub.domain.local
    4. Authentication = Windows Authentication
    5. Account Name = DOMAIN\ad_sync_account
    1. Make sure your chosen account has “Replicating Changes” rights in AD [for more details refer to this article]
    6. Click "Populate Containers"
    7. Click "Select All"
    8. "OK"
19. Run a Full Import
    1. Central Administration –> Manage Service Applications" -> "User Profile Service Application" -> "Start Profile Synchronization" -> select Full Import radio button option
1. This will take a few minutes..
20. Setup Profile Sync schedules [Central Administration –> Monitoring –> Timer Jobs]
21. Test the MySites site with a domain user account…success!

Oddly, the web application pools do not show up in IIS 7.0, but you can still inadvertently select them for new service applications..and they are just clutter/remnants.

In the SharePoint 2010 Management shell (PowerShell), you will still see them listed if you run the Get-SPServiceApplicationPool cmdlet:

> Get-SPServiceApplicationPool | select Id, Name

Here is how you can remove them:

> Remove-SPServiceApplicationPool -Identity "Your Orphaned SharePoint Service Application Pool Name"

(or below if you want to step through the process)

> $apppool = Get-SPServiceApplicationPool -Identity "Your Orphaned SharePoint Service Application Pool Name”

> $apppool
> Remove-SPServiceApplicationPool $apppool
> Get-SPServiceApplicationPool

Notice here that the -Identity is looking for the “Name” of the application pool and not the “Id” value! To be clear (as mud):

• Identity != Id
• Identity = Name

http://store.vmware.com/store/vmware/pd/productID.165308800/Currency.USD/?src=EM2_09Q4_VMW_OTHER_WS-CYBER-MONDAY-NORAM

In the weeks following SPC2009, I am beginning to feel like I have spent most of my waking hours watching videos on SP2010.  I saw a post about 2010 developer videos on Channel 9 on twitter a couple of weeks ago, but couldn’t muster up the energy to add them to my pile of recorded conference sessions   I finally got around to watching some of them this weekend a found them to be quite good as deeper dives into some of the new features/capabilities in SharePoint 2010.  They are all dev focused, too, so the content is not “dumbed down” for admins (j/k)!

This time around with SharePoint 2010, you will have the opportunity to access and submit feedback on code samples and snippets to be included in the SDK as they are released.  Additionally, you will be able to submit your own code samples for inclusion in the RTM SDK! Submitters will get full credit for their contributions…and we will all reap the benefit of having a more complete, consolidated collection of samples to get started building the next generation of killer apps on the SharePoint 2010 platform!

Here is the original post from Andrew May on the Microsoft SharePoint Developer Documentation Team Blog:

Got Code?

Contribute a Code Sample and Get Your Name in the SharePoint 2010 SDK

We’re looking for experienced SharePoint developers to share their skill and technical expertise with the SharePoint community. You’ll help your fellow SharePoint developers, and receive full attribution in the SharePoint SDK for doing so!

What we’re looking for are short code samples, what we on documentation teams tend to think of as ‘snippets’. A handful of lines that illustrate a discreet task or show how to exercise a specific piece of the object model, rather than a full-blown solution that addresses an entire scenario. Basically, the short code samples you’d find in a typical reference topic like this one.

In particular, we’re on the hunt for code samples that do one or more of the following:

· Show developers how to accomplish common SharePoint tasks programmatically

· Illustrate best coding practices in using the SharePoint object model

· Demonstrate how to avoid pitfalls when using lesser-known areas of the SharePoint object model

· Or otherwise show off the power and flexibility of developing SharePoint solutions

If you’re an experienced SharePoint developer, you probably have a toolbox of code snippets like these already; sections of code that you use over and over to perform the same routine tasks, or pieces of code that you’re particularly proud of having come up with as work-arounds for some of the, um, “eccentricities” of the SharePoint object model.

What we’re asking is that you share your hard-won knowledge by letting us publish your code samples in our SDK reference topics. In return, we want to make sure you get full credit, by giving you attribution right in the topic where the code sample appears. This includes a link to your company site. You can see an early example of this in this reference topic for the CreateTaskWithContentType class.

The SDK gets more real-world code samples, and you get increased visibility within the larger SharePoint developer community.

To submit a code sample, just shoot us an email including your code sample(s) at gotcode@microsoft.com. Include a short description of what each code sample does, or what task you would use the code sample to accomplish. Oh, and if there are any prerequisites that need to be specified for your code sample to run successfully, that’d be great to know as well. (For example, the code sample on the SPList class topic lists a few using directives, and the existence of an .aspx page containing a label control, as prerequisites.)

I’ve attached a zip with our code sample guidelines and some sample data to this post. These are the best practices for writing code samples that we give our external partners who write samples for us. For the best chance of getting your sample included in the SDK, take a look at the best practices for code snippets (the guidelines are really short, and won’t take more than a few minutes to review, I promise.)

Now, since the SharePoint 2010 Betas aren’t due out until November, for now we’re talking about code snippets written against the WSS 3.0 or MOSS 2007 object models. Go ahead and send them our way. And once you’ve worked with the SharePoint 2010 Betas a bit, you’ll undoubtedly create some useful or illuminating code samples in fairly short order. Send those our way as well. You could end up with a byline in the SharePoint SDK!

Any questions, feel free to ping gotcode@microsoft.com, or leave a comment.

In spite of my rudimentary javascript skills, I’ve been using jQuery for just about anything I can think of lately to spruce up the MOSS 2007/WSS user experience.  Yesterday I threw together a simple interactive image element using the jQueryUI library.  I wanted to display info dialog/modal windows when the user moved the mouse over a region on the image.  Using some old school HTML and simple javascript I was able to throw some neat content up very quickly.

Click here for the demo

Again no ground-breaking stuff here for you javascript gurus, but I was pleased with the results for the minimal amount of effort I put into it.  Here is what I did:

1) Created a barebones html page and with an <img> element and created an associated image map (aka “hot spot” for those of us willing to admit we ever used FrontPage…)

<html>
    <head>
        <title>jQueryUI Dialog Test</title>
    </head>
    <body>
        <img src="images/map.png" alt="" usemap="#atl_map" border="0">
        <map name="atl_map">

    <!– coords="left, top, right, bottom "–>
    <area     shape="rect" coords="150,40,180,70"
            href="#" alt=""
            onMouseOver="$(northwest).dialog(‘open’)"
            onMouseOut="$(northwest).dialog(‘close’)">
    <area     shape="rect" coords="440,200,470,234"
            href="#" alt=""
            onMouseOver="$(northeast).dialog(‘open’)"
            onMouseOut="$(northeast).dialog(‘close’)">
    <area     shape="rect" coords="50,295,80,325"
            href="#" alt=""
            onMouseOver="$(southwest).dialog(‘open’)"
            onMouseOut="$(southwest).dialog(‘close’)">
    <area     shape="rect" coords="225,390,255,420"
            href="#" alt=""
            onMouseOver="$(southeast).dialog(‘open’)"
            onMouseOut="$(southeast).dialog(‘close’)">
</map>

    </body>
</html>

2) Loaded the jQuery and jQueryUI libraries from Google’s CDN by adding some lines to the <head> of my new page and linked to the jQueryUI theme .css file (not well documented, I might add!)

<script src="http://www.google.com/jsapi"></script> <script> google.load("jquery", "1.3.2"); google.load("jqueryui", "1.7.2"); </script> <link rel="stylesheet" href="http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.2 /themes/smoothness/jquery-ui.css" type="text/css" />

3) Added <div> elements for my dialog windows to the <body> tag in the html

<!– dialog windows –>
<div id="northwest" class="modal" title="NW Atlanta">Woodstock, Smyrna, etc.</div>
<div id="northeast" class="modal" title="NE Atlanta">Duluth, Lawrenceville, etc.</div>
<div id="southwest" class="modal" title="SW Atlanta">Douglasville, PTC, etc.</div>
<div id="southwest" class="modal" title="SE Atlanta">Stockbridge, McDonough, etc.</div>

4) Added some javascript using jQuery and jQueryUI libraries to call dialog windows and added the onmouseover and onmouseout elements to my <area> tags for the image map.  Note the e.pageX and e.pageY coordinates in the script below.  These are the current mouse coordinates on the initial mouseover event.  I am using these values to place the dialog box content.  I referred to to the jQueryUI dialog demo documentation for the available options for dialogs.

<script type="text/javascript">
var coordinates = []
$().mousemove(function(e){

    coordinates[0] = e.pageX;
    coordinates[1] = e.pageY;
    return true;
});

$.ui.dialog.defaults.bgiframe = true;
$.ui.dialog.defaults.autoOpen = false;
$.ui.dialog.defaults.resizable = false;
$.ui.dialog.defaults.hide =’slide’;
$.ui.dialog.defaults.show = ‘slide’;
$.ui.dialog.defaults.position = coordinates;
$(function() {
  $(northwest).dialog();
  $(northeast).dialog();
  $(southwest).dialog();
  $(southeast).dialog();
});
</script>

…

<img src="images/map.png" alt="" usemap="#atl_map" border="0">
<map name="atl_map">
    <area     shape="rect" coords="0,0,304,234"
            href="#" alt=""
            onMouseOver="$(northwest).dialog(‘open’)"
            onMouseOut="$(northwest).dialog(‘close’)">
    <area     shape="rect" coords="305,0,610,234"
            href="#" alt=""
            onMouseOver="$(northeast).dialog(‘open’)"
            onMouseOut="$(northeast).dialog(‘close’)">
    <area     shape="rect" coords="0,235,304,469"
            href="#" alt=""
            onMouseOver="$(southwest).dialog(‘open’)"
            onMouseOut="$(southwest).dialog(‘close’)">
    <area     shape="rect" coords="305,235,610,469"
            href="#" alt=""
            onMouseOver="$(southeast).dialog(‘open’)"
            onMouseOut="$(southeast).dialog(‘close’)">
</map>

5) Finally, I added some styles to the header to hide the dialog close button and play around with the look of the dialog box

<style type="text/css">
.modal
{
    font-size:x-small;
}
.ui-dialog-titlebar-close
{
    visibility:hidden;
}
.ui-widget-header
{
    color:#0033CC;
    font-size:small;
}
</style>

Here is the full page (see below). To add something like this quick and dirty to a SharePoint page, you would just need to strip out the <html>, <head>, and <body> tags and cut and paste the HTML into the “Source” for a Content Editor web part (also below)

HTML:

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>jQueryUI Dialog Test</title>
<script src="http://www.google.com/jsapi"></script>
<script>
    google.load("jquery", "1.3.2");
    google.load("jqueryui", "1.7.2");
</script>
<link rel="stylesheet"
href="http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.2/themes/smoothness/jquery-ui.css"
type="text/css" >

<style type="text/css">
.modal
{
    font-size:x-small;
}
.ui-dialog-titlebar-close
{
    visibility:hidden;
}
.ui-widget-header
{
    color:#0033CC;
    font-size:small;
}
</style>

</head>
<body>
<!– jQueryUI dialog –>
<script type="text/javascript">
var coordinates = []
$().mousemove(function(e){

    coordinates[0] = e.pageX;
    coordinates[1] = e.pageY;
    return true;
});

$.ui.dialog.defaults.bgiframe = true;
$.ui.dialog.defaults.autoOpen = false;
$.ui.dialog.defaults.resizable = false;
//$.ui.dialog.defaults.hide =’slide’;
//$.ui.dialog.defaults.show = ‘slide’;
$.ui.dialog.defaults.position = coordinates;
$(function() {
  $(northwest).dialog();
  $(northeast).dialog();
  $(southwest).dialog();
  $(southeast).dialog();
});
</script>
<font face="calibri, arial, helvetica" color="navy"><strong>Move your mouse cursor over the pushpins for a dialog window</strong></font>
<br />
<!– dialog windows –>
<div id="northwest" class="modal" title="Northwest Atlanta">Woodstock, Smyrna,
                etc.</div>
<div id="northeast" class="modal" title="Northeast Atlanta">Duluth,
                Lawrenceville, etc.</div>
<div id="southwest" class="modal" title="Southwest Atlanta">Douglasville,
                Peachtree City, etc.</div>
<div id="southeast" class="modal" title="Southeast Atlanta">Stockbridge,
                McDonough, etc.</div>

<img src="images/map.png" alt="" usemap="#atl_map" border="0">
<map name="atl_map">
    <!– coords="left, top, right, bottom "–>
    <area     shape="rect" coords="150,40,180,70"
            href="#" alt=""
            onMouseOver="$(northwest).dialog(‘open’)"
            onMouseOut="$(northwest).dialog(‘close’)">
    <area     shape="rect" coords="440,200,470,234"
            href="#" alt=""
            onMouseOver="$(northeast).dialog(‘open’)"
            onMouseOut="$(northeast).dialog(‘close’)">
    <area     shape="rect" coords="50,295,80,325"
            href="#" alt=""
            onMouseOver="$(southwest).dialog(‘open’)"
            onMouseOut="$(southwest).dialog(‘close’)">
    <area     shape="rect" coords="225,390,255,420"
            href="#" alt=""
            onMouseOver="$(southeast).dialog(‘open’)"
            onMouseOut="$(southeast).dialog(‘close’)">
</map>

</body>
</html>

Content Editor Web Part snippet:

<script src="http://www.google.com/jsapi"></script>
<script>
    google.load("jquery", "1.3.2");
    google.load("jqueryui", "1.7.2");
</script>
<link rel="stylesheet"
href="http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.2/themes/smoothness/jquery-ui.css"
type="text/css" >

<style type="text/css">
.modal
{
    font-size:x-small;
}
.ui-dialog-titlebar-close
{
    visibility:hidden;
}
.ui-widget-header
{
    color:#0033CC;
    font-size:small;
}
</style>

<!– jQueryUI dialog –>
<script type="text/javascript">
var coordinates = []
$().mousemove(function(e){

    coordinates[0] = e.pageX;
    coordinates[1] = e.pageY;
    return true;
});

$.ui.dialog.defaults.bgiframe = true;
$.ui.dialog.defaults.autoOpen = false;
$.ui.dialog.defaults.resizable = false;
//$.ui.dialog.defaults.hide =’slide’;
//$.ui.dialog.defaults.show = ‘slide’;
$.ui.dialog.defaults.position = coordinates;
$(function() {
  $(northwest).dialog();
  $(northeast).dialog();
  $(southwest).dialog();
  $(southeast).dialog();
});
</script>
<font face="calibri, arial, helvetica" color="navy"><strong>Move your mouse cursor over the pushpins for a dialog window</strong></font>
<br />
<!– dialog windows –>
<div id="northwest" class="modal" title="Northwest Atlanta">Woodstock, Smyrna,
                etc.</div>
<div id="northeast" class="modal" title="Northeast Atlanta">Duluth,
                Lawrenceville, etc.</div>
<div id="southwest" class="modal" title="Southwest Atlanta">Douglasville,
                Peachtree City, etc.</div>
<div id="southeast" class="modal" title="Southeast Atlanta">Stockbridge,
                McDonough, etc.</div>

<img src="images/map.png" alt="" usemap="#atl_map" border="0">
<map name="atl_map">
    <!– coords="left, top, right, bottom "–>
    <area     shape="rect" coords="150,40,180,70"
            href="#" alt=""
            onMouseOver="$(northwest).dialog(‘open’)"
            onMouseOut="$(northwest).dialog(‘close’)">
    <area     shape="rect" coords="440,200,470,234"
            href="#" alt=""
            onMouseOver="$(northeast).dialog(‘open’)"
            onMouseOut="$(northeast).dialog(‘close’)">
    <area     shape="rect" coords="50,295,80,325"
            href="#" alt=""
            onMouseOver="$(southwest).dialog(‘open’)"
            onMouseOut="$(southwest).dialog(‘close’)">
    <area     shape="rect" coords="225,390,255,420"
            href="#" alt=""
            onMouseOver="$(southeast).dialog(‘open’)"
            onMouseOut="$(southeast).dialog(‘close’)">
</map>

From the Microsoft SharePoint Team Blog:

The server-packages of October 2009 Cumulative Update for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 are ready for download. October 2009 Cumulative Updates introduce more rules on Pre-Upgrade Checker, which can help customers to prepare the upgrade of their SharePoint farm to SharePoint 2010. Download Information Windows SharePoint Services 3.0 October 2009 cumulative update package http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=974989 Office SharePoint Server 2007 October 2009 cumulative update package http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=974988 Detail Description Description of the Windows SharePoint Services 3.0 October 2009 cumulative update package http://support.microsoft.com/kb/974989 (link may not be live yet) Description of the Office SharePoint Server 2007 October 2009 cumulative update package http://support.microsoft.com/kb/974988 (link may not be 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. Service Pack 2 for Windows SharePoint Services 3.0 and language packs Service Pack 2 for Office SharePoint Server 2007 and language packs October 2009 Cumulative Update package for Windows SharePoint Services 3.0 October 2009 Cumulative Update package for Office SharePoint Server 2007 Please note: Start from April 2009 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.6520.5000 after successfully applying these updates. You can also refer to April Cumulative Update post for deployment guides, slipstream how-to links and FAQs. Jie Li Technical Product Manager, SharePoint

View article…

Here is the list up the latest fixes included in the update:

WSS 3.0:

Stsadm.exe –o import –url <siteURL> -f c:\sub1.cab –includeusersecurity

MOSS 2007:

After usage reporting is enabled, site administrators and site collection administrators can view site usage summary pages that have the following information for their sites and site collections:

· Requests and queries in the last day and the last 30 days.

· Average number of requests per day over the last 30 days.

· A chart of requests per day over the last 30 days.

· A list of the top page requests over the last 30 days.

· A list of top users over the last 30 days.

· A chart of top referring hosts over the last 30 days.

· A chart of top referring pages over the last 30 days.

· A list of top destination pages over the last 30 days.

· Top queries for the last 30 days (if search usage reporting is enabled).

· Search results top destination pages (if search usage reporting is enabled).

SSP administrators for the search service can view a search usage reports page that tracks the following information.

· Number of queries per day over the previous 30 days.

· Number of queries per month over the previous 12 months.

· Top queries over the previous 30 days.

· Top site collections originating queries over the previous 30 days.

· Queries per search scope over the previous 30 days.

Site collection administrators for the SSP site can view a usage summary page that tracks the following information:

· Total amount of storage used by the site collection.

· Percent of storage space used by Web Discussions.

· Maximum storage space allowed.

· Number of users for all sites in the hierarchy.

· Total hits and recent bandwidth usage across all sites.

Site collection administrators can also view a site usage report that includes monthly and daily page hit totals filtered by the following criteria:

· Page

· User

· Operating system

· Browser

· Referrer URL

• SPC09 Video Highlights (including keynotes from Steve Ballmer and Jeff Teper)
• Microsoft SharePoint 2010 Landing page (running on 2010 beta!)
• 2010 Demo Videos
• SharePoint 2010 Upgrade Resource Center
• SharePoint 2010 General Questions and Answers
• TechNet Getting Started with SharePoint 2010 (Beta)

  Development

• SharePoint 2010: SharePoint Developer Platform Wall Poster
• MSDN SharePoint 2010 Developer Center
• Get Started Developing on SharePoint 2010 (http://mssharepointdeveloper.com)
• SharePoint Products and Technologies: 2010 (Technical Preview) Developer Documentation
• SharePoint 2010 SDK
• SharePoint 2010: Developer and IT Professional Learning Plan
• SharePoint 2010: Getting Started with Development on SharePoint 2010 Hands-on Labs in C# and Visual Basic

Starting from Service Pack 2, Windows SharePoint Services 3.0 and SharePoint Server 2007 support Windows Server 2008 R2 and Windows Server 2008 SP2. When you try to install SharePoint bits on Windows Server 2008 R2 directly, you may see the following dialogue:

This is because Windows SharePoint Services 3.0 and SharePoint Server 2007 bits without SP2 slipstreamed are not supported on Windows Server 2008 R2. The KB article 962935 is not live on the web site yet.

To install on Windows Server 2008 R2, for Windows SharePoint Services 3.0 you can download the slipstream builds here:

Windows SharePoint Services 3.0 with SP2 (x86)
http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en

Windows SharePoint Services 3.0 with SP2 (x64)
http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en

For SharePoint Server 2007, you can follow Create an installation source that includes software updates (Office SharePoint Server 2007) to create one. Or you can also read on, we will go through the complete steps to create a new slipstream build for SharePoint Server 2007.

Installation Steps

1. Copy the content of SharePoint Server 2007 setup files from the installation media to a folder on your hard drive.

2. Delete everything inside Updates folder.

3. Download Windows SharePoint Services 3.0 SP2 and Office SharePoint Server 2007 SP2 to a folder.

Make sure your Office SharePoint Server 2007 SP2 is downloaded after July 29^th.

4. Open a command prompt,  change directory to the folder you put the downloaded patches, and run the following two commands:

wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:[Path to installation bits]\Updates /quiet

officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract: [Path to installation bits]\Updates /quiet

Change [Path to installation bits] to where you put the bits. These will extract all the content from the two packages to Updates folder. SharePoint installation program will automatically read this folder to apply the patches.

5. Delete wsssetup.dll. This is a very important step so please don’t miss it.

6. If you also need the Cumulative Updates to be applied when install SharePoint, download the latest Windows SharePoint Services 3.0 and SharePoint Server 2007 Cumulative Update packages and extract them into Updates folder like step 4.

7. Your slipstream build of SharePoint Server 2007 is done!

8. Go and install it on your Windows Server 2008 R2 box, after the installation, the site version will show 12.0.0.6421 or possibly a higher version if you added additional cumulative update files.

Jie Li
Technical Product Manager, SharePoint

]]> http://sharepointmike.com/?feed=rss2&p=134 0