Pro SharePoint 2013 Administration - EBook Free Download

More documents

Recommendations

Info

Chapter 4 ■ Upgrading from SharePoint 2010The first task in managing customizations is to itemize them. If you have only ever installed customizations usingSharePoint deployment packages (Microsoft best practice), then you are in a good place. However, if your SharePointsite has evolved over time with various manual edits to files in the hive (the file location where SharePoint maintainsstatic files), manual changes to configuration files, and manual placement of custom assemblies in the GAC or webapplication, then you have a greater task to manage.SharePoint 2007 to 2010 upgrade used to include a pre-upgrade check tool, which would list all potential issuesprior to an upgrade. This tool included a report of all installed features and customizations in the farm. Microsofthas since retired this tool. Although the process of identifying customizations is not as straightforward as withthe pre-upgrade checker, the good news is that SharePoint 2013 supports parallel hives, so you can maintain yourcustomizations in a “14” hive directory structure without breaking your customizations.■ ■Note SharePoint 2013 no longer supports the pre-upgrade checker.I recommend that you upgrade all customizations to SharePoint 2013, which might involve installing the latestversion of a third-party product, or may involve some in-house development of custom components. However, thisprocess need not hold up the upgrade process and prevent users using the post-upgraded site on the new platformwhile your development team undertakes this effort.Once you have itemized your customizations, you should next evaluate the impact of each customization on theupgrade. Customizations typically fall into one of three categories, as described in Table 4-2.Table 4-2. Customization CategoriesCategory of Customization Types of Customization Potential Effects on UpgradeVisualData StructureNon-VisualMaster pagesThemesCustom controlsWeb pagesWeb PartsCustom JavaScriptCustom CSS filesContent typesList typesWeb templatesSite definitionsWeb servicesWindows servicesHTTP handlersHTTP modulesCustom classesNo impact on database attach upgrades; shouldwork in SharePoint 2010 user interface mode; likelyrequires change to work in SharePoint 2013 userinterfaceMay affect database upgrade if content or list typesconflict with new SharePoint 2013 list or contenttypes; missing list definitions or templates may alsocause the upgrade to failMight not work with SharePoint 2013; test thoroughlyin the new platform and consider updating to anew version (third-party) or developing againstthe latest version of SharePoint 2013 API (in-housedevelopment)After evaluating every customization and assessing the impact of the customization on the upgrade to the newSharePoint system, you can decide the outcome of each customization as follows:80• Keep the customization but do not upgrade site collections—In cases where a customizationdepends on the SharePoint 2010 platform, e.g., a particular branding married to theSharePoint 2010 branding style, you can continue to use the customization in the legacy visualmode. Users are unable to use some of the newer features of SharePoint 2013 (especially someof the visual capabilities) until you convert the customization to use SharePoint 2013.www.it-ebooks.info
Chapter 4 ■ Upgrading from SharePoint 2010• Replace the customization—Perhaps you are taking this upgrade opportunity to redesignyour site or redevelop existing customizations. In this case, redeveloping customizations ordeploying the latest SharePoint 2013–supported version of a third-party component will allowyour users to take full advantage of the SharePoint 2013 capabilities.• Discard the customization—Sometimes a customization is no longer relevant. PerhapsSharePoint 2013 now provides capabilities that SharePoint 2010 lacked and the customizationfulfilled. Perhaps the upgrade is part of a larger strategy to redesign and there is no place fora particular customization. In these cases, retire the customization from service and removereferences of the customizations prior to upgrade (as part of pre-maintenance). The extentof the customization in the database (e.g., a content type) will determine how easy it is toremove the customization prior to upgrade, and therefore determine if you should remove thecustomization from a production copy of your SharePoint 2010 farm, rather than productionitself—I never said dealing with customizations is easy.Different types of customization require different consideration in their upgrade to work in SharePoint 2013. Letme assume you have a customization that you intend to upgrade to SharePoint 2013 and fully integrate into the newvisual style of SharePoint 2013. The implementation type of the customization will determine the best course of actionto upgrade, as shown in Table 4-3.Table 4-3. Customization Types and Upgrade ApproachCustomizationSite definitionFeatureWorkflow and server controlsEvent handlerThemesMaster pages and CSS filesJavaScriptWeb PartsUpgrade ApproachApply the main components of your site definition to an existing definition inSharePoint 2013—apply features, files, etc. In cases where you no longer wish to createnew sites based on the custom site definition in SharePoint 2013, you can move overthe custom site definition as is and run legacy sites in SharePoint 2010 mode.Evaluate your feature and redesign as necessary. The feature-packaging modelin SharePoint 2013 is identical to that of SharePoint 2010—it is the capabilitiescontained in the feature itself that usually require redevelopment.Upgrade of workflow and server components depends on the implementation andtypically aligns closely to a business need. Consult the users of said workflow orcomponent to determine the need of such functionality in the new SharePoint 2013system.Event handlers should continue to operate in SharePoint 2013 after upgradingcontent. However, any API calls that event handlers make, or assumptions about theenvironment, may affect the continual successful operation of these event handlers.You should re-create themes, based on best practices for creating themes forSharePoint 2013.Rework visual customizations into SharePoint 2013 master pages and CSS files soyour brand works with the latest SharePoint 2013 user interface.Validate that your JavaScript works with the new SharePoint 2013 page mode, andredevelop as appropriate.Similar to event handlers, Web Parts may make API calls, which require changes tosupport SharePoint 2013 API. Additionally, visual Web Parts should comply withXHTML and support the user interface of SharePoint 2013 if not operating in legacySharePoint 2010 compatibility mode.(continued)81www.it-ebooks.info
Page 1 and 2:
www.it-ebooks.info
Page 3 and 4:
Contents at a GlanceForeword xixAbo
Page 5 and 6:
IntroductionHello, and welcome to P
Page 7 and 8:
Chapter 1 ■ SharePoint 2013 Overv
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Chapter 2 ■ New Installation and
Page 29 and 30:
Page 31 and 32:
Page 33 and 34: Chapter 2 ■ New Installation and
Page 65 and 66: Chapter 3 ■ Working with PowerShe
Page 79 and 80: Chapter 4Upgrading from SharePoint
Page 81 and 82: Chapter 4 ■ Upgrading from ShareP
Page 83: Chapter 4 ■ Upgrading from ShareP
Page 87 and 88: UpgradeChapter 4 ■ Upgrading from
Page 107 and 108: SummaryChapter 4 ■ Upgrading from
Page 109 and 110: Chapter 5 ■ Health Monitoring and
Page 135 and 136:
Chapter 5 ■ Health Monitoring and
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Chapter 6 ■ Users, Profiles, and
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Chapter 7Security and PolicyAsking
Page 207 and 208:
Chapter 7 ■ Security and Policy
Page 209 and 210:
Permissions and Permission LevelsCh
Page 211 and 212:
Chapter 7 ■ Security and PolicyFi
Page 213 and 214:
Chapter 7 ■ Security and PolicyHo
Page 215 and 216:
Page 217 and 218:
Chapter 7 ■ Security and PolicyPu
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Chapter 7 ■ Security and Policy1.
Page 225 and 226:
Chapter 7 ■ Security and PolicyPe
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Chapter 7 ■ Security and PolicyTh
Page 233 and 234:
Chapter 7 ■ Security and Policy6.
Page 235 and 236:
Page 237 and 238:
Chapter 8 ■ Claims-Based and Fede
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Chapter 9 ■ Content Model and Man
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Chapter 10 ■ Publishing and Web C
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Chapter 11 ■ Documents and Record
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Chapter 12Business IntelligenceBusi
Page 429 and 430:
PerformancePoint ServicesChapter 12
Page 431 and 432:
Chapter 12 ■ Business Intelligenc
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
PerformancePoint Dashboards in Prod
Page 449 and 450:
Save from Visio to SharePointChapte
Page 451 and 452:
Create Workflows from VisioChapter
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Chapter 13Business Connectivity Ser
Page 465 and 466:
Chapter 13 ■ Business Connectivit
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Connecting to an OData SourceChapte
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
Page 501 and 502:
Chapter 14 ■ Microsoft Office Int
Page 503 and 504:
Page 505 and 506:
Page 507 and 508:
Page 509 and 510:
Page 511 and 512:
Page 513 and 514:
Page 515 and 516:
Page 517 and 518:
Page 519 and 520:
Page 521 and 522:
Page 523 and 524:
Page 525 and 526:
Page 527 and 528:
Page 529 and 530:
Page 531 and 532:
Page 533 and 534:
Page 535 and 536:
Page 537 and 538:
Page 539 and 540:
Page 541 and 542:
Page 543 and 544:
Page 545 and 546:
Page 547 and 548:
Page 549 and 550:
Page 551 and 552:
Chapter 15 ■ SharePoint SearchFig
Page 553 and 554:
Chapter 15 ■ SharePoint SearchCon
Page 555 and 556:
Chapter 15 ■ SharePoint Searchbec
Page 557 and 558:
Page 559 and 560:
Chapter 15 ■ SharePoint Search5.
Page 561 and 562:
Page 563 and 564:
Page 565 and 566:
Page 567 and 568:
Chapter 15 ■ SharePoint Searchkno
Page 569 and 570:
Chapter 15 ■ SharePoint Search■
Page 571 and 572:
Chapter 15 ■ SharePoint SearchAut
Page 573 and 574:
Page 575 and 576:
Chapter 15 ■ SharePoint SearchThe
Page 577 and 578:
Page 579 and 580:
Page 581 and 582:
Page 583 and 584:
Chapter 15 ■ SharePoint SearchIn
Page 585 and 586:
Page 587 and 588:
Page 589 and 590:
Page 591 and 592:
Page 593 and 594:
Page 595 and 596:
Page 597 and 598:
Chapter 15 ■ SharePoint Search•
Page 599 and 600:
Chapter 15 ■ SharePoint SearchUsa
Page 601 and 602:
Chapter 16SharePoint Designer and B
Page 603 and 604:
Chapter 16 ■ SharePoint Designer
Page 605 and 606:
Page 607 and 608:
Page 609 and 610:
Page 611 and 612:
Page 613 and 614:
Page 615 and 616:
Page 617 and 618:
Page 619 and 620:
Page 621 and 622:
Page 623 and 624:
Page 625 and 626:
Page 627 and 628:
Page 629 and 630:
■ indexBusiness connectivity serv
Page 631 and 632:
■ indexEnterprise search platform
Page 633 and 634:
■ indexOffice applications (cont.
Page 635 and 636:
■ indexSecurity (cont.)anonymous
Page 637 and 638:
■ indexSharePoint metadata types
Page 639 and 640:
Pro SharePoint 2013AdministrationRo
Page 641 and 642:
I dedicate this manuscript to my wi
Page 643 and 644:
■ ContentsService Application Cha
Page 645 and 646:
■ ContentsUpgrade83Copying Legacy
Page 647 and 648:
■ Contents■■Chapter 7: Securi
Page 649 and 650:
■ ContentsContent Management 322C
Page 651 and 652:
■ ContentsExport and Import Model
Page 653 and 654:
ForewordThank you for taking the ti
Page 655 and 656:
About the Technical ReviewerPranav
show all

Pro SharePoint 2013 Administration - EBook Free Download

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?