• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Amplexor Sharepoint 2013 seminar
 

Amplexor Sharepoint 2013 seminar

on

  • 754 views

 

Statistics

Views

Total Views
754
Views on SlideShare
751
Embed Views
3

Actions

Likes
0
Downloads
44
Comments
0

1 Embed 3

https://twitter.com 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Datasheet View is now Quick Edit – and it now works with Managed Metadata. Mass editing of metadata is back!
  • External Sharing
  • Like / UnlikeComment: on item level “tags & notes”. Follow sites anddocumentsShare sites & documents. Also w/ external usersMicroblogging: status updates, use of hashtags
  • Yammer: enterprise social network tool for company collaborationReplacement of the newsfeed
  • Html5/css3 : richer toolset for branding our sitesComposed looks: themes 2010-> evolved. Contain master pages, colors, fonts, background image, preview - not created in powerpoint but by xml filesDesign manager: New tool for designersDisplay templates (HTML + JavaScript replace XSLT itemstyles)
  • Country code Top Level domains : via X-site publishing
  • Push notificationsSharePoint Server 2013 supports applications on mobile devices (such as smartphones, tablets, and so on) that should receive notifications from a SharePoint site. Notifications can include events that occur in the site, such as when a user adds an item to a list or updates an item. For mobile devices to receive these notifications, device applications must register with a SharePoint site. Once the device is registered, you can write event handler code to interact with Microsoft Push Notification Service or notification services of other mobile device platforms. Notifications are sent from the server where the application is hosted to the registered mobile device applicationLocationSharePoint Server 2013 introduces a new geolocation field type that can be used in a list. For example, you can now make lists “location-aware” and display latitude and longitude coordinates through Bing Maps. An entry is typically seen as a pushpin on the map view. Although there are several ways to use this geolocation field, one key scenario is for mobile application development. Users can track or log location-specific data while they work remotely from the corporate office. Alternatively, the application can help them locate points of interest when it performs offsite functions.Office Web AppsIn SharePoint Server 2010, Office Web Apps Server provides browser-based companions for Word, Excel, and PowerPoint. When Office Web Apps Server is installed on SharePoint Server 2010, Office Mobile Web Apps is also installed on the server. Office Mobile Web Apps enables users to open documents in the mobile web application by using a mobile browser. With SharePoint Server 2013, Office Web Apps Server is no longer a companion product installed on a computer that is running SharePoint Server. Instead, Office Web Apps Server is a new stand-alone server product that still provides mobile browser-based viewers for these applications. These viewers called Word Mobile Viewer, Excel Mobile Viewer, and PowerPoint Mobile Viewer are optimized to render documents for phones. When integrated with SharePoint Server 2013, a user can enjoy enhanced viewing experiences when interacting with documents on the phone.
  • Push notificationsSharePoint Server 2013 supports applications on mobile devices (such as smartphones, tablets, and so on) that should receive notifications from a SharePoint site. Notifications can include events that occur in the site, such as when a user adds an item to a list or updates an item. For mobile devices to receive these notifications, device applications must register with a SharePoint site. Once the device is registered, you can write event handler code to interact with Microsoft Push Notification Service or notification services of other mobile device platforms. Notifications are sent from the server where the application is hosted to the registered mobile device applicationLocationSharePoint Server 2013 introduces a new geolocation field type that can be used in a list. For example, you can now make lists “location-aware” and display latitude and longitude coordinates through Bing Maps. An entry is typically seen as a pushpin on the map view. Although there are several ways to use this geolocation field, one key scenario is for mobile application development. Users can track or log location-specific data while they work remotely from the corporate office. Alternatively, the application can help them locate points of interest when it performs offsite functions.Office Web AppsIn SharePoint Server 2010, Office Web Apps Server provides browser-based companions for Word, Excel, and PowerPoint. When Office Web Apps Server is installed on SharePoint Server 2010, Office Mobile Web Apps is also installed on the server. Office Mobile Web Apps enables users to open documents in the mobile web application by using a mobile browser. With SharePoint Server 2013, Office Web Apps Server is no longer a companion product installed on a computer that is running SharePoint Server. Instead, Office Web Apps Server is a new stand-alone server product that still provides mobile browser-based viewers for these applications. These viewers called Word Mobile Viewer, Excel Mobile Viewer, and PowerPoint Mobile Viewer are optimized to render documents for phones. When integrated with SharePoint Server 2013, a user can enjoy enhanced viewing experiences when interacting with documents on the phone.
  • Image renditions -> creates different renditions of an image for predefined resolutions.
  • From a crawling perspective, we have some new features. One of them is the ability to configure a crawl to happen anonymously. For example, if you are crawling a public web site like Microsoft.Com then it makes no sense to try and have the crawl account authenticate with it each time it tries to start a new crawl. In addition to that, we’ve also made a big push in SharePoint 2013 to have much of the user interface rendered asynchronously. That works great from an end user perspective, but it is a problem when you try and index it because the crawler will just ask for data and index whatever it is returned to it; it won’t wait for an asynchronous call to retrieve additional data. What we’ve done to mitigate that is made our chrome controls “aware” of the crawler by looking for the user agent string that it uses during a crawl. By doing this, the web parts can determine when a request is being made by the search crawler. If it is then they just render their data synchronously instead of asynchronously. This is a pattern that custom developers will also want to consider as they developer applications for SharePoint 2013.
  • New way of building product driven sitesOld way was create a publishing site and a page for every productNew wayProduct catalog: List and a term set for categorizing the itemProduct site that consumes the catalogUse Term set for navigation , content by search web partZZZZZZZZAZZZAZZAHome page, product page and item detail pageProducts can be a broad conceptAmplexor -> we have projects
  • Youbasically host SharePointwithinyourown company andmaintainitwe’retalkingaboutone or multiple SharePoint farms - virtualized or not - the’re part of your server park,and offer your employees: Intranet portal, collaboration sites, Integratewith back end systems andso on … with SharePoint
  • Extranet / Intranet scenario’s: no more needfor SharePoint for Internet Sites (FIS) licenseNo CAL’sneededforExternal UsersOffice Web AppsLicensing: Read = Free Edit = users Office 2013 Standard or Professional Plus editionsneeded
  • Office 365Planshttp://blogs.technet.com/b/lystavlen/archive/2013/03/30/office-365-comparing-p-m-and-e-plans.aspxP1 = Office 365 Small BusinessP2 = Office 365 Small Business Premium(Designed for 1-10 users, maximum of 25 users)E1 = Office 365 Enterprise E1E3 = Office 365 Enterprise E3 > BCS, InfoPath Forms ServicesE4 = Office 365 Enterprise E4 >Plans differ in offered workloads, #users and storage
  • Some features are onlyavailable in the on-premises/azure. E.g. Cross Site PublishingSome features are onlyavailable in SharePoint online
  • SharePoint OnlineCloud reduces costs on infrastructure, licenses and maintenance -> Allows to focus on core business, not IT. Example: costs for backup & restore on prem are not transparentAlways have the latest and greatestReduce storage footprintCan easily scale up/down according to demandMore easily work with customers, partners outside of my companyHybrid scenario’s: for example, need for external collaboration (a.k.a. Extranet). Move to the cloud for sharing data / collaborating with partners, clients while maintaining existing sharepoint infrastructure for intranet, internal collaboration
  • OneexampleCloudShare – offers demo/development environments which are up & running in minutes
  • LimitationsNo cross-site collection access
  • DevModels:FarmSolutions > on-premSandboxedSolutions > Cloud, limited Object ModelApp Model > on-prem & cloud
  • Open Data Protocol (OData) is a web protocol that is used to query and update data in the web and cloudREST – Client Side Object Model (JavaScript) for BCS
  • Original Farm settingsAuthentication providers andusedauthenticationmodelsCertificatesAAM, ManagedPathCustomizations: custom or 3rd party solutions, SharePoint Designer site modifications
  • 3. For a database-attach upgrade, you upgrade the data and sites on a separate farm from your original farm.4. Side by side modes: a SC can remain in 2010 mode, running solutions in the 14th hive. Limitations: solutions using Microsoft.SharePoint DLL = use of 15 version!5a. Create an upgrade evaluation site collection= test copy of SC to detect potential upgrade problems
  • Redesign / do-over.Certainworkloads (a.k.a site collections) in the legacy farm canbemigratedandothersnot.For instance: migrateexistingcollaboration sites + new collaboration sites are in 2013 mode. Redo the Intranet because new company branding is in scope (+ mobile devices)?
  • Deprecated features: http://www.c-sharpcorner.com/UploadFile/Roji.Joy/deprecated-features-in-sharepoint-2013-from-sharepoint-2010/- Site templates: Document/Meeting Workspace site template, … (4 total)- SharePoint Search SQL syntax > now FAST under the hood: FAST Query LanguageTechnically 2010 to 2013 versions are closer toeachotherthen MOSS 2007 with SP2010SP2010 solutions are stillsupported

Amplexor Sharepoint 2013 seminar Amplexor Sharepoint 2013 seminar Presentation Transcript

  • Micro blogging
  • DEMO
  • 2013 Intranet Extranet Internet Sites Internal Users SharePoint Server + CAL SharePoint Server + CAL SharePoint Server External Users* N/A SharePoint Server SharePoint Server
  • http://technet.microsoft.com/en-us/library/jj819274.aspx
  • Analytics, PerformancePoint BI Excel Services, Power View, PowerPivot SP Online SharePoint 2013 Deep refinement, enhance relevancy Search People/Expertise, hover card, enterprise search Full-trust code, BCS+Developer Cloud app model, Sandbox, CSOM, BCS Cross-site scripting, content by search Internet Public Website, Design Manager, apps/store Central AdministrationAdmin Tenant-level, PowerShell, IRM, Recycle Bin ECM / Social eDiscovery, Records Center, Site Mailbox, Mobile, Newsfeed
  • http://office.microsoft.com/en-us/store/apps-for-sharepoint- FX102804987.aspx
  • MOSS 2007 SharePoint 2010 SharePoint 2013
  • http://www.c-sharpcorner.com/UploadFile/Roji.Joy/deprecated-features-in-sharepoint-2013-from- sharepoint-2010