- Package.ddf: The ddf directives specify the path to the physical files to be copied to the .cab/.wsp file. .Set DestinationDir sets the target location within the .cab file (like a folder); all other paths are relative to the file system location of the .ddf file itself.
- Manifest.xml: Instructs SharePoint where to deploy the files held in the cabinet. File paths depend on the containing XML element: assembly paths are relative to the target /bin directory, TemplateFiles are relative to the 12-hive's TEMPLATE directory, DwpFiles are relative to the wwwroot\wss\VirtualDirectories\wpcatalog directory, and FeatureManifests and Resources are both relative to the 12-hive's TEMPLATE\FEATURES directory.
- Feature.xml: ElementFile locations are relative to the directory structure where the feature is installed (eg. as specified in Manfiest.xml)
- Elements.xml (via Feature.xml): Module URLs are targets within MOSS; File URLs are relative to the Module URL
Sunday, 28 September 2008
Saturday, 27 September 2008
Wednesday, 24 September 2008
Note this is not a comprehensive guide to VPC building: I make no assumptions about your virtualisation software (I used the free VMware Server product for x64 guest support in this case but I regularly use MS Virtual PC 2007). You may also want to consider differencing disks, memory allocation, physical disk performance, CPU allocations, and so on.
Install Windows Server 2008
- Don't add it to a domain but changing the machine name from the default is usually helpful.
- Add the ASP.NET service
- Add HTTP Redirection service (somewhat arbitrary)
- Add Windows Authentication service
- Add IIS Management Scripts and Tools
- Add the .NET Framework 3.0 Feature (excluding XPS Viewer)
- Download and install .NET 3.5 with SP1 (although you can skip this step if you like and let the SQL Server 2008 install handle it)
Install SQL Server 2008 (RTM)
- Yes to the prompt to install an updated Windows Installer version (and optionally the .NET Framework 3.5 SP1)
- Select the stand alone installation option
Choose to install the following at a minimum:
- Database Engine Service
- Management Tools - Basic
- Management Tools - Complete
Configure the SQL Server instance as follows
- Use the default instance name
- Use the Network Service account for all services. The database engine service should be set to start automatically.
- Select Windows authentication mode and add your local administrators group
Create Local Accounts
Create moss_farm and moss_web local Windows accounts and set a password. Don't add either account to any specific Windows group or SQL Server. MOSS will take care of creating logins for these accounts in SQL Server and assigning them to the appropriate roles.
Install MOSS 2007 SP1
MOSS SP1 is required to install on SQL Server 2008. SP1 can be slipstreamed into the RTM build although Microsoft supplies a ready-to-go MOSS 2007 with SP1 installer.
- Select the Advanced option
- This is a small farm installation, so select the Complete option (not the Stand-alone option unless you're not using SQL Server 2008)
- Leave all defaults as they are
- Install any post-SP1 updates before running the configuration wizard.
Note there's no requirement to install Windows SharePoint Services (WSS) 3.0 when installing MOSS 2007.
- Run the configuration wizard
- Select to create a new farm
- Point MOSS to localhost as the database instance
- Leave the configuration database name as SharePoint_Config or change it if you like
- Provide credentials for your moss_farm account
- Create the Central Administration site on any free port
- Extend the server's path variable to include C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN (for easy access to stsadm)
Enable Ping (always helpful)
- netsh firewall set icmpsetting 8
(to disable ping: netsh firewall set icmpsetting 8 disable)
- Disable visual enhancements
- Turn off the Windows page file
- Delete installer and windows update files (all the junk under %windir%)
- Defrag, compress, backup, etc
Create a Test Site
- Create a site using your moss_web account.
- Set up SSPs, etc, etc.
[Update: Since I wrote this post I've come Justin Devine's very extensive and well-illustrated post on configuring a small farm, with AD and SQL Server 2005, on Windows 2003. Well worth reading and there are some detailed walkthroughs on POP3 and SSP setup. Awesome work Justin! Also worth checking out this link]
MOSS Won't Check In or Publish: "Unable to complete this operation. Please contact your administrator."
Wednesday, 10 September 2008
Monday, 8 September 2008
The approach I use most often is to access the MOSS content database I'm after through a UNC path. Doing so exposes the content database structure through Windows Explorer and I can simply drag and drop files as I'm used to. If you've ever used SharePoint Designer to access a MOSS site, you'll see a structure through UNC that looks about the same (eg. _catalogs, SiteCollectionImages, etc).
UNC paths work with both port-based and host header-based sites but they can be a bit fiddly. Firstly, you need to ensure you're trying to access an edit site to which you have permissions--you probably won't get much from a read-only (anonymous) URL. Secondly, you may be prompted to authenticate. Finally, I always run into an error on first access if I try to browse the site root, so I usually start in \SiteCollectionImages.
Here's an example:
\\edit.mediawhole.com\SiteCollectionImages (host header)
\\dev-moss-mh:28000\SiteCollectionImages (becomes \\dev-moss-mh@28000\SiteCollectionImages) (
If you then drop the \SiteCollectionImages part, you'll see the full site hierarchy.
The Windows Explorer interface is obviously pretty basic so you won't be able to see version histories and approve content--you'll still need to take care of those aspects through the UI or some other way.
UNC paths allow spaces so if you're coming from a browser, make sure you URL decode the %20 values as spaces.
One last note, you may have a "Open with Windows Explorer" option on the Actions menu if you're viewing a document library via the All Site Content screen. Clicking this menu item will open a new Windows Explorer window pointing at an http:// URL to the same location (eg. http://dev-moss:30000/PublishingImages).
The FieldId elements defining the columns in question were missing two attributes: RichText="TRUE" and RichTextMode="FullHtml". New sites based on this template are now working correctly but MS has recommended we not change the site template for the sake of existing sites. We're therefore exporting content, recreating the site, and importing content back in--a hassle but should do the trick.
DisplayName="Publishing Page Content Bottom"
The MSDN documentation currently reflects this structure but I'm not positive it did previously... our mistake either way but at least it's fixed now and the doco is accurate.