Here’s how you install it.

First download the installation helper and the correct version of WSS with SP1.

Windows SharePoint Services 3.0 with Service Pack 1

Windows SharePoint Services 3.0 x64 with Service Pack 1

Go here to download the Setup Helper file

Now run the setup helper (WssVista.msi).

You will see an UAC prompt select Continue to proceed with the installation.

Once the install has completed you will find the SetupLauncher.exe in the install location you selected. If you didn’t change the default option you will see it under the directory ..\Program Files\WssOnVista\Setup

Configuring IIS7

Before we go any further we need to make sure IIS7 is installed with all required options .

Go to Control Panel and click Programs.

Under Program and Features click Turn Windows features on or off.

Under Windows Features select Web Management Tools and World Wide Web Services. Enable at least the following options and choose OK.

Wait until Windows has configured all options.

Installing Windows SharePoint Services 3.0 SP1 on Vista.

After completing the above steps it’s time for the interesting part. Locate SetupLauncher.exe and start it. You will once again see an UAC prompt, select Continue.

After the SetupLauncher run, select the WSS installation file Sharepoint.exe, or the MOSS installation file, and click OK.  First, the package will be extracted.

After the files have been extracted the WSS setup program will be started.

The current version only supports the advanced installation option so select that one.

Select Web Front End when asked about Server Type. The database will be created later.

(If you are installing MOSS select the option which installs all services on the Web Front End)

Sit back and relax while SharePoint is being installed, you are running Vista remember

Hopefully you will see the following screen at the end of the installation. If you would get an error during the installation step try to run a Repair.

Leave the checkbox checked and click Close to run the Configuration Wizard.

At the second screen select the option to create a new server farm.

Specify your database server (e.g. MYLAPTOP\SQLEXPRESS) and account information.

Let the Configuration Wizard do it’s work.

And you should end up with this screen, congratulations!

The final result is WSS running on Vista, Enjoy!

No related posts.

You may backup a site collection using the following command:

   stsadm -o backup -url
   -filename

Similarly, you may restore a site collection using the following command:

   stsadm -o restore -url
   -filename  

stsadm -o export -url Now note that I mentioned “site collection” and not site. In order to backup a site, you may use the following command:

   -filename

Similarly, in order to import a site you may use the following command:

   stsadm -o export -url
   -filename

To import and export single sites need you to pay extra attention to site GUID identifiers, and the versions of items/documents in the site.

Now, this brings up some interesting permutations and combinations. Using the preceding commmands, you could:

• Move site collections to/from servers, or within the same website.
• Move sites up or down in the hierarchy of a site collection.
• Convert a site into a site collection.

Now, why would you ever want to convert a site into a site collection? Because, you cannot split a site collection between multiple content databases, and sometimes content databases get too huge to manage. As it turns out, Stsadm can also help you manage your content databases.

Managing Content Databases
Sometimes you might land in a project where you have a content database that is bursting its seams. Usually, when a content database grows to over 50GB, a SharePoint architect’s warning lights should turn yellow. If it crosses 200GB for high I/O sites, or 500GB for read-only sites, the warning lights should glow red. Note that you can tweak these soft limits beyond the numbers I mentioned, but—sooner or later—you’ll have to face the problem of taking an existing website with numerous sites or site collections, and splitting them up into manageable chunks containing separate content databases.

To do so, use the following command to force the creation of a new site collection in a new content database:

   stsadm -o createsiteinnewdb
   -url
   -owneremail
   -ownerlogin
   -databasename

After running the preceding command successfully, you may verify under Central Administration → Application Management → Content Databases that a new content database has indeed been added, and that the single site collection specified in the preceding code was created.

You can use the following sequence of commands to move a site collection from <oldUrl> to <newUrl>:

   stsadm -o backup -url
   -filename
   stsadm -o deletesite -url
   stsadm -o restore -url
   -filename  -overwrite

As you can see, the commands back up the site from the old URL, delete it, and then restore it at the new URL, which exists in a new content database. You accomplished all this with only a few lines usingStsadm, which supports a number of other commands that let you work with content databases.

No related posts.

No related posts.

SharePoint 2007 – c:\program files\common files\microsoft shared\web server extensions\12\bin\

SharePoint 2010 – c:\program files\common files\microsoft shared\web server extensions\14\bin\

Now type in the following for a backup:

stsadm.exe -o backup -url http://enterurlhere -filename c:\enterbackupnamehere.bak

Wait for the operation to complete. Hey look, you have a backup that holds all permissions, settings, content, etc.

Restoring the site is like this:

stsadm.exe -o restore -url http://enterurlhere -filename c:\enterbackupnamehere.bak -overwrite

Other commands can be used can be found here. (http://technet.microsoft.com/en-us/library/cc261956.aspx)

Related posts:

1. STSADM.exe is your friend

We will have this site open for other developers to write articles and share solutions. If you wish to become an author on this site please CONTACT US and let us know.

No related posts.