I need to move a Windows SharePoint Services 2 environment on a hosted Windows 2003 server to a Windows SharePoint 3 environment on a Windows 2008 server located at a different hosting company. I am a Network Engineer who's new to SharePoint. I'm not a developer in any way so scripting and editing code will be difficult to accomplish.
- Single server in the farm with a single Site Collection
- Single content database with a single config database
- Content database is about 14GB and config is about 2MB
- Storage is not a concern
- NO 3rd party tools are installed
- AD pass-through integration is NOT configured; users have to login using the domain account when accessing SharePoint
- URL to access the site will remain the same
- Source and Destination servers have different names and are in different domains
- WSS 3 is already installed on the destination server and a site collection has been created; no data has been added and no configuration has been done on it
I keep reading conflicting instructions on this process so I'm not really sure what the proper process is. Some say I only need the move the content database. Some say I need to upgrade to WSS 3 on the source server first. Some say I need to use the default web.config file on the destination server and customize it for the SharePoint environment that's brought over from the source server.
I'm lost in a sea of information comprised of bits and pieces of information. Does anyone have a complete step by step list from start to finish on how to accomplish what I need to do here? Any help would be greatly appreciated.
We had a requirement to extract data from a SharePoint 2010 Customer List into a CSV file and then place the CSV file into a directory on the network so that the file could be consumed by an AS400 system. I will share in Part 1 how to Extract the Da…
A recent project that involved parsing Tableau Desktop and Server log files to extract reusable user queries for use in other systems. I chose to use PowerShell to gather the data, and SharePoint to present it...
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?