Design Manager in SharePoint 2013

Design Manager is a feature in SharePoint 2013 that makes it easier to create a fully customized, pixel-perfect design while using the web-design tools that you’re already familiar with. Design Manager is a publishing feature that is available in publishing sites in both SharePoint Server 2013 and Office 365. You can also use Design Manager to brand the public-facing website in Office 365.

Below article is focused on Enable Design manager in SharePoint and Open Design Manager in SharePoint.

You can refer the MSDN article on Overview of Design Manager in SharePoint 2013 for further details.

Enable Design Manager in SharePoint

  • As Design Manager is a publishing feature that is available in publishing sites activate “SharePoint Server Publishing Infrastructure” under Site Collection Features

    Site Collection Features

    clip_image001

  • Then activate “SharePoint Server Publishing” feature under Manage Site Features

    Site Features

    clip_image002


    Open Design Manager in SharePoint

  • Option 01: Click on the gear icon on the top right corner of the page. Then click on “Design Manager”
  • clip_image003

  • Option 02: Open Site setting then click on “Design Manager” under look and Feel.

    clip_image004

  • Option 03: Browse http://ServerName/_layouts/15/DesignWelcomePage.aspx (Replace ServerName with your server name)
  • You are here. It’s the Design manager Landing Page

    clip_image005 

    Additional Resources

    What’s new with SharePoint 2013 site development: http://msdn.microsoft.com/en-us/library/jj163942(office.15).aspx

    Overview of the SharePoint 2013 page model: http://msdn.microsoft.com/en-us/library/jj191506(v=office.15).aspx

    How to: Convert an HTML file into a master page in SharePoint 2013: http://msdn.microsoft.com/en-us/library/jj822370(v=office.15).aspx

    How to: Create a page layout in SharePoint 2013: http://msdn.microsoft.com/en-us/library/jj822368(v=office.15).aspx

    What’s new in Branding ? http://edithzor.wordpress.com/2012/11/22/whats-new-in-branding/

    Intro to SharePoint 2013 Design Manager: http://sharepointbrian.com/2012/07/intro-to-sharepoint-2013-design-manager/

    Using Dreamweaver and Design Manager with SharePoint 2013: http://blogs.technet.com/b/speschka/archive/2012/07/27/using-dreamweaver-and-design-manager-with-sharepoint-2013.aspx

    Thank you. Smile
    Happy SharePointing Open-mouthed smile Open-mouthed smile Open-mouthed smile

    Advertisements

    Remove _layouts/15/start.aspx# from SharePoint URL

    If you notice having  the URL with _layouts/15/start.aspx because the new feature which is introduces in SharePoint 2013 Minimal Download Strategy is activated on your site. Minimal Download Strategy is a new framework which is been written to increase the performance of the SharePoint site.

    In order to fix this Deactive Feature “Minimal Download Strategy” under Manage Site Features.

    image

    Hope this helped Smile

    Thank you.

    Enjoy SharePointing Open-mouthed smile Open-mouthed smile Open-mouthed smile

    Remove Server from Service Bus Farm

    Hi Guys,

    This one of the issue that I experienced when Removing the Workflow manager from one farm and joining another farm. This requirement popped out as we crated the development farm by cloning the servers in Production Farm. I renamed the servers accordingly. As the Workflow Manager and Service Bus manager were already configured I had to remove the server from both farms (Workflow Manager and Service Bus)

    Good news is I was able to remove from Workflow Farm using Workflow Configuration manager. But even I tried removing from Service Bus Farm using UI its still there. So that I moved to PowerShell Open-mouthed smile to get this done. This is not the only issue that I had to face. Others will be addressed in Related post bottom of this post.

    • Open Service Bus PowerShell as Administrator

    clip_image001

    Warning Message shows as this is the new cloned SP server. What was in the SB Farm was the old server name. No problem this will remove current server from SB Farm. Use Get-SBFarm command to verify.

    image

    • To make sure I restarted the server and ran Workflow Configuration Manager. Now its possible both WF manager and SB to connect to an existing farm Smile

    clip_image003

    DNS Configuration for SharePoint Apps

    When you trying to add an app from store you might get below error. In order to fix this there are two things to be done.

    Task 01. Configure App Managements and Subscription Settings service in SharePoint

    Task 02. Configure DNS server to support app URLs

    Below blog post will be focused on Task 02 where you configure DNS record in DNS server.

    image

     

    • Open DNS using MMC then right click your domain and select add new CNAME

    clip_image001

    • Once you got prompted to enter record details add *.app as the alias name and as FQDN of target host as your domain name (in my case its silab.int)

    clip_image002

    • After successful addition of DNS you will find the record as below.

    clip_image003

    • Now from the DNS end you are ready to go. Verify the entry by ping blablablaa.app.silab.int

    image

    • Make sure you configure the App Management and Subscription Settings services (both) in SharePoint before adding the app URLs.

    image

    Thank you Smile

    Enjoy SharePointing Open-mouthed smile Open-mouthed smile Open-mouthed smile

    Register-SPWorkflowService The remote server returned an error: (404) Not Found

    This errors pops out if you have installed SharePoint Server 2013 on Windows Server 2012 R2. Its true that SharePoint 2013 now supports Windows Server 2012 R2 after the SP1 update.

    Even though you have SP1 (​15.0.4569.1000) you still will get the error when registering workflow service.

    image

    • If it shows “Workflow is Not Connected” you have to register the workflow service in SharePoint.
    • In order to register run “Register-SPWorkflowService -SPSite “http://SPSite” -WorkflowHostUri “http://ServerName:12291″ -AllowOAuthHttp” in elevated SharePoint Management shell

    clip_image002

    • If the workflow service in running on a Windows Server 2012 R2 server you will get an error (Register-SPWorkflowService : The remote server returned an error: (404) Not Found) as shown above.
    • In order to fix download the Web Platform Installer (http://www.microsoft.com/web/downloads/platform.aspx) then search for Workflow Manager CU2 and proceed with installation.

    clip_image003

    clip_image004

    clip_image005

    clip_image006

    clip_image007

    clip_image008

    Thanks you. Smile

    Enjoy SharePointing Open-mouthed smileOpen-mouthed smileOpen-mouthed smile

    Download Service Pack 1 for Microsoft SharePoint Server 2013 (Updated)

    Microsoft released an updated and fixed version of Service Pack 1 (SP1)( http://support.microsoft.com/kb/2880552 ) for SharePoint 2013 on April 22.
    A list of all the new associated Knowledge Base articles on the updated SP1s for SharePoint Foundation 2013, SharePoint Server 2013, Project Server 2013, and Office Web Apps Server 2013 are available from this TechNet blog post.(http://blogs.technet.com/b/wbaer/archive/2014/04/08/service-pack-for-sharepoint-server-2013-1-recalled.aspx)

    The post notes that these KB articles are different from those associated with the recalled (http://support.microsoft.com/kb/2817429) SP1. Customers who previously deployed SharePoint 2013 SP1 are advised to download the updated SP1 and install it over the existing SP1. Customers who didn’t deploy the original SP1 bits should just use the uploaded bits.

    There is no update to the slipstreamed ISO from MSDN, MPN and the Volume Licensing Service Center “as it was not affected by the issue,” according to Microsoft officials.

    Much awaited SharePoint Server 2013 Service Pack 1 has been released Smile

    Download Link: http://www.microsoft.com/en-us/download/confirmation.aspx?id=42008
      http://www.microsoft.com/en-us/download/details.aspx?id=42008
    KB Article http://support.microsoft.com/kb/2817429
    TechNet Blog Article http://blogs.technet.com/b/office_sustained_engineering/archive/2014/02/25/announcing-the-release-of-service-pack-1-for-office-2013-and-sharepoint-2013.aspx

    Access Denied on Sites after migrating SharePoint 2010 to SharePoint 2013

    After migrating the Farm from SharePoint 2010 site to SharePoint 2013 platform (Under Same domain) using the “Mount-SPContentDatabase” command, users were unable to login or access denied. When grant permission again you might note that now that particular user can access the site.

    And you might also have note a prefix (i:0#.w|) has been added to username.

    Solution: You have to convert the authentication method of the SharePoint Web Application from Classic to Claims

    This is where PowerShell becomes really nifty. You can use PowerShell to get the conversion done.

    $WebApp = Get-SPWebApplication “http://WebAppURL”

    Convert-SPWebApplication -Identity $WebApp -To Claims –RetainPermissions -Verbose

    $WebApp.MigrateUsers($true)

    For more details on Migrate from classic-mode to claims-based authentication in SharePoint 2013 you can refer this TechNet Article: http://technet.microsoft.com/en-us/library/gg251985.aspx

    Happy SharePointing !!! Open-mouthed smile