Just finished watching Don Jones excellent video on PowerShell training. Definitely recommend you check it out.
So, systems administrators are probably familiar with using the wizard driven tools in SQL Server Management Studio to set up a backup plan, right? But what if you have lots of slower/networked storage such as Amazon's S3 and want to make use of it to keep backups for historical purposes? I put together this PowerShell script and using a scheduled task, I run it each week, after the SQL backups run, to move backups to S3.
If you have differential backups, you can just change the time frame to use [$Now.AddHours] instead. One warning if you are using S3, the files will not appear on the destination drive immediately, as they have to be copied across separate geographical regions, as explained on their FAQ
I recently worked on a rather large implementation of FAST Search 2010. After configuring, setting up content crawls and basically making sure everything was working, we noticed that the first search of the day (by any user) would be painfully slow. It turns out this is an issue with the SharePoint root certificates and the fact that our farm did not have access to the Internet (common in highly secured implementations). The solution was thankfully posted to a KB here:
I ran across this today and thanks to my co-worker, Chris Battle, he pointed me to the solution via the link below.
We were trying to complete an SSL certificate request in IIS 7 and got this weird error: "Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
Turns out to be a permissions issue, head over here to get the solution.
In our case, we actually had to take ownership of the folders because using local administrators didn't propagate all the way down.
I was working on a SharePoint helpdesk ticket yesterday from a user that could not save a document using the 'Save As' in PowerPoint to create a new version of the document in an existing library. They kept getting an error like the screen shot below:
Turns out after searching high and low on Google that this is caused by missing meta data on the file being added to the library. We use a custom template based on the publishing features of SharePoint and you cannot select any of the other OOTB templates offered for sites, such as the Document Workspace site. When you use the Document Workspace site, you can make use of the Office Document Management task pane to enter all required meta data (in our case just a Title). The work around is of course, have them save the file locally and then upload it where they are prompted for a title, etc. before adding it to the library.
If you are looking at Small Business Server as a solution for your business but are afraid of the complexity of managing an on site IT infrastructure?
Consider the benefits: