Archive for the 'Sharepoint' Category

Easy way to move documents – Sharepoint

We wanted to move a whole bunch of documents from one folder to another and was looking for a easy way to do it. I Googled it and got the answer:

From your computer go to “My Network Places”, click on “Add network connections” enter the URL for the site you want to open as a network place. This will open the site as a network folder; you will need to open two instances of the network place if the document libraries are located on the same site. Double click on the Document Folder which contains the documents you want to move in one window, and drag them to the Document folder in the other window.

Another optional way to open a WSS site as a folder is to use Internet Explorer to open the site as a web folder. Select File — Open from IE, Enter the URL of the site in the text box and select “Open As Web Folder”, click “OK” and the site will open as a web folder. Here you will have the same option of dragging or cutting and copying documents between document libraries.

Using this method you can also easily copy files from your computer into Document Libraries or even save email attachments to the WSS Network Place.

A note if you renamed your Shared Document Folder on the WSS site, it will always be named Shared Document Folder when you browse the site as a Web Folder or Network Place.

Hope this helps 🙂

Happy Programming,




SharePoint Farm Expansions

When I started my current position, I inherited a SharePoint mess. Before I arrived a tech was tasked with installing SharePoint development environment in preparation for a deployment. Due to hardware constraints or some such issue, the development installation and hardware soon became the production environment.

The first hurdle was actually licensing the software. The installation was done with a demo version. We purchased the requisite licenses under out volume license agreement, which of course means that activation failed. Remember, this is a production environment. A couple of weeks later we acquired the proper key and we were on our way.

Our production environment had less than 250 total users and less than 50 regular users for the last year and has humming along quietly. Then came the expansion project.

Now, the current installation was the default installation, which means that it was running off of SQL Server 2005 Express. The service accounts were all NETWORK SERVICE. (Again, and I cannot say this enough, this was done before I arrived!)

We had to expand (finally) our SharePoint Farm. OK, first things first, lets get those service accounts configured properly and put into production. Best practices aside, this is necessary as we will be standing up an additional SQL Server and the SharePoint service accounts are the credentials used to access the databases.

Set the service principle name for each SharePoint service account.

setspn -A HTTP/ServerFQDN DOMAIN\Account
setspn -A HTTP/ServerFQDN:80 DOMAIN\Account
setspn -A HTTP/ServerNetBIOSName DOMAIN\Account
setspn -A HTTP/ServerNetBIOSName :80 DOMAIN\Account

Now do it for each SQL service account.

setspn -A MSSqlSvc/ServerFQDN DOMAIN\Account
setspn -A MSSqlSvc/ServerFQDN:1433 DOMAIN\Account
setspn -A MSSqlSvc/ServerNetBIOSName DOMAIN\Account
setspn -A MSSqlSvc/ServerNetBIOSName :1433 DOMAIN\Account

Now that the accounts are created we need to swap out the credentials. Simple enough task, but it failed miserably. The error referenced that an update was currently in progress. I was a bit confused, as I was the only one in the system, but after a bit of research I located a fix.

Stop the “Windows SharePoint Services Timer” service. Navigate to C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\{GUID}. Backup the contents of this directory. After the backup completes delete everything except cache.ini. Open cache.ini and replace the contents with “1” and save the file. Start the “Windows SharePoint Services Timer” service.

Now to redirect the SQL Server. Open C:\windows\system32\cliconfg.exe. Added an alias on the application server redirecting the old instance to the new one. Stop the SQL services on the old server and copy the data and log files to the new server. Attach the databases on the new server.

SharePoint was still throwing a fit, so for good measure I rebooted both servers.