ULS Viewer Download

This was taken down or disappeared for a while, so I figured I’d share that it was back up and available.¬† If you haven’t ever used it, you are in for a treat ūüôā

http://www.microsoft.com/en-us/download/details.aspx?id=44020

Advertisements

Adding File Type Icons To SharePoint 2013

This is almost entirely copied from, thank you Alan Richards.  There are some notes worth looking at that are specific to 2013

http://www.edutechnow.com/?p=192

“Adding File Type Icons To SharePoint 2010/2013

When you add documents to SharePoint 2010/2013 document libraries sometimes an icon doesn‚Äôt appear in the Type column. While this doesn‚Äôt stop the file from opening it does spoil the aesthetics of your site.”

Add The Icon
Find an icon for the application (17 x 17 Pixel gif will do it) and copy it to
..Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES

Edit XML File

You now need to edit the Docicon.xml file, this can be found in

..Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML

Navigate to the <ByExtension> section and add an entry for the file extension of the application similar to the one shown below

<Mapping Key=”abc” Value=”abc_icon.gif”>

Restart IIS by opening up a command prompt and using the command iisreset

NOTE

If you have a multiple server farm then you will need to repeat these steps on each of your servers”

SPECIFIC TO 2013:

You’d think that this would be needed in the 15 hive, but in my experience nothing changed until I made these changes in the 14 hive.¬† Also, watch out when copying the mapping key from anything other than the DOCICON.xml file.¬† The ” may be a format that the file doesn’t like and it will replace all of your icons with a .

Atlanta SharePoint User Group Presentation

I spoke at the Atlanta SharePoint User Group tonight about using Azure as a SharePoint Restore Rehearsal space.¬† As promised I’ve uploaded the slide deck I used…¬† Azure_Final

SharePoint Saturday Atlanta – June 21st – Speaker

I’ll be speaking at SharePoint Saturday on June 21st in Atlanta.¬† The topic will be, “Windows Azure as a SharePoint Farm Restore Rehearsal Space”

http://www.spsevents.org/_layouts/15/SPSEvents/Speakers/Speaker.aspx?List=faef661f-3659-46a4-8c74-734e35b94feb&ID=211&ContentTypeId=0x01009B7456B53860422CA50E457AD696463100BDF574C690DA6A418F29C5AD7D4E484D

Atlanta SharePoint User Group Meeting Tonight

I will be participating in an interactive panel discussion tonight at the Atlanta SharePoint User Group. The focus of the panel I’ll be on is SharePoint Development. For more details click on the link below…

http://us1.campaign-archive2.com/?u=60e6c2e40b365dfa290f60ae2&id=a908f58803

B2B Public Website built with SharePoint 2013

We actually started building this on preview, and moved to RTM as soon as it was available.

http://www.b2btech.com

 

 

Moving content between SharePoint environments

Yesterday I finished setting up a development environment for a SharePoint 2013 production environment that I maintain.¬† The last step was to move my production content to my development environment.¬† I had to dig around a bit to find the PowerShell etc.¬†Rather than go through that again next time,¬†I decided to¬†write a blog about it, so that I’d have all the steps in one place.

The first step is to back up the content database that you want to restore to development.  To do this open up SQL Server Management Studio, right-click on the database you want to back up, hover over tasks, and select backup.  You will be presented with the Back Up Database window.  Make sure that your backup type is set to full, give the backup a name or stick with the default, and note or change the destination.

You can skip these steps if you have scheduled backups running and are able to access the backup drive.  In that case just go grab a copy of the most recent full backup and copy it to your development SQL Server.

The next step is to restore the database to development.  To do this open up SQL Server Management Studio in your development environment, right-click on the Databases folder, and select Restore Database.  When presented with the Restore Database window, click on the Device Radio Button and click the ellipsis next to the text box.  This will bring up the Select backup devices window.  From there click Add, locate your backup file and click OK, click OK again to be returned to the Restore Database Window, and finally from there click OK.  Now your database has been restored, and you are ready to add it to SharePoint.

If you don’t already have one with content in it that you don’t care about in it, create a new Web Application…

https://sharepointv15.wordpress.com/2012/07/24/create-a-web-application-in-sharepoint-2013/

Don’t worry about creating a site collection.

Now go to Central Admin and click on Manage content databases under Application Management.

rsd1

Make sure that the correct Web Application is selected.  If it is not click on the drop down arrow next to the Web Application name, click change web application and select the correct Web Application in the window that you are presented with.

rsd2

Next click on the Content Database name

On the Manage Content Database Settings screen scroll down, click on the Remove Content Database check box, click OK on the warning pop up and click OK at the bottom of the screen.

rsd3

Now you’ll need to open up the SharePoint 2013 Management Shell as an administrator.¬† To do this click on your start menu, click all programs, click on the Sharepoint 2013 folder, right-click the SharePoint 2013 Management Shell and select Run as Administrator.

From here you will run the Mount-SPContentDatabase cmdlet

Mount-SPContentDatabase ‚ÄúMyDatabase‚ÄĚ -DatabaseServer “MyServer” -WebApplication http://sitename

Click below¬†for details¬†on this cmdlt…

http://technet.microsoft.com/en-us/library/ff607581.aspx

At this point you should be able to navigate to the web application URL and see the Site Collection that lives in the database you just mounted.

Note:  This will work in SharePoint 2010 or SharePoint 2013.  However, the database must be the same version of SharePoint that the farm you are trying to mount to is.  If it is a lower version it will automatically try to upgrade it, so keep that in mind.