1. Go to Start > All Programs > Microsoft SQL Server 2005 (or 2008) > Configuration Tools > SQL Server Configuration Manager
2. Now navigate through the tree on the left side to “SQL Server Network Configuration” and select “Protocols for MSSQLServer”
3. From the right pane ensure that “Named Pipes” is enabled
   
4. Once it has been enabled then you can restart the service “SQL Server (MSSQLSERVER)”
5. Now check the Sharepoint website to confirm that it is working again.

These steps resolved the issue on our server so I hope this will help others resolve their issue.

- Rob


Add-PsSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue
try
{
  $today = (Get-Date -Format dd-MM-yyyy)
# Created the a new directory with todays date and store in a variable
  [IO.Directory]::CreateDirectory("F:\sp_backup\"+$today)
  $backuppath = "F:\sp_backup\"+$today

# This will iterate through all of your sharepoint sites and create a backup with the site URL as the name 
  Get-SPWebApplication | Get-SPSite | ForEach-Object{$filepath = $backuppath + "\" + $_.Url.Replace("http://","").Replace("/","-").Replace(":","-") + ".bak" ; Backup-SPSite -Identity $_.Url -Path $filepath}

# Edit this address to suit your own needs 
  $emailFrom = "Sharepoint@server.local"

# This is the address that the notification email should be sent to 
  $emailTo = "administrator@server.local"

# Subject for the notification email. The + "$today" part will add the date in the subject.
  $subject = "The SharePoint sites Backup was Successful for "+"$today"

# Body or the notification email. The + "$today" part will add the date in the subject.
  $body = "The SharePoint sites Backup was Successful for "+"$today"

  # IP address of your SMTP server. Make sure relay Is enabled for the SharePoint server on your SMTP server
  $smtpServer = "1.1.1.1"
  $smtp = new-object Net.Mail.SmtpClient($smtpServer)
  $smtp.Send($emailFrom, $emailTo, $subject, $body)
}
Catch
{
  $ErrorMessage = $_.Exception.Message
  # Configure the below parameters as per the above.
  $emailFrom = "Sharepoint@server.local"
  $emailTo = "administrator@server.local"
  $subject = "The SharePoint sites Backup Job failed on "+"$today"
  $body = "The SharePoint sites Backup Job failed on "+"$today and the reason for failure was $ErrorMessage."
  $smtpServer = "1.1.1.1"
  $smtp = new-object Net.Mail.SmtpClient($smtpServer)
  $smtp.Send($emailFrom, $emailTo, $subject, $body)
}

This script can simply be copied into notepad and saved onto your server as a ".ps1" file. This can then be run straight from the servers "run" command by entering "powershell {scriptname}.ps1" and it will create a backup file, this in turn can be used to created a scheduled task on your server to be run each day/week etc.

Credit where due though, this script is a combination of the following 2 sources:

http://thecommunicator.co.cc/2010/12/07/automated-powershell-script-to-backup-sharepoint-farm-or-site-collection-with-email-notification/

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?List=56f96349-3bb6-4087-94f4-7f95ff4ca81f&ID=191&Web=48e6fdd1-17db-4543-b2f9-6fc7185484fc

Hopefully this will help others out there

- Rob

Having configured it for remote use it was great but it was still a little clunky as I needed to be online to do anything (I could work through Outlook but it is not too pretty IMHO)..then I discovered Microsoft Sharepoint Workspace, formally Groove. The only real drawback about it is that you can only get it with Microsoft Office Professional Plus 2010 which is only available through Microsoft Volume Licensing, a real over sight by Microsoft in my opinion. That said, if you do have it then use it!!

As standard, Sharepoint Foundation 2010 does not work when you click the link in the library that says "Sync to Sharepoint Workspace" you get the message:

SharePoint Workspace was unable to interpret the SharePoint location. Please check and ensure the location contains no typing errors.

This is due to a change which needs to be made on the Sharepoint server to make it work, follow the link below to resolve the issue:

http://weblogs.asp.net/jeffwids/archive/2010/05/06/configuring-sharepoint-foundation-2010-for-sharepoint-workspace-2010.aspx

If you have Sharepoint setup on a none standard port then ensure that you have it specified at the end of the URL.

- Rob

So what's the difference? The core difference between the two products is that Microsoft Forefront Security is a centrally managed product which had updates and definitions distributed from a central source which is traditionally the office server. In contrast Microsoft Security Essentials is ideally suited to Small businesses that may not have a server in place, for example when they are using cloud services, or that do not require central management. Either way it is a compelling and interesting move by Microsoft in to a market space which they currently do not have a significant market share in.

Either way this is great news for Small Businesses everywhere!

- Rob

The February 24, 2009 cumulative update for Outlook 2007 includes changes related to the general reading and writing characteristics of the .pst/.ost file so that less is demanded from your hard drive to perform the same general operations in Outlook. For instance, the file flushing process was optimized so that it interacts more efficiently with operating system and disk-write caches. There is also a change in the way new data is written to the .pst/.ost so that the data is saved much closer together on the physical disk. As a result, there is less physical work required from the drive, thereby speeding up the time it takes to write the same amount of data to the drive. However, a side-effect of this data writing algorithm is that .pst/.ost files will be about 20% larger than before the February 24, 2009 cumulative update.

Most people will not have noticed the difference as many corporate clients use Exchange & Outlook so never see the OST files but those with PST files may have. For what it’s worth with the cost of storage being so low I would put up with the storage increase for the performance gain.

This may seem like a bold move but it is not the first time they have done this. In 2005 they paid $250,000 to two individuals who helped identify the creator of the Sasser worm.  Rewards were also offered of $250,000 for the creators of the other three major computer worms Blaster, MyDoom and Sobig however the authors of these were never caught.

In reality this amount of money is a small drop in the ocean for a company like Microsoft but in doing so they are trying to send out a strong message to the authors of such worms.  They are simply saying that they will not sit idly by while the creators wreak havoc on their clients systems.  In reality the fact of the matter is that regardless of what Microsoft or Microsoft Trustworth Computing Group offer it seems that it will offer very little in the way of a deterrent for such authors as it is a challenge that they enjoy rising to.  What it does do is help their clients to feel that they are doing all they can to try an prevent such hassles returning in the future.

The worm itself infects a computer that is not fully up to date with the latest updates from the Microsoft Update website. If you are in any doubt then the best action is to visit the Microsoft Update website and apply all the latest critical updates.  Once this is complete continue to revisit the site until you are told there are no further critical updates. You should also ensure that your Anti-Virus software is fully up-to-date, if you don’t already have one then visit either AVG or aVast who both provide free versions for home use.

Once of the reasons has been due to the dismal failure of Windows Vista, that is not to say that the product is bad because to be quite honest it isn’t, but initially it received a lot of bad press due delayed deliveries as well as, once launched, poor compatibility with hardware as well as some software.  Now what we have to understand with this is when any new product is released there will always be teething problems, this is not unique to technology this applies  to cars, motorbikes just about anything really.  This is because not matter how much you test something there is always going to be someone that will do something in a way that was never imagined or it will become visible through simple length of use.  Windows Vista itself has been a very solid stable product for a great deal of time now, I have been using it myself for over a year now and it really just works, that’s all there is to say on the matter.  But it never won the hearts of the IT community which resulted in poor uptake, this then left a poor legacy for Microsoft which is going to be hard to shake.  One of the biggest challenges it had to overcome is that Windows XP is just so good, it had been a solid operating system that is highly compatible which has left it with an almost “cult-like” following.

So what does this mean for Windows 7?  Well simply put it has a very hard path to find in life, it must first overcome that love and passion that is held by the Windows XP followers.  Then, if it overcomes XP, it must then work its way through the minefield of the Windows Vista naysayers which in itself is going to be a challenge of its own and I believe that in itself will be more difficult.

So what of Windows 7 itself, well I have not yet had chance to install it myself however I picked up a twitter from Scott Ullrich (the developer behind pfSense) overnight which said

Upgraded windows Vista -> Windows 7 and holy <beepers>, it’s fantastic! No, seriously… Not kidding!!

 

Still in the meantime take a look at these videos courtesy of BBC news and see for yourself:  BBC News

Client: Hi Rob, I’m probably going to regret asking this but I have been asked and I don’t quite know how to fix it.

Me: Go on

Client: I have been asked to look at the time on the server as it’s wrong so it’s making all the PC’s the wrong time.

Me: Oh right, I thought we had the network timesyncing externally

Client: I’m on the Grenwich Mean Time website and our server is 20 seconds fast and I’ve been told to see if it can be sorted.

Me: (thud as I hit the floor, wait a further 10 second to stop laughing) Right ok, you are joking right?

Client: NO

Me: Oh right, you sure you’re not joking?

Client: NO

Me: Ok let’s see if we can sort it out

So the conversation went on, now the above wasn’t being rude as it may seem as we often make a point taking pot shots for a laugh but it did raise an interesting point which I tend to perform as second nature on servers that we manage but not everyone does.  The point is that now with the advent of PC integrated clocking in systems they often take their time source from the network so if the time is wrong (usually tends to be a problem when its out by minutes rather than seconds but hey not for me to judge) then staff could be clocking out at the wrong times so these systems become flawed.  So if anyone wants to get their Windows Domain controller synced with a reliable time source then read on.

Important The following information contains details of changes to be made to the Windows Registry.  If you are unsure of what you are doing then please do not attempt it as serious damage can occur if you modify it incorrectly.  For extra protection read the following KB article from Microsoft on how to backup and restore the registry KB322756

To configure the server with an external time source then do the following:

1. Click on Start, click Run, type Regedit then click OK
2. Change the type to NTP Server
1. Locate the registry key
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
2. In the right pane double click on Type
3. Change the value to read NTP, the click OK
3. Set AnnounceFlags to 5
1. Locate the registry key
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
2. In the right pane double click on AnnounceFlags
3. Change the value to read 5, then click OK
4. Enable NTPServer
1. Locate the registry key
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
2. In the right pane double click NTPServer
3. Change the value to read 0.pool.ntp.org,0×1, then click OK
   Other time servers can be specified however I have found that this one is the most accurate
5. Quit the registry editor
6. Open the command prompt an enter:
   net stop w32time && net start w32time

There are a number of other values that can be changed with regard to acceptable time differences and time shift however the standard setting is sufficient for most small business however details can be found in article KB816042.  With regard to my friend, this is the process that I ran on his server now he’s a happy man as his server is now accurate to within half a second of GMT……go figure!

By adding in the ADM template at the bottom of this article you will be able to restrict access to USB storage devices as well as CD/DVD Drives.  Once you have the downloaded file then on your server go to the %SYSTEMROOT% folder this is typically "C:\WINDOWS" and copy the ADM file into the "INF" folder.  Once you have done this go into the "Group Policy Management" tool.  Once there if you create a new group policy or edit an existing policy then navigate to "Administrative Templates" under "Computer Management".

Right click on "Administrative Templates" and select "Add/Remove Templates"

Click on "Add" and from the list of files select "ext_storage.adm" and click on "OK", now click on "Close"

Now from the "View" menu select "Filtering" and unselect the "Only show policy settings that can be fully managed" option and click "OK"

Now from the main group policy window under "Administrative Templates" you will see "Custom Policy Settings" and below this you will see "Restrict Drives".  Once selected on the right hand pane you will see the options to disable USB, CD Rom, Floppy and High Capacity Floppy.

Once these are enabled the users which have this policy applied to will no longer be able to use these facilities.  This gives small businesses a means of securing their data without spending the earth.

Attachments: ext_storage.adm