Exporting and Importing sites between WSS 3 and SharePoint Foundation 2010.

I was recently tasked with moving a list from a WSS3 server to a SharePoint Foundation 2010 server. After Googling around, I tried exporting the list as a template in WSS3, then importing the template into Foundation. However, I quickly learned that SharePoint Foundation cannot import WSS3 list templates. There didn’t seem to be a way to ‘update’ the WSS3 list template to Foundation; dead-end. To get around this limitation, I backed up the entire WSS3 site and performed a ‘database attach upgrade’ to a new temporary Sharepoint Foundation server, then transferred the list as a template.

Basic Process:

  1. Backup the SP_WSS3 database
  2. Restore it to a temporary SP_2010 server (SP_2010Temp)
  3. Copy the list (as a template) from the temporary server to your production SP_Foundation server

Things to note:

  • The Two SharePoint servers we are using are Windows Sharepoint Services 3.0  and SharePoint Foundation 2010
  • For reference, here are my version numbers: SP_WSS3′s version is: 12.0.0.6421, SP SP_2010′s version is: 14.0.4762.1000, SP2010 RTM
  • SP_2010Temp’s version will be the same as SP_2010

Setting up your new SP_2010Temp site:

Note: I referenced this blog for lots of this information Installing a Standalone Sharepoint Foundation 2010 Server. However, we’re not going to complete every step because we shouldn’t need SSL for this temporary SharePoint Foundation server.

The basic outline:

  1. Install SQL Server 2008 R2 Express
  2. Download SharePoint Foundation. You do not need Search server Express
  3. Follow Prepare your system
  4. Install SharePoint Prerequisites
  5. Install SharePoint Foundation 2010
  6. Follow the Intial Configuration Wizard
  7. Follow Create Site Collection
  8. Ignore everything else!

To upgrade the actual WSS 3 content to SP2010, we will use the “database attach upgrade” method. See this blog post for more info: WSS3.0 to SharePoint Foundation 2010 upgrade


Backing up the WSS 3 Content Database:

  1. On your  SP_WSS3 server, Open SQL Server Management Studio and connect.
  2. Expand Databases, than right click WSS_Content -> tasks -> Back Up…
  3. When the back up window opens, set your destination to: “disk” then click “Add”.
  4. In the next menu, Choose a location , and give the backup a name.
  5. Now on your SP_2010Temp server, open SQL Server Management Studio
  6. Expand the databases, right click on the database you want to restore to. This database will be similar to the filename that you just backed up (e.g. WSS_Content_1)
  7. Right click on the database -> tasks -> Restore -> database
  8. In this Menu, check that the Destination for restore is the database you just backed up from SP_WSS3, Under “Source for restore” choose “From device”, then click the “…” button, This will open another menu prompting for you to choose your backup file, find the backup file of the WSS_Content and click ok.
  9. After you choose the backup file, you will notice that the selected backup file is now under your “Source for restore”, make sure its checked and proceed to the next step
  10. Open options and check “Overwrite”            
  11. Click ok and you should get a message saying “The Restore of <database> completed successfully.”
  12. Login to SP_2010New’s central administration website.
  13. Go to “Manage Content Databases”
  14. If there is a database there, delete it, ignore the pop up
  15. The last step: We are going to add our new database to the SP_2010New’s Farm using this command, we should be still Remote desktop to SP_2010New cd “<programfiles>\common files\microsoft shared\web service extensions\14\bin” stsadm -o addcontentdb -url <URL> -databasename <database name>
  16. This will upgrade your database to 2010 format at the same time
  17. Navigate to the Central admin site for SP_2010New, the new database should be under “Manage Content Databases”

18. Your Done! The two websites should look similar becuase we havent done a visual upgrade, you can see simularities in the menus and how the is website setup.

Posted in Sharepoint Services 2010, Sharepoint Services 3 | Leave a comment

STSADM help from Sharepoint 2010 Foundation

C:\Program   Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>STSADM   -help
Usage:
stsadm.exe -o   <operation> [<parameters>]
stsadm.exe -help   [<operation>]
Operations:
activatefeature
addalternatedomain
addcontentdb
addpath
addpermissionpolicy
addsolution
addtemplate
adduser
addwppack
addzoneurl
authentication
backup
backuphistory
binddrservice
blockedfilelist
canceldeployment
changepermissionpolicy
copyappbincontent
createadminvs
creategroup
createsite
createsiteinnewdb
createweb
databaserepair
deactivatefeature
deleteadminvs
deletealternatedomain
deleteconfigdb
deletecontentdb
deletegroup
deletepath
deletepermissionpolicy
deletesite
deletesolution
deletetemplate
deleteuser
deleteweb
deletewppack
deletezoneurl
deploysolution
deploywppack
disablessc
displaysolution
email
enablessc
enumallwebs
enumalternatedomains
enumcontentdbs
enumdeployments
enumgroups
enumroles
enumservices
enumsites
enumsolutions
enumsubwebs
enumtemplates
enumusers
enumwppacks
enumzoneurls
execadmsvcjobs
export
extendvs
extendvsinwebfarm
forcedeletelist
getadminport
getproperty
getsitelock
getsiteuseraccountdirectorypath
geturlzone
import
installfeature
listlogginglevels
localupgradestatus
managepermissionpolicylevel
mergecontentdbs
migrategroup
migrateuser
monitordb
patchpostaction
provisionservice
refreshdms
refreshsitedms
refreshsitemap
registerwsswriter
removedrservice
removesolutiondeploymentlock
renameserver
renamesite
renameweb
restore
retractsolution
retractwppack
scanforfeatures
setadminport
setapppassword
setconfigdb
setlogginglevel
setproperty
setsitelock
setsiteuseraccountdirectorypath
setworkflowconfig
siteowner
spsearch
spsearchdiacriticsensitive
syncsolution
unextendvs
uninstallfeature
unregisterwsswriter
updateaccountpassword
updatealerttemplates
updatefarmcredentials
upgrade
upgradesolution
upgradetargetwebapplication
userrole
Examples:
stsadm.exe -o addpath -url   http://server/sites -type wildcardinclusion
stsadm.exe -o adduser
-url http://server/site
-userlogin DOMAIN\name
-useremail someone@example.com
-role reader
-username “Your   Name”
-siteadmin
stsadm.exe -o backup -url   http://server/site -filename backup.dat -overwrite
stsadm.exe -o backup   -directory c:\backup -backupmethod full
stsadm.exe -o createsite -url   http://server/site
-ownerlogin DOMAIN\name
-owneremail   someone@example.com
stsadm.exe -o createweb -url   http://server/site/web
stsadm.exe -o deletesite -url   http://server/site
stsadm.exe -o deleteweb -url   http://server/site/web
stsadm.exe -o enumsites -url   http://server
stsadm.exe -o enumsubwebs -url   http://server/site/web
stsadm.exe -o enumusers -url   http://server/site/web
stsadm.exe -o extendvs -url   http://server:80
-ownerlogin DOMAIN\name
-owneremail   someone@example.com
stsadm.exe -o renameweb -url   http://server/site/web1 -newname web2
stsadm.exe -o restore -url   http://server/site -filename backup.dat
stsadm.exe -o restore   -directory c:\backup -restoremethod overwrite
stsadm.exe -o setconfigdb   -databaseserver server
stsadm.exe -o unextendvs -url   http://server
For information about other   operations and parameters,
use “stsadm.exe   -help” or “stsadm.exe -help <operation>”
C:\Program Files\Common   Files\Microsoft Shared\Web Server Extensions\14\BIN>
Posted in Sharepoint Services 2010 | Leave a comment

Apache restrict access based on IP address to selected directories

Apache web server allows server access based upon various conditions. For example you just want to restrict access to url http://www.mysite.net/ (mapped to /var/www/sub/payroll directory) from 192.168.1.0/24 network (within intranet).

Apache provides access control based on client hostname, IP address, or other characteristics of the client request using mod_access module.

Open your httpd.conf file:

nano /etc/httpd/conf/httpd.conf

Locate directory section (for example/var/www/sub/payroll) and set it as follows:

<Directory /var/www/sub/payroll/>
Order allow,deny
Allow from 192.168.1.0/24
Allow from 127
</Directory>

Where,

  1. Order allow,deny: The Order directive controls the default access state and the order in which Allow and Deny directives are evaluated. The (allow,deny) Allow directives are evaluated before the Deny directives. Access is denied by default. Any client which does not match an Allow directive or does match a Deny directive will be denied access to the server.
  2. Allow from 192.168.1.0/24: The Allow directive affects which hosts can access an area of the server (i.e. /var/www/sub/payroll/). Access is only allowed from network 192.168.1.0/24 and localhost (127.0.0.1).
  3. Save file and restart apache web server: # /etc/init.d/httpd restart
Posted in Linux, Linux (General) | Leave a comment

Running {lspci} in Ubuntu

You can run lspci to display information about PCI buses in the system and devices connected to them.

type {sudo lscpi} and hit enter.

Posted in Linux, Linux (General) | Leave a comment

Ubuntu network documentation

Ubuntu network documentation for network-configuration

http://manpages.ubuntu.com/manpages/hardy/man8/ifup.8.html

Posted in Linux, Linux (General) | Leave a comment

Running {ifconfig -a}

This is exampkle output of running {ifconfig -a}

you can also run {ifconfig -a | grep eth} for a summary of the ethernet interfaces.

Posted in Linux, Linux (General) | Leave a comment

Running {lshw -C network}

Running lshw -C network and ifconfig -a allows you to see

Below is an example output of running {lshw -C network|more}

Posted in Linux, Linux (General) | Leave a comment

Correcting Ubuntu interface eth0_rename

From the Command line - the: To solve this specific problem you need to follow these specific steps. Do a ifconfig on the interface -

ifconfig eth0_rename

This should have some information like hw addr: aa:bb:cc:dd:ee:ff Use this hardware address to search the entry within this file -

nano /etc/udev/rules.d/70-persistent-net.rules

and change the name of that interface to whatever you want – E.g. eth0. Please note that the name eth0_rename might have come out due to wrong renaming of interfaces, and hence you might see multiple entries with the same interface name in the file.

Save and quit the file. Reboot the machine and your woes will be all gone.

Posted in Linux, Linux (General) | Leave a comment

Show interfaces in Ubuntu

To show the interfacesa in Ubuntu run the command below.

ifconfig -a | grep eth

Your output will be similar to the imsage shown below.

Posted in Uncategorized | Leave a comment

Configure interface for promiscuous mode on Ubuntu

When configuring an IDS server, I like to modify /etc/network/interfaces and have the following lines for the Interface I listen.

In this example the interface is {eth1}.

auto eth1
iface eth1 inet manual
ifconfig eth1 up -promisc

Using -promisc enables promiscuous mode  of  the  interface. In this case {eth1} All packets on the network will be received by the interface.

Posted in Linux, Linux (General) | Leave a comment