diff --git a/.gitignore b/.gitignore index acaea0eabe..3eac81834f 100644 --- a/.gitignore +++ b/.gitignore @@ -1,7 +1,7 @@ -log/ -obj/ -_site/ -.optemp/ -_themes*/ - +log/ +obj/ +_site/ +.optemp/ +_themes*/ + .openpublishing.buildcore.ps1 \ No newline at end of file diff --git a/.openpublishing.build.ps1 b/.openpublishing.build.ps1 index aadef76202..93bdf62f2f 100644 --- a/.openpublishing.build.ps1 +++ b/.openpublishing.build.ps1 @@ -1,17 +1,17 @@ -param( - [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1", - [string]$parameters -) -# Main -$errorActionPreference = 'Stop' - -# Step-1: Download buildcore script to local -echo "download build core script to local with source url: $buildCorePowershellUrl" -$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition -$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1" -Invoke-WebRequest $buildCorePowershellUrl -OutFile "$buildCorePowershellDestination" - -# Step-2: Run build core -echo "run build core script with parameters: $parameters" -& "$buildCorePowershellDestination" "$parameters" -exit $LASTEXITCODE +param( + [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1", + [string]$parameters +) +# Main +$errorActionPreference = 'Stop' + +# Step-1: Download buildcore script to local +echo "download build core script to local with source url: $buildCorePowershellUrl" +$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition +$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1" +Invoke-WebRequest $buildCorePowershellUrl -OutFile "$buildCorePowershellDestination" + +# Step-2: Run build core +echo "run build core script with parameters: $parameters" +& "$buildCorePowershellDestination" "$parameters" +exit $LASTEXITCODE diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json index 6bfcf194f1..29936a6eb8 100644 --- a/.openpublishing.publish.config.json +++ b/.openpublishing.publish.config.json @@ -1,53 +1,53 @@ -{ - "need_generate_pdf": false, - "need_generate_intellisense": false, - "docsets_to_publish": [ - { - "docset_name": "OfficeDocs-SharePoint", - "build_source_folder": "SharePoint", - "build_output_subfolder": "OfficeDocs-SharePoint", - "locale": "en-us", - "monikers": [], - "moniker_ranges": [], - "open_to_public_contributors": false, - "type_mapping": { - "Conceptual": "Content", - "ManagedReference": "Content", - "RestApi": "Content" - }, - "build_entry_point": "docs", - "template_folder": "_themes", - "version": 0 - }, - { - "docset_name": "OfficeDocs-OneDrive", - "build_source_folder": "OneDriveForBusiness", - "build_output_subfolder": "OfficeDocs-OneDrive", - "locale": "en-us", - "monikers": [], - "moniker_ranges": [], - "open_to_public_contributors": false, - "type_mapping": { - "Conceptual": "Content", - "ManagedReference": "Content", - "RestApi": "Content" - }, - "build_entry_point": "docs", - "template_folder": "_themes", - "version": 0 - } - ], - "notification_subscribers": [], - "branches_to_filter": [], - "skip_source_output_uploading": false, - "need_preview_pull_request": false, - "dependent_repositories": [ - { - "path_to_root": "_themes", - "url": "https://github.com/Microsoft/templates.docs.msft", - "branch": "master", - "branch_mapping": {} - } - ], - "need_generate_pdf_url_template": false +{ + "need_generate_pdf": false, + "need_generate_intellisense": false, + "docsets_to_publish": [ + { + "docset_name": "OfficeDocs-SharePoint", + "build_source_folder": "SharePoint", + "build_output_subfolder": "OfficeDocs-SharePoint", + "locale": "en-us", + "monikers": [], + "moniker_ranges": [], + "open_to_public_contributors": false, + "type_mapping": { + "Conceptual": "Content", + "ManagedReference": "Content", + "RestApi": "Content" + }, + "build_entry_point": "docs", + "template_folder": "_themes", + "version": 0 + }, + { + "docset_name": "OfficeDocs-OneDrive", + "build_source_folder": "OneDriveForBusiness", + "build_output_subfolder": "OfficeDocs-OneDrive", + "locale": "en-us", + "monikers": [], + "moniker_ranges": [], + "open_to_public_contributors": false, + "type_mapping": { + "Conceptual": "Content", + "ManagedReference": "Content", + "RestApi": "Content" + }, + "build_entry_point": "docs", + "template_folder": "_themes", + "version": 0 + } + ], + "notification_subscribers": [], + "branches_to_filter": [], + "skip_source_output_uploading": false, + "need_preview_pull_request": false, + "dependent_repositories": [ + { + "path_to_root": "_themes", + "url": "https://github.com/Microsoft/templates.docs.msft", + "branch": "master", + "branch_mapping": {} + } + ], + "need_generate_pdf_url_template": false } \ No newline at end of file diff --git a/LICENSE b/LICENSE index e056e7c3ec..abe99dbee4 100644 --- a/LICENSE +++ b/LICENSE @@ -1,395 +1,395 @@ -Attribution 4.0 International - -======================================================================= - -Creative Commons Corporation ("Creative Commons") is not a law firm and -does not provide legal services or legal advice. Distribution of -Creative Commons public licenses does not create a lawyer-client or -other relationship. Creative Commons makes its licenses and related -information available on an "as-is" basis. Creative Commons gives no -warranties regarding its licenses, any material licensed under their -terms and conditions, or any related information. Creative Commons -disclaims all liability for damages resulting from their use to the -fullest extent possible. - -Using Creative Commons Public Licenses - -Creative Commons public licenses provide a standard set of terms and -conditions that creators and other rights holders may use to share -original works of authorship and other material subject to copyright -and certain other rights specified in the public license below. The -following considerations are for informational purposes only, are not -exhaustive, and do not form part of our licenses. - - Considerations for licensors: Our public licenses are - intended for use by those authorized to give the public - permission to use material in ways otherwise restricted by - copyright and certain other rights. Our licenses are - irrevocable. Licensors should read and understand the terms - and conditions of the license they choose before applying it. - Licensors should also secure all rights necessary before - applying our licenses so that the public can reuse the - material as expected. Licensors should clearly mark any - material not subject to the license. This includes other CC- - licensed material, or material used under an exception or - limitation to copyright. More considerations for licensors: - wiki.creativecommons.org/Considerations_for_licensors - - Considerations for the public: By using one of our public - licenses, a licensor grants the public permission to use the - licensed material under specified terms and conditions. If - the licensor's permission is not necessary for any reason--for - example, because of any applicable exception or limitation to - copyright--then that use is not regulated by the license. Our - licenses grant only permissions under copyright and certain - other rights that a licensor has authority to grant. Use of - the licensed material may still be restricted for other - reasons, including because others have copyright or other - rights in the material. A licensor may make special requests, - such as asking that all changes be marked or described. - Although not required by our licenses, you are encouraged to - respect those requests where reasonable. More_considerations - for the public: - wiki.creativecommons.org/Considerations_for_licensees - -======================================================================= - -Creative Commons Attribution 4.0 International Public License - -By exercising the Licensed Rights (defined below), You accept and agree -to be bound by the terms and conditions of this Creative Commons -Attribution 4.0 International Public License ("Public License"). To the -extent this Public License may be interpreted as a contract, You are -granted the Licensed Rights in consideration of Your acceptance of -these terms and conditions, and the Licensor grants You such rights in -consideration of benefits the Licensor receives from making the -Licensed Material available under these terms and conditions. - - -Section 1 -- Definitions. - - a. Adapted Material means material subject to Copyright and Similar - Rights that is derived from or based upon the Licensed Material - and in which the Licensed Material is translated, altered, - arranged, transformed, or otherwise modified in a manner requiring - permission under the Copyright and Similar Rights held by the - Licensor. For purposes of this Public License, where the Licensed - Material is a musical work, performance, or sound recording, - Adapted Material is always produced where the Licensed Material is - synched in timed relation with a moving image. - - b. Adapter's License means the license You apply to Your Copyright - and Similar Rights in Your contributions to Adapted Material in - accordance with the terms and conditions of this Public License. - - c. Copyright and Similar Rights means copyright and/or similar rights - closely related to copyright including, without limitation, - performance, broadcast, sound recording, and Sui Generis Database - Rights, without regard to how the rights are labeled or - categorized. For purposes of this Public License, the rights - specified in Section 2(b)(1)-(2) are not Copyright and Similar - Rights. - - d. Effective Technological Measures means those measures that, in the - absence of proper authority, may not be circumvented under laws - fulfilling obligations under Article 11 of the WIPO Copyright - Treaty adopted on December 20, 1996, and/or similar international - agreements. - - e. Exceptions and Limitations means fair use, fair dealing, and/or - any other exception or limitation to Copyright and Similar Rights - that applies to Your use of the Licensed Material. - - f. Licensed Material means the artistic or literary work, database, - or other material to which the Licensor applied this Public - License. - - g. Licensed Rights means the rights granted to You subject to the - terms and conditions of this Public License, which are limited to - all Copyright and Similar Rights that apply to Your use of the - Licensed Material and that the Licensor has authority to license. - - h. Licensor means the individual(s) or entity(ies) granting rights - under this Public License. - - i. Share means to provide material to the public by any means or - process that requires permission under the Licensed Rights, such - as reproduction, public display, public performance, distribution, - dissemination, communication, or importation, and to make material - available to the public including in ways that members of the - public may access the material from a place and at a time - individually chosen by them. - - j. Sui Generis Database Rights means rights other than copyright - resulting from Directive 96/9/EC of the European Parliament and of - the Council of 11 March 1996 on the legal protection of databases, - as amended and/or succeeded, as well as other essentially - equivalent rights anywhere in the world. - - k. You means the individual or entity exercising the Licensed Rights - under this Public License. Your has a corresponding meaning. - - -Section 2 -- Scope. - - a. License grant. - - 1. Subject to the terms and conditions of this Public License, - the Licensor hereby grants You a worldwide, royalty-free, - non-sublicensable, non-exclusive, irrevocable license to - exercise the Licensed Rights in the Licensed Material to: - - a. reproduce and Share the Licensed Material, in whole or - in part; and - - b. produce, reproduce, and Share Adapted Material. - - 2. Exceptions and Limitations. For the avoidance of doubt, where - Exceptions and Limitations apply to Your use, this Public - License does not apply, and You do not need to comply with - its terms and conditions. - - 3. Term. The term of this Public License is specified in Section - 6(a). - - 4. Media and formats; technical modifications allowed. The - Licensor authorizes You to exercise the Licensed Rights in - all media and formats whether now known or hereafter created, - and to make technical modifications necessary to do so. The - Licensor waives and/or agrees not to assert any right or - authority to forbid You from making technical modifications - necessary to exercise the Licensed Rights, including - technical modifications necessary to circumvent Effective - Technological Measures. For purposes of this Public License, - simply making modifications authorized by this Section 2(a) - (4) never produces Adapted Material. - - 5. Downstream recipients. - - a. Offer from the Licensor -- Licensed Material. Every - recipient of the Licensed Material automatically - receives an offer from the Licensor to exercise the - Licensed Rights under the terms and conditions of this - Public License. - - b. No downstream restrictions. You may not offer or impose - any additional or different terms or conditions on, or - apply any Effective Technological Measures to, the - Licensed Material if doing so restricts exercise of the - Licensed Rights by any recipient of the Licensed - Material. - - 6. No endorsement. Nothing in this Public License constitutes or - may be construed as permission to assert or imply that You - are, or that Your use of the Licensed Material is, connected - with, or sponsored, endorsed, or granted official status by, - the Licensor or others designated to receive attribution as - provided in Section 3(a)(1)(A)(i). - - b. Other rights. - - 1. Moral rights, such as the right of integrity, are not - licensed under this Public License, nor are publicity, - privacy, and/or other similar personality rights; however, to - the extent possible, the Licensor waives and/or agrees not to - assert any such rights held by the Licensor to the limited - extent necessary to allow You to exercise the Licensed - Rights, but not otherwise. - - 2. Patent and trademark rights are not licensed under this - Public License. - - 3. To the extent possible, the Licensor waives any right to - collect royalties from You for the exercise of the Licensed - Rights, whether directly or through a collecting society - under any voluntary or waivable statutory or compulsory - licensing scheme. In all other cases the Licensor expressly - reserves any right to collect such royalties. - - -Section 3 -- License Conditions. - -Your exercise of the Licensed Rights is expressly made subject to the -following conditions. - - a. Attribution. - - 1. If You Share the Licensed Material (including in modified - form), You must: - - a. retain the following if it is supplied by the Licensor - with the Licensed Material: - - i. identification of the creator(s) of the Licensed - Material and any others designated to receive - attribution, in any reasonable manner requested by - the Licensor (including by pseudonym if - designated); - - ii. a copyright notice; - - iii. a notice that refers to this Public License; - - iv. a notice that refers to the disclaimer of - warranties; - - v. a URI or hyperlink to the Licensed Material to the - extent reasonably practicable; - - b. indicate if You modified the Licensed Material and - retain an indication of any previous modifications; and - - c. indicate the Licensed Material is licensed under this - Public License, and include the text of, or the URI or - hyperlink to, this Public License. - - 2. You may satisfy the conditions in Section 3(a)(1) in any - reasonable manner based on the medium, means, and context in - which You Share the Licensed Material. For example, it may be - reasonable to satisfy the conditions by providing a URI or - hyperlink to a resource that includes the required - information. - - 3. If requested by the Licensor, You must remove any of the - information required by Section 3(a)(1)(A) to the extent - reasonably practicable. - - 4. If You Share Adapted Material You produce, the Adapter's - License You apply must not prevent recipients of the Adapted - Material from complying with this Public License. - - -Section 4 -- Sui Generis Database Rights. - -Where the Licensed Rights include Sui Generis Database Rights that -apply to Your use of the Licensed Material: - - a. for the avoidance of doubt, Section 2(a)(1) grants You the right - to extract, reuse, reproduce, and Share all or a substantial - portion of the contents of the database; - - b. if You include all or a substantial portion of the database - contents in a database in which You have Sui Generis Database - Rights, then the database in which You have Sui Generis Database - Rights (but not its individual contents) is Adapted Material; and - - c. You must comply with the conditions in Section 3(a) if You Share - all or a substantial portion of the contents of the database. - -For the avoidance of doubt, this Section 4 supplements and does not -replace Your obligations under this Public License where the Licensed -Rights include other Copyright and Similar Rights. - - -Section 5 -- Disclaimer of Warranties and Limitation of Liability. - - a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - - b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - - c. The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - - -Section 6 -- Term and Termination. - - a. This Public License applies for the term of the Copyright and - Similar Rights licensed here. However, if You fail to comply with - this Public License, then Your rights under this Public License - terminate automatically. - - b. Where Your right to use the Licensed Material has terminated under - Section 6(a), it reinstates: - - 1. automatically as of the date the violation is cured, provided - it is cured within 30 days of Your discovery of the - violation; or - - 2. upon express reinstatement by the Licensor. - - For the avoidance of doubt, this Section 6(b) does not affect any - right the Licensor may have to seek remedies for Your violations - of this Public License. - - c. For the avoidance of doubt, the Licensor may also offer the - Licensed Material under separate terms or conditions or stop - distributing the Licensed Material at any time; however, doing so - will not terminate this Public License. - - d. Sections 1, 5, 6, 7, and 8 survive termination of this Public - License. - - -Section 7 -- Other Terms and Conditions. - - a. The Licensor shall not be bound by any additional or different - terms or conditions communicated by You unless expressly agreed. - - b. Any arrangements, understandings, or agreements regarding the - Licensed Material not stated herein are separate from and - independent of the terms and conditions of this Public License. - - -Section 8 -- Interpretation. - - a. For the avoidance of doubt, this Public License does not, and - shall not be interpreted to, reduce, limit, restrict, or impose - conditions on any use of the Licensed Material that could lawfully - be made without permission under this Public License. - - b. To the extent possible, if any provision of this Public License is - deemed unenforceable, it shall be automatically reformed to the - minimum extent necessary to make it enforceable. If the provision - cannot be reformed, it shall be severed from this Public License - without affecting the enforceability of the remaining terms and - conditions. - - c. No term or condition of this Public License will be waived and no - failure to comply consented to unless expressly agreed to by the - Licensor. - - d. Nothing in this Public License constitutes or may be interpreted - as a limitation upon, or waiver of, any privileges and immunities - that apply to the Licensor or You, including from the legal - processes of any jurisdiction or authority. - - -======================================================================= - -Creative Commons is not a party to its public -licenses. Notwithstanding, Creative Commons may elect to apply one of -its public licenses to material it publishes and in those instances -will be considered the “Licensor.” The text of the Creative Commons -public licenses is dedicated to the public domain under the CC0 Public -Domain Dedication. Except for the limited purpose of indicating that -material is shared under a Creative Commons public license or as -otherwise permitted by the Creative Commons policies published at -creativecommons.org/policies, Creative Commons does not authorize the -use of the trademark "Creative Commons" or any other trademark or logo -of Creative Commons without its prior written consent including, -without limitation, in connection with any unauthorized modifications -to any of its public licenses or any other arrangements, -understandings, or agreements concerning use of licensed material. For -the avoidance of doubt, this paragraph does not form part of the -public licenses. - +Attribution 4.0 International + +======================================================================= + +Creative Commons Corporation ("Creative Commons") is not a law firm and +does not provide legal services or legal advice. Distribution of +Creative Commons public licenses does not create a lawyer-client or +other relationship. Creative Commons makes its licenses and related +information available on an "as-is" basis. Creative Commons gives no +warranties regarding its licenses, any material licensed under their +terms and conditions, or any related information. Creative Commons +disclaims all liability for damages resulting from their use to the +fullest extent possible. + +Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and +conditions that creators and other rights holders may use to share +original works of authorship and other material subject to copyright +and certain other rights specified in the public license below. The +following considerations are for informational purposes only, are not +exhaustive, and do not form part of our licenses. + + Considerations for licensors: Our public licenses are + intended for use by those authorized to give the public + permission to use material in ways otherwise restricted by + copyright and certain other rights. Our licenses are + irrevocable. Licensors should read and understand the terms + and conditions of the license they choose before applying it. + Licensors should also secure all rights necessary before + applying our licenses so that the public can reuse the + material as expected. Licensors should clearly mark any + material not subject to the license. This includes other CC- + licensed material, or material used under an exception or + limitation to copyright. More considerations for licensors: + wiki.creativecommons.org/Considerations_for_licensors + + Considerations for the public: By using one of our public + licenses, a licensor grants the public permission to use the + licensed material under specified terms and conditions. If + the licensor's permission is not necessary for any reason--for + example, because of any applicable exception or limitation to + copyright--then that use is not regulated by the license. Our + licenses grant only permissions under copyright and certain + other rights that a licensor has authority to grant. Use of + the licensed material may still be restricted for other + reasons, including because others have copyright or other + rights in the material. A licensor may make special requests, + such as asking that all changes be marked or described. + Although not required by our licenses, you are encouraged to + respect those requests where reasonable. More_considerations + for the public: + wiki.creativecommons.org/Considerations_for_licensees + +======================================================================= + +Creative Commons Attribution 4.0 International Public License + +By exercising the Licensed Rights (defined below), You accept and agree +to be bound by the terms and conditions of this Creative Commons +Attribution 4.0 International Public License ("Public License"). To the +extent this Public License may be interpreted as a contract, You are +granted the Licensed Rights in consideration of Your acceptance of +these terms and conditions, and the Licensor grants You such rights in +consideration of benefits the Licensor receives from making the +Licensed Material available under these terms and conditions. + + +Section 1 -- Definitions. + + a. Adapted Material means material subject to Copyright and Similar + Rights that is derived from or based upon the Licensed Material + and in which the Licensed Material is translated, altered, + arranged, transformed, or otherwise modified in a manner requiring + permission under the Copyright and Similar Rights held by the + Licensor. For purposes of this Public License, where the Licensed + Material is a musical work, performance, or sound recording, + Adapted Material is always produced where the Licensed Material is + synched in timed relation with a moving image. + + b. Adapter's License means the license You apply to Your Copyright + and Similar Rights in Your contributions to Adapted Material in + accordance with the terms and conditions of this Public License. + + c. Copyright and Similar Rights means copyright and/or similar rights + closely related to copyright including, without limitation, + performance, broadcast, sound recording, and Sui Generis Database + Rights, without regard to how the rights are labeled or + categorized. For purposes of this Public License, the rights + specified in Section 2(b)(1)-(2) are not Copyright and Similar + Rights. + + d. Effective Technological Measures means those measures that, in the + absence of proper authority, may not be circumvented under laws + fulfilling obligations under Article 11 of the WIPO Copyright + Treaty adopted on December 20, 1996, and/or similar international + agreements. + + e. Exceptions and Limitations means fair use, fair dealing, and/or + any other exception or limitation to Copyright and Similar Rights + that applies to Your use of the Licensed Material. + + f. Licensed Material means the artistic or literary work, database, + or other material to which the Licensor applied this Public + License. + + g. Licensed Rights means the rights granted to You subject to the + terms and conditions of this Public License, which are limited to + all Copyright and Similar Rights that apply to Your use of the + Licensed Material and that the Licensor has authority to license. + + h. Licensor means the individual(s) or entity(ies) granting rights + under this Public License. + + i. Share means to provide material to the public by any means or + process that requires permission under the Licensed Rights, such + as reproduction, public display, public performance, distribution, + dissemination, communication, or importation, and to make material + available to the public including in ways that members of the + public may access the material from a place and at a time + individually chosen by them. + + j. Sui Generis Database Rights means rights other than copyright + resulting from Directive 96/9/EC of the European Parliament and of + the Council of 11 March 1996 on the legal protection of databases, + as amended and/or succeeded, as well as other essentially + equivalent rights anywhere in the world. + + k. You means the individual or entity exercising the Licensed Rights + under this Public License. Your has a corresponding meaning. + + +Section 2 -- Scope. + + a. License grant. + + 1. Subject to the terms and conditions of this Public License, + the Licensor hereby grants You a worldwide, royalty-free, + non-sublicensable, non-exclusive, irrevocable license to + exercise the Licensed Rights in the Licensed Material to: + + a. reproduce and Share the Licensed Material, in whole or + in part; and + + b. produce, reproduce, and Share Adapted Material. + + 2. Exceptions and Limitations. For the avoidance of doubt, where + Exceptions and Limitations apply to Your use, this Public + License does not apply, and You do not need to comply with + its terms and conditions. + + 3. Term. The term of this Public License is specified in Section + 6(a). + + 4. Media and formats; technical modifications allowed. The + Licensor authorizes You to exercise the Licensed Rights in + all media and formats whether now known or hereafter created, + and to make technical modifications necessary to do so. The + Licensor waives and/or agrees not to assert any right or + authority to forbid You from making technical modifications + necessary to exercise the Licensed Rights, including + technical modifications necessary to circumvent Effective + Technological Measures. For purposes of this Public License, + simply making modifications authorized by this Section 2(a) + (4) never produces Adapted Material. + + 5. Downstream recipients. + + a. Offer from the Licensor -- Licensed Material. Every + recipient of the Licensed Material automatically + receives an offer from the Licensor to exercise the + Licensed Rights under the terms and conditions of this + Public License. + + b. No downstream restrictions. You may not offer or impose + any additional or different terms or conditions on, or + apply any Effective Technological Measures to, the + Licensed Material if doing so restricts exercise of the + Licensed Rights by any recipient of the Licensed + Material. + + 6. No endorsement. Nothing in this Public License constitutes or + may be construed as permission to assert or imply that You + are, or that Your use of the Licensed Material is, connected + with, or sponsored, endorsed, or granted official status by, + the Licensor or others designated to receive attribution as + provided in Section 3(a)(1)(A)(i). + + b. Other rights. + + 1. Moral rights, such as the right of integrity, are not + licensed under this Public License, nor are publicity, + privacy, and/or other similar personality rights; however, to + the extent possible, the Licensor waives and/or agrees not to + assert any such rights held by the Licensor to the limited + extent necessary to allow You to exercise the Licensed + Rights, but not otherwise. + + 2. Patent and trademark rights are not licensed under this + Public License. + + 3. To the extent possible, the Licensor waives any right to + collect royalties from You for the exercise of the Licensed + Rights, whether directly or through a collecting society + under any voluntary or waivable statutory or compulsory + licensing scheme. In all other cases the Licensor expressly + reserves any right to collect such royalties. + + +Section 3 -- License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the +following conditions. + + a. Attribution. + + 1. If You Share the Licensed Material (including in modified + form), You must: + + a. retain the following if it is supplied by the Licensor + with the Licensed Material: + + i. identification of the creator(s) of the Licensed + Material and any others designated to receive + attribution, in any reasonable manner requested by + the Licensor (including by pseudonym if + designated); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of + warranties; + + v. a URI or hyperlink to the Licensed Material to the + extent reasonably practicable; + + b. indicate if You modified the Licensed Material and + retain an indication of any previous modifications; and + + c. indicate the Licensed Material is licensed under this + Public License, and include the text of, or the URI or + hyperlink to, this Public License. + + 2. You may satisfy the conditions in Section 3(a)(1) in any + reasonable manner based on the medium, means, and context in + which You Share the Licensed Material. For example, it may be + reasonable to satisfy the conditions by providing a URI or + hyperlink to a resource that includes the required + information. + + 3. If requested by the Licensor, You must remove any of the + information required by Section 3(a)(1)(A) to the extent + reasonably practicable. + + 4. If You Share Adapted Material You produce, the Adapter's + License You apply must not prevent recipients of the Adapted + Material from complying with this Public License. + + +Section 4 -- Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that +apply to Your use of the Licensed Material: + + a. for the avoidance of doubt, Section 2(a)(1) grants You the right + to extract, reuse, reproduce, and Share all or a substantial + portion of the contents of the database; + + b. if You include all or a substantial portion of the database + contents in a database in which You have Sui Generis Database + Rights, then the database in which You have Sui Generis Database + Rights (but not its individual contents) is Adapted Material; and + + c. You must comply with the conditions in Section 3(a) if You Share + all or a substantial portion of the contents of the database. + +For the avoidance of doubt, this Section 4 supplements and does not +replace Your obligations under this Public License where the Licensed +Rights include other Copyright and Similar Rights. + + +Section 5 -- Disclaimer of Warranties and Limitation of Liability. + + a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE + EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS + AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF + ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, + IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, + WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR + PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, + ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT + KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT + ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. + + b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE + TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, + NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, + INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, + COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR + USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN + ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR + DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR + IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + + c. The disclaimer of warranties and limitation of liability provided + above shall be interpreted in a manner that, to the extent + possible, most closely approximates an absolute disclaimer and + waiver of all liability. + + +Section 6 -- Term and Termination. + + a. This Public License applies for the term of the Copyright and + Similar Rights licensed here. However, if You fail to comply with + this Public License, then Your rights under this Public License + terminate automatically. + + b. Where Your right to use the Licensed Material has terminated under + Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided + it is cured within 30 days of Your discovery of the + violation; or + + 2. upon express reinstatement by the Licensor. + + For the avoidance of doubt, this Section 6(b) does not affect any + right the Licensor may have to seek remedies for Your violations + of this Public License. + + c. For the avoidance of doubt, the Licensor may also offer the + Licensed Material under separate terms or conditions or stop + distributing the Licensed Material at any time; however, doing so + will not terminate this Public License. + + d. Sections 1, 5, 6, 7, and 8 survive termination of this Public + License. + + +Section 7 -- Other Terms and Conditions. + + a. The Licensor shall not be bound by any additional or different + terms or conditions communicated by You unless expressly agreed. + + b. Any arrangements, understandings, or agreements regarding the + Licensed Material not stated herein are separate from and + independent of the terms and conditions of this Public License. + + +Section 8 -- Interpretation. + + a. For the avoidance of doubt, this Public License does not, and + shall not be interpreted to, reduce, limit, restrict, or impose + conditions on any use of the Licensed Material that could lawfully + be made without permission under this Public License. + + b. To the extent possible, if any provision of this Public License is + deemed unenforceable, it shall be automatically reformed to the + minimum extent necessary to make it enforceable. If the provision + cannot be reformed, it shall be severed from this Public License + without affecting the enforceability of the remaining terms and + conditions. + + c. No term or condition of this Public License will be waived and no + failure to comply consented to unless expressly agreed to by the + Licensor. + + d. Nothing in this Public License constitutes or may be interpreted + as a limitation upon, or waiver of, any privileges and immunities + that apply to the Licensor or You, including from the legal + processes of any jurisdiction or authority. + + +======================================================================= + +Creative Commons is not a party to its public +licenses. Notwithstanding, Creative Commons may elect to apply one of +its public licenses to material it publishes and in those instances +will be considered the “Licensor.” The text of the Creative Commons +public licenses is dedicated to the public domain under the CC0 Public +Domain Dedication. Except for the limited purpose of indicating that +material is shared under a Creative Commons public license or as +otherwise permitted by the Creative Commons policies published at +creativecommons.org/policies, Creative Commons does not authorize the +use of the trademark "Creative Commons" or any other trademark or logo +of Creative Commons without its prior written consent including, +without limitation, in connection with any unauthorized modifications +to any of its public licenses or any other arrangements, +understandings, or agreements concerning use of licensed material. For +the avoidance of doubt, this paragraph does not form part of the +public licenses. + Creative Commons may be contacted at creativecommons.org. \ No newline at end of file diff --git a/LICENSE-CODE b/LICENSE-CODE index b17b032a43..5c9653fad5 100644 --- a/LICENSE-CODE +++ b/LICENSE-CODE @@ -1,17 +1,17 @@ -The MIT License (MIT) -Copyright (c) Microsoft Corporation - -Permission is hereby granted, free of charge, to any person obtaining a copy of this software and -associated documentation files (the "Software"), to deal in the Software without restriction, -including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, -and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, -subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all copies or substantial -portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT -NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. -IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, -WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE +The MIT License (MIT) +Copyright (c) Microsoft Corporation + +Permission is hereby granted, free of charge, to any person obtaining a copy of this software and +associated documentation files (the "Software"), to deal in the Software without restriction, +including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, +and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, +subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or substantial +portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT +NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. +IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \ No newline at end of file diff --git a/OneDriveForBusiness/TOC.md b/OneDriveForBusiness/TOC.md index 06913f7aef..0277573a47 100644 --- a/OneDriveForBusiness/TOC.md +++ b/OneDriveForBusiness/TOC.md @@ -1 +1,2 @@ -# [Index](index.md) \ No newline at end of file +# OneDriveForBusiness Test Table of Contents +## [Welcome to OfficeDocs-OneDrive!](index.md) diff --git a/OneDriveForBusiness/docfx.json b/OneDriveForBusiness/docfx.json index 9f5b7423c0..cb3ba2e187 100644 --- a/OneDriveForBusiness/docfx.json +++ b/OneDriveForBusiness/docfx.json @@ -1,37 +1,37 @@ -{ - "build": { - "content": [ - { - "files": [ - "**/*.md" - ], - "exclude": [ - "**/obj/**", - "**/includes/**", - "README.md", - "LICENSE", - "LICENSE-CODE", - "ThirdPartyNotices" - ] - } - ], - "resource": [ - { - "files": [ - "**/*.png", - "**/*.jpg" - ], - "exclude": [ - "**/obj/**", - "**/includes/**" - ] - } - ], - "overwrite": [], - "externalReference": [], - "globalMetadata": {}, - "fileMetadata": {}, - "template": [], - "dest": "OfficeDocs-OneDrive" - } +{ + "build": { + "content": [ + { + "files": [ + "**/*.md" + ], + "exclude": [ + "**/obj/**", + "**/includes/**", + "README.md", + "LICENSE", + "LICENSE-CODE", + "ThirdPartyNotices" + ] + } + ], + "resource": [ + { + "files": [ + "**/*.png", + "**/*.jpg" + ], + "exclude": [ + "**/obj/**", + "**/includes/**" + ] + } + ], + "overwrite": [], + "externalReference": [], + "globalMetadata": {}, + "fileMetadata": {}, + "template": [], + "dest": "OfficeDocs-OneDrive" + } } \ No newline at end of file diff --git a/README.md b/README.md index 824a7c6d56..ec8a825db2 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,3 @@ -## Microsoft Open Source Code of Conduct -This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). +## Microsoft Open Source Code of Conduct +This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. \ No newline at end of file diff --git a/SharePoint/SharePoint16ITPro.md b/SharePoint/SharePoint16ITPro.md new file mode 100644 index 0000000000..6139c49eb7 --- /dev/null +++ b/SharePoint/SharePoint16ITPro.md @@ -0,0 +1,1235 @@ +# [SharePoint Server 2016](articles/sharepoint-server-2016.md) +# [Accessibility guidelines](articles/accessibility-guidelines-in-sharepoint-server-2016.md) +# [Technical diagrams](articles/technical-diagrams-for-sharepoint-server.md) +# [Updated Product Servicing Policy for SharePoint Server 2016](articles/updated-product-servicing-policy-for-sharepoint-server-2016.md) +# [Updated Product Servicing Policy for SharePoint 2013](articles/updated-product-servicing-policy-for-sharepoint-2013.md) +# [Explore](articles/explore-sharepoint-server.md) + ## [New and improved features in SharePoint Server 2016](articles/new-and-improved-features-in-sharepoint-server-2016.md) + ## [New features in November 2016 PU for SharePoint Server 2016 (Feature Pack 1)](articles/new-features-in-november-2016-pu-for-sharepoint-server-2016-feature-pack-1.md) + ## [What's deprecated or removed from SharePoint Server 2016](articles/what-s-deprecated-or-removed-from-sharepoint-server-2016.md) + ## [Overview of MinRole Server Roles in SharePoint Server 2016](articles/overview-of-minrole-server-roles-in-sharepoint-server-2016.md) + ## [Understanding workflow in SharePoint Server 2016](articles/understanding-workflow-in-sharepoint-server-2016.md) +# [New and improved features in SharePoint Server 2016](articles/new-and-improved-features-in-sharepoint-server-2016.md) +# [New features in November 2016 PU for SharePoint Server 2016 (Feature Pack 1)](articles/new-features-in-november-2016-pu-for-sharepoint-server-2016-feature-pack-1.md) +# [What's deprecated or removed from SharePoint Server 2016](articles/what-s-deprecated-or-removed-from-sharepoint-server-2016.md) +# [Overview of MinRole Server Roles in SharePoint Server 2016](articles/overview-of-minrole-server-roles-in-sharepoint-server-2016.md) +# [Understanding workflow in SharePoint Server 2016](articles/understanding-workflow-in-sharepoint-server-2016.md) +# [Plan](articles/plan-for-sharepoint-server.md) + ## [System requirements for SharePoint 2013](articles/system-requirements-for-sharepoint-2013.md) + ## [System requirements for SharePoint Server 2016](articles/system-requirements-for-sharepoint-server-2016.md) + ## [Planning for a MinRole server deployment in SharePoint Server 2016](articles/planning-for-a-minrole-server-deployment-in-sharepoint-server-2016.md) + ## [Services and Application Planning](articles/services-and-application-planning-in-sharepoint-server-2016.md) + ## [Backup and recovery planning](articles/plan-for-backup-and-recovery-in-sharepoint-server.md) + ## [Business intelligence overview](articles/business-intelligence-in-sharepoint-server-overview.md) + ## [User profiles and identities planning](articles/plan-user-profiles-and-identities.md) + ## [Email integration planning](articles/plan-email-integration-for-a-sharepoint-server-2016-farm.md) + ## [eDiscovery planning](articles/plan-ediscovery-in-sharepoint-server.md) + ## [Governance Planning](articles/governance-planning-in-sharepoint-server-2016.md) + ## [Business Connectivity Services planning](articles/plan-for-business-connectivity-services-in-sharepoint-server.md) + ## [My Sites and OneDrive for Business planning](articles/plan-for-my-sites-and-onedrive-for-business-in-sharepoint-server.md) + ## [Web content management planning](articles/plan-web-content-management-in-sharepoint-server.md) + ## [Search planning](articles/plan-search-in-sharepoint-server.md) + ## [Permissions planning for sites and content](articles/permissions-planning-for-sites-and-content-in-sharepoint-server-2016.md) + ## [Fundamental site planning](articles/fundamental-site-planning-in-sharepoint-server-2016.md) + ## [High availability and disaster recovery planning](articles/plan-for-high-availability-and-disaster-recovery-for-sharepoint-server.md) + ## [SQL Server and storage](articles/sql-server-and-storage-sharepoint-server.md) + ## [Getting started with SharePoint Server 2013 workflow](articles/getting-started-with-sharepoint-server-2013-workflow.md) + ## [Plan for feeds and the Distributed Cache service](articles/plan-for-feeds-and-the-distributed-cache-service-in-sharepoint-server.md) + ## [Global architectures](articles/global-architectures-for-sharepoint-server-2016.md) + ## [Supporting the SharePoint mobile apps online and on-premises](articles/supporting-the-sharepoint-mobile-apps-online-and-on-premises.md) + ## [Records management planning](articles/plan-records-management-in-sharepoint-server-2013.md) + ## [Managing digital assets overview](articles/overview-of-managing-digital-assets-in-sharepoint-server-2013.md) + ## [Document management planning](articles/plan-document-management-in-sharepoint-2013.md) + ## [Mobile devices planning](articles/plan-for-mobile-devices-in-sharepoint-2013.md) +# [System requirements for SharePoint 2013](articles/system-requirements-for-sharepoint-2013.md) + ## [Hardware and software requirements](articles/hardware-and-software-requirements-for-sharepoint-2013.md) + ## [Browser support planning](articles/plan-browser-support-in-sharepoint-2013.md) + ## [IP support](articles/ip-support-in-sharepoint-2013.md) + ## [Software boundaries and limits](articles/software-boundaries-and-limits-for-sharepoint-2013.md) + ## [Capacity management and sizing overview](articles/capacity-management-and-sizing-overview-for-sharepoint-server-2013.md) +# [Hardware and software requirements](articles/hardware-and-software-requirements-for-sharepoint-2013.md) +# [Browser support planning](articles/plan-browser-support-in-sharepoint-2013.md) +# [IP support](articles/ip-support-in-sharepoint-2013.md) +# [Software boundaries and limits](articles/software-boundaries-and-limits-for-sharepoint-2013.md) +# [Capacity management and sizing overview](articles/capacity-management-and-sizing-overview-for-sharepoint-server-2013.md) +# [System requirements for SharePoint Server 2016](articles/system-requirements-for-sharepoint-server-2016.md) + ## [Hardware and software requirements](articles/hardware-and-software-requirements-for-sharepoint-server-2016.md) + ## [Browser support planning](articles/plan-browser-support-in-sharepoint-server-2016.md) + ## [Software boundaries and limits](articles/software-boundaries-and-limits-for-sharepoint-server-2016.md) +# [Hardware and software requirements](articles/hardware-and-software-requirements-for-sharepoint-server-2016.md) +# [Browser support planning](articles/plan-browser-support-in-sharepoint-server-2016.md) +# [Software boundaries and limits](articles/software-boundaries-and-limits-for-sharepoint-server-2016.md) +# [Planning for a MinRole server deployment in SharePoint Server 2016](articles/planning-for-a-minrole-server-deployment-in-sharepoint-server-2016.md) +# [Services and Application Planning](articles/services-and-application-planning-in-sharepoint-server-2016.md) + ## [Secure Store Service planning](articles/plan-the-secure-store-service-in-sharepoint-server.md) + ## [Visio Services planning](articles/plan-for-visio-services-in-sharepoint-server.md) + ## [PerformancePoint Services overview](articles/performancepoint-services-in-sharepoint-server-2016-overview.md) +# [Secure Store Service planning](articles/plan-the-secure-store-service-in-sharepoint-server.md) +# [Visio Services planning](articles/plan-for-visio-services-in-sharepoint-server.md) + ## [Visio Services overview](articles/overview-of-visio-services-in-sharepoint-server.md) + ## [Plan Visio Services deployment](articles/plan-visio-services-deployment-in-sharepoint-server.md) + ## [Visio Services security planning](articles/plan-visio-services-security-in-sharepoint-server.md) + ## [Data authentication for Visio Services](articles/data-authentication-for-visio-services-in-sharepoint-server.md) +# [Visio Services overview](articles/overview-of-visio-services-in-sharepoint-server.md) +# [Plan Visio Services deployment](articles/plan-visio-services-deployment-in-sharepoint-server.md) +# [Visio Services security planning](articles/plan-visio-services-security-in-sharepoint-server.md) +# [Data authentication for Visio Services](articles/data-authentication-for-visio-services-in-sharepoint-server.md) +# [PerformancePoint Services overview](articles/performancepoint-services-in-sharepoint-server-2016-overview.md) + ## [Overview of reports and scorecards](articles/overview-of-performancepoint-reports-and-scorecards.md) +# [Overview of reports and scorecards](articles/overview-of-performancepoint-reports-and-scorecards.md) + ## [Overview of strategy maps](articles/overview-of-performancepoint-strategy-maps.md) + ## [Overview of analytic charts and grids](articles/overview-of-performancepoint-analytic-charts-and-grids.md) + ## [Overview of KPI Details reports](articles/overview-of-performancepoint-kpi-details-reports.md) + ## [Overview of Reporting Services reports](articles/overview-of-reporting-services-reports-displayed-in-performancepoint-web-parts.md) + ## [Overview of Web Page reports](articles/overview-of-web-page-reports-in-dashboard-designer.md) + ## [Overview of the Decomposition Tree](articles/overview-of-the-performancepoint-decomposition-tree.md) + ## [Overview of PerformancePoint scorecards](articles/overview-of-performancepoint-scorecards.md) +# [Overview of strategy maps](articles/overview-of-performancepoint-strategy-maps.md) +# [Overview of analytic charts and grids](articles/overview-of-performancepoint-analytic-charts-and-grids.md) +# [Overview of KPI Details reports](articles/overview-of-performancepoint-kpi-details-reports.md) +# [Overview of Reporting Services reports](articles/overview-of-reporting-services-reports-displayed-in-performancepoint-web-parts.md) +# [Overview of Web Page reports](articles/overview-of-web-page-reports-in-dashboard-designer.md) +# [Overview of the Decomposition Tree](articles/overview-of-the-performancepoint-decomposition-tree.md) +# [Overview of PerformancePoint scorecards](articles/overview-of-performancepoint-scorecards.md) +# [Backup and recovery planning](articles/plan-for-backup-and-recovery-in-sharepoint-server.md) +# [Business intelligence overview](articles/business-intelligence-in-sharepoint-server-overview.md) + ## [Software requirements for business intelligence](articles/software-requirements-for-business-intelligence-in-sharepoint-server.md) + ## [Excel Services overview](articles/overview-of-excel-services-in-sharepoint-server-2013.md) +# [Software requirements for business intelligence](articles/software-requirements-for-business-intelligence-in-sharepoint-server.md) +# [Excel Services overview](articles/overview-of-excel-services-in-sharepoint-server-2013.md) + ## [BI capabilities in Excel and Excel Services](articles/business-intelligence-capabilities-in-excel-service-sharepoint-server-2013.md) + ## [Data authentication for Excel Services](articles/data-authentication-for-excel-services-in-sharepoint-server-2013.md) + ## [Data sources supported in Excel Services (SharePoint Server 2013)](articles/data-sources-supported-in-excel-services-sharepoint-server-2013.md) + ## [Plan Excel Services Global Settings](articles/plan-excel-services-global-settings-in-sharepoint-server-2013.md) + ## [Plan Trusted File Locations](articles/plan-trusted-file-locations-in-sharepoint-server-2013.md) + ## [Plan Trusted Data Connection Libraries](articles/plan-trusted-data-connection-libraries-in-sharepoint-server-2013.md) + ## [Plan Excel Services Data Model settings](articles/plan-excel-services-data-model-settings-in-sharepoint-server-2013.md) +# [BI capabilities in Excel and Excel Services](articles/business-intelligence-capabilities-in-excel-service-sharepoint-server-2013.md) +# [Data authentication for Excel Services](articles/data-authentication-for-excel-services-in-sharepoint-server-2013.md) +# [Data sources supported in Excel Services (SharePoint Server 2013)](articles/data-sources-supported-in-excel-services-sharepoint-server-2013.md) +# [Plan Excel Services Global Settings](articles/plan-excel-services-global-settings-in-sharepoint-server-2013.md) +# [Plan Trusted File Locations](articles/plan-trusted-file-locations-in-sharepoint-server-2013.md) +# [Plan Trusted Data Connection Libraries](articles/plan-trusted-data-connection-libraries-in-sharepoint-server-2013.md) +# [Plan Excel Services Data Model settings](articles/plan-excel-services-data-model-settings-in-sharepoint-server-2013.md) +# [User profiles and identities planning](articles/plan-user-profiles-and-identities.md) + ## [Profile synchronization in SharePoint Server 2013](articles/overview-of-profile-synchronization-in-sharepoint-server-2013.md) + ## [Profile synchronization in SharePoint Server 2016](articles/overview-of-profile-synchronization-in-sharepoint-server-2016.md) + ## [Plan profile synchronization for SharePoint Server 2013](articles/plan-profile-synchronization-for-sharepoint-server-2013.md) + ## [User Profile service architecture](articles/overview-of-the-user-profile-service-architecture-in-sharepoint-server.md) + ## [Plan user profiles](articles/plan-user-profiles-in-sharepoint-server.md) + ## [People Picker and claims providers overview](articles/people-picker-and-claims-providers-overview-sharepoint-2013.md) +# [Profile synchronization in SharePoint Server 2013](articles/overview-of-profile-synchronization-in-sharepoint-server-2013.md) +# [Profile synchronization in SharePoint Server 2016](articles/overview-of-profile-synchronization-in-sharepoint-server-2016.md) +# [Plan profile synchronization for SharePoint Server 2013](articles/plan-profile-synchronization-for-sharepoint-server-2013.md) +# [User Profile service architecture](articles/overview-of-the-user-profile-service-architecture-in-sharepoint-server.md) +# [Plan user profiles](articles/plan-user-profiles-in-sharepoint-server.md) +# [People Picker and claims providers overview](articles/people-picker-and-claims-providers-overview-sharepoint-2013.md) + ## [Plan for People Picker](articles/plan-for-people-picker-in-sharepoint-2013.md) + ## [Plan for custom claims providers for People Picker](articles/plan-for-custom-claims-providers-for-people-picker-in-sharepoint-2013.md) +# [Plan for People Picker](articles/plan-for-people-picker-in-sharepoint-2013.md) +# [Plan for custom claims providers for People Picker](articles/plan-for-custom-claims-providers-for-people-picker-in-sharepoint-2013.md) +# [Email integration planning](articles/plan-email-integration-for-a-sharepoint-server-2016-farm.md) + ## [Incoming email planning](articles/plan-incoming-email-for-a-sharepoint-server-2016-farm.md) + ## [Outgoing email planning](articles/plan-outgoing-email-for-a-sharepoint-server-2016-farm.md) +# [Incoming email planning](articles/plan-incoming-email-for-a-sharepoint-server-2016-farm.md) +# [Outgoing email planning](articles/plan-outgoing-email-for-a-sharepoint-server-2016-farm.md) +# [eDiscovery planning](articles/plan-ediscovery-in-sharepoint-server.md) + ## [Overview of eDiscovery and in-place holds](articles/overview-of-ediscovery-and-in-place-holds-in-sharepoint-server.md) + ## [Plan for eDiscovery](articles/plan-for-ediscovery-in-sharepoint-server.md) +# [Overview of eDiscovery and in-place holds](articles/overview-of-ediscovery-and-in-place-holds-in-sharepoint-server.md) +# [Plan for eDiscovery](articles/plan-for-ediscovery-in-sharepoint-server.md) +# [Governance Planning](articles/governance-planning-in-sharepoint-server-2016.md) + ## [What is governance in SharePoint?](articles/what-is-governance-in-sharepoint.md) + ## [IT governance in SharePoint](articles/it-governance-in-sharepoint.md) + ## [Application management and governance in SharePoint](articles/application-management-and-governance-in-sharepoint.md) + ## [Managed metadata planning](articles/plan-for-managed-metadata-in-sharepoint-server.md) + ## [How to use the Managed Solutions Gallery](articles/how-to-use-the-managed-solutions-gallery.md) +# [What is governance in SharePoint?](articles/what-is-governance-in-sharepoint.md) +# [IT governance in SharePoint](articles/it-governance-in-sharepoint.md) +# [Application management and governance in SharePoint](articles/application-management-and-governance-in-sharepoint.md) +# [Managed metadata planning](articles/plan-for-managed-metadata-in-sharepoint-server.md) +# [How to use the Managed Solutions Gallery](articles/how-to-use-the-managed-solutions-gallery.md) +# [Business Connectivity Services planning](articles/plan-for-business-connectivity-services-in-sharepoint-server.md) + ## [Business Connectivity Services overview](articles/overview-of-business-connectivity-services-in-sharepoint-server.md) + ## [Security tasks overview](articles/overview-of-business-connectivity-services-security-tasks-in-sharepoint-server.md) + ## [Plan a Business Connectivity Services solution](articles/plan-a-business-connectivity-services-solution-in-sharepoint-server.md) +# [Business Connectivity Services overview](articles/overview-of-business-connectivity-services-in-sharepoint-server.md) +# [Security tasks overview](articles/overview-of-business-connectivity-services-security-tasks-in-sharepoint-server.md) +# [Plan a Business Connectivity Services solution](articles/plan-a-business-connectivity-services-solution-in-sharepoint-server.md) +# [My Sites and OneDrive for Business planning](articles/plan-for-my-sites-and-onedrive-for-business-in-sharepoint-server.md) + ## [OneDrive for Business overview](articles/overview-of-onedrive-for-business-in-sharepoint-server.md) + ## [My Sites overview](articles/overview-of-my-sites-in-sharepoint-server.md) + ## [OneDrive for Business planning](articles/plan-for-onedrive-for-business-in-sharepoint-server.md) + ## [My Sites planning](articles/plan-for-my-sites-in-sharepoint-server.md) +# [OneDrive for Business overview](articles/overview-of-onedrive-for-business-in-sharepoint-server.md) +# [My Sites overview](articles/overview-of-my-sites-in-sharepoint-server.md) +# [OneDrive for Business planning](articles/plan-for-onedrive-for-business-in-sharepoint-server.md) +# [My Sites planning](articles/plan-for-my-sites-in-sharepoint-server.md) +# [Web content management planning](articles/plan-web-content-management-in-sharepoint-server.md) + ## [Overview of publishing to Internet, intranet, and extranet sites](articles/overview-of-publishing-to-internet-intranet-and-extranet-sites-in-sharepoint-ser.md) + ## [Plan for Internet, intranet, and extranet publishing sites](articles/plan-for-internet-intranet-and-extranet-publishing-sites-in-sharepoint-server.md) + ## [Plan for cross-site publishing](articles/plan-for-cross-site-publishing-in-sharepoint-server.md) + ## [Overview of managed navigation](articles/overview-of-managed-navigation-in-sharepoint-server.md) + ## [Plan navigation term sets](articles/plan-navigation-term-sets-in-sharepoint-server.md) + ## [Variations overview](articles/variations-overview-in-sharepoint-server.md) + ## [Plan for variations](articles/plan-for-variations-in-sharepoint-server.md) + ## [Caching and performance planning](articles/plan-for-caching-and-performance-in-sharepoint-server.md) +# [Overview of publishing to Internet, intranet, and extranet sites](articles/overview-of-publishing-to-internet-intranet-and-extranet-sites-in-sharepoint-ser.md) +# [Plan for Internet, intranet, and extranet publishing sites](articles/plan-for-internet-intranet-and-extranet-publishing-sites-in-sharepoint-server.md) +# [Plan for cross-site publishing](articles/plan-for-cross-site-publishing-in-sharepoint-server.md) + ## [Overview of cross-site publishing](articles/overview-of-cross-site-publishing-in-sharepoint-server.md) + ## [Plan the logical architecture for cross-site publishing](articles/plan-the-logical-architecture-for-cross-site-publishing-in-sharepoint-server.md) + ## [Plan SharePoint authoring sites for cross-site publishing](articles/plan-authoring-sites-for-cross-site-publishing-in-sharepoint-server.md) + ## [Plan SharePoint publishing sites for cross-site publishing](articles/plan-publishing-sites-for-cross-site-publishing-in-sharepoint-server.md) + ## [Plan search for SharePoint cross-site publishing sites](articles/plan-search-for-cross-site-publishing-sites-in-sharepoint-server-2016.md) + ## [Plan variations for multilingual cross-site publishing site](articles/plan-variations-for-multilingual-cross-site-publishing-site-in-sharepoint-server.md) +# [Overview of cross-site publishing](articles/overview-of-cross-site-publishing-in-sharepoint-server.md) +# [Plan the logical architecture for cross-site publishing](articles/plan-the-logical-architecture-for-cross-site-publishing-in-sharepoint-server.md) +# [Plan SharePoint authoring sites for cross-site publishing](articles/plan-authoring-sites-for-cross-site-publishing-in-sharepoint-server.md) +# [Plan SharePoint publishing sites for cross-site publishing](articles/plan-publishing-sites-for-cross-site-publishing-in-sharepoint-server.md) +# [Plan search for SharePoint cross-site publishing sites](articles/plan-search-for-cross-site-publishing-sites-in-sharepoint-server-2016.md) +# [Plan variations for multilingual cross-site publishing site](articles/plan-variations-for-multilingual-cross-site-publishing-site-in-sharepoint-server.md) +# [Overview of managed navigation](articles/overview-of-managed-navigation-in-sharepoint-server.md) +# [Plan navigation term sets](articles/plan-navigation-term-sets-in-sharepoint-server.md) +# [Variations overview](articles/variations-overview-in-sharepoint-server.md) +# [Plan for variations](articles/plan-for-variations-in-sharepoint-server.md) +# [Caching and performance planning](articles/plan-for-caching-and-performance-in-sharepoint-server.md) +# [Search planning](articles/plan-search-in-sharepoint-server.md) + ## [Search architecture overview](articles/overview-of-search-architecture-in-sharepoint-server.md) + ## [Plan enterprise search architecture](articles/plan-enterprise-search-architecture-in-sharepoint-server-2016.md) + ## [Scale enterprise search](articles/scale-enterprise-search-in-sharepoint-server.md) + ## [Scale search for Internet sites](articles/scale-search-for-internet-sites-in-sharepoint-server.md) + ## [Best practices for organizing content for search](articles/best-practices-for-organizing-content-for-search-in-sharepoint-server.md) + ## [Plan crawling and federation](articles/plan-crawling-and-federation-in-sharepoint-server.md) + ## [Search schema overview](articles/overview-of-the-search-schema-in-sharepoint-server.md) + ## [Understanding result sources for search](articles/understanding-result-sources-for-search-in-sharepoint-server.md) + ## [Plan to transform queries and order results](articles/plan-to-transform-queries-and-order-results-in-sharepoint-server.md) + ## [Overview of search result ranking](articles/overview-of-search-result-ranking-in-sharepoint-server.md) + ## [Overview of analytics processing](articles/overview-of-analytics-processing-in-sharepoint-server.md) +# [Search architecture overview](articles/overview-of-search-architecture-in-sharepoint-server.md) +# [Plan enterprise search architecture](articles/plan-enterprise-search-architecture-in-sharepoint-server-2016.md) +# [Scale enterprise search](articles/scale-enterprise-search-in-sharepoint-server.md) + ## [Redesign topology for more content and users](articles/redesign-enterprise-search-topology-for-more-content-and-users-in-sharepoint-201.md) + ## [Redesign for specific performance requirements](articles/redesign-enterprise-search-topology-for-specific-performance-requirements-in-sha.md) +# [Redesign topology for more content and users](articles/redesign-enterprise-search-topology-for-more-content-and-users-in-sharepoint-201.md) +# [Redesign for specific performance requirements](articles/redesign-enterprise-search-topology-for-specific-performance-requirements-in-sha.md) +# [Scale search for Internet sites](articles/scale-search-for-internet-sites-in-sharepoint-server.md) +# [Best practices for organizing content for search](articles/best-practices-for-organizing-content-for-search-in-sharepoint-server.md) +# [Plan crawling and federation](articles/plan-crawling-and-federation-in-sharepoint-server.md) +# [Search schema overview](articles/overview-of-the-search-schema-in-sharepoint-server.md) +# [Understanding result sources for search](articles/understanding-result-sources-for-search-in-sharepoint-server.md) +# [Plan to transform queries and order results](articles/plan-to-transform-queries-and-order-results-in-sharepoint-server.md) +# [Overview of search result ranking](articles/overview-of-search-result-ranking-in-sharepoint-server.md) +# [Overview of analytics processing](articles/overview-of-analytics-processing-in-sharepoint-server.md) +# [Permissions planning for sites and content](articles/permissions-planning-for-sites-and-content-in-sharepoint-server-2016.md) +# [Fundamental site planning](articles/fundamental-site-planning-in-sharepoint-server-2016.md) + ## [Sites and site collections overview](articles/overview-of-sites-and-site-collections-in-sharepoint-server.md) + ## [Plan sites and site collections](articles/plan-sites-and-site-collections-in-sharepoint-server.md) + ## [Plan self-service site creation](articles/plan-self-service-site-creation-in-sharepoint-server.md) + ## [Site policy overview](articles/overview-of-site-policies-in-sharepoint-server.md) + ## [Site navigation overview](articles/overview-of-site-navigation-in-sharepoint-server.md) + ## [Plan for multilingual sites](articles/plan-for-multilingual-sites-in-sharepoint-server.md) + ## [Plan for the multilingual user interface](articles/plan-for-the-multilingual-user-interface-in-sharepoint-server.md) + ## [Themes overview](articles/overview-of-themes-in-sharepoint-server.md) + ## [Plan site maintenance and management](articles/plan-for-site-maintenance-and-management-in-sharepoint-server.md) +# [Sites and site collections overview](articles/overview-of-sites-and-site-collections-in-sharepoint-server.md) +# [Plan sites and site collections](articles/plan-sites-and-site-collections-in-sharepoint-server.md) +# [Plan self-service site creation](articles/plan-self-service-site-creation-in-sharepoint-server.md) +# [Site policy overview](articles/overview-of-site-policies-in-sharepoint-server.md) +# [Site navigation overview](articles/overview-of-site-navigation-in-sharepoint-server.md) +# [Plan for multilingual sites](articles/plan-for-multilingual-sites-in-sharepoint-server.md) +# [Plan for the multilingual user interface](articles/plan-for-the-multilingual-user-interface-in-sharepoint-server.md) +# [Themes overview](articles/overview-of-themes-in-sharepoint-server.md) +# [Plan site maintenance and management](articles/plan-for-site-maintenance-and-management-in-sharepoint-server.md) +# [High availability and disaster recovery planning](articles/plan-for-high-availability-and-disaster-recovery-for-sharepoint-server.md) + ## [High availability and disaster recovery concepts](articles/high-availability-and-disaster-recovery-concepts-in-sharepoint-server.md) + ## [Plan for disaster recovery](articles/choose-a-disaster-recovery-strategy-for-sharepoint-server.md) + ## [Supported high availability and disaster recovery options for SharePoint databases](articles/supported-high-availability-and-disaster-recovery-options-for-sharepoint-databas.md) + ## [Plan for high availability](articles/create-a-high-availability-architecture-and-strategy-for-sharepoint-server.md) + ## [Disaster Recovery best practices for SharePoint Server and Access Services](articles/disaster-recovery-best-practices-for-sharepoint-server-and-access-services.md) +# [High availability and disaster recovery concepts](articles/high-availability-and-disaster-recovery-concepts-in-sharepoint-server.md) +# [Plan for disaster recovery](articles/choose-a-disaster-recovery-strategy-for-sharepoint-server.md) +# [Supported high availability and disaster recovery options for SharePoint databases](articles/supported-high-availability-and-disaster-recovery-options-for-sharepoint-databas.md) +# [Plan for high availability](articles/create-a-high-availability-architecture-and-strategy-for-sharepoint-server.md) +# [Disaster Recovery best practices for SharePoint Server and Access Services](articles/disaster-recovery-best-practices-for-sharepoint-server-and-access-services.md) +# [SQL Server and storage](articles/sql-server-and-storage-sharepoint-server.md) + ## [Overview of SQL Server in a SharePoint environment](articles/overview-of-sql-server-in-a-sharepoint-server-2016-environment.md) + ## [Storage and SQL Server capacity planning and configuration](articles/storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md) +# [Overview of SQL Server in a SharePoint environment](articles/overview-of-sql-server-in-a-sharepoint-server-2016-environment.md) +# [Storage and SQL Server capacity planning and configuration](articles/storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md) +# [Getting started with SharePoint Server 2013 workflow](articles/getting-started-with-sharepoint-server-2013-workflow.md) +# [Plan for feeds and the Distributed Cache service](articles/plan-for-feeds-and-the-distributed-cache-service-in-sharepoint-server.md) +# [Global architectures](articles/global-architectures-for-sharepoint-server-2016.md) +# [Supporting the SharePoint mobile apps online and on-premises](articles/supporting-the-sharepoint-mobile-apps-online-and-on-premises.md) +# [Records management planning](articles/plan-records-management-in-sharepoint-server-2013.md) + ## [Records management overview](articles/overview-of-records-management-in-sharepoint-server-2013.md) + ## [Create a file plan to manage records](articles/create-a-file-plan-to-manage-records-in-sharepoint-server-2013.md) + ## [Plan how records are collected](articles/plan-ways-to-convert-active-documents-to-records-in-sharepoint-server-2013.md) + ## [Use a records archive or manage records in place](articles/use-a-sharepoint-server-2013-records-archive-or-manage-records-in-place.md) +# [Records management overview](articles/overview-of-records-management-in-sharepoint-server-2013.md) +# [Create a file plan to manage records](articles/create-a-file-plan-to-manage-records-in-sharepoint-server-2013.md) +# [Plan how records are collected](articles/plan-ways-to-convert-active-documents-to-records-in-sharepoint-server-2013.md) +# [Use a records archive or manage records in place](articles/use-a-sharepoint-server-2013-records-archive-or-manage-records-in-place.md) +# [Managing digital assets overview](articles/overview-of-managing-digital-assets-in-sharepoint-server-2013.md) + ## [Plan digital asset libraries](articles/plan-digital-asset-libraries-in-sharepoint-server-2013.md) +# [Plan digital asset libraries](articles/plan-digital-asset-libraries-in-sharepoint-server-2013.md) +# [Document management planning](articles/plan-document-management-in-sharepoint-2013.md) + ## [Overview of document management](articles/overview-of-document-management-in-sharepoint-2013.md) + ## [Identify users and analyze document usage](articles/identify-users-and-analyze-document-usage-in-sharepoint-2013.md) + ## [Document library planning](articles/plan-document-libraries-in-sharepoint-2013.md) + ## [Content type and workflow planning](articles/plan-content-types-and-workflows-in-sharepoint-2013.md) + ## [Document set planning](articles/plan-document-sets-in-sharepoint-server-2013.md) + ## [Information management policy planning](articles/plan-for-information-management-policy-in-sharepoint-server-2013.md) + ## [Versioning, content approval, and check-out planning](articles/plan-document-versioning-content-approval-and-check-out-controls-in-sharepoint-2.md) + ## [Co-authoring administration](articles/co-authoring-administration-in-sharepoint-2013.md) +# [Overview of document management](articles/overview-of-document-management-in-sharepoint-2013.md) +# [Identify users and analyze document usage](articles/identify-users-and-analyze-document-usage-in-sharepoint-2013.md) +# [Document library planning](articles/plan-document-libraries-in-sharepoint-2013.md) +# [Content type and workflow planning](articles/plan-content-types-and-workflows-in-sharepoint-2013.md) +# [Document set planning](articles/plan-document-sets-in-sharepoint-server-2013.md) +# [Information management policy planning](articles/plan-for-information-management-policy-in-sharepoint-server-2013.md) +# [Versioning, content approval, and check-out planning](articles/plan-document-versioning-content-approval-and-check-out-controls-in-sharepoint-2.md) +# [Co-authoring administration](articles/co-authoring-administration-in-sharepoint-2013.md) + ## [Co-authoring overview](articles/overview-of-co-authoring-in-sharepoint-2013.md) + ## [Configure versioning for co-authoring](articles/configure-versioning-for-co-authoring-in-sharepoint-2013.md) + ## [Configure the co-authoring versioning period](articles/configure-the-co-authoring-versioning-period-in-sharepoint-2013.md) + ## [Configure the maximum number of co-authoring authors](articles/configure-the-maximum-number-of-co-authoring-authors-in-sharepoint-2013.md) + ## [Disable co-authoring](articles/disable-co-authoring-in-sharepoint-2013.md) +# [Co-authoring overview](articles/overview-of-co-authoring-in-sharepoint-2013.md) +# [Configure versioning for co-authoring](articles/configure-versioning-for-co-authoring-in-sharepoint-2013.md) +# [Configure the co-authoring versioning period](articles/configure-the-co-authoring-versioning-period-in-sharepoint-2013.md) +# [Configure the maximum number of co-authoring authors](articles/configure-the-maximum-number-of-co-authoring-authors-in-sharepoint-2013.md) +# [Disable co-authoring](articles/disable-co-authoring-in-sharepoint-2013.md) +# [Mobile devices planning](articles/plan-for-mobile-devices-in-sharepoint-2013.md) + ## [Mobile devices overview](articles/overview-of-mobile-devices-and-sharepoint-server-2013.md) + ## [Plan for mobile views](articles/plan-for-mobile-views-in-sharepoint-server-2013.md) + ## [Supported mobile device browsers](articles/mobile-device-browsers-supported-in-sharepoint-2013.md) + ## [Mobile security and authentication](articles/mobile-security-and-authentication-in-sharepoint-2013.md) + ## [Authentication for mobile devices](articles/authentication-for-mobile-devices-in-sharepoint-2013.md) +# [Mobile devices overview](articles/overview-of-mobile-devices-and-sharepoint-server-2013.md) +# [Plan for mobile views](articles/plan-for-mobile-views-in-sharepoint-server-2013.md) +# [Supported mobile device browsers](articles/mobile-device-browsers-supported-in-sharepoint-2013.md) +# [Mobile security and authentication](articles/mobile-security-and-authentication-in-sharepoint-2013.md) +# [Authentication for mobile devices](articles/authentication-for-mobile-devices-in-sharepoint-2013.md) +# [Install and configure](articles/install-and-configure-sharepoint-server-2016.md) + ## [Install for SharePoint Server 2016](articles/install-sharepoint-server-2016.md) + ## [Prepare for installation](articles/prepare-for-installation-of-sharepoint-server-2016.md) + ## [Configure](articles/configure-sharepoint-server-2016.md) + ## [Install and manage apps for SharePoint Server](articles/install-and-manage-apps-for-sharepoint-server.md) + ## [Upgrade to SharePoint Server 2016](articles/upgrade-to-sharepoint-server-2016.md) + ## [Deploy updates for SharePoint Server 2016](articles/deploy-software-updates-for-sharepoint-server-2016.md) + ## [Test and troubleshoot an upgrade](articles/test-and-troubleshoot-an-upgrade-to-sharepoint-server-2016.md) + ## [Configure SQL Server security for SharePoint environments](articles/configure-sql-server-security-for-sharepoint-server-2016.md) + ## [SharePoint Server 2016 in Microsoft Azure](articles/sharepoint-server-2016-in-microsoft-azure.md) + ## [Microsoft Identity Manager in SharePoint Server 2016](articles/microsoft-identity-manager-in-sharepoint-server-2016.md) +# [Install for SharePoint Server 2016](articles/install-sharepoint-server-2016.md) + ## [Single server with SQL Server](articles/install-sharepoint-server-2016-on-a-single-server-with-sql-server.md) + ## [Install SharePoint Server 2016 across multiple servers](articles/install-sharepoint-server-2016-across-multiple-servers.md) + ## [Install or uninstall language packs](articles/install-or-uninstall-language-packs-for-sharepoint-server-2016.md) + ## [Add SharePoint server to a farm in SharePoint Server 2016](articles/add-sharepoint-server-to-a-farm-in-sharepoint-server-2016.md) + ## [Remove a server from the farm](articles/remove-a-server-from-a-farm-in-sharepoint-server-2016.md) + ## [Uninstall SharePoint Server 2016](articles/uninstall-sharepoint-server-2016.md) +# [Single server with SQL Server](articles/install-sharepoint-server-2016-on-a-single-server-with-sql-server.md) +# [Install SharePoint Server 2016 across multiple servers](articles/install-sharepoint-server-2016-across-multiple-servers.md) +# [Install or uninstall language packs](articles/install-or-uninstall-language-packs-for-sharepoint-server-2016.md) +# [Add SharePoint server to a farm in SharePoint Server 2016](articles/add-sharepoint-server-to-a-farm-in-sharepoint-server-2016.md) +# [Remove a server from the farm](articles/remove-a-server-from-a-farm-in-sharepoint-server-2016.md) +# [Uninstall SharePoint Server 2016](articles/uninstall-sharepoint-server-2016.md) +# [Prepare for installation](articles/prepare-for-installation-of-sharepoint-server-2016.md) + ## [Initial deployment administrative and service accounts in SharePoint Server](articles/initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md) + ## [Account permissions and security settings](articles/account-permissions-and-security-settings-in-sharepoint-server-2016.md) + ## [Install prerequisites from network share](articles/install-prerequisites-for-sharepoint-server-from-a-network-share.md) +# [Initial deployment administrative and service accounts in SharePoint Server](articles/initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md) +# [Account permissions and security settings](articles/account-permissions-and-security-settings-in-sharepoint-server-2016.md) +# [Install prerequisites from network share](articles/install-prerequisites-for-sharepoint-server-from-a-network-share.md) +# [Configure](articles/configure-sharepoint-server-2016.md) + ## [Configure services and service applications](articles/configure-services-and-service-applications-in-sharepoint-server.md) + ## [Configure My Sites and OneDrive for Business](articles/configure-my-sites-and-onedrive-for-business-in-sharepoint-server.md) + ## [Configure search](articles/configure-enterprise-search-in-sharepoint-server-2016.md) + ## [Configure eDiscovery](articles/configure-ediscovery-in-sharepoint-server.md) + ## [Manage the Distributed Cache service](articles/manage-the-distributed-cache-service-in-sharepoint-server.md) + ## [Custom Tiles in SharePoint Server 2016](articles/custom-tiles-in-sharepoint-server-2016.md) + ## [Configure availability and recovery solutions](articles/configure-availability-and-recovery-solutions-for-sharepoint-server-2016.md) + ## [Configure email integration](articles/configure-email-integration-for-a-sharepoint-server-farm.md) + ## [Configure site mailboxes in SharePoint](articles/configure-site-mailboxes-in-sharepoint-server.md) + ## [Turn on automated document translation](articles/turn-on-automated-document-translation-in-sharepoint-server-2016.md) + ## [Configure Business Connectivity Services solutions](articles/configure-business-connectivity-services-solutions-for-sharepoint-server.md) + ## [Configure workflow in SharePoint Server 2013](articles/configure-workflow-in-sharepoint-server-2013.md) +# [Configure services and service applications](articles/configure-services-and-service-applications-in-sharepoint-server.md) + ## [Configure the Managed Metadata service](articles/configure-the-managed-metadata-service.md) + ## [Configure the Secure Store Service](articles/configure-the-secure-store-service-in-sharepoint-server.md) + ## [Configure a Business Data Connectivity service application](articles/configure-a-business-data-connectivity-service-application-in-sharepoint-server.md) + ## [Configure Visio Services](articles/configure-visio-services.md) + ## [Configure PerformancePoint Services](articles/configure-performancepoint-services.md) +# [Configure the Managed Metadata service](articles/configure-the-managed-metadata-service.md) +# [Configure the Secure Store Service](articles/configure-the-secure-store-service-in-sharepoint-server.md) +# [Configure a Business Data Connectivity service application](articles/configure-a-business-data-connectivity-service-application-in-sharepoint-server.md) +# [Configure Visio Services](articles/configure-visio-services.md) +# [Configure PerformancePoint Services](articles/configure-performancepoint-services.md) +# [Configure My Sites and OneDrive for Business](articles/configure-my-sites-and-onedrive-for-business-in-sharepoint-server.md) + ## [Configure My Sites](articles/configure-my-sites-in-sharepoint-server.md) + ## [Set up OneDrive for Business](articles/set-up-onedrive-for-business-in-a-sharepoint-server-on-premises-environment.md) +# [Configure My Sites](articles/configure-my-sites-in-sharepoint-server.md) +# [Set up OneDrive for Business](articles/set-up-onedrive-for-business-in-a-sharepoint-server-on-premises-environment.md) + ## [Configure the OneDrive for Business modern user experience](articles/configure-the-onedrive-for-business-modern-user-experience.md) +# [Configure the OneDrive for Business modern user experience](articles/configure-the-onedrive-for-business-modern-user-experience.md) +# [Configure search](articles/configure-enterprise-search-in-sharepoint-server-2016.md) + ## [Create and configure a Search service application](articles/create-and-configure-a-search-service-application-in-sharepoint-server-2016.md) + ## [Create a Search Center site](articles/create-a-search-center-site-in-sharepoint-server.md) + ## [Deploy people search](articles/deploy-people-search-in-sharepoint-server.md) +# [Create and configure a Search service application](articles/create-and-configure-a-search-service-application-in-sharepoint-server-2016.md) +# [Create a Search Center site](articles/create-a-search-center-site-in-sharepoint-server.md) +# [Deploy people search](articles/deploy-people-search-in-sharepoint-server.md) +# [Configure eDiscovery](articles/configure-ediscovery-in-sharepoint-server.md) +# [Manage the Distributed Cache service](articles/manage-the-distributed-cache-service-in-sharepoint-server.md) +# [Custom Tiles in SharePoint Server 2016](articles/custom-tiles-in-sharepoint-server-2016.md) +# [Configure availability and recovery solutions](articles/configure-availability-and-recovery-solutions-for-sharepoint-server-2016.md) + ## [Configure an AlwaysOn Availability Group](articles/configure-sql-server-alwayson-availability-groups-for-sharepoint-server-2016.md) +# [Configure an AlwaysOn Availability Group](articles/configure-sql-server-alwayson-availability-groups-for-sharepoint-server-2016.md) +# [Configure email integration](articles/configure-email-integration-for-a-sharepoint-server-farm.md) + ## [Incoming email configuration](articles/configure-incoming-email-for-a-sharepoint-server-farm.md) + ## [Outgoing email configuration](articles/configure-outgoing-email-for-a-sharepoint-server-farm.md) +# [Incoming email configuration](articles/configure-incoming-email-for-a-sharepoint-server-farm.md) +# [Outgoing email configuration](articles/configure-outgoing-email-for-a-sharepoint-server-farm.md) +# [Configure site mailboxes in SharePoint](articles/configure-site-mailboxes-in-sharepoint-server.md) +# [Turn on automated document translation](articles/turn-on-automated-document-translation-in-sharepoint-server-2016.md) +# [Configure Business Connectivity Services solutions](articles/configure-business-connectivity-services-solutions-for-sharepoint-server.md) + ## [Deploy an on-premises solution](articles/deploy-a-business-connectivity-services-on-premises-solution-in-sharepoint-serve.md) +# [Deploy an on-premises solution](articles/deploy-a-business-connectivity-services-on-premises-solution-in-sharepoint-serve.md) +# [Configure workflow in SharePoint Server 2013](articles/configure-workflow-in-sharepoint-server-2013.md) + ## [Install and configure workflow for SharePoint Server 2013](articles/install-and-configure-workflow-for-sharepoint-server-2013.md) + ## [Install Workflow Manager certificates in SharePoint Server 2013](articles/install-workflow-manager-certificates-in-sharepoint-server-2013.md) + ## [Video series: Install and configure Workflow in SharePoint Server 2013](articles/video-series-install-and-configure-workflow-in-sharepoint-server-2013.md) + ## [Update Workflow in SharePoint Server 2013](articles/update-workflow-in-sharepoint-server-2013.md) +# [Install and configure workflow for SharePoint Server 2013](articles/install-and-configure-workflow-for-sharepoint-server-2013.md) +# [Install Workflow Manager certificates in SharePoint Server 2013](articles/install-workflow-manager-certificates-in-sharepoint-server-2013.md) +# [Video series: Install and configure Workflow in SharePoint Server 2013](articles/video-series-install-and-configure-workflow-in-sharepoint-server-2013.md) +# [Update Workflow in SharePoint Server 2013](articles/update-workflow-in-sharepoint-server-2013.md) +# [Install and manage apps for SharePoint Server](articles/install-and-manage-apps-for-sharepoint-server.md) + ## [Plan for apps for SharePoint](articles/plan-for-apps-for-sharepoint-server.md) + ## [Configure an environment for apps for SharePoint](articles/configure-an-environment-for-apps-for-sharepoint-server.md) + ## [Manage the App Catalog](articles/manage-the-app-catalog-in-sharepoint-server.md) + ## [Add apps for SharePoint to a SharePoint site](articles/add-apps-for-sharepoint-to-a-sharepoint-site.md) + ## [Remove app for SharePoint instances from a SharePoint site](articles/remove-app-for-sharepoint-instances-from-a-sharepoint-site.md) + ## [Monitor apps for SharePoint](articles/monitor-apps-for-sharepoint-for-sharepoint-server.md) + ## [Monitor and manage app licenses](articles/monitor-and-manage-app-licenses-in-sharepoint-server.md) +# [Plan for apps for SharePoint](articles/plan-for-apps-for-sharepoint-server.md) +# [Configure an environment for apps for SharePoint](articles/configure-an-environment-for-apps-for-sharepoint-server.md) +# [Manage the App Catalog](articles/manage-the-app-catalog-in-sharepoint-server.md) +# [Add apps for SharePoint to a SharePoint site](articles/add-apps-for-sharepoint-to-a-sharepoint-site.md) +# [Remove app for SharePoint instances from a SharePoint site](articles/remove-app-for-sharepoint-instances-from-a-sharepoint-site.md) +# [Monitor apps for SharePoint](articles/monitor-apps-for-sharepoint-for-sharepoint-server.md) +# [Monitor and manage app licenses](articles/monitor-and-manage-app-licenses-in-sharepoint-server.md) +# [Upgrade to SharePoint Server 2016](articles/upgrade-to-sharepoint-server-2016.md) + ## [Get started with upgrade](articles/get-started-with-upgrades-to-sharepoint-server-2016.md) + ## [Upgrade databases](articles/upgrade-databases-from-sharepoint-2013-to-sharepoint-server-2016.md) + ## [Upgrade site collections](articles/upgrade-site-collections-to-sharepoint-server-2016.md) + ## [Video: Cleanup of databases after upgrade procedure](articles/video-cleanup-of-databases-after-upgrade-procedure.md) +# [Get started with upgrade](articles/get-started-with-upgrades-to-sharepoint-server-2016.md) + ## [Overview of the upgrade process](articles/overview-of-the-upgrade-process-to-sharepoint-server-2016.md) + ## [Overview of the services upgrade process](articles/services-upgrade-overview-for-sharepoint-server-2016.md) + ## [Best practices for upgrade](articles/best-practices-for-upgrading-to-sharepoint-server-2016.md) +# [Overview of the upgrade process](articles/overview-of-the-upgrade-process-to-sharepoint-server-2016.md) +# [Overview of the services upgrade process](articles/services-upgrade-overview-for-sharepoint-server-2016.md) +# [Best practices for upgrade](articles/best-practices-for-upgrading-to-sharepoint-server-2016.md) +# [Upgrade databases](articles/upgrade-databases-from-sharepoint-2013-to-sharepoint-server-2016.md) + ## [Create the SharePoint Server 2016 farm for a database attach upgrade](articles/create-the-sharepoint-server-2016-farm-for-a-database-attach-upgrade.md) + ## [Copy databases to the new farm for upgrade to SharePoint Server 2016](articles/copy-databases-to-the-new-farm-for-upgrade-to-sharepoint-server-2016.md) + ## [Upgrade service applications to SharePoint Server 2016](articles/upgrade-service-applications-to-sharepoint-server-2016.md) + ## [Upgrade content databases](articles/upgrade-content-databases-to-sharepoint-server-2016.md) + ## [Verify upgrade for databases](articles/verify-database-upgrades-in-sharepoint-server-2016.md) +# [Create the SharePoint Server 2016 farm for a database attach upgrade](articles/create-the-sharepoint-server-2016-farm-for-a-database-attach-upgrade.md) +# [Copy databases to the new farm for upgrade to SharePoint Server 2016](articles/copy-databases-to-the-new-farm-for-upgrade-to-sharepoint-server-2016.md) +# [Upgrade service applications to SharePoint Server 2016](articles/upgrade-service-applications-to-sharepoint-server-2016.md) +# [Upgrade content databases](articles/upgrade-content-databases-to-sharepoint-server-2016.md) +# [Verify upgrade for databases](articles/verify-database-upgrades-in-sharepoint-server-2016.md) +# [Upgrade site collections](articles/upgrade-site-collections-to-sharepoint-server-2016.md) + ## [Upgrade a site collection](articles/upgrade-a-site-collection-to-sharepoint-server-2016.md) + ## [Upgrade My Sites](articles/upgrade-my-sites-to-sharepoint-server-2016.md) +# [Upgrade a site collection](articles/upgrade-a-site-collection-to-sharepoint-server-2016.md) +# [Upgrade My Sites](articles/upgrade-my-sites-to-sharepoint-server-2016.md) +# [Video: Cleanup of databases after upgrade procedure](articles/video-cleanup-of-databases-after-upgrade-procedure.md) +# [Deploy updates for SharePoint Server 2016](articles/deploy-software-updates-for-sharepoint-server-2016.md) + ## [Software updates overview](articles/software-updates-overview-for-sharepoint-server-2016.md) + ## [Install a software update](articles/install-a-software-update-for-sharepoint-server-2016.md) + ## [Video demo of Zero Downtime Patching in SharePoint Server 2016](articles/video-demo-of-zero-downtime-patching-in-sharepoint-server-2016.md) + ## [SharePoint Server 2016 zero downtime patching steps](articles/sharepoint-server-2016-zero-downtime-patching-steps.md) + ## [Video: How to enable Remote Windows PowerShell to use with SharePoint Server](articles/video-how-to-enable-remote-windows-powershell-to-use-with-sharepoint-server.md) +# [Software updates overview](articles/software-updates-overview-for-sharepoint-server-2016.md) +# [Install a software update](articles/install-a-software-update-for-sharepoint-server-2016.md) +# [Video demo of Zero Downtime Patching in SharePoint Server 2016](articles/video-demo-of-zero-downtime-patching-in-sharepoint-server-2016.md) +# [SharePoint Server 2016 zero downtime patching steps](articles/sharepoint-server-2016-zero-downtime-patching-steps.md) +# [Video: How to enable Remote Windows PowerShell to use with SharePoint Server](articles/video-how-to-enable-remote-windows-powershell-to-use-with-sharepoint-server.md) +# [Test and troubleshoot an upgrade](articles/test-and-troubleshoot-an-upgrade-to-sharepoint-server-2016.md) + ## [Troubleshoot site collection upgrade issues](articles/troubleshoot-site-collection-upgrade-issues-in-sharepoint-server-2016.md) +# [Troubleshoot site collection upgrade issues](articles/troubleshoot-site-collection-upgrade-issues-in-sharepoint-server-2016.md) +# [Configure SQL Server security for SharePoint environments](articles/configure-sql-server-security-for-sharepoint-server-2016.md) +# [SharePoint Server 2016 in Microsoft Azure](articles/sharepoint-server-2016-in-microsoft-azure.md) + ## [SharePoint Server 2016 dev/test environment in Azure](articles/sharepoint-server-2016-dev-test-environment-in-azure.md) + ## [Intranet SharePoint Server 2016 in Azure dev/test environment](articles/intranet-sharepoint-server-2016-in-azure-dev-test-environment.md) + ## [Designing a SharePoint Server 2016 farm in Azure](articles/designing-a-sharepoint-server-2016-farm-in-azure.md) + ## [Deploying SharePoint Server 2016 with SQL Server AlwaysOn Availability Groups in Azure](articles/deploying-sharepoint-server-2016-with-sql-server-alwayson-availability-groups-in.md) +# [SharePoint Server 2016 dev/test environment in Azure](articles/sharepoint-server-2016-dev-test-environment-in-azure.md) +# [Intranet SharePoint Server 2016 in Azure dev/test environment](articles/intranet-sharepoint-server-2016-in-azure-dev-test-environment.md) +# [Designing a SharePoint Server 2016 farm in Azure](articles/designing-a-sharepoint-server-2016-farm-in-azure.md) +# [Deploying SharePoint Server 2016 with SQL Server AlwaysOn Availability Groups in Azure](articles/deploying-sharepoint-server-2016-with-sql-server-alwayson-availability-groups-in.md) + ## [SharePoint Intranet Farm in Azure Phase 1: Configure Azure](articles/sharepoint-intranet-farm-in-azure-phase-1-configure-azure.md) + ## [SharePoint Intranet Farm in Azure Phase 2: Configure domain controllers](articles/sharepoint-intranet-farm-in-azure-phase-2-configure-domain-controllers.md) + ## [SharePoint Intranet Farm in Azure Phase 3: Configure SQL Server Infrastructure](articles/sharepoint-intranet-farm-in-azure-phase-3-configure-sql-server-infrastructure.md) + ## [SharePoint Intranet Farm in Azure Phase 4: Configure SharePoint servers](articles/sharepoint-intranet-farm-in-azure-phase-4-configure-sharepoint-servers.md) + ## [SharePoint Intranet Farm in Azure Phase 5: Create the availability group and add the SharePoint databases](articles/sharepoint-intranet-farm-in-azure-phase-5-create-the-availability-group-and-add.md) +# [SharePoint Intranet Farm in Azure Phase 1: Configure Azure](articles/sharepoint-intranet-farm-in-azure-phase-1-configure-azure.md) +# [SharePoint Intranet Farm in Azure Phase 2: Configure domain controllers](articles/sharepoint-intranet-farm-in-azure-phase-2-configure-domain-controllers.md) +# [SharePoint Intranet Farm in Azure Phase 3: Configure SQL Server Infrastructure](articles/sharepoint-intranet-farm-in-azure-phase-3-configure-sql-server-infrastructure.md) +# [SharePoint Intranet Farm in Azure Phase 4: Configure SharePoint servers](articles/sharepoint-intranet-farm-in-azure-phase-4-configure-sharepoint-servers.md) +# [SharePoint Intranet Farm in Azure Phase 5: Create the availability group and add the SharePoint databases](articles/sharepoint-intranet-farm-in-azure-phase-5-create-the-availability-group-and-add.md) +# [Microsoft Identity Manager in SharePoint Server 2016](articles/microsoft-identity-manager-in-sharepoint-server-2016.md) + ## [Install Microsoft Identity Manager for User Profiles in SharePoint Server 2016](articles/install-microsoft-identity-manager-for-user-profiles-in-sharepoint-server-2016.md) + ## [Overview of Microsoft Identity Manager Synchronization Service in SharePoint Server 2016](articles/overview-of-microsoft-identity-manager-synchronization-service-in-sharepoint-ser.md) + ## [Deployment considerations for implementing Microsoft Identity Manager with SharePoint Server 2016](articles/deployment-considerations-for-implementing-microsoft-identity-manager-with-share.md) +# [Install Microsoft Identity Manager for User Profiles in SharePoint Server 2016](articles/install-microsoft-identity-manager-for-user-profiles-in-sharepoint-server-2016.md) + ## [Use a sample MIM solution in SharePoint Server 2016](articles/use-a-sample-mim-solution-in-sharepoint-server-2016.md) +# [Use a sample MIM solution in SharePoint Server 2016](articles/use-a-sample-mim-solution-in-sharepoint-server-2016.md) +# [Overview of Microsoft Identity Manager Synchronization Service in SharePoint Server 2016](articles/overview-of-microsoft-identity-manager-synchronization-service-in-sharepoint-ser.md) +# [Deployment considerations for implementing Microsoft Identity Manager with SharePoint Server 2016](articles/deployment-considerations-for-implementing-microsoft-identity-manager-with-share.md) +# [Operate and maintain](articles/operations-for-sharepoint-server.md) + ## [Backup and restore](articles/backup-and-restore-in-sharepoint-server.md) + ## [Database management](articles/manage-databases-in-sharepoint-server.md) + ## [Service application and service management](articles/service-application-and-service-management-in-sharepoint-server.md) + ## [Health monitoring and reporting](articles/monitoring-and-reporting-in-sharepoint-server.md) + ## [Web applications management](articles/web-applications-management-in-sharepoint-server.md) + ## [Description of MinRole and associated services in SharePoint Server 2016](articles/description-of-minrole-and-associated-services-in-sharepoint-server-2016.md) + ## [Managing a MinRole Server Farm in SharePoint Server 2016](articles/managing-a-minrole-server-farm-in-sharepoint-server-2016.md) + ## [Role conversion using MinRole in SharePoint Server 2016](articles/role-conversion-using-minrole-in-sharepoint-server-2016.md) + ## [Site and site collection administration](articles/administer-sites-and-site-collections-in-sharepoint-server.md) + ## [Search administration](articles/administer-search-in-sharepoint-server.md) + ## [Business intelligence administration](articles/administer-business-intelligence-in-sharepoint-server.md) + ## [User Profile service administration](articles/administer-the-user-profile-service-in-sharepoint-server.md) +# [Backup and restore](articles/backup-and-restore-in-sharepoint-server.md) + ## [Backup and recovery overview](articles/overview-of-backup-and-recovery-in-sharepoint-server.md) + ## [Prepare to back up and restore](articles/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md) + ## [Configure permissions for backup and restore](articles/configure-backup-and-restore-permissions-in-sharepoint-server.md) + ## [Backup](articles/backup-solutions-in-sharepoint-server.md) + ## [Restore](articles/restore-solutions-in-sharepoint-server.md) + ## [Best practices for backup and restore](articles/backup-and-restore-best-practices-in-sharepoint-server.md) +# [Backup and recovery overview](articles/overview-of-backup-and-recovery-in-sharepoint-server.md) +# [Prepare to back up and restore](articles/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md) +# [Configure permissions for backup and restore](articles/configure-backup-and-restore-permissions-in-sharepoint-server.md) +# [Backup](articles/backup-solutions-in-sharepoint-server.md) + ## [Back up a farm](articles/back-up-farms-in-sharepoint-server.md) + ## [Back up a farm configuration](articles/back-up-farm-configurations-in-sharepoint-server.md) + ## [Back up a web application](articles/back-up-web-applications-in-sharepoint-server.md) + ## [Back up a service application](articles/back-up-service-applications-in-sharepoint-server.md) + ## [Back up a User Profile Service application](articles/back-up-user-profile-service-applications-in-sharepoint-server.md) + ## [Back up a Search service application](articles/back-up-search-service-applications-in-sharepoint-server.md) + ## [Back up the Secure Store Service](articles/back-up-the-secure-store-service-in-sharepoint-server.md) + ## [Back up a content database](articles/back-up-content-databases-in-sharepoint-server.md) + ## [Back up databases to snapshots](articles/back-up-databases-to-snapshots-in-sharepoint-server.md) + ## [Back up customizations](articles/back-up-customizations-in-sharepoint-server.md) + ## [Back up site collections](articles/back-up-site-collections-in-sharepoint-server.md) + ## [Back up apps for SharePoint](articles/back-up-apps-for-sharepoint-in-sharepoint-server.md) + ## [Export a site, list, or document library](articles/export-sites-lists-or-document-libraries-in-sharepoint-server.md) +# [Back up a farm](articles/back-up-farms-in-sharepoint-server.md) +# [Back up a farm configuration](articles/back-up-farm-configurations-in-sharepoint-server.md) +# [Back up a web application](articles/back-up-web-applications-in-sharepoint-server.md) +# [Back up a service application](articles/back-up-service-applications-in-sharepoint-server.md) +# [Back up a User Profile Service application](articles/back-up-user-profile-service-applications-in-sharepoint-server.md) +# [Back up a Search service application](articles/back-up-search-service-applications-in-sharepoint-server.md) +# [Back up the Secure Store Service](articles/back-up-the-secure-store-service-in-sharepoint-server.md) +# [Back up a content database](articles/back-up-content-databases-in-sharepoint-server.md) +# [Back up databases to snapshots](articles/back-up-databases-to-snapshots-in-sharepoint-server.md) +# [Back up customizations](articles/back-up-customizations-in-sharepoint-server.md) +# [Back up site collections](articles/back-up-site-collections-in-sharepoint-server.md) +# [Back up apps for SharePoint](articles/back-up-apps-for-sharepoint-in-sharepoint-server.md) +# [Export a site, list, or document library](articles/export-sites-lists-or-document-libraries-in-sharepoint-server.md) +# [Restore](articles/restore-solutions-in-sharepoint-server.md) + ## [Restore a farm](articles/restore-farms-in-sharepoint-server.md) + ## [Restore a farm configuration](articles/restore-farm-configurations-in-sharepoint-server.md) + ## [Document farm configuration settings](articles/document-farm-configuration-settings-in-sharepoint-server.md) + ## [Copy configuration settings between farms](articles/copy-configuration-settings-between-farms-in-sharepoint-server.md) + ## [Restore a web application](articles/restore-web-applications-in-sharepoint-server.md) + ## [Restore a service application](articles/restore-service-applications-in-sharepoint-server.md) + ## [Restore a User Profile Service application](articles/restore-user-profile-service-applications-in-sharepoint-server.md) + ## [Restore a Search service application](articles/restore-search-service-applications-in-sharepoint-server.md) + ## [Restore a Secure Store Service application](articles/restore-secure-store-service-applications-in-sharepoint-server.md) + ## [Restore a content database](articles/restore-content-databases-in-sharepoint-server.md) + ## [Attach and restore a read-only content database](articles/attach-and-restore-read-only-content-databases-in-sharepoint-server.md) + ## [Restore content from an unattached content database](articles/restore-content-from-unattached-content-databases-in-sharepoint-server.md) + ## [Restore customizations](articles/restore-customizations-in-sharepoint-server.md) + ## [Restore site collections](articles/restore-site-collections-in-sharepoint-server.md) + ## [Restore apps for SharePoint](articles/restore-apps-for-sharepoint-in-sharepoint-server.md) + ## [Import a list or document library](articles/import-a-list-or-document-library-in-sharepoint-server.md) +# [Restore a farm](articles/restore-farms-in-sharepoint-server.md) +# [Restore a farm configuration](articles/restore-farm-configurations-in-sharepoint-server.md) +# [Document farm configuration settings](articles/document-farm-configuration-settings-in-sharepoint-server.md) +# [Copy configuration settings between farms](articles/copy-configuration-settings-between-farms-in-sharepoint-server.md) +# [Restore a web application](articles/restore-web-applications-in-sharepoint-server.md) +# [Restore a service application](articles/restore-service-applications-in-sharepoint-server.md) +# [Restore a User Profile Service application](articles/restore-user-profile-service-applications-in-sharepoint-server.md) +# [Restore a Search service application](articles/restore-search-service-applications-in-sharepoint-server.md) +# [Restore a Secure Store Service application](articles/restore-secure-store-service-applications-in-sharepoint-server.md) +# [Restore a content database](articles/restore-content-databases-in-sharepoint-server.md) +# [Attach and restore a read-only content database](articles/attach-and-restore-read-only-content-databases-in-sharepoint-server.md) +# [Restore content from an unattached content database](articles/restore-content-from-unattached-content-databases-in-sharepoint-server.md) +# [Restore customizations](articles/restore-customizations-in-sharepoint-server.md) +# [Restore site collections](articles/restore-site-collections-in-sharepoint-server.md) +# [Restore apps for SharePoint](articles/restore-apps-for-sharepoint-in-sharepoint-server.md) +# [Import a list or document library](articles/import-a-list-or-document-library-in-sharepoint-server.md) +# [Best practices for backup and restore](articles/backup-and-restore-best-practices-in-sharepoint-server.md) +# [Database management](articles/manage-databases-in-sharepoint-server.md) + ## [Add a content database](articles/add-content-databases-in-sharepoint-server.md) + ## [Attach or detach content databases](articles/attach-or-detach-content-databases-in-sharepoint-server.md) + ## [Move site collections between databases](articles/move-site-collections-between-databases-in-sharepoint-server.md) + ## [Move content databases](articles/move-content-databases-in-sharepoint-server.md) + ## [Move all databases](articles/move-all-databases-in-sharepoint-server.md) + ## [Move or rename service application databases](articles/move-or-rename-service-application-databases-in-sharepoint-server.md) + ## [Run a farm that uses read-only databases](articles/run-a-farm-that-uses-read-only-databases-in-sharepoint-server.md) + ## [Manage RBS](articles/manage-rbs-in-sharepoint-server.md) + ## [Best practices for SQL Server in a SharePoint Server farm](articles/best-practices-for-sql-server-in-a-sharepoint-server-farm.md) +# [Add a content database](articles/add-content-databases-in-sharepoint-server.md) +# [Attach or detach content databases](articles/attach-or-detach-content-databases-in-sharepoint-server.md) +# [Move site collections between databases](articles/move-site-collections-between-databases-in-sharepoint-server.md) +# [Move content databases](articles/move-content-databases-in-sharepoint-server.md) +# [Move all databases](articles/move-all-databases-in-sharepoint-server.md) +# [Move or rename service application databases](articles/move-or-rename-service-application-databases-in-sharepoint-server.md) +# [Run a farm that uses read-only databases](articles/run-a-farm-that-uses-read-only-databases-in-sharepoint-server.md) +# [Manage RBS](articles/manage-rbs-in-sharepoint-server.md) + ## [RBS overview](articles/overview-of-rbs-in-sharepoint-server.md) + ## [RBS planning](articles/deciding-to-use-rbs-in-sharepoint-server.md) + ## [Install and configure RBS](articles/install-and-configure-rbs-with-filestream-in-a-sharepoint-server-farm.md) + ## [Install and configure RBS with a 3rd party provider](articles/install-and-configure-rbs-with-a-3rd-party-provider-for-sharepoint-server.md) + ## [Set a content database to use RBS](articles/set-a-content-database-to-use-rbs-with-filestream-in-sharepoint-server.md) + ## [Migrate content into or out of RBS](articles/migrate-content-into-or-out-of-rbs-in-sharepoint-server.md) + ## [Maintain RBS](articles/maintain-rbs-in-sharepoint-server.md) + ## [Disable RBS on a content database](articles/disable-rbs-on-content-databases-in-sharepoint-server.md) +# [RBS overview](articles/overview-of-rbs-in-sharepoint-server.md) +# [RBS planning](articles/deciding-to-use-rbs-in-sharepoint-server.md) +# [Install and configure RBS](articles/install-and-configure-rbs-with-filestream-in-a-sharepoint-server-farm.md) +# [Install and configure RBS with a 3rd party provider](articles/install-and-configure-rbs-with-a-3rd-party-provider-for-sharepoint-server.md) +# [Set a content database to use RBS](articles/set-a-content-database-to-use-rbs-with-filestream-in-sharepoint-server.md) +# [Migrate content into or out of RBS](articles/migrate-content-into-or-out-of-rbs-in-sharepoint-server.md) +# [Maintain RBS](articles/maintain-rbs-in-sharepoint-server.md) +# [Disable RBS on a content database](articles/disable-rbs-on-content-databases-in-sharepoint-server.md) +# [Best practices for SQL Server in a SharePoint Server farm](articles/best-practices-for-sql-server-in-a-sharepoint-server-farm.md) +# [Service application and service management](articles/service-application-and-service-management-in-sharepoint-server.md) + ## [About service applications and services](articles/about-service-applications-and-services-in-sharepoint-server.md) + ## [Start or stop a service](articles/start-or-stop-a-service-in-sharepoint-server.md) + ## [Service application management](articles/manage-service-applications-in-sharepoint-server.md) + ## [Restrict or enable access to a service application](articles/restrict-or-enable-access-to-a-service-application-in-sharepoint-server.md) + ## [Configure automatic password change](articles/configure-automatic-password-change-in-sharepoint-server.md) +# [About service applications and services](articles/about-service-applications-and-services-in-sharepoint-server.md) +# [Start or stop a service](articles/start-or-stop-a-service-in-sharepoint-server.md) +# [Service application management](articles/manage-service-applications-in-sharepoint-server.md) + ## [Assign or remove administrators of service applications](articles/assign-or-remove-administrators-of-service-applications-in-sharepoint-server.md) + ## [Delete a service application](articles/delete-a-service-application-in-sharepoint-server.md) + ## [Share service applications across farms](articles/share-service-applications-across-farms-in-sharepoint-server.md) +# [Assign or remove administrators of service applications](articles/assign-or-remove-administrators-of-service-applications-in-sharepoint-server.md) +# [Delete a service application](articles/delete-a-service-application-in-sharepoint-server.md) +# [Share service applications across farms](articles/share-service-applications-across-farms-in-sharepoint-server.md) + ## [Exchange trust certificates between farms](articles/exchange-trust-certificates-between-farms-in-sharepoint-server.md) + ## [Publish a service application](articles/publish-service-applications-in-sharepoint-server.md) + ## [Set permission to a published service application](articles/set-permissions-to-published-service-applications-in-sharepoint-server.md) + ## [Connect to a service application on a remote farm](articles/connect-to-service-applications-on-remote-farms-in-sharepoint-server.md) + ## [Add or remove a service application connection to a Web application](articles/add-or-remove-service-application-connections-from-a-web-application-in-sharepoi.md) +# [Exchange trust certificates between farms](articles/exchange-trust-certificates-between-farms-in-sharepoint-server.md) +# [Publish a service application](articles/publish-service-applications-in-sharepoint-server.md) +# [Set permission to a published service application](articles/set-permissions-to-published-service-applications-in-sharepoint-server.md) +# [Connect to a service application on a remote farm](articles/connect-to-service-applications-on-remote-farms-in-sharepoint-server.md) +# [Add or remove a service application connection to a Web application](articles/add-or-remove-service-application-connections-from-a-web-application-in-sharepoi.md) +# [Restrict or enable access to a service application](articles/restrict-or-enable-access-to-a-service-application-in-sharepoint-server.md) +# [Configure automatic password change](articles/configure-automatic-password-change-in-sharepoint-server.md) +# [Health monitoring and reporting](articles/monitoring-and-reporting-in-sharepoint-server.md) + ## [Monitoring overview](articles/overview-of-monitoring-in-sharepoint-server.md) + ## [Using Administrative Actions logging in SharePoint Server 2016](articles/using-administrative-actions-logging-in-sharepoint-server-2016.md) + ## [Configure SharePoint Hybrid Auditing (Preview)](articles/configure-sharepoint-hybrid-auditing-in-sharepoint-2016-preview.md) + ## [Configure monitoring](articles/configure-monitoring-in-sharepoint-server-2016.md) + ## [View reports and logs](articles/view-reports-and-logs-in-sharepoint-server-2016.md) +# [Monitoring overview](articles/overview-of-monitoring-in-sharepoint-server.md) +# [Using Administrative Actions logging in SharePoint Server 2016](articles/using-administrative-actions-logging-in-sharepoint-server-2016.md) +# [Configure SharePoint Hybrid Auditing (Preview)](articles/configure-sharepoint-hybrid-auditing-in-sharepoint-2016-preview.md) +# [Configure monitoring](articles/configure-monitoring-in-sharepoint-server-2016.md) + ## [Configure diagnostic logging](articles/configure-diagnostic-logging-in-sharepoint-server.md) + ## [Configure SharePoint Health Analyzer timer jobs](articles/configure-sharepoint-health-analyzer-timer-jobs-in-sharepoint-server-2016.md) + ## [Configure usage and health data collection](articles/configure-usage-and-health-data-collection-in-sharepoint-server.md) + ## [Configure SharePoint Health Analyzer rules](articles/configure-sharepoint-health-analyzer-rules-in-sharepoint-server.md) +# [Configure diagnostic logging](articles/configure-diagnostic-logging-in-sharepoint-server.md) +# [Configure SharePoint Health Analyzer timer jobs](articles/configure-sharepoint-health-analyzer-timer-jobs-in-sharepoint-server-2016.md) +# [Configure usage and health data collection](articles/configure-usage-and-health-data-collection-in-sharepoint-server.md) +# [Configure SharePoint Health Analyzer rules](articles/configure-sharepoint-health-analyzer-rules-in-sharepoint-server.md) +# [View reports and logs](articles/view-reports-and-logs-in-sharepoint-server-2016.md) + ## [View health reports](articles/view-health-reports-in-sharepoint-server.md) + ## [View diagnostic logs](articles/view-diagnostic-logs-in-sharepoint-server.md) + ## [View timer job status](articles/view-timer-job-status-in-sharepoint-server-2016.md) + ## [Monitor cache performance](articles/monitor-cache-performance-in-sharepoint-server-2016.md) + ## [View data in the logging database](articles/view-data-in-the-logging-database-in-sharepoint-server-2016.md) +# [View health reports](articles/view-health-reports-in-sharepoint-server.md) +# [View diagnostic logs](articles/view-diagnostic-logs-in-sharepoint-server.md) +# [View timer job status](articles/view-timer-job-status-in-sharepoint-server-2016.md) +# [Monitor cache performance](articles/monitor-cache-performance-in-sharepoint-server-2016.md) +# [View data in the logging database](articles/view-data-in-the-logging-database-in-sharepoint-server-2016.md) +# [Web applications management](articles/web-applications-management-in-sharepoint-server.md) + ## [Manage permissions for a web application](articles/manage-permissions-for-a-web-application-in-sharepoint-server.md) + ## [Manage permission policies for a web application](articles/manage-permission-policies-for-a-web-application-in-sharepoint-server.md) + ## [Manage anonymous access for a web application](articles/manage-anonymous-access-for-a-web-application-in-sharepoint-server.md) + ## [Extend a claims-based web application](articles/extend-claims-based-web-applications-in-sharepoint.md) + ## [Define managed paths](articles/define-managed-paths-in-sharepoint-server.md) + ## [Cache settings operations](articles/cache-settings-operations-in-sharepoint-server.md) +# [Manage permissions for a web application](articles/manage-permissions-for-a-web-application-in-sharepoint-server.md) +# [Manage permission policies for a web application](articles/manage-permission-policies-for-a-web-application-in-sharepoint-server.md) +# [Manage anonymous access for a web application](articles/manage-anonymous-access-for-a-web-application-in-sharepoint-server.md) +# [Extend a claims-based web application](articles/extend-claims-based-web-applications-in-sharepoint.md) +# [Define managed paths](articles/define-managed-paths-in-sharepoint-server.md) +# [Cache settings operations](articles/cache-settings-operations-in-sharepoint-server.md) + ## [Cache settings configuration for a web application](articles/configure-cache-settings-for-a-web-application-in-sharepoint-server.md) + ## [Configure object cache user accounts](articles/configure-object-cache-user-accounts-in-sharepoint-server.md) + ## [Flush the BLOB cache](articles/flush-the-blob-cache-in-sharepoint-server.md) +# [Cache settings configuration for a web application](articles/configure-cache-settings-for-a-web-application-in-sharepoint-server.md) +# [Configure object cache user accounts](articles/configure-object-cache-user-accounts-in-sharepoint-server.md) +# [Flush the BLOB cache](articles/flush-the-blob-cache-in-sharepoint-server.md) +# [Description of MinRole and associated services in SharePoint Server 2016](articles/description-of-minrole-and-associated-services-in-sharepoint-server-2016.md) +# [Managing a MinRole Server Farm in SharePoint Server 2016](articles/managing-a-minrole-server-farm-in-sharepoint-server-2016.md) +# [Role conversion using MinRole in SharePoint Server 2016](articles/role-conversion-using-minrole-in-sharepoint-server-2016.md) +# [Site and site collection administration](articles/administer-sites-and-site-collections-in-sharepoint-server.md) + ## [Manage site collections](articles/manage-site-collections-in-sharepoint-server.md) + ## [Manage sites](articles/manage-sites-in-sharepoint-server.md) + ## [Manage web parts](articles/manage-web-parts-in-sharepoint-server.md) +# [Manage site collections](articles/manage-site-collections-in-sharepoint-server.md) + ## [Create a site collection](articles/create-a-site-collection-in-sharepoint-server.md) + ## [Delete and restore site collections](articles/delete-and-restore-site-collections-in-sharepoint-server.md) + ## [Manage the lock status for site collections](articles/manage-the-lock-status-for-site-collections-in-sharepoint-server.md) + ## [View all site collections](articles/view-all-site-collections-in-sharepoint-server.md) + ## [Manage a connection to a document center or a records center](articles/manage-a-connection-to-a-document-center-or-a-records-center-in-sharepoint-serve.md) + ## [Change site collection administrators](articles/change-site-collection-administrators-in-sharepoint-server.md) + ## [Create, edit, and delete quota templates](articles/create-edit-and-delete-quota-templates-in-sharepoint-server.md) +# [Create a site collection](articles/create-a-site-collection-in-sharepoint-server.md) +# [Delete and restore site collections](articles/delete-and-restore-site-collections-in-sharepoint-server.md) +# [Manage the lock status for site collections](articles/manage-the-lock-status-for-site-collections-in-sharepoint-server.md) +# [View all site collections](articles/view-all-site-collections-in-sharepoint-server.md) +# [Manage a connection to a document center or a records center](articles/manage-a-connection-to-a-document-center-or-a-records-center-in-sharepoint-serve.md) +# [Change site collection administrators](articles/change-site-collection-administrators-in-sharepoint-server.md) +# [Create, edit, and delete quota templates](articles/create-edit-and-delete-quota-templates-in-sharepoint-server.md) +# [Manage sites](articles/manage-sites-in-sharepoint-server.md) + ## [Manage unused site collections](articles/manage-unused-site-collections-in-sharepoint-server.md) +# [Manage unused site collections](articles/manage-unused-site-collections-in-sharepoint-server.md) +# [Manage web parts](articles/manage-web-parts-in-sharepoint-server.md) + ## [Configure and deploy web parts](articles/configure-and-deploy-web-parts-in-sharepoint-server.md) + ## [Edit existing web parts in SharePoint](articles/edit-existing-web-parts-in-sharepoint-server.md) +# [Configure and deploy web parts](articles/configure-and-deploy-web-parts-in-sharepoint-server.md) +# [Edit existing web parts in SharePoint](articles/edit-existing-web-parts-in-sharepoint-server.md) +# [Search administration](articles/administer-search-in-sharepoint-server.md) + ## [Manage the Search Center in SharePoint Server](articles/manage-the-search-center-in-sharepoint-server.md) + ## [Manage the index](articles/manage-the-search-index-in-sharepoint-server-2016.md) + ## [Manage crawling](articles/manage-crawling-in-sharepoint-server.md) + ## [Manage relevance](articles/manage-search-relevance-in-sharepoint-server.md) + ## [Manage the search topology](articles/manage-the-search-topology-in-sharepoint-server.md) + ## [View search diagnostics](articles/view-search-diagnostics-in-sharepoint-server.md) + ## [Enable search alerts](articles/enable-search-alerts-in-sharepoint-server.md) + ## [Enable query logging](articles/enable-query-logging-in-sharepoint-server.md) + ## [Export and import customized search configuration settings](articles/export-and-import-customized-search-configuration-settings-in-sharepoint-server.md) +# [Manage the Search Center in SharePoint Server](articles/manage-the-search-center-in-sharepoint-server.md) + ## [Configure properties of the Search Box Web Part](articles/configure-properties-of-the-search-box-web-part-in-sharepoint-server.md) + ## [Configure properties of the Search Results Web Part](articles/configure-properties-of-the-search-results-web-part-in-sharepoint-server.md) + ## [Configure properties of the Refinement Web Part](articles/configure-properties-of-the-refinement-web-part-in-sharepoint-server.md) + ## [Configure properties of the Search Navigation Web Part](articles/configure-properties-of-the-search-navigation-web-part-in-sharepoint-server.md) +# [Configure properties of the Search Box Web Part](articles/configure-properties-of-the-search-box-web-part-in-sharepoint-server.md) +# [Configure properties of the Search Results Web Part](articles/configure-properties-of-the-search-results-web-part-in-sharepoint-server.md) +# [Configure properties of the Refinement Web Part](articles/configure-properties-of-the-refinement-web-part-in-sharepoint-server.md) +# [Configure properties of the Search Navigation Web Part](articles/configure-properties-of-the-search-navigation-web-part-in-sharepoint-server.md) +# [Manage the index](articles/manage-the-search-index-in-sharepoint-server-2016.md) + ## [Manage the search schema](articles/manage-the-search-schema-in-sharepoint-server.md) + ## [Add or remove a file type from the search index](articles/add-or-remove-a-file-type-from-the-search-index-in-sharepoint-server.md) + ## [Delete items from the search index or from search results](articles/delete-items-from-the-search-index-or-from-search-results-in-sharepoint-server.md) + ## [Reset the search index](articles/reset-the-search-index-in-sharepoint-server.md) +# [Manage the search schema](articles/manage-the-search-schema-in-sharepoint-server.md) +# [Add or remove a file type from the search index](articles/add-or-remove-a-file-type-from-the-search-index-in-sharepoint-server.md) +# [Delete items from the search index or from search results](articles/delete-items-from-the-search-index-or-from-search-results-in-sharepoint-server.md) +# [Reset the search index](articles/reset-the-search-index-in-sharepoint-server.md) +# [Manage crawling](articles/manage-crawling-in-sharepoint-server.md) + ## [Add, edit, or delete a content source](articles/add-edit-or-delete-a-content-source-in-sharepoint-server.md) + ## [Change the default account for crawling](articles/change-the-default-account-for-crawling-in-sharepoint-server.md) + ## [Start, pause, resume, or stop a crawl](articles/start-pause-resume-or-stop-a-crawl-in-sharepoint-server.md) + ## [Manage continuous crawls](articles/manage-continuous-crawls-in-sharepoint-server.md) + ## [Manage crawl rules](articles/manage-crawl-rules-in-sharepoint-server.md) + ## [Configure and use the Exchange connector](articles/configure-and-use-the-exchange-connector-for-sharepoint-server.md) + ## [Configure and use the Documentum connector](articles/configure-and-use-the-documentum-connector-in-sharepoint-server.md) + ## [Configure and use the Lotus Notes connector](articles/configure-and-use-the-lotus-notes-connector-for-sharepoint-server.md) + ## [Manage farm-level crawl settings](articles/manage-farm-level-crawl-settings-in-sharepoint-server.md) + ## [Best practices for crawling](articles/best-practices-for-crawling-in-sharepoint-server.md) +# [Add, edit, or delete a content source](articles/add-edit-or-delete-a-content-source-in-sharepoint-server.md) +# [Change the default account for crawling](articles/change-the-default-account-for-crawling-in-sharepoint-server.md) +# [Start, pause, resume, or stop a crawl](articles/start-pause-resume-or-stop-a-crawl-in-sharepoint-server.md) +# [Manage continuous crawls](articles/manage-continuous-crawls-in-sharepoint-server.md) +# [Manage crawl rules](articles/manage-crawl-rules-in-sharepoint-server.md) +# [Configure and use the Exchange connector](articles/configure-and-use-the-exchange-connector-for-sharepoint-server.md) +# [Configure and use the Documentum connector](articles/configure-and-use-the-documentum-connector-in-sharepoint-server.md) +# [Configure and use the Lotus Notes connector](articles/configure-and-use-the-lotus-notes-connector-for-sharepoint-server.md) +# [Manage farm-level crawl settings](articles/manage-farm-level-crawl-settings-in-sharepoint-server.md) + ## [Configure time-out values for crawler connections](articles/configure-time-out-values-for-crawler-connections-in-sharepoint-server.md) + ## [Configure the crawler in case of SSL certificate warnings](articles/configure-the-crawler-in-case-of-ssl-certificate-warnings-in-sharepoint-server.md) + ## [Configure proxy server settings for Search](articles/configure-proxy-server-settings-for-search-in-sharepoint-server.md) +# [Configure time-out values for crawler connections](articles/configure-time-out-values-for-crawler-connections-in-sharepoint-server.md) +# [Configure the crawler in case of SSL certificate warnings](articles/configure-the-crawler-in-case-of-ssl-certificate-warnings-in-sharepoint-server.md) +# [Configure proxy server settings for Search](articles/configure-proxy-server-settings-for-search-in-sharepoint-server.md) +# [Best practices for crawling](articles/best-practices-for-crawling-in-sharepoint-server.md) +# [Manage relevance](articles/manage-search-relevance-in-sharepoint-server.md) + ## [Manage query spelling correction](articles/manage-query-spelling-correction-in-sharepoint-server.md) + ## [Manage query suggestions](articles/manage-query-suggestions-in-sharepoint-server.md) + ## [Create and deploy a thesaurus](articles/create-and-deploy-a-thesaurus-in-sharepoint-server.md) + ## [Configure authoritative pages](articles/configure-authoritative-pages-in-sharepoint-server.md) + ## [Manage query rules](articles/manage-query-rules-in-sharepoint-server.md) + ## [Configure result sources for search](articles/configure-result-sources-for-search-in-sharepoint-server.md) + ## [Create and deploy custom entity extractors](articles/create-and-deploy-custom-entity-extractors-in-sharepoint-server.md) + ## [Manage company name extraction](articles/manage-company-name-extraction-in-sharepoint-server.md) + ## [Customize search result types](articles/customize-search-result-types-in-sharepoint-server.md) + ## [Configure trust for search between two SharePoint Server farms](articles/configure-trust-for-search-between-two-sharepoint-server-farms.md) +# [Manage query spelling correction](articles/manage-query-spelling-correction-in-sharepoint-server.md) +# [Manage query suggestions](articles/manage-query-suggestions-in-sharepoint-server.md) +# [Create and deploy a thesaurus](articles/create-and-deploy-a-thesaurus-in-sharepoint-server.md) +# [Configure authoritative pages](articles/configure-authoritative-pages-in-sharepoint-server.md) +# [Manage query rules](articles/manage-query-rules-in-sharepoint-server.md) +# [Configure result sources for search](articles/configure-result-sources-for-search-in-sharepoint-server.md) +# [Create and deploy custom entity extractors](articles/create-and-deploy-custom-entity-extractors-in-sharepoint-server.md) +# [Manage company name extraction](articles/manage-company-name-extraction-in-sharepoint-server.md) +# [Customize search result types](articles/customize-search-result-types-in-sharepoint-server.md) +# [Configure trust for search between two SharePoint Server farms](articles/configure-trust-for-search-between-two-sharepoint-server-farms.md) +# [Manage the search topology](articles/manage-the-search-topology-in-sharepoint-server.md) + ## [Change the default search topology](articles/change-the-default-search-topology-in-sharepoint-server.md) + ## [Manage search components](articles/manage-search-components-in-sharepoint-server.md) + ## [Manage the index component](articles/manage-the-index-component-in-sharepoint-server.md) + ## [Manage a paused Search service application](articles/manage-a-paused-search-service-application-in-sharepoint-server.md) +# [Change the default search topology](articles/change-the-default-search-topology-in-sharepoint-server.md) +# [Manage search components](articles/manage-search-components-in-sharepoint-server.md) +# [Manage the index component](articles/manage-the-index-component-in-sharepoint-server.md) +# [Manage a paused Search service application](articles/manage-a-paused-search-service-application-in-sharepoint-server.md) +# [View search diagnostics](articles/view-search-diagnostics-in-sharepoint-server.md) +# [Enable search alerts](articles/enable-search-alerts-in-sharepoint-server.md) +# [Enable query logging](articles/enable-query-logging-in-sharepoint-server.md) +# [Export and import customized search configuration settings](articles/export-and-import-customized-search-configuration-settings-in-sharepoint-server.md) +# [Business intelligence administration](articles/administer-business-intelligence-in-sharepoint-server.md) + ## [Excel Services administration](articles/administer-excel-services-in-sharepoint-server-2013.md) + ## [PerformancePoint Services administration](articles/performancepoint-services-administration.md) + ## [Secure Store for Business Intelligence service applications](articles/secure-store-for-business-intelligence-service-applications.md) + ## [Configure Power Pivot for SharePoint 2013](articles/configure-power-pivot-for-sharepoint-2013.md) + ## [Use Analysis Services EffectiveUserName in SharePoint Server](articles/use-analysis-services-effectiveusername-in-sharepoint-server.md) + ## [Use Secure Store with SQL Server Authentication](articles/use-secure-store-with-sql-server-authentication.md) + ## [Use Visio Services with external lists in SharePoint Server](articles/use-visio-services-with-external-lists-in-sharepoint-server.md) + ## [Use Visio Services with SharePoint lists](articles/use-visio-services-with-sharepoint-lists.md) + ## [Share data connections by using Excel and Excel Services (SharePoint Server 2013)](articles/share-data-connections-by-using-excel-and-excel-services-sharepoint-server-2013.md) + ## [Configure AdventureWorks](articles/configure-adventureworks-for-business-intelligence-solutions.md) + ## [Business Connectivity Service](articles/business-connectivity-service.md) + ## [Share workbooks by using Excel Services (SharePoint Server 2013)](articles/share-workbooks-by-using-excel-services-sharepoint-server-2013.md) +# [Excel Services administration](articles/administer-excel-services-in-sharepoint-server-2013.md) + ## [Configure Excel Services](articles/configure-excel-services-sharepoint-server-2013.md) + ## [Manage Excel Services global settings](articles/manage-excel-services-global-settings-sharepoint-server-2013.md) + ## [Manage Excel Services trusted file locations](articles/manage-excel-services-trusted-file-locations-sharepoint-server-2013.md) + ## [Manage Excel Services trusted data providers](articles/manage-excel-services-trusted-data-providers-sharepoint-server-2013.md) + ## [Manage Excel Services trusted data connection libraries](articles/manage-excel-services-trusted-data-connection-libraries-sharepoint-server-2013.md) + ## [Manage Excel Services user defined function assemblies](articles/manage-excel-services-user-defined-function-assemblies-sharepoint-server-2013.md) + ## [Manage Excel Services data model settings](articles/manage-excel-services-data-model-settings-sharepoint-server-2013.md) +# [Configure Excel Services](articles/configure-excel-services-sharepoint-server-2013.md) +# [Manage Excel Services global settings](articles/manage-excel-services-global-settings-sharepoint-server-2013.md) +# [Manage Excel Services trusted file locations](articles/manage-excel-services-trusted-file-locations-sharepoint-server-2013.md) +# [Manage Excel Services trusted data providers](articles/manage-excel-services-trusted-data-providers-sharepoint-server-2013.md) +# [Manage Excel Services trusted data connection libraries](articles/manage-excel-services-trusted-data-connection-libraries-sharepoint-server-2013.md) +# [Manage Excel Services user defined function assemblies](articles/manage-excel-services-user-defined-function-assemblies-sharepoint-server-2013.md) +# [Manage Excel Services data model settings](articles/manage-excel-services-data-model-settings-sharepoint-server-2013.md) +# [PerformancePoint Services administration](articles/performancepoint-services-administration.md) + ## [Enable trusted locations for PerformancePoint Services](articles/enable-trusted-locations-for-performancepoint-services.md) + ## [PerformancePoint Services application settings](articles/performancepoint-services-application-settings.md) +# [Enable trusted locations for PerformancePoint Services](articles/enable-trusted-locations-for-performancepoint-services.md) +# [PerformancePoint Services application settings](articles/performancepoint-services-application-settings.md) +# [Secure Store for Business Intelligence service applications](articles/secure-store-for-business-intelligence-service-applications.md) + ## [Use Excel Services with Secure Store](articles/use-excel-services-with-secure-store-service-in-sharepoint-server-2016.md) + ## [Use PerformancePoint Services with Secure Store](articles/use-performancepoint-services-with-secure-store-service-in-sharepoint-server.md) + ## [Use Visio Services with Secure Store](articles/use-visio-services-with-secure-store-service-in-sharepoint-server.md) +# [Use Excel Services with Secure Store](articles/use-excel-services-with-secure-store-service-in-sharepoint-server-2016.md) + ## [Configure the unattended service account](articles/configure-excel-services-data-refresh-by-using-the-unattended-service-account-in.md) + ## [Configure Excel Services data refresh by using embedded data connections in SharePoint Server 2013](articles/configure-excel-services-data-refresh-by-using-embedded-data-connections-in-shar.md) + ## [Configure Excel Services data refresh by using external data connections in SharePoint Server 2013](articles/configure-excel-services-data-refresh-by-using-external-data-connections-in-shar.md) +# [Configure the unattended service account](articles/configure-excel-services-data-refresh-by-using-the-unattended-service-account-in.md) +# [Configure Excel Services data refresh by using embedded data connections in SharePoint Server 2013](articles/configure-excel-services-data-refresh-by-using-embedded-data-connections-in-shar.md) +# [Configure Excel Services data refresh by using external data connections in SharePoint Server 2013](articles/configure-excel-services-data-refresh-by-using-external-data-connections-in-shar.md) +# [Use PerformancePoint Services with Secure Store](articles/use-performancepoint-services-with-secure-store-service-in-sharepoint-server.md) + ## [Configure the unattended service account for PerformancePoint Services](articles/configure-the-unattended-service-account-for-performancepoint-services.md) + ## [Configure Secure Store for use with PerformancePoint Services](articles/configure-secure-store-for-use-with-performancepoint-services.md) +# [Configure the unattended service account for PerformancePoint Services](articles/configure-the-unattended-service-account-for-performancepoint-services.md) +# [Configure Secure Store for use with PerformancePoint Services](articles/configure-secure-store-for-use-with-performancepoint-services.md) +# [Use Visio Services with Secure Store](articles/use-visio-services-with-secure-store-service-in-sharepoint-server.md) + ## [Configure the unattended service account](articles/configure-visio-services-data-refresh-in-sharepoint-server-2016-by-using-the-una.md) + ## [Configure data refresh by using external data connections](articles/configure-visio-services-data-refresh-in-sharepoint-server-by-using-external-dat.md) +# [Configure the unattended service account](articles/configure-visio-services-data-refresh-in-sharepoint-server-2016-by-using-the-una.md) +# [Configure data refresh by using external data connections](articles/configure-visio-services-data-refresh-in-sharepoint-server-by-using-external-dat.md) +# [Configure Power Pivot for SharePoint 2013](articles/configure-power-pivot-for-sharepoint-2013.md) + ## [Data refresh using Secure Store](articles/configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoin.md) + ## [Data refresh using a specified account](articles/configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh.md) + ## [Data refresh using the unattended data refresh account](articles/configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re.md) +# [Data refresh using Secure Store](articles/configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoin.md) +# [Data refresh using a specified account](articles/configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh.md) +# [Data refresh using the unattended data refresh account](articles/configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re.md) +# [Use Analysis Services EffectiveUserName in SharePoint Server](articles/use-analysis-services-effectiveusername-in-sharepoint-server.md) + ## [Use EffectiveUserName with Excel Services (SharePoint Server 2013)](articles/use-effectiveusername-with-excel-services-sharepoint-server-2013.md) + ## [Use EffectiveUserName in PerformancePoint Services](articles/use-effectiveusername-in-performancepoint-services.md) +# [Use EffectiveUserName with Excel Services (SharePoint Server 2013)](articles/use-effectiveusername-with-excel-services-sharepoint-server-2013.md) +# [Use EffectiveUserName in PerformancePoint Services](articles/use-effectiveusername-in-performancepoint-services.md) +# [Use Secure Store with SQL Server Authentication](articles/use-secure-store-with-sql-server-authentication.md) +# [Use Visio Services with external lists in SharePoint Server](articles/use-visio-services-with-external-lists-in-sharepoint-server.md) +# [Use Visio Services with SharePoint lists](articles/use-visio-services-with-sharepoint-lists.md) +# [Share data connections by using Excel and Excel Services (SharePoint Server 2013)](articles/share-data-connections-by-using-excel-and-excel-services-sharepoint-server-2013.md) + ## [Share a SQL Server Analysis Services data connection using Excel Services (SharePoint Server 2013)](articles/share-a-sql-server-analysis-services-data-connection-using-excel-services-sharep.md) + ## [Share a SQL Server data connection using Excel Services (SharePoint Server 2013)](articles/share-a-sql-server-data-connection-using-excel-services-sharepoint-server-2013.md) + ## [Share an OLE DB or ODBC connection using Excel Services (SharePoint Server 2013)](articles/share-an-ole-db-or-odbc-connection-using-excel-services-sharepoint-server-2013.md) +# [Share a SQL Server Analysis Services data connection using Excel Services (SharePoint Server 2013)](articles/share-a-sql-server-analysis-services-data-connection-using-excel-services-sharep.md) +# [Share a SQL Server data connection using Excel Services (SharePoint Server 2013)](articles/share-a-sql-server-data-connection-using-excel-services-sharepoint-server-2013.md) +# [Share an OLE DB or ODBC connection using Excel Services (SharePoint Server 2013)](articles/share-an-ole-db-or-odbc-connection-using-excel-services-sharepoint-server-2013.md) +# [Configure AdventureWorks](articles/configure-adventureworks-for-business-intelligence-solutions.md) +# [Business Connectivity Service](articles/business-connectivity-service.md) + ## [Create an Excel Services dashboard using an OData data feed](articles/create-an-excel-services-dashboard-using-an-odata-data-feed.md) + ## [Create an Excel Services dashboard using SQL Server Analysis Services data](articles/create-an-excel-services-dashboard-using-sql-server-analysis-services-data.md) + ## [Create an Excel Services dashboard using a Data Model (SharePoint Server 2013)](articles/create-an-excel-services-dashboard-using-a-data-model-sharepoint-server-2013.md) +# [Create an Excel Services dashboard using an OData data feed](articles/create-an-excel-services-dashboard-using-an-odata-data-feed.md) +# [Create an Excel Services dashboard using SQL Server Analysis Services data](articles/create-an-excel-services-dashboard-using-sql-server-analysis-services-data.md) +# [Create an Excel Services dashboard using a Data Model (SharePoint Server 2013)](articles/create-an-excel-services-dashboard-using-a-data-model-sharepoint-server-2013.md) +# [Share workbooks by using Excel Services (SharePoint Server 2013)](articles/share-workbooks-by-using-excel-services-sharepoint-server-2013.md) +# [User Profile service administration](articles/administer-the-user-profile-service-in-sharepoint-server.md) + ## [Create a User Profile service application](articles/create-a-user-profile-service-applications-in-sharepoint-server.md) + ## [Delegate administration of a User Profile service application](articles/delegate-administration-of-user-profile-service-applications-or-features-in-shar.md) + ## [Add, edit, or delete custom properties for a user profile](articles/add-edit-or-delete-custom-properties-in-sharepoint-server-user-profiles.md) + ## [Manage profile synchronization](articles/manage-user-profile-synchronization-in-sharepoint-server.md) +# [Create a User Profile service application](articles/create-a-user-profile-service-applications-in-sharepoint-server.md) +# [Delegate administration of a User Profile service application](articles/delegate-administration-of-user-profile-service-applications-or-features-in-shar.md) +# [Add, edit, or delete custom properties for a user profile](articles/add-edit-or-delete-custom-properties-in-sharepoint-server-user-profiles.md) +# [Manage profile synchronization](articles/manage-user-profile-synchronization-in-sharepoint-server.md) + ## [Configure profile synchronization](articles/synchronize-user-and-group-profiles-in-sharepoint-server-2013.md) + ## [Configure profile synchronization by using SharePoint Active Directory Import](articles/configure-profile-synchronization-by-using-sharepoint-active-directory-import-in.md) + ## [Start profile synchronization manually](articles/start-profile-synchronization-manually-in-sharepoint-server.md) + ## [Schedule profile synchronization](articles/schedule-profile-synchronization-in-sharepoint-server.md) + ## [Maintain profile synchronization](articles/maintain-user-profile-synchronization-settings-in-sharepoint-server-2013.md) +# [Configure profile synchronization](articles/synchronize-user-and-group-profiles-in-sharepoint-server-2013.md) +# [Configure profile synchronization by using SharePoint Active Directory Import](articles/configure-profile-synchronization-by-using-sharepoint-active-directory-import-in.md) +# [Start profile synchronization manually](articles/start-profile-synchronization-manually-in-sharepoint-server.md) +# [Schedule profile synchronization](articles/schedule-profile-synchronization-in-sharepoint-server.md) +# [Maintain profile synchronization](articles/maintain-user-profile-synchronization-settings-in-sharepoint-server-2013.md) +# [Hybrid](articles/hybrid-for-sharepoint-server.md) + ## [Plan SharePoint Server hybrid](articles/plan-sharepoint-server-hybrid.md) + ## [Install and configure SharePoint Server hybrid](articles/install-and-configure-sharepoint-server-hybrid.md) +# [Plan SharePoint Server hybrid](articles/plan-sharepoint-server-hybrid.md) + ## [The building blocks of SharePoint hybrid](articles/the-building-blocks-of-sharepoint-hybrid.md) + ## [Plan server-to-server authentication](articles/plan-server-to-server-authentication.md) + ## [Plan hybrid federated search](articles/plan-hybrid-federated-search-for-sharepoint-server.md) + ## [Plan connectivity from Office 365 to SharePoint Server](articles/plan-connectivity-from-office-365-to-sharepoint-server.md) + ## [Plan for SharePoint Hybrid Picker](articles/plan-for-sharepoint-hybrid-picker.md) +# [The building blocks of SharePoint hybrid](articles/the-building-blocks-of-sharepoint-hybrid.md) +# [Plan server-to-server authentication](articles/plan-server-to-server-authentication.md) +# [Plan hybrid federated search](articles/plan-hybrid-federated-search-for-sharepoint-server.md) +# [Plan connectivity from Office 365 to SharePoint Server](articles/plan-connectivity-from-office-365-to-sharepoint-server.md) +# [Plan for SharePoint Hybrid Picker](articles/plan-for-sharepoint-hybrid-picker.md) +# [Install and configure SharePoint Server hybrid](articles/install-and-configure-sharepoint-server-hybrid.md) + ## [Hardware and software requirements for SharePoint hybrid](articles/hardware-and-software-requirements-for-sharepoint-hybrid.md) + ## [Accounts needed for hybrid configuration and testing](articles/accounts-needed-for-hybrid-configuration-and-testing.md) + ## [Configuration roadmaps](articles/sharepoint-server-2016-hybrid-configuration-roadmaps.md) + ## [Configure the hybrid infrastructure](articles/configure-the-hybrid-infrastructure.md) + ## [Configure a hybrid solution](articles/configure-a-hybrid-solution-for-sharepoint-server.md) +# [Hardware and software requirements for SharePoint hybrid](articles/hardware-and-software-requirements-for-sharepoint-hybrid.md) +# [Accounts needed for hybrid configuration and testing](articles/accounts-needed-for-hybrid-configuration-and-testing.md) +# [Configuration roadmaps](articles/sharepoint-server-2016-hybrid-configuration-roadmaps.md) + ## [Configure hybrid OneDrive for Business - roadmap](articles/configure-hybrid-onedrive-for-businessroadmap.md) + ## [Configure hybrid sites features - roadmap](articles/configure-hybrid-sites-featuresroadmap.md) + ## [Configure cloud hybrid search - roadmap](articles/configure-cloud-hybrid-searchroadmap.md) + ## [Configure hybrid federated search (SharePoint Server) - roadmap](articles/configure-hybrid-federated-search-from-sharepoint-server-to-sharepoint-onlineroa.md) + ## [Configure hybrid federated search (SharePoint Online) - roadmap](articles/configure-hybrid-federated-search-from-sharepoint-online-to-sharepoint-serverroa.md) + ## [Configure hybrid Business Connectivity Services - roadmap](articles/configure-hybrid-business-connectivity-servicesroadmap.md) +# [Configure hybrid OneDrive for Business - roadmap](articles/configure-hybrid-onedrive-for-businessroadmap.md) +# [Configure hybrid sites features - roadmap](articles/configure-hybrid-sites-featuresroadmap.md) +# [Configure cloud hybrid search - roadmap](articles/configure-cloud-hybrid-searchroadmap.md) +# [Configure hybrid federated search (SharePoint Server) - roadmap](articles/configure-hybrid-federated-search-from-sharepoint-server-to-sharepoint-onlineroa.md) +# [Configure hybrid federated search (SharePoint Online) - roadmap](articles/configure-hybrid-federated-search-from-sharepoint-online-to-sharepoint-serverroa.md) +# [Configure hybrid Business Connectivity Services - roadmap](articles/configure-hybrid-business-connectivity-servicesroadmap.md) +# [Configure the hybrid infrastructure](articles/configure-the-hybrid-infrastructure.md) + ## [Configure Office 365 for SharePoint hybrid](articles/configure-office-365-for-sharepoint-hybrid.md) + ## [Set up SharePoint services for hybrid environments](articles/set-up-sharepoint-services-for-hybrid-environments.md) + ## [Configure server-to-server authentication](articles/configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o.md) + ## [Run Hybrid Picker](articles/run-hybrid-picker.md) + ## [Configure inbound connectivity](articles/configure-connectivity-from-office-365-to-sharepoint-server.md) + ## [Configure a reverse proxy device for SharePoint Server hybrid](articles/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md) +# [Configure Office 365 for SharePoint hybrid](articles/configure-office-365-for-sharepoint-hybrid.md) +# [Set up SharePoint services for hybrid environments](articles/set-up-sharepoint-services-for-hybrid-environments.md) +# [Configure server-to-server authentication](articles/configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o.md) +# [Run Hybrid Picker](articles/run-hybrid-picker.md) +# [Configure inbound connectivity](articles/configure-connectivity-from-office-365-to-sharepoint-server.md) +# [Configure a reverse proxy device for SharePoint Server hybrid](articles/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md) + ## [Configure Web Application Proxy for a hybrid environment](articles/configure-web-application-proxy-for-a-hybrid-environment.md) + ## [Configure Forefront TMG for a hybrid environment](articles/configure-forefront-tmg-for-a-hybrid-environment.md) +# [Configure Web Application Proxy for a hybrid environment](articles/configure-web-application-proxy-for-a-hybrid-environment.md) +# [Configure Forefront TMG for a hybrid environment](articles/configure-forefront-tmg-for-a-hybrid-environment.md) +# [Configure a hybrid solution](articles/configure-a-hybrid-solution-for-sharepoint-server.md) + ## [Configure hybrid OneDrive for Business](articles/configure-hybrid-onedrive-for-business.md) + ## [Show results from Office 365 in on-premises SharePoint with cloud hybrid search](articles/show-results-from-office-365-in-on-premises-sharepoint-with-cloud-hybrid-search.md) + ## [Enable previews of on-premises search results in cloud hybrid search](articles/enable-previews-of-on-premises-search-results-in-cloud-hybrid-search.md) + ## [Display hybrid federated search results in SharePoint Server](articles/display-hybrid-federated-search-results-in-sharepoint-server.md) + ## [Display hybrid federated search results in SharePoint Online](articles/display-hybrid-federated-search-results-in-sharepoint-online.md) + ## [Set up Search of OneDrive for Business in Office 365 from SharePoint Server](articles/set-up-search-of-onedrive-for-business-in-office-365-from-sharepoint-server.md) + ## [Deploy a Business Connectivity Services hybrid solution](articles/deploy-a-business-connectivity-services-hybrid-solution-in-sharepoint.md) +# [Configure hybrid OneDrive for Business](articles/configure-hybrid-onedrive-for-business.md) +# [Show results from Office 365 in on-premises SharePoint with cloud hybrid search](articles/show-results-from-office-365-in-on-premises-sharepoint-with-cloud-hybrid-search.md) +# [Enable previews of on-premises search results in cloud hybrid search](articles/enable-previews-of-on-premises-search-results-in-cloud-hybrid-search.md) +# [Display hybrid federated search results in SharePoint Server](articles/display-hybrid-federated-search-results-in-sharepoint-server.md) +# [Display hybrid federated search results in SharePoint Online](articles/display-hybrid-federated-search-results-in-sharepoint-online.md) +# [Set up Search of OneDrive for Business in Office 365 from SharePoint Server](articles/set-up-search-of-onedrive-for-business-in-office-365-from-sharepoint-server.md) +# [Deploy a Business Connectivity Services hybrid solution](articles/deploy-a-business-connectivity-services-hybrid-solution-in-sharepoint.md) + ## [Prepare your environment](articles/prepare-your-environment-for-the-business-connectivity-services-hybrid-scenario.md) + ## [Validate the hybrid scenario](articles/validate-the-business-connectivity-services-hybrid-scenario.md) +# [Prepare your environment](articles/prepare-your-environment-for-the-business-connectivity-services-hybrid-scenario.md) + ## [Deploy the hybrid scenario as an external list](articles/deploy-the-business-connectivity-services-hybrid-scenario-as-an-external-list.md) +# [Deploy the hybrid scenario as an external list](articles/deploy-the-business-connectivity-services-hybrid-scenario-as-an-external-list.md) +# [Validate the hybrid scenario](articles/validate-the-business-connectivity-services-hybrid-scenario.md) +# [Technical reference](articles/technical-reference-for-sharepoint-server.md) + ## [System Center Operations Manager knowledge articles](articles/system-center-operations-manager-knowledge-articles-for-sharepoint-server.md) + ## [Database types and descriptions](articles/database-types-and-descriptions-in-sharepoint-server.md) + ## [SharePoint Health Analyzer rules reference](articles/sharepoint-health-analyzer-rules-reference-for-sharepoint-server-2016.md) + ## [Timer job reference](articles/timer-job-reference-for-sharepoint-server-2016.md) + ## [Search technical reference](articles/search-technical-reference-for-sharepoint-server.md) +# [System Center Operations Manager knowledge articles](articles/system-center-operations-manager-knowledge-articles-for-sharepoint-server.md) + ## [Access Services in SharePoint Server 2016](articles/access-services-in-sharepoint-server-2016-knowledge-articles.md) + ## [Machine Translation service in SharePoint Server 2016](articles/machine-translation-service-in-sharepoint-server-2016-knowledge-articles.md) + ## [Search in SharePoint Server 2016](articles/search-in-sharepoint-server-2016-knowledge-articles-for-systems-center-operation.md) + ## [Visio Services in SharePoint Server 2016](articles/visio-services-in-sharepoint-server-2016-knowledge-articles.md) +# [Access Services in SharePoint Server 2016](articles/access-services-in-sharepoint-server-2016-knowledge-articles.md) +# [Machine Translation service in SharePoint Server 2016](articles/machine-translation-service-in-sharepoint-server-2016-knowledge-articles.md) +# [Search in SharePoint Server 2016](articles/search-in-sharepoint-server-2016-knowledge-articles-for-systems-center-operation.md) +# [Visio Services in SharePoint Server 2016](articles/visio-services-in-sharepoint-server-2016-knowledge-articles.md) +# [Database types and descriptions](articles/database-types-and-descriptions-in-sharepoint-server.md) +# [SharePoint Health Analyzer rules reference](articles/sharepoint-health-analyzer-rules-reference-for-sharepoint-server-2016.md) + ## [A State Service Application has no database defined](articles/a-state-service-application-has-no-database-defined-sharepoint-server-2016.md) + ## [Accounts used by application pools or service identities are in the local machine Administrators group](articles/accounts-used-by-application-pools-or-service-identities-are-in-the-local-machin.md) + ## [All State Service databases are paused for a State Service Application](articles/all-state-service-databases-are-paused-for-a-state-service-application-sharepoin.md) + ## [Alternate access URLs have not been configured](articles/alternate-access-urls-have-not-been-configured-sharepoint-server-2016.md) + ## [Application pools recycle when memory limits are exceeded](articles/application-pools-recycle-when-memory-limits-are-exceeded-sharepoint-server-2016.md) + ## [Business Data Connectivity connectors are currently enabled in a partitioned environment](articles/business-data-connectivity-connectors-are-currently-enabled-in-a-partitioned-env.md) + ## [Cached objects have been evicted](articles/cached-objects-have-been-evicted-sharepoint-server-2016.md) + ## [Content databases contain orphaned Apps](articles/content-databases-contain-orphaned-apps-sharepoint-server-2016.md) + ## [Critical state of this rule indicates that the Word Automation Services is not running when it should be running](articles/critical-state-of-this-rule-indicates-that-the-word-automation-services-is-not-r.md) + ## [Database has large amounts of unused space](articles/database-has-large-amounts-of-unused-space-sharepoint-server-2016.md) + ## [Databases exist on servers running SharePoint Foundation](articles/databases-exist-on-servers-running-sharepoint-foundation-sharepointserver-2016.md) + ## [Databases require upgrade or not supported](articles/databases-require-upgrade-or-not-supported-sharepoint-server-2016.md) + ## [Databases running in compatibility range, upgrade recommended](articles/databases-running-in-compatibility-range-upgrade-recommended-sharepoint-server-2.md) + ## [Databases within this farm are set to read only and will fail to upgrade unless it is set to a read-write state](articles/databases-within-this-farm-are-set-to-read-only-and-will-fail-to-upgrade-unless.md) + ## [Databases used by SharePoint have outdated index statistics](articles/databases-used-by-sharepoint-have-outdated-index-statistics-sharepoint-server-20.md) + ## [Dedicated crawl target configuration has one or more invalid servers](articles/dedicated-crawl-target-configuration-has-one-or-more-invalid-servers-sharepoint.md) + ## [Distributed cache service is not configured on server(s)](articles/distributed-cache-service-is-not-configured-on-server-s.md) + ## [Distributed cache service is not enabled in this deployment](articles/distributed-cache-service-is-not-enabled-in-this-deployment-sharepoint-server-20.md) + ## [Distributed cache service is unexpectedly configured on server(s)](articles/distributed-cache-service-is-unexpectedly-configured-on-server-s.md) + ## [Drives used for SQL databases are running out of free space](articles/drives-used-for-sql-databases-are-running-out-of-free-space-sharepoint-server-20.md) + ## [Expired sessions are not being deleted from the ASP.NET Session State database](articles/expired-sessions-are-not-being-deleted-from-the-asp-net-session-state-database-s.md) + ## [Firewall client settings on the cache host are incorrect](articles/firewall-client-settings-on-the-cache-host-are-incorrect-sharepoint-server-2016.md) + ## [Immediate translations for the Machine Translation service are disabled](articles/immediate-translations-for-the-machine-translation-service-are-disabled-sharepoi.md) + ## [InfoPath form library forms cannot be filled out in a Web browser](articles/infopath-form-library-forms-cannot-be-filled-out-in-a-web-browser-sharepoint-ser.md) + ## [InfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured](articles/infopath-forms-services-forms-cannot-be-filled-out-in-a-web-browser-because-no-s.md) + ## [More cache hosts are running in this deployment than are registered with SharePoint](articles/more-cache-hosts-are-running-in-this-deployment-than-are-registered-with-sharepo.md) + ## [One of the cache hosts in the cluster is down](articles/one-of-the-cache-hosts-in-the-cluster-is-down-sharepoint-server-2016.md) + ## [One or more servers is not responding](articles/one-or-more-servers-is-not-responding-sharepoint-server-2016.md) + ## [One or more web applications are configured to use Windows Classic authentication](articles/one-or-more-web-applications-are-configured-to-use-windows-classic-authenticatio.md) + ## [People Search relevance is not optimized when the Active Directory has errors in the manager reporting structure](articles/people-search-relevance-is-not-optimized-when-the-active-directory-has-errors-in.md) + ## [Product / patch installation or server upgrade required](articles/productpatch-installation-or-server-upgrade-required-sharepoint-server-2016.md) + ## [Search - One or more crawl databases may have fragmented indices](articles/searchone-or-more-crawl-databases-may-have-fragmented-indices-sharepoint-server.md) + ## [Some content databases are growing too large](articles/some-content-databases-are-growing-too-large-sharepoint-server-2016.md) + ## [The Application Discovery and Load Balancer Service is not running in this farm](articles/the-application-discovery-and-load-balancer-service-is-not-running-in-this-farm.md) + ## [The InfoPath Forms Services Maintenance Timer Job not enabled](articles/the-infopath-forms-services-maintenance-timer-job-is-not-enabled-sharepoint-serv.md) + ## [The Machine Translation Service is not running when it should be running](articles/the-machine-translation-service-is-not-running-when-it-should-be-running-sharepo.md) + ## [The number of Distributed Cache hosts in the farm exceeds the recommended value.](articles/the-number-of-distributed-cache-hosts-in-the-farm-exceeds-the-recommended-value.md) + ## [The Security Token Service is not available](articles/the-security-token-service-is-not-available-sharepoint-server-2016.md) + ## [The settings for the Machine Translation Service are not within the recommended limits](articles/the-settings-for-the-machine-translation-service-are-not-within-the-recommended.md) + ## [The settings for Word Automation Services are not within the recommended limits](articles/the-settings-for-word-automation-services-are-not-within-the-recommended-limits.md) + ## [The State Service Delete Expired Sessions timer job is not enabled](articles/the-state-service-delete-expired-sessions-timer-job-is-not-enabled-sharepoint-se.md) + ## [The timer service failed to recycle](articles/the-timer-service-failed-to-recycle-sharepoint-server-2016.md) + ## [The unattended Service Account Application ID is not specified or has an invalid value](articles/the-unattended-service-account-application-id-is-not-specified-or-has-an-invalid.md) + ## [The Visio Graphics Service has a maximum cache age setting that will adversely impact performance](articles/the-visio-graphics-service-has-a-maximum-cache-age-setting-that-will-adversely-i.md) + ## [The Visio Graphics Service has a maximum cache size setting that may adversely impact performance](articles/the-visio-graphics-service-has-a-maximum-cache-size-setting-that-may-adversely-i.md) + ## [The Visio Graphics Service has a maximum recalc duration setting that will adversely impact user perceived performance](articles/the-visio-graphics-service-has-a-maximum-recalc-duration-setting-that-will-adver.md) + ## [The Visio Graphics Service has a maximum Web Drawing Size setting that will adversely impact performance](articles/the-visio-graphics-service-has-a-maximum-web-drawing-size-setting-that-will-adve.md) + ## [The Visio Graphics Service has a minimum cache age setting that may cause a security issue](articles/the-visio-graphics-service-has-a-minimum-cache-age-setting-that-may-cause-a-secu.md) + ## [The Visio Graphics Service has a minimum cache age setting that will adversely impact performance](articles/the-visio-graphics-service-has-a-minimum-cache-age-setting-that-will-adversely-i.md) + ## [This Distributed Cache host may cause cache reliability problems](articles/this-distributed-cache-host-may-cause-cache-reliability-problems-sharepoint-serv.md) + ## [Validate the My Site Host and individual My Sites are on a dedicated Web application and separate URL domain](articles/validate-the-my-site-host-and-individual-my-sites-are-on-a-dedicated-web-applica.md) + ## [Verify each User Profile service application has a My Site host configured](articles/verify-each-user-profile-service-application-has-a-my-site-host-configured-share.md) + ## [Verify each User Profile Service Application has an associated Managed Metadata Service Connection](articles/verify-each-user-profile-service-application-has-an-associated-managed-metadata.md) + ## [Verify each User Profile Service Application has an associated Search Service Connection](articles/verify-each-user-profile-service-application-has-an-associated-search-service-co.md) + ## [Verify that OAuth is configured correctly for the Machine Translation Service application](articles/verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-ap.md) + ## [Verify that OAuth is configured correctly for the Machine Translation Service application proxy](articles/verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-ap.md) + ## [Verify that the Activity Feed Timer Job is enabled](articles/verify-that-the-activity-feed-timer-job-is-enabled-sharepoint-server-2016.md) + ## [Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted](articles/verify-that-the-critical-user-profile-application-and-user-profile-proxy-applica.md) + ## [Web Applications using Claims authentication require an update](articles/web-applications-using-claims-authentication-require-an-update-sharepoint-server.md) + ## [Web.config file has incorrect settings for the requestFiltering element](articles/web-config-file-has-incorrect-settings-for-the-requestfiltering-element-sharepoi.md) + ## [Web.config files are not identical on all machines in the farm](articles/web-config-files-are-not-identical-on-all-machines-in-the-farm-sharepoint-server.md) + ## [XLIFF translations for the Machine Translation Service is disabled](articles/xliff-translations-for-the-machine-translation-service-is-disabled-sharepoint-se.md) + ## [The server farm account should not be used for other services](articles/the-server-farm-account-should-not-be-used-for-other-services-sharepoint-server.md) + ## [Databases used by SharePoint have fragmented indices](articles/databases-used-by-sharepoint-have-fragmented-indices-sharepoint-server-2016.md) + ## [The paging file size should exceed the amount of physical RAM in the system](articles/the-paging-file-size-should-exceed-the-amount-of-physical-ram-in-the-system-shar.md) + ## [Automatic Update setting inconsistent across farm servers](articles/automatic-update-setting-inconsistent-across-farm-servers-sharepoint-server-2016.md) + ## [Built-in accounts are used as application pool or service identities](articles/built-in-accounts-are-used-as-application-pool-or-service-identities-sharepoint.md) + ## [Missing server side dependencies](articles/missing-server-side-dependencies-sharepoint-server-2016.md) + ## [One or more categories are configured with Verbose trace logging](articles/one-or-more-categories-are-configured-with-verbose-trace-logging-sharepoint-serv.md) + ## [Outbound e-mail has not been configured](articles/outbound-e-mail-has-not-been-configured-sharepoint-server-2016.md) + ## [Server role configuration isn't correct](articles/server-role-configuration-isn-t-correct-sharepoint-server-2016.md) + ## [One or more app domains for web applications aren't configured correctly](articles/one-or-more-app-domains-for-web-applications-aren-t-configured-correctly-sharepo.md) + ## [Drives are running out of free space](articles/drives-are-running-out-of-free-space-sharepoint-server-2016.md) + ## [Drives are at risk of running out of free space](articles/drives-are-at-risk-of-running-out-of-free-space-sharepoint-server-2016.md) + ## [Content databases contain orphaned items](articles/content-databases-contain-orphaned-items-sharepoint-server-2016.md) + ## [The Net.Pipe Listener Adapter isn't available](articles/the-net-pipe-listener-adapter-isn-t-available-sharepoint-server-2016.md) + ## [One or more services have started or stopped unexpectedly](articles/one-or-more-services-have-started-or-stopped-unexpectedly-sharepoint-server-2016.md) + ## [The current server is running low on memory](articles/the-current-server-is-running-low-on-memory-sharepoint-server-2016.md) +# [A State Service Application has no database defined](articles/a-state-service-application-has-no-database-defined-sharepoint-server-2016.md) +# [Accounts used by application pools or service identities are in the local machine Administrators group](articles/accounts-used-by-application-pools-or-service-identities-are-in-the-local-machin.md) +# [All State Service databases are paused for a State Service Application](articles/all-state-service-databases-are-paused-for-a-state-service-application-sharepoin.md) +# [Alternate access URLs have not been configured](articles/alternate-access-urls-have-not-been-configured-sharepoint-server-2016.md) +# [Application pools recycle when memory limits are exceeded](articles/application-pools-recycle-when-memory-limits-are-exceeded-sharepoint-server-2016.md) +# [Business Data Connectivity connectors are currently enabled in a partitioned environment](articles/business-data-connectivity-connectors-are-currently-enabled-in-a-partitioned-env.md) +# [Cached objects have been evicted](articles/cached-objects-have-been-evicted-sharepoint-server-2016.md) +# [Content databases contain orphaned Apps](articles/content-databases-contain-orphaned-apps-sharepoint-server-2016.md) +# [Critical state of this rule indicates that the Word Automation Services is not running when it should be running](articles/critical-state-of-this-rule-indicates-that-the-word-automation-services-is-not-r.md) +# [Database has large amounts of unused space](articles/database-has-large-amounts-of-unused-space-sharepoint-server-2016.md) +# [Databases exist on servers running SharePoint Foundation](articles/databases-exist-on-servers-running-sharepoint-foundation-sharepointserver-2016.md) +# [Databases require upgrade or not supported](articles/databases-require-upgrade-or-not-supported-sharepoint-server-2016.md) +# [Databases running in compatibility range, upgrade recommended](articles/databases-running-in-compatibility-range-upgrade-recommended-sharepoint-server-2.md) +# [Databases within this farm are set to read only and will fail to upgrade unless it is set to a read-write state](articles/databases-within-this-farm-are-set-to-read-only-and-will-fail-to-upgrade-unless.md) +# [Databases used by SharePoint have outdated index statistics](articles/databases-used-by-sharepoint-have-outdated-index-statistics-sharepoint-server-20.md) +# [Dedicated crawl target configuration has one or more invalid servers](articles/dedicated-crawl-target-configuration-has-one-or-more-invalid-servers-sharepoint.md) +# [Distributed cache service is not configured on server(s)](articles/distributed-cache-service-is-not-configured-on-server-s.md) +# [Distributed cache service is not enabled in this deployment](articles/distributed-cache-service-is-not-enabled-in-this-deployment-sharepoint-server-20.md) +# [Distributed cache service is unexpectedly configured on server(s)](articles/distributed-cache-service-is-unexpectedly-configured-on-server-s.md) +# [Drives used for SQL databases are running out of free space](articles/drives-used-for-sql-databases-are-running-out-of-free-space-sharepoint-server-20.md) +# [Expired sessions are not being deleted from the ASP.NET Session State database](articles/expired-sessions-are-not-being-deleted-from-the-asp-net-session-state-database-s.md) +# [Firewall client settings on the cache host are incorrect](articles/firewall-client-settings-on-the-cache-host-are-incorrect-sharepoint-server-2016.md) +# [Immediate translations for the Machine Translation service are disabled](articles/immediate-translations-for-the-machine-translation-service-are-disabled-sharepoi.md) +# [InfoPath form library forms cannot be filled out in a Web browser](articles/infopath-form-library-forms-cannot-be-filled-out-in-a-web-browser-sharepoint-ser.md) +# [InfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured](articles/infopath-forms-services-forms-cannot-be-filled-out-in-a-web-browser-because-no-s.md) +# [More cache hosts are running in this deployment than are registered with SharePoint](articles/more-cache-hosts-are-running-in-this-deployment-than-are-registered-with-sharepo.md) +# [One of the cache hosts in the cluster is down](articles/one-of-the-cache-hosts-in-the-cluster-is-down-sharepoint-server-2016.md) +# [One or more servers is not responding](articles/one-or-more-servers-is-not-responding-sharepoint-server-2016.md) +# [One or more web applications are configured to use Windows Classic authentication](articles/one-or-more-web-applications-are-configured-to-use-windows-classic-authenticatio.md) +# [People Search relevance is not optimized when the Active Directory has errors in the manager reporting structure](articles/people-search-relevance-is-not-optimized-when-the-active-directory-has-errors-in.md) +# [Product / patch installation or server upgrade required](articles/productpatch-installation-or-server-upgrade-required-sharepoint-server-2016.md) +# [Search - One or more crawl databases may have fragmented indices](articles/searchone-or-more-crawl-databases-may-have-fragmented-indices-sharepoint-server.md) +# [Some content databases are growing too large](articles/some-content-databases-are-growing-too-large-sharepoint-server-2016.md) +# [The Application Discovery and Load Balancer Service is not running in this farm](articles/the-application-discovery-and-load-balancer-service-is-not-running-in-this-farm.md) +# [The InfoPath Forms Services Maintenance Timer Job not enabled](articles/the-infopath-forms-services-maintenance-timer-job-is-not-enabled-sharepoint-serv.md) +# [The Machine Translation Service is not running when it should be running](articles/the-machine-translation-service-is-not-running-when-it-should-be-running-sharepo.md) +# [The number of Distributed Cache hosts in the farm exceeds the recommended value.](articles/the-number-of-distributed-cache-hosts-in-the-farm-exceeds-the-recommended-value.md) +# [The Security Token Service is not available](articles/the-security-token-service-is-not-available-sharepoint-server-2016.md) +# [The settings for the Machine Translation Service are not within the recommended limits](articles/the-settings-for-the-machine-translation-service-are-not-within-the-recommended.md) +# [The settings for Word Automation Services are not within the recommended limits](articles/the-settings-for-word-automation-services-are-not-within-the-recommended-limits.md) +# [The State Service Delete Expired Sessions timer job is not enabled](articles/the-state-service-delete-expired-sessions-timer-job-is-not-enabled-sharepoint-se.md) +# [The timer service failed to recycle](articles/the-timer-service-failed-to-recycle-sharepoint-server-2016.md) +# [The unattended Service Account Application ID is not specified or has an invalid value](articles/the-unattended-service-account-application-id-is-not-specified-or-has-an-invalid.md) +# [The Visio Graphics Service has a maximum cache age setting that will adversely impact performance](articles/the-visio-graphics-service-has-a-maximum-cache-age-setting-that-will-adversely-i.md) +# [The Visio Graphics Service has a maximum cache size setting that may adversely impact performance](articles/the-visio-graphics-service-has-a-maximum-cache-size-setting-that-may-adversely-i.md) +# [The Visio Graphics Service has a maximum recalc duration setting that will adversely impact user perceived performance](articles/the-visio-graphics-service-has-a-maximum-recalc-duration-setting-that-will-adver.md) +# [The Visio Graphics Service has a maximum Web Drawing Size setting that will adversely impact performance](articles/the-visio-graphics-service-has-a-maximum-web-drawing-size-setting-that-will-adve.md) +# [The Visio Graphics Service has a minimum cache age setting that may cause a security issue](articles/the-visio-graphics-service-has-a-minimum-cache-age-setting-that-may-cause-a-secu.md) +# [The Visio Graphics Service has a minimum cache age setting that will adversely impact performance](articles/the-visio-graphics-service-has-a-minimum-cache-age-setting-that-will-adversely-i.md) +# [This Distributed Cache host may cause cache reliability problems](articles/this-distributed-cache-host-may-cause-cache-reliability-problems-sharepoint-serv.md) +# [Validate the My Site Host and individual My Sites are on a dedicated Web application and separate URL domain](articles/validate-the-my-site-host-and-individual-my-sites-are-on-a-dedicated-web-applica.md) +# [Verify each User Profile service application has a My Site host configured](articles/verify-each-user-profile-service-application-has-a-my-site-host-configured-share.md) +# [Verify each User Profile Service Application has an associated Managed Metadata Service Connection](articles/verify-each-user-profile-service-application-has-an-associated-managed-metadata.md) +# [Verify each User Profile Service Application has an associated Search Service Connection](articles/verify-each-user-profile-service-application-has-an-associated-search-service-co.md) +# [Verify that OAuth is configured correctly for the Machine Translation Service application](articles/verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-ap.md) +# [Verify that OAuth is configured correctly for the Machine Translation Service application proxy](articles/verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-ap.md) +# [Verify that the Activity Feed Timer Job is enabled](articles/verify-that-the-activity-feed-timer-job-is-enabled-sharepoint-server-2016.md) +# [Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted](articles/verify-that-the-critical-user-profile-application-and-user-profile-proxy-applica.md) +# [Web Applications using Claims authentication require an update](articles/web-applications-using-claims-authentication-require-an-update-sharepoint-server.md) +# [Web.config file has incorrect settings for the requestFiltering element](articles/web-config-file-has-incorrect-settings-for-the-requestfiltering-element-sharepoi.md) +# [Web.config files are not identical on all machines in the farm](articles/web-config-files-are-not-identical-on-all-machines-in-the-farm-sharepoint-server.md) +# [XLIFF translations for the Machine Translation Service is disabled](articles/xliff-translations-for-the-machine-translation-service-is-disabled-sharepoint-se.md) +# [The server farm account should not be used for other services](articles/the-server-farm-account-should-not-be-used-for-other-services-sharepoint-server.md) +# [Databases used by SharePoint have fragmented indices](articles/databases-used-by-sharepoint-have-fragmented-indices-sharepoint-server-2016.md) +# [The paging file size should exceed the amount of physical RAM in the system](articles/the-paging-file-size-should-exceed-the-amount-of-physical-ram-in-the-system-shar.md) +# [Automatic Update setting inconsistent across farm servers](articles/automatic-update-setting-inconsistent-across-farm-servers-sharepoint-server-2016.md) +# [Built-in accounts are used as application pool or service identities](articles/built-in-accounts-are-used-as-application-pool-or-service-identities-sharepoint.md) +# [Missing server side dependencies](articles/missing-server-side-dependencies-sharepoint-server-2016.md) +# [One or more categories are configured with Verbose trace logging](articles/one-or-more-categories-are-configured-with-verbose-trace-logging-sharepoint-serv.md) +# [Outbound e-mail has not been configured](articles/outbound-e-mail-has-not-been-configured-sharepoint-server-2016.md) +# [Server role configuration isn't correct](articles/server-role-configuration-isn-t-correct-sharepoint-server-2016.md) +# [One or more app domains for web applications aren't configured correctly](articles/one-or-more-app-domains-for-web-applications-aren-t-configured-correctly-sharepo.md) +# [Drives are running out of free space](articles/drives-are-running-out-of-free-space-sharepoint-server-2016.md) +# [Drives are at risk of running out of free space](articles/drives-are-at-risk-of-running-out-of-free-space-sharepoint-server-2016.md) +# [Content databases contain orphaned items](articles/content-databases-contain-orphaned-items-sharepoint-server-2016.md) +# [The Net.Pipe Listener Adapter isn't available](articles/the-net-pipe-listener-adapter-isn-t-available-sharepoint-server-2016.md) +# [One or more services have started or stopped unexpectedly](articles/one-or-more-services-have-started-or-stopped-unexpectedly-sharepoint-server-2016.md) +# [The current server is running low on memory](articles/the-current-server-is-running-low-on-memory-sharepoint-server-2016.md) +# [Timer job reference](articles/timer-job-reference-for-sharepoint-server-2016.md) +# [Search technical reference](articles/search-technical-reference-for-sharepoint-server.md) + ## [Default crawled file name extensions and parsed file types](articles/default-crawled-file-name-extensions-and-parsed-file-types-in-sharepoint-server.md) + ## [Default connectors](articles/default-connectors-in-sharepoint-server.md) + ## [Linguistic search features](articles/linguistic-search-features-in-sharepoint-server.md) + ## [Query variables](articles/query-variables-in-sharepoint-server.md) + ## [Result types and display templates that are used to display search results](articles/result-types-and-display-templates-that-are-used-to-display-search-results-in-sh.md) + ## [Supported and unsupported Documentum object types and properties](articles/supported-and-unsupported-documentum-object-types-and-properties-in-sharepoint-s.md) +# [Default crawled file name extensions and parsed file types](articles/default-crawled-file-name-extensions-and-parsed-file-types-in-sharepoint-server.md) +# [Default connectors](articles/default-connectors-in-sharepoint-server.md) +# [Linguistic search features](articles/linguistic-search-features-in-sharepoint-server.md) +# [Query variables](articles/query-variables-in-sharepoint-server.md) +# [Result types and display templates that are used to display search results](articles/result-types-and-display-templates-that-are-used-to-display-search-results-in-sh.md) +# [Supported and unsupported Documentum object types and properties](articles/supported-and-unsupported-documentum-object-types-and-properties-in-sharepoint-s.md) +# [Security for SharePoint Server](articles/security-for-sharepoint-server.md) + ## [Plan authentication](articles/plan-authentication-in-sharepoint-server.md) + ## [Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocol support in SharePoint Server 2016](articles/secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sh.md) + ## [Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocol support in SharePoint 2013](articles/secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sh.md) + ## [Enable TLS 1.1 and TLS 1.2 support in SharePoint Server 2016](articles/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2016.md) + ## [Enable TLS and SSL support in SharePoint 2013](articles/enable-tls-and-ssl-support-in-sharepoint-2013.md) + ## [Security hardening](articles/plan-security-hardening-for-sharepoint-server-2016.md) +# [Plan authentication](articles/plan-authentication-in-sharepoint-server.md) + ## [Authentication overview](articles/authentication-overview-for-sharepoint-server.md) + ## [Plan user authentication](articles/plan-for-user-authentication-methods-in-sharepoint-server.md) + ## [Plan server-to-server authentication](articles/plan-for-server-to-server-authentication-in-sharepoint-server.md) + ## [Server-to-server authentication and user profiles](articles/server-to-server-authentication-and-user-profiles-in-sharepoint-server.md) + ## [Kerberos authentication planning](articles/plan-for-kerberos-authentication-in-sharepoint-server.md) + ## [Plan for app authentication in SharePoint Server](articles/plan-for-app-authentication-in-sharepoint-server.md) +# [Authentication overview](articles/authentication-overview-for-sharepoint-server.md) +# [Plan user authentication](articles/plan-for-user-authentication-methods-in-sharepoint-server.md) +# [Plan server-to-server authentication](articles/plan-for-server-to-server-authentication-in-sharepoint-server.md) +# [Server-to-server authentication and user profiles](articles/server-to-server-authentication-and-user-profiles-in-sharepoint-server.md) +# [Kerberos authentication planning](articles/plan-for-kerberos-authentication-in-sharepoint-server.md) +# [Plan for app authentication in SharePoint Server](articles/plan-for-app-authentication-in-sharepoint-server.md) +# [Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocol support in SharePoint Server 2016](articles/secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sh.md) +# [Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocol support in SharePoint 2013](articles/secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sh.md) +# [Enable TLS 1.1 and TLS 1.2 support in SharePoint Server 2016](articles/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2016.md) +# [Enable TLS and SSL support in SharePoint 2013](articles/enable-tls-and-ssl-support-in-sharepoint-2013.md) +# [Security hardening](articles/plan-security-hardening-for-sharepoint-server-2016.md) +# [Scenarios and solutions](articles/solutions-for-the-real-world-in-sharepoint-server.md) + ## [Test lab guides](articles/test-lab-guides-for-sharepoint-server-2013.md) + ## [Integrate Yammer with on-premises SharePoint 2013 environments](articles/integrate-yammer-with-on-premises-sharepoint-2013-environments.md) +# [Test lab guides](articles/test-lab-guides-for-sharepoint-server-2013.md) + ## [Configure SharePoint Server 2013 in a three-tier farm](articles/test-lab-guide-configure-sharepoint-server-2013-in-a-three-tier-farm.md) + ## [Configure intranet and team sites](articles/test-lab-guide-configure-intranet-and-team-sites-for-sharepoint-server-2013.md) + ## [Demonstrate forms-based claims authentication](articles/test-lab-guide-demonstrate-forms-based-claims-authentication-for-sharepoint-serv.md) + ## [Demonstrate profile synchronization](articles/test-lab-guide-demonstrate-profile-synchronization-for-sharepoint-server-2013.md) + ## [Demonstrate SAML-based claims authentication](articles/test-lab-guide-demonstrate-saml-based-claims-authentication-with-sharepoint-serv.md) + ## [Demonstrate social features](articles/test-lab-guide-demonstrate-social-features-for-sharepoint-server-2013.md) +# [Configure SharePoint Server 2013 in a three-tier farm](articles/test-lab-guide-configure-sharepoint-server-2013-in-a-three-tier-farm.md) +# [Configure intranet and team sites](articles/test-lab-guide-configure-intranet-and-team-sites-for-sharepoint-server-2013.md) +# [Demonstrate forms-based claims authentication](articles/test-lab-guide-demonstrate-forms-based-claims-authentication-for-sharepoint-serv.md) +# [Demonstrate profile synchronization](articles/test-lab-guide-demonstrate-profile-synchronization-for-sharepoint-server-2013.md) +# [Demonstrate SAML-based claims authentication](articles/test-lab-guide-demonstrate-saml-based-claims-authentication-with-sharepoint-serv.md) +# [Demonstrate social features](articles/test-lab-guide-demonstrate-social-features-for-sharepoint-server-2013.md) +# [Integrate Yammer with on-premises SharePoint 2013 environments](articles/integrate-yammer-with-on-premises-sharepoint-2013-environments.md) + ## [Yammer networks, groups, and users overview](articles/yammer-networks-groups-and-users-overview.md) + ## [Social scenarios with Yammer and SharePoint Server 2013](articles/social-scenarios-with-yammer-and-sharepoint-server-2013.md) + ## [Add Yammer to the navigation bar for SharePoint 2013](articles/add-yammer-to-the-navigation-bar-for-sharepoint-2013.md) + ## [Hide SharePoint Server 2013 social features](articles/hide-sharepoint-server-2013-social-features.md) + ## [Get and install the Yammer app onto SharePoint Server 2013 sites](articles/get-and-install-the-yammer-app-onto-sharepoint-server-2013-sites.md) + ## [Add the Yammer Embed widget to a SharePoint page](articles/add-the-yammer-embed-widget-to-a-sharepoint-page.md) +# [Yammer networks, groups, and users overview](articles/yammer-networks-groups-and-users-overview.md) +# [Social scenarios with Yammer and SharePoint Server 2013](articles/social-scenarios-with-yammer-and-sharepoint-server-2013.md) + ## [Integrate a new Yammer network into SharePoint Server 2013](articles/integrate-a-new-yammer-network-into-sharepoint-server-2013.md) + ## [Integrate a single Yammer network into SharePoint Server 2013](articles/integrate-a-single-yammer-network-into-sharepoint-server-2013.md) + ## [Integrate multiple Yammer networks into SharePoint Server 2013](articles/integrate-multiple-yammer-networks-into-sharepoint-server-2013.md) + ## [Integrate a Yammer network into SharePoint Server 2013 with social features](articles/integrate-a-yammer-network-into-sharepoint-server-2013-with-social-features.md) + ## [Integrate a Yammer network into SharePoint Server 2013 and Office 365](articles/integrate-a-yammer-network-into-sharepoint-server-2013-and-office-365.md) +# [Integrate a new Yammer network into SharePoint Server 2013](articles/integrate-a-new-yammer-network-into-sharepoint-server-2013.md) +# [Integrate a single Yammer network into SharePoint Server 2013](articles/integrate-a-single-yammer-network-into-sharepoint-server-2013.md) +# [Integrate multiple Yammer networks into SharePoint Server 2013](articles/integrate-multiple-yammer-networks-into-sharepoint-server-2013.md) +# [Integrate a Yammer network into SharePoint Server 2013 with social features](articles/integrate-a-yammer-network-into-sharepoint-server-2013-with-social-features.md) +# [Integrate a Yammer network into SharePoint Server 2013 and Office 365](articles/integrate-a-yammer-network-into-sharepoint-server-2013-and-office-365.md) +# [Add Yammer to the navigation bar for SharePoint 2013](articles/add-yammer-to-the-navigation-bar-for-sharepoint-2013.md) +# [Hide SharePoint Server 2013 social features](articles/hide-sharepoint-server-2013-social-features.md) +# [Get and install the Yammer app onto SharePoint Server 2013 sites](articles/get-and-install-the-yammer-app-onto-sharepoint-server-2013-sites.md) +# [Add the Yammer Embed widget to a SharePoint page](articles/add-the-yammer-embed-widget-to-a-sharepoint-page.md) diff --git a/SharePoint/SharePoint16ITPro_Errors_Found.csv b/SharePoint/SharePoint16ITPro_Errors_Found.csv new file mode 100644 index 0000000000..face8af7c2 --- /dev/null +++ b/SharePoint/SharePoint16ITPro_Errors_Found.csv @@ -0,0 +1,1171 @@ +Error Type,Topic Guid,Message +Warning,00c33e26-dacb-47d4-97b8-84659095b108,Found a an ul list inside a table in html file:00c33e26-dacb-47d4-97b8-84659095b108.xml +Warning,00c33e26-dacb-47d4-97b8-84659095b108,Found nested table in md file:00c33e26-dacb-47d4-97b8-84659095b108.md +Warning,0112182a-6246-4d8a-8c07-39622be3c4a1,Found a an ul list inside a table in html file:0112182a-6246-4d8a-8c07-39622be3c4a1.xml +Warning,0112182a-6246-4d8a-8c07-39622be3c4a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<

in md file:0112182a-6246-4d8a-8c07-39622be3c4a1.md total found:0 +Warning,0317c126-78ed-47e0-9109-fe143ddb0259,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDbName> in md file:0317c126-78ed-47e0-9109-fe143ddb0259.md total found:0 +Warning,0317c126-78ed-47e0-9109-fe143ddb0259,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDbName> in md file:0317c126-78ed-47e0-9109-fe143ddb0259.md total found:0 +Warning,0317c126-78ed-47e0-9109-fe143ddb0259,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewProvider> in md file:0317c126-78ed-47e0-9109-fe143ddb0259.md total found:0 +Warning,0317c126-78ed-47e0-9109-fe143ddb0259,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewProvider> in md file:0317c126-78ed-47e0-9109-fe143ddb0259.md total found:0 +Warning,04812402-43d6-4605-960c-1dd5ec65bef1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

There is a highly consistent intra-farm latency of <1ms (one way)- 99.9% of the time over a period of ten minutes. (Intra-farm latency is commonly defined as the latency between the front-end web servers and the database servers.)

in md file:04812402-43d6-4605-960c-1dd5ec65bef1.md total found:0 +Warning,04812402-43d6-4605-960c-1dd5ec65bef1,Found nested table in md file:04812402-43d6-4605-960c-1dd5ec65bef1.md +Warning,055e27eb-3e02-4470-a037-5896bab44736,Found a an ul list inside a table in html file:055e27eb-3e02-4470-a037-5896bab44736.xml +Warning,055e27eb-3e02-4470-a037-5896bab44736,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Path> in md file:055e27eb-3e02-4470-a037-5896bab44736.md total found:0 +Warning,055e27eb-3e02-4470-a037-5896bab44736,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Dictionary name> in md file:055e27eb-3e02-4470-a037-5896bab44736.md total found:0 +Warning,055e27eb-3e02-4470-a037-5896bab44736,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<no index> in md file:055e27eb-3e02-4470-a037-5896bab44736.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found a an ul list inside a table in html file:056e74ea-9428-45f8-abed-1040d8e413dd.xml +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Set your Azure subscription with the following commands. Set the $subscr variable by replacing everything within the quotes- including the < and > characters- with the correct name.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Create your new resource group with these commands. Set the variables by replacing everything within the quotes- including the < and > characters- with the correct names.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In the Azure portal- click Resource Groups > <the name of your new resource group> > adVM > Connect .

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In Windows Security - click Use another account . In User name - type adVM\ <ADMIN_NAME>.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In the Azure portal- click Resource Groups > <your resource group name> > adVM > Connect .

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In Windows Security - click Use another account . In User name - type CORP\ <ADMIN_NAME>.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Note that you must supply domain account credentials after entering the Add-Computer command. Use the CORP\<ADMIN_NAME> account and password.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In Login name - type CORP\ <ADMIN_NAME>.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Note that you must supply domain account credentials after entering the Add-Compute r command. Use the CORP\<ADMIN_NAME> account name and password.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

After the SharePoint virtual machine restarts- reconnect to it using the CORP\<ADMIN_NAME> account name and password.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

On the Edit Public Zone URLs page- in Internet - type http:// <the DNS name from step 2>- and then click Save .

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,056e74ea-9428-45f8-abed-1040d8e413dd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

From a browser on your local computer- access http:// < DNS name of the spVM virtual machine>. When prompted from credentials- use the CORP\<ADMIN_NAME> account name and password. You should see the default Contoso team site.

in md file:056e74ea-9428-45f8-abed-1040d8e413dd.md total found:0 +Warning,062b6ff7-a4ee-408f-811e-fdba45ca3c08,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 25 (Megabytes)

in md file:062b6ff7-a4ee-408f-811e-fdba45ca3c08.md total found:0 +Warning,062b6ff7-a4ee-408f-811e-fdba45ca3c08,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Minutes)

in md file:062b6ff7-a4ee-408f-811e-fdba45ca3c08.md total found:0 +Warning,062b6ff7-a4ee-408f-811e-fdba45ca3c08,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Seconds)

in md file:062b6ff7-a4ee-408f-811e-fdba45ca3c08.md total found:0 +Warning,06765032-fedb-4b73-a019-f096b48cd2a8,Found a an ul list inside a table in html file:06765032-fedb-4b73-a019-f096b48cd2a8.xml +Warning,06765032-fedb-4b73-a019-f096b48cd2a8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

MSSQL<InstanceName>

in md file:06765032-fedb-4b73-a019-f096b48cd2a8.md total found:0 +Warning,06765032-fedb-4b73-a019-f096b48cd2a8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

SQLAgent<InstanceName>

in md file:06765032-fedb-4b73-a019-f096b48cd2a8.md total found:0 +Warning,06765032-fedb-4b73-a019-f096b48cd2a8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

If you plan to back up to or restore from an external resource- permissions to the external resource must be granted to the appropriate account. If you use a domain user account for the SQL Server service account- grant permissions to that domain user account. However- if you use the Network Service or the Local System account- grant permissions to the external resource to the machine account (<domain_name>\<SQL_hostname>).

in md file:06765032-fedb-4b73-a019-f096b48cd2a8.md total found:0 +Warning,067783ba-e22f-41a8-9a1b-38a89c3a30c2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Database role membership for: <database> in md file:067783ba-e22f-41a8-9a1b-38a89c3a30c2.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourWebPartName> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourWebPartName> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourWebPartNamespace> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourWebPartName> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourWebPartNamespace> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<PathToCabFile> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebPartName> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<PathToCabFile> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebPartName> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MyServer> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MyServer> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0810018d-188b-4d42-b908-d794faeacd0a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourWebPartNamespace>.<YourWebPartName> in md file:0810018d-188b-4d42-b908-d794faeacd0a.md total found:0 +Warning,0853bed9-1084-413b-bf91-427dc643a5e5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Database role membership for: <database> in md file:0853bed9-1084-413b-bf91-427dc643a5e5.md total found:0 +Warning,0889004d-6820-4282-a63c-863f4796ff85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDbName> in md file:0889004d-6820-4282-a63c-863f4796ff85.md total found:0 +Warning,0889004d-6820-4282-a63c-863f4796ff85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationName> in md file:0889004d-6820-4282-a63c-863f4796ff85.md total found:0 +Warning,0889004d-6820-4282-a63c-863f4796ff85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDbName> in md file:0889004d-6820-4282-a63c-863f4796ff85.md total found:0 +Warning,0889004d-6820-4282-a63c-863f4796ff85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationName> in md file:0889004d-6820-4282-a63c-863f4796ff85.md total found:0 +Warning,0926f63d-8dae-44c0-9e91-51209aa4c3ef,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Where <ServerRole> can be any of the following values: WebFrontEnd- Application- DistributedCache- Search- or Custom.

in md file:0926f63d-8dae-44c0-9e91-51209aa4c3ef.md total found:0 +Warning,0926f63d-8dae-44c0-9e91-51209aa4c3ef,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<$DatabaseServer> in md file:0926f63d-8dae-44c0-9e91-51209aa4c3ef.md total found:0 +Warning,0926f63d-8dae-44c0-9e91-51209aa4c3ef,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:0926f63d-8dae-44c0-9e91-51209aa4c3ef.md total found:0 +Warning,0926f63d-8dae-44c0-9e91-51209aa4c3ef,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<$Passphrase> in md file:0926f63d-8dae-44c0-9e91-51209aa4c3ef.md total found:0 +Warning,0926f63d-8dae-44c0-9e91-51209aa4c3ef,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerRole> in md file:0926f63d-8dae-44c0-9e91-51209aa4c3ef.md total found:0 +Warning,0926f63d-8dae-44c0-9e91-51209aa4c3ef,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Where <ServerRole> can be any of the following values: WebFrontEnd- Application- DistributedCache- Search- or Custom.

in md file:0926f63d-8dae-44c0-9e91-51209aa4c3ef.md total found:0 +Warning,0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<RBS installation path> in md file:0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5.md total found:0 +Warning,0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<RBS installation directory>\ in md file:0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5.md total found:0 +Warning,0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<version> in md file:0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5.md total found:0 +Warning,0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Under Settings - in the Program/script box- browse to the Maintainer binary file <RBS installation directory> \Maintainer\Microsoft.Data.SqlRemoteBlobs.Maintainer.exe- and in the Add arguments (optional) text box- add any optional arguments. The following default values are created by the installer:
<-ConnectionStringName RBSMaintainerConnection>
<-Operation GarbageCollection ConsistencyCheck ConsistencyCheckForStores>
<-GarbageCollectionPhases rdo>
<-ConsistencyCheckMode r>
<-TimeLimit 120>

in md file:0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5.md total found:0 +Warning,0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<RBS installation directory> in md file:0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5.md total found:0 +Warning,0b6e5490-ea92-4e6d-b2fe-743d06a4c3e6,Found a an ul list inside a table in html file:0b6e5490-ea92-4e6d-b2fe-743d06a4c3e6.xml +Warning,0b6e5490-ea92-4e6d-b2fe-743d06a4c3e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:http://www.<site>/search/results.aspx?k={subjectTerms} in md file:0b6e5490-ea92-4e6d-b2fe-743d06a4c3e6.md total found:0 +Warning,0b6e5490-ea92-4e6d-b2fe-743d06a4c3e6,Missing tables headers in file:0b6e5490-ea92-4e6d-b2fe-743d06a4c3e6.md +Warning,0bba350d-ec33-43db-a873-930559c78dee,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Your company's or organization’s SharePoint Online portal URL- such as https://<yourtenantname>.sharepoint.com

in md file:0bba350d-ec33-43db-a873-930559c78dee.md total found:0 +Warning,0bba350d-ec33-43db-a873-930559c78dee,Missing tables headers in file:0bba350d-ec33-43db-a873-930559c78dee.md +Warning,0d326419-25c2-4591-acc6-9e487aa80c6e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<FormsMaintenanceJobDefinition> in md file:0d326419-25c2-4591-acc6-9e487aa80c6e.md total found:0 +Warning,0d326419-25c2-4591-acc6-9e487aa80c6e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<FormsMaintenanceJobDefintion> in md file:0d326419-25c2-4591-acc6-9e487aa80c6e.md total found:0 +Warning,0ed3c559-86c1-40d0-8804-8adb7038492f,Missing tables headers in file:0ed3c559-86c1-40d0-8804-8adb7038492f.md +Warning,0fb9616f-3877-4ba8-a7a7-9f00b6d896cb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPTimerJobPipeBind> in md file:0fb9616f-3877-4ba8-a7a7-9f00b6d896cb.md total found:0 +Warning,0fb9616f-3877-4ba8-a7a7-9f00b6d896cb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ScheduleString> in md file:0fb9616f-3877-4ba8-a7a7-9f00b6d896cb.md total found:0 +Warning,0fb9616f-3877-4ba8-a7a7-9f00b6d896cb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPTimerJobPipeBind> in md file:0fb9616f-3877-4ba8-a7a7-9f00b6d896cb.md total found:0 +Warning,0fb9616f-3877-4ba8-a7a7-9f00b6d896cb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ScheduleString> in md file:0fb9616f-3877-4ba8-a7a7-9f00b6d896cb.md total found:0 +Warning,0fe9d4a1-faf9-4941-a45a-b54f47a5dea5,Found a an ul list inside a table in html file:0fe9d4a1-faf9-4941-a45a-b54f47a5dea5.xml +Warning,0fe9d4a1-faf9-4941-a45a-b54f47a5dea5,Found nested table in md file:0fe9d4a1-faf9-4941-a45a-b54f47a5dea5.md +Warning,0fe9d4a1-faf9-4941-a45a-b54f47a5dea5,Could not Add new line after images in md file:0fe9d4a1-faf9-4941-a45a-b54f47a5dea5.md +Warning,144baa85-cbd8-45d6-9141-e6e688cac210,Found a an ul list inside a table in html file:144baa85-cbd8-45d6-9141-e6e688cac210.xml +Warning,144e5f6e-0c9c-4f01-9b1f-26190d527e85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DOMAIN> in md file:144e5f6e-0c9c-4f01-9b1f-26190d527e85.md total found:0 +Warning,144e5f6e-0c9c-4f01-9b1f-26190d527e85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<user name> in md file:144e5f6e-0c9c-4f01-9b1f-26190d527e85.md total found:0 +Warning,144e5f6e-0c9c-4f01-9b1f-26190d527e85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In the My Site Managed Path section- enter the part of the path which- when appended to the My Site host URL- will give the path of users' My Sites (see the Profile Synchronization Planning worksheet). For example- if the My Site host URL is http://server:12345/ and you want each user's My Site to be at http://server:12345/personal/<user name>- enter /personal for the My Site managed path. The managed path that you enter is created automatically. There does not already have to be a managed path with the name that you provide.

in md file:144e5f6e-0c9c-4f01-9b1f-26190d527e85.md total found:0 +Warning,144e5f6e-0c9c-4f01-9b1f-26190d527e85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UPSAName> in md file:144e5f6e-0c9c-4f01-9b1f-26190d527e85.md total found:0 +Warning,144e5f6e-0c9c-4f01-9b1f-26190d527e85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UPSAName> in md file:144e5f6e-0c9c-4f01-9b1f-26190d527e85.md total found:0 +Warning,144e5f6e-0c9c-4f01-9b1f-26190d527e85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Permissions for <account> in md file:144e5f6e-0c9c-4f01-9b1f-26190d527e85.md total found:0 +Warning,144e5f6e-0c9c-4f01-9b1f-26190d527e85,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Permissions for <account> in md file:144e5f6e-0c9c-4f01-9b1f-26190d527e85.md total found:0 +Warning,150f0179-b9d4-4823-b314-98b83a95d85e,Missing tables headers in file:150f0179-b9d4-4823-b314-98b83a95d85e.md +Warning,1609167e-e47a-41d6-b8fc-7a8d0ba8f7ce,Could not Add new line after images in md file:1609167e-e47a-41d6-b8fc-7a8d0ba8f7ce.md +Warning,1780ec27-19f8-4d77-b787-8abc23921258,Found nested table in md file:1780ec27-19f8-4d77-b787-8abc23921258.md +Warning,185da9e8-9ed1-4bf1-bfb5-2a5a874f2a19,Found a an ul list inside a table in html file:185da9e8-9ed1-4bf1-bfb5-2a5a874f2a19.xml +Warning,18fedf59-f293-4c15-953e-c42ec66fa13f,Found a an ul list inside a table in html file:18fedf59-f293-4c15-953e-c42ec66fa13f.xml +Warning,18fedf59-f293-4c15-953e-c42ec66fa13f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<instance name> in md file:18fedf59-f293-4c15-953e-c42ec66fa13f.md total found:0 +Warning,18fedf59-f293-4c15-953e-c42ec66fa13f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<instance name> in md file:18fedf59-f293-4c15-953e-c42ec66fa13f.md total found:0 +Warning,18fedf59-f293-4c15-953e-c42ec66fa13f,Found nested table in md file:18fedf59-f293-4c15-953e-c42ec66fa13f.md +Warning,197ce911-c4f6-40a3-84c1-fb5999623b51,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<host n> in md file:197ce911-c4f6-40a3-84c1-fb5999623b51.md total found:0 +Warning,197ce911-c4f6-40a3-84c1-fb5999623b51,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Server name> in md file:197ce911-c4f6-40a3-84c1-fb5999623b51.md total found:0 +Warning,197ce911-c4f6-40a3-84c1-fb5999623b51,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:($<host n>) in md file:197ce911-c4f6-40a3-84c1-fb5999623b51.md total found:0 +Warning,197ce911-c4f6-40a3-84c1-fb5999623b51,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchComponent> in md file:197ce911-c4f6-40a3-84c1-fb5999623b51.md total found:0 +Warning,197ce911-c4f6-40a3-84c1-fb5999623b51,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:$<host n> in md file:197ce911-c4f6-40a3-84c1-fb5999623b51.md total found:0 +Warning,197ce911-c4f6-40a3-84c1-fb5999623b51,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Search component id> in md file:197ce911-c4f6-40a3-84c1-fb5999623b51.md total found:0 +Warning,19d553a7-7001-4b07-a03d-616b865b05ae,Found a an ul list inside a table in html file:19d553a7-7001-4b07-a03d-616b865b05ae.xml +Warning,19d553a7-7001-4b07-a03d-616b865b05ae,Missing tables headers in file:19d553a7-7001-4b07-a03d-616b865b05ae.md +Warning,1ad49d4e-598d-446c-aabd-de4a8f6ad391,Could not Add new line after images in md file:1ad49d4e-598d-446c-aabd-de4a8f6ad391.md +Warning,1bb10de1-2b80-48b3-a9f7-9745cb725e6c,Found a an ul list inside a table in html file:1bb10de1-2b80-48b3-a9f7-9745cb725e6c.xml +Warning,1c030561-e15f-43a0-9ef2-f43e67fb4c67,Could not Add new line after images in md file:1c030561-e15f-43a0-9ef2-f43e67fb4c67.md +Warning,1cd060e0-1eb6-424c-8ade-f8d39cd20d1d,Found a an ul list inside a table in html file:1cd060e0-1eb6-424c-8ade-f8d39cd20d1d.xml +Warning,1cd060e0-1eb6-424c-8ade-f8d39cd20d1d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPTimerJobPipeBind> in md file:1cd060e0-1eb6-424c-8ade-f8d39cd20d1d.md total found:0 +Warning,1cd060e0-1eb6-424c-8ade-f8d39cd20d1d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPTimerJobPipeBind> in md file:1cd060e0-1eb6-424c-8ade-f8d39cd20d1d.md total found:0 +Warning,1cd060e0-1eb6-424c-8ade-f8d39cd20d1d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPTimerJobPipeBind> in md file:1cd060e0-1eb6-424c-8ade-f8d39cd20d1d.md total found:0 +Warning,1cd060e0-1eb6-424c-8ade-f8d39cd20d1d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPTimerJobPipeBind> in md file:1cd060e0-1eb6-424c-8ade-f8d39cd20d1d.md total found:0 +Warning,1e637e17-2634-4601-a574-299a7c27bb24,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteURL> in md file:1e637e17-2634-4601-a574-299a7c27bb24.md total found:0 +Warning,1e637e17-2634-4601-a574-299a7c27bb24,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Path and FileName> in md file:1e637e17-2634-4601-a574-299a7c27bb24.md total found:0 +Warning,1e637e17-2634-4601-a574-299a7c27bb24,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<URL of Site- List- or Library> in md file:1e637e17-2634-4601-a574-299a7c27bb24.md total found:0 +Warning,1e637e17-2634-4601-a574-299a7c27bb24,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

If you receive any errors- you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the <file name>.export.log file at the UNC path that you specified in step 6.

in md file:1e637e17-2634-4601-a574-299a7c27bb24.md total found:0 +Warning,20e1e0c3-7d5c-489c-a588-a11b30adffb9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 25 (Megabytes)

in md file:20e1e0c3-7d5c-489c-a588-a11b30adffb9.md total found:0 +Warning,20e1e0c3-7d5c-489c-a588-a11b30adffb9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Minutes)

in md file:20e1e0c3-7d5c-489c-a588-a11b30adffb9.md total found:0 +Warning,20e1e0c3-7d5c-489c-a588-a11b30adffb9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Seconds)

in md file:20e1e0c3-7d5c-489c-a588-a11b30adffb9.md total found:0 +Warning,237d399e-b50b-42e6-90ff-e659a94d8099,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Farm\Shared Services\Shared Services Applications\<Secure Store Service name> in md file:237d399e-b50b-42e6-90ff-e659a94d8099.md total found:0 +Warning,237d399e-b50b-42e6-90ff-e659a94d8099,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:237d399e-b50b-42e6-90ff-e659a94d8099.md total found:0 +Warning,237d399e-b50b-42e6-90ff-e659a94d8099,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SecureStoreServicename> in md file:237d399e-b50b-42e6-90ff-e659a94d8099.md total found:0 +Warning,237d399e-b50b-42e6-90ff-e659a94d8099,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Passphrase> in md file:237d399e-b50b-42e6-90ff-e659a94d8099.md total found:0 +Warning,240f8caa-afb3-44ce-90bb-861cfa258b09,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:240f8caa-afb3-44ce-90bb-861cfa258b09.md total found:0 +Warning,240f8caa-afb3-44ce-90bb-861cfa258b09,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDatabase> in md file:240f8caa-afb3-44ce-90bb-861cfa258b09.md total found:0 +Warning,2689bb6a-fd05-4273-87eb-daac5b2722f3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UserProfileServiceApplicationName> in md file:2689bb6a-fd05-4273-87eb-daac5b2722f3.md total found:0 +Warning,2689bb6a-fd05-4273-87eb-daac5b2722f3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<URL> in md file:2689bb6a-fd05-4273-87eb-daac5b2722f3.md total found:0 +Warning,2689bb6a-fd05-4273-87eb-daac5b2722f3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UserProfileServiceApplicationName> in md file:2689bb6a-fd05-4273-87eb-daac5b2722f3.md total found:0 +Warning,2689bb6a-fd05-4273-87eb-daac5b2722f3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<URL> in md file:2689bb6a-fd05-4273-87eb-daac5b2722f3.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Ensure that the profile of the migrated user can be accessed by browsing to the My Site for that user- for example- http://mysite/person.aspx?accountname=<new account name>.

in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<identity> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<identity> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Identity> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<newName> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UPSAppProxyGUID> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewTimeout> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UPSAppProxyGUID> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewTimeout> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UPSAppProxyGUID> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UPSAppProxyGUID> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewTimeout> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UPSAppGUID> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewTimeout> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UPSAppGUID> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewTimeout> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<file name> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,26f02074-af0b-4548-ab68-9d46dd05b8ff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<file name> in md file:26f02074-af0b-4548-ab68-9d46dd05b8ff.md total found:0 +Warning,28b06934-933b-4899-a7a6-707eb0516552,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 25 (Megabytes)

in md file:28b06934-933b-4899-a7a6-707eb0516552.md total found:0 +Warning,28b06934-933b-4899-a7a6-707eb0516552,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Minutes)

in md file:28b06934-933b-4899-a7a6-707eb0516552.md total found:0 +Warning,28b06934-933b-4899-a7a6-707eb0516552,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Seconds)

in md file:28b06934-933b-4899-a7a6-707eb0516552.md total found:0 +Warning,29c0bc76-d835-401b-a2fb-abb069e84125,Found a an ul list inside a table in html file:29c0bc76-d835-401b-a2fb-abb069e84125.xml +Warning,29c0bc76-d835-401b-a2fb-abb069e84125,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

"! " # $ % & ' ( ) * + - - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

in md file:29c0bc76-d835-401b-a2fb-abb069e84125.md total found:0 +Warning,29c0bc76-d835-401b-a2fb-abb069e84125,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Use default page : Any Web sites that use the target application to access external data will have an individual sign-up page that was added automatically. The URL of this page will be http:/<samplesite>/_layouts/SecureStoreSetCredentials.aspx?TargetAppId=<TargetApplicationID>- where <TargetApplicationID> is the string typed in the Target Application ID box. By publicizing the location of this page- you can enable users to add their credentials for the external data source.

in md file:29c0bc76-d835-401b-a2fb-abb069e84125.md total found:0 +Warning,2b2c3b2a-49f3-4c96-9efd-0d557f0332db,Found a an ul list inside a table in html file:2b2c3b2a-49f3-4c96-9efd-0d557f0332db.xml +Warning,2b2c3b2a-49f3-4c96-9efd-0d557f0332db,Missing tables headers in file:2b2c3b2a-49f3-4c96-9efd-0d557f0332db.md +Warning,2be5291e-b6cc-4730-bc58-78b14ea1984b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Database role membership for: <database> in md file:2be5291e-b6cc-4730-bc58-78b14ea1984b.md total found:0 +Warning,2c727311-e83e-4f7b-b02c-9a0699a81e64,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Server is listening on [ 'any' <ipv4>50000]

in md file:2c727311-e83e-4f7b-b02c-9a0699a81e64.md total found:0 +Warning,2ce4b90f-5eb0-4d5d-8ddb-3cf00952de4e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

If the farm that can perform server-to-server authentication is on-premises- you must configure the farm that runs SharePoint Server. Use the New-SPTrustedSecurityTokenIssuer  PowerShell cmdlet to add a JavaScript Object Notation (JSON) metadata endpoint of the server that can perform server-to-server authentication to the server that runs SharePoint Server. If the server that can perform server-to-server authentication is another server that runs SharePoint Server- the JSON metadata endpoint is in the format: https://<HostName>/_layouts/15/metadata/json/1.

in md file:2ce4b90f-5eb0-4d5d-8ddb-3cf00952de4e.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{Site.<property>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{SiteCollection.<property>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{Page.<FieldName>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{URLToken.<integer>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{QueryString.<ParameterName>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{Request.<PropertyName>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{User.<property>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{Term.<property>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{List.<property>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{ListItem.<property>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,2d8373ff-0808-40b7-8a21-5534720719f4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

{Today+/- <integer value for number of days>}

in md file:2d8373ff-0808-40b7-8a21-5534720719f4.md total found:0 +Warning,31b74292-9333-455d-8c52-aba97bbfc0e6,Found a an ul list inside a table in html file:31b74292-9333-455d-8c52-aba97bbfc0e6.xml +Warning,32bc4341-ba5f-444b-bd55-462f67f16c27,Could not Add new line after images in md file:32bc4341-ba5f-444b-bd55-462f67f16c27.md +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found a an ul list inside a table in html file:33ed78c8-25fc-48ea-b0c1-50b540213cff.xml +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Path> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Path> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPUsageDefinitionPipeBind> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPUsageDefinitionPipeBind> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServerName> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UserName> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Password> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServerName> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UserName> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Password> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UserName> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,33ed78c8-25fc-48ea-b0c1-50b540213cff,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Password> in md file:33ed78c8-25fc-48ea-b0c1-50b540213cff.md total found:0 +Warning,356d3a0b-fc26-455c-9afb-6d2ffdceef84,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line: + If Setup fails- check log files in the Temp folder of the user account you used to run Setup. Ensure that you are logged in using the same user account and then type %temp% in the location bar in Windows Explorer. If the path in Windows Explorer resolves to a location that ends in a "1" or "2"- you have to navigate up one level to view the log files. The log file name is SharePoint Server Setup (<time stamp >). + in md file:356d3a0b-fc26-455c-9afb-6d2ffdceef84.md total found:0 +Warning,3661eafe-91da-4467-91f1-5fa47947e178,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 25 (Megabytes)

in md file:3661eafe-91da-4467-91f1-5fa47947e178.md total found:0 +Warning,3661eafe-91da-4467-91f1-5fa47947e178,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Minutes)

in md file:3661eafe-91da-4467-91f1-5fa47947e178.md total found:0 +Warning,3661eafe-91da-4467-91f1-5fa47947e178,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Seconds)

in md file:3661eafe-91da-4467-91f1-5fa47947e178.md total found:0 +Warning,38147eec-d89a-478a-956a-779fe76c6679,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:38147eec-d89a-478a-956a-779fe76c6679.md total found:0 +Warning,38147eec-d89a-478a-956a-779fe76c6679,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:38147eec-d89a-478a-956a-779fe76c6679.md total found:0 +Warning,38147eec-d89a-478a-956a-779fe76c6679,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SolutionPath> in md file:38147eec-d89a-478a-956a-779fe76c6679.md total found:0 +Warning,38147eec-d89a-478a-956a-779fe76c6679,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:38147eec-d89a-478a-956a-779fe76c6679.md total found:0 +Warning,38147eec-d89a-478a-956a-779fe76c6679,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:38147eec-d89a-478a-956a-779fe76c6679.md total found:0 +Warning,38147eec-d89a-478a-956a-779fe76c6679,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SolutionPath> in md file:38147eec-d89a-478a-956a-779fe76c6679.md total found:0 +Warning,38147eec-d89a-478a-956a-779fe76c6679,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

The XML definition files (.actions files) are stored in the 16\TEMPLATE\<LCID >\Workflow directory.

in md file:38147eec-d89a-478a-956a-779fe76c6679.md total found:0 +Warning,3a25437a-e994-42c7-b4df-ac9fa29f38f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Database ID> in md file:3a25437a-e994-42c7-b4df-ac9fa29f38f5.md total found:0 +Warning,3a25437a-e994-42c7-b4df-ac9fa29f38f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<User account> in md file:3a25437a-e994-42c7-b4df-ac9fa29f38f5.md total found:0 +Warning,3a25437a-e994-42c7-b4df-ac9fa29f38f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<User account> in md file:3a25437a-e994-42c7-b4df-ac9fa29f38f5.md total found:0 +Warning,3a832d60-f14f-4663-93bd-f006e6148c02,Found nested table in md file:3a832d60-f14f-4663-93bd-f006e6148c02.md +Warning,3adafdd2-f276-4a9d-8a74-e06b8916bbc2,Found a an ul list inside a table in html file:3adafdd2-f276-4a9d-8a74-e06b8916bbc2.xml +Warning,3e3b8737-c6a3-4e2c-a35f-f0095d952b78,Found a an ul list inside a table in html file:3e3b8737-c6a3-4e2c-a35f-f0095d952b78.xml +Warning,3e3b8737-c6a3-4e2c-a35f-f0095d952b78,Missing tables headers in file:3e3b8737-c6a3-4e2c-a35f-f0095d952b78.md +Warning,3e3b8737-c6a3-4e2c-a35f-f0095d952b78,Could not Add new line after images in md file:3e3b8737-c6a3-4e2c-a35f-f0095d952b78.md +Warning,3e61c238-cc09-4369-b8d3-f1150c1ae89b,Found a an ul list inside a table in html file:3e61c238-cc09-4369-b8d3-f1150c1ae89b.xml +Warning,3e61c238-cc09-4369-b8d3-f1150c1ae89b,Found nested table in md file:3e61c238-cc09-4369-b8d3-f1150c1ae89b.md +Warning,3e66d9df-442e-445f-bddc-99b446c2a4cb,Found a an ul list inside a table in html file:3e66d9df-442e-445f-bddc-99b446c2a4cb.xml +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Farm\Shared Services Applications\<Service application> in md file:3e9dcd50-53e6-4471-a969-aeb4d079dfa3.md total found:0 +Warning,3ebcdcdf-593e-44bd-b60d-16efd5f07a16,Found a an ul list inside a table in html file:3ebcdcdf-593e-44bd-b60d-16efd5f07a16.xml +Warning,3ebcdcdf-593e-44bd-b60d-16efd5f07a16,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:https://<SendingFarm_web_application> in md file:3ebcdcdf-593e-44bd-b60d-16efd5f07a16.md total found:0 +Warning,3ebcdcdf-593e-44bd-b60d-16efd5f07a16,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:https://<ReceivingFarm_web_application> in md file:3ebcdcdf-593e-44bd-b60d-16efd5f07a16.md total found:0 +Warning,3ebcdcdf-593e-44bd-b60d-16efd5f07a16,Missing tables headers in file:3ebcdcdf-593e-44bd-b60d-16efd5f07a16.md +Warning,3ede6cef-193d-4c25-8d41-cacabab95ac9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<path> in md file:3ede6cef-193d-4c25-8d41-cacabab95ac9.md total found:0 +Warning,3ede6cef-193d-4c25-8d41-cacabab95ac9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<path> is expressed as the path of a local file or the path of a file share- for example- "C:\foldername\sqlncli.msi" or "\\<servername>\<sharename>\sqlncli.msi".

in md file:3ede6cef-193d-4c25-8d41-cacabab95ac9.md total found:0 +Warning,3ede6cef-193d-4c25-8d41-cacabab95ac9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<path> in md file:3ede6cef-193d-4c25-8d41-cacabab95ac9.md total found:0 +Warning,3ede6cef-193d-4c25-8d41-cacabab95ac9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line: + To install more than one prerequisite- type each switch and argument pair. Be sure to separate each pair by a space- for example:
+ PrerequisiteInstaller.exe /IDFX: "\\<path >\Windows6.1-KB974405-x64.msu" /sqlncli: "\\<path >\sqlncli.msi" /Sync: "\\<path >\Synchronization.msi" + in md file:3ede6cef-193d-4c25-8d41-cacabab95ac9.md total found:0 +Warning,3ede6cef-193d-4c25-8d41-cacabab95ac9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<path> in md file:3ede6cef-193d-4c25-8d41-cacabab95ac9.md total found:0 +Warning,3ede6cef-193d-4c25-8d41-cacabab95ac9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<path> in md file:3ede6cef-193d-4c25-8d41-cacabab95ac9.md total found:0 +Warning,3ede6cef-193d-4c25-8d41-cacabab95ac9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Navigate to the startup directory- which is usually <systemdir>\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup.

in md file:3ede6cef-193d-4c25-8d41-cacabab95ac9.md total found:0 +Warning,3f7cf424-3340-4010-ad3b-6aef0cd74428,Video is found in md file:3f7cf424-3340-4010-ad3b-6aef0cd74428.md total found:1 +Warning,3fa7973f-2c1a-4be0-b903-3f1e6bdcf1d8,Found a an ul list inside a table in html file:3fa7973f-2c1a-4be0-b903-3f1e6bdcf1d8.xml +Warning,3fdbc40b-8562-4bec-be89-113a64e19911,Video is found in md file:3fdbc40b-8562-4bec-be89-113a64e19911.md total found:1 +Warning,40117fda-70a0-4e3d-8cd3-0def768da16c,Video is found in md file:40117fda-70a0-4e3d-8cd3-0def768da16c.md total found:3 +Warning,403e75f3-9e53-4d5b-a476-365e6e4bc92e,Video is found in md file:403e75f3-9e53-4d5b-a476-365e6e4bc92e.md total found:1 +Warning,4045020c-6ed2-4139-84f4-4bf7d099918d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

< 10-000

in md file:4045020c-6ed2-4139-84f4-4bf7d099918d.md total found:0 +Warning,4045020c-6ed2-4139-84f4-4bf7d099918d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

< 100-000

in md file:4045020c-6ed2-4139-84f4-4bf7d099918d.md total found:0 +Warning,4045020c-6ed2-4139-84f4-4bf7d099918d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

< 500-000

in md file:4045020c-6ed2-4139-84f4-4bf7d099918d.md total found:0 +Warning,4045020c-6ed2-4139-84f4-4bf7d099918d,Found nested table in md file:4045020c-6ed2-4139-84f4-4bf7d099918d.md +Warning,40d265d9-dd16-405f-8c85-390975024bad,Could not Add new line after images in md file:40d265d9-dd16-405f-8c85-390975024bad.md +Warning,40ed4458-d798-4aa1-82b9-2e5433991596,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:40ed4458-d798-4aa1-82b9-2e5433991596.md total found:0 +Warning,40ed4458-d798-4aa1-82b9-2e5433991596,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServer> in md file:40ed4458-d798-4aa1-82b9-2e5433991596.md total found:0 +Warning,40ed4458-d798-4aa1-82b9-2e5433991596,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:40ed4458-d798-4aa1-82b9-2e5433991596.md total found:0 +Warning,40ed4458-d798-4aa1-82b9-2e5433991596,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServer> in md file:40ed4458-d798-4aa1-82b9-2e5433991596.md total found:0 +Warning,42e7a722-1e13-4f48-b866-2548cff05225,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DOMAIN> in md file:42e7a722-1e13-4f48-b866-2548cff05225.md total found:0 +Warning,42e7a722-1e13-4f48-b866-2548cff05225,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<user name> in md file:42e7a722-1e13-4f48-b866-2548cff05225.md total found:0 +Warning,42e7a722-1e13-4f48-b866-2548cff05225,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

RSI doesn't support a multi-farm scenario where the My Site Host is not on the content farm. This site collection typically has a URL such as http://<hostname>/my. If the My Site Host is not on the content farm- sharing will be broken. + +

in md file:42e7a722-1e13-4f48-b866-2548cff05225.md total found:0 +Warning,42e7a722-1e13-4f48-b866-2548cff05225,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Have a user open a SharePoint Server site (for example- their own My Site: http://<hostname>/my).

in md file:42e7a722-1e13-4f48-b866-2548cff05225.md total found:0 +Warning,4356bad9-de1d-4e81-b049-17248b4a86c1,Found nested table in md file:4356bad9-de1d-4e81-b049-17248b4a86c1.md +Warning,43e52f2f-2586-451d-814d-edf43f3459ab,Found nested table in md file:43e52f2f-2586-451d-814d-edf43f3459ab.md +Warning,445bce79-f6d6-4ab6-9d50-f0672cd093f4,Found nested table in md file:445bce79-f6d6-4ab6-9d50-f0672cd093f4.md +Warning,44640e29-bd9c-4b6a-94e1-8d5d30e7fdd2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Path> in md file:44640e29-bd9c-4b6a-94e1-8d5d30e7fdd2.md total found:0 +Warning,44c05570-37c1-49dd-8015-015f8908199c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<URL> in md file:44c05570-37c1-49dd-8015-015f8908199c.md total found:0 +Warning,44c05570-37c1-49dd-8015-015f8908199c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<URL> in md file:44c05570-37c1-49dd-8015-015f8908199c.md total found:0 +Warning,45acdd33-b322-4f36-97f1-0701159e15f0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteCollectionGUIDorURL> in md file:45acdd33-b322-4f36-97f1-0701159e15f0.md total found:0 +Warning,45acdd33-b322-4f36-97f1-0701159e15f0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFile> in md file:45acdd33-b322-4f36-97f1-0701159e15f0.md total found:0 +Warning,462e12d6-1a5d-4b7c-a0d5-14c551262be1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<Select template later…>

in md file:462e12d6-1a5d-4b7c-a0d5-14c551262be1.md total found:0 +Warning,462e12d6-1a5d-4b7c-a0d5-14c551262be1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<Select template later…>

in md file:462e12d6-1a5d-4b7c-a0d5-14c551262be1.md total found:0 +Warning,462e12d6-1a5d-4b7c-a0d5-14c551262be1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<Select template later…>

in md file:462e12d6-1a5d-4b7c-a0d5-14c551262be1.md total found:0 +Warning,462e12d6-1a5d-4b7c-a0d5-14c551262be1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Same functionality as the 2013 <Select template later…> option.

in md file:462e12d6-1a5d-4b7c-a0d5-14c551262be1.md total found:0 +Warning,462e12d6-1a5d-4b7c-a0d5-14c551262be1,Found nested table in md file:462e12d6-1a5d-4b7c-a0d5-14c551262be1.md +Warning,4692ebba-90eb-4d72-ac12-e90c4d4ee7ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In the Object Explorer - expand the <database server name>- expand Security - and then expand Logins .

in md file:4692ebba-90eb-4d72-ac12-e90c4d4ee7ae.md total found:0 +Warning,4692ebba-90eb-4d72-ac12-e90c4d4ee7ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In the Set the Database Server box- enter <The name of the database server> and in the Set the Database Name box- enter AdventureWorks2008R2 . Optionally- in the Name box- enter AdventureWorks Sample Database.

in md file:4692ebba-90eb-4d72-ac12-e90c4d4ee7ae.md total found:0 +Warning,4692ebba-90eb-4d72-ac12-e90c4d4ee7ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<Site Name> Members

in md file:4692ebba-90eb-4d72-ac12-e90c4d4ee7ae.md total found:0 +Warning,4692ebba-90eb-4d72-ac12-e90c4d4ee7ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<Site Name> Owners

in md file:4692ebba-90eb-4d72-ac12-e90c4d4ee7ae.md total found:0 +Warning,4692ebba-90eb-4d72-ac12-e90c4d4ee7ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<Site Name> Visitors

in md file:4692ebba-90eb-4d72-ac12-e90c4d4ee7ae.md total found:0 +Warning,4692ebba-90eb-4d72-ac12-e90c4d4ee7ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Team Site Name> AWCustomers in md file:4692ebba-90eb-4d72-ac12-e90c4d4ee7ae.md total found:0 +Warning,46aecccb-6196-48b4-a889-cbd408354d56,Found a an ul list inside a table in html file:46aecccb-6196-48b4-a889-cbd408354d56.xml +Warning,46aecccb-6196-48b4-a889-cbd408354d56,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:External <All IP addresses> in md file:46aecccb-6196-48b4-a889-cbd408354d56.md total found:0 +Warning,46aecccb-6196-48b4-a889-cbd408354d56,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<rule name> Properties in md file:46aecccb-6196-48b4-a889-cbd408354d56.md total found:0 +Warning,46aecccb-6196-48b4-a889-cbd408354d56,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Redirect requests to <HTTP port or SSL port> in md file:46aecccb-6196-48b4-a889-cbd408354d56.md total found:0 +Warning,46aecccb-6196-48b4-a889-cbd408354d56,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<rule name> Properties in md file:46aecccb-6196-48b4-a889-cbd408354d56.md total found:0 +Warning,46aecccb-6196-48b4-a889-cbd408354d56,Missing tables headers in file:46aecccb-6196-48b4-a889-cbd408354d56.md +Warning,46aecccb-6196-48b4-a889-cbd408354d56,Could not Add new line after images in md file:46aecccb-6196-48b4-a889-cbd408354d56.md +Warning,46e0f7e7-cd69-41a5-9988-bd0e7db564d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationGUID> in md file:46e0f7e7-cd69-41a5-9988-bd0e7db564d9.md total found:0 +Warning,478be4b7-1480-4f97-87c5-b18cd2436bce,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BlobCache location="C:\BlobCache\14" path="\.(gif|jpg|jpeg|jpe|jfif|bmp|dib|tif|tiff|themedbmp|themedcss|themedgif|themedjpg|themedpng|ico|png|wdp|hdp|css|js|asf|avi|flv|m4v|mov|mp3|mp4|mpeg|mpg|rm|rmvb|wma|wmv|ogg|ogv|oga|webm|xap)$" maxSize="10" imageRenditionMaxSourcePixels="100000000" enabled="true" /> in md file:478be4b7-1480-4f97-87c5-b18cd2436bce.md total found:0 +Warning,48a1c449-7bf6-4f12-a5f3-1933caadf713,Found a an ul list inside a table in html file:48a1c449-7bf6-4f12-a5f3-1933caadf713.xml +Warning,48d39f84-9698-4249-b7e0-b885c462622e,Found a an ul list inside a table in html file:48d39f84-9698-4249-b7e0-b885c462622e.xml +Warning,4bd426f4-105c-41cf-a4b8-815db62191ce,Found a an ol list inside a table in html file:4bd426f4-105c-41cf-a4b8-815db62191ce.xml +Warning,4c50e9d2-a1f9-45a5-8466-829e056a92d0,Found a an ul list inside a table in html file:4c50e9d2-a1f9-45a5-8466-829e056a92d0.xml +Warning,4c7e118f-e3f3-450d-acf1-4e219c932fce,Could not Add new line after images in md file:4c7e118f-e3f3-450d-acf1-4e219c932fce.md +Warning,4cbe141a-095f-4c09-82f4-dec8af16c590,Missing tables headers in file:4cbe141a-095f-4c09-82f4-dec8af16c590.md +Warning,4cf30b48-f908-4774-920c-d2f2916f2c1b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDatabaseName> in md file:4cf30b48-f908-4774-920c-d2f2916f2c1b.md total found:0 +Warning,4cf30b48-f908-4774-920c-d2f2916f2c1b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDatabaseName> in md file:4cf30b48-f908-4774-920c-d2f2916f2c1b.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found a an ul list inside a table in html file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.xml +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

There is a highly consistent intra-farm latency of <1 ms one way- 99.9% of the time over a period of ten minutes. (Intra-farm latency is commonly defined as the latency between the front-end web servers and the database servers.)

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

The intra-farm latency of <1 ms one way- 99-9% of the time over a period of ten minutes is also required for SharePoint environments with servers that are located in the same datacenter. The bandwidth speed should also be in this case at least 1 gigabit per second.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

The installer installs from the file that you specify in the command-line options described in the following list. In this list- <file > signifies the file from which you want to install. If you do not specify the <file > option- the installer downloads the file from the Internet and installs it. If the option does not apply to the current operating system- it is ignored.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/SQLNCli:<file > Install Microsoft SQL Server 2012 SP1 Native Client from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/SQLNCli:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/IDFX11:<file > Install Microsoft Identity Extensions from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/IDFX11:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/Sync:<file > Install Microsoft Sync Framework Runtime SP1 v1.0 (x64) from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/Sync:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/AppFabric:<file > Install Windows Server AppFabric from <file > (AppFabric must be installed with the options /i CacheClient-CachingService-CacheAdmin /gac).

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/AppFabric:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/KB3092423:<file > Install Cumulative Update Package 7 for Microsoft AppFabric 1.1 for Windows Server (KB3092423) from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/KB3092423:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/MSIPCClient:<file > Install Microsoft Information Protection and Control Client from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/MSIPCClient:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/WCFDataServices56:<file > Install Microsoft WCF Data Services 5.6 from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/WCFDataServices56:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/ODBC:<file > Install Microsoft ODBC Driver 11 for SQL Server from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/ODBC:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/DotNetFx:<file > Install Microsoft .NET Framework 4.6 from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/DotNetFx:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/MSVCRT11:<file > Install Visual C++ Redistributable Package for Visual Studio 2012 from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/MSVCRT11:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/MSVCRT14:<file > Install Visual C++ Redistributable Package for Visual Studio 2015 from <file >.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/MSVCRT14:<file > in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4d88c402-24f2-449b-86a6-6e7afcfec0cd,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

The prerequisite installer creates log files at %TEMP%\prerequisiteinstaller.<date>.<time>.log. You can check these log files for specific details about all changes the installer makes to the target computer.

in md file:4d88c402-24f2-449b-86a6-6e7afcfec0cd.md total found:0 +Warning,4fcd074b-32b1-49b3-9910-5bb174894603,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 25 (Megabytes)

in md file:4fcd074b-32b1-49b3-9910-5bb174894603.md total found:0 +Warning,4fcd074b-32b1-49b3-9910-5bb174894603,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Minutes)

in md file:4fcd074b-32b1-49b3-9910-5bb174894603.md total found:0 +Warning,4fcd074b-32b1-49b3-9910-5bb174894603,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Seconds)

in md file:4fcd074b-32b1-49b3-9910-5bb174894603.md total found:0 +Warning,4fceb168-753a-4227-8a23-ab415f9abce7,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<contoso\jane> in md file:4fceb168-753a-4227-8a23-ab415f9abce7.md total found:0 +Warning,4fceb168-753a-4227-8a23-ab415f9abce7,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<contoso\jane> in md file:4fceb168-753a-4227-8a23-ab415f9abce7.md total found:0 +Warning,4fceb168-753a-4227-8a23-ab415f9abce7,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationDisplayName> in md file:4fceb168-753a-4227-8a23-ab415f9abce7.md total found:0 +Warning,4fceb168-753a-4227-8a23-ab415f9abce7,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationDisplayName> in md file:4fceb168-753a-4227-8a23-ab415f9abce7.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found a an ul list inside a table in html file:5005124c-09d0-435c-99a4-1f2cb1fdae91.xml +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServer> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ApplicationPoolName> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServer> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ApplicationPoolName> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<TimerJobFrequency> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MaximumTranslationAttempts> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<JobExpirationDays> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MaximumSyncTranslationRequests> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<RecycleProcessThreshold> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DisableBinaryFileScan> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<TimerJobFrequency> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MaximumTranslationAttempts> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<JobExpirationDays> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MaximumSyncTranslationRequests> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<RecycleProcessThreshold> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DisableBinaryFileScan> in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md total found:0 +Warning,5005124c-09d0-435c-99a4-1f2cb1fdae91,Found nested table in md file:5005124c-09d0-435c-99a4-1f2cb1fdae91.md +Warning,502fcb0a-c20a-433d-aac1-02ba20d81a7e,Found a an ul list inside a table in html file:502fcb0a-c20a-433d-aac1-02ba20d81a7e.xml +Warning,53598509-9821-4c0b-9ab4-a9e594ac8fec,Video is found in md file:53598509-9821-4c0b-9ab4-a9e594ac8fec.md total found:1 +Warning,5417b04a-c7d9-4e9a-86fb-ee1d1c63508b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:5417b04a-c7d9-4e9a-86fb-ee1d1c63508b.md total found:0 +Warning,5417b04a-c7d9-4e9a-86fb-ee1d1c63508b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationID> in md file:5417b04a-c7d9-4e9a-86fb-ee1d1c63508b.md total found:0 +Warning,57b7618a-2ca4-450d-aa8b-77bce21a9884,Found a an ul list inside a table in html file:57b7618a-2ca4-450d-aa8b-77bce21a9884.xml +Warning,57b7618a-2ca4-450d-aa8b-77bce21a9884,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Open Internet Explorer and navigate to Outlook Web App (if the deployment is on SharePoint Server) or the SSL SharePoint Server site (if the deployment is on Exchange Server): https://<ExServerName>/owa or https://<SP_FQDN>.

in md file:57b7618a-2ca4-450d-aa8b-77bce21a9884.md total found:0 +Warning,57b7618a-2ca4-450d-aa8b-77bce21a9884,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

.\Set-SiteMailboxConfig.ps1 -ExchangeSiteMailboxDomain <Domain> -ExchangeAutodiscoverDomain [Exchange Server] -WebApplicationUrl [URL]

in md file:57b7618a-2ca4-450d-aa8b-77bce21a9884.md total found:0 +Warning,57b7618a-2ca4-450d-aa8b-77bce21a9884,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Where <Domain> equals the FQDN of the domain your Exchange Server is in- and <Exchange Server> is the Exchange Server that you intend to connect to. This is a required parameter.

in md file:57b7618a-2ca4-450d-aa8b-77bce21a9884.md total found:0 +Warning,57b7618a-2ca4-450d-aa8b-77bce21a9884,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Where <SP_FQDN> is the URL to the SharePoint SSL root site collection that you want to configure.

in md file:57b7618a-2ca4-450d-aa8b-77bce21a9884.md total found:0 +Warning,58901f1a-dbc9-46ca-8b51-e683ea5f2ce3,Found a an ul list inside a table in html file:58901f1a-dbc9-46ca-8b51-e683ea5f2ce3.xml +Warning,58901f1a-dbc9-46ca-8b51-e683ea5f2ce3,Missing tables headers in file:58901f1a-dbc9-46ca-8b51-e683ea5f2ce3.md +Warning,58901f1a-dbc9-46ca-8b51-e683ea5f2ce3,Could not Add new line after images in md file:58901f1a-dbc9-46ca-8b51-e683ea5f2ce3.md +Warning,59c0540e-1238-4138-b98d-0d74ca59b9db,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:59c0540e-1238-4138-b98d-0d74ca59b9db.md total found:0 +Warning,59c0540e-1238-4138-b98d-0d74ca59b9db,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:59c0540e-1238-4138-b98d-0d74ca59b9db.md total found:0 +Warning,59c0540e-1238-4138-b98d-0d74ca59b9db,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:59c0540e-1238-4138-b98d-0d74ca59b9db.md total found:0 +Warning,59c0540e-1238-4138-b98d-0d74ca59b9db,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:59c0540e-1238-4138-b98d-0d74ca59b9db.md total found:0 +Warning,59f3af85-89f9-43ba-b364-28a810cae42e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:59f3af85-89f9-43ba-b364-28a810cae42e.md total found:0 +Warning,59f3af85-89f9-43ba-b364-28a810cae42e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Time> in md file:59f3af85-89f9-43ba-b364-28a810cae42e.md total found:0 +Warning,5a1b6cd9-358c-41af-8309-495640518eac,Found a an ul list inside a table in html file:5a1b6cd9-358c-41af-8309-495640518eac.xml +Warning,5a1b6cd9-358c-41af-8309-495640518eac,Missing tables headers in file:5a1b6cd9-358c-41af-8309-495640518eac.md +Warning,5a1b6cd9-358c-41af-8309-495640518eac,Could not Add new line after images in md file:5a1b6cd9-358c-41af-8309-495640518eac.md +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

BDC_Service_DB_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Managed Metadata Service_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

PerformancePoint Service Application_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_DB_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_AnalyticsReportingStoreDB_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Secure_Store_Service_DB_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_ProfileDB_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_SocialDB_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5aeff319-0a8f-4d6b-86d5-6086611c48ed,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_SyncDB_<GUID>

in md file:5aeff319-0a8f-4d6b-86d5-6086611c48ed.md total found:0 +Warning,5c23f9ea-d019-4750-abdf-0633bffa84f4,Video is found in md file:5c23f9ea-d019-4750-abdf-0633bffa84f4.md total found:1 +Warning,5cf2a498-d879-4673-b4d4-2eaa36695ff9,Found a an ul list inside a table in html file:5cf2a498-d879-4673-b4d4-2eaa36695ff9.xml +Warning,5cf2a498-d879-4673-b4d4-2eaa36695ff9,Missing tables headers in file:5cf2a498-d879-4673-b4d4-2eaa36695ff9.md +Warning,5cf2a498-d879-4673-b4d4-2eaa36695ff9,Found nested table in md file:5cf2a498-d879-4673-b4d4-2eaa36695ff9.md +Warning,5e242415-c288-48c7-a373-29acc359ad95,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 25 (Megabytes)

in md file:5e242415-c288-48c7-a373-29acc359ad95.md total found:0 +Warning,5e242415-c288-48c7-a373-29acc359ad95,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Minutes)

in md file:5e242415-c288-48c7-a373-29acc359ad95.md total found:0 +Warning,5e242415-c288-48c7-a373-29acc359ad95,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<= 60 (Seconds)

in md file:5e242415-c288-48c7-a373-29acc359ad95.md total found:0 +Warning,5e44cf6c-2271-4ff1-af7f-4e73849ffdf6,Video is found in md file:5e44cf6c-2271-4ff1-af7f-4e73849ffdf6.md total found:1 +Warning,5f80cdb8-d6d1-45f0-9710-d30544fcb3e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Use the following Azure PowerShell command block creates the virtual machines for the two domain controllers. Specify the values for the variables- removing the < and > characters. Note that this Azure PowerShell command block uses values from the following:

in md file:5f80cdb8-d6d1-45f0-9710-d30544fcb3e6.md total found:0 +Warning,5fbe84ab-4ec4-4b8f-be25-559a1cdfc68e,Could not Add new line after images in md file:5fbe84ab-4ec4-4b8f-be25-559a1cdfc68e.md +Warning,6259e195-2b83-454f-b635-8f228c1fd1ac,Found a an ul list inside a table in html file:6259e195-2b83-454f-b635-8f228c1fd1ac.xml +Warning,62d0b8d3-e8ea-4523-a69f-62623fb340fb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Connect to the primary SQL Server virtual machine with the <your domain>\sp_farm_db account credentials.

in md file:62d0b8d3-e8ea-4523-a69f-62623fb340fb.md total found:0 +Warning,62d0b8d3-e8ea-4523-a69f-62623fb340fb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In the File sharing dialog- type <your domain name>\sqlservice - and then click Add .

in md file:62d0b8d3-e8ea-4523-a69f-62623fb340fb.md total found:0 +Warning,62d0b8d3-e8ea-4523-a69f-62623fb340fb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Click Add. In File name - type \\ <machineName>\backup <databaseName>.bak - where machineName is the name of the primary SQL Server computer and databaseName is the name of the database. Click OK - and then click OK again after the message about the successful backup.

in md file:62d0b8d3-e8ea-4523-a69f-62623fb340fb.md total found:0 +Warning,62d0b8d3-e8ea-4523-a69f-62623fb340fb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In the left pane- right-click <databaseName>- point to Tasks - and then click Back Up .

in md file:62d0b8d3-e8ea-4523-a69f-62623fb340fb.md total found:0 +Warning,62d0b8d3-e8ea-4523-a69f-62623fb340fb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Connect to the secondary SQL Server virtual machine with the <your domain>\sp_farm_db account credentials.

in md file:62d0b8d3-e8ea-4523-a69f-62623fb340fb.md total found:0 +Warning,62d0b8d3-e8ea-4523-a69f-62623fb340fb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In Backup file location- type \ <machine name>\backup - press Enter- select <databaseName>.bak - and then click OK twice. You should now see the full backup and the log backup in the Backup sets to restore section.

in md file:62d0b8d3-e8ea-4523-a69f-62623fb340fb.md total found:0 +Warning,62d0b8d3-e8ea-4523-a69f-62623fb340fb,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Connect to one of the SQL Server virtual machines with the <domain name>\sp_farm_db account credentials.

in md file:62d0b8d3-e8ea-4523-a69f-62623fb340fb.md total found:0 +Warning,64233599-f18c-4081-a3ce-450e878a1b9f,Could not Add new line after images in md file:64233599-f18c-4081-a3ce-450e878a1b9f.md +Warning,6641730b-7099-47c0-938f-783ea8ef8e62,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceGUID> in md file:6641730b-7099-47c0-938f-783ea8ef8e62.md total found:0 +Warning,6641730b-7099-47c0-938f-783ea8ef8e62,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceGUID> in md file:6641730b-7099-47c0-938f-783ea8ef8e62.md total found:0 +Warning,6641730b-7099-47c0-938f-783ea8ef8e62,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceGUID> in md file:6641730b-7099-47c0-938f-783ea8ef8e62.md total found:0 +Warning,6641730b-7099-47c0-938f-783ea8ef8e62,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceGUID> in md file:6641730b-7099-47c0-938f-783ea8ef8e62.md total found:0 +Warning,68551945-009f-43c2-b38f-5248aaf6d540,Found nested table in md file:68551945-009f-43c2-b38f-5248aaf6d540.md +Warning,69f8553c-3df5-4366-ac6a-941e619a84cf,Found a an ul list inside a table in html file:69f8553c-3df5-4366-ac6a-941e619a84cf.xml +Warning,6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe,Found a an ul list inside a table in html file:6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe.xml +Warning,6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Browsing the Review database status page (<your_SharePoint_CentralAdmin_URL>/_admin/UpgradeStatus.aspx) on the Central Administration web site may result in a timeout.

in md file:6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe.md total found:0 +Warning,6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe,Found nested table in md file:6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe.md +Warning,6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:< the service application proxy group > in md file:6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2.md total found:0 +Warning,6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<members to add to the service application proxy group> in md file:6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2.md total found:0 +Warning,6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPServiceApplicationProxyGroupPipeBind> in md file:6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2.md total found:0 +Warning,6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SPServiceApplicationProxyPipeBind > in md file:6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found a an ul list inside a table in html file:6aa16d9a-812a-4bbc-b421-1b4589452503.xml +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://SiteName> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://SiteName> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://SiteName> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://SiteName> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://WebApplicationURL> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<c:\timerjobfile.txt> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<c:\timerjobfile.txt> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://WebApplicationURL> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<c:\timerjobfile.txt> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDB> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDB> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDB> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DBServer> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://SiteName> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDB> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DBServer> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://SiteName> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<c:\timerjobfile.txt> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6aa16d9a-812a-4bbc-b421-1b4589452503,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<c:\timerjobfile.txt> in md file:6aa16d9a-812a-4bbc-b421-1b4589452503.md total found:0 +Warning,6bf64b3d-edf0-4d2a-a1f5-b53318a24a1a,Found a an ul list inside a table in html file:6bf64b3d-edf0-4d2a-a1f5-b53318a24a1a.xml +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:$<host n> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Server name> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:$<host n> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Index partition number> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<host n> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Server name> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:$<host n> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Index partition number> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Index component name> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6c4f87aa-1004-4b87-aaca-2c262588fc46,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Id of the activating topology> in md file:6c4f87aa-1004-4b87-aaca-2c262588fc46.md total found:0 +Warning,6cd7e6d2-092d-47f0-aed0-97bf2c09369a,Video is found in md file:6cd7e6d2-092d-47f0-aed0-97bf2c09369a.md total found:1 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\ConsumingFarmRoot.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\ConsumingFarmRoot.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\ConsumingFarmSTS.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\ConsumingFarmSTS.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\PublishingFarmRoot.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\PublishingFarmRoot.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\PublishingFarmRoot.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<PublishingFarm> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\PublishingFarmRoot.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<PublishingFarm> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\ConsumingFarmRoot.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ConsumingFarm> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\ConsumingFarmRoot.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ConsumingFarm> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<c:\ConsumingFarmSTS.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ConsumingFarm> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<C:\ConsumingFarmSTS.cer> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ConsumingFarm> in md file:6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c.md total found:0 +Warning,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,Found a an ul list inside a table in html file:6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77.xml +Warning,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Passphrase> in md file:6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77.md total found:0 +Warning,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Passphrase> in md file:6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77.md total found:0 +Warning,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77.md total found:0 +Warning,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationDBName> in md file:6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77.md total found:0 +Warning,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77.md total found:0 +Warning,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,Missing tables headers in file:6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77.md +Warning,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,Could not Add new line after images in md file:6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77.md +Warning,6f1b9f42-2408-43e3-ab87-33b122a8b545,Found nested table in md file:6f1b9f42-2408-43e3-ab87-33b122a8b545.md +Warning,70e043ef-8908-436e-92bf-abbcd89874f7,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DOMAIN> in md file:70e043ef-8908-436e-92bf-abbcd89874f7.md total found:0 +Warning,70e043ef-8908-436e-92bf-abbcd89874f7,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<user name> in md file:70e043ef-8908-436e-92bf-abbcd89874f7.md total found:0 +Warning,73ceb46e-d3aa-45bd-ac3e-77f58a9ab34d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DOMAIN> in md file:73ceb46e-d3aa-45bd-ac3e-77f58a9ab34d.md total found:0 +Warning,73ceb46e-d3aa-45bd-ac3e-77f58a9ab34d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UserName> in md file:73ceb46e-d3aa-45bd-ac3e-77f58a9ab34d.md total found:0 +Warning,73cfd7b3-be90-480a-b415-039fa97d9b89,Found a an ul list inside a table in html file:73cfd7b3-be90-480a-b415-039fa97d9b89.xml +Warning,73e8ee39-0865-497a-b9e2-a0b0b46cde20,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteCollectionURL> in md file:73e8ee39-0865-497a-b9e2-a0b0b46cde20.md total found:0 +Warning,73e8ee39-0865-497a-b9e2-a0b0b46cde20,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServerName> in md file:73e8ee39-0865-497a-b9e2-a0b0b46cde20.md total found:0 +Warning,73e8ee39-0865-497a-b9e2-a0b0b46cde20,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDatabaseName> in md file:73e8ee39-0865-497a-b9e2-a0b0b46cde20.md total found:0 +Warning,75096f60-b94e-44c2-bc84-8aa3e2c4fff3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://yourSiteURL> in md file:75096f60-b94e-44c2-bc84-8aa3e2c4fff3.md total found:0 +Warning,75096f60-b94e-44c2-bc84-8aa3e2c4fff3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://yourSiteURL> in md file:75096f60-b94e-44c2-bc84-8aa3e2c4fff3.md total found:0 +Warning,75113d71-7193-44ab-b79b-34cb9cf9aa94,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

For site collection administrators: There are also log files for site collection upgrade stored inside the site collection itself- in the Maintenance Logs catalog at (http://<SiteName>/_catalogs/MaintenanceLogs/YYYYMMDD-HHMMSS-SSS.txt - where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format- minutes- seconds- and milliseconds).

in md file:75113d71-7193-44ab-b79b-34cb9cf9aa94.md total found:0 +Warning,763613ac-83f4-424e-99d0-32efd0667bd9,Found a an ul list inside a table in html file:763613ac-83f4-424e-99d0-32efd0667bd9.xml +Warning,763613ac-83f4-424e-99d0-32efd0667bd9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Ensure <SafeMode> CallStack="false" and AllowPageLevelTrace="false".

in md file:763613ac-83f4-424e-99d0-32efd0667bd9.md total found:0 +Warning,763613ac-83f4-424e-99d0-32efd0667bd9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Ensure that customErrors is turned on (<customErrors mode="On"/>).

in md file:763613ac-83f4-424e-99d0-32efd0667bd9.md total found:0 +Warning,763613ac-83f4-424e-99d0-32efd0667bd9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Consider your Web proxy settings as needed (<system.net>/<defaultProxy>).

in md file:763613ac-83f4-424e-99d0-32efd0667bd9.md total found:0 +Warning,766e0169-1a5d-4730-9c9f-7e2b27ba7d5d,Found a an ul list inside a table in html file:766e0169-1a5d-4730-9c9f-7e2b27ba7d5d.xml +Warning,76c08191-13da-4cdc-beee-82c30033b7dc,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Consumes content types from the content type gallery at http://<site> in md file:76c08191-13da-4cdc-beee-82c30033b7dc.md total found:0 +Warning,78df8a76-0dbc-403b-b54d-9572fc918531,Video is found in md file:78df8a76-0dbc-403b-b54d-9572fc918531.md total found:1 +Warning,79240081-1495-4db7-b0c5-e5e4d4e59c37,Could not Add new line after images in md file:79240081-1495-4db7-b0c5-e5e4d4e59c37.md +Warning,79428586-0a1c-4fd8-ae49-e1e76eb022e1,Found a an ul list inside a table in html file:79428586-0a1c-4fd8-ae49-e1e76eb022e1.xml +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationID> in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationID> in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7942ef65-c309-402d-b4bb-d54e686fc5d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line: + If you are restoring the User Profile database (by default named "User Profile Service_ProfileDB_<GUID>")- then also restore the Social database (by default named "User Profile Service_SocialDB_<GUID>"). Failing to do this can cause inaccuracies in the User Profile data that might be difficult to detect and fix. + in md file:7942ef65-c309-402d-b4bb-d54e686fc5d9.md total found:0 +Warning,7a1835c3-6375-4647-b190-84676fc9f9b0,Found a an ul list inside a table in html file:7a1835c3-6375-4647-b190-84676fc9f9b0.xml +Warning,7c75dc80-6910-4c10-a9a0-d821bedd602d,Found a an ul list inside a table in html file:7c75dc80-6910-4c10-a9a0-d821bedd602d.xml +Warning,7c75dc80-6910-4c10-a9a0-d821bedd602d,Missing tables headers in file:7c75dc80-6910-4c10-a9a0-d821bedd602d.md +Warning,7c75dc80-6910-4c10-a9a0-d821bedd602d,Could not Add new line after images in md file:7c75dc80-6910-4c10-a9a0-d821bedd602d.md +Warning,7c877590-c6b4-48b2-aee3-330c5d42d44c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDatabaseName> in md file:7c877590-c6b4-48b2-aee3-330c5d42d44c.md total found:0 +Warning,7c877590-c6b4-48b2-aee3-330c5d42d44c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDatabaseName> in md file:7c877590-c6b4-48b2-aee3-330c5d42d44c.md total found:0 +Warning,7d2cbe64-5888-415e-81be-98b6921929de,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<servername> in md file:7d2cbe64-5888-415e-81be-98b6921929de.md total found:0 +Warning,7d2cbe64-5888-415e-81be-98b6921929de,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<servername> in md file:7d2cbe64-5888-415e-81be-98b6921929de.md total found:0 +Warning,7d88430f-2f0f-4c83-863b-ad840bdbf696,Found a an ul list inside a table in html file:7d88430f-2f0f-4c83-863b-ad840bdbf696.xml +Warning,7fa9730a-2d11-4c78-b546-60179c5bb646,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Specify the new servers you want to add search components to- start a search service instance (ssi) on these servers and create references to the search service instances. In this procedure we have used the example host names "myserver<n >" for the servers as listed in the Target search topology table. At the Windows PowerShell command prompt- type the following command(s):

in md file:7fa9730a-2d11-4c78-b546-60179c5bb646.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationProxyName > in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationProxyName> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<root directory drive> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,80f7df54-738e-49ba-9ff9-2f312d77a271,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<root directory drive> in md file:80f7df54-738e-49ba-9ff9-2f312d77a271.md total found:0 +Warning,81890ff0-e2f9-4752-8e8e-2e8502c76311,Found a an ul list inside a table in html file:81890ff0-e2f9-4752-8e8e-2e8502c76311.xml +Warning,81ea6763-c331-453b-80f7-8028c3e551f8,Found a an ol list inside a table in html file:81ea6763-c331-453b-80f7-8028c3e551f8.xml +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseID> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseID> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ID> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Credential> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ID> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Credential> in md file:8386d324-816a-42ee-aff2-ce135ca2f241.md total found:0 +Warning,83ee2a38-1b91-4c6a-83de-1e968db74611,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDbName> in md file:83ee2a38-1b91-4c6a-83de-1e968db74611.md total found:0 +Warning,83ee2a38-1b91-4c6a-83de-1e968db74611,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DBInstanceName> in md file:83ee2a38-1b91-4c6a-83de-1e968db74611.md total found:0 +Warning,83ee2a38-1b91-4c6a-83de-1e968db74611,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDbName> in md file:83ee2a38-1b91-4c6a-83de-1e968db74611.md total found:0 +Warning,83ee2a38-1b91-4c6a-83de-1e968db74611,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DBInstanceName> in md file:83ee2a38-1b91-4c6a-83de-1e968db74611.md total found:0 +Warning,8404adef-6bfb-4795-be16-15739e1212f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WSS_Content> in md file:8404adef-6bfb-4795-be16-15739e1212f5.md total found:0 +Warning,8404adef-6bfb-4795-be16-15739e1212f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://servername> in md file:8404adef-6bfb-4795-be16-15739e1212f5.md total found:0 +Warning,8404adef-6bfb-4795-be16-15739e1212f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<WSS_Content> is the <name and ID of the database>.

in md file:8404adef-6bfb-4795-be16-15739e1212f5.md total found:0 +Warning,8404adef-6bfb-4795-be16-15739e1212f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WSS_Content> in md file:8404adef-6bfb-4795-be16-15739e1212f5.md total found:0 +Warning,8404adef-6bfb-4795-be16-15739e1212f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<http://servername> is <the URL of the Web Application>.

in md file:8404adef-6bfb-4795-be16-15739e1212f5.md total found:0 +Warning,8404adef-6bfb-4795-be16-15739e1212f5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://servername> in md file:8404adef-6bfb-4795-be16-15739e1212f5.md total found:0 +Warning,842d7420-32ee-4e82-a8db-2dbb3e01a36c,Could not Add new line after images in md file:842d7420-32ee-4e82-a8db-2dbb3e01a36c.md +Warning,8451dde9-bbd1-4285-bc24-71bd795fb912,Found a an ul list inside a table in html file:8451dde9-bbd1-4285-bc24-71bd795fb912.xml +Warning,8451dde9-bbd1-4285-bc24-71bd795fb912,Found nested table in md file:8451dde9-bbd1-4285-bc24-71bd795fb912.md +Warning,84972766-6527-4791-ae68-02d3a50b67f0,Missing tables headers in file:84972766-6527-4791-ae68-02d3a50b67f0.md +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://ServerName/Sites/SiteName> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://ServerName/Sites/SiteName> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://ServerName/Sites/SiteName> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://ServerName/Sites/SiteName> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://ServerName/Sites/SiteName> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://ServerName/Sites/SiteName> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DestinationContentDb> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://ServerName/Sites/SiteName> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DestinationContentDb> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SourceContentDb> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DestinationContentDb> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SourceContentDb> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DestinationContentDb> in md file:86bb109d-865f-4f86-bb3d-87ecfc4e50ae.md total found:0 +Warning,86e0fc90-0ef8-4c22-9d3b-7af42bf882f1,Found a an ul list inside a table in html file:86e0fc90-0ef8-4c22-9d3b-7af42bf882f1.xml +Warning,86e4a832-ef3a-46cf-9b60-f9796292bf3e,Found nested table in md file:86e4a832-ef3a-46cf-9b60-f9796292bf3e.md +Warning,883fac19-3048-4ef0-b473-10b3b05493b6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:IsReadyForRoleConversion(SPServerRole newRole- out IEnumerable<string> errorMessages) in md file:883fac19-3048-4ef0-b473-10b3b05493b6.md total found:0 +Warning,883fac19-3048-4ef0-b473-10b3b05493b6,Found nested table in md file:883fac19-3048-4ef0-b473-10b3b05493b6.md +Warning,89c08a8b-74ee-4a97-8885-16c4c5a1288d,Found a an ul list inside a table in html file:89c08a8b-74ee-4a97-8885-16c4c5a1288d.xml +Warning,89c08a8b-74ee-4a97-8885-16c4c5a1288d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<no index> in md file:89c08a8b-74ee-4a97-8885-16c4c5a1288d.md total found:0 +Warning,8b91dc0a-c37d-4ec8-aa75-deb3f268fb97,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Site URL> in md file:8b91dc0a-c37d-4ec8-aa75-deb3f268fb97.md total found:0 +Warning,8b91dc0a-c37d-4ec8-aa75-deb3f268fb97,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Site URL> in md file:8b91dc0a-c37d-4ec8-aa75-deb3f268fb97.md total found:0 +Warning,8c733fb9-18b9-4770-b90b-364bd7ab30d1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Use the following blocks of PowerShell commands to create the components in Azure. Specify the values for the variables- removing the < and > characters. Note that these PowerShell command blocks use values from the following tables:

in md file:8c733fb9-18b9-4770-b90b-364bd7ab30d1.md total found:0 +Warning,8c733fb9-18b9-4770-b90b-364bd7ab30d1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

After the virtual machine restarts- create a Remote Desktop connection using the <your domain>\sp_farm_db account credentials four times- once for each SharePoint server. You created these credentials in SharePoint Intranet Farm in Azure Phase 2: Configure domain controllers.

in md file:8c733fb9-18b9-4770-b90b-364bd7ab30d1.md total found:0 +Warning,8c733fb9-18b9-4770-b90b-364bd7ab30d1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

In Username - type <your domain>\sp_farm_db . +

in md file:8c733fb9-18b9-4770-b90b-364bd7ab30d1.md total found:0 +Warning,8c733fb9-18b9-4770-b90b-364bd7ab30d1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Open a new tab in Internet Explorer- type http:// <name of the first SharePoint application server>/ in the Address bar- and then press Enter. You should see the default team site.

in md file:8c733fb9-18b9-4770-b90b-364bd7ab30d1.md total found:0 +Warning,8daa31a5-0f8c-4bd6-84c9-ee1f5074594d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:8daa31a5-0f8c-4bd6-84c9-ee1f5074594d.md total found:0 +Warning,8daa31a5-0f8c-4bd6-84c9-ee1f5074594d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:8daa31a5-0f8c-4bd6-84c9-ee1f5074594d.md total found:0 +Warning,8f98a750-19bb-4ea0-9ff5-719b85febbb3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UNC location> in md file:8f98a750-19bb-4ea0-9ff5-719b85febbb3.md total found:0 +Warning,8f98a750-19bb-4ea0-9ff5-719b85febbb3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<UNC location> in md file:8f98a750-19bb-4ea0-9ff5-719b85febbb3.md total found:0 +Warning,8f98a750-19bb-4ea0-9ff5-719b85febbb3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

The XML definition files (.ACTIONS files) are stored in the 16\TEMPLATE\<LCID >\Workflow directory.

in md file:8f98a750-19bb-4ea0-9ff5-719b85febbb3.md total found:0 +Warning,8fe00c69-317f-49c9-8669-832a5f85e42c,Found a an ul list inside a table in html file:8fe00c69-317f-49c9-8669-832a5f85e42c.xml +Warning,8fe00c69-317f-49c9-8669-832a5f85e42c,Missing tables headers in file:8fe00c69-317f-49c9-8669-832a5f85e42c.md +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Farm\Shared Services Applications\<User Profile Service service application name> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GIUD> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,9061f245-7b75-4211-af5f-b87ec09b5c82,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:9061f245-7b75-4211-af5f-b87ec09b5c82.md total found:0 +Warning,90d8dee0-5c31-4c9b-93d5-cf09cb2320aa,Found a an ul list inside a table in html file:90d8dee0-5c31-4c9b-93d5-cf09cb2320aa.xml +Warning,91274b73-f7be-4066-a4ab-ec30af30016e,Video is found in md file:91274b73-f7be-4066-a4ab-ec30af30016e.md total found:1 +Warning,91274b73-f7be-4066-a4ab-ec30af30016e,Found a an ul list inside a table in html file:91274b73-f7be-4066-a4ab-ec30af30016e.xml +Warning,91274b73-f7be-4066-a4ab-ec30af30016e,Missing tables headers in file:91274b73-f7be-4066-a4ab-ec30af30016e.md +Warning,91274b73-f7be-4066-a4ab-ec30af30016e,Found nested table in md file:91274b73-f7be-4066-a4ab-ec30af30016e.md +Warning,91274b73-f7be-4066-a4ab-ec30af30016e,Could not Add new line after images in md file:91274b73-f7be-4066-a4ab-ec30af30016e.md +Warning,918a570e-ce86-4ff7-857f-d08dbb35d08d,Found a an ul list inside a table in html file:918a570e-ce86-4ff7-857f-d08dbb35d08d.xml +Warning,93327a06-ed2c-43f2-a40a-d7257f61f915,Found a an ul list inside a table in html file:93327a06-ed2c-43f2-a40a-d7257f61f915.xml +Warning,93327a06-ed2c-43f2-a40a-d7257f61f915,Missing tables headers in file:93327a06-ed2c-43f2-a40a-d7257f61f915.md +Warning,93327a06-ed2c-43f2-a40a-d7257f61f915,Could not Add new line after images in md file:93327a06-ed2c-43f2-a40a-d7257f61f915.md +Warning,937a136c-7cc1-4e61-8a2c-2161d484c13f,Found nested table in md file:937a136c-7cc1-4e61-8a2c-2161d484c13f.md +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found a an ul list inside a table in html file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.xml +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

SharePoint_AdminContent_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2016: AppMng_Service_DB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Bdc_Service_DB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2016: Managed Metadata Service_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2013: Managed Metadata Service Application_Metadata_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2016: PerformancePoint Service Application _<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2013: PerformancePoint Service _<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

DefaultPowerPivotServiceApplicationDB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_DB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_AnalyticsReportingStoreDB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_CrawlStoreDB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_LinkStoreDB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Secure_Store_Service_DB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2016: TranslationService_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2013: SharePoint Translation Services_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2016: StateService_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

2013: SessionStateService_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_ProfileDB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_SyncDB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_SocialDB_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

WordAutomationServices_<GUID>

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Report Server Catalog (ReportingService_<GUID>) - Stores all report metadata including report definitions- report history and snapshots- and scheduling information.

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

ReportServerTempDB (ReportingService_<GUID>_TempDB) - Stores all the temporary snapshots while reports are running.

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Report Server Alerting (ReportingService_<GUID>_Alerting) - Stores all Data Alerts and runtime information.

in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md total found:0 +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Found nested table in md file:94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8.md +Warning,9528dfeb-3f44-4c76-8d07-eb916e04b674,Found a an ul list inside a table in html file:9528dfeb-3f44-4c76-8d07-eb916e04b674.xml +Warning,9528dfeb-3f44-4c76-8d07-eb916e04b674,Found nested table in md file:9528dfeb-3f44-4c76-8d07-eb916e04b674.md +Warning,9528dfeb-3f44-4c76-8d07-eb916e04b674,Could not Add new line after images in md file:9528dfeb-3f44-4c76-8d07-eb916e04b674.md +Warning,95e12c80-7a86-4655-ba11-a05b9587fee0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Database role membership for: <database> in md file:95e12c80-7a86-4655-ba11-a05b9587fee0.md total found:0 +Warning,96dc4ef1-cec8-47d0-b995-46bca3e8eda2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:96dc4ef1-cec8-47d0-b995-46bca3e8eda2.md total found:0 +Warning,96dc4ef1-cec8-47d0-b995-46bca3e8eda2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:96dc4ef1-cec8-47d0-b995-46bca3e8eda2.md total found:0 +Warning,982d3ab2-d1a6-4625-b4c6-e12a1f4532d5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<AppID> in md file:982d3ab2-d1a6-4625-b4c6-e12a1f4532d5.md total found:0 +Warning,982d3ab2-d1a6-4625-b4c6-e12a1f4532d5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<AppID> in md file:982d3ab2-d1a6-4625-b4c6-e12a1f4532d5.md total found:0 +Warning,982d3ab2-d1a6-4625-b4c6-e12a1f4532d5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Domain\UserName> in md file:982d3ab2-d1a6-4625-b4c6-e12a1f4532d5.md total found:0 +Warning,982d3ab2-d1a6-4625-b4c6-e12a1f4532d5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Domain\UserName> in md file:982d3ab2-d1a6-4625-b4c6-e12a1f4532d5.md total found:0 +Warning,99684f0b-f617-4c10-8420-d4d0adea3687,Found a an ul list inside a table in html file:99684f0b-f617-4c10-8420-d4d0adea3687.xml +Warning,99684f0b-f617-4c10-8420-d4d0adea3687,Missing tables headers in file:99684f0b-f617-4c10-8420-d4d0adea3687.md +Warning,99684f0b-f617-4c10-8420-d4d0adea3687,Could not Add new line after images in md file:99684f0b-f617-4c10-8420-d4d0adea3687.md +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found a an ul list inside a table in html file:9b1e8b21-7675-4186-beb6-3adeef4360e6.xml +Error,9b1e8b21-7675-4186-beb6-3adeef4360e6,Checking for list in tables in file:9b1e8b21-7675-4186-beb6-3adeef4360e6.xml message:System.Collections.ArrayList +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

SharePoint_AdminContent_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

AppMng_Service_DB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Bdc_Service_DB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_DB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_AnalyticsReportingStoreDB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_CrawlStoreDB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Search_Service_Application_LinkStoreDB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Secure_Store_Service_DB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_ProfileDB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_SyncDB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

User Profile Service Application_SocialDB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

WordAutomationServices_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Managed Metadata Service_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

TranslationService_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

DefaultPowerPivotServiceApplicationDB_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

PerformancePoint Service Application _<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

StateService_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

ReportingService_<GUID>

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

ReportingService_<GUID>_TempDB

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b1e8b21-7675-4186-beb6-3adeef4360e6,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

ReportingService_<GUID>_Alerting

in md file:9b1e8b21-7675-4186-beb6-3adeef4360e6.md total found:0 +Warning,9b5a1f99-0193-4a97-b0d1-4a5633b32c43,Found a an ul list inside a table in html file:9b5a1f99-0193-4a97-b0d1-4a5633b32c43.xml +Warning,9ccce076-f47b-44b8-9ec3-e0dcd46e9985,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Recycling Settings for an Application Pool <recycling> in md file:9ccce076-f47b-44b8-9ec3-e0dcd46e9985.md total found:0 +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<service type> in md file:9cd888dc-9104-422e-8d8a-d795f0b1c0d0.md total found:0 +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<instance name> in md file:9cd888dc-9104-422e-8d8a-d795f0b1c0d0.md total found:0 +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<service type> in md file:9cd888dc-9104-422e-8d8a-d795f0b1c0d0.md total found:0 +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<instance name> in md file:9cd888dc-9104-422e-8d8a-d795f0b1c0d0.md total found:0 +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:00000003-0000-0ff1-ce00-000000000000/*.<public domain name>.com in md file:9cd888dc-9104-422e-8d8a-d795f0b1c0d0.md total found:0 +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:00000001-0000-0000-c000-000000000000@<context ID> in md file:9cd888dc-9104-422e-8d8a-d795f0b1c0d0.md total found:0 +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

where <context ID> is the context ID of your SharePoint Online tenancy- which is the value in the $spocontextID variable.

in md file:9cd888dc-9104-422e-8d8a-d795f0b1c0d0.md total found:0 +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Missing tables headers in file:9cd888dc-9104-422e-8d8a-d795f0b1c0d0.md +Warning,9cea4a3d-c196-4d9e-942d-2677a6c15c13,Video is found in md file:9cea4a3d-c196-4d9e-942d-2677a6c15c13.md total found:1 +Warning,9cea4a3d-c196-4d9e-942d-2677a6c15c13,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

On the User Mapping page- click the SharePoint Admin content database (usually named SharePoint_AdminContent_<GUID>).

in md file:9cea4a3d-c196-4d9e-942d-2677a6c15c13.md total found:0 +Warning,9cf64bff-f52b-46c9-bf25-d38d6b15e25d,Found a an ul list inside a table in html file:9cf64bff-f52b-46c9-bf25-d38d6b15e25d.xml +Warning,9f039270-d426-4e79-b608-8db792de74ed,Found a an ul list inside a table in html file:9f039270-d426-4e79-b608-8db792de74ed.xml +Warning,9f0df411-ba75-4d04-9195-836129fe2282,Found a an ul list inside a table in html file:9f0df411-ba75-4d04-9195-836129fe2282.xml +Error,9f0df411-ba75-4d04-9195-836129fe2282,Checking for list in tables in file:9f0df411-ba75-4d04-9195-836129fe2282.xml message:System.Collections.ArrayList +Warning,9fc3a696-b2cb-435c-8199-7048953ec609,Found a an ul list inside a table in html file:9fc3a696-b2cb-435c-8199-7048953ec609.xml +Warning,9fc3a696-b2cb-435c-8199-7048953ec609,Missing tables headers in file:9fc3a696-b2cb-435c-8199-7048953ec609.md +Warning,9ff8ab96-6028-4f6a-8cc2-2ebe7eb19413,Found a an ul list inside a table in html file:9ff8ab96-6028-4f6a-8cc2-2ebe7eb19413.xml +Warning,a0f2c651-e353-4197-b0dd-0cbe6f18c811,Could not Add new line after images in md file:a0f2c651-e353-4197-b0dd-0cbe6f18c811.md +Warning,a193cfdb-ac5e-45fa-bf83-87849e38ac27,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

+ Secure Store Service application - Secure_Store_Service_DB_<GUID>

in md file:a193cfdb-ac5e-45fa-bf83-87849e38ac27.md total found:0 +Warning,a193cfdb-ac5e-45fa-bf83-87849e38ac27,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

App Management service application - App_Management_<GUID>

in md file:a193cfdb-ac5e-45fa-bf83-87849e38ac27.md total found:0 +Warning,a193cfdb-ac5e-45fa-bf83-87849e38ac27,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteCollectionGUIDorURL> in md file:a193cfdb-ac5e-45fa-bf83-87849e38ac27.md total found:0 +Warning,a193cfdb-ac5e-45fa-bf83-87849e38ac27,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFile> in md file:a193cfdb-ac5e-45fa-bf83-87849e38ac27.md total found:0 +Warning,a2609bd3-928a-479a-9c8d-c0a751d76fcf,Found a an ul list inside a table in html file:a2609bd3-928a-479a-9c8d-c0a751d76fcf.xml +Warning,a2609bd3-928a-479a-9c8d-c0a751d76fcf,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<80% shows green

in md file:a2609bd3-928a-479a-9c8d-c0a751d76fcf.md total found:0 +Warning,a29d4cc4-7944-4c3e-94ea-d681f432f07b,Found nested table in md file:a29d4cc4-7944-4c3e-94ea-d681f432f07b.md +Warning,a2db324b-bcbe-40b4-8fa1-66f16cc89890,Could not Add new line after images in md file:a2db324b-bcbe-40b4-8fa1-66f16cc89890.md +Warning,a2ef35c4-6b29-4ad1-8652-48a019838ea0,Video is found in md file:a2ef35c4-6b29-4ad1-8652-48a019838ea0.md total found:1 +Warning,a3b78815-c1a0-47e0-97a3-d255f9efc96d,Found a an ul list inside a table in html file:a3b78815-c1a0-47e0-97a3-d255f9efc96d.xml +Warning,a5c66813-3523-40d1-99d8-86e8359b6c73,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<URL for the new site collection> in md file:a5c66813-3523-40d1-99d8-86e8359b6c73.md total found:0 +Warning,a5c66813-3523-40d1-99d8-86e8359b6c73,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<domain\user> in md file:a5c66813-3523-40d1-99d8-86e8359b6c73.md total found:0 +Warning,a61b531f-218e-4edf-ab90-f2f30f490900,Missing tables headers in file:a61b531f-218e-4edf-ab90-f2f30f490900.md +Warning,a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a.md total found:0 +Warning,a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServerName> in md file:a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a.md total found:0 +Warning,a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a.md total found:0 +Warning,a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WindowsPowerShellCredentialObject> in md file:a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a.md total found:0 +Warning,a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a.md total found:0 +Warning,a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServerName> in md file:a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a.md total found:0 +Warning,a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SystemDrive> in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md total found:0 +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Missing tables headers in file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md +Warning,a7960bf4-d5be-4ad7-a430-724ef194ad39,Found nested table in md file:a7960bf4-d5be-4ad7-a430-724ef194ad39.md +Warning,a8653e44-5bbc-4ca1-8e9a-61cc41349df1,Found a an ul list inside a table in html file:a8653e44-5bbc-4ca1-8e9a-61cc41349df1.xml +Warning,a8653e44-5bbc-4ca1-8e9a-61cc41349df1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Browsing the Review database status page (<your_SharePoint_CentralAdmin_URL>/_admin/UpgradeStatus.aspx) on the Central Administration web site may result in a timeout.

in md file:a8653e44-5bbc-4ca1-8e9a-61cc41349df1.md total found:0 +Warning,a8653e44-5bbc-4ca1-8e9a-61cc41349df1,Found nested table in md file:a8653e44-5bbc-4ca1-8e9a-61cc41349df1.md +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found a an ul list inside a table in html file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.xml +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

There is a highly consistent intra-farm latency of <1ms one way- 99.9% of the time over a period of ten minutes. (Intra-farm latency is commonly defined as the latency between the front-end web servers and the database servers.)

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

The installer installs from the file that you specify in the command-line options described in the following list. In this list- <file > signifies the file from which you want to install. If you do not specify the <file > option- the installer downloads the file from the Internet and installs it. If the option does not apply to the current operating system- it is ignored.

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/SQLNCli:<file > Install Microsoft SQL Server 2008 SP1 Native Client from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/SQLNCli:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/PowerShell:<file > Install Windows Management Framework 3.0 from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/PowerShell:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/NETFX:<file > Install Microsoft .NET Framework version 4.5 from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/NETFX:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/IDFX:<file > Install Windows Identity Foundation (KB974405) from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/IDFX:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/IDFX11:<file > Install Windows Identity Foundation v1.1 from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/IDFX11:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/Sync:<file > Install Microsoft Sync Framework Runtime SP1 v1.0 (x64) from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/Sync:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/AppFabric:<file > Install Windows Server AppFabric from <file > (AppFabric must be installed with the options /i CacheClient-CachingService-CacheAdmin /gac)

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/AppFabric:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/KB2671763:<file > Install Microsoft AppFabric 1.1 for Windows Server (AppFabric 1.1) from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/KB2671763:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/MSIPCClient:<file > Install Microsoft Information Protection and Control Client from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/MSIPCClient:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

/WCFDataServices:<file > Install Microsoft WCF Data Services from <file >

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:/WCFDataServices:<file > in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a88d3f72-7ac3-4f08-b302-c4ca0a796268,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

The prerequisite installer creates log files at %TEMP%\prerequisiteinstaller.<date>.<time>.log. You can check these log files for specific details about all changes the installer makes to the target computer.

in md file:a88d3f72-7ac3-4f08-b302-c4ca0a796268.md total found:0 +Warning,a96075c6-d315-40a8-a739-49b91c61978f,Found nested table in md file:a96075c6-d315-40a8-a739-49b91c61978f.md +Warning,a96cfa2d-87f8-4991-801c-fd5482d49d0b,Could not Add new line after images in md file:a96cfa2d-87f8-4991-801c-fd5482d49d0b.md +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found a an ul list inside a table in html file:a9edfdaf-99da-4740-9e2a-631aded785ae.xml +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceGUID> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Name/GUID of service application> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServerName\DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServerName\DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewDatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<OldDatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewDatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<OldDatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseID> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseID> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DbName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SQLServerName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SQLServerName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServer> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServer> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServer> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceGUID> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewDbName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NewServerName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Search Server> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,a9edfdaf-99da-4740-9e2a-631aded785ae,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:a9edfdaf-99da-4740-9e2a-631aded785ae.md total found:0 +Warning,ac2338f5-1b06-4a7c-9dc0-4751b6421cb3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Service application display name> in md file:ac2338f5-1b06-4a7c-9dc0-4751b6421cb3.md total found:0 +Warning,ac2338f5-1b06-4a7c-9dc0-4751b6421cb3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Service application display name> in md file:ac2338f5-1b06-4a7c-9dc0-4751b6421cb3.md total found:0 +Warning,adbb853e-d8ef-48bb-9ca1-55612809c680,Found a an ul list inside a table in html file:adbb853e-d8ef-48bb-9ca1-55612809c680.xml +Warning,adbb853e-d8ef-48bb-9ca1-55612809c680,Could not Add new line after images in md file:adbb853e-d8ef-48bb-9ca1-55612809c680.md +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Area> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Area> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Category> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Category> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<EventID> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<EventID> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<string> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<string> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Process> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Process> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae1e3447-46e2-45f9-852a-ab39f23345d4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<property name>:<value> in md file:ae1e3447-46e2-45f9-852a-ab39f23345d4.md total found:0 +Warning,ae92f528-9768-4ea1-9b19-110fb4c88c7f,Could not Add new line after images in md file:ae92f528-9768-4ea1-9b19-110fb4c88c7f.md +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found a an ul list inside a table in html file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.xml +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<configuration> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<name of your Search service application> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\15\CONFIG\SearchConnectors\Documentum\MODEL.xml> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MyWebTopServer:PortOfMyWebTopServer> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MyRepository n> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DFSWebServices n>:<30000> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<name of your Search service application> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MyWebTopServer:PortOfMyWebTopServer> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourDatabaseServerName> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourDatabaseInstanceName> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourMappingDatabaseName> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<YourMappingTableName> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MyRepository n> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DFSWebServices n>:<30000> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

dctm://<clientapphostname>/<repository name>

in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

dctm://<clientapphostname>/<repository name>/<cabinet name>

in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

dctm://<clientapphostname>/<repository name>/<cabinet name>/<folder name>

in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

dctm://<clientapphostname>/<repository name>/<cabinet name>/<folder name>/…/<folder name>?DocSysID=<r_object_id> (where r_object_id is the object id of that document)

in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<clientapphostname> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<clientapphostname> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<repository name> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<cabinet name> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<folder name> in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md total found:0 +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Missing tables headers in file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Could not change drive path:New-SPEnterpriseSearchSecurityTrimmer -SearchApplication <name of your Search service application> -typeName "Microsoft.Office.Server.Search.Connector.Documentum.Trimmers.DctmTrimPre, Microsoft.Office.Server.Search.Connector.Documentum.Trimmers, Version=15.0.0.0,Culture=neutral, PublicKeyToken=48e046c834625a88, processorArchitecture=MSIL" -id 26 -RulePath dctm:\\* in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md +Warning,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,Could not change drive path:New-SPEnterpriseSearchSecurityTrimmer -SearchApplication <name of your Search service application> -typeName "Microsoft.Office.Server.Search.Connector.Documentum.Trimmers.DctmTrimPost, Microsoft.Office.Server.Search.Connector.Documentum.Trimmers, Version=15.0.0.0,Culture=neutral, PublicKeyToken=48e046c834625a88, processorArchitecture=MSIL" -id 17 -RulePath dctm:\\* in md file:b17a56ea-2e7f-43c6-9a17-00ae1f5c4089.md +Warning,b23e4fb4-6ee1-451e-92b3-7c90be5dc7e7,Found nested table in md file:b23e4fb4-6ee1-451e-92b3-7c90be5dc7e7.md +Warning,b291ea58-cfda-48ec-92d7-5180cb7e9469,Found a an ul list inside a table in html file:b291ea58-cfda-48ec-92d7-5180cb7e9469.xml +Warning,b291ea58-cfda-48ec-92d7-5180cb7e9469,Missing tables headers in file:b291ea58-cfda-48ec-92d7-5180cb7e9469.md +Warning,b291ea58-cfda-48ec-92d7-5180cb7e9469,Could not Add new line after images in md file:b291ea58-cfda-48ec-92d7-5180cb7e9469.md +Warning,b2b379b8-838c-4faa-b3ca-9d1eacd94b01,Video is found in md file:b2b379b8-838c-4faa-b3ca-9d1eacd94b01.md total found:1 +Warning,b35d9b02-2207-417c-bb90-870474b6f57c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationURL> in md file:b35d9b02-2207-417c-bb90-870474b6f57c.md total found:0 +Warning,b35d9b02-2207-417c-bb90-870474b6f57c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationURL> in md file:b35d9b02-2207-417c-bb90-870474b6f57c.md total found:0 +Warning,b37c1d36-5bfe-4f76-bb03-2c5436c043a2,Missing tables headers in file:b37c1d36-5bfe-4f76-bb03-2c5436c043a2.md +Warning,b37c1d36-5bfe-4f76-bb03-2c5436c043a2,Found nested table in md file:b37c1d36-5bfe-4f76-bb03-2c5436c043a2.md +Warning,b3cb17a1-939c-4314-9f83-3c6b8a309bba,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteURL> in md file:b3cb17a1-939c-4314-9f83-3c6b8a309bba.md total found:0 +Warning,b3cb17a1-939c-4314-9f83-3c6b8a309bba,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ImportFileName> in md file:b3cb17a1-939c-4314-9f83-3c6b8a309bba.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<domain> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<username> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteCollection> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<User> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteCollection> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<User> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<domain> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<username> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<domain> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b3d2f46d-783c-4f81-9c0a-d41a3486917e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<username> in md file:b3d2f46d-783c-4f81-9c0a-d41a3486917e.md total found:0 +Warning,b62b6690-a1a6-4163-bdb5-8abae968c5c8,Missing tables headers in file:b62b6690-a1a6-4163-bdb5-8abae968c5c8.md +Warning,b62b6690-a1a6-4163-bdb5-8abae968c5c8,Found nested table in md file:b62b6690-a1a6-4163-bdb5-8abae968c5c8.md +Warning,b6580f87-40b4-4768-b589-6ba54013f7e4,Could not Add new line after images in md file:b6580f87-40b4-4768-b589-6ba54013f7e4.md +Warning,b71ccbbf-37c0-46c2-a403-20934e1e104e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Use the following blocks of PowerShell commands to create the components in Azure. Specify the values for the variables- removing the < and > characters. Note that these PowerShell command blocks use values from the following tables:

in md file:b71ccbbf-37c0-46c2-a403-20934e1e104e.md total found:0 +Warning,b71ccbbf-37c0-46c2-a403-20934e1e104e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Click Log On tab- ensure the This Account radio button is selected- then type <your domain>\sqlservice in Account Name . Type the sqlservice account password in Password and Confirm password - and then click OK .

in md file:b71ccbbf-37c0-46c2-a403-20934e1e104e.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://WebApplication> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<http://WebApplication> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceAccount> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceAccount> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationDisplayName> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationDisplayName> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Rights> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Rights> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationDisplayName> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b81f80f1-182f-42eb-9546-8a621a4f069f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationDisplayName> in md file:b81f80f1-182f-42eb-9546-8a621a4f069f.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found a an ul list inside a table in html file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.xml +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<externalUrl> in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<bridging URL> in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<friendly name of the published application> in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<certificate thumbprint> in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

:<populated at run time>

in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

:<relying party name>

in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

: https://<bridging URL>/

in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

: <certificate thumbprint>

in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

: <certificate thumbprint>

in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

: https://<external URL>/

in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

: <friendly name of the published application>

in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md total found:0 +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Missing tables headers in file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md +Warning,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,Could not Add new line after images in md file:b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1.md +Warning,bbb62edb-def7-45dd-931c-78746c3d9fa5,Video is found in md file:bbb62edb-def7-45dd-931c-78746c3d9fa5.md total found:1 +Warning,bcbae7bd-656b-4003-969c-8411b81fcd77,Found herf tag with an image in file:bcbae7bd-656b-4003-969c-8411b81fcd77.md total found:6 +Warning,bcbae7bd-656b-4003-969c-8411b81fcd77,Found a an ul list inside a table in html file:bcbae7bd-656b-4003-969c-8411b81fcd77.xml +Warning,bcbddee7-1c77-4788-9a32-fb585c48ee37,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<server name> is the server to change.

in md file:bcbddee7-1c77-4788-9a32-fb585c48ee37.md total found:0 +Warning,bcbddee7-1c77-4788-9a32-fb585c48ee37,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<server role> in md file:bcbddee7-1c77-4788-9a32-fb585c48ee37.md total found:0 +Warning,bd9db767-6b87-450d-a8e6-9dc684d59ae4,Found a an ul list inside a table in html file:bd9db767-6b87-450d-a8e6-9dc684d59ae4.xml +Warning,bd9db767-6b87-450d-a8e6-9dc684d59ae4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Share <SearchCenterName> in md file:bd9db767-6b87-450d-a8e6-9dc684d59ae4.md total found:0 +Warning,bd9db767-6b87-450d-a8e6-9dc684d59ae4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchCenterName> Visitors [Read] in md file:bd9db767-6b87-450d-a8e6-9dc684d59ae4.md total found:0 +Warning,be4e1054-ada6-4eea-a92d-e35d1da61eb9,Could not Add new line after images in md file:be4e1054-ada6-4eea-a92d-e35d1da61eb9.md +Warning,bf9068c7-9187-49bb-9946-c298389bf4b0,Found nested table in md file:bf9068c7-9187-49bb-9946-c298389bf4b0.md +Warning,bf94ede1-79cc-4016-99f3-a1eef244fdf3,Found a an ol list inside a table in html file:bf94ede1-79cc-4016-99f3-a1eef244fdf3.xml +Warning,bf94ede1-79cc-4016-99f3-a1eef244fdf3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<appDomain> in md file:bf94ede1-79cc-4016-99f3-a1eef244fdf3.md total found:0 +Warning,bf94ede1-79cc-4016-99f3-a1eef244fdf3,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<appDomain> in md file:bf94ede1-79cc-4016-99f3-a1eef244fdf3.md total found:0 +Warning,bfa2f924-f411-4b13-8c24-bf251d7e4c91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDb> in md file:bfa2f924-f411-4b13-8c24-bf251d7e4c91.md total found:0 +Warning,bfa2f924-f411-4b13-8c24-bf251d7e4c91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DbServer> in md file:bfa2f924-f411-4b13-8c24-bf251d7e4c91.md total found:0 +Warning,bfa2f924-f411-4b13-8c24-bf251d7e4c91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDb> in md file:bfa2f924-f411-4b13-8c24-bf251d7e4c91.md total found:0 +Warning,bfa2f924-f411-4b13-8c24-bf251d7e4c91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DbServer> in md file:bfa2f924-f411-4b13-8c24-bf251d7e4c91.md total found:0 +Warning,bfa2f924-f411-4b13-8c24-bf251d7e4c91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentdBName> in md file:bfa2f924-f411-4b13-8c24-bf251d7e4c91.md total found:0 +Warning,bfa2f924-f411-4b13-8c24-bf251d7e4c91,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentdBName> in md file:bfa2f924-f411-4b13-8c24-bf251d7e4c91.md total found:0 +Warning,c24cffe8-fa32-43e4-95ed-42118ef9643d,Found a an ul list inside a table in html file:c24cffe8-fa32-43e4-95ed-42118ef9643d.xml +Warning,c24cffe8-fa32-43e4-95ed-42118ef9643d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Typically- the enterprise Search Center in SharePoint Online is at https://<domain >.sharepoint.com/search—for example- https://adventureworks.sharepoint.com/search.

in md file:c24cffe8-fa32-43e4-95ed-42118ef9643d.md total found:0 +Warning,c24cffe8-fa32-43e4-95ed-42118ef9643d,Missing tables headers in file:c24cffe8-fa32-43e4-95ed-42118ef9643d.md +Warning,c24cffe8-fa32-43e4-95ed-42118ef9643d,Could not Add new line after images in md file:c24cffe8-fa32-43e4-95ed-42118ef9643d.md +Warning,c2eda191-1814-423b-882f-1fdafe9df6c9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Site> in md file:c2eda191-1814-423b-882f-1fdafe9df6c9.md total found:0 +Warning,c2eda191-1814-423b-882f-1fdafe9df6c9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Template> in md file:c2eda191-1814-423b-882f-1fdafe9df6c9.md total found:0 +Warning,c2eda191-1814-423b-882f-1fdafe9df6c9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Site> in md file:c2eda191-1814-423b-882f-1fdafe9df6c9.md total found:0 +Warning,c2eda191-1814-423b-882f-1fdafe9df6c9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Limit> in md file:c2eda191-1814-423b-882f-1fdafe9df6c9.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<consumingfarmid> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<consumingfarmid> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NamedAccessRights> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Consumingfarmid> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<NamedAccessRights> is the name of the access right from the Get-SPServiceApplicationSecurity <GUID>.NamedAccessRights.

in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<NamedAccessRights> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c598457b-38d9-434c-b715-3786109cd27e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<consumingfarmid> in md file:c598457b-38d9-434c-b715-3786109cd27e.md total found:0 +Warning,c5c6fd31-d747-49c0-9784-b4f29bd82809,Found a an ul list inside a table in html file:c5c6fd31-d747-49c0-9784-b4f29bd82809.xml +Warning,c5d39627-dfa6-4122-8571-a38bdd3ab4d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteCollection> in md file:c5d39627-dfa6-4122-8571-a38bdd3ab4d9.md total found:0 +Warning,c5d39627-dfa6-4122-8571-a38bdd3ab4d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<State> in md file:c5d39627-dfa6-4122-8571-a38bdd3ab4d9.md total found:0 +Warning,c5d39627-dfa6-4122-8571-a38bdd3ab4d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteCollection> in md file:c5d39627-dfa6-4122-8571-a38bdd3ab4d9.md total found:0 +Warning,c5d39627-dfa6-4122-8571-a38bdd3ab4d9,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<State> in md file:c5d39627-dfa6-4122-8571-a38bdd3ab4d9.md total found:0 +Warning,c75f3390-283f-4380-b740-e672ea8b933d,Missing tables headers in file:c75f3390-283f-4380-b740-e672ea8b933d.md +Warning,c8209ecc-59e4-4568-a7e6-782a6b0ab02f,Video is found in md file:c8209ecc-59e4-4568-a7e6-782a6b0ab02f.md total found:1 +Warning,c824fa0f-bae9-4791-92ee-38d8e70140ec,Found a an ul list inside a table in html file:c824fa0f-bae9-4791-92ee-38d8e70140ec.xml +Warning,ca092ed2-4aa2-4c2e-b273-661ca6a76e01,Found a an ul list inside a table in html file:ca092ed2-4aa2-4c2e-b273-661ca6a76e01.xml +Warning,cb57d4f7-8353-420b-8a10-d05c9bdf1b56,Could not Add new line after images in md file:cb57d4f7-8353-420b-8a10-d05c9bdf1b56.md +Warning,cb6871cc-7fc5-4b54-9940-8c0ed51cb08f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<file location and name.csv> in md file:cb6871cc-7fc5-4b54-9940-8c0ed51cb08f.md total found:0 +Warning,cbb3b242-76ed-4539-b454-4685a84d57c5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolderName> in md file:cbb3b242-76ed-4539-b454-4685a84d57c5.md total found:0 +Warning,cbb3b242-76ed-4539-b454-4685a84d57c5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationName> in md file:cbb3b242-76ed-4539-b454-4685a84d57c5.md total found:0 +Warning,cbb3b242-76ed-4539-b454-4685a84d57c5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:cbb3b242-76ed-4539-b454-4685a84d57c5.md total found:0 +Warning,cbb3b242-76ed-4539-b454-4685a84d57c5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolderName> in md file:cbb3b242-76ed-4539-b454-4685a84d57c5.md total found:0 +Warning,cbb3b242-76ed-4539-b454-4685a84d57c5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationName> in md file:cbb3b242-76ed-4539-b454-4685a84d57c5.md total found:0 +Warning,cbb3b242-76ed-4539-b454-4685a84d57c5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:cbb3b242-76ed-4539-b454-4685a84d57c5.md total found:0 +Warning,cbb3b242-76ed-4539-b454-4685a84d57c5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolderName> in md file:cbb3b242-76ed-4539-b454-4685a84d57c5.md total found:0 +Warning,cbb3b242-76ed-4539-b454-4685a84d57c5,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Farm\<Web application> in md file:cbb3b242-76ed-4539-b454-4685a84d57c5.md total found:0 +Warning,cd646bb3-28c6-4040-866c-7d7936837ade,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplication> in md file:cd646bb3-28c6-4040-866c-7d7936837ade.md total found:0 +Warning,cd646bb3-28c6-4040-866c-7d7936837ade,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SuperUser> in md file:cd646bb3-28c6-4040-866c-7d7936837ade.md total found:0 +Warning,cd646bb3-28c6-4040-866c-7d7936837ade,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SuperReader> in md file:cd646bb3-28c6-4040-866c-7d7936837ade.md total found:0 +Warning,cd646bb3-28c6-4040-866c-7d7936837ade,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplication> in md file:cd646bb3-28c6-4040-866c-7d7936837ade.md total found:0 +Warning,cd646bb3-28c6-4040-866c-7d7936837ade,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SuperUser> in md file:cd646bb3-28c6-4040-866c-7d7936837ade.md total found:0 +Warning,cd646bb3-28c6-4040-866c-7d7936837ade,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SuperReader> in md file:cd646bb3-28c6-4040-866c-7d7936837ade.md total found:0 +Warning,cdaf9810-59dc-4afb-af6a-36ceb3795da7,Found a an ul list inside a table in html file:cdaf9810-59dc-4afb-af6a-36ceb3795da7.xml +Warning,cdd1d3d6-034e-458f-9324-c51d90fa9273,Found a an ul list inside a table in html file:cdd1d3d6-034e-458f-9324-c51d90fa9273.xml +Warning,cdd1d3d6-034e-458f-9324-c51d90fa9273,Found nested table in md file:cdd1d3d6-034e-458f-9324-c51d90fa9273.md +Warning,cf19810b-5548-447c-a94d-026ad6e9d096,Found a an ul list inside a table in html file:cf19810b-5548-447c-a94d-026ad6e9d096.xml +Warning,d08d6d65-23c2-48cb-a871-1e021a382e5e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:d08d6d65-23c2-48cb-a871-1e021a382e5e.md total found:0 +Warning,d08d6d65-23c2-48cb-a871-1e021a382e5e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SecureStoreService> in md file:d08d6d65-23c2-48cb-a871-1e021a382e5e.md total found:0 +Warning,d0a50e40-5322-4f7a-a3a4-c4660c879666,Found a an ol list inside a table in html file:d0a50e40-5322-4f7a-a3a4-c4660c879666.xml +Warning,d0a50e40-5322-4f7a-a3a4-c4660c879666,Missing tables headers in file:d0a50e40-5322-4f7a-a3a4-c4660c879666.md +Warning,d0a50e40-5322-4f7a-a3a4-c4660c879666,Could not Add new line after images in md file:d0a50e40-5322-4f7a-a3a4-c4660c879666.md +Warning,d0e68cf4-80f6-4f1f-af49-a3b9c43408ac,Found a an ul list inside a table in html file:d0e68cf4-80f6-4f1f-af49-a3b9c43408ac.xml +Warning,d0e68cf4-80f6-4f1f-af49-a3b9c43408ac,Missing tables headers in file:d0e68cf4-80f6-4f1f-af49-a3b9c43408ac.md +Warning,d0e68cf4-80f6-4f1f-af49-a3b9c43408ac,Found nested table in md file:d0e68cf4-80f6-4f1f-af49-a3b9c43408ac.md +Warning,d21f7d68-c18b-4253-af8b-0765c86a331b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Database role membership for: <database> in md file:d21f7d68-c18b-4253-af8b-0765c86a331b.md total found:0 +Warning,d47575fa-bb85-4017-8db7-5e25f98ba171,Found a an ul list inside a table in html file:d47575fa-bb85-4017-8db7-5e25f98ba171.xml +Warning,d6845f9b-7c1e-4220-a24d-1e5cade8f0d8,Found a an ul list inside a table in html file:d6845f9b-7c1e-4220-a24d-1e5cade8f0d8.xml +Warning,d6845f9b-7c1e-4220-a24d-1e5cade8f0d8,Missing tables headers in file:d6845f9b-7c1e-4220-a24d-1e5cade8f0d8.md +Warning,d6845f9b-7c1e-4220-a24d-1e5cade8f0d8,Found nested table in md file:d6845f9b-7c1e-4220-a24d-1e5cade8f0d8.md +Warning,d845819f-0cbf-4595-bb14-19414acbd79b,Video is found in md file:d845819f-0cbf-4595-bb14-19414acbd79b.md total found:1 +Warning,d849b7df-b26d-45f6-a74f-6641f18788cf,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<RestoreShare> in md file:d849b7df-b26d-45f6-a74f-6641f18788cf.md total found:0 +Warning,d8635abe-1b1b-42db-95ff-ab9341d957e2,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<video> in md file:d8635abe-1b1b-42db-95ff-ab9341d957e2.md total found:0 +Warning,d9dac189-0736-448d-928c-68bf38603613,Found a an ul list inside a table in html file:d9dac189-0736-448d-928c-68bf38603613.xml +Warning,d9dac189-0736-448d-928c-68bf38603613,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<AGGroupName> is the name of the Avaliability Group.

in md file:d9dac189-0736-448d-928c-68bf38603613.md total found:0 +Warning,d9dac189-0736-448d-928c-68bf38603613,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<DatabaseName> is the name of the database that you are adding to the Availability Group

in md file:d9dac189-0736-448d-928c-68bf38603613.md total found:0 +Warning,d9dac189-0736-448d-928c-68bf38603613,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

If the optional -FileShare parameter is used- <\\server\share> is the name of the server and the share that you use.

in md file:d9dac189-0736-448d-928c-68bf38603613.md total found:0 +Warning,d9dac189-0736-448d-928c-68bf38603613,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<GUID> is the ID of the database that you move.

in md file:d9dac189-0736-448d-928c-68bf38603613.md total found:0 +Warning,d9dac189-0736-448d-928c-68bf38603613,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<DBServerName> is the name or alias of the new SQL Server or is the AlwaysOn Availability Group listener DNS name.

in md file:d9dac189-0736-448d-928c-68bf38603613.md total found:0 +Warning,d9dac189-0736-448d-928c-68bf38603613,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<DBServerName> is the name or alias of the mirrored SQL Server.

in md file:d9dac189-0736-448d-928c-68bf38603613.md total found:0 +Warning,db44c8d7-e081-42a3-a42a-2ee1b369dd47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:db44c8d7-e081-42a3-a42a-2ee1b369dd47.md total found:0 +Warning,db44c8d7-e081-42a3-a42a-2ee1b369dd47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDatabaseName> in md file:db44c8d7-e081-42a3-a42a-2ee1b369dd47.md total found:0 +Warning,dca8b241-85f9-486c-97eb-ed9ef23622b8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:dca8b241-85f9-486c-97eb-ed9ef23622b8.md total found:0 +Warning,dca8b241-85f9-486c-97eb-ed9ef23622b8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MaxAuthors> in md file:dca8b241-85f9-486c-97eb-ed9ef23622b8.md total found:0 +Warning,dca8b241-85f9-486c-97eb-ed9ef23622b8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:dca8b241-85f9-486c-97eb-ed9ef23622b8.md total found:0 +Warning,dca8b241-85f9-486c-97eb-ed9ef23622b8,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<MaxAuthors> in md file:dca8b241-85f9-486c-97eb-ed9ef23622b8.md total found:0 +Warning,dee7c975-5738-494f-bf70-31b0e0bc8206,Found a an ul list inside a table in html file:dee7c975-5738-494f-bf70-31b0e0bc8206.xml +Warning,dee7c975-5738-494f-bf70-31b0e0bc8206,Missing tables headers in file:dee7c975-5738-494f-bf70-31b0e0bc8206.md +Warning,df399658-84ac-4ca6-aaf4-378eef361cbb,Found a an ul list inside a table in html file:df399658-84ac-4ca6-aaf4-378eef361cbb.xml +Warning,df399658-84ac-4ca6-aaf4-378eef361cbb,Missing tables headers in file:df399658-84ac-4ca6-aaf4-378eef361cbb.md +Warning,df399658-84ac-4ca6-aaf4-378eef361cbb,Could not Add new line after images in md file:df399658-84ac-4ca6-aaf4-378eef361cbb.md +Warning,e09599f5-f900-48b3-9680-af1f1de3f65a,Found a an ul list inside a table in html file:e09599f5-f900-48b3-9680-af1f1de3f65a.xml +Warning,e09599f5-f900-48b3-9680-af1f1de3f65a,Missing tables headers in file:e09599f5-f900-48b3-9680-af1f1de3f65a.md +Warning,e0ad657d-f5d1-4cae-bb0d-d2b619eed261,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:e0ad657d-f5d1-4cae-bb0d-d2b619eed261.md total found:0 +Warning,e0ad657d-f5d1-4cae-bb0d-d2b619eed261,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationName> in md file:e0ad657d-f5d1-4cae-bb0d-d2b619eed261.md total found:0 +Warning,e0ad657d-f5d1-4cae-bb0d-d2b619eed261,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:e0ad657d-f5d1-4cae-bb0d-d2b619eed261.md total found:0 +Warning,e0ad657d-f5d1-4cae-bb0d-d2b619eed261,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<WebApplicationName> in md file:e0ad657d-f5d1-4cae-bb0d-d2b619eed261.md total found:0 +Warning,e1c3fe21-9110-4861-9fc9-715745c9197a,Found a an ul list inside a table in html file:e1c3fe21-9110-4861-9fc9-715745c9197a.xml +Warning,e1c3fe21-9110-4861-9fc9-715745c9197a,Missing tables headers in file:e1c3fe21-9110-4861-9fc9-715745c9197a.md +Warning,e283aaec-e962-46b4-92e4-b8a825521641,Found a an ul list inside a table in html file:e283aaec-e962-46b4-92e4-b8a825521641.xml +Warning,e283aaec-e962-46b4-92e4-b8a825521641,Missing tables headers in file:e283aaec-e962-46b4-92e4-b8a825521641.md +Warning,e4aafc9c-f7d6-4ffd-b4e3-f74d1cf502ee,Found a an ul list inside a table in html file:e4aafc9c-f7d6-4ffd-b4e3-f74d1cf502ee.xml +Warning,e4aafc9c-f7d6-4ffd-b4e3-f74d1cf502ee,Could not Add new line after images in md file:e4aafc9c-f7d6-4ffd-b4e3-f74d1cf502ee.md +Warning,e81557fb-5046-4a67-8ec8-fdfda648af68,Found nested table in md file:e81557fb-5046-4a67-8ec8-fdfda648af68.md +Warning,e8baee59-a84d-4f56-bdeb-45de7d522b68,Found a an ul list inside a table in html file:e8baee59-a84d-4f56-bdeb-45de7d522b68.xml +Warning,e8baee59-a84d-4f56-bdeb-45de7d522b68,Missing tables headers in file:e8baee59-a84d-4f56-bdeb-45de7d522b68.md +Warning,e8baee59-a84d-4f56-bdeb-45de7d522b68,Could not Add new line after images in md file:e8baee59-a84d-4f56-bdeb-45de7d522b68.md +Warning,e8c0fccd-8364-4352-8778-c9c46a668b70,Could not Add new line after images in md file:e8c0fccd-8364-4352-8778-c9c46a668b70.md +Warning,e8eb4d14-cb99-4f43-b845-0cc0963fab47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

This event appears in the event log: Event ID: 8049 Description: Application proxy invalid endpoint for <descriptive text>.

in md file:e8eb4d14-cb99-4f43-b845-0cc0963fab47.md total found:0 +Warning,e8f2c08c-8e9f-40b4-b066-747d65dcb0e4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<PublishingFarmTopologyURL> in md file:e8f2c08c-8e9f-40b4-b066-747d65dcb0e4.md total found:0 +Warning,e8f2c08c-8e9f-40b4-b066-747d65dcb0e4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<PublishingFarmTopologyURL> in md file:e8f2c08c-8e9f-40b4-b066-747d65dcb0e4.md total found:0 +Warning,e8f2c08c-8e9f-40b4-b066-747d65dcb0e4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line: <ServiceApplicationProxyName> in md file:e8f2c08c-8e9f-40b4-b066-747d65dcb0e4.md total found:0 +Warning,e8f2c08c-8e9f-40b4-b066-747d65dcb0e4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<PublishingFarmTopologyURL> in md file:e8f2c08c-8e9f-40b4-b066-747d65dcb0e4.md total found:0 +Warning,e8f2c08c-8e9f-40b4-b066-747d65dcb0e4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationProxyName> in md file:e8f2c08c-8e9f-40b4-b066-747d65dcb0e4.md total found:0 +Warning,e8f2c08c-8e9f-40b4-b066-747d65dcb0e4,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<PublishingFarmTopologyURL> in md file:e8f2c08c-8e9f-40b4-b066-747d65dcb0e4.md total found:0 +Warning,eabe099e-5eea-4b33-8241-8079d9409095,Found a an ul list inside a table in html file:eabe099e-5eea-4b33-8241-8079d9409095.xml +Warning,ee879d48-44a3-46e7-a631-736c4430ec94,Found a an ul list inside a table in html file:ee879d48-44a3-46e7-a631-736c4430ec94.xml +Warning,ef9a10b9-2283-431e-9dc2-f98a78a33b39,Could not Add new line after images in md file:ef9a10b9-2283-431e-9dc2-f98a78a33b39.md +Warning,f1dfdac2-81ad-452f-b5b6-df9e5a8e976e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

To find the My Sites URL in Office 365- on the Admin menu- click SharePoint . In the Site Collections list- look for the site collection that contains <domain>-my.sharepoint.com.

in md file:f1dfdac2-81ad-452f-b5b6-df9e5a8e976e.md total found:0 +Warning,f1dfdac2-81ad-452f-b5b6-df9e5a8e976e,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<yourtenant name> in md file:f1dfdac2-81ad-452f-b5b6-df9e5a8e976e.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Credential> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ID> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Credential> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ID> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseName> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Credential> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ID> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseNname> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServerName> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<Credential> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ID> in md file:f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b.md total found:0 +Warning,f37b3b61-2b26-4635-a04a-a8a744e8c3ef,Video is found in md file:f37b3b61-2b26-4635-a04a-a8a744e8c3ef.md total found:1 +Warning,f3819495-4b67-4a71-ba46-23e43b175620,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:YYYYMMDD-HHMMSS-SSS-<GUID> in md file:f3819495-4b67-4a71-ba46-23e43b175620.md total found:0 +Warning,f3819495-4b67-4a71-ba46-23e43b175620,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:YYYYMMDD-HHMMSS-SSS-<GUID> in md file:f3819495-4b67-4a71-ba46-23e43b175620.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ServiceApplicationName> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<BackupFolder> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<GUID> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Farm\Shared Services Applications\<Service application> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f50ca1b2-5075-49f6-9689-46c7b8a29b47,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SearchServiceApplicationName> in md file:f50ca1b2-5075-49f6-9689-46c7b8a29b47.md total found:0 +Warning,f6663d4b-30e5-48d6-9bbc-aed8db1aae24,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

The About me page includes a title that is typically "About <user’s name >" and it displays the user’s profile data- such as the user's picture- title- group and telephone number.

in md file:f6663d4b-30e5-48d6-9bbc-aed8db1aae24.md total found:0 +Warning,f6c7b56e-f684-45d9-8752-67fff01c1728,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<catalog name> in md file:f6c7b56e-f684-45d9-8752-67fff01c1728.md total found:0 +Warning,f6c7b56e-f684-45d9-8752-67fff01c1728,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<catalog name> in md file:f6c7b56e-f684-45d9-8752-67fff01c1728.md total found:0 +Warning,f7b617fc-cc45-41bf-bb71-f3d49ed4a59c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line: + In SharePoint Foundation 2013- Self-Service Site Creation is disabled by default. When you enable Self-Service Site Creation- users can use the site creation page (http://<server>/_layouts/15/scsignup.aspx) to create a new site or site collection. + in md file:f7b617fc-cc45-41bf-bb71-f3d49ed4a59c.md total found:0 +Warning,f8efdfaf-8ef6-445c-9fb9-8845667e478b,Found a an ul list inside a table in html file:f8efdfaf-8ef6-445c-9fb9-8845667e478b.xml +Warning,f8efdfaf-8ef6-445c-9fb9-8845667e478b,Missing tables headers in file:f8efdfaf-8ef6-445c-9fb9-8845667e478b.md +Warning,f8efdfaf-8ef6-445c-9fb9-8845667e478b,Could not Add new line after images in md file:f8efdfaf-8ef6-445c-9fb9-8845667e478b.md +Warning,f8f81869-a51f-4d7f-b4b6-52dd99078c23,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<SiteCollectionURL> in md file:f8f81869-a51f-4d7f-b4b6-52dd99078c23.md total found:0 +Warning,f8f81869-a51f-4d7f-b4b6-52dd99078c23,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<DatabaseServerName> in md file:f8f81869-a51f-4d7f-b4b6-52dd99078c23.md total found:0 +Warning,f8f81869-a51f-4d7f-b4b6-52dd99078c23,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<ContentDatabaseName> in md file:f8f81869-a51f-4d7f-b4b6-52dd99078c23.md total found:0 +Warning,f957e1ce-0a39-490c-b533-4ddab4f5bb7a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Set your Azure subscription. Replace everything within the quotes- including the < and > characters- with the correct name.

in md file:f957e1ce-0a39-490c-b533-4ddab4f5bb7a.md total found:0 +Warning,fcfdb2ad-9d0e-43ca-8bfa-45064eeca5af,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:Database role membership for: <database> in md file:fcfdb2ad-9d0e-43ca-8bfa-45064eeca5af.md total found:0 +Warning,feedf4f0-0e18-4592-983b-8d769830bcac,Could not Add new line after images in md file:feedf4f0-0e18-4592-983b-8d769830bcac.md +Warning,ff364add-e18d-4d1c-824f-f0ea549fe904,Could not Add new line after images in md file:ff364add-e18d-4d1c-824f-f0ea549fe904.md +Warning,ff6c5b8c-59bd-4079-8f0b-de4f8b4e0a86,Found a an ul list inside a table in html file:ff6c5b8c-59bd-4079-8f0b-de4f8b4e0a86.xml +Warning,ff6c5b8c-59bd-4079-8f0b-de4f8b4e0a86,Missing tables headers in file:ff6c5b8c-59bd-4079-8f0b-de4f8b4e0a86.md +Warning,ffec2e36-9142-45ae-866e-308d6efbc114,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<protocol>://hostname/* in md file:ffec2e36-9142-45ae-866e-308d6efbc114.md total found:0 +Warning,ffec2e36-9142-45ae-866e-308d6efbc114,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<protocol> in md file:ffec2e36-9142-45ae-866e-308d6efbc114.md total found:0 +Warning,ffec2e36-9142-45ae-866e-308d6efbc114,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<protocol> in md file:ffec2e36-9142-45ae-866e-308d6efbc114.md total found:0 +Warning,ffec2e36-9142-45ae-866e-308d6efbc114,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<protocol> in md file:ffec2e36-9142-45ae-866e-308d6efbc114.md total found:0 +Warning,ffec2e36-9142-45ae-866e-308d6efbc114,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<protocol> in md file:ffec2e36-9142-45ae-866e-308d6efbc114.md total found:0 +Warning,ffec2e36-9142-45ae-866e-308d6efbc114,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<protocol> in md file:ffec2e36-9142-45ae-866e-308d6efbc114.md total found:0 + + +Warning,ee3bd227-1ba9-4eff-9d60-02cd32f64171,Topic title:databases-running-in-compatibility-range-upgrade-recommended-sharepoint-server-2016 bigger then max length:80 new topic titile name:databases-running-in-compatibility-range-upgrade-recommended-sharepoint-server-2 +Warning,5f0402ca-90c6-4528-b1de-04d4f28fb2a6,Topic title:manage-a-connection-to-a-document-center-or-a-records-center-in-sharepoint-server bigger then max length:80 new topic titile name:manage-a-connection-to-a-document-center-or-a-records-center-in-sharepoint-serve +Warning,5020140d-24c4-4817-8bb4-05e1c225d1f2,Topic title:deployment-considerations-for-implementing-microsoft-identity-manager-with-sharepoint-server-2016 bigger then max length:80 new topic titile name:deployment-considerations-for-implementing-microsoft-identity-manager-with-share +Warning,ec3a8cb2-141f-4c4b-a3c3-068ea89121cf,Topic title:the-unattended-service-account-application-id-is-not-specified-or-has-an-invalid-value-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-unattended-service-account-application-id-is-not-specified-or-has-an-invalid +Warning,d21f7d68-c18b-4253-af8b-0765c86a331b,Topic title:configure-visio-services-data-refresh-in-sharepoint-server-2016-by-using-the-unattended-service-account bigger then max length:80 new topic titile name:configure-visio-services-data-refresh-in-sharepoint-server-2016-by-using-the-una +Warning,987f22e3-53cc-4e6a-93e7-0851af4f31db,Topic title:immediate-translations-for-the-machine-translation-service-are-disabled-sharepoint-server-2016 bigger then max length:80 new topic titile name:immediate-translations-for-the-machine-translation-service-are-disabled-sharepoi +Warning,f3625c2f-a588-422c-9fbe-0b83205fbc88,Topic title:web-config-file-has-incorrect-settings-for-the-requestfiltering-element-sharepoint-server-2016 bigger then max length:80 new topic titile name:web-config-file-has-incorrect-settings-for-the-requestfiltering-element-sharepoi +Warning,9136a204-9877-4591-a7e5-0cdeda60114e,Topic title:delegate-administration-of-user-profile-service-applications-or-features-in-sharepoint-server bigger then max length:80 new topic titile name:delegate-administration-of-user-profile-service-applications-or-features-in-shar +Warning,3fdbc40b-8562-4bec-be89-113a64e19911,Topic title:configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-refresh-account-sharepoint-server-2013 bigger then max length:80 new topic titile name:configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re +Warning,85aa1c35-1322-42ad-a625-1496aee67858,Topic title:databases-within-this-farm-are-set-to-read-only-and-will-fail-to-upgrade-unless-it-is-set-to-a-read-write-state-sharepoint-server-2016 bigger then max length:80 new topic titile name:databases-within-this-farm-are-set-to-read-only-and-will-fail-to-upgrade-unless- +Warning,45d9570f-59d7-4f6b-b8e1-18868b27b0bc,Topic title:the-settings-for-word-automation-services-are-not-within-the-recommended-limits-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-settings-for-word-automation-services-are-not-within-the-recommended-limits- +Warning,d7b9c8dd-274a-46ec-a8f6-28b7f5f0fa9e,Topic title:verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-application-proxy-sharepoint-server-2016 bigger then max length:80 new topic titile name:verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-ap +Warning,5e242415-c288-48c7-a373-29acc359ad95,Topic title:the-visio-graphics-service-has-a-maximum-cache-size-setting-that-may-adversely-impact-performancesharepoint-server-2016 bigger then max length:80 new topic titile name:the-visio-graphics-service-has-a-maximum-cache-size-setting-that-may-adversely-i +Warning,f753e138-04c2-4358-a12e-2a406a431ac9,Topic title:supported-and-unsupported-documentum-object-types-and-properties-in-sharepoint-server bigger then max length:80 new topic titile name:supported-and-unsupported-documentum-object-types-and-properties-in-sharepoint-s +Warning,bfe89420-2a60-4ce7-8b11-2b45fd38f822,Topic title:verify-that-the-critical-user-profile-application-and-user-profile-proxy-application-timer-jobs-are-available-and-have-not-been-mistakenly-deleted-sharepoint-server-2016 bigger then max length:80 new topic titile name:verify-that-the-critical-user-profile-application-and-user-profile-proxy-applica +Warning,7a690328-78c5-4dc2-b03f-30165ad186c1,Topic title:result-types-and-display-templates-that-are-used-to-display-search-results-in-sharepoint-server bigger then max length:80 new topic titile name:result-types-and-display-templates-that-are-used-to-display-search-results-in-sh +Warning,6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2,Topic title:add-or-remove-service-application-connections-from-a-web-application-in-sharepoint-server bigger then max length:80 new topic titile name:add-or-remove-service-application-connections-from-a-web-application-in-sharepoi +Warning,dee7c975-5738-494f-bf70-31b0e0bc8206,Topic title:overview-of-microsoft-identity-manager-synchronization-service-in-sharepoint-server-2016 bigger then max length:80 new topic titile name:overview-of-microsoft-identity-manager-synchronization-service-in-sharepoint-ser +Warning,3fdf9bcc-11c0-48af-b8c3-327902f53d73,Topic title:search-in-sharepoint-server-2016-knowledge-articles-for-systems-center-operations-manager bigger then max length:80 new topic titile name:search-in-sharepoint-server-2016-knowledge-articles-for-systems-center-operation +Warning,e56b99dc-3731-4cdd-8576-3777c3827e49,Topic title:the-number-of-distributed-cache-hosts-in-the-farm-exceeds-the-recommended-value-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-number-of-distributed-cache-hosts-in-the-farm-exceeds-the-recommended-value- +Warning,cab37e59-7ae1-403a-8fa2-37fe0701961e,Topic title:one-or-more-web-applications-are-configured-to-use-windows-classic-authentication-sharepoint-server-2016 bigger then max length:80 new topic titile name:one-or-more-web-applications-are-configured-to-use-windows-classic-authenticatio +Warning,067783ba-e22f-41a8-9a1b-38a89c3a30c2,Topic title:configure-visio-services-data-refresh-in-sharepoint-server-by-using-external-data-connections bigger then max length:80 new topic titile name:configure-visio-services-data-refresh-in-sharepoint-server-by-using-external-dat +Warning,57592cbe-47c1-44c7-8f57-38fa192df4f7,Topic title:the-server-farm-account-should-not-be-used-for-other-services-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-server-farm-account-should-not-be-used-for-other-services-sharepoint-server- +Warning,e4b1234e-2b69-4c44-9621-398d20122cab,Topic title:business-data-connectivity-connectors-are-currently-enabled-in-a-partitioned-environment-sharepoint-server-2016 bigger then max length:80 new topic titile name:business-data-connectivity-connectors-are-currently-enabled-in-a-partitioned-env +Warning,f7fcf9d3-c895-4f91-b9c2-4036519a2fd5,Topic title:secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sharepoint-server-2016 bigger then max length:80 new topic titile name:secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sh +Warning,0853bed9-1084-413b-bf91-427dc643a5e5,Topic title:configure-excel-services-data-refresh-by-using-external-data-connections-in-sharepoint-server-2013 bigger then max length:80 new topic titile name:configure-excel-services-data-refresh-by-using-external-data-connections-in-shar +Warning,fb651b8b-5657-4686-b084-443016aba76c,Topic title:the-paging-file-size-should-exceed-the-amount-of-physical-ram-in-the-system-sharepoint-server bigger then max length:80 new topic titile name:the-paging-file-size-should-exceed-the-amount-of-physical-ram-in-the-system-shar +Warning,fcfdb2ad-9d0e-43ca-8bfa-45064eeca5af,Topic title:configure-excel-services-data-refresh-by-using-the-unattended-service-account-in-sharepoint-server-2016 bigger then max length:80 new topic titile name:configure-excel-services-data-refresh-by-using-the-unattended-service-account-in +Warning,e00cc8ed-8a01-4928-9175-49efe03288a1,Topic title:critical-state-of-this-rule-indicates-that-the-word-automation-services-is-not-running-when-it-should-be-running-sharepoint-server-2016 bigger then max length:80 new topic titile name:critical-state-of-this-rule-indicates-that-the-word-automation-services-is-not-r +Warning,9b5a1f99-0193-4a97-b0d1-4a5633b32c43,Topic title:redesign-enterprise-search-topology-for-more-content-and-users-in-sharepoint-2016 bigger then max length:80 new topic titile name:redesign-enterprise-search-topology-for-more-content-and-users-in-sharepoint-201 +Warning,335af336-da96-4b50-9901-4c4ef151c790,Topic title:verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-application-sharepoint-server-2016 bigger then max length:80 new topic titile name:verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-ap +Warning,f140e0ad-07e4-42f8-a198-54d800355698,Topic title:the-machine-translation-service-is-not-running-when-it-should-be-running-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-machine-translation-service-is-not-running-when-it-should-be-running-sharepo +Warning,4fcd074b-32b1-49b3-9910-5bb174894603,Topic title:the-visio-graphics-service-has-a-minimum-cache-age-setting-that-may-cause-a-security-issuesharepoint-server-2016 bigger then max length:80 new topic titile name:the-visio-graphics-service-has-a-minimum-cache-age-setting-that-may-cause-a-secu +Warning,80521ae8-be93-4d1c-9956-5f4bed1ac4a7,Topic title:dedicated-crawl-target-configuration-has-one-or-more-invalid-servers-sharepoint-server-2016 bigger then max length:80 new topic titile name:dedicated-crawl-target-configuration-has-one-or-more-invalid-servers-sharepoint- +Warning,3661eafe-91da-4467-91f1-5fa47947e178,Topic title:the-visio-graphics-service-has-a-maximum-web-drawing-size-setting-that-will-adversely-impact-performance-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-visio-graphics-service-has-a-maximum-web-drawing-size-setting-that-will-adve +Warning,62d0b8d3-e8ea-4523-a69f-62623fb340fb,Topic title:sharepoint-intranet-farm-in-azure-phase-5-create-the-availability-group-and-add-the-sharepoint-databases bigger then max length:80 new topic titile name:sharepoint-intranet-farm-in-azure-phase-5-create-the-availability-group-and-add- +Warning,28b06934-933b-4899-a7a6-707eb0516552,Topic title:the-visio-graphics-service-has-a-maximum-cache-age-setting-that-will-adversely-impact-performance-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-visio-graphics-service-has-a-maximum-cache-age-setting-that-will-adversely-i +Warning,e1c3fe21-9110-4861-9fc9-715745c9197a,Topic title:redesign-enterprise-search-topology-for-specific-performance-requirements-in-sharepoint-2016 bigger then max length:80 new topic titile name:redesign-enterprise-search-topology-for-specific-performance-requirements-in-sha +Warning,7ebd1422-4f3d-44b9-8df6-75274c65b7e5,Topic title:infopath-form-library-forms-cannot-be-filled-out-in-a-web-browser-sharepoint-server-2016 bigger then max length:80 new topic titile name:infopath-form-library-forms-cannot-be-filled-out-in-a-web-browser-sharepoint-ser +Warning,b5f098eb-219a-4483-adee-75d7b6b3089a,Topic title:validate-the-my-site-host-and-individual-my-sites-are-on-a-dedicated-web-application-and-separate-url-domain-sharepoint-server-2016 bigger then max length:80 new topic titile name:validate-the-my-site-host-and-individual-my-sites-are-on-a-dedicated-web-applica +Warning,73ceb46e-d3aa-45bd-ac3e-77f58a9ab34d,Topic title:configure-profile-synchronization-by-using-sharepoint-active-directory-import-in-sharepoint-server-2016 bigger then max length:80 new topic titile name:configure-profile-synchronization-by-using-sharepoint-active-directory-import-in +Warning,c8209ecc-59e4-4568-a7e6-782a6b0ab02f,Topic title:configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoint-server-2013 bigger then max length:80 new topic titile name:configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoin +Warning,2be5291e-b6cc-4730-bc58-78b14ea1984b,Topic title:configure-excel-services-data-refresh-by-using-embedded-data-connections-in-sharepoint-server-2013 bigger then max length:80 new topic titile name:configure-excel-services-data-refresh-by-using-embedded-data-connections-in-shar +Warning,24292545-0844-4eb0-9e80-7d4c9985755d,Topic title:drives-used-for-sql-databases-are-running-out-of-free-space-sharepoint-server-2016 bigger then max length:80 new topic titile name:drives-used-for-sql-databases-are-running-out-of-free-space-sharepoint-server-20 +Warning,af7cf3e7-94b1-4a5d-8cb9-80c5a0b397f2,Topic title:deploying-sharepoint-server-2016-with-sql-server-alwayson-availability-groups-in-azure bigger then max length:80 new topic titile name:deploying-sharepoint-server-2016-with-sql-server-alwayson-availability-groups-in +Warning,7021185c-1f2b-44a6-ba4a-8355dd8409e1,Topic title:share-a-sql-server-analysis-services-data-connection-using-excel-services-sharepoint-server-2013 bigger then max length:80 new topic titile name:share-a-sql-server-analysis-services-data-connection-using-excel-services-sharep +Warning,25970085-39e6-4b1f-83c7-8687a5f8e939,Topic title:databases-used-by-sharepoint-have-outdated-index-statistics-sharepoint-server-2016 bigger then max length:80 new topic titile name:databases-used-by-sharepoint-have-outdated-index-statistics-sharepoint-server-20 +Warning,a3ad4dea-36b2-48df-b699-8fd9725df53c,Topic title:overview-of-publishing-to-internet-intranet-and-extranet-sites-in-sharepoint-server bigger then max length:80 new topic titile name:overview-of-publishing-to-internet-intranet-and-extranet-sites-in-sharepoint-ser +Warning,78df8a76-0dbc-403b-b54d-9572fc918531,Topic title:test-lab-guide-demonstrate-forms-based-claims-authentication-for-sharepoint-server-2013 bigger then max length:80 new topic titile name:test-lab-guide-demonstrate-forms-based-claims-authentication-for-sharepoint-serv +Warning,c145579b-fc8b-4ab4-bc80-95c3202deae2,Topic title:xliff-translations-for-the-machine-translation-service-is-disabled-sharepoint-server-2016 bigger then max length:80 new topic titile name:xliff-translations-for-the-machine-translation-service-is-disabled-sharepoint-se +Warning,6cd7e6d2-092d-47f0-aed0-97bf2c09369a,Topic title:test-lab-guide-demonstrate-saml-based-claims-authentication-with-sharepoint-server-2013 bigger then max length:80 new topic titile name:test-lab-guide-demonstrate-saml-based-claims-authentication-with-sharepoint-serv +Warning,150f0179-b9d4-4823-b314-98b83a95d85e,Topic title:secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sharepoint-2013 bigger then max length:80 new topic titile name:secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sh +Warning,0d326419-25c2-4591-acc6-9e487aa80c6e,Topic title:the-infopath-forms-services-maintenance-timer-job-is-not-enabled-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-infopath-forms-services-maintenance-timer-job-is-not-enabled-sharepoint-serv +Warning,b607e000-9436-4cbb-b6aa-9e76d70a4314,Topic title:plan-document-versioning-content-approval-and-check-out-controls-in-sharepoint-2013 bigger then max length:80 new topic titile name:plan-document-versioning-content-approval-and-check-out-controls-in-sharepoint-2 +Warning,20e1e0c3-7d5c-489c-a588-a11b30adffb9,Topic title:the-visio-graphics-service-has-a-maximum-recalc-duration-setting-that-will-adversely-impact-user-perceived-performancesharepoint-server-2016 bigger then max length:80 new topic titile name:the-visio-graphics-service-has-a-maximum-recalc-duration-setting-that-will-adver +Warning,8de5bc7f-026c-4685-a6f6-a8fd814c2b70,Topic title:infopath-forms-services-forms-cannot-be-filled-out-in-a-web-browser-because-no-state-service-connection-is-configured-sharepoint-server-2016 bigger then max length:80 new topic titile name:infopath-forms-services-forms-cannot-be-filled-out-in-a-web-browser-because-no-s +Warning,53598509-9821-4c0b-9ab4-a9e594ac8fec,Topic title:configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sharepoint-server-2013 bigger then max length:80 new topic titile name:configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh +Warning,5ed9fe7c-48c5-4511-aab4-aa58a440954d,Topic title:built-in-accounts-are-used-as-application-pool-or-service-identities-sharepoint-server-2016 bigger then max length:80 new topic titile name:built-in-accounts-are-used-as-application-pool-or-service-identities-sharepoint- +Warning,086fd0f5-8580-414f-a088-b1238ad02014,Topic title:verify-each-user-profile-service-application-has-an-associated-search-service-connection-sharepoint-server-2016 bigger then max length:80 new topic titile name:verify-each-user-profile-service-application-has-an-associated-search-service-co +Warning,9d2d8945-5a6f-45dc-91bd-b588720ba745,Topic title:web-applications-using-claims-authentication-require-an-update-sharepoint-server-2016 bigger then max length:80 new topic titile name:web-applications-using-claims-authentication-require-an-update-sharepoint-server +Warning,c78266d8-33de-4edc-94ea-b8110ac8db81,Topic title:one-or-more-categories-are-configured-with-verbose-trace-logging-sharepoint-server-2016 bigger then max length:80 new topic titile name:one-or-more-categories-are-configured-with-verbose-trace-logging-sharepoint-serv +Warning,c2f1d2a8-dc6a-471c-b373-be420b460306,Topic title:web-config-files-are-not-identical-on-all-machines-in-the-farm-sharepoint-server-2016 bigger then max length:80 new topic titile name:web-config-files-are-not-identical-on-all-machines-in-the-farm-sharepoint-server +Warning,63f233ef-8a72-449e-8211-c66fea977b6e,Topic title:verify-each-user-profile-service-application-has-an-associated-managed-metadata-service-connectionsharepoint-server-2016 bigger then max length:80 new topic titile name:verify-each-user-profile-service-application-has-an-associated-managed-metadata- +Warning,0ffd36db-3f34-4f9f-b3fe-c8bea09a9d8f,Topic title:searchone-or-more-crawl-databases-may-have-fragmented-indices-sharepoint-server-2016 bigger then max length:80 new topic titile name:searchone-or-more-crawl-databases-may-have-fragmented-indices-sharepoint-server- +Warning,8386d324-816a-42ee-aff2-ce135ca2f241,Topic title:all-state-service-databases-are-paused-for-a-state-service-application-sharepoint-server-2016 bigger then max length:80 new topic titile name:all-state-service-databases-are-paused-for-a-state-service-application-sharepoin +Warning,9983054b-ed90-491a-ac1d-cf95204f0931,Topic title:expired-sessions-are-not-being-deleted-from-the-asp-net-session-state-database-sharepoint-server-2016 bigger then max length:80 new topic titile name:expired-sessions-are-not-being-deleted-from-the-asp-net-session-state-database-s +Warning,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,Topic title:supported-high-availability-and-disaster-recovery-options-for-sharepoint-databases bigger then max length:80 new topic titile name:supported-high-availability-and-disaster-recovery-options-for-sharepoint-databas +Warning,70d6f3af-2ad4-497d-a449-d75bacfd8aea,Topic title:the-application-discovery-and-load-balancer-service-is-not-running-in-this-farm-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-application-discovery-and-load-balancer-service-is-not-running-in-this-farm- +Warning,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,Topic title:configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-online bigger then max length:80 new topic titile name:configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o +Warning,04d1607a-21a9-4b77-929a-d9d7ffad51f8,Topic title:convert-forefront-identity-manager-fim-xml-files-to-microsoft-identity-management-mim-service-config-files-for-user-profile-sync bigger then max length:80 new topic titile name:convert-forefront-identity-manager-fim-xml-files-to-microsoft-identity-managemen +Warning,17d06bdf-69e1-4a85-86f9-da78a3c79952,Topic title:the-state-service-delete-expired-sessions-timer-job-is-not-enabled-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-state-service-delete-expired-sessions-timer-job-is-not-enabled-sharepoint-se +Warning,2689bb6a-fd05-4273-87eb-daac5b2722f3,Topic title:verify-each-user-profile-service-application-has-a-my-site-host-configured-sharepoint-server-2016 bigger then max length:80 new topic titile name:verify-each-user-profile-service-application-has-a-my-site-host-configured-share +Warning,982d3ab2-d1a6-4625-b4c6-e12a1f4532d5,Topic title:people-search-relevance-is-not-optimized-when-the-active-directory-has-errors-in-the-manager-reporting-structure-sharepoint-server-2016 bigger then max length:80 new topic titile name:people-search-relevance-is-not-optimized-when-the-active-directory-has-errors-in +Warning,45b39899-1686-43e5-9073-e51d2979ba9b,Topic title:this-distributed-cache-host-may-cause-cache-reliability-problems-sharepoint-server-2016 bigger then max length:80 new topic titile name:this-distributed-cache-host-may-cause-cache-reliability-problems-sharepoint-serv +Warning,6e743c5b-b70c-4e86-ae31-e5ffcc0c099a,Topic title:distributed-cache-service-is-not-enabled-in-this-deployment-sharepoint-server-2016 bigger then max length:80 new topic titile name:distributed-cache-service-is-not-enabled-in-this-deployment-sharepoint-server-20 +Warning,4692ebba-90eb-4d72-ac12-e90c4d4ee7ae,Topic title:deploy-a-business-connectivity-services-on-premises-solution-in-sharepoint-server bigger then max length:80 new topic titile name:deploy-a-business-connectivity-services-on-premises-solution-in-sharepoint-serve +Warning,eb5d2d46-8bf6-43d7-add0-e9d61290a4d0,Topic title:the-settings-for-the-machine-translation-service-are-not-within-the-recommended-limits-sharepoint-server-2016 bigger then max length:80 new topic titile name:the-settings-for-the-machine-translation-service-are-not-within-the-recommended- +Warning,445bce79-f6d6-4ab6-9d50-f0672cd093f4,Topic title:configure-hybrid-federated-search-from-sharepoint-server-to-sharepoint-onlineroadmap bigger then max length:80 new topic titile name:configure-hybrid-federated-search-from-sharepoint-server-to-sharepoint-onlineroa +Warning,5f0f9910-d851-4ffa-832b-f47558e4758c,Topic title:accounts-used-by-application-pools-or-service-identities-are-in-the-local-machine-administrators-group-sharepoint-server-2016 bigger then max length:80 new topic titile name:accounts-used-by-application-pools-or-service-identities-are-in-the-local-machin +Warning,f6d49e94-ad29-456d-8cd9-f940154d5a0e,Topic title:configure-hybrid-federated-search-from-sharepoint-online-to-sharepoint-serverroadmap bigger then max length:80 new topic titile name:configure-hybrid-federated-search-from-sharepoint-online-to-sharepoint-serverroa +Warning,5e7be5ff-5216-406b-9bfe-f9ff1f9651aa,Topic title:more-cache-hosts-are-running-in-this-deployment-than-are-registered-with-sharepoint-sharepoint-server-2016 bigger then max length:80 new topic titile name:more-cache-hosts-are-running-in-this-deployment-than-are-registered-with-sharepo +Warning,062b6ff7-a4ee-408f-811e-fdba45ca3c08,Topic title:the-visio-graphics-service-has-a-minimum-cache-age-setting-that-will-adversely-impact-performancesharepoint-server-2016 bigger then max length:80 new topic titile name:the-visio-graphics-service-has-a-minimum-cache-age-setting-that-will-adversely-i +Warning,76a4e2e3-7e10-41da-b3a8-fe62e193dc24,Topic title:one-or-more-app-domains-for-web-applications-aren-t-configured-correctly-sharepoint-server-2016 bigger then max length:80 new topic titile name:one-or-more-app-domains-for-web-applications-aren-t-configured-correctly-sharepo +Warning,N/A,Sql Query:use [DDCMS_MOD_IW] SELECT tkw.[topicGuid] as topicGuid,kwf.[keyword] as f1Keyword + FROM [TopicKeywordsF] tkw join [dbo].[KeywordsF] kwf on tkw.[kwdGuid] = kwf.[kwdGuid] + join [dbo].[Topics] topics on topics.[topicGuid] = tkw.[topicGuid] + join [dbo].[Projects] pro on pro.[projectGuid] = topics.[homeProjectGuid] + where pro.[projectName] = 'SharePoint16ITPro' retuned no rows for project:SharePoint16ITPro server:ocpubcms for database:DDCMS_MOD_IW +Warning,N/A,Sql Query:use [DDCMS_MOD_IW] SELECT tkw.[topicGuid] as topicGuid,kwf.[keyword] as f1Keyword + FROM [TopicKeywordsF] tkw join [dbo].[KeywordsF] kwf on tkw.[kwdGuid] = kwf.[kwdGuid] + join [dbo].[Topics] topics on topics.[topicGuid] = tkw.[topicGuid] + join [dbo].[Projects] pro on pro.[projectGuid] = topics.[homeProjectGuid] + where pro.[projectName] = 'SharePoint16ITPro' retuned no rows for project:SharePoint16ITPro server:ocpubcms for database:DDCMS_MOD_IW diff --git a/SharePoint/SharePoint16ITPro_Friendly_Name_Mapping.csv b/SharePoint/SharePoint16ITPro_Friendly_Name_Mapping.csv new file mode 100644 index 0000000000..5419f81f78 --- /dev/null +++ b/SharePoint/SharePoint16ITPro_Friendly_Name_Mapping.csv @@ -0,0 +1,636 @@ +VBA Project,GUID,Friendly name +SharePoint16ITPro,d359cdaa-0ebd-4c59-8fc5-002cba241b18,overview-of-rbs-in-sharepoint-server +SharePoint16ITPro,f687788b-f9b6-4a63-94d2-008939108c65,add-edit-or-delete-a-content-source-in-sharepoint-server +SharePoint16ITPro,b17a56ea-2e7f-43c6-9a17-00ae1f5c4089,configure-and-use-the-documentum-connector-in-sharepoint-server +SharePoint16ITPro,44c05570-37c1-49dd-8015-015f8908199c,delete-and-restore-site-collections-in-sharepoint-server +SharePoint16ITPro,156f69fe-1831-472f-8e42-01c138d408ed,some-content-databases-are-growing-too-large-sharepoint-server-2016 +SharePoint16ITPro,cf19810b-5548-447c-a94d-026ad6e9d096,customize-search-result-types-in-sharepoint-server +SharePoint16ITPro,502fcb0a-c20a-433d-aac1-02ba20d81a7e,manage-query-suggestions-in-sharepoint-server +SharePoint16ITPro,ee3bd227-1ba9-4eff-9d60-02cd32f64171,databases-running-in-compatibility-range-upgrade-recommended-sharepoint-server-2 +SharePoint16ITPro,84972766-6527-4791-ae68-02d3a50b67f0,install-microsoft-identity-manager-for-user-profiles-in-sharepoint-server-2016 +SharePoint16ITPro,73cfd7b3-be90-480a-b415-039fa97d9b89,enable-search-alerts-in-sharepoint-server +SharePoint16ITPro,f8249a19-005f-4ae0-b7c0-04a683691fbf,the-net-pipe-listener-adapter-isn-t-available-sharepoint-server-2016 +SharePoint16ITPro,5f0402ca-90c6-4528-b1de-04d4f28fb2a6,manage-a-connection-to-a-document-center-or-a-records-center-in-sharepoint-serve +SharePoint16ITPro,9e952b26-fb0e-48a5-89b1-054f54f9b986,overview-of-visio-services-in-sharepoint-server +SharePoint16ITPro,5020140d-24c4-4817-8bb4-05e1c225d1f2,deployment-considerations-for-implementing-microsoft-identity-manager-with-share +SharePoint16ITPro,7eea752e-5bdc-48b1-99cb-05e6c3669c4a,enable-trusted-locations-for-performancepoint-services +SharePoint16ITPro,5c23f9ea-d019-4750-abdf-0633bffa84f4,test-lab-guide-configure-sharepoint-server-2013-in-a-three-tier-farm +SharePoint16ITPro,ec3a8cb2-141f-4c4b-a3c3-068ea89121cf,the-unattended-service-account-application-id-is-not-specified-or-has-an-invalid +SharePoint16ITPro,45acdd33-b322-4f36-97f1-0701159e15f0,back-up-site-collections-in-sharepoint-server +SharePoint16ITPro,d21f7d68-c18b-4253-af8b-0765c86a331b,configure-visio-services-data-refresh-in-sharepoint-server-2016-by-using-the-una +SharePoint16ITPro,2b98f39e-649f-4b00-b025-0775ac996268,integrate-a-yammer-network-into-sharepoint-server-2013-and-office-365 +SharePoint16ITPro,56a95840-704c-4aa0-9d37-078e7ab4f83c,overview-of-onedrive-for-business-in-sharepoint-server +SharePoint16ITPro,2d11e10c-c224-46a6-8c03-07913b38c13e,use-excel-services-with-secure-store-service-in-sharepoint-server-2016 +SharePoint16ITPro,987f22e3-53cc-4e6a-93e7-0851af4f31db,immediate-translations-for-the-machine-translation-service-are-disabled-sharepoi +SharePoint16ITPro,cbb210e8-2969-4fd5-a82d-08ad1996c5b4,plan-trusted-data-connection-libraries-in-sharepoint-server-2013 +SharePoint16ITPro,955084c9-91e1-4f66-9ec4-09d2816c5c6f,plan-excel-services-global-settings-in-sharepoint-server-2013 +SharePoint16ITPro,96af09c3-95c5-4472-b452-0aef8116bd79,updated-product-servicing-policy-for-sharepoint-server-2016 +SharePoint16ITPro,f3625c2f-a588-422c-9fbe-0b83205fbc88,web-config-file-has-incorrect-settings-for-the-requestfiltering-element-sharepoi +SharePoint16ITPro,45e8f120-3d0c-4b5f-bf5f-0bc4e3c679d7,plan-a-business-connectivity-services-solution-in-sharepoint-server +SharePoint16ITPro,65552a5e-228b-4789-8982-0c29871c85b0,governance-planning-in-sharepoint-server-2016 +SharePoint16ITPro,a0f2c651-e353-4197-b0dd-0cbe6f18c811,plan-authentication-in-sharepoint-server +SharePoint16ITPro,e8eb4d14-cb99-4f43-b845-0cc0963fab47,visio-services-in-sharepoint-server-2016-knowledge-articles +SharePoint16ITPro,9136a204-9877-4591-a7e5-0cdeda60114e,delegate-administration-of-user-profile-service-applications-or-features-in-shar +SharePoint16ITPro,0e24bb6a-8977-467f-bf69-0cfef1c8e288,distributed-cache-service-is-not-configured-on-server-s +SharePoint16ITPro,626fc816-cd0e-44e1-8ea7-0d0b536b379b,manage-the-search-index-in-sharepoint-server-2016 +SharePoint16ITPro,2b2c3b2a-49f3-4c96-9efd-0d557f0332db,plan-enterprise-search-architecture-in-sharepoint-server-2016 +SharePoint16ITPro,59c0540e-1238-4138-b98d-0d74ca59b9db,back-up-search-service-applications-in-sharepoint-server +SharePoint16ITPro,40117fda-70a0-4e3d-8cd3-0def768da16c,plan-for-user-authentication-methods-in-sharepoint-server +SharePoint16ITPro,7af845bc-f245-459f-871d-0ee06c64a184,plan-content-types-and-workflows-in-sharepoint-2013 +SharePoint16ITPro,0adff5f5-26d3-439f-86fa-0f0f8e0b8fc5,maintain-rbs-in-sharepoint-server +SharePoint16ITPro,40f1d080-3523-444f-a389-0f37a40ae44a,plan-excel-services-data-model-settings-in-sharepoint-server-2013 +SharePoint16ITPro,f6012bb0-04c1-4c9c-a4e6-0f45133f2da0,content-databases-contain-orphaned-apps-sharepoint-server-2016 +SharePoint16ITPro,056e74ea-9428-45f8-abed-1040d8e413dd,sharepoint-server-2016-dev-test-environment-in-azure +SharePoint16ITPro,883fac19-3048-4ef0-b473-10b3b05493b6,managing-a-minrole-server-farm-in-sharepoint-server-2016 +SharePoint16ITPro,4737381b-24e5-4c32-bdff-10dd4a81e648,manage-unused-site-collections-in-sharepoint-server +SharePoint16ITPro,ae92f528-9768-4ea1-9b19-110fb4c88c7f,plan-sharepoint-server-hybrid +SharePoint16ITPro,3fdbc40b-8562-4bec-be89-113a64e19911,configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re +SharePoint16ITPro,ebbd99e2-98e8-478f-87f3-12f195741b72,sql-server-and-storage-sharepoint-server +SharePoint16ITPro,39928a90-e197-4755-af49-130e1ba6f5e5,manage-web-parts-in-sharepoint-server +SharePoint16ITPro,d1c43543-2363-4762-882f-13f06295d0d5,best-practices-for-sql-server-in-a-sharepoint-server-farm +SharePoint16ITPro,85aa1c35-1322-42ad-a625-1496aee67858,databases-within-this-farm-are-set-to-read-only-and-will-fail-to-upgrade-unless +SharePoint16ITPro,462e12d6-1a5d-4b7c-a0d5-14c551262be1,overview-of-sites-and-site-collections-in-sharepoint-server +SharePoint16ITPro,8404adef-6bfb-4795-be16-15739e1212f5,copy-configuration-settings-between-farms-in-sharepoint-server +SharePoint16ITPro,d63f37bc-3383-4df8-af12-15da5eb1133c,accessibility-guidelines-in-sharepoint-server-2016 +SharePoint16ITPro,6483e4c3-dc7e-49fd-92a7-15e1bb63d432,overview-of-monitoring-in-sharepoint-server +SharePoint16ITPro,89c08a8b-74ee-4a97-8885-16c4c5a1288d,manage-company-name-extraction-in-sharepoint-server +SharePoint16ITPro,3ebcdcdf-593e-44bd-b60d-16efd5f07a16,configure-trust-for-search-between-two-sharepoint-server-farms +SharePoint16ITPro,4356bad9-de1d-4e81-b049-17248b4a86c1,plan-crawling-and-federation-in-sharepoint-server +SharePoint16ITPro,8198232e-8d49-46fa-b9f0-17b1d5ee6b62,overview-of-the-user-profile-service-architecture-in-sharepoint-server +SharePoint16ITPro,e0797f61-5b78-4a8d-92ea-17e9f5b5ab56,video-cleanup-of-databases-after-upgrade-procedure +SharePoint16ITPro,a8c86550-d709-4333-9b38-181590d5ead9,monitor-and-manage-app-licenses-in-sharepoint-server +SharePoint16ITPro,dfe5a861-519a-4fc0-89b8-185df5e73284,overview-of-managing-digital-assets-in-sharepoint-server-2013 +SharePoint16ITPro,56ea0f40-426b-43da-aff5-187fe5adc946,prepare-to-back-up-and-restore-farms-in-sharepoint-server +SharePoint16ITPro,45d9570f-59d7-4f6b-b8e1-18868b27b0bc,the-settings-for-word-automation-services-are-not-within-the-recommended-limits +SharePoint16ITPro,0ed0b44c-d60d-4b85-87de-19065d968835,plan-for-sharepoint-server +SharePoint16ITPro,48a1c449-7bf6-4f12-a5f3-1933caadf713,validate-the-business-connectivity-services-hybrid-scenario +SharePoint16ITPro,d845819f-0cbf-4595-bb14-19414acbd79b,plan-hybrid-federated-search-for-sharepoint-server +SharePoint16ITPro,f58bdfdc-0c7e-481e-b3ac-194423f37262,system-center-operations-manager-knowledge-articles-for-sharepoint-server +SharePoint16ITPro,41ec2552-43cd-471a-ba22-1962297758c0,configure-a-business-data-connectivity-service-application-in-sharepoint-server +SharePoint16ITPro,97384552-ef3d-48ba-be57-1abc7d4c7f0a,capacity-management-and-sizing-overview-for-sharepoint-server-2013 +SharePoint16ITPro,6aa16d9a-812a-4bbc-b421-1b4589452503,move-content-databases-in-sharepoint-server +SharePoint16ITPro,04812402-43d6-4605-960c-1dd5ec65bef1,create-a-high-availability-architecture-and-strategy-for-sharepoint-server +SharePoint16ITPro,d08d6d65-23c2-48cb-a871-1e021a382e5e,back-up-the-secure-store-service-in-sharepoint-server +SharePoint16ITPro,d6845f9b-7c1e-4220-a24d-1e5cade8f0d8,configure-result-sources-for-search-in-sharepoint-server +SharePoint16ITPro,83ee2a38-1b91-4c6a-83de-1e968db74611,set-a-content-database-to-use-rbs-with-filestream-in-sharepoint-server +SharePoint16ITPro,5005124c-09d0-435c-99a4-1f2cb1fdae91,turn-on-automated-document-translation-in-sharepoint-server-2016 +SharePoint16ITPro,d10d1262-7127-424e-a0a8-1f3c5d42dd85,run-hybrid-picker +SharePoint16ITPro,bd5f42e5-81a9-47bc-a17e-1f9574324961,use-effectiveusername-in-performancepoint-services +SharePoint16ITPro,c2eda191-1814-423b-882f-1fdafe9df6c9,create-edit-and-delete-quota-templates-in-sharepoint-server +SharePoint16ITPro,0490bf49-4e23-475f-bf37-2000dca31845,co-authoring-administration-in-sharepoint-2013 +SharePoint16ITPro,b71ccbbf-37c0-46c2-a403-20934e1e104e,sharepoint-intranet-farm-in-azure-phase-3-configure-sql-server-infrastructure +SharePoint16ITPro,7c82bdf9-453f-4ee9-a2e6-20adf05ad59c,use-visio-services-with-secure-store-service-in-sharepoint-server +SharePoint16ITPro,937a136c-7cc1-4e61-8a2c-2161d484c13f,configure-sharepoint-health-analyzer-rules-in-sharepoint-server +SharePoint16ITPro,f3819495-4b67-4a71-ba46-23e43b175620,verify-database-upgrades-in-sharepoint-server-2016 +SharePoint16ITPro,57d52c9e-5069-4bcf-87e3-24482198a462,add-apps-for-sharepoint-to-a-sharepoint-site +SharePoint16ITPro,2093c146-c880-48c6-9526-24cdf80969ba,plan-for-people-picker-in-sharepoint-2013 +SharePoint16ITPro,42e7a722-1e13-4f48-b866-2548cff05225,set-up-onedrive-for-business-in-a-sharepoint-server-on-premises-environment +SharePoint16ITPro,144e5f6e-0c9c-4f01-9b1f-26190d527e85,synchronize-user-and-group-profiles-in-sharepoint-server-2013 +SharePoint16ITPro,9cea4a3d-c196-4d9e-942d-2677a6c15c13,configure-power-pivot-for-sharepoint-2013 +SharePoint16ITPro,59f3af85-89f9-43ba-b364-28a810cae42e,configure-the-co-authoring-versioning-period-in-sharepoint-2013 +SharePoint16ITPro,7bc6999f-c4f4-476f-ba0b-28b74166e9c2,get-and-install-the-yammer-app-onto-sharepoint-server-2013-sites +SharePoint16ITPro,d7b9c8dd-274a-46ec-a8f6-28b7f5f0fa9e,verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-ap +SharePoint16ITPro,820ace03-1fb7-41fd-a077-28b82ebddde3,administer-search-in-sharepoint-server +SharePoint16ITPro,1e637e17-2634-4601-a574-299a7c27bb24,export-sites-lists-or-document-libraries-in-sharepoint-server +SharePoint16ITPro,5e242415-c288-48c7-a373-29acc359ad95,the-visio-graphics-service-has-a-maximum-cache-size-setting-that-may-adversely-i +SharePoint16ITPro,d04ccc23-89b1-4927-9607-2a1073d67580,verify-that-the-activity-feed-timer-job-is-enabled-sharepoint-server-2016 +SharePoint16ITPro,22d5dc9c-66bd-40d7-8c60-2a2a066db224,plan-for-multilingual-sites-in-sharepoint-server +SharePoint16ITPro,f753e138-04c2-4358-a12e-2a406a431ac9,supported-and-unsupported-documentum-object-types-and-properties-in-sharepoint-s +SharePoint16ITPro,185da9e8-9ed1-4bf1-bfb5-2a5a874f2a19,identify-users-and-analyze-document-usage-in-sharepoint-2013 +SharePoint16ITPro,bfe89420-2a60-4ce7-8b11-2b45fd38f822,verify-that-the-critical-user-profile-application-and-user-profile-proxy-applica +SharePoint16ITPro,6c4f87aa-1004-4b87-aaca-2c262588fc46,manage-the-index-component-in-sharepoint-server +SharePoint16ITPro,b37c1d36-5bfe-4f76-bb03-2c5436c043a2,install-and-configure-workflow-for-sharepoint-server-2013 +SharePoint16ITPro,f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b,a-state-service-application-has-no-database-defined-sharepoint-server-2016 +SharePoint16ITPro,e913bd67-b50b-47d7-9784-2d312b97de0b,best-practices-for-organizing-content-for-search-in-sharepoint-server +SharePoint16ITPro,842d7420-32ee-4e82-a8db-2dbb3e01a36c,configure-my-sites-and-onedrive-for-business-in-sharepoint-server +SharePoint16ITPro,40ed4458-d798-4aa1-82b9-2e5433991596,restore-content-from-unattached-content-databases-in-sharepoint-server +SharePoint16ITPro,81890ff0-e2f9-4752-8e8e-2e8502c76311,manage-the-search-schema-in-sharepoint-server +SharePoint16ITPro,5cf2a498-d879-4673-b4d4-2eaa36695ff9,view-search-diagnostics-in-sharepoint-server +SharePoint16ITPro,9ff8ab96-6028-4f6a-8cc2-2ebe7eb19413,view-health-reports-in-sharepoint-server +SharePoint16ITPro,db44c8d7-e081-42a3-a42a-2ee1b369dd47,back-up-content-databases-in-sharepoint-server +SharePoint16ITPro,80f7df54-738e-49ba-9ff9-2f312d77a271,back-up-user-profile-service-applications-in-sharepoint-server +SharePoint16ITPro,7a690328-78c5-4dc2-b03f-30165ad186c1,result-types-and-display-templates-that-are-used-to-display-search-results-in-sh +SharePoint16ITPro,6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2,add-or-remove-service-application-connections-from-a-web-application-in-sharepoi +SharePoint16ITPro,ffec2e36-9142-45ae-866e-308d6efbc114,configure-and-use-the-exchange-connector-for-sharepoint-server +SharePoint16ITPro,49150632-b723-44ae-9918-3099f7dd0151,overview-of-performancepoint-scorecards +SharePoint16ITPro,2785b806-01ce-498a-9f73-30da470c2956,configure-the-hybrid-infrastructure +SharePoint16ITPro,ca5a0b10-4020-4f9e-8ecc-30e64c4b109f,plan-for-the-multilingual-user-interface-in-sharepoint-server +SharePoint16ITPro,4fbe0228-54c6-40ce-a9d3-3198423fe688,use-effectiveusername-with-excel-services-sharepoint-server-2013 +SharePoint16ITPro,dee7c975-5738-494f-bf70-31b0e0bc8206,overview-of-microsoft-identity-manager-synchronization-service-in-sharepoint-ser +SharePoint16ITPro,3fdf9bcc-11c0-48af-b8c3-327902f53d73,search-in-sharepoint-server-2016-knowledge-articles-for-systems-center-operation +SharePoint16ITPro,763613ac-83f4-424e-99d0-32efd0667bd9,plan-security-hardening-for-sharepoint-server-2016 +SharePoint16ITPro,7b24439f-640a-412d-a35b-33007966bb58,supporting-the-sharepoint-mobile-apps-online-and-on-premises +SharePoint16ITPro,7c877590-c6b4-48b2-aee3-330c5d42d44c,install-and-configure-rbs-with-a-3rd-party-provider-for-sharepoint-server +SharePoint16ITPro,8926030c-ace4-4e32-ada6-3333b56812c3,how-to-use-the-managed-solutions-gallery +SharePoint16ITPro,1c3b661f-7d88-4b2c-bc3a-3337253f3f30,best-practices-for-upgrading-to-sharepoint-server-2016 +SharePoint16ITPro,6f1b9f42-2408-43e3-ab87-33b122a8b545,plan-publishing-sites-for-cross-site-publishing-in-sharepoint-server +SharePoint16ITPro,5d120a41-37e5-4711-b31e-33e82b034af0,manage-the-distributed-cache-service-in-sharepoint-server +SharePoint16ITPro,6f72c13c-d745-484a-b07f-3426e3c49d3f,overview-of-the-performancepoint-decomposition-tree +SharePoint16ITPro,75113d71-7193-44ab-b79b-34cb9cf9aa94,troubleshoot-site-collection-upgrade-issues-in-sharepoint-server-2016 +SharePoint16ITPro,8c733fb9-18b9-4770-b90b-364bd7ab30d1,sharepoint-intranet-farm-in-azure-phase-4-configure-sharepoint-servers +SharePoint16ITPro,403e75f3-9e53-4d5b-a476-365e6e4bc92e,authentication-overview-for-sharepoint-server +SharePoint16ITPro,cdaf9810-59dc-4afb-af6a-36ceb3795da7,create-an-excel-services-dashboard-using-an-odata-data-feed +SharePoint16ITPro,c5b49fbd-4c1a-4188-a509-373298e92c1b,ip-support-in-sharepoint-2013 +SharePoint16ITPro,837761f9-0e18-4b42-8798-3776997a6c95,high-availability-and-disaster-recovery-concepts-in-sharepoint-server +SharePoint16ITPro,e56b99dc-3731-4cdd-8576-3777c3827e49,the-number-of-distributed-cache-hosts-in-the-farm-exceeds-the-recommended-value +SharePoint16ITPro,c598457b-38d9-434c-b715-3786109cd27e,set-permissions-to-published-service-applications-in-sharepoint-server +SharePoint16ITPro,df399658-84ac-4ca6-aaf4-378eef361cbb,what-is-governance-in-sharepoint +SharePoint16ITPro,cab37e59-7ae1-403a-8fa2-37fe0701961e,one-or-more-web-applications-are-configured-to-use-windows-classic-authenticatio +SharePoint16ITPro,de17a1ff-79f4-4638-918b-380fb0a15205,monitoring-and-reporting-in-sharepoint-server +SharePoint16ITPro,7c8ddec1-c8ff-4a90-afae-387b27a653f1,overview-of-search-result-ranking-in-sharepoint-server +SharePoint16ITPro,067783ba-e22f-41a8-9a1b-38a89c3a30c2,configure-visio-services-data-refresh-in-sharepoint-server-by-using-external-dat +SharePoint16ITPro,c824fa0f-bae9-4791-92ee-38d8e70140ec,accounts-needed-for-hybrid-configuration-and-testing +SharePoint16ITPro,57592cbe-47c1-44c7-8f57-38fa192df4f7,the-server-farm-account-should-not-be-used-for-other-services-sharepoint-server +SharePoint16ITPro,40d265d9-dd16-405f-8c85-390975024bad,get-started-with-upgrades-to-sharepoint-server-2016 +SharePoint16ITPro,ca15deea-3645-4a49-b39d-395ff87195fa,test-and-troubleshoot-an-upgrade-to-sharepoint-server-2016 +SharePoint16ITPro,0112182a-6246-4d8a-8c07-39622be3c4a1,export-and-import-customized-search-configuration-settings-in-sharepoint-server +SharePoint16ITPro,e4b1234e-2b69-4c44-9621-398d20122cab,business-data-connectivity-connectors-are-currently-enabled-in-a-partitioned-env +SharePoint16ITPro,7ad523f5-db54-4169-81ba-3a7b60f218b7,uninstall-sharepoint-server-2016 +SharePoint16ITPro,9b1e8b21-7675-4186-beb6-3adeef4360e6,database-types-and-descriptions-in-sharepoint-server +SharePoint16ITPro,733647a3-a5d3-475b-967d-3bb627c2a0c2,install-and-manage-apps-for-sharepoint-server +SharePoint16ITPro,a19bb905-2984-4512-8e8a-3c17ec3680c0,manage-the-app-catalog-in-sharepoint-server +SharePoint16ITPro,b3cb17a1-939c-4314-9f83-3c6b8a309bba,import-a-list-or-document-library-in-sharepoint-server +SharePoint16ITPro,2ce4b90f-5eb0-4d5d-8ddb-3cf00952de4e,plan-for-server-to-server-authentication-in-sharepoint-server +SharePoint16ITPro,26272515-e0ec-4764-b148-3cf55e520995,plan-search-for-cross-site-publishing-sites-in-sharepoint-server-2016 +SharePoint16ITPro,ba00a200-ea96-45f6-a423-3cfcffba77f8,about-service-applications-and-services-in-sharepoint-server +SharePoint16ITPro,30f4e254-0b00-49bb-84af-3ece619ad0e4,use-a-sharepoint-server-2013-records-archive-or-manage-records-in-place +SharePoint16ITPro,3fa7973f-2c1a-4be0-b903-3f1e6bdcf1d8,create-and-configure-a-search-service-application-in-sharepoint-server-2016 +SharePoint16ITPro,38095e9b-5b48-4d2a-a787-3f7900b138e0,machine-translation-service-in-sharepoint-server-2016-knowledge-articles +SharePoint16ITPro,d7d023a6-0d61-47ae-b442-3fd8108bcbb7,distributed-cache-service-is-unexpectedly-configured-on-server-s +SharePoint16ITPro,f7fcf9d3-c895-4f91-b9c2-4036519a2fd5,secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sh +SharePoint16ITPro,01abe8d2-33f8-48fe-af76-40522a5afe08,plan-for-backup-and-recovery-in-sharepoint-server +SharePoint16ITPro,88878bbd-e26e-4fed-8f2a-40a81fb4d528,the-timer-service-failed-to-recycle-sharepoint-server-2016 +SharePoint16ITPro,c24cffe8-fa32-43e4-95ed-42118ef9643d,display-hybrid-federated-search-results-in-sharepoint-online +SharePoint16ITPro,0853bed9-1084-413b-bf91-427dc643a5e5,configure-excel-services-data-refresh-by-using-external-data-connections-in-shar +SharePoint16ITPro,984e2448-e53a-4b4e-bd4a-4340213218a2,manage-crawl-rules-in-sharepoint-server +SharePoint16ITPro,b4c2dace-97fc-43c7-8991-44279a4fe05d,use-a-sample-mim-solution-in-sharepoint-server-2016 +SharePoint16ITPro,fb651b8b-5657-4686-b084-443016aba76c,the-paging-file-size-should-exceed-the-amount-of-physical-ram-in-the-system-shar +SharePoint16ITPro,3efb6e12-ad3c-41c7-9def-446df626aefd,server-to-server-authentication-and-user-profiles-in-sharepoint-server +SharePoint16ITPro,fcfdb2ad-9d0e-43ca-8bfa-45064eeca5af,configure-excel-services-data-refresh-by-using-the-unattended-service-account-in +SharePoint16ITPro,64233599-f18c-4081-a3ce-450e878a1b9f,system-requirements-for-sharepoint-server-2016 +SharePoint16ITPro,e8baee59-a84d-4f56-bdeb-45de7d522b68,integrate-a-yammer-network-into-sharepoint-server-2013-with-social-features +SharePoint16ITPro,32bc4341-ba5f-444b-bd55-462f67f16c27,security-for-sharepoint-server +SharePoint16ITPro,cbb3b242-76ed-4539-b454-4685a84d57c5,restore-web-applications-in-sharepoint-server +SharePoint16ITPro,96dc4ef1-cec8-47d0-b995-46bca3e8eda2,back-up-service-applications-in-sharepoint-server +SharePoint16ITPro,f50ca1b2-5075-49f6-9689-46c7b8a29b47,restore-search-service-applications-in-sharepoint-server +SharePoint16ITPro,215432d7-cb3b-4af4-beed-47492a6777f0,administer-the-user-profile-service-in-sharepoint-server +SharePoint16ITPro,ac2338f5-1b06-4a7c-9dc0-4751b6421cb3,delete-a-service-application-in-sharepoint-server +SharePoint16ITPro,9d1f5998-e6b6-474c-a2aa-47782b63e53e,overview-of-managed-navigation-in-sharepoint-server +SharePoint16ITPro,a2ef35c4-6b29-4ad1-8652-48a019838ea0,configure-excel-services-sharepoint-server-2013 +SharePoint16ITPro,73d7f970-c378-4b31-92d5-48cdeb8075e6,document-farm-configuration-settings-in-sharepoint-server +SharePoint16ITPro,5a1b6cd9-358c-41af-8309-495640518eac,integrate-multiple-yammer-networks-into-sharepoint-server-2013 +SharePoint16ITPro,a96075c6-d315-40a8-a739-49b91c61978f,storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server +SharePoint16ITPro,e00cc8ed-8a01-4928-9175-49efe03288a1,critical-state-of-this-rule-indicates-that-the-word-automation-services-is-not-r +SharePoint16ITPro,4385b870-c3ec-462f-a43d-49f18e4d8675,plan-for-visio-services-in-sharepoint-server +SharePoint16ITPro,9b5a1f99-0193-4a97-b0d1-4a5633b32c43,redesign-enterprise-search-topology-for-more-content-and-users-in-sharepoint-201 +SharePoint16ITPro,ff584a8c-871c-40bf-8ada-4a59615abbc9,hide-sharepoint-server-2013-social-features +SharePoint16ITPro,48fa0391-b996-4a46-8744-4b1777db3d2f,add-the-yammer-embed-widget-to-a-sharepoint-page +SharePoint16ITPro,606ba9e1-807a-4a1a-a1ad-4bad474e5371,manage-site-collections-in-sharepoint-server +SharePoint16ITPro,4045020c-6ed2-4139-84f4-4bf7d099918d,plan-for-feeds-and-the-distributed-cache-service-in-sharepoint-server +SharePoint16ITPro,335af336-da96-4b50-9901-4c4ef151c790,verify-that-oauth-is-configured-correctly-for-the-machine-translation-service-ap +SharePoint16ITPro,eebac7af-f3e4-4e71-ad57-4c5ff3a58f30,plan-for-apps-for-sharepoint-server +SharePoint16ITPro,f957e1ce-0a39-490c-b533-4ddab4f5bb7a,sharepoint-intranet-farm-in-azure-phase-1-configure-azure +SharePoint16ITPro,213926f7-93d0-410c-ad6f-4de55376fe5b,overview-of-performancepoint-strategy-maps +SharePoint16ITPro,6485e76d-9c52-40eb-ae0f-4e00c321c7d8,integrate-a-new-yammer-network-into-sharepoint-server-2013 +SharePoint16ITPro,4c7e118f-e3f3-450d-acf1-4e219c932fce,plan-for-my-sites-and-onedrive-for-business-in-sharepoint-server +SharePoint16ITPro,5e44cf6c-2271-4ff1-af7f-4e73849ffdf6,configure-adventureworks-for-business-intelligence-solutions +SharePoint16ITPro,0c7bea8c-36aa-450e-806c-4eacf793ae9c,manage-sites-in-sharepoint-server +SharePoint16ITPro,ad39b1b5-a73b-4a48-af5e-4f032ea52e1d,configure-a-hybrid-solution-for-sharepoint-server +SharePoint16ITPro,24ddec7e-b6a3-4a93-ad97-501d32d1a4c1,edit-existing-web-parts-in-sharepoint-server +SharePoint16ITPro,a6a42ac0-abad-44ce-98f3-508c531a29b2,overview-of-site-navigation-in-sharepoint-server +SharePoint16ITPro,33ed78c8-25fc-48ea-b0c1-50b540213cff,configure-usage-and-health-data-collection-in-sharepoint-server +SharePoint16ITPro,0926f63d-8dae-44c0-9e91-51209aa4c3ef,add-sharepoint-server-to-a-farm-in-sharepoint-server-2016 +SharePoint16ITPro,b291ea58-cfda-48ec-92d7-5180cb7e9469,plan-connectivity-from-office-365-to-sharepoint-server +SharePoint16ITPro,68551945-009f-43c2-b38f-5248aaf6d540,mobile-device-browsers-supported-in-sharepoint-2013 +SharePoint16ITPro,f26ad022-5c99-4a27-a093-52cc9ee71296,hybrid-for-sharepoint-server +SharePoint16ITPro,f8f81869-a51f-4d7f-b4b6-52dd99078c23,restore-site-collections-in-sharepoint-server +SharePoint16ITPro,f3855245-795f-4a77-bc70-5456511eaadd,understanding-result-sources-for-search-in-sharepoint-server +SharePoint16ITPro,f140e0ad-07e4-42f8-a198-54d800355698,the-machine-translation-service-is-not-running-when-it-should-be-running-sharepo +SharePoint16ITPro,8da53a30-27f2-4297-95c2-54eff999e863,sharepoint-server-2016-in-microsoft-azure +SharePoint16ITPro,2ea95490-00c0-4c67-b7e3-551d2fe032b9,restore-solutions-in-sharepoint-server +SharePoint16ITPro,2d8373ff-0808-40b7-8a21-5534720719f4,query-variables-in-sharepoint-server +SharePoint16ITPro,adbb853e-d8ef-48bb-9ca1-55612809c680,test-lab-guides-for-sharepoint-server-2013 +SharePoint16ITPro,5fbe84ab-4ec4-4b8f-be25-559a1cdfc68e,plan-for-mobile-devices-in-sharepoint-2013 +SharePoint16ITPro,8b35493f-45d2-428f-b17b-55d69ee11138,manage-anonymous-access-for-a-web-application-in-sharepoint-server +SharePoint16ITPro,d6a85e37-4a3c-4c89-913c-563bb9c8a013,overview-of-ediscovery-and-in-place-holds-in-sharepoint-server +SharePoint16ITPro,7924fe8b-986c-44eb-8dd3-5724acecd529,overview-of-themes-in-sharepoint-server +SharePoint16ITPro,3c0edb6f-3b77-48bc-a542-57626741f3ba,plan-for-cross-site-publishing-in-sharepoint-server +SharePoint16ITPro,4d7a8038-4b27-4bd8-a855-585db4e924a8,overview-of-the-upgrade-process-to-sharepoint-server-2016 +SharePoint16ITPro,94d4fecf-3250-42aa-8230-5890790e24db,configure-the-onedrive-for-business-modern-user-experience +SharePoint16ITPro,055e27eb-3e02-4470-a037-5896bab44736,create-and-deploy-custom-entity-extractors-in-sharepoint-server +SharePoint16ITPro,4fcd074b-32b1-49b3-9910-5bb174894603,the-visio-graphics-service-has-a-minimum-cache-age-setting-that-may-cause-a-secu +SharePoint16ITPro,069bcdb5-f9bb-4346-8304-5be2f768e3dc,configure-sharepoint-server-2016 +SharePoint16ITPro,9ed8159f-9501-4ef3-8c84-5d775a1e6223,manage-excel-services-trusted-file-locations-sharepoint-server-2013 +SharePoint16ITPro,1b4765ef-3d28-4082-bb37-5d84e9996c44,overview-of-records-management-in-sharepoint-server-2013 +SharePoint16ITPro,02f10b70-d634-41ae-914e-5de337c8b408,overview-of-business-connectivity-services-in-sharepoint-server +SharePoint16ITPro,d47575fa-bb85-4017-8db7-5e25f98ba171,upgrade-my-sites-to-sharepoint-server-2016 +SharePoint16ITPro,acb2d589-6c19-4b6b-9cd1-5e334ba4f2cd,remove-a-server-from-a-farm-in-sharepoint-server-2016 +SharePoint16ITPro,85ba39ff-5dd3-4a88-98c2-5ec9d6928d2e,yammer-networks-groups-and-users-overview +SharePoint16ITPro,4bf21275-1b38-4299-b80d-5f12e8b87a47,plan-for-hybrid-sites-features +SharePoint16ITPro,80521ae8-be93-4d1c-9956-5f4bed1ac4a7,dedicated-crawl-target-configuration-has-one-or-more-invalid-servers-sharepoint +SharePoint16ITPro,3661eafe-91da-4467-91f1-5fa47947e178,the-visio-graphics-service-has-a-maximum-web-drawing-size-setting-that-will-adve +SharePoint16ITPro,7fa9730a-2d11-4c78-b546-60179c5bb646,change-the-default-search-topology-in-sharepoint-server +SharePoint16ITPro,18aeede1-07b9-43ee-88ee-602a7a5acfa6,database-has-large-amounts-of-unused-space-sharepoint-server-2016 +SharePoint16ITPro,5aeff319-0a8f-4d6b-86d5-6086611c48ed,services-upgrade-overview-for-sharepoint-server-2016 +SharePoint16ITPro,8bfb96e6-f27e-41f0-8038-609e82098dd9,plan-the-logical-architecture-for-cross-site-publishing-in-sharepoint-server +SharePoint16ITPro,19d553a7-7001-4b07-a03d-616b865b05ae,default-crawled-file-name-extensions-and-parsed-file-types-in-sharepoint-server +SharePoint16ITPro,a8653e44-5bbc-4ca1-8e9a-61cc41349df1,software-boundaries-and-limits-for-sharepoint-2013 +SharePoint16ITPro,4f5ab7db-276f-4de3-a991-62136ba8ca91,databases-exist-on-servers-running-sharepoint-foundation-sharepointserver-2016 +SharePoint16ITPro,62d0b8d3-e8ea-4523-a69f-62623fb340fb,sharepoint-intranet-farm-in-azure-phase-5-create-the-availability-group-and-add +SharePoint16ITPro,6529a690-639d-47fc-9399-62813ae331ef,overview-of-performancepoint-analytic-charts-and-grids +SharePoint16ITPro,7fda5f6e-ffbc-40af-9e5d-62f055a9c9b0,intranet-sharepoint-server-2016-in-azure-dev-test-environment +SharePoint16ITPro,a9edfdaf-99da-4740-9e2a-631aded785ae,move-or-rename-service-application-databases-in-sharepoint-server +SharePoint16ITPro,5af9ee8b-39b8-489b-bcb9-64099618db51,what-s-deprecated-or-removed-from-sharepoint-server-2016 +SharePoint16ITPro,94a8041c-f047-4f03-b973-65eb85f8e4fc,remove-app-for-sharepoint-instances-from-a-sharepoint-site +SharePoint16ITPro,ca092ed2-4aa2-4c2e-b273-661ca6a76e01,plan-incoming-email-for-a-sharepoint-server-2016-farm +SharePoint16ITPro,fe776cf2-17a4-4bb6-95ea-66288f243a93,overview-of-excel-services-in-sharepoint-server-2013 +SharePoint16ITPro,d849b7df-b26d-45f6-a74f-6641f18788cf,restore-farm-configurations-in-sharepoint-server +SharePoint16ITPro,a2db324b-bcbe-40b4-8fa1-66f16cc89890,plan-web-content-management-in-sharepoint-server +SharePoint16ITPro,3b4c9519-b68c-4247-8b58-674537f0c5fe,prepare-your-environment-for-the-business-connectivity-services-hybrid-scenario +SharePoint16ITPro,f6c7b56e-f684-45d9-8752-67fff01c1728,overview-of-cross-site-publishing-in-sharepoint-server +SharePoint16ITPro,d9dac189-0736-448d-928c-68bf38603613,move-all-databases-in-sharepoint-server +SharePoint16ITPro,d59e6849-84af-4ad0-abed-68fae92574c6,fundamental-site-planning-in-sharepoint-server-2016 +SharePoint16ITPro,d0db716b-1ee7-42c7-b8cf-694360b39d56,configure-versioning-for-co-authoring-in-sharepoint-2013 +SharePoint16ITPro,0864e3e6-37bc-4b43-ae38-6a01f8728e8b,deploy-people-search-in-sharepoint-server +SharePoint16ITPro,3f7cf424-3340-4010-ad3b-6aef0cd74428,deploy-a-business-connectivity-services-hybrid-solution-in-sharepoint +SharePoint16ITPro,16fdd865-105f-47e6-8a3a-6b37092a463c,plan-navigation-term-sets-in-sharepoint-server +SharePoint16ITPro,1a20e357-a21f-4409-9a99-6b8263ab30c5,explore-sharepoint-server +SharePoint16ITPro,b6580f87-40b4-4768-b589-6ba54013f7e4,upgrade-databases-from-sharepoint-2013-to-sharepoint-server-2016 +SharePoint16ITPro,356d3a0b-fc26-455c-9afb-6d2ffdceef84,install-sharepoint-server-2016-on-a-single-server-with-sql-server +SharePoint16ITPro,b67550f6-fc12-4734-950f-6e2f50ef0ca2,missing-server-side-dependencies-sharepoint-server-2016 +SharePoint16ITPro,037fb582-6448-4baf-85d4-6e6221f21655,create-a-file-plan-to-manage-records-in-sharepoint-server-2013 +SharePoint16ITPro,ac16bc32-f623-4658-8bc5-6e6b958629a4,drives-are-at-risk-of-running-out-of-free-space-sharepoint-server-2016 +SharePoint16ITPro,4d88c402-24f2-449b-86a6-6e7afcfec0cd,hardware-and-software-requirements-for-sharepoint-server-2016 +SharePoint16ITPro,53885793-4150-4212-af04-6ea2e6e066f7,outbound-e-mail-has-not-been-configured-sharepoint-server-2016 +SharePoint16ITPro,45264de9-6859-45c1-9d6d-70035c471a2a,plan-for-variations-in-sharepoint-server +SharePoint16ITPro,9fc3a696-b2cb-435c-8199-7048953ec609,planning-for-a-minrole-server-deployment-in-sharepoint-server-2016 +SharePoint16ITPro,28b06934-933b-4899-a7a6-707eb0516552,the-visio-graphics-service-has-a-maximum-cache-age-setting-that-will-adversely-i +SharePoint16ITPro,0a785758-694c-4c5c-abe6-70a17b490c6e,manage-service-applications-in-sharepoint-server +SharePoint16ITPro,e27a812e-9ddd-434f-a32c-70c74d4319f8,manage-farm-level-crawl-settings-in-sharepoint-server +SharePoint16ITPro,e1c3fe21-9110-4861-9fc9-715745c9197a,redesign-enterprise-search-topology-for-specific-performance-requirements-in-sha +SharePoint16ITPro,8f98a750-19bb-4ea0-9ff5-719b85febbb3,back-up-customizations-in-sharepoint-server +SharePoint16ITPro,8451dde9-bbd1-4285-bc24-71bd795fb912,plan-profile-synchronization-for-sharepoint-server-2013 +SharePoint16ITPro,60913d6d-c069-4dfc-9399-71d5344da4e0,enable-tls-and-ssl-support-in-sharepoint-2013 +SharePoint16ITPro,a7960bf4-d5be-4ad7-a430-724ef194ad39,configure-and-use-the-lotus-notes-connector-for-sharepoint-server +SharePoint16ITPro,386082ce-339d-4652-8323-72a78b092782,foo +SharePoint16ITPro,ee879d48-44a3-46e7-a631-736c4430ec94,overview-of-backup-and-recovery-in-sharepoint-server +SharePoint16ITPro,0b6e5490-ea92-4e6d-b2fe-743d06a4c3e6,manage-query-rules-in-sharepoint-server +SharePoint16ITPro,e8f2c08c-8e9f-40b4-b066-747d65dcb0e4,connect-to-service-applications-on-remote-farms-in-sharepoint-server +SharePoint16ITPro,6d980186-7f23-46e9-a2aa-750f1c24fc3d,manage-crawling-in-sharepoint-server +SharePoint16ITPro,7ebd1422-4f3d-44b9-8df6-75274c65b7e5,infopath-form-library-forms-cannot-be-filled-out-in-a-web-browser-sharepoint-ser +SharePoint16ITPro,b5f098eb-219a-4483-adee-75d7b6b3089a,validate-the-my-site-host-and-individual-my-sites-are-on-a-dedicated-web-applica +SharePoint16ITPro,f27522ca-6f78-4b97-b169-77066e965727,designing-a-sharepoint-server-2016-farm-in-azure +SharePoint16ITPro,550e4018-54a3-4e34-a647-7797b4244e80,manage-site-collection-upgrades-to-sharepoint-server-2016 +SharePoint16ITPro,9d89800f-7ebb-4454-9e0a-779ba1737d04,use-visio-services-with-sharepoint-lists +SharePoint16ITPro,38147eec-d89a-478a-956a-779fe76c6679,restore-customizations-in-sharepoint-server +SharePoint16ITPro,57b7618a-2ca4-450d-aa8b-77bce21a9884,configure-site-mailboxes-in-sharepoint-server +SharePoint16ITPro,73ceb46e-d3aa-45bd-ac3e-77f58a9ab34d,configure-profile-synchronization-by-using-sharepoint-active-directory-import-in +SharePoint16ITPro,c8209ecc-59e4-4568-a7e6-782a6b0ab02f,configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoin +SharePoint16ITPro,c033a091-2c08-4d20-8d3f-783317d718fa,plan-for-onedrive-for-business-in-sharepoint-server +SharePoint16ITPro,6641730b-7099-47c0-938f-783ea8ef8e62,start-or-stop-a-service-in-sharepoint-server +SharePoint16ITPro,88317397-e0cb-47c7-9093-7872bc685213,configure-incoming-email-for-a-sharepoint-server-farm +SharePoint16ITPro,bbb62edb-def7-45dd-931c-78746c3d9fa5,the-building-blocks-of-sharepoint-hybrid +SharePoint16ITPro,2be5291e-b6cc-4730-bc58-78b14ea1984b,configure-excel-services-data-refresh-by-using-embedded-data-connections-in-shar +SharePoint16ITPro,8e7535ee-8a38-4878-aaf3-78b669f4aca8,custom-tiles-in-sharepoint-server-2016 +SharePoint16ITPro,169ef750-0c8c-471d-b04e-79bf8b4d5ec7,sharepoint-server-2016-zero-downtime-patching-steps +SharePoint16ITPro,1609167e-e47a-41d6-b8fc-7a8d0ba8f7ce,system-requirements-for-sharepoint-2013 +SharePoint16ITPro,d7173fc7-65cd-4201-8095-7ad805f50c95,deploy-the-business-connectivity-services-hybrid-scenario-as-an-external-list +SharePoint16ITPro,7acd8bf3-5bb5-4ae6-afa2-7af3c5cefa85,share-workbooks-by-using-excel-services-sharepoint-server-2013 +SharePoint16ITPro,86e0fc90-0ef8-4c22-9d3b-7af42bf882f1,configure-sharepoint-hybrid-auditing-in-sharepoint-2016-preview +SharePoint16ITPro,f628e7df-ce37-4c33-aed3-7c6745d48a39,manage-the-search-center-in-sharepoint-server +SharePoint16ITPro,b23e4fb4-6ee1-451e-92b3-7c90be5dc7e7,timer-job-reference-for-sharepoint-server-2016 +SharePoint16ITPro,4b32dfba-1af6-4077-9a92-7cec8f220f20,sharepoint-updates +SharePoint16ITPro,24292545-0844-4eb0-9e80-7d4c9985755d,drives-used-for-sql-databases-are-running-out-of-free-space-sharepoint-server-20 +SharePoint16ITPro,cd646bb3-28c6-4040-866c-7d7936837ade,configure-object-cache-user-accounts-in-sharepoint-server +SharePoint16ITPro,766e0169-1a5d-4730-9c9f-7e2b27ba7d5d,configure-properties-of-the-search-box-web-part-in-sharepoint-server +SharePoint16ITPro,ad6a501d-5d8c-4b87-af69-7f655b8c3d1e,authentication-for-mobile-devices-in-sharepoint-2013 +SharePoint16ITPro,81ea6763-c331-453b-80f7-8028c3e551f8,configure-hybrid-onedrive-for-businessroadmap +SharePoint16ITPro,eabe099e-5eea-4b33-8241-8079d9409095,manage-query-spelling-correction-in-sharepoint-server +SharePoint16ITPro,265ace67-3115-4987-ab2d-80c55e452d4b,extend-claims-based-web-applications-in-sharepoint +SharePoint16ITPro,af7cf3e7-94b1-4a5d-8cb9-80c5a0b397f2,deploying-sharepoint-server-2016-with-sql-server-alwayson-availability-groups-in +SharePoint16ITPro,2258fc12-68ad-4175-9735-812768a80093,configure-services-and-service-applications-in-sharepoint-server +SharePoint16ITPro,74b5c26f-a033-4d3a-a2ae-812ef043c3a7,manage-excel-services-trusted-data-providers-sharepoint-server-2013 +SharePoint16ITPro,4bd426f4-105c-41cf-a4b8-815db62191ce,configure-hybrid-sites-featuresroadmap +SharePoint16ITPro,3e2db0df-d07c-4adc-98a1-81e3fd42a272,scale-enterprise-search-in-sharepoint-server +SharePoint16ITPro,4de4007d-a45f-419d-9512-824421e14380,plan-for-information-management-policy-in-sharepoint-server-2013 +SharePoint16ITPro,ae626fda-efc1-4b99-9909-829346b04b6f,configure-performancepoint-services +SharePoint16ITPro,4c50e9d2-a1f9-45a5-8466-829e056a92d0,create-an-excel-services-dashboard-using-a-data-model-sharepoint-server-2013 +SharePoint16ITPro,76c08191-13da-4cdc-beee-82c30033b7dc,configure-the-managed-metadata-service +SharePoint16ITPro,8fe00c69-317f-49c9-8669-832a5f85e42c,data-authentication-for-excel-services-in-sharepoint-server-2013 +SharePoint16ITPro,7021185c-1f2b-44a6-ba4a-8355dd8409e1,share-a-sql-server-analysis-services-data-connection-using-excel-services-sharep +SharePoint16ITPro,9f0df411-ba75-4d04-9195-836129fe2282,share-service-applications-across-farms-in-sharepoint-server +SharePoint16ITPro,cf432f6e-cd0d-425f-b774-83d802ea84cd,configure-workflow-in-sharepoint-server-2016 +SharePoint16ITPro,bcbae7bd-656b-4003-969c-8411b81fcd77,technical-diagrams-for-sharepoint-server +SharePoint16ITPro,00c33e26-dacb-47d4-97b8-84659095b108,description-of-minrole-and-associated-services-in-sharepoint-server-2016 +SharePoint16ITPro,7a1835c3-6375-4647-b190-84676fc9f9b0,reset-the-search-index-in-sharepoint-server +SharePoint16ITPro,06ad416d-8830-4b1d-96e5-854eda879b60,use-visio-services-with-external-lists-in-sharepoint-server +SharePoint16ITPro,fb4e9a7d-1ad2-4a89-ad90-85d61b44f56d,the-security-token-service-is-not-available-sharepoint-server-2016 +SharePoint16ITPro,240f8caa-afb3-44ce-90bb-861cfa258b09,restore-content-databases-in-sharepoint-server +SharePoint16ITPro,0889004d-6820-4282-a63c-863f4796ff85,add-content-databases-in-sharepoint-server +SharePoint16ITPro,de173e89-b6d8-4d9e-8516-865c2735bfff,update-workflow-in-sharepoint-server-2013 +SharePoint16ITPro,cc73be76-a329-449f-90ab-86822b1c2ee8,getting-started-with-sharepoint-server-2013-workflow +SharePoint16ITPro,25970085-39e6-4b1f-83c7-8687a5f8e939,databases-used-by-sharepoint-have-outdated-index-statistics-sharepoint-server-20 +SharePoint16ITPro,a5c66813-3523-40d1-99d8-86e8359b6c73,create-a-site-collection-in-sharepoint-server +SharePoint16ITPro,b35d9b02-2207-417c-bb90-870474b6f57c,flush-the-blob-cache-in-sharepoint-server +SharePoint16ITPro,a193cfdb-ac5e-45fa-bf83-87849e38ac27,back-up-apps-for-sharepoint-in-sharepoint-server +SharePoint16ITPro,4192cf8b-0f17-43ad-8e79-87acfc96e935,search-technical-reference-for-sharepoint-server +SharePoint16ITPro,86bb109d-865f-4f86-bb3d-87ecfc4e50ae,move-site-collections-between-databases-in-sharepoint-server +SharePoint16ITPro,f8efdfaf-8ef6-445c-9fb9-8845667e478b,application-management-and-governance-in-sharepoint +SharePoint16ITPro,5c3a4913-246a-4f1e-9257-88587a4272f2,overview-of-reporting-services-reports-displayed-in-performancepoint-web-parts +SharePoint16ITPro,78e2f208-e4b9-49cd-a036-89809fa24baf,upgrade-a-site-collection-to-sharepoint-server-2016 +SharePoint16ITPro,101dd661-8843-4b98-bab7-89c14abe65b8,back-up-databases-to-snapshots-in-sharepoint-server +SharePoint16ITPro,c6284830-1127-472d-9610-8a0b9b0298aa,share-data-connections-by-using-excel-and-excel-services-sharepoint-server-2013 +SharePoint16ITPro,f3c0fda5-7a36-4c5d-801f-8a3baccb6d6a,plan-document-sets-in-sharepoint-server-2013 +SharePoint16ITPro,b81f80f1-182f-42eb-9546-8a621a4f069f,restrict-or-enable-access-to-a-service-application-in-sharepoint-server +SharePoint16ITPro,75401651-ef01-4348-878e-8a636f0b072d,plan-outgoing-email-for-a-sharepoint-server-2016-farm +SharePoint16ITPro,75096f60-b94e-44c2-bc84-8aa3e2c4fff3,disable-rbs-on-content-databases-in-sharepoint-server +SharePoint16ITPro,b62b6690-a1a6-4163-bdb5-8abae968c5c8,install-and-configure-workflow-for-sharepoint-server-2016 +SharePoint16ITPro,1780ec27-19f8-4d77-b787-8abc23921258,configure-a-reverse-proxy-device-for-sharepoint-server-hybrid +SharePoint16ITPro,0ed3c559-86c1-40d0-8804-8adb7038492f,linguistic-search-features-in-sharepoint-server +SharePoint16ITPro,9c470892-d865-4796-ad45-8b050f29aead,one-or-more-servers-is-not-responding-sharepoint-server-2016 +SharePoint16ITPro,d489421a-f6be-4ee4-8acf-8b79f917aa6b,administer-sites-and-site-collections-in-sharepoint-server +SharePoint16ITPro,cb6871cc-7fc5-4b54-9940-8c0ed51cb08f,plan-sites-and-site-collections-in-sharepoint-server +SharePoint16ITPro,44640e29-bd9c-4b6a-94e1-8d5d30e7fdd2,create-and-deploy-a-thesaurus-in-sharepoint-server +SharePoint16ITPro,feedf4f0-0e18-4592-983b-8d769830bcac,sharepoint-server-2016-hybrid-configuration-roadmaps +SharePoint16ITPro,2db321b3-1d59-4b3a-a242-8daabfde367c,configure-visio-services +SharePoint16ITPro,9f039270-d426-4e79-b608-8db792de74ed,configure-properties-of-the-refinement-web-part-in-sharepoint-server +SharePoint16ITPro,145fc383-d584-487a-8738-8de15512ae26,configure-workflow-in-sharepoint-server-2013 +SharePoint16ITPro,1a11cbf3-ab19-4aa0-ae9c-8e4b793154a2,show-results-from-office-365-in-on-premises-sharepoint-with-cloud-hybrid-search +SharePoint16ITPro,6259e195-2b83-454f-b635-8f228c1fd1ac,enable-query-logging-in-sharepoint-server +SharePoint16ITPro,a3ad4dea-36b2-48df-b699-8fd9725df53c,overview-of-publishing-to-internet-intranet-and-extranet-sites-in-sharepoint-ser +SharePoint16ITPro,f21ef281-ac83-400f-8794-903edf80066d,overview-of-web-page-reports-in-dashboard-designer +SharePoint16ITPro,0bba350d-ec33-43db-a873-930559c78dee,configure-cloud-hybrid-searchroadmap +SharePoint16ITPro,79d47308-a90a-4c51-a1ae-93567e978236,backup-solutions-in-sharepoint-server +SharePoint16ITPro,e1196de0-1eb9-4c50-aeca-93e0eba7be0d,plan-the-secure-store-service-in-sharepoint-server +SharePoint16ITPro,23622f74-cc2c-4121-b22d-93e41af88b94,global-architectures-for-sharepoint-server-2016 +SharePoint16ITPro,69f8553c-3df5-4366-ac6a-941e619a84cf,display-hybrid-federated-search-results-in-sharepoint-server +SharePoint16ITPro,f8dcfd5c-aaec-46cd-b25e-94e14bf98c7d,firewall-client-settings-on-the-cache-host-are-incorrect-sharepoint-server-2016 +SharePoint16ITPro,3e7b12cf-e9bb-48be-9484-950ba70f466c,configure-proxy-server-settings-for-search-in-sharepoint-server +SharePoint16ITPro,63b9e454-f21e-4e0e-bc96-953c0a337c70,the-current-server-is-running-low-on-memory-sharepoint-server-2016 +SharePoint16ITPro,78df8a76-0dbc-403b-b54d-9572fc918531,test-lab-guide-demonstrate-forms-based-claims-authentication-for-sharepoint-serv +SharePoint16ITPro,4982a861-ad5c-43e4-a49f-958afd4370aa,install-sharepoint-server-2016-across-multiple-servers +SharePoint16ITPro,4fdf96bd-813f-4499-b7d2-958b7bce002c,plan-for-site-maintenance-and-management-in-sharepoint-server +SharePoint16ITPro,c145579b-fc8b-4ab4-bc80-95c3202deae2,xliff-translations-for-the-machine-translation-service-is-disabled-sharepoint-se +SharePoint16ITPro,555e6de4-eece-440c-857b-9601c65df4fe,integrate-yammer-with-on-premises-sharepoint-2013-environments +SharePoint16ITPro,ea492d95-d2de-4db2-a848-96cb12dc9eaa,install-and-configure-sharepoint-server-hybrid +SharePoint16ITPro,274c4c7a-e635-4bc9-85b3-9737620f9909,configure-monitoring-in-sharepoint-server-2016 +SharePoint16ITPro,1bb10de1-2b80-48b3-a9f7-9745cb725e6c,plan-variations-for-multilingual-cross-site-publishing-site-in-sharepoint-server +SharePoint16ITPro,6cd7e6d2-092d-47f0-aed0-97bf2c09369a,test-lab-guide-demonstrate-saml-based-claims-authentication-with-sharepoint-serv +SharePoint16ITPro,47603b59-cf37-4778-803d-97c4ebd9b452,plan-authoring-sites-for-cross-site-publishing-in-sharepoint-server +SharePoint16ITPro,7d2cbe64-5888-415e-81be-98b6921929de,disable-co-authoring-in-sharepoint-2013 +SharePoint16ITPro,150f0179-b9d4-4823-b314-98b83a95d85e,secure-sockets-layer-ssl-and-transport-layer-security-tls-protocol-support-in-sh +SharePoint16ITPro,73f19541-9321-4abd-b014-98df79f84d2a,best-practices-for-crawling-in-sharepoint-server +SharePoint16ITPro,3e66d9df-442e-445f-bddc-99b446c2a4cb,plan-for-kerberos-authentication-in-sharepoint-server +SharePoint16ITPro,0ae2f59b-309e-4853-8ce7-99bc40de4c03,cache-settings-operations-in-sharepoint-server +SharePoint16ITPro,28a53440-2adc-4957-84bd-99ed97f0c430,manage-permissions-for-a-web-application-in-sharepoint-server +SharePoint16ITPro,2c727311-e83e-4f7b-b02c-9a0699a81e64,configure-sql-server-security-for-sharepoint-server-2016 +SharePoint16ITPro,761ffca8-ae92-405e-b8c1-9aada2fcbd86,install-a-software-update-for-sharepoint-server-2016 +SharePoint16ITPro,636d25e9-be42-4b66-a354-9b9af570f907,content-databases-contain-orphaned-items-sharepoint-server-2016 +SharePoint16ITPro,95fa5eaf-8130-4dca-814c-9c51eafae0d4,plan-for-hybrid-onedrive-for-business +SharePoint16ITPro,cdaaf121-3fd3-4889-9020-9cf7606c8f6b,share-an-ole-db-or-odbc-connection-using-excel-services-sharepoint-server-2013 +SharePoint16ITPro,b2b379b8-838c-4faa-b3ca-9d1eacd94b01,test-lab-guide-configure-intranet-and-team-sites-for-sharepoint-server-2013 +SharePoint16ITPro,26f02074-af0b-4548-ab68-9d46dd05b8ff,maintain-user-profile-synchronization-settings-in-sharepoint-server-2013 +SharePoint16ITPro,c0adc0b5-ea84-46ae-b2a1-9d8d05dbac03,install-workflow-manager-certificates-in-sharepoint-server-2013 +SharePoint16ITPro,bd9db767-6b87-450d-a8e6-9dc684d59ae4,create-a-search-center-site-in-sharepoint-server +SharePoint16ITPro,486a1b2e-b1e3-4736-9d92-9dca61d57d56,new-features-in-november-2016-pu-for-sharepoint-server-2016-feature-pack-1 +SharePoint16ITPro,0d326419-25c2-4591-acc6-9e487aa80c6e,the-infopath-forms-services-maintenance-timer-job-is-not-enabled-sharepoint-serv +SharePoint16ITPro,b607e000-9436-4cbb-b6aa-9e76d70a4314,plan-document-versioning-content-approval-and-check-out-controls-in-sharepoint-2 +SharePoint16ITPro,85a1866e-2743-4f98-a1ac-9ea61905c6d4,permissions-planning-for-sites-and-content-in-sharepoint-server-2016 +SharePoint16ITPro,0fb9616f-3877-4ba8-a7a7-9f00b6d896cb,configure-sharepoint-health-analyzer-timer-jobs-in-sharepoint-server-2016 +SharePoint16ITPro,134ef0df-babc-42d9-b46e-9f1792a122fe,sharepoint-hybrid-auditing-preview +SharePoint16ITPro,95e12c80-7a86-4655-ba11-a05b9587fee0,configure-secure-store-for-use-with-performancepoint-services +SharePoint16ITPro,73e8ee39-0865-497a-b9e2-a0b0b46cde20,restore-apps-for-sharepoint-in-sharepoint-server +SharePoint16ITPro,3f8ea55b-e483-478c-8b35-a0ef4c6890f4,variations-overview-in-sharepoint-server +SharePoint16ITPro,20e1e0c3-7d5c-489c-a588-a11b30adffb9,the-visio-graphics-service-has-a-maximum-recalc-duration-setting-that-will-adver +SharePoint16ITPro,56187c25-0444-4da7-9879-a141da864704,service-application-and-service-management-in-sharepoint-server +SharePoint16ITPro,fa4625ab-9076-4506-aa7c-a19b6e45a847,change-the-default-account-for-crawling-in-sharepoint-server +SharePoint16ITPro,cccccea9-fda2-4640-ad91-a1d39bdcdfc8,sharepoint-health-analyzer-rules-reference-for-sharepoint-server-2016 +SharePoint16ITPro,bf94ede1-79cc-4016-99f3-a1eef244fdf3,configure-an-environment-for-apps-for-sharepoint-server +SharePoint16ITPro,432973c1-21c1-4fdc-87e6-a2252596937a,configure-the-crawler-in-case-of-ssl-certificate-warnings-in-sharepoint-server +SharePoint16ITPro,5eccfa5b-05ec-46b6-935c-a2d8487965da,configure-automatic-password-change-in-sharepoint-server +SharePoint16ITPro,411e0fa7-2a27-4883-93ac-a2fd228e40d8,configure-the-unattended-service-account-for-performancepoint-services +SharePoint16ITPro,c5d39627-dfa6-4122-8571-a38bdd3ab4d9,manage-the-lock-status-for-site-collections-in-sharepoint-server +SharePoint16ITPro,d0e68cf4-80f6-4f1f-af49-a3b9c43408ac,configure-properties-of-the-search-results-web-part-in-sharepoint-server +SharePoint16ITPro,3a080c72-df1f-43a2-8aee-a3ffd0c43ad2,plan-trusted-file-locations-in-sharepoint-server-2013 +SharePoint16ITPro,aa637ca9-d27b-463c-8691-a457e0988bf8,prepare-for-installation-of-sharepoint-server-2016 +SharePoint16ITPro,25d888b2-035a-40b4-a2b9-a496657a36e3,create-a-user-profile-service-applications-in-sharepoint-server +SharePoint16ITPro,ccd99adc-b00a-4a0b-8609-a51ebe19c982,enable-previews-of-on-premises-search-results-in-cloud-hybrid-search +SharePoint16ITPro,ec012300-2ebe-48f0-b110-a5bc9166e353,overview-of-business-connectivity-services-security-tasks-in-sharepoint-server +SharePoint16ITPro,d454aed4-4e26-4ef1-9f72-a605af6ed2cd,video-demo-of-zero-downtime-patching-in-sharepoint-server-2016 +SharePoint16ITPro,7269169c-6aa2-46b0-b99f-a6cfbcd08c78,video-how-to-enable-remote-windows-powershell-to-use-with-sharepoint-server +SharePoint16ITPro,3cfb2148-9d1a-4022-a55a-a6d2963bef0e,add-edit-or-delete-custom-properties-in-sharepoint-server-user-profiles +SharePoint16ITPro,26c07867-0150-463d-b21a-a6d42aecf05a,install-or-uninstall-language-packs-for-sharepoint-server-2016 +SharePoint16ITPro,6d871772-b90b-4e48-9122-a6d9a1122b8d,plan-visio-services-security-in-sharepoint-server +SharePoint16ITPro,5c9d5c10-a7a8-43d1-ac36-a6f50f2d0cd1,plan-email-integration-for-a-sharepoint-server-2016-farm +SharePoint16ITPro,020f3595-b1bb-4def-9614-a7819b84b936,upgrade-site-collections-to-sharepoint-server-2016 +SharePoint16ITPro,6ab8a28b-fa2f-4530-8b55-a7f663bf15ea,understanding-workflow-in-sharepoint-server-2016 +SharePoint16ITPro,e1fb66ca-d0ee-4935-b8dc-a87abf98e216,manage-excel-services-data-model-settings-sharepoint-server-2013 +SharePoint16ITPro,f37b3b61-2b26-4635-a04a-a8a744e8c3ef,video-series-install-and-configure-workflow-in-sharepoint-server-2013 +SharePoint16ITPro,c16d9881-f356-45ba-b928-a8f6858840a6,test-lab-guide-demonstrate-profile-synchronization-for-sharepoint-server-2013 +SharePoint16ITPro,8de5bc7f-026c-4685-a6f6-a8fd814c2b70,infopath-forms-services-forms-cannot-be-filled-out-in-a-web-browser-because-no-s +SharePoint16ITPro,53598509-9821-4c0b-9ab4-a9e594ac8fec,configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh +SharePoint16ITPro,b95b4ecc-f31b-4bbc-9b3d-a9f111dac8a1,configure-web-application-proxy-for-a-hybrid-environment +SharePoint16ITPro,5ed9fe7c-48c5-4511-aab4-aa58a440954d,built-in-accounts-are-used-as-application-pool-or-service-identities-sharepoint +SharePoint16ITPro,37277bfe-4e25-4050-9f99-aac16b47d079,view-all-site-collections-in-sharepoint-server +SharePoint16ITPro,ae1e3447-46e2-45f9-852a-ab39f23345d4,view-diagnostic-logs-in-sharepoint-server +SharePoint16ITPro,4fceb168-753a-4227-8a23-ab415f9abce7,assign-or-remove-administrators-of-service-applications-in-sharepoint-server +SharePoint16ITPro,f3fae102-5b20-4c9f-9707-ab76c68be937,plan-ways-to-convert-active-documents-to-records-in-sharepoint-server-2013 +SharePoint16ITPro,d8635abe-1b1b-42db-95ff-ab9341d957e2,plan-digital-asset-libraries-in-sharepoint-server-2013 +SharePoint16ITPro,31b74292-9333-455d-8c52-aba97bbfc0e6,overview-of-analytics-processing-in-sharepoint-server +SharePoint16ITPro,29c0bc76-d835-401b-a2fb-abb069e84125,configure-the-secure-store-service-in-sharepoint-server +SharePoint16ITPro,70e043ef-8908-436e-92bf-abbcd89874f7,set-up-sharepoint-services-for-hybrid-environments +SharePoint16ITPro,f436a248-984f-40bd-bbe2-ac4dd1e1f961,manage-databases-in-sharepoint-server +SharePoint16ITPro,c12cdce4-1a73-4602-96ff-ac50da27f614,overview-of-search-architecture-in-sharepoint-server +SharePoint16ITPro,3a25437a-e994-42c7-b4df-ac9fa29f38f5,configure-backup-and-restore-permissions-in-sharepoint-server +SharePoint16ITPro,6c4a140e-aac4-43ca-a8e9-ad181beb7073,technical-reference-for-sharepoint-server +SharePoint16ITPro,a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a,back-up-farm-configurations-in-sharepoint-server +SharePoint16ITPro,7d88430f-2f0f-4c83-863b-ad840bdbf696,add-or-remove-a-file-type-from-the-search-index-in-sharepoint-server +SharePoint16ITPro,55b99d80-3fa7-49f0-bdf4-adb5aa959019,account-permissions-and-security-settings-in-sharepoint-server-2016 +SharePoint16ITPro,371181ec-d27c-4899-9d3c-ae0ffefa1cc0,manage-excel-services-user-defined-function-assemblies-sharepoint-server-2013 +SharePoint16ITPro,3e9dcd50-53e6-4471-a969-aeb4d079dfa3,restore-service-applications-in-sharepoint-server +SharePoint16ITPro,f6663d4b-30e5-48d6-9bbc-aed8db1aae24,overview-of-my-sites-in-sharepoint-server +SharePoint16ITPro,e09599f5-f900-48b3-9680-af1f1de3f65a,plan-browser-support-in-sharepoint-2013 +SharePoint16ITPro,590a94c3-11f2-41b9-962d-b10d3e1f328e,overview-of-mobile-devices-and-sharepoint-server-2013 +SharePoint16ITPro,fee4c4d8-a7f2-4392-99ce-b122e918c081,microsoft-identity-manager-in-sharepoint-server-2016 +SharePoint16ITPro,086fd0f5-8580-414f-a088-b1238ad02014,verify-each-user-profile-service-application-has-an-associated-search-service-co +SharePoint16ITPro,478be4b7-1480-4f97-87c5-b18cd2436bce,configure-cache-settings-for-a-web-application-in-sharepoint-server +SharePoint16ITPro,0f95a1e6-7044-487e-8681-b1d717caabb3,define-managed-paths-in-sharepoint-server +SharePoint16ITPro,4edf74cf-8808-4277-ba10-b1f925d7c440,plan-for-my-sites-in-sharepoint-server +SharePoint16ITPro,3fca2556-ebca-4395-8f66-b3a645c05878,plan-for-custom-claims-providers-for-people-picker-in-sharepoint-2013 +SharePoint16ITPro,9aafbcc8-c1f0-4037-a249-b465d301bd43,plan-for-high-availability-and-disaster-recovery-for-sharepoint-server +SharePoint16ITPro,f91de311-e531-4a15-bcc4-b4af01774e0b,one-or-more-services-have-started-or-stopped-unexpectedly-sharepoint-server-2016 +SharePoint16ITPro,c5c6fd31-d747-49c0-9784-b4f29bd82809,view-data-in-the-logging-database-in-sharepoint-server-2016 +SharePoint16ITPro,6bf64b3d-edf0-4d2a-a1f5-b53318a24a1a,configure-authoritative-pages-in-sharepoint-server +SharePoint16ITPro,0fe9d4a1-faf9-4941-a45a-b54f47a5dea5,mobile-security-and-authentication-in-sharepoint-2013 +SharePoint16ITPro,9d2d8945-5a6f-45dc-91bd-b588720ba745,web-applications-using-claims-authentication-require-an-update-sharepoint-server +SharePoint16ITPro,f3ccc8bd-922e-49f6-9929-b5b8a6982d76,configure-outgoing-email-for-a-sharepoint-server-farm +SharePoint16ITPro,e6600dfa-7f96-4c6f-a1be-b7ad348ac30f,configure-my-sites-in-sharepoint-server +SharePoint16ITPro,e91d6339-549c-4620-a559-b7c3c7ecba5d,administer-business-intelligence-in-sharepoint-server +SharePoint16ITPro,c78266d8-33de-4edc-94ea-b8110ac8db81,one-or-more-categories-are-configured-with-verbose-trace-logging-sharepoint-serv +SharePoint16ITPro,9061f245-7b75-4211-af5f-b87ec09b5c82,restore-user-profile-service-applications-in-sharepoint-server +SharePoint16ITPro,48d39f84-9698-4249-b7e0-b885c462622e,delete-items-from-the-search-index-or-from-search-results-in-sharepoint-server +SharePoint16ITPro,e283aaec-e962-46b4-92e4-b8a825521641,overview-of-profile-synchronization-in-sharepoint-server-2016 +SharePoint16ITPro,684173bb-e90a-4eb7-b268-b8d7458bc802,updated-product-servicing-policy-for-sharepoint-2013 +SharePoint16ITPro,53038195-cb59-4779-9bdb-ba0b1cad6f07,schedule-profile-synchronization-in-sharepoint-server +SharePoint16ITPro,faab1eb4-5848-4970-b13f-ba6df14272fe,configure-diagnostic-logging-in-sharepoint-server +SharePoint16ITPro,4e26b32c-f5f8-40b7-a240-bad147c33402,manage-excel-services-trusted-data-connection-libraries-sharepoint-server-2013 +SharePoint16ITPro,a19e8cb8-4b41-492b-b33c-bc490f911f1d,secure-store-for-business-intelligence-service-applications +SharePoint16ITPro,46e0f7e7-cd69-41a5-9988-bd0e7db564d9,publish-service-applications-in-sharepoint-server +SharePoint16ITPro,621619c8-105a-4056-917e-bd771d113a95,overview-of-performancepoint-kpi-details-reports +SharePoint16ITPro,c2f1d2a8-dc6a-471c-b373-be420b460306,web-config-files-are-not-identical-on-all-machines-in-the-farm-sharepoint-server +SharePoint16ITPro,2ddb9cfe-38fc-477c-88d1-beb190e36ab0,automatic-update-setting-inconsistent-across-farm-servers-sharepoint-server-2016 +SharePoint16ITPro,6de4e8e0-5d27-4b1b-a87f-bebd8b9d6e77,upgrade-service-applications-to-sharepoint-server-2016 +SharePoint16ITPro,bfa2f924-f411-4b13-8c24-bf251d7e4c91,attach-or-detach-content-databases-in-sharepoint-server +SharePoint16ITPro,6d8a9d37-d400-4d7c-b4f1-bf3c5643c98c,exchange-trust-certificates-between-farms-in-sharepoint-server +SharePoint16ITPro,0f33d9cc-7b26-4418-b901-bf773abaf574,access-services-in-sharepoint-server-2016-knowledge-articles +SharePoint16ITPro,354706a8-a7f0-4e83-b2b0-bfccd1753c2e,configure-email-integration-for-a-sharepoint-server-farm +SharePoint16ITPro,39f9eaa2-867e-47b9-b7ea-bff74f9f8c6a,operations-for-sharepoint-server +SharePoint16ITPro,e580fcae-b768-4b81-afda-c037fbd7bd6d,plan-for-managed-metadata-in-sharepoint-server +SharePoint16ITPro,c3802be8-9c57-4b25-9666-c07b485aabf0,use-analysis-services-effectiveusername-in-sharepoint-server +SharePoint16ITPro,a2609bd3-928a-479a-9c8d-c0a751d76fcf,monitor-cache-performance-in-sharepoint-server-2016 +SharePoint16ITPro,5dee7e15-3b81-40c5-978e-c10357bb7a3d,use-secure-store-with-sql-server-authentication +SharePoint16ITPro,bf9068c7-9187-49bb-9946-c298389bf4b0,performancepoint-services-application-settings +SharePoint16ITPro,405d8d1a-2952-4f51-9527-c2c305b76a29,configure-hybrid-business-connectivity-servicesroadmap +SharePoint16ITPro,77722a66-8340-4ae3-ad15-c3610f398da0,manage-rbs-in-sharepoint-server +SharePoint16ITPro,1350e659-04ba-423e-a1b3-c41563073473,plan-for-ediscovery-in-sharepoint-server +SharePoint16ITPro,18fedf59-f293-4c15-953e-c42ec66fa13f,configure-sql-server-alwayson-availability-groups-for-sharepoint-server-2016 +SharePoint16ITPro,aecba264-abdb-4515-8b4f-c451cc0c0107,test-lab-guide-demonstrate-social-features-for-sharepoint-server-2013 +SharePoint16ITPro,d0a50e40-5322-4f7a-a3a4-c4660c879666,upgrade-content-databases-to-sharepoint-server-2016 +SharePoint16ITPro,f255d39a-8231-42e7-957d-c4855b9ab529,configure-business-connectivity-services-solutions-for-sharepoint-server +SharePoint16ITPro,809fe3d9-6121-4e2e-8556-c48a39756365,overview-of-document-management-in-sharepoint-2013 +SharePoint16ITPro,a88d3f72-7ac3-4f08-b302-c4ca0a796268,hardware-and-software-requirements-for-sharepoint-2013 +SharePoint16ITPro,723dba65-4887-4ef2-9971-c51c8669cbac,choose-a-disaster-recovery-strategy-for-sharepoint-server +SharePoint16ITPro,cdd1d3d6-034e-458f-9324-c51d90fa9273,business-intelligence-capabilities-in-excel-service-sharepoint-server-2013 +SharePoint16ITPro,63f233ef-8a72-449e-8211-c66fea977b6e,verify-each-user-profile-service-application-has-an-associated-managed-metadata +SharePoint16ITPro,6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe,software-boundaries-and-limits-for-sharepoint-server-2016 +SharePoint16ITPro,0ffd36db-3f34-4f9f-b3fe-c8bea09a9d8f,searchone-or-more-crawl-databases-may-have-fragmented-indices-sharepoint-server +SharePoint16ITPro,e8c0fccd-8364-4352-8778-c9c46a668b70,plan-search-in-sharepoint-server +SharePoint16ITPro,ea1134be-89a1-49ca-9c3b-ca8bc70a3242,view-reports-and-logs-in-sharepoint-server-2016 +SharePoint16ITPro,3ede6cef-193d-4c25-8d41-cacabab95ac9,install-prerequisites-for-sharepoint-server-from-a-network-share +SharePoint16ITPro,46aecccb-6196-48b4-a889-cbd408354d56,configure-forefront-tmg-for-a-hybrid-environment +SharePoint16ITPro,6cdcb2e3-8a77-4219-ba08-cc1d0ae8944f,start-profile-synchronization-manually-in-sharepoint-server +SharePoint16ITPro,6951d670-e2a8-4a7e-b3ea-ccc9c00a0ffc,plan-server-to-server-authentication +SharePoint16ITPro,60a1110d-27dc-45d0-86e2-cddc72d072b2,plan-to-transform-queries-and-order-results-in-sharepoint-server +SharePoint16ITPro,8386d324-816a-42ee-aff2-ce135ca2f241,all-state-service-databases-are-paused-for-a-state-service-application-sharepoin +SharePoint16ITPro,c8a62094-b951-47d5-b048-ce6bc5b518be,one-of-the-cache-hosts-in-the-cluster-is-down-sharepoint-server-2016 +SharePoint16ITPro,90d8dee0-5c31-4c9b-93d5-cf09cb2320aa,overview-of-performancepoint-reports-and-scorecards +SharePoint16ITPro,091165d1-76c4-4c15-ae75-cf338b573b13,deactivated-controls-in-sharepoint-designer-2013 +SharePoint16ITPro,9983054b-ed90-491a-ac1d-cf95204f0931,expired-sessions-are-not-being-deleted-from-the-asp-net-session-state-database-s +SharePoint16ITPro,559dddb1-95c9-4242-99ca-cf9cf1cbd0c3,enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2016 +SharePoint16ITPro,94a0dfe4-66e8-4503-9cc6-cfb438f4fbc8,supported-high-availability-and-disaster-recovery-options-for-sharepoint-databas +SharePoint16ITPro,cb57d4f7-8353-420b-8a10-d05c9bdf1b56,plan-document-management-in-sharepoint-2013 +SharePoint16ITPro,918a570e-ce86-4ff7-857f-d08dbb35d08d,data-authentication-for-visio-services-in-sharepoint-server +SharePoint16ITPro,52966fa3-1654-41b2-aea5-d1d5d007534e,disaster-recovery-best-practices-for-sharepoint-server-and-access-services +SharePoint16ITPro,4de99997-edda-4414-85f2-d210ea717d1a,plan-for-internet-intranet-and-extranet-publishing-sites-in-sharepoint-server +SharePoint16ITPro,d7d2dff9-c7a9-402b-958a-d233cbacab8f,backup-and-restore-best-practices-in-sharepoint-server +SharePoint16ITPro,a3b78815-c1a0-47e0-97a3-d255f9efc96d,overview-of-sql-server-in-a-sharepoint-server-2016-environment +SharePoint16ITPro,e0ad657d-f5d1-4cae-bb0d-d2b619eed261,back-up-web-applications-in-sharepoint-server +SharePoint16ITPro,4cf30b48-f908-4774-920c-d2f2916f2c1b,install-and-configure-rbs-with-filestream-in-a-sharepoint-server-farm +SharePoint16ITPro,5f80cdb8-d6d1-45f0-9710-d30544fcb3e6,sharepoint-intranet-farm-in-azure-phase-2-configure-domain-controllers +SharePoint16ITPro,9cf64bff-f52b-46c9-bf25-d38d6b15e25d,business-connectivity-service +SharePoint16ITPro,9188225f-8281-4b4a-8414-d39ffac9d371,share-a-sql-server-data-connection-using-excel-services-sharepoint-server-2013 +SharePoint16ITPro,0d32d946-52d0-4913-bfdb-d3c1193cfc4a,add-yammer-to-the-navigation-bar-for-sharepoint-2013 +SharePoint16ITPro,b3d2f46d-783c-4f81-9c0a-d41a3486917e,change-site-collection-administrators-in-sharepoint-server +SharePoint16ITPro,a590d614-7488-4b03-8c8f-d45dd48ca726,overview-of-minrole-server-roles-in-sharepoint-server-2016 +SharePoint16ITPro,99684f0b-f617-4c10-8420-d4d0adea3687,create-the-sharepoint-server-2016-farm-for-a-database-attach-upgrade +SharePoint16ITPro,7942ef65-c309-402d-b4bb-d54e686fc5d9,restore-farms-in-sharepoint-server +SharePoint16ITPro,0bcc4cd8-68cf-45b5-a880-d56fdaabe284,performancepoint-services-in-sharepoint-server-2016-overview +SharePoint16ITPro,a29d4cc4-7944-4c3e-94ea-d681f432f07b,plan-for-app-authentication-in-sharepoint-server +SharePoint16ITPro,47db8aed-7e2b-4ccb-b248-d71df3bffa99,install-sharepoint-server-2016 +SharePoint16ITPro,93327a06-ed2c-43f2-a40a-d7257f61f915,copy-databases-to-the-new-farm-for-upgrade-to-sharepoint-server-2016 +SharePoint16ITPro,70d6f3af-2ad4-497d-a449-d75bacfd8aea,the-application-discovery-and-load-balancer-service-is-not-running-in-this-farm +SharePoint16ITPro,0810018d-188b-4d42-b908-d794faeacd0a,configure-and-deploy-web-parts-in-sharepoint-server +SharePoint16ITPro,9cd888dc-9104-422e-8d8a-d795f0b1c0d0,configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o +SharePoint16ITPro,7c75dc80-6910-4c10-a9a0-d821bedd602d,it-governance-in-sharepoint +SharePoint16ITPro,043481c0-f467-44ed-9772-d822eb314a81,databases-used-by-sharepoint-have-fragmented-indices-sharepoint-server-2016 +SharePoint16ITPro,eddba98c-dec8-4fc8-823d-d908bdf0bc83,configure-office-365-for-sharepoint-hybrid +SharePoint16ITPro,d7abd498-7bc4-44fe-a086-d9b1c5a340d2,plan-document-libraries-in-sharepoint-2013 +SharePoint16ITPro,04d1607a-21a9-4b77-929a-d9d7ffad51f8,convert-forefront-identity-manager-fim-xml-files-to-microsoft-identity-managemen +SharePoint16ITPro,17d06bdf-69e1-4a85-86f9-da78a3c79952,the-state-service-delete-expired-sessions-timer-job-is-not-enabled-sharepoint-se +SharePoint16ITPro,2689bb6a-fd05-4273-87eb-daac5b2722f3,verify-each-user-profile-service-application-has-a-my-site-host-configured-share +SharePoint16ITPro,f1bb8664-85dd-49bc-b162-daebf657377e,manage-continuous-crawls-in-sharepoint-server +SharePoint16ITPro,f484f5f2-35bb-4d70-bf56-dd1c4c287c72,deploy-software-updates-for-sharepoint-server-2016 +SharePoint16ITPro,6824b3bf-9046-4d43-b266-de463d0007e5,software-requirements-for-business-intelligence-in-sharepoint-server +SharePoint16ITPro,1ad49d4e-598d-446c-aabd-de4a8f6ad391,web-applications-management-in-sharepoint-server +SharePoint16ITPro,ff6c5b8c-59bd-4079-8f0b-de4f8b4e0a86,plan-browser-support-in-sharepoint-server-2016 +SharePoint16ITPro,5cdce2aa-fa6e-4888-a34f-de61713f5096,configure-ediscovery-in-sharepoint-server +SharePoint16ITPro,8b91dc0a-c37d-4ec8-aa75-deb3f268fb97,run-a-farm-that-uses-read-only-databases-in-sharepoint-server +SharePoint16ITPro,4cbe141a-095f-4c09-82f4-dec8af16c590,software-updates-overview-for-sharepoint-server-2016 +SharePoint16ITPro,0d74b6bb-0355-4d18-b5fb-def0aca566d9,manage-excel-services-global-settings-sharepoint-server-2013 +SharePoint16ITPro,8fa6b865-c11a-4bc3-b3da-df492ffadf38,plan-for-sharepoint-hybrid-picker +SharePoint16ITPro,d14f09d4-6540-42dc-b6ff-df6487705fa7,plan-ediscovery-in-sharepoint-server +SharePoint16ITPro,ebf72243-3d0c-43e4-8538-df8e4f4b9c5c,social-scenarios-with-yammer-and-sharepoint-server-2013 +SharePoint16ITPro,f1dfdac2-81ad-452f-b5b6-df9e5a8e976e,configure-hybrid-onedrive-for-business +SharePoint16ITPro,5978d831-4070-4b03-a81c-dfce3b7d594e,configure-time-out-values-for-crawler-connections-in-sharepoint-server +SharePoint16ITPro,3adafdd2-f276-4a9d-8a74-e06b8916bbc2,monitor-apps-for-sharepoint-for-sharepoint-server +SharePoint16ITPro,9ccce076-f47b-44b8-9ec3-e0dcd46e9985,application-pools-recycle-when-memory-limits-are-exceeded-sharepoint-server-2016 +SharePoint16ITPro,f6accc60-23b8-4242-b12d-e118270251cf,overview-of-co-authoring-in-sharepoint-2013 +SharePoint16ITPro,982d3ab2-d1a6-4625-b4c6-e12a1f4532d5,people-search-relevance-is-not-optimized-when-the-active-directory-has-errors-in +SharePoint16ITPro,3ee1591b-6908-499f-9a39-e19bcfbec8a4,overview-of-site-policies-in-sharepoint-server +SharePoint16ITPro,4905c929-464a-4051-a32f-e1d2b3f3be8a,$$sharepoint16itpro +SharePoint16ITPro,79428586-0a1c-4fd8-ae49-e1e76eb022e1,configure-properties-of-the-search-navigation-web-part-in-sharepoint-server +SharePoint16ITPro,7f65b235-8e0d-48d8-acca-e2e0295e6522,alternate-access-urls-have-not-been-configured-sharepoint-server-2016 +SharePoint16ITPro,f0565d7f-3efd-46c5-9a73-e307bc2df669,set-up-search-of-onedrive-for-business-in-office-365-from-sharepoint-server +SharePoint16ITPro,58a2b307-de20-4fa8-868c-e33abc9b7901,services-and-application-planning-in-sharepoint-server-2016 +SharePoint16ITPro,be4e1054-ada6-4eea-a92d-e35d1da61eb9,configure-availability-and-recovery-solutions-for-sharepoint-server-2016 +SharePoint16ITPro,71abd06e-6730-442e-b2c1-e3ba9c04d497,backup-and-restore-in-sharepoint-server +SharePoint16ITPro,fae8ce7b-7c93-4cce-8a44-e3cf2f9f7b71,business-intelligence-in-sharepoint-server-overview +SharePoint16ITPro,45b39899-1686-43e5-9073-e51d2979ba9b,this-distributed-cache-host-may-cause-cache-reliability-problems-sharepoint-serv +SharePoint16ITPro,89377b22-b1de-4f11-9a16-e54783c046fc,productpatch-installation-or-server-upgrade-required-sharepoint-server-2016 +SharePoint16ITPro,79240081-1495-4db7-b0c5-e5e4d4e59c37,plan-user-profiles-and-identities +SharePoint16ITPro,6e743c5b-b70c-4e86-ae31-e5ffcc0c099a,distributed-cache-service-is-not-enabled-in-this-deployment-sharepoint-server-20 +SharePoint16ITPro,237d399e-b50b-42e6-90ff-e659a94d8099,restore-secure-store-service-applications-in-sharepoint-server +SharePoint16ITPro,c75f3390-283f-4380-b740-e672ea8b933d,default-connectors-in-sharepoint-server +SharePoint16ITPro,58901f1a-dbc9-46ca-8b51-e683ea5f2ce3,integrate-a-single-yammer-network-into-sharepoint-server-2013 +SharePoint16ITPro,144baa85-cbd8-45d6-9141-e6e688cac210,create-an-excel-services-dashboard-using-sql-server-analysis-services-data +SharePoint16ITPro,bdb3b575-7c20-490d-9a28-e7108edabad5,cached-objects-have-been-evicted-sharepoint-server-2016 +SharePoint16ITPro,23829b00-db4c-4400-b236-e86ea60fa193,server-role-configuration-isn-t-correct-sharepoint-server-2016 +SharePoint16ITPro,7705a9ef-cc59-4b08-990c-e88014b4ac03,plan-visio-services-deployment-in-sharepoint-server +SharePoint16ITPro,4692ebba-90eb-4d72-ac12-e90c4d4ee7ae,deploy-a-business-connectivity-services-on-premises-solution-in-sharepoint-serve +SharePoint16ITPro,eb5d2d46-8bf6-43d7-add0-e9d61290a4d0,the-settings-for-the-machine-translation-service-are-not-within-the-recommended +SharePoint16ITPro,47a18181-cf59-4b7b-9b00-eae7cb11f5e9,databases-require-upgrade-or-not-supported-sharepoint-server-2016 +SharePoint16ITPro,9528dfeb-3f44-4c76-8d07-eb916e04b674,plan-for-mobile-views-in-sharepoint-server-2013 +SharePoint16ITPro,91274b73-f7be-4066-a4ab-ec30af30016e,configure-connectivity-from-office-365-to-sharepoint-server +SharePoint16ITPro,c20ca79f-2086-4a32-974a-ed2a720d57fe,overview-of-profile-synchronization-in-sharepoint-server-2013 +SharePoint16ITPro,dca8b241-85f9-486c-97eb-ed9ef23622b8,configure-the-maximum-number-of-co-authoring-authors-in-sharepoint-2013 +SharePoint16ITPro,43e52f2f-2586-451d-814d-edf43f3459ab,hardware-and-software-requirements-for-sharepoint-hybrid +SharePoint16ITPro,5417b04a-c7d9-4e9a-86fb-ee1d1c63508b,attach-and-restore-read-only-content-databases-in-sharepoint-server +SharePoint16ITPro,8daa31a5-0f8c-4bd6-84c9-ee1f5074594d,back-up-farms-in-sharepoint-server +SharePoint16ITPro,3a832d60-f14f-4663-93bd-f006e6148c02,using-administrative-actions-logging-in-sharepoint-server-2016 +SharePoint16ITPro,3e3b8737-c6a3-4e2c-a35f-f0095d952b78,sharepoint-server-2016 +SharePoint16ITPro,445bce79-f6d6-4ab6-9d50-f0672cd093f4,configure-hybrid-federated-search-from-sharepoint-server-to-sharepoint-onlineroa +SharePoint16ITPro,4d94f491-4f01-4ab8-8c4b-f086c2ccfb89,manage-user-profile-synchronization-in-sharepoint-server +SharePoint16ITPro,cba65279-cba5-46cb-aea1-f095365ed83a,manage-permission-policies-for-a-web-application-in-sharepoint-server +SharePoint16ITPro,06765032-fedb-4b73-a019-f096b48cd2a8,initial-deployment-administrative-and-service-accounts-in-sharepoint-server +SharePoint16ITPro,ff364add-e18d-4d1c-824f-f0ea549fe904,plan-for-business-connectivity-services-in-sharepoint-server +SharePoint16ITPro,3e61c238-cc09-4369-b8d3-f1150c1ae89b,plan-user-profiles-in-sharepoint-server +SharePoint16ITPro,fd6a6c07-1979-4254-873c-f146fb630de5,plan-for-caching-and-performance-in-sharepoint-server +SharePoint16ITPro,bf8717c2-463d-4e8d-acaf-f186b5907df1,people-picker-and-claims-providers-overview-sharepoint-2013 +SharePoint16ITPro,1d93093a-4da3-40c0-b0fd-f2567a32d2e9,use-performancepoint-services-with-secure-store-service-in-sharepoint-server +SharePoint16ITPro,651dba4d-8751-4bd8-9492-f2842b2e1177,scale-search-for-internet-sites-in-sharepoint-server +SharePoint16ITPro,a61b531f-218e-4edf-ab90-f2f30f490900,configure-enterprise-search-in-sharepoint-server-2016 +SharePoint16ITPro,76e31e76-afb3-4f2f-b3cb-f3b42886fb6e,manage-search-relevance-in-sharepoint-server +SharePoint16ITPro,f7b617fc-cc45-41bf-bb71-f3d49ed4a59c,plan-self-service-site-creation-in-sharepoint-server +SharePoint16ITPro,6ed5b73c-6403-46ea-9d56-f42d972e7748,drives-are-running-out-of-free-space-sharepoint-server-2016 +SharePoint16ITPro,1c030561-e15f-43a0-9ef2-f43e67fb4c67,plan-records-management-in-sharepoint-server-2013 +SharePoint16ITPro,a2420e0a-bc3d-4a07-b7b9-f44c7a74ade1,manage-the-search-topology-in-sharepoint-server +SharePoint16ITPro,5f0f9910-d851-4ffa-832b-f47558e4758c,accounts-used-by-application-pools-or-service-identities-are-in-the-local-machin +SharePoint16ITPro,8a911115-de8a-4cf3-9701-f5ba78fa8bfc,install-and-configure-sharepoint-server-2016 +SharePoint16ITPro,396c85d9-4b86-484e-9cc5-f6c4d725c578,upgrade-to-sharepoint-server-2016 +SharePoint16ITPro,e4aafc9c-f7d6-4ffd-b4e3-f74d1cf502ee,solutions-for-the-real-world-in-sharepoint-server +SharePoint16ITPro,fbfd98f1-403f-4648-9850-f7bd37f2255e,start-pause-resume-or-stop-a-crawl-in-sharepoint-server +SharePoint16ITPro,1cd060e0-1eb6-424c-8ade-f8d39cd20d1d,view-timer-job-status-in-sharepoint-server-2016 +SharePoint16ITPro,f6d49e94-ad29-456d-8cd9-f940154d5a0e,configure-hybrid-federated-search-from-sharepoint-online-to-sharepoint-serverroa +SharePoint16ITPro,db4bea29-65fb-4c48-828a-f96502fed697,data-sources-supported-in-excel-services-sharepoint-server-2013 +SharePoint16ITPro,86e4a832-ef3a-46cf-9b60-f9796292bf3e,overview-of-the-search-schema-in-sharepoint-server +SharePoint16ITPro,ef9a10b9-2283-431e-9dc2-f98a78a33b39,performancepoint-services-administration +SharePoint16ITPro,5e7be5ff-5216-406b-9bfe-f9ff1f9651aa,more-cache-hosts-are-running-in-this-deployment-than-are-registered-with-sharepo +SharePoint16ITPro,bcbddee7-1c77-4788-9a32-fb585c48ee37,role-conversion-using-minrole-in-sharepoint-server-2016 +SharePoint16ITPro,197ce911-c4f6-40a3-84c1-fb5999623b51,manage-search-components-in-sharepoint-server +SharePoint16ITPro,a96cfa2d-87f8-4991-801c-fd5482d49d0b,administer-excel-services-in-sharepoint-server-2013 +SharePoint16ITPro,062b6ff7-a4ee-408f-811e-fdba45ca3c08,the-visio-graphics-service-has-a-minimum-cache-age-setting-that-will-adversely-i +SharePoint16ITPro,e81557fb-5046-4a67-8ec8-fdfda648af68,new-and-improved-features-in-sharepoint-server-2016 +SharePoint16ITPro,0317c126-78ed-47e0-9109-fe143ddb0259,migrate-content-into-or-out-of-rbs-in-sharepoint-server +SharePoint16ITPro,76a4e2e3-7e10-41da-b3a8-fe62e193dc24,one-or-more-app-domains-for-web-applications-aren-t-configured-correctly-sharepo +SharePoint16ITPro,18b1dbaf-d8e1-416b-b2fb-fe6cd0a369f1,manage-a-paused-search-service-application-in-sharepoint-server +SharePoint16ITPro,c1f83b4f-a507-42f7-bd82-fed5404ed1ad,deciding-to-use-rbs-in-sharepoint-server diff --git a/SharePoint/TOC.md b/SharePoint/TOC.md index 06913f7aef..2dcc770ba4 100644 --- a/SharePoint/TOC.md +++ b/SharePoint/TOC.md @@ -1 +1,633 @@ -# [Index](index.md) \ No newline at end of file +# SharePoint Test Table of Contents +## [A State Service Application has no database defined (SharePoint Server 2016)](pr/) +## [About service applications and services in SharePoint Server](pr/) +## [Access Services in SharePoint Server 2016 knowledge articles](pr/) +## [Accessibility guidelines in SharePoint Server 2016](pr/) +## [Account permissions and security settings in SharePoint Server 2016](pr/) +## [Accounts needed for hybrid configuration and testing](pr/) +## [Accounts used by application pools or service identities are in the local machine Administrators group (SharePoint Server 2016)](pr/) +## [Add apps for SharePoint to a SharePoint site](pr/) +## [Add content databases in SharePoint Server](pr/) +## [Add, edit, or delete a content source in SharePoint Server](pr/) +## [Add, edit, or delete custom properties in SharePoint Server user profiles](pr/) +## [Add or remove a file type from the search index in SharePoint Server](pr/) +## [Add or remove service application connections from a web application in SharePoint Server](pr/) +## [Add SharePoint server to a farm in SharePoint Server 2016](pr/) +## [Add the Yammer Embed widget to a SharePoint page](pr/) +## [Add Yammer to the navigation bar for SharePoint 2013](pr/) +## [Administer business intelligence in SharePoint Server](pr/) +## [Administer Excel Services in SharePoint Server 2013](pr/) +## [Administer search in SharePoint Server](pr/) +## [Administer sites and site collections in SharePoint Server](pr/) +## [Administer the User Profile service in SharePoint Server](pr/) +## [All State Service databases are paused for a State Service Application (SharePoint Server 2016)](pr/) +## [Alternate access URLs have not been configured (SharePoint Server 2016)](pr/) +## [Application management and governance in SharePoint](pr/) +## [Application pools recycle when memory limits are exceeded (SharePoint Server 2016)](pr/) +## [Assign or remove administrators of service applications in SharePoint Server](pr/) +## [Attach and restore read-only content databases in SharePoint Server](pr/) +## [Attach or detach content databases in SharePoint Server](pr/) +## [Authentication for mobile devices in SharePoint 2013](pr/) +## [Authentication overview for SharePoint Server](pr/) +## [Automatic Update setting inconsistent across farm servers (SharePoint Server 2016)](pr/) +## [Back up apps for SharePoint in SharePoint Server](pr/) +## [Back up content databases in SharePoint Server](pr/) +## [Back up customizations in SharePoint Server](pr/) +## [Back up databases to snapshots in SharePoint Server](pr/) +## [Back up farm configurations in SharePoint Server](pr/) +## [Back up farms in SharePoint Server](pr/) +## [Back up Search service applications in SharePoint Server](pr/) +## [Back up service applications in SharePoint Server](pr/) +## [Back up site collections in SharePoint Server](pr/) +## [Back up the Secure Store Service in SharePoint Server](pr/) +## [Back up User Profile service applications in SharePoint Server](pr/) +## [Back up web applications in SharePoint Server](pr/) +## [Backup and restore best practices in SharePoint Server](pr/) +## [Backup and restore in SharePoint Server](pr/) +## [Backup solutions in SharePoint Server](pr/) +## [Best practices for crawling in SharePoint Server](pr/) +## [Best practices for organizing content for search in SharePoint Server](pr/) +## [Best practices for SQL Server in a SharePoint Server farm](pr/) +## [Best practices for upgrading to SharePoint Server 2016](pr/) +## [Built-in accounts are used as application pool or service identities (SharePoint Server 2016)](pr/) +## [Business Connectivity Service](pr/) +## [Business Data Connectivity connectors are currently enabled in a partitioned environment (SharePoint Server 2016)](pr/) +## [Business intelligence capabilities in Excel Service (SharePoint Server 2013)](pr/) +## [Business intelligence in SharePoint Server overview](pr/) +## [Cache settings operations in SharePoint Server](pr/) +## [Cached objects have been evicted (SharePoint Server 2016)](pr/) +## [Capacity management and sizing overview for SharePoint Server 2013](pr/) +## [Change site collection administrators in SharePoint Server](pr/) +## [Change the default account for crawling in SharePoint Server](pr/) +## [Change the default search topology in SharePoint Server](pr/) +## [Choose a disaster recovery strategy for SharePoint Server](pr/) +## [Co-authoring administration in SharePoint 2013](pr/) +## [Configure a Business Data Connectivity service application in SharePoint Server](pr/) +## [Configure a hybrid solution for SharePoint Server](pr/) +## [Configure a reverse proxy device for SharePoint Server hybrid](pr/) +## [Configure AdventureWorks for Business Intelligence solutions](pr/) +## [Configure an environment for apps for SharePoint Server](pr/) +## [Configure and deploy web parts in SharePoint Server](pr/) +## [Configure and use the Documentum connector in SharePoint Server](pr/) +## [Configure and use the Exchange connector for SharePoint Server](pr/) +## [Configure and use the Lotus Notes connector for SharePoint Server](pr/) +## [Configure authoritative pages in SharePoint Server](pr/) +## [Configure automatic password change in SharePoint Server](pr/) +## [Configure availability and recovery solutions for SharePoint Server 2016](pr/) +## [Configure backup and restore permissions in SharePoint Server](pr/) +## [Configure Business Connectivity Services solutions for SharePoint Server](pr/) +## [Configure cache settings for a web application in SharePoint Server](pr/) +## [Configure cloud hybrid search - roadmap](pr/) +## [Configure connectivity from Office 365 to SharePoint Server](pr/) +## [Configure diagnostic logging in SharePoint Server](pr/) +## [Configure eDiscovery in SharePoint Server](pr/) +## [Configure email integration for a SharePoint Server farm](pr/) +## [Configure enterprise search in SharePoint Server 2016](pr/) +## [Configure Excel Services data refresh by using embedded data connections in SharePoint Server 2013](pr/) +## [Configure Excel Services data refresh by using external data connections in SharePoint Server 2013](pr/) +## [Configure Excel Services data refresh by using the unattended service account in SharePoint Server 2016](pr/) +## [Configure Excel Services (SharePoint Server 2013)](pr/) +## [Configure Forefront TMG for a hybrid environment](pr/) +## [Configure hybrid Business Connectivity Services - roadmap](pr/) +## [Configure hybrid federated search from SharePoint Online to SharePoint Server - roadmap](pr/) +## [Configure hybrid federated search from SharePoint Server to SharePoint Online - roadmap](pr/) +## [Configure hybrid OneDrive for Business](pr/) +## [Configure hybrid OneDrive for Business - roadmap](pr/) +## [Configure hybrid sites features - roadmap](pr/) +## [Configure incoming email for a SharePoint Server farm](pr/) +## [Configure monitoring in SharePoint Server 2016](pr/) +## [Configure My Sites and OneDrive for Business in SharePoint Server](pr/) +## [Configure My Sites in SharePoint Server](pr/) +## [Configure object cache user accounts in SharePoint Server](pr/) +## [Configure Office 365 for SharePoint hybrid](pr/) +## [Configure outgoing email for a SharePoint Server farm](pr/) +## [Configure PerformancePoint Services](pr/) +## [Configure Power Pivot for SharePoint 2013](pr/) +## [Configure profile synchronization by using SharePoint Active Directory Import in SharePoint Server 2016](pr/) +## [Configure properties of the Refinement Web Part in SharePoint Server](pr/) +## [Configure properties of the Search Box Web Part in SharePoint Server](pr/) +## [Configure properties of the Search Navigation Web Part in SharePoint Server](pr/) +## [Configure properties of the Search Results Web Part in SharePoint Server](pr/) +## [Configure proxy server settings for Search in SharePoint Server](pr/) +## [Configure result sources for search in SharePoint Server](pr/) +## [Configure scheduled data refresh for Power Pivot by using a specified account (SharePoint Server 2013)](pr/) +## [Configure scheduled data refresh for Power Pivot by using Secure Store (SharePoint Server 2013)](pr/) +## [Configure scheduled data refresh for Power Pivot by using the unattended data refresh account (SharePoint Server 2013)](pr/) +## [Configure Secure Store for use with PerformancePoint Services](pr/) +## [Configure server-to-server authentication from SharePoint Server to SharePoint Online](pr/) +## [Configure services and service applications in SharePoint Server](pr/) +## [Configure SharePoint Health Analyzer rules in SharePoint Server](pr/) +## [Configure SharePoint Health Analyzer timer jobs in SharePoint Server 2016](pr/) +## [Configure SharePoint Hybrid Auditing in SharePoint 2016 (Preview)](pr/) +## [Configure SharePoint Server 2016](pr/) +## [Configure site mailboxes in SharePoint Server](pr/) +## [Configure SQL Server AlwaysOn Availability Groups for SharePoint Server 2016](pr/) +## [Configure SQL Server security for SharePoint Server 2016](pr/) +## [Configure the co-authoring versioning period in SharePoint 2013](pr/) +## [Configure the crawler in case of SSL certificate warnings in SharePoint Server](pr/) +## [Configure the hybrid infrastructure](pr/) +## [Configure the Managed Metadata service](pr/) +## [Configure the maximum number of co-authoring authors in SharePoint 2013](pr/) +## [Configure the OneDrive for Business modern user experience](pr/) +## [Configure the Secure Store Service in SharePoint Server](pr/) +## [Configure the unattended service account for PerformancePoint Services](pr/) +## [Configure time-out values for crawler connections in SharePoint Server](pr/) +## [Configure trust for search between two SharePoint Server farms](pr/) +## [Configure usage and health data collection in SharePoint Server](pr/) +## [Configure versioning for co-authoring in SharePoint 2013](pr/) +## [Configure Visio Services data refresh in SharePoint Server 2016 by using the unattended service account](pr/) +## [Configure Visio Services data refresh in SharePoint Server by using external data connections](pr/) +## [Configure Visio Services](pr/) +## [Configure Web Application Proxy for a hybrid environment](pr/) +## [Configure workflow in SharePoint Server 2013](pr/) +## [Configure Workflow in SharePoint Server 2016](pr/) +## [Connect to service applications on remote farms in SharePoint Server](pr/) +## [Content databases contain orphaned Apps (SharePoint Server 2016)](pr/) +## [Content databases contain orphaned items (SharePoint Server 2016)](pr/) +## [Convert Forefront Identity Manager (FIM) XML files to Microsoft Identity Management (MIM) service config files for User Profile Sync](pr/) +## [Copy configuration settings between farms in SharePoint Server](pr/) +## [Copy databases to the new farm for upgrade to SharePoint Server 2016](pr/) +## [Create a file plan to manage records in SharePoint Server 2013](pr/) +## [Create a high availability architecture and strategy for SharePoint Server](pr/) +## [Create a Search Center site in SharePoint Server](pr/) +## [Create a site collection in SharePoint Server](pr/) +## [Create a User Profile service applications in SharePoint Server](pr/) +## [Create an Excel Services dashboard using a Data Model (SharePoint Server 2013)](pr/) +## [Create an Excel Services dashboard using an OData data feed](pr/) +## [Create an Excel Services dashboard using SQL Server Analysis Services data](pr/) +## [Create and configure a Search service application in SharePoint Server 2016](pr/) +## [Create and deploy a thesaurus in SharePoint Server](pr/) +## [Create and deploy custom entity extractors in SharePoint Server](pr/) +## [Create, edit, and delete quota templates in SharePoint Server](pr/) +## [Create the SharePoint Server 2016 farm for a database attach upgrade](pr/) +## [Critical state of this rule indicates that the Word Automation Services is not running when it should be running (SharePoint Server 2016)](pr/) +## [Custom Tiles in SharePoint Server 2016](pr/) +## [Customize search result types in SharePoint Server](pr/) +## [Data authentication for Excel Services in SharePoint Server 2013](pr/) +## [Data authentication for Visio Services in SharePoint Server](pr/) +## [Data sources supported in Excel Services (SharePoint Server 2013)](pr/) +## [Database has large amounts of unused space (SharePoint Server 2016)](pr/) +## [Database types and descriptions in SharePoint Server](pr/) +## [Databases exist on servers running SharePoint Foundation (SharePointServer 2016)](pr/) +## [Databases require upgrade or not supported (SharePoint Server 2016)](pr/) +## [Databases running in compatibility range, upgrade recommended (SharePoint Server 2016)](pr/) +## [Databases used by SharePoint have fragmented indices (SharePoint Server 2016)](pr/) +## [Databases used by SharePoint have outdated index statistics (SharePoint Server 2016)](pr/) +## [Databases within this farm are set to read only and will fail to upgrade unless it is set to a read-write state (SharePoint Server 2016)](pr/) +## [Deactivated controls in SharePoint Designer 2013](pr/) +## [Deciding to use RBS in SharePoint Server](pr/) +## [Dedicated crawl target configuration has one or more invalid servers (SharePoint Server 2016)](pr/) +## [Default connectors in SharePoint Server](pr/) +## [Default crawled file name extensions and parsed file types in SharePoint Server](pr/) +## [Define managed paths in SharePoint Server](pr/) +## [Delegate administration of User Profile service applications or features in SharePoint Server](pr/) +## [Delete a service application in SharePoint Server](pr/) +## [Delete and restore site collections in SharePoint Server](pr/) +## [Delete items from the search index or from search results in SharePoint Server](pr/) +## [Deploy a Business Connectivity Services hybrid solution in SharePoint](pr/) +## [Deploy a Business Connectivity Services on-premises solution in SharePoint Server](pr/) +## [Deploy people search in SharePoint Server](pr/) +## [Deploy software updates for SharePoint Server 2016](pr/) +## [Deploy the Business Connectivity Services hybrid scenario as an external list](pr/) +## [Deploying SharePoint Server 2016 with SQL Server AlwaysOn Availability Groups in Azure](pr/) +## [Deployment considerations for implementing Microsoft Identity Manager with SharePoint Server 2016](pr/) +## [Description of MinRole and associated services in SharePoint Server 2016](pr/) +## [Designing a SharePoint Server 2016 farm in Azure](pr/) +## [Disable co-authoring in SharePoint 2013](pr/) +## [Disable RBS on content databases in SharePoint Server](pr/) +## [Disaster Recovery best practices for SharePoint Server and Access Services](pr/) +## [Display hybrid federated search results in SharePoint Online](pr/) +## [Display hybrid federated search results in SharePoint Server](pr/) +## [Distributed cache service is not configured on server(s)](pr/) +## [Distributed cache service is not enabled in this deployment (SharePoint Server 2016)](pr/) +## [Distributed cache service is unexpectedly configured on server(s)](pr/) +## [Document farm configuration settings in SharePoint Server](pr/) +## [Drives are at risk of running out of free space (SharePoint Server 2016)](pr/) +## [Drives are running out of free space (SharePoint Server 2016)](pr/) +## [Drives used for SQL databases are running out of free space (SharePoint Server 2016)](pr/) +## [Edit existing web parts in SharePoint Server](pr/) +## [Enable previews of on-premises search results in cloud hybrid search](pr/) +## [Enable query logging in SharePoint Server](pr/) +## [Enable search alerts in SharePoint Server](pr/) +## [Enable TLS 1.1 and TLS 1.2 support in SharePoint Server 2016](pr/) +## [Enable TLS and SSL support in SharePoint 2013](pr/) +## [Enable trusted locations for PerformancePoint Services](pr/) +## [Exchange trust certificates between farms in SharePoint Server](pr/) +## [Expired sessions are not being deleted from the ASP.NET Session State database (SharePoint Server 2016)](pr/) +## [Explore SharePoint Server](pr/) +## [Export and import customized search configuration settings in SharePoint Server](pr/) +## [Export sites, lists, or document libraries in SharePoint Server](pr/) +## [Extend claims-based web applications in SharePoint](pr/) +## [Firewall client settings on the cache host are incorrect (SharePoint Server 2016)](pr/) +## [Flush the BLOB cache in SharePoint Server](pr/) +## [Fundamental site planning in SharePoint Server 2016](pr/) +## [Get and install the Yammer app onto SharePoint Server 2013 sites](pr/) +## [Get started with upgrades to SharePoint Server 2016](pr/) +## [Getting started with SharePoint Server 2013 workflow](pr/) +## [Global architectures for SharePoint Server 2016](pr/) +## [Governance Planning in SharePoint Server 2016](pr/) +## [Hardware and software requirements for SharePoint 2013](pr/) +## [Hardware and software requirements for SharePoint hybrid](pr/) +## [Hardware and software requirements for SharePoint Server 2016](pr/) +## [Hide SharePoint Server 2013 social features](pr/) +## [High availability and disaster recovery concepts in SharePoint Server](pr/) +## [How to use the Managed Solutions Gallery](pr/) +## [Hybrid for SharePoint Server](pr/) +## [Identify users and analyze document usage in SharePoint 2013](pr/) +## [Immediate translations for the Machine Translation service are disabled (SharePoint Server 2016)](pr/) +## [Import a list or document library in SharePoint Server](pr/) +## [Welcome to OfficeDocs-SharePoint!](pr/) +## [InfoPath form library forms cannot be filled out in a Web browser (SharePoint Server 2016)](pr/) +## [InfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured (SharePoint Server 2016)](pr/) +## [Initial deployment administrative and service accounts in SharePoint Server](pr/) +## [Install a software update for SharePoint Server 2016](pr/) +## [Install and configure RBS with a 3rd party provider for SharePoint Server](pr/) +## [Install and configure RBS with FILESTREAM in a SharePoint Server farm](pr/) +## [Install and configure SharePoint Server 2016](pr/) +## [Install and configure SharePoint Server hybrid](pr/) +## [Install and configure workflow for SharePoint Server 2013](pr/) +## [Install and configure workflow for SharePoint Server 2016](pr/) +## [Install and manage apps for SharePoint Server](pr/) +## [Install Microsoft Identity Manager for User Profiles in SharePoint Server 2016](pr/) +## [Install or uninstall language packs for SharePoint Server 2016](pr/) +## [Install prerequisites for SharePoint Server from a network share](pr/) +## [Install SharePoint Server 2016 across multiple servers](pr/) +## [Install SharePoint Server 2016 on a single server with SQL Server](pr/) +## [Install SharePoint Server 2016](pr/) +## [Install Workflow Manager certificates in SharePoint Server 2013](pr/) +## [Integrate a new Yammer network into SharePoint Server 2013](pr/) +## [Integrate a single Yammer network into SharePoint Server 2013](pr/) +## [Integrate a Yammer network into SharePoint Server 2013 and Office 365](pr/) +## [Integrate a Yammer network into SharePoint Server 2013 with social features](pr/) +## [Integrate multiple Yammer networks into SharePoint Server 2013](pr/) +## [Integrate Yammer with on-premises SharePoint 2013 environments](pr/) +## [Intranet SharePoint Server 2016 in Azure dev/test environment](pr/) +## [IP support in SharePoint 2013](pr/) +## [IT governance in SharePoint](pr/) +## [Linguistic search features in SharePoint Server](pr/) +## [Machine Translation service in SharePoint Server 2016 knowledge articles](pr/) +## [Maintain RBS in SharePoint Server](pr/) +## [Maintain user profile synchronization settings in SharePoint Server 2013](pr/) +## [Manage a connection to a document center or a records center in SharePoint Server](pr/) +## [Manage a paused Search service application in SharePoint Server](pr/) +## [Manage anonymous access for a web application in SharePoint Server](pr/) +## [Manage company name extraction in SharePoint Server](pr/) +## [Manage continuous crawls in SharePoint Server](pr/) +## [Manage crawl rules in SharePoint Server](pr/) +## [Manage crawling in SharePoint Server](pr/) +## [Manage databases in SharePoint Server](pr/) +## [Manage Excel Services data model settings (SharePoint Server 2013)](pr/) +## [Manage Excel Services global settings (SharePoint Server 2013)](pr/) +## [Manage Excel Services trusted data connection libraries (SharePoint Server 2013)](pr/) +## [Manage Excel Services trusted data providers (SharePoint Server 2013)](pr/) +## [Manage Excel Services trusted file locations (SharePoint Server 2013)](pr/) +## [Manage Excel Services user defined function assemblies (SharePoint Server 2013)](pr/) +## [Manage farm-level crawl settings in SharePoint Server](pr/) +## [Manage permission policies for a web application in SharePoint Server](pr/) +## [Manage permissions for a web application in SharePoint Server](pr/) +## [Manage query rules in SharePoint Server](pr/) +## [Manage query spelling correction in SharePoint Server](pr/) +## [Manage query suggestions in SharePoint Server](pr/) +## [Manage RBS in SharePoint Server](pr/) +## [Manage search components in SharePoint Server](pr/) +## [Manage search relevance in SharePoint Server](pr/) +## [Manage service applications in SharePoint Server](pr/) +## [Manage site collections in SharePoint Server](pr/) +## [Manage sites in SharePoint Server](pr/) +## [Manage the App Catalog in SharePoint Server](pr/) +## [Manage the Distributed Cache service in SharePoint Server](pr/) +## [Manage the index component in SharePoint Server](pr/) +## [Manage the lock status for site collections in SharePoint Server](pr/) +## [Manage the Search Center in SharePoint Server](pr/) +## [Manage the search index in SharePoint Server 2016](pr/) +## [Manage the search schema in SharePoint Server](pr/) +## [Manage the search topology in SharePoint Server](pr/) +## [Manage unused site collections in SharePoint Server](pr/) +## [Manage user profile synchronization in SharePoint Server](pr/) +## [Manage web parts in SharePoint Server](pr/) +## [Managing a MinRole Server Farm in SharePoint Server 2016](pr/) +## [Microsoft Identity Manager in SharePoint Server 2016](pr/) +## [Migrate content into or out of RBS in SharePoint Server](pr/) +## [Missing server side dependencies (SharePoint Server 2016)](pr/) +## [Mobile device browsers supported in SharePoint 2013](pr/) +## [Mobile security and authentication in SharePoint 2013](pr/) +## [Monitor and manage app licenses in SharePoint Server](pr/) +## [Monitor apps for SharePoint for SharePoint Server](pr/) +## [Monitor cache performance in SharePoint Server 2016](pr/) +## [Monitoring and Reporting in SharePoint Server](pr/) +## [More cache hosts are running in this deployment than are registered with SharePoint (SharePoint Server 2016)](pr/) +## [Move all databases in SharePoint Server](pr/) +## [Move content databases in SharePoint Server](pr/) +## [Move or rename service application databases in SharePoint Server](pr/) +## [Move site collections between databases in SharePoint Server](pr/) +## [New and improved features in SharePoint Server 2016](pr/) +## [New features in November 2016 PU for SharePoint Server 2016 (Feature Pack 1)](pr/) +## [One of the cache hosts in the cluster is down (SharePoint Server 2016)](pr/) +## [One or more app domains for web applications aren't configured correctly (SharePoint Server 2016)](pr/) +## [One or more categories are configured with Verbose trace logging (SharePoint Server 2016)](pr/) +## [One or more servers is not responding (SharePoint Server 2016)](pr/) +## [One or more services have started or stopped unexpectedly (SharePoint Server 2016)](pr/) +## [One or more web applications are configured to use Windows Classic authentication (SharePoint Server 2016)](pr/) +## [Operations for SharePoint Server](pr/) +## [Outbound e-mail has not been configured (SharePoint Server 2016)](pr/) +## [Overview of analytics processing in SharePoint Server](pr/) +## [Overview of backup and recovery in SharePoint Server](pr/) +## [Overview of Business Connectivity Services in SharePoint Server](pr/) +## [Overview of Business Connectivity Services security tasks in SharePoint Server](pr/) +## [Overview of co-authoring in SharePoint 2013](pr/) +## [Overview of cross-site publishing in SharePoint Server](pr/) +## [Overview of document management in SharePoint 2013](pr/) +## [Overview of eDiscovery and in-place holds in SharePoint Server](pr/) +## [Overview of Excel Services in SharePoint Server 2013](pr/) +## [Overview of managed navigation in SharePoint Server](pr/) +## [Overview of managing digital assets in SharePoint Server 2013](pr/) +## [Overview of Microsoft Identity Manager Synchronization Service in SharePoint Server 2016](pr/) +## [Overview of MinRole Server Roles in SharePoint Server 2016](pr/) +## [Overview of mobile devices and SharePoint Server 2013](pr/) +## [Overview of monitoring in SharePoint Server](pr/) +## [Overview of My Sites in SharePoint Server](pr/) +## [Overview of OneDrive for Business in SharePoint Server](pr/) +## [Overview of PerformancePoint analytic charts and grids](pr/) +## [Overview of PerformancePoint KPI Details reports](pr/) +## [Overview of PerformancePoint reports and scorecards](pr/) +## [Overview of PerformancePoint scorecards](pr/) +## [Overview of PerformancePoint strategy maps](pr/) +## [Overview of profile synchronization in SharePoint Server 2013](pr/) +## [Overview of profile synchronization in SharePoint Server 2016](pr/) +## [Overview of publishing to Internet, intranet, and extranet sites in SharePoint Server](pr/) +## [Overview of RBS in SharePoint Server](pr/) +## [Overview of records management in SharePoint Server 2013](pr/) +## [Overview of Reporting Services reports displayed in PerformancePoint Web Parts](pr/) +## [Overview of search architecture in SharePoint Server](pr/) +## [Overview of search result ranking in SharePoint Server](pr/) +## [Overview of site navigation in SharePoint Server](pr/) +## [Overview of site policies in SharePoint Server](pr/) +## [Overview of sites and site collections in SharePoint Server](pr/) +## [Overview of SQL Server in a SharePoint Server 2016 environment](pr/) +## [Overview of the PerformancePoint Decomposition Tree](pr/) +## [Overview of the search schema in SharePoint Server](pr/) +## [Overview of the upgrade process to SharePoint Server 2016](pr/) +## [Overview of the User Profile service architecture in SharePoint Server](pr/) +## [Overview of themes in SharePoint Server](pr/) +## [Overview of Visio Services in SharePoint Server](pr/) +## [Overview of Web Page reports in Dashboard Designer](pr/) +## [People Picker and claims providers overview (SharePoint 2013)](pr/) +## [People Search relevance is not optimized when the Active Directory has errors in the manager reporting structure (SharePoint Server 2016)](pr/) +## [PerformancePoint Services administration](pr/) +## [PerformancePoint Services application settings](pr/) +## [PerformancePoint Services in SharePoint Server 2016 overview](pr/) +## [Permissions planning for sites and content in SharePoint Server 2016](pr/) +## [Plan a Business Connectivity Services solution in SharePoint Server](pr/) +## [Plan authentication in SharePoint Server](pr/) +## [Plan authoring sites for cross-site publishing in SharePoint Server](pr/) +## [Plan browser support in SharePoint 2013](pr/) +## [Plan browser support in SharePoint Server 2016](pr/) +## [Plan connectivity from Office 365 to SharePoint Server](pr/) +## [Plan content types and workflows in SharePoint 2013](pr/) +## [Plan crawling and federation in SharePoint Server](pr/) +## [Plan digital asset libraries in SharePoint Server 2013](pr/) +## [Plan document libraries in SharePoint 2013](pr/) +## [Plan document management in SharePoint 2013](pr/) +## [Plan document sets in SharePoint Server 2013](pr/) +## [Plan document versioning, content approval, and check-out controls in SharePoint 2013](pr/) +## [Plan eDiscovery in SharePoint Server](pr/) +## [Plan email integration for a SharePoint Server 2016 farm](pr/) +## [Plan enterprise search architecture in SharePoint Server 2016](pr/) +## [Plan Excel Services Data Model settings in SharePoint Server 2013](pr/) +## [Plan Excel Services Global Settings in SharePoint Server 2013](pr/) +## [Plan for app authentication in SharePoint Server](pr/) +## [Plan for apps for SharePoint Server](pr/) +## [Plan for backup and recovery in SharePoint Server](pr/) +## [Plan for Business Connectivity Services in SharePoint Server](pr/) +## [Plan for caching and performance in SharePoint Server](pr/) +## [Plan for cross-site publishing in SharePoint Server](pr/) +## [Plan for custom claims providers for People Picker in SharePoint 2013](pr/) +## [Plan for eDiscovery in SharePoint Server](pr/) +## [Plan for feeds and the Distributed Cache service in SharePoint Server](pr/) +## [Plan for high availability and disaster recovery for SharePoint Server](pr/) +## [Plan for hybrid OneDrive for Business](pr/) +## [Plan for hybrid sites features](pr/) +## [Plan for information management policy in SharePoint Server 2013](pr/) +## [Plan for Internet, intranet, and extranet publishing sites in SharePoint Server](pr/) +## [Plan for Kerberos authentication in SharePoint Server](pr/) +## [Plan for managed metadata in SharePoint Server](pr/) +## [Plan for mobile devices in SharePoint 2013](pr/) +## [Plan for mobile views in SharePoint Server 2013](pr/) +## [Plan for multilingual sites in SharePoint Server](pr/) +## [Plan for My Sites and OneDrive for Business in SharePoint Server](pr/) +## [Plan for My Sites in SharePoint Server](pr/) +## [Plan for OneDrive for Business in SharePoint Server](pr/) +## [Plan for People Picker in SharePoint 2013](pr/) +## [Plan for server-to-server authentication in SharePoint Server](pr/) +## [Plan for SharePoint Hybrid Picker](pr/) +## [Plan for SharePoint Server](pr/) +## [Plan for site maintenance and management in SharePoint Server](pr/) +## [Plan for the multilingual user interface in SharePoint Server](pr/) +## [Plan for user authentication methods in SharePoint Server](pr/) +## [Plan for variations in SharePoint Server](pr/) +## [Plan for Visio Services in SharePoint Server](pr/) +## [Plan hybrid federated search for SharePoint Server](pr/) +## [Plan incoming email for a SharePoint Server 2016 farm](pr/) +## [Plan navigation term sets in SharePoint Server](pr/) +## [Plan outgoing email for a SharePoint Server 2016 farm](pr/) +## [Plan profile synchronization for SharePoint Server 2013](pr/) +## [Plan publishing sites for cross-site publishing in SharePoint Server](pr/) +## [Plan records management in SharePoint Server 2013](pr/) +## [Plan search for cross-site publishing sites in SharePoint Server 2016](pr/) +## [Plan search in SharePoint Server](pr/) +## [Plan security hardening for SharePoint Server 2016](pr/) +## [Plan self-service site creation in SharePoint Server](pr/) +## [Plan server-to-server authentication](pr/) +## [Plan SharePoint Server hybrid](pr/) +## [Plan sites and site collections in SharePoint Server](pr/) +## [Plan the logical architecture for cross-site publishing in SharePoint Server](pr/) +## [Plan the Secure Store Service in SharePoint Server](pr/) +## [Plan to transform queries and order results in SharePoint Server](pr/) +## [Plan Trusted Data Connection Libraries in SharePoint Server 2013](pr/) +## [Plan Trusted File Locations in SharePoint Server 2013](pr/) +## [Plan user profiles and identities](pr/) +## [Plan user profiles in SharePoint Server](pr/) +## [Plan variations for multilingual cross-site publishing site in SharePoint Server](pr/) +## [Plan Visio Services deployment in SharePoint Server](pr/) +## [Plan Visio Services security in SharePoint Server](pr/) +## [Plan ways to convert active documents to records in SharePoint Server 2013](pr/) +## [Plan web content management in SharePoint Server](pr/) +## [Planning for a MinRole server deployment in SharePoint Server 2016](pr/) +## [Prepare for installation of SharePoint Server 2016](pr/) +## [Prepare to back up and restore farms in SharePoint Server](pr/) +## [Prepare your environment for the Business Connectivity Services hybrid scenario](pr/) +## [Product / patch installation or server upgrade required (SharePoint Server 2016)](pr/) +## [Publish service applications in SharePoint Server](pr/) +## [Query variables in SharePoint Server](pr/) +## [Redesign enterprise search topology for more content and users in SharePoint 2016](pr/) +## [Redesign enterprise search topology for specific performance requirements in SharePoint 2016](pr/) +## [Remove a server from a farm in SharePoint Server 2016](pr/) +## [Remove app for SharePoint instances from a SharePoint site](pr/) +## [Reset the search index in SharePoint Server](pr/) +## [Restore apps for SharePoint in SharePoint Server](pr/) +## [Restore content databases in SharePoint Server](pr/) +## [Restore content from unattached content databases in SharePoint Server](pr/) +## [Restore customizations in SharePoint Server](pr/) +## [Restore farm configurations in SharePoint Server](pr/) +## [Restore farms in SharePoint Server](pr/) +## [Restore Search service applications in SharePoint Server](pr/) +## [Restore Secure Store Service applications in SharePoint Server](pr/) +## [Restore service applications in SharePoint Server](pr/) +## [Restore site collections in SharePoint Server](pr/) +## [Restore solutions in SharePoint Server](pr/) +## [Restore User Profile Service applications in SharePoint Server](pr/) +## [Restore web applications in SharePoint Server](pr/) +## [Restrict or enable access to a service application in SharePoint Server](pr/) +## [Result types and display templates that are used to display search results in SharePoint Server](pr/) +## [Role conversion using MinRole in SharePoint Server 2016](pr/) +## [Run a farm that uses read-only databases in SharePoint Server](pr/) +## [Run Hybrid Picker](pr/) +## [Scale enterprise search in SharePoint Server](pr/) +## [Scale search for Internet sites in SharePoint Server](pr/) +## [Schedule profile synchronization in SharePoint Server](pr/) +## [Search in SharePoint Server 2016 knowledge articles for Systems Center Operations Manager](pr/) +## [Search technical reference for SharePoint Server](pr/) +## [Search - One or more crawl databases may have fragmented indices (SharePoint Server 2016)](pr/) +## [Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocol support in SharePoint Server 2016](pr/) +## [Secure Store for Business Intelligence service applications](pr/) +## [Security for SharePoint Server](pr/) +## [Server role configuration isn't correct (SharePoint Server 2016)](pr/) +## [Server-to-server authentication and user profiles in SharePoint Server](pr/) +## [Service application and service management in SharePoint Server](pr/) +## [Services and Application Planning in SharePoint Server 2016](pr/) +## [Services upgrade overview for SharePoint Server 2016](pr/) +## [Set a content database to use RBS with FILESTREAM in SharePoint Server](pr/) +## [Set permissions to published service applications in SharePoint Server](pr/) +## [Set up OneDrive for Business in a SharePoint Server on-premises environment](pr/) +## [Set up Search of OneDrive for Business in Office 365 from SharePoint Server](pr/) +## [Set up SharePoint services for hybrid environments](pr/) +## [Share a SQL Server Analysis Services data connection using Excel Services (SharePoint Server 2013)](pr/) +## [Share a SQL Server data connection using Excel Services (SharePoint Server 2013)](pr/) +## [Share an OLE DB or ODBC connection using Excel Services (SharePoint Server 2013)](pr/) +## [Share data connections by using Excel and Excel Services (SharePoint Server 2013)](pr/) +## [Share service applications across farms in SharePoint Server](pr/) +## [Share workbooks by using Excel Services (SharePoint Server 2013)](pr/) +## [SharePoint Health Analyzer rules reference for SharePoint Server 2016](pr/) +## [SharePoint Hybrid Auditing (Preview)](pr/) +## [SharePoint Intranet Farm in Azure Phase 1 Configure Azure](pr/) +## [SharePoint Intranet Farm in Azure Phase 2 Configure domain controllers](pr/) +## [SharePoint Intranet Farm in Azure Phase 3 Configure SQL Server Infrastructure](pr/) +## [SharePoint Intranet Farm in Azure Phase 4 Configure SharePoint servers](pr/) +## [SharePoint Intranet Farm in Azure Phase 5 Create the availability group and add the SharePoint databases](pr/) +## [SharePoint Server 2016 dev/test environment in Azure](pr/) +## [SharePoint Server 2016 hybrid configuration roadmaps](pr/) +## [SharePoint Server 2016 in Microsoft Azure](pr/) +## [SharePoint Server 2016 zero downtime patching steps](pr/) +## [SharePoint Server 2016](pr/) +## [SharePoint Updates](pr/) +## [[SharePoint Server 2016](articles/sharepoint-server-2016.md)](pr/) +## [Show results from Office 365 in on-premises SharePoint with cloud hybrid search](pr/) +## [Social scenarios with Yammer and SharePoint Server 2013](pr/) +## [Software boundaries and limits for SharePoint 2013](pr/) +## [Software boundaries and limits for SharePoint Server 2016](pr/) +## [Software requirements for business intelligence in SharePoint Server](pr/) +## [Software updates overview for SharePoint Server 2016](pr/) +## [Solutions for the real world in SharePoint Server](pr/) +## [Some content databases are growing too large (SharePoint Server 2016)](pr/) +## [SQL Server and storage (SharePoint Server)](pr/) +## [Start or stop a service in SharePoint Server](pr/) +## [Start, pause, resume, or stop a crawl in SharePoint Server](pr/) +## [Start profile synchronization manually in SharePoint Server](pr/) +## [Storage and SQL Server capacity planning and configuration (SharePoint Server)](pr/) +## [Supported and unsupported Documentum object types and properties in SharePoint Server](pr/) +## [Supported high availability and disaster recovery options for SharePoint databases](pr/) +## [Supporting the SharePoint mobile apps online and on-premises](pr/) +## [Synchronize user and group profiles in SharePoint Server 2013](pr/) +## [System Center Operations Manager knowledge articles for SharePoint Server](pr/) +## [System requirements for SharePoint 2013](pr/) +## [System requirements for SharePoint Server 2016](pr/) +## [Technical diagrams for SharePoint Server](pr/) +## [Technical reference for SharePoint Server](pr/) +## [Test and troubleshoot an upgrade to SharePoint Server 2016](pr/) +## [Test Lab Guide Configure intranet and team sites for SharePoint Server 2013](pr/) +## [Test Lab Guide Configure SharePoint Server 2013 in a three-tier farm](pr/) +## [Test Lab Guide Demonstrate forms-based claims authentication for SharePoint Server 2013](pr/) +## [Test Lab Guide Demonstrate profile synchronization for SharePoint Server 2013](pr/) +## [Test Lab Guide Demonstrate SAML-based Claims Authentication with SharePoint Server 2013](pr/) +## [Test Lab Guide Demonstrate Social Features for SharePoint Server 2013](pr/) +## [Test lab guides for SharePoint Server 2013](pr/) +## [The Application Discovery and Load Balancer Service is not running in this farm (SharePoint Server 2016)](pr/) +## [The building blocks of SharePoint hybrid](pr/) +## [The current server is running low on memory (SharePoint Server 2016)](pr/) +## [The InfoPath Forms Services Maintenance timer job is not enabled (SharePoint Server 2016)](pr/) +## [The Machine Translation Service is not running when it should be running (SharePoint Server 2016)](pr/) +## [The Net.Pipe Listener Adapter isn't available (SharePoint Server 2016)](pr/) +## [The number of Distributed Cache hosts in the farm exceeds the recommended value (SharePoint Server 2016)](pr/) +## [The paging file size should exceed the amount of physical RAM in the system (SharePoint Server)](pr/) +## [The Security Token Service is not available (SharePoint Server 2016)](pr/) +## [The server farm account should not be used for other services (SharePoint Server 2016)](pr/) +## [The settings for the Machine Translation Service are not within the recommended limits (SharePoint Server 2016)](pr/) +## [The settings for Word Automation Services are not within the recommended limits (SharePoint Server 2016)](pr/) +## [The State Service Delete Expired Sessions timer job is not enabled (SharePoint Server 2016)](pr/) +## [The timer service failed to recycle (SharePoint Server 2016)](pr/) +## [The unattended Service Account Application ID is not specified or has an invalid value (SharePoint Server 2016)](pr/) +## [The Visio Graphics Service has a maximum cache age setting that will adversely impact performance (SharePoint Server 2016)](pr/) +## [The Visio Graphics Service has a maximum cache size setting that may adversely impact performance ((SharePoint Server 2016)](pr/) +## [The Visio Graphics Service has a maximum recalc duration setting that will adversely impact user perceived performance ((SharePoint Server 2016)](pr/) +## [The Visio Graphics Service has a maximum Web Drawing Size setting that will adversely impact performance (SharePoint Server 2016)](pr/) +## [The Visio Graphics Service has a minimum cache age setting that may cause a security issue ((SharePoint Server 2016)](pr/) +## [The Visio Graphics Service has a minimum cache age setting that will adversely impact performance ((SharePoint Server 2016)](pr/) +## [This Distributed Cache host may cause cache reliability problems (SharePoint Server 2016)](pr/) +## [Timer job reference for SharePoint Server 2016](pr/) +## [Troubleshoot site collection upgrade issues in SharePoint Server 2016](pr/) +## [Turn on automated document translation in SharePoint Server 2016](pr/) +## [Understanding result sources for search in SharePoint Server](pr/) +## [Understanding workflow in SharePoint Server 2016](pr/) +## [Uninstall SharePoint Server 2016](pr/) +## [Update Workflow in SharePoint Server 2013](pr/) +## [Updated Product Servicing Policy for SharePoint 2013](pr/) +## [Updated Product Servicing Policy for SharePoint Server 2016](pr/) +## [Upgrade a site collection to SharePoint Server 2016](pr/) +## [Upgrade content databases to SharePoint Server 2016](pr/) +## [Upgrade databases from SharePoint 2013 to SharePoint Server 2016](pr/) +## [Upgrade My Sites to SharePoint Server 2016](pr/) +## [Upgrade service applications to SharePoint Server 2016](pr/) +## [Upgrade site collections to SharePoint Server 2016](pr/) +## [Upgrade to SharePoint Server 2016](pr/) +## [Use a sample MIM solution in SharePoint Server 2016](pr/) +## [Use a SharePoint Server 2013 records archive or manage records in place](pr/) +## [Use Analysis Services EffectiveUserName in SharePoint Server](pr/) +## [Use EffectiveUserName in PerformancePoint Services](pr/) +## [Use EffectiveUserName with Excel Services (SharePoint Server 2013)](pr/) +## [Use Excel Services with Secure Store Service in SharePoint Server 2016](pr/) +## [Use PerformancePoint Services with Secure Store Service in SharePoint Server](pr/) +## [Use Secure Store with SQL Server Authentication](pr/) +## [Use Visio Services with external lists in SharePoint Server](pr/) +## [Use Visio Services with Secure Store Service in SharePoint Server](pr/) +## [Use Visio Services with SharePoint lists](pr/) +## [Using Administrative Actions logging in SharePoint Server 2016](pr/) +## [Validate the Business Connectivity Services hybrid scenario](pr/) +## [Validate the My Site Host and individual My Sites are on a dedicated Web application and separate URL domain (SharePoint Server 2016)](pr/) +## [Variations overview in SharePoint Server](pr/) +## [Verify database upgrades in SharePoint Server 2016](pr/) +## [Verify each User Profile service application has a My Site host configured (SharePoint Server 2016)](pr/) +## [Verify each User Profile Service Application has an associated Managed Metadata Service Connection ((SharePoint Server 2016)](pr/) +## [Verify each User Profile Service Application has an associated Search Service Connection (SharePoint Server 2016)](pr/) +## [Verify that OAuth is configured correctly for the Machine Translation Service application proxy (SharePoint Server 2016)](pr/) +## [Verify that the Activity Feed Timer Job is enabled (SharePoint Server 2016)](pr/) +## [Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted (SharePoint Server 2016)](pr/) +## [Video Cleanup of databases after upgrade procedure](pr/) +## [Video demo of Zero Downtime Patching in SharePoint Server 2016](pr/) +## [Video How to enable Remote Windows PowerShell to use with SharePoint Server](pr/) +## [Video series Install and configure Workflow in SharePoint Server 2013](pr/) +## [View all site collections in SharePoint Server](pr/) +## [View data in the logging database in SharePoint Server 2016](pr/) +## [View diagnostic logs in SharePoint Server](pr/) +## [View health reports in SharePoint Server](pr/) +## [View reports and logs in SharePoint Server 2016](pr/) +## [View search diagnostics in SharePoint Server](pr/) +## [View timer job status in SharePoint Server 2016](pr/) +## [Visio Services in SharePoint Server 2016 knowledge articles](pr/) +## [Web applications management in SharePoint Server](pr/) +## [Web Applications using Claims authentication require an update (SharePoint Server 2016)](pr/) +## [Web.config file has incorrect settings for the requestFiltering element (SharePoint Server 2016)](pr/) +## [Web.config files are not identical on all machines in the farm (SharePoint Server 2016)](pr/) +## [What is governance in SharePoint?](pr/) +## [What's deprecated or removed from SharePoint Server 2016](pr/) +## [XLIFF translations for the Machine Translation Service is disabled (SharePoint Server 2016)](pr/) +## [Yammer networks, groups, and users overview](pr/) diff --git a/SharePoint/a-state-service-application-has-no-database-defined-sharepoint-server-2016.md b/SharePoint/a-state-service-application-has-no-database-defined-sharepoint-server-2016.md new file mode 100644 index 0000000000..5adc314327 --- /dev/null +++ b/SharePoint/a-state-service-application-has-no-database-defined-sharepoint-server-2016.md @@ -0,0 +1,81 @@ +--- +title: A State Service Application has no database defined (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: f2bd109d-83ce-4bf5-aec8-2c7df2ff5c3b +--- + + +# A State Service Application has no database defined (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "A State Service Application has no database defined." **Rule Name:**    A State Service Application has no database defined **Summary:**    A State Service service application has no State Service database defined. This may result in errors when using some SharePoint components such as InfoPath Web browser forms and the Microsoft SharePoint Server Chart Web Part. **Cause:**    One or more of the following might be causing this: +- The farm administrator deleted all databases associated with the State Service service application. + + +- The farm administrator never created or associated a database with the State Service service application. + + + **Resolution:   Create a new database or use an existing database for the State Service service application by using Microsoft PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint 2013 Products cmdlets. + + > [!NOTE:] + +2. Start the SharePoint 2016 Management Shell. + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows](http://go.microsoft.com/fwlink/?LinkID=715712&clcid=0x409). + + +3. If no database already exists that you can use, type the following command at the PowerShell command prompt: + + ``` + +New-SPStateServiceDatabase -Name -DatabaseServer [-DatabaseCredentials ] [-ServiceApplication ] + ``` + + + Where: + + - ** is name of the database as a String. + + + - ** is name of the database server. + + + - ** is SQL Server authentication credentials for the database. If this parameter is not used, Windows authentication will be used. + + + - ** is the identifier for the State Service service application as a string or a GUID. If there is only one State Service service application, you do not have to specify this parameter. + + +4. In some environments, you must connect to an existing, empty SQL database. In this case, type the following command at the Windows PowerShell command prompt: + + ``` + Mount-SPStateServiceDatabase -Name -DatabaseServer [-DatabaseCredentials ] [-ServiceApplication ] + ``` + + + Where: + + - ** is name of the database as a String. + + + - ** is name of the database server. + + + - ** is the SQL Server authentication credentials for the database. If this parameter is not used, Windows authentication will be used. + + + - ** is the identifier for the State Service service application as a string or a GUID. If there is only one State Service service application, you do not have to specify this parameter. + + +For more information, see Mount-SPStateServiceDatabase or New-SPStateServiceDatabase. diff --git a/SharePoint/about-service-applications-and-services-in-sharepoint-server.md b/SharePoint/about-service-applications-and-services-in-sharepoint-server.md new file mode 100644 index 0000000000..28217489cd --- /dev/null +++ b/SharePoint/about-service-applications-and-services-in-sharepoint-server.md @@ -0,0 +1,12 @@ +--- +title: About service applications and services in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: ba00a200-ea96-45f6-a423-3cfcffba77f8 +--- + + +# About service applications and services in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-24* **Summary:** Learn about service applications and service application connections in SharePoint Server 2016 and SharePoint Server 2013.In SharePoint Server, individual services can be configured independently and third-party companies can add services. The services infrastructure gives you control over which services are deployed and how services are shared. Services that are deployed are named *service applications* . A service application provides a resource that can be shared across sites throughout a farm, and can be accessed by users through a hosting web application. Service applications are associated to web applications by *service application connections* . Some services can be shared across farms.For more information about how to manage service applications that included instructions for publishing service applications across farms, see [Manage service applications in SharePoint Server](html/manage-service-applications-in-sharepoint-server.md) and [Share service applications across farms in SharePoint Server](html/share-service-applications-across-farms-in-sharepoint-server.md).For more information about starting, stopping, and configuring services, see [Start or stop a service in SharePoint Server](html/start-or-stop-a-service-in-sharepoint-server.md).For details about the SharePoint Server 2016 service applications associated with each MinRole server role, see [Description of MinRole and associated services in SharePoint Server 2016](html/description-of-minrole-and-associated-services-in-sharepoint-server-2016.md). +## + + diff --git a/SharePoint/access-services-in-sharepoint-server-2016-knowledge-articles.md b/SharePoint/access-services-in-sharepoint-server-2016-knowledge-articles.md new file mode 100644 index 0000000000..21ca3e5c09 --- /dev/null +++ b/SharePoint/access-services-in-sharepoint-server-2016-knowledge-articles.md @@ -0,0 +1,371 @@ +--- +title: Access Services in SharePoint Server 2016 knowledge articles +ms.prod: SHAREPOINT +ms.assetid: 0f33d9cc-7b26-4418-b901-bf773abaf574 +--- + + +# Access Services in SharePoint Server 2016 knowledge articles + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2016-09-16* Learn how to resolve alerts about Access Services in the SharePoint Server 2016 management pack for Systems Center Operations Manager (SCOM).The articles in this section are knowledge articles for UNRESOLVED_TOKEN_VAL(AccessServices_2nd_NoVerr) in SharePoint Server 2016. Typically, you would see these articles after clicking a link in an alert in the Operations Manager console. You can use these articles to help you troubleshoot and resolve problems in Access Services in SharePoint Server 2016. Download and install [System Center Monitoring Pack for SharePoint Server 2016](http://go.microsoft.com/fwlink/?LinkID=746863&clcid=0x409). +- [Access Services: No application info from content database](#NoAppInfo) + + +- [Access Services: WFE to ADS communication failure](#WFEADS) + + +- [Access Services: No servers available for database creation](#NoServers) + + +- [Access Services: Partitioned SSS communication failure](#SSSFail) + + +- [Access Services: Unpartitioned SSS communication failure](#SSSFailUnpart) + + +- [Access Services: Trigger for excessive failed SQL connections requests](#TrigSQLReq) + + +- [Access Services: Excessive failed SQL connections](#SQLCon) + + +- [Access Services: Trigger for excessive SQL connection retries](#TrigSQLRetries) + + +- [Access Services: Excessive SQL connection retries](#SQLRetries) + + +- [Access Services: Trigger for excessive SQL write failures](#TrigSQLWrite) + + +- [Access Services: Excessive SQL write failures](#SQLWrite) + + +- [Access Services: No available ADS servers](#NoADS) + + +- [Access Services: No default proxy](#NoProxy) + + +- [Access Services: Failed to register database server](#NoDBServ) + + + +## No application info from content database + + + **Alert Name:** Access Services: No application info from content database **Summary:** Access Data Services tries to retrieve application information from the SharePoint Content Database, but cannot find the relevant app's information. If this occurs, the application will not be available for use. +## Cause + +Someone creates a site that uses an Access template that is not actually an Access application. +## Resolution + +Delete the site that is created incorrectly. +## WFE to ADS communication failure + + + **Alert Name:** Access Services: WFE to ADS communication failure **Summary:** Access Data Services WFE (Web Front End) is unable to communicate with the ADS (Access Data Services) middle tier. +## Cause + +One or more of the following might be the cause: +- Network issues + + +- Hardware failure + + +- SharePoint service failure + + +- Disabled Access Database Services on the server + + + +## Resolution + + +1. Ensure that network is healthy. + + +2. Ensure that ADS server is available. + + +3. Ensure that ADS server can be accessed from WFE. + + +4. Ensure IIS Process for ADS application pool is running. + + +5. Ensure that the ADS service is enabled on the failing ADS server. + + + +## No servers available for database creation + + + **Alert Name:** Access Services: No servers available for database creation **Summary:** During application creation, Access Data services cannot find an available SQL Server to provision the new database. +## Cause + +No SQL database servers are configured for Access to provision new databases. +## Resolution + + +- If the creation failure occurs while creating from the Access client, check the Database Server group mappings to determine where the shortage has occurred: + +1. Use Get-SPAccessServicesDatabaseServerGroupMapping to determine whether there is a mapping from the Object Model to the Server Group. + + +2. Use Get-SPAccessServicesDatabaseServerGroup to determine whether the server group has at least one database. + + +3. Use Get-SPAccessServicesDatabaseServer to determine whether there is at least one database in the server group marked as "AvailableForCreate". + + +- If the creation failure occurs while creating from the Corporate Catalog, check the Database Server group mappings to determine where the shortage has occurred: + +1. Use Get-SPAccessServicesDatabaseServerGroupMapping to determine whether there is a mapping from the Corporate Catalog to the Server Group. + + +2. Use Get-SPAccessServicesDatabaseServerGroup to determine whether the server group has at least one database. + + +3. Use Get-SPAccessServicesDatabaseServer to determine whether there is at least one database in the server group marked as "AvailableForCreate". + + + +## Related topics + + **Get-SPAccessServicesDatabaseServerGroupMapping** **Get-SPAccessServicesDatabaseServerGroup** **Get-SPAccessServicesDatabaseServer** +## Partitioned SSS communication failure + + + **Alert Name:** Access Services: Partitioned SSS communication failure **Summary:** Access Data Services tries to communicate with SharePoint partitioned Secure Store Service, but is unable to communicate with it. +## Cause + +Partitioned Secure Store Service in the farm is down or unreachable because of Network issues or incorrect configurations. +## Resolution + + +1. Ensure partitioned Secure Store Service Application exists and is running. + + +2. Ensure Proxy for partitioned Secure Store Service exists and is in the default Proxy group. + + + +## Related topics + + +## Unpartitioned SSS communication failure + + + **Alert Name:** Access Services: Unpartitioned SSS communication failure **Summary:** Access Data Services tries to communicate with SharePoint unpartitioned Secure Store Service, but is unable to communicate with it. +## Cause + +Unpartitioned Secure Store Service in the farm is down or unreachable because of Network issues or incorrect configurations. +## Resolution + + +1. Ensure unpartitioned Secure Store Service Application exists and is running. + + +2. Ensure Proxy for unpartitioned Secure Store Service exists and is in the default Proxy group. + + + +## Related topics + + +## Trigger for excessive failed SQL connections requests + + + **Alert Name:** Access Services: Trigger for excessive failed SQL connections requests **Summary:** This alert occurs when Access Data services exceed the expected number of retries when the services connect to the SQL Server Databases. +## Cause + +SQL Server database server is down, unavailable, or unreachable. +## Resolution + + +- Check network health. + + +- Make sure that the SQL Server database server is available and healthy. + + + +## Excessive failed SQL connections + + + **Alert Name:** Access Services: Excessive failed SQL connections **Summary:** This tracks the number of failed SQL connections. +## Cause + +N/A +## Resolution + +N/A +## Trigger for excessive SQL connection retries + + + **Alert Name:** Access Services: Trigger for excessive SQL connection retries **Summary:** This alert occurs when Access Data services exceed the expected number of retries when the services connect to the Application SQL Databases. +## Cause + +One or more of the following might be the cause: +- Network issues + + +- Application SQL databases are unavailable or unreachable. + + + +## Resolution + + +1. Check network health. + + +2. Check Application SQL databases availability and healthy states. + + + +## Excessive SQL connection retries + + + **Alert Name:** Access Services: Excessive SQL connection retries **Summary:** This monitors the number of SQL Database Server Connection retries. +## Cause + +N/A +## Resolution + +N/A +## Trigger for excessive SQL write failures + + + **Alert Name:** Access Services: Trigger for excessive SQL write failures **Summary:** This alert occurs if there are too many SQL Write failures. +## Cause + +Excessive number of SQL Write failures. +## Resolution + + +1. Check network health. + + +2. Check status of SQL Azure service. + + +3. Raise an incident with SQL Azure for resolution. + + + +## Excessive SQL write failures + + + **Alert Name:** Access Services: Excessive SQL write failures **Summary:** Monitors the number of failed SQL Database Server writes +## Cause + +One or more of the following might be the cause: +- Application SQL Databases are unavailable or unreachable. + + +- Deadlock occurs on the server. + + +- Excessive server load makes the database server unresponsive. + + + +## Resolution + +Ensure that the Database server is available, is not overloaded, and has no deadlocks. +## No available ADS servers + + + **Alert Name:** Access Services: No available ADS servers **Summary:** There are no Access Data Services Servers or the available Access Data Services Servers are not healthy enough to serve the request. +## Cause + +One or more of the following might be the cause: +- Excessive memory consumption overloads your ADS Servers. + + +- Network problems + + +- A number of Access Database Server instances fail or are down. + + + +## Resolution + + +1. Ensure that Access Database Services is enabled on at least one server in the farm. + + +2. Reboot Access Database Service instances to free memory. + + +3. Ensure Access Database Service instances are available and are configured correctly. + + + +## No default proxy + + + **Alert Name:** Access Services: No default proxy **Summary:** There is no Access Data Services Proxy in the Default Proxy group. +## Cause + +No default proxy is established during configuration, or there is a problem during provisions and a default proxy is not established. +## Resolution + +Use new-SPAccessServicesApplicationProxy to create a new default proxy. +## Related topics + + **New-SPAccessServicesApplication** +## Failed to register database server + + + **Alert Name:** Access Services: Failed to register database server **Summary:** During Database server configuration, a server fails to register. +## Cause + +One or more of the following might be the cause: +- Network issues connecting to the server + + +- Incorrect Database server version + + +- Server does not have required features or insufficient permissions + + + +## Resolution + + +1. Check network health. + + +2. Update the database server version. + + +3. Install required features or update permissions. + + + +> [!NOTE:] + + + + + + +# See also + +#### + + [System Center Monitoring Pack for SharePoint Server 2016](http://go.microsoft.com/fwlink/?LinkID=746863&clcid=0x409) + + + + + + + + diff --git a/SharePoint/accessibility-guidelines-in-sharepoint-server-2016.md b/SharePoint/accessibility-guidelines-in-sharepoint-server-2016.md new file mode 100644 index 0000000000..7b51838f30 --- /dev/null +++ b/SharePoint/accessibility-guidelines-in-sharepoint-server-2016.md @@ -0,0 +1,59 @@ +--- +title: Accessibility guidelines in SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: d63f37bc-3383-4df8-af12-15da5eb1133c +--- + + +# Accessibility guidelines in SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Access and learn about the W3C Web Content Accessibility Guidelines (WCAG) 2.0 Conformance Statement and Voluntary Product Accessibility Template (VPAT) for SharePoint Server 2016 and SharePoint Server 2013.SharePoint Server supports the accessibility features of common browsers that help IT Pros administer deployments and access sites. For more information about supported features, see [Web Content Accessibility Guidelines 2.0](https://www.w3.org/TR/WCAG20/).Administrators and other users who have administrative responsibilities typically use the SharePoint Central Administration website and the SharePoint 2016 Management Shell to manage deployments. The mouse and keyboard are typical devices that administrators use to interact with Central Administration.Because SharePoint Server runs as web sites in Internet Information Services (IIS), administrators and users depend on the accessibility features that browsers provide. SharePoint Server supports the accessibility features of supported browsers. For more information, see [Plan browser support in SharePoint Server 2016](html/plan-browser-support-in-sharepoint-server-2016.md).Users who don't use a mouse can use a keyboard to navigate the user interface and complete actions. The ability to use the keyboard in this way is a result of support for keyboard interactions that a browser provides. Users who have devices that support touch can also use gestures to complete operations. For more information, see [Touch](https://msdn.microsoft.com/en-us/library/windows/desktop/dn742468.aspx). +## SharePoint Server 2016 conformance statement + +The following SharePoint Server 2016 conformance statement, VPAT, and EN 301 549 reports are available on the [Section 508 VPAT](https://enterprise.microsoft.com/en-us/industries/government/section-508-vpats-for-microsoft-products/), [WCAG conformance statement](https://enterprise.microsoft.com/en-us/industries/government/wcag-2-0-reports-for-microsoft-products/) and [EN 301 549](https://www.microsoft.com/en301549) sites. +- [WCAG Conformance Statement: SharePoint Server 2016](https://download.microsoft.com/download/8/1/3/8130866F-591A-49C2-82E9-CC7561A5554A/SharePoint_Server_2016_Web_WCAG_081116.DOCX) + + +- [Section 508 VPAT: SharePoint Server 2016](https://download.microsoft.com/download/8/1/3/8130866F-591A-49C2-82E9-CC7561A5554A/SharePoint_Server_2016_Web_VPAT_081116.DOCX) + + + +## SharePoint Server 2013 conformance statement + +The SharePoint 2013 conformance statement is available at [Section 508 reports for Microsoft products](https://enterprise.microsoft.com/en-us/industries/government/section-508-vpats-for-microsoft-products/). +## Accessibility features in SharePoint Server + +Many of the accessibility features in SharePoint Online also apply to SharePoint Server 2016 and SharePoint 2013. For more information about these accessibility features, see the following topics: +- [Keyboard shortcuts](https://support.office.com/en-us/article/Keyboard-shortcuts-in-SharePoint-Online-466e33ee-613b-4f47-96bb-1c20f20b1015) + + +- [Using screen readers](https://support.office.com/en-us/article/Accessibility-features-in-SharePoint-Online-f291404a-dc7e-44de-a31f-d81b3099c2b9?ui=en-US&rs=en-US&ad=US&fromAR=1#bkm_moretasks) + + +- [Create accessible sites](https://support.office.com/en-us/article/Accessibility-features-in-SharePoint-Online-f291404a-dc7e-44de-a31f-d81b3099c2b9?ui=en-US&rs=en-US&ad=US&fromAR=1#bkm_accessiblesites) + + +- [Plan browser support in SharePoint Server 2016](html/plan-browser-support-in-sharepoint-server-2016.md) + + + +# See also + +#### + + [Microsoft accessibility](https://www.microsoft.com/en-us/accessibility/) + + + + [Accessibility features in SharePoint Online](https://support.office.com/en-us/article/Accessibility-features-in-SharePoint-Online-f291404a-dc7e-44de-a31f-d81b3099c2b9?ui=en-US&rs=en-US&ad=US&fromAR=1) + + + + [Accessibility support for enterprise](https://support.microsoft.com/en-us/accessibility/enterprise-answer-desk) + + + + + + + + diff --git a/SharePoint/account-permissions-and-security-settings-in-sharepoint-server-2016.md b/SharePoint/account-permissions-and-security-settings-in-sharepoint-server-2016.md new file mode 100644 index 0000000000..278df39ec1 --- /dev/null +++ b/SharePoint/account-permissions-and-security-settings-in-sharepoint-server-2016.md @@ -0,0 +1,392 @@ +--- +title: Account permissions and security settings in SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 55b99d80-3fa7-49f0-bdf4-adb5aa959019 +--- + + +# Account permissions and security settings in SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2016-12-30* **Summary:** Learn about the permissions and security settings to use with a deployment of SharePoint Server 2016.This article describes SharePoint administrative and services account permissions for the following areas: Microsoft SQL Server, the file system, file shares, and registry entries. +> [!IMPORTANT:] + + + + + +In this article: +- [About account permissions and security settings](#Section1) + + +- [Administrative accounts](#Section2) + + +- [Service application accounts](#Section3) + + +- [Database roles](#Section4) + + +- [Group permissions](#Section5) + + + +## About account permissions and security settings in SharePoint Server 2016 + + +The SharePoint Products Configuration Wizard (Psconfig) and the Farm Configuration Wizard, both of which are run during a complete installation, configure many of the SharePoint baseline account permissions and security settings. +## SharePoint administrative accounts + + +One of the following SharePoint components automatically configures most of the SharePoint administrative account permissions during the setup process: +- The SharePoint Products Configuration Wizard (Psconfig). + + +- The Farm Configuration Wizard. + + +- The SharePoint the SharePoint Central Administration website website. + + +- Microsoft PowerShell. + + + +## Setup user administrator account + +This account is used to set up each server in your farm by running the SharePoint Products Configuration Wizard, the initial Farm Configuration Wizard, and PowerShell. For the examples in this article, the setup user administrator account is used for farm administration, and you can use Central Administration to manage it. Some configuration options, for example, configuration of the SharePoint Server 2016 Search query server, require local administration permissions. The setup user administrator account requires the following permissions: +- It must have domain user account permissions. + + +- It must be a member of the local administrators group on each server in the SharePoint farm. + + +- This account must have access to the SharePoint databases. + + +- If you use any PowerShell operations that affect a database, the setup user administrator account must be a member of the **db_owner** role. + + +- This account must be assigned to the **securityadmin** and **dbcreator** SQL Server security roles during setup and configuration. + + + +> [!NOTE:] + + + + + +After you run the configuration wizards, machine-level permissions for the setup user administrator account include: +- Membership in the WSS_ADMIN_WPG Windows security group. + + +- Membership in the IIS_WPG role. + + +After you run the configuration wizards, database permissions include: +- **db_owner** on the SharePoint server farm configuration database. + + +- **db_owner** on the SharePoint Central Administration content database. + + + +> [!WARNING:] + + + + + + +## SharePoint farm service account + +The server farm account, which is also referred to as the database access account, is used as the application pool identity for Central Administration and as the process account for the SharePoint Foundation 2013 Timer service. The server farm account requires the following permissions: +- It must have domain user account permissions. + + +Additional permissions are automatically granted to the server farm account on web servers and application servers that are joined to a server farm.After you run Setup, machine-level permissions include: +- Membership in the WSS_ADMIN_WPG Windows security group for the SharePoint Foundation 2013 Timer service. + + +- Membership in WSS_RESTRICTED_WPG for the Central Administration and Timer service application pools. + + +- Membership in WSS_WPG for the Central Administration application pool. + + +After you run the configuration wizards, SQL Server and database permissions include: +- **Dbcreator** fixed server role. + + +- **Securityadmin** fixed server role. + + +- **db_owner** for all SharePoint databases. + + +- Membership in the WSS_CONTENT_APPLICATION_POOLS role for the SharePoint server farm configuration database. + + +- Membership in the WSS_CONTENT_APPLICATION_POOLS role for the SharePoint_Admin content database. + + + +## SharePoint service application accounts + + +This section describes the service application accounts that are set up by default during installation. +## Application pool account + +The application pool account is used for application pool identity. The application pool account requires the following permission configuration settings:The following machine-level permission is configured automatically: The application pool account is a member of WSS_WPG.The following SQL Server and database permissions for this account are configured automatically: +- The application pool accounts for Web applications are assigned to the SP_DATA_ACCESS role for the content databases. + + +- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role associated with the farm configuration database. + + +- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role associated with the SharePoint_Admin content database. + + + +## Default content access account + + +> [!IMPORTANT:] + + + + + +The default content access account is used within a specific service application to crawl content, unless a different authentication method is specified by a crawl rule for a URL or URL pattern. This account requires the following permission configuration settings: +- The default content access account must be a domain user account that has read access to external or secure content sources that you want to crawl by using this account. + + +- For SharePoint Server sites that are not part of the server farm, you have to explicitly grant this account full read permissions to the web applications that host the sites. + + +- This account must not be a member of the Farm Administrators group. + + + +## Content access accounts + + +> [!IMPORTANT:] + + + + + +Content access accounts are configured to access content by using the Search administration crawl rules feature. This type of account is optional, and you can configure it when you create a new crawl rule. For example, external content (such as a file share) might require this separate content access account. This account requires the following permission configuration settings: +- The content access account must have read access to external or secure content sources that this account is configured to access. + + +- For SharePoint Server sites that are not part of the server farm, you have to explicitly grant this account full read permissions to the web applications that host the sites. + + + +## My Sites application pool account + + +> [!IMPORTANT:] + + + + + +The My Sites application pool account must be a domain user account. This account must not be a member of the Farm Administrators group. The following machine-level permission is configured automatically: This account is a member of WSS_WPG.The following SQL Server and database permissions are configured automatically: +- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role that is associated with the farm configuration database. + + +- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role that is associated with the SharePoint_Admin content database. + + +- The application pool accounts for web applications are assigned to the SP_DATA_ACCESS role for the content databases + + + +## Other application pool accounts + +The other application pool account must be a domain user account. This account must not be a member of the Administrators group on any computer in the server farm.The following machine-level permission is configured automatically: This account is a member of WSS_WPG.The following SQL Server and database permissions are configured automatically: +- This account is assigned to the SP_DATA_ACCESS role for the content databases. + + +- This account is assigned to the SP_DATA_ACCESS role for search database that is associated with the web application. + + +- This account must have read and write access to the associated service application database. + + +- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role that is associated with the farm configuration database. + + +- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role that is associated with the SharePoint_Admin content database. + + + +## SharePoint database roles + + +This section describes the database roles that installation sets up by default or that you can configure optionally. +## WSS_CONTENT_APPLICATION_POOLS database role + +The WSS_CONTENT_APPLICATION_POOLS database role applies to the application pool account for each web application that is registered in a SharePoint farm. This enables web applications to query and update the site map and have read-only access to other items in the configuration database. Setup assigns the WSS_CONTENT_APPLICATION_POOLS role to the following databases: +- The SharePoint_Config database (the configuration database) + + +- The SharePoint_AdminContent database + + +Members of the WSS_CONTENT_APPLICATION_POOLS role have the execute permission for a subset of the stored procedures for the database. In addition, members of this role have the select permission to the Versions table (dbo.Versions) in the SharePoint_AdminContent database. For other databases, the accounts planning tool indicates that access to read these databases is automatically configured. In some cases, limited access to write to a database is also automatically configured. To provide this access, permissions for stored procedures are configured. +#### WSS_SHELL_ACCESS database role + +The secure WSS_SHELL_ACCESS database role on the configuration database replaces the need to add an administration account as a **db_owner** on the configuration database. By default, the setup account is assigned to the WSS_SHELL_ACCESS database role. You can use a PowerShell command to grant or remove memberships to this role. Setup assigns the WSS_SHELL_ACCESS role to the following databases: +- The SharePoint_Config database (the configuration database). + + +- One or more of the SharePoint Content databases. This is configurable by using the PowerShell command that manages membership and the object that is assigned to this role. + + +Members of the WSS_SHELL_ACCESS role have the execute permission for all stored procedures for the database. In addition, members of this role have the read and write permissions on all of the database tables. +##### SP_READ_ONLY database role +The **SP_READ_ONLY** role should be used for setting the database to read-only mode instead of using sp_dboption. This role as its name suggests should be used when only read access is required for data such as usage and telemetry data. +> [!NOTE:] + + + + + +The SP_READ_ONLY SQL role will have the following permissions: +- Grant SELECT on all SharePoint stored procedures and functions. + + +- Grant SELECT on all SharePoint tables. + + +- Grant EXECUTE on user-defined type where schema is dbo. + + + +##### SP_DATA_ACCESS database role +The **SP_DATA_ACCESS** role is the default role for database access and should be used for all object model level access to databases. Add the application pool account to this role during upgrade or new deployments. +> [!NOTE:] + + + + + +The SP_DATA_ACCESS role will have the following permissions: +- Grant EXECUTE or SELECT on all SharePoint stored procedures and functions. + + +- Grant SELECT on all SharePoint tables. + + +- Grant EXECUTE on User-defined type where schema is dbo. + + +- Grant INSERT on AllUserDataJunctions table. + + +- Grant UPDATE on Sites view. + + +- Grant UPDATE on UserData view. + + +- Grant UPDATE on AllUserData table. + + +- Grant INSERT and DELETE on NameValuePair tables. + + +- Grant create table permission. + + + +## Group permissions + + +This section describes permissions of groups that the SharePoint Server 2016 setup and configuration tools create. +## WSS_ADMIN_WPG + +WSS_ADMIN_WPG has read and write access to local resources. The application pool accounts for the Central Administration and Timer services are in WSS_ADMIN_WPG. The following table shows the WSS_ADMIN_WPG registry entry permissions. +### + +Key namePermissionsInheritDescriptionHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\VSS
Full control
Not applicable
Not applicable
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\16.0\\Registration\\{90150000-110D-0000-1000-0000000FF1CE}
Read, write
Not applicable
Not applicable
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office Server
Read
No
This key is the root of the SharePoint Server 2016 registry settings tree. If this key is altered, SharePoint Server 2016 functionality will fail.
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office Server\\16.0
Full control
No
This key is the root of the SharePoint Server 2016 registry settings.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\LoadBalancerSettings
Read, write
No
This key contains settings for the document conversion service. Altering this key will break document conversion functionality.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\LauncherSettings
Read, write
No
This key contains settings for the document conversion service. Altering this key will break document conversion functionality.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\Search
Full control
Not applicable
Not applicable
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\Search
Full control
Not applicable
Not applicable
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\Secure
Full control
No
This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server 2016 installation on the machine will not function.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\WSS
Full control
Yes
This key contains settings used during setup. If this key is altered, diagnostic logging might fail, and setup or post-setup configuration might fail.
The following table shows the WSS_ADMIN_WPG file system permissions. +### + +File system pathPermissionsInheritDescription%AllUsersProfile%\\ Microsoft\\SharePoint
Full control
No
This directory contains the file-system-backed cache of the farm configuration. Processes might fail to start, and the administrative actions might fail if this directory is altered or deleted.
C:\\Inetpub\\wwwroot\\wss
Full control
No
This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites. SharePoint sites will be unavailable, and administrative actions might fail if this directory is altered or deleted, unless custom IIS Web site paths are provided for all IIS Web sites extended with SharePoint Server 2016.
%ProgramFiles%\\Microsoft Office Servers\\16.0
Full control
No
This directory is the installation location for SharePoint Server 2016 binaries and data. The directory can be changed during installation. All SharePoint Server 2016 functionality will fail if this directory is removed, altered, or removed after installation. Membership in the WSS_ADMIN_WPG Windows security group is required for some SharePoint Server 2016 services to be able to store data on disk.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\WebServices
Read, write
No
This directory is the root directory where back-end Web services are hosted, for example, Excel and Search. The SharePoint Server 2016 features that depend on these services will fail if this directory is removed or altered.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\Data
Full control
No
This directory is the root location where local data is stored, including search indexes. Search functionality will fail if this directory is removed or altered. WSS_ADMIN_WPG Windows security group permissions are required to enable search to save and secure data in this folder.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\Logs
Full control
Yes
This directory is the location where the run-time diagnostic logging is generated. Logging functionality will not function properly if this directory is removed or altered.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\Data\\Office Server
Full control
Yes
Same as the parent folder.
%windir%\\System32\\drivers\\etc\\HOSTS
Read, write
Not applicable
Not applicable
%windir%\\Tasks
Full control
Not applicable
Not applicable
%COMMONPROGRAMFILES%Microsoft Shared\\Web Server Extensions\\16
Modify
Yes
This directory is the installation directory for core SharePoint Server 2016 files. If the access control list (ACL) is modified, feature activation, solution deployment, and other features will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\ADMISAPI
Full control
Yes
This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\CONFIG
Full control
Yes
This directory contains files used to extend IIS Web sites with SharePoint Server 2016. If this directory or its contents are altered, web application provisioning will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\LOGS
Full control
No
This directory contains setup and runtime tracing logs. If the directory is altered, diagnostic logging will not function correctly.
%windir%\\temp
Full control
Yes
This directory is used by platform components on which SharePoint Server 2016 depends. If the access control list is modified, Web Part rendering and other deserialization operations might fail.
%windir%\\System32\\logfiles\\SharePoint
Full control
No
This directory is used by SharePoint Server usage logging. If this directory is modified, usage logging will not function correctly.
This registry key applies only to SharePoint Server.
%systemdrive\\program files\\Microsoft Office Servers\\16 folder on Index servers
Full control
Not applicable
This permission is granted for a %systemdrive\\program files\\Microsoft Office Servers\\16 folder on Index servers.
+## WSS_WPG + +WSS_WPG has read access to local resources. All application pool and services accounts are in WSS_WPG. The following table shows WSS_WPG registry entry permissions. +### + +Key namePermissionsInheritDescriptionHKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office Server\\16.0
Read
No
This key is the root of the SharePoint Server 2016 registry settings.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\Diagnostics
Read, write
No
This key contains settings for the SharePoint Server 2016 diagnostic logging. Altering this key will break the logging functionality.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\LoadBalancerSettings
Read, write
No
This key contains settings for the document conversion service. Altering this key will break document conversion functionality.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\LauncherSettings
Read, write
No
This key contains settings for the document conversion service. Altering this key will break document conversion functionality.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\Secure
Read
No
This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server 2016 installation on the machine will not function.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\WSS
Read
Yes
This key contains settings that are used during setup. If this key is altered, diagnostic logging might fail and setup or post-setup configuration mightay fail.
The following table shows the WSS_WPG file system permissions. +### + +File system pathPermissionsInheritDescription%AllUsersProfile%\\ Microsoft\\SharePoint
Read
No
This directory contains the file-system-backed cache of the farm configuration. Processes might fail to start and the administrative actions might fail if this directory is altered or deleted.
C:\\Inetpub\\wwwroot\\wss
Read, execute
No
This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites. SharePoint sites will be unavailable and administrative actions might fail if this directory is altered or deleted, unless custom IIS Web site paths are provided for all IIS Web sites extended with SharePoint Server 2016.
%ProgramFiles%\\Microsoft Office Servers\\16.0
Read, execute
No
This directory is the installation location for the SharePoint Server 2016 binaries and data. It can be changed during installation. All SharePoint Server 2016 functionality will fail if this directory is removed, altered, or moved after installation. WSS_WPG read and execute permissions are required to enable IIS sites to load SharePoint Server 2016 binaries.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\WebServices
Read
No
This directory is the root directory where back-end Web services are hosted, for example, Excel and Search. The SharePoint Server 2016 features that depend on these services will fail if this directory is removed or altered.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\Logs
Read, write
Yes
This directory is the location where the runtime diagnostic logging is generated. Logging functionality will not function properly if this directory is removed or altered.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\ADMISAPI
Read
Yes
This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\CONFIG
Read
Yes
This directory contains files used to extend IIS Web sites with SharePoint Server 2016. If this directory or its contents are altered, web application provisioning will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\LOGS
Modify
No
This directory contains setup and runtime tracing logs. If the directory is altered, diagnostic logging will not function correctly.
%windir%\\temp
Read
Yes
This directory is used by platform components on which SharePoint Server 2016 depends. If the access control list is modified, Web Part rendering, and other deserialization operations might fail.
%windir%\\System32\\logfiles\\SharePoint
Read
No
This directory is used by SharePoint Server usage logging. If this directory is modified, usage logging will not function correctly.
The registry key applies only to SharePoint Server.
%systemdrive\\program files\\Microsoft Office Servers\\16
Read, execute
Not applicable
The permission is granted for %systemdrive\\program files\\Microsoft Office Servers\\16 folder on Index servers.
+## Local service + +The following table shows the local service registry entry permission: +### + +Key namePermissionsInheritDescriptionHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\LoadBalancerSettings
Read
No
This key contains settings for the document conversion service. Altering this key will break document conversion functionality.
The following table shows the local service file system permission: +### + +File system pathPermissionsInheritDescription%ProgramFiles%\\Microsoft Office Servers\\16.0\\Bin
Read, execute
No
This directory is the installed location of the SharePoint Server 2016 binaries. All the SharePoint Server 2016 functionality will fail if this directory is removed or altered.
+## Local system + +The following table shows the local system registry entry permissions: +### + +Key namePermissionsInheritDescriptionHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\LauncherSettings
Read
No
This key contains settings for the document conversion service. Altering this key will break document conversion functionality.
This registry key applies only to SharePoint Server.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\Secure
Full control
No
This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server 2016 installation on the machine will not function.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\Secure\\FarmAdmin
Full control
No
This key contains the encryption key that is used to store secrets in the configuration database. If this key is altered, service provisioning and other features will fail.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\WSS
Full control
Yes
This key contains settings that are used during setup. If this key is altered, diagnostic logging might fail and setup or post-setup configuration might fail.
The following table shows the local file system permissions: +### + +File system pathPermissionsInheritDescription%AllUsersProfile%\\ Microsoft\\SharePoint
Full control
No
This directory contains the file-system-backed cache of the farm configuration. Processes might fail to start and administrative actions might fail if this directory is altered or deleted.
C:\\Inetpub\\wwwroot\\wss
Full control
No
This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites. SharePoint sites will be unavailable and administrative actions might fail if this directory is altered or deleted, unless custom IIS Web site paths are provided for all IIS Web sites extended with SharePoint Server 2016.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\ADMISAPI
Full control
Yes
This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\CONFIG
Full control
Yes
If this directory or its contents are altered, Web Application provisioning will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\LOGS
Full control
No
This directory contains setup and run-time tracing logs. If the directory is altered, diagnostic logging will not function correctly.
%windir%\\temp
Full control
Yes
This directory is used by platform components on which SharePoint Server 2016 depends. If the access control list is modified, Web Part rendering, and other deserialization operations might fail.
%windir%\\System32\\logfiles\\SharePoint
Full control
No
This directory is used by SharePoint Server for usage logging. If this directory is modified, usage logging will not function correctly.
This registry key applies only to SharePoint Server.
+## Network service + +The following table shows the network service registry entry permission: +### + +Key namePermissionsInheritDescriptionHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office Server\\16.0\\Search\\Setup
Read
Not applicable
Not applicable
+## Administrators + +The following table shows the administrators registry entry permissions: +### + +Key namePermissionsInheritDescriptionHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\Secure
Full control
No
This key contains the connection string and the ID of the configuration database to which the machine is joined. If this key is altered, the SharePoint Server 2016 installation on the machine will not function.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\Secure\\FarmAdmin
Full control
No
This key contains the encryption key that is used to store secrets in the configuration database. If this key is altered, service provisioning and other features will fail.
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\WSS
Full control
Yes
This key contains settings that are used during setup. If this key is altered, diagnostic logging might fail and setup or post-setup configuration might fail.
The following table shows the administrators file system permissions: +### + +File system pathPermissionsInheritDescription%AllUsersProfile%\\ Microsoft\\SharePoint
Full control
No
This directory contains the file-system-backed cache of the farm configuration. Processes might fail to start and administrative actions might fail if this directory is altered or deleted.
C:\\Inetpub\\wwwroot\\wss
Full Control
No
This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites. SharePoint sites will be unavailable and administrative actions might fail if this directory is altered or deleted, unless custom IIS web site paths are provided for all IIS web sites that are extended with SharePoint Server 2016.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\ADMISAPI
Full control
Yes
This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\CONFIG
Full control
Yes
If this directory or its contents are altered, web application provisioning will not function correctly.
%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\LOGS
Full control
No
This directory contains setup and run-time tracing logs. If the directory is altered, diagnostic logging will not function correctly.
%windir%\\temp
Full control
Yes
This directory is used by platform components on which SharePoint Server 2016 depends. If the ACL is modified, Web Part rendering, and other deserialization operations might fail.
%windir%\\System32\\logfiles\\SharePoint
Full control
No
This directory is used by SharePoint Server for usage logging. If this directory is modified, usage logging will not function correctly.
This registry key applies only to SharePoint Server.
+## WSS_RESTRICTED_WPG + +WSS_RESTRICTED_WPG can read the encrypted farm administration credential registry entry. WSS_RESTRICTED_WPG is only used for encryption and decryption of passwords that are stored in the configuration database. The following table shows the WSS_RESTRICTED_WPG registry entry permission: +### + +Key namePermissionsInheritDescriptionHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Shared Tools\\Web Server Extensions\\16.0\\Secure\\FarmAdmin
Full control
No
This key contains the encryption key that is used to store secrets in the configuration database. If this key is altered, service provisioning and other features will fail.
+## Users group + +The following table shows the users group file system permissions: +### + +File system pathPermissionsInheritDescription%ProgramFiles%\\Microsoft Office Servers\\16.0
Read, execute
No
This directory is the installation location for SharePoint Server 2016 binaries and data. It can be changed during installation. All SharePoint Server 2016 functionality will fail if this directory is removed, altered, or moved after installation.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\WebServices\\Root
Read, execute
No
This directory is the root directory where back-end root Web services are hosted. The only service initially installed on this directory is a search global administration service. Some search administration functionality that uses the server-specific Central Administration Settings page will not work if this directory is removed or altered.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\Logs
Read, write
Yes
This directory is the location where the run-time diagnostic logging is generated. Logging will not function properly if this directory is removed or altered.
%ProgramFiles%\\Microsoft Office Servers\\16.0\\Bin
Read, execute
No
This directory is the installed location of SharePoint Server 2016 binaries. All of the SharePoint Server 2016 functionality will fail if this directory is removed or altered.
+## All SharePoint Server 2016 service accounts + +The following table shows the all SharePoint Server 2016 service accounts file system permission: +### + +File system pathPermissionsInheritDescription%COMMONPROGRAMFILES%\\Microsoft Shared\\Web Server Extensions\\16\\LOGS
Modify
No
This directory contains setup and run-time tracing logs. If this directory is altered, diagnostic logging will not function correctly. All SharePoint Server 2016 service accounts must have write permission to this directory.
+# See also + +#### + + [Install and configure SharePoint Server 2016](html/install-and-configure-sharepoint-server-2016.md) + + + + + + + + diff --git a/SharePoint/accounts-needed-for-hybrid-configuration-and-testing.md b/SharePoint/accounts-needed-for-hybrid-configuration-and-testing.md new file mode 100644 index 0000000000..050389afd1 --- /dev/null +++ b/SharePoint/accounts-needed-for-hybrid-configuration-and-testing.md @@ -0,0 +1,19 @@ +--- +title: Accounts needed for hybrid configuration and testing +ms.prod: SHAREPOINT +ms.assetid: c824fa0f-bae9-4791-92ee-38d8e70140ec +--- + + +# Accounts needed for hybrid configuration and testing + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-20* **Summary:** Learn about the accounts you need to use when you configure a SharePoint Server hybrid solution.When you configure a SharePoint Server hybrid environment, you need several user accounts in both your on-premises Active Directory and Office 365. These accounts also need different permissions and group or role memberships. Some of these accounts are used to deploy and configure software, and some are used to test specific functionality to help ensure that security and authentication systems are working as expected.In a hybrid environment, some or all user accounts in Active Directory are synchronized with Azure AD directory services. We refer to these accounts as *federated users* . SharePoint Server and SharePoint Online are configured with a server-to-server (S2S) trust relationship, and service applications can be configured to enable federated users to access content and resources from both farms using a single identity. Because user accounts and credentials are synchronized between SharePoint Server and SharePoint Online, list and library content security can be applied in both farms using the same set of users and groups. +> [!NOTE:] + + + + + + +### Table: Accounts needed for SharePoint hybrid configuration and testing + +AccountIdentity providerRoleGlobal Administrator
Office 365 and Azure Active Directory
Use an Office 365 work account that has been assigned to the Global Administrator role for Office 365 configuration tasks such as configuring SharePoint Online features, running Azure AD and SharePoint Online PowerShell commands, and testing SharePoint Online.
AD Domain Administrator
On-premises AD
Use an AD account in the Domain Admins group to configure and test AD, ADFS, DNS, and certificates and to do other tasks that require elevation.
SharePoint Farm Administrator
On-premises AD
Use an AD account in the Farm Administrators SharePoint group for SharePoint Server configuration tasks such as running PowerShell commands in the SharePoint Management Shell to configure S2S trusts, create and configure web applications and site collections, deploy and configure SQL Server databases, and troubleshoot SharePoint Server.
This account must also have additional privileges to use the SharePoint Management Shell:
Membership in the **securityadmin** fixed server role on the SQL Server instance.
Membership in the **db_owner** fixed database role on all databases that are to be updated.
Membership in the Administrators group on the server on which you are running the PowerShell cmdlets.
Federated Users
On-premises AD
Use AD accounts that have been synchronized with Office 365 to test access to specific resources in both SharePoint Server and SharePoint Online.
These accounts, or groups of which they are members, must have permissions to SharePoint Server site collections and resources in both environments and have the appropriate product licenses assigned in the Office 365 subscription. They also must be set to use the alternative domain UPN suffix that you specify for federated users during the planning process.
You can configure multiple federated accounts with different permissions or group memberships to test for appropriate security trimming and access to site resources.
diff --git a/SharePoint/accounts-used-by-application-pools-or-service-identities-are-in-the-local-machin.md b/SharePoint/accounts-used-by-application-pools-or-service-identities-are-in-the-local-machin.md new file mode 100644 index 0000000000..bd36bb2b19 --- /dev/null +++ b/SharePoint/accounts-used-by-application-pools-or-service-identities-are-in-the-local-machin.md @@ -0,0 +1,25 @@ +--- +title: Accounts used by application pools or service identities are in the local machine Administrators group (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: 5f0f9910-d851-4ffa-832b-f47558e4758c +--- + + +# Accounts used by application pools or service identities are in the local machine Administrators group (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "Accounts used by application pools or service identities are in the local machine Administrators group" for SharePoint Server 2016. **Rule Name:**   Accounts used by application pools or service identities are in the local machine Administrators group. **Summary:**   A user account that is used by application pools or services must have permissions of a domain user account and must not be a member of the Farm Administrators group or a member of the Administrators group on the local computer. Using highly privileged accounts for application pools or services poses a security risk to the farm, and could allow malicious code to execute. **Cause:**   Accounts that are used by application pools or services are members of the Administrators group on the local computer. **Resolution: Change the user account to a predefined account, or to a domain user account that is not a member of the Administrators group.** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. On the Central Administration home page, in the **Security** section, click **Configure service accounts**. + + +3. On the Service Accounts page, in the **Select the component to update** list, click the application pool or service that uses the credentials of a member of the Administrators group on the local computer as its security account. + + +4. In the **Select an account** list, click an appropriate account for this component — for example, the predefined account  **Network Service**  — or click **Register new managed account**, and then on the Register Managed Account page, specify the credentials and the password change settings that you want. + + +5. Click **OK**. + + +For more information, see [Account permissions and security settings in SharePoint Server 2016](html/account-permissions-and-security-settings-in-sharepoint-server-2016.md). diff --git a/SharePoint/add-apps-for-sharepoint-to-a-sharepoint-site.md b/SharePoint/add-apps-for-sharepoint-to-a-sharepoint-site.md new file mode 100644 index 0000000000..84de963134 --- /dev/null +++ b/SharePoint/add-apps-for-sharepoint-to-a-sharepoint-site.md @@ -0,0 +1,115 @@ +--- +title: Add apps for SharePoint to a SharePoint site +ms.prod: SHAREPOINT +ms.assetid: 57d52c9e-5069-4bcf-87e3-24482198a462 +--- + + +# Add apps for SharePoint to a SharePoint site + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Site owners can add apps for SharePoint to SharePoint sites so that they and other users of the site can use the app.Site owners can add apps for SharePoint from the SharePoint Store or an App Catalog to their sites. Adding an app installs an instance of that app to the site. This article covers how to add apps to your sites.Be sure you've [configured your environment for SharePoint apps](html/configure-an-environment-for-apps-for-sharepoint-server.md) before you get started. +## Add apps for SharePoint to SharePoint sites + +Site owners can add apps for SharePoint from the following sources to their sites: +- from the list of apps already available for a site (default apps, such as standard lists and libraries, and apps that have been purchased already). + + +- from the App Catalog. + + +- from the SharePoint Store. + + +Note that a user logged in as teh system account cannot install a app.When you add an app for SharePoint, the app requests permissions that it needs to function (for example, access to Search, or to create a list). If you don't have those permissions, the app won't install. Contact your administrator to get the needed permissions or have someone with those permissions add the app.The following procedures provide steps for adding apps from these sources. **To add an app from the list of available apps in a site** +1. Verify that the user account that is performing this procedure is a member of the site Owners group. + + +2. On the home page, under **Get started with your site**, click **Add lists, libraries, and other apps.** + + If the Get started with your site control does not appear on the home page, click the **Settings** icon, and click **View Site Contents**, and then on the **Site Contents** page, click **Add an App**. + + +3. In the Your Apps list, click the app you want to add. + + +4. Follow the instructions to Trust the app (if it is a custom component) or Name the app (if it is a SharePoint component). + + The app for SharePoint is added and appears in the **Apps** section of your Site Contents list. + + + **To add an app from an App Catalog** +1. Verify that the user account that is performing this procedure is a member of the site Owners group. + + +2. On the home page, under **Get started with your site**, click **Add lists, libraries, and other apps.** + + If the Get started with your site control does not appear on the home page, click the Settings icon, and click **View Site Contents**, and then on the Site Contents page, click **Add an App**. + + +3. Click **From** *Name* . + + Where *Name* is the name of your organization's App Catalog. For example, "From Contoso". + + > [!TIP:] + +4. Click the app you want to add. + + +5. In the Grant Permission to an App dialog box, if you trust the app, click **Allow Access**. + + The app for SharePoint is added and appears in Apps section of your Site Contents list. + + + **To add an app from the SharePoint Store** +1. Verify that the user account that is performing this procedure is a member of the site Owners group. + + +2. On the home page, under **Get started with your site**, click **Add lists, libraries, and other apps.** + + If the Get started with your site control does not appear on the home page, click the Settings icon, and click **View Site Contents**, and then on the Site Contents page, click **Add an App**. + + +3. Click **SharePoint Store**. + + +4. Browse the SharePoint Store to find an app that you want. + + +5. Click the app you want to add. + + +6. Click Details, and then click **Buy It**. + + +7. Follow the steps to log in and purchase the app, if required. + + +8. In the **Grant Permission to an App** dialog box, if you trust the app, click **Allow Access**. + + The app for SharePoint is added and appears in the Apps section of your Site Contents list. + + + +# See also + +#### + + [Install and manage apps for SharePoint Server](html/install-and-manage-apps-for-sharepoint-server.md) + + + + +#### + + **Import-SPAppPackage** + + + + **Install-SPApp** + + + + + + + + diff --git a/SharePoint/add-content-databases-in-sharepoint-server.md b/SharePoint/add-content-databases-in-sharepoint-server.md new file mode 100644 index 0000000000..0ea265b4f0 --- /dev/null +++ b/SharePoint/add-content-databases-in-sharepoint-server.md @@ -0,0 +1,149 @@ +--- +title: Add content databases in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 0889004d-6820-4282-a63c-863f4796ff85 +--- + + +# Add content databases in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Search Server 2013, SharePoint Foundation 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-21* **Summary:** Learn how to add a content database to your SharePoint Server 2016 and SharePoint Server 2013 farm.You can add a content database to a SharePoint Server farm by using the SharePoint Central Administration website or Microsoft PowerShell. The tool that you use depends on the kind of environment that you have deployed, your schedule requirements, and service level agreements that you have made with your organization.In this article: +- [Before you begin](#begin) + + +- [Adding a content database to a SharePoint Server web application](#proc1) + + - [To add a content database to a web application by using Central Administration](#CA) + + + - [To add a content database to a web application by using Windows PowerShell](#PS) + + + +## Before you begin + + +You can add a new content database or attach an existing content database from a backup file.Before you begin this operation, review the following information about prerequisites: +- The user account that is performing this operation must be a member of the Farm Administrators SharePoint group. + + +- If you use Windows authentication to connect to SQL Server, the user account must be a member of the **dbcreator** fixed server role on the SQL Server instance where the database is to be created. + + + +## Adding a content database to a SharePoint Server web application + + +You can use the procedures that are described in this article to create a new content database and attach it to a web application. If you are using Windows authentication to connect to SQL Server, the user account must also be a member the SQL Server **dbcreator** fixed server role on the SQL Server instance where the database will be created. If you are using SQL authentication to connect to SQL Server, the SQL authentication account that you specify when you create the content database must have **dbcreator** permission on the SQL Server instance where the database will be created. **To add a content database to a web application by using Central Administration** +1. Verify that the user account that is performing this operation is a member of the Farm Administrators SharePoint group. + + +2. Start Central Administration. + + +3. On the SharePoint Central Administration website, click **Application Management**. + + +4. In the **Databases** section, click **Manage content databases**. + + +5. On the **Manage Content Databases** page, click **Add a content database**. + + +6. On the **Add Content Database** page: + +1. Specify a web application for the new database. + + +2. Specify a database server to host the new database. + + +3. Specify the authentication method that the new database will use and supply an account name and password, if they are necessary. + + + + > [!IMPORTANT:] + +4. Specify the name of the failover database server, if one exists. + + +5. Specify the number of top-level sites that can be created before a warning is issued. By default, this is 2,000. + + +6. Specify the total number of top-level sites that can be created in the database. By default, this is 5,000. + + + + +7. Click **OK**. + + + **To add a content database to a web application by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2016 cmdlets. + + > [!NOTE:] + +2. Open **SharePoint Management Shell**. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +New-SPContentDatabase -Name -WebApplication + ``` + + + + + Where: + + - ** is the name of the content database to create. + + + - ** is the name of the web application to which the new database is attached. + + +For more information, see **New-SPContentDatabase**. +> [!NOTE:] + + + + + + +> [!NOTE:] + + + + + + +# See also + +#### + + [Attach or detach content databases in SharePoint Server](html/attach-or-detach-content-databases-in-sharepoint-server.md) + + + + [Move site collections between databases in SharePoint Server](html/move-site-collections-between-databases-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/add-edit-or-delete-a-content-source-in-sharepoint-server.md b/SharePoint/add-edit-or-delete-a-content-source-in-sharepoint-server.md new file mode 100644 index 0000000000..f68498de75 --- /dev/null +++ b/SharePoint/add-edit-or-delete-a-content-source-in-sharepoint-server.md @@ -0,0 +1,112 @@ +--- +title: Add, edit, or delete a content source in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: f687788b-f9b6-4a63-94d2-008939108c65 +--- + + +# Add, edit, or delete a content source in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Learn how to create a content source to specify what type of content to crawl, schedules for crawling, start addresses, and crawl priority.A *content source* is a set of options that you use to specify what, when, and how to crawl.When a Search service application is created, a content source named "Local SharePoint sites" is automatically created and configured for crawling all SharePoint Server sites in the local server farm. You can create additional content sources to specify other content to crawl and how the system should crawl that content. After you create a content source, you can edit or delete it at any time. +> [!WARNING:] + + + + + +In this article: +- [Before you begin](#begin) + + +- [To create a content source](#proc2) + + +- [To edit a content source](#proc3) + + +- [To delete a content source](#proc4) + + + +## Before you begin + + +Before you begin this operation, review the following information about prerequisites: +- Create a Search service application + + + +## Create, edit, or delete a content source + + + **To get to the Manage Content Sources page** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. On the home page of the SharePoint Server Central Administration website, in the **Application Management** section, click **Manage service applications**. + + +3. On the Manage Service Applications page, click the Search service application. + + +4. On the Search Administration Page, in the **Crawling** section, click **Content Sources**. + + + +## + + + **To create a content source** +1. On the Manage Content Sources page, click **New Content Source**. + + +2. On the Add Content Source page, in the **Name** section, in the **Name** box, type a name for the new content source. + + +3. In the **Content Source Type** section, select the type of content that you want to crawl. + + +4. In the **Start Addresses** section, in the **Type start addresses below (one per line)** box, type the URLs from which the crawler should begin crawling. + + +5. In the **Crawl Settings** section, select the crawling behavior that you want. + + +6. In the **Crawl Schedules** section, to specify a schedule for full crawls, select a defined schedule from the **Full Crawl** list. A full crawl crawls all content that is specified by the content source, regardless of whether the content has changed. To define a full crawl schedule, click **Create schedule**. + + +7. To specify a schedule for incremental crawls, select a defined schedule from the **Incremental Crawl** list. An incremental crawl crawls content that is specified by the content source that has changed since the last crawl. To define a schedule, click **Create schedule**. You can change a defined schedule by clicking **Edit schedule**. + + > [!NOTE:] + +8. To set the priority of this content source, in the **Content Source Priority** section, on the **Priority** list, select **Normal** or **High**. + + +9. Click **OK**. + + + +## + + + **To edit a content source** +1. You can edit a content source to change the schedule on which the content is crawled, the crawl start addresses, the content source priority, or the name of the crawl. Crawl settings and content source type cannot be changed when you edit a content source. + + +2. On the Manage Content Sources page, in the list of content sources, point to the name of the content source that you want to edit, click the arrow that appears, and then click **Edit**. + + +3. After you make the changes that you want, click **OK**. + + + +## + + + **To delete a content source** +1. On the Manage Content Sources page, in the list of content sources, point to the name of the content source that you want to delete, click the arrow that appears, and then click **Delete**. + + +2. Click **OK** to confirm that you want to delete this content source. + + + diff --git a/SharePoint/add-edit-or-delete-custom-properties-in-sharepoint-server-user-profiles.md b/SharePoint/add-edit-or-delete-custom-properties-in-sharepoint-server-user-profiles.md new file mode 100644 index 0000000000..9bd169f697 --- /dev/null +++ b/SharePoint/add-edit-or-delete-custom-properties-in-sharepoint-server-user-profiles.md @@ -0,0 +1,150 @@ +--- +title: Add, edit, or delete custom properties in SharePoint Server user profiles +ms.prod: SHAREPOINT +ms.assetid: 3cfb2148-9d1a-4022-a55a-a6d2963bef0e +--- + + +# Add, edit, or delete custom properties in SharePoint Server user profiles + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-08-02* **Summary:** Learn how to create, edit, and delete user profile properties in SharePoint Server 2013 and SharePoint Server 2016.The **Manage Profile Service** page of a User Profile service application in SharePoint Server is a central location for managing available user profile properties and creating new properties. You need to be a member of the Farm Administrators SharePoint group or a Service Application Administrator for the User Profile service application to make changes.You can supplement default user profile properties with additional properties to track key information that is not otherwise available. Key business needs might encourage you to create new properties that associate users with important business processes. For example, a sales department can create a specific sales role property to share with a particular audience or audiences. Custom user profile properties can be edited to better suit business needs or they can be deleted when no longer needed.In this article: +- [Create a user profile property](#create) + + +- [Edit a user profile property](#edit) + + +- [Delete a user profile property](#delete) + + + +## Add a user profile property + + +Perform the following procedure to create a user profile property. **To create a new user profile property** +1. On Central Administration, in the **Application Management** section, click **Manage service applications**. + + +2. On the **Manage Service Applications** page, click the link for the User Profile service application. + + +3. On the **Manage Profile Service** page, in the **People** section, click **Manage User Properties**. + + +4. On the **Manage User Profile Properties** page, click **New Property**. + + +5. On the **Add User Profile Property** page, in the **Property Settings** section, in the **Name** text box, type a name to be used by the User Profile service application for the user profile property. + + +6. In the **Property Settings** section, in the **Display Name** box, type the user profile property name that will be displayed to all users. + + > [!NOTE:] + +7. On the **Type** drop-down list, click the data type for the property. + + > [!NOTE:] + +8. In the **Length** box, type the maximum number of characters that are allowed for values for this property. + + +9. Click to select **Configure a Term Set to be used for this property** to associate the profile property with a managed metadata term set and select a term set from the drop-down list. + + +10. In the **Sub-type of Profile** section, select the **Default User Profile Subtype** to associate the default user profile subtype with this user profile property. + + +11. In the **User Description** section, in the **Description** box, type the instructions or information that is displayed to users about this user profile property. + + > [!NOTE:] + +12. In the **Policy Settings** section, select the policy setting and default privacy setting that you want for this property. Click to select **User can override box** to enable users to override these settings. + + +13. In the **Edit Settings** section, select whether users can edit values for this property. + + +14. In the **Display Settings** section, specify if and how the property will be viewed by users. + + +15. In the **Search Settings** section, select the **Alias** check box, the **Indexed** check box, or both, depending on the kinds of searches that you want to be associated with this user profile property. + + > [!NOTE:] + + + > [!NOTE:] + +16. In the **Property Mapping for Synchronization** section, click **Remove** to delete or change an existing mapping. + + +17. In the **Add new Mapping** section, specify the source data connection, attribute, and synchronization direction for the mapping. When you are finished, click **Add**. + + +18. Click **OK**. + + + +## Edit a user profile property + + +Perform the following procedure to edit a user profile property. **To edit a user profile property** +1. On Central Administration, in the **Application Management** section, click **Manage service applications**. + + +2. On the **Manage Service Applications** page, click the link for the User Profile service application. + + +3. On the **Manage Profile Service** page, in the **People** section, click **Manage User Properties**. + + +4. On the **Manage User Profile Properties** page, in the **Property Name** column, select the user profile property that you want to change, and then, in the dropdown menu, click **Edit**. + + +5. On the **Edit User Profile Property** page, locate the element or elements of the user profile property that you want to change and edit them. + + +6. When you are finished, click **OK**. + + + +## Delete a user profile property + + +Perform the following procedure to delete a user profile property. **To delete a user profile property profile property by using Central Administration** +1. On Central Administration, in the **Application Management** section, click **Manage service applications**. + + +2. On the **Manage Profile Service** page, in the **People** section, click **Manage User Properties**. + + +3. On the **Manage User Profile Properties** page, in the **Property Name** column, select the user profile property that you want to remove, and then, in the dropdown menu, click **Delete**. + + +4. In the dialog box, verify that you have selected the correct user profile property, and then click **OK**. + + + +# See also + +#### + + [Administer the User Profile service in SharePoint Server](html/administer-the-user-profile-service-in-sharepoint-server.md) + + + + [Plan profile synchronization for SharePoint Server 2013](html/plan-profile-synchronization-for-sharepoint-server-2013.md) + + + + [Delegate administration of User Profile service applications or features in SharePoint Server](html/delegate-administration-of-user-profile-service-applications-or-features-in-shar.md) + + + + [Overview of the User Profile service architecture in SharePoint Server](html/overview-of-the-user-profile-service-architecture-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/add-or-remove-a-file-type-from-the-search-index-in-sharepoint-server.md b/SharePoint/add-or-remove-a-file-type-from-the-search-index-in-sharepoint-server.md new file mode 100644 index 0000000000..c338d44b70 --- /dev/null +++ b/SharePoint/add-or-remove-a-file-type-from-the-search-index-in-sharepoint-server.md @@ -0,0 +1,402 @@ +--- +title: Add or remove a file type from the search index in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 7d88430f-2f0f-4c83-863b-ad840bdbf696 +--- + + +# Add or remove a file type from the search index in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Learn how to add or remove a file type from the search index and how to start or stop including content from the file type, in the search index.Before you start, you may want to read [Default crawled file name extensions and parsed file types in SharePoint Server](html/default-crawled-file-name-extensions-and-parsed-file-types-in-sharepoint-server.md). This article lists the file types that SharePoint Server 2016 by default includes in the search index.If your SharePoint Server environment is hybrid and uses [cloud hybrid search](https://support.office.com/en-us/article/Learn-about-cloud-hybrid-search-for-SharePoint-af830951-8ddf-48b2-8340-179c1cc4d291), you can decide what types of files that are stored in SharePoint Server that you want to add or remove from the Office 365 index. Use the following procedures on the server that hosts the crawl component in the cloud Search service application. To add or remove a file type from the search index: +1. Add or remove the file name extension from the list of file name extensions on the Manage File Types page. See [Add or remove file name extensions from the Manage File Types page](#proc1). + + +2. Run a full crawl for all content sources that this change might affect. + + +When the full crawl finishes, the search index will include or exclude properties from files of the type that you have either added or removed.To start including content from a file type, in the search index: +1. On a server that hosts a content processing component in the Search service application, check whether the format of the file type is supported by a built-in format handler or a third-party filter-based format handler (iFilter). Built-in format handlers are the those that SharePoint Server has by default. See [View information about file formats that can be parsed](#ViewInformationFileFormats). + + +2. If the server does not have a format handler for the file type, install a third-party filter-based format handler on all servers hosting content processing components in the Search service application. Follow the installation guidance given by the manufacturer of the third-party format handler. + + +3. On all servers that host a content processing component in the Search service application, enable parsing of the format of the file and the file name extension. See [Enable or disable parsing of a file format](#EnbleParsing). + + +4. Run a full crawl for all content sources that this change might affect. + + +When the full crawl finishes, the search index will include content from files of the type that you enabled.To stop including content from a file type, in the search index: +1. On a server that hosts a content processing component in the Search service application, check whether the format of the file type is supported by a built-in format handler or a third-party filter-based format handler (iFilter). Built-in format handlers are those that SharePoint Server has by default. + + +2. On all servers that host a content processing component in the Search service application, disable parsing of the format of the file and the file name extension. See [Enable or disable parsing of a file format](#EnbleParsing). + + +3. Run a full crawl for all content sources that this change might affect. + + +When the full crawl finishes, the search index will exclude content from files of the type that you disabled.In this article: +- [Before you begin](#begin) + + +- [Add or remove file name extensions from the Manage File Types page](#proc1) + + +- [View information about file formats that can be parsed](#ViewInformationFileFormats) + + +- [Enable or disable parsing of a file format](#EnbleParsing) + + + +## Before you begin + + + +> [!NOTE:] +> [Plan browser support](https://go.microsoft.com/fwlink/p/?LinkId=246502)> **Accessibility for SharePoint 2013**> [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)> [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504)> [Touch](https://go.microsoft.com/fwlink/p/?LinkId=246506) + + + + +Before you begin this operation, review the following information about prerequisites: +- Create a Search service application + + + +## Add or remove file name extensions from the Manage File Types page + + + +## + + **To add a file name extension to the Manage File Types page** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. In Central Administration, in the Application Management section, click **Manage Service Applications**. + + +3. On the Manage Service Applications page, in the list of service applications, click the Search service application. + + +4. On the Search Administration page, in the Crawling section, click **File types**. The Manage File Types page appears. + + +5. Click **New File Type**. + + +6. In the **File extension** box, type the extension of the file type that you want to add. + + +7. Click **OK**. + + +8. **Verification:** make sure that the extension appears in the list of file types on the Manage File Types page. + + + +## + + **To remove a file name extension from the Manage File Types page** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. In Central Administration, in the Application Management section, click **Manage Service Applications**. + + +3. On the Manage Service Applications page, in the list of service applications, click the Search service application. + + +4. On the Search Administration page, in the Crawling section, click **File types**. The Manage File Types page appears. + + +5. Point to the file type that you want to remove, click the arrow that appears and then click **Delete**. + + +6. Click **OK** to confirm that you want to delete the file type. + + +7. **Verification:** make sure that the extension no longer appears in the list of file types on the Manage File Types page. + + + +## View information about file formats that can be parsed + + +To view information about the file formats that the content processing component has format handlers for, you have to use Windows PowerShell. +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. Start a SharePoint 2016 Management Shell on the server. + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://technet.microsoft.com/en-us/library/hh831491.aspx). + + +3. At the Microsoft PowerShell command prompt, type the following commands: + + ``` + +$ssa = Get-SPEnterpriseSearchServiceApplication +Get-SPEnterpriseSearchFileFormat -SearchApplication $ssa + + ``` + + + The result is a list of all file formats that the content processing component in the Search service application referenced by $ssa can parse. For each file format the list shows: + + - The file name extension and mime type + + + - The type of format handler that the content processing component uses to parse the format. The entry "BuiltIn:True" indicates a built-in format handler. The entry "BuiltIn:False" indicates a third-party filter-based format handler. + + + - The parsing state of the format. The entry "Enabled:True" indicates that parsing is enabled. The entry "Enabled:False" indicates that parsing is disabled. + + + +## Enable or disable parsing of a file format + + +To enable or disable parsing of a file format, you have to use Windows PowerShell. +## + + **To enable parsing of a file format using a built-in format handler** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. Start a SharePoint 2016 Management Shell on the server that hosts the content processing component. + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://technet.microsoft.com/en-us/library/hh831491.aspx). + + +3. At the Microsoft PowerShell command prompt, type the following commands: + + ``` + +$ssa = Get-SPEnterpriseSearchServiceApplication +Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa FormatID $TRUE + ``` + + + Where: + + FormatID is the identity of the file format. + + $TRUE enables the format handler to parse the file type. + + +4. Restart the SharePoint Search Host Controller service to apply the changes: + +1. Open a command prompt window on the server that hosts the content processing component. On the **Start** menu, click **All Programs**, click **Accessories**, right-click **Command Prompt** and then click **Run as administrator**. + + +2. To stop the SharePoint Search Host Controller, type this command: **net stop spsearchhostcontroller** + + +3. To restart the SharePoint Search Host Controller, type this command: **net start spsearchhostcontroller** + + +5. **Verification:** show the list of file name extensions and file formats that the content processing component can parse and make sure that the file name extension is there. See [View information about file formats that can be parsed](#ViewInformationFileFormats). + + + +## + + **To disable parsing of a file format using a built-in format handler** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. Start a SharePoint 2016 Management Shell on the server that hosts the content processing component. + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://technet.microsoft.com/en-us/library/hh831491.aspx). + + +3. At the Microsoft PowerShell command prompt, type the following commands: + + ``` + +$ssa = Get-SPEnterpriseSearchServiceApplication +Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa FormatID $FALSE + ``` + + + Where: + + FormatID is the identity of the file format. + + $FALSE disables the format handler from parsing the file type. + + +4. Restart the SharePoint Search Host Controller service to apply the changes: + +1. Open a command prompt window on the server that hosts the content processing component. On the **Start** menu, click **All Programs**, click **Accessories**, right-click **Command Prompt** and then click **Run as administrator**. + + +2. To stop the SharePoint Search Host Controller, type this command: **net stop spsearchhostcontroller** + + +3. To restart the SharePoint Search Host Controller, type this command: **net start spsearchhostcontroller** + + +5. **Verification:** show the list of file name extensions and file formats that the content processing component can parse and make sure that the file name extension is not there. See [View information about file formats that can be parsed](#ViewInformationFileFormats). + + + +## + + **To enable parsing of a file format using a third-party filter-based format handler** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. Start a SharePoint 2016 Management Shell on the server that hosts the content processing component. + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://technet.microsoft.com/en-us/library/hh831491.aspx). + + +3. At the Microsoft PowerShell command prompt, type the following commands: + + ``` + +$ssa = Get-SPEnterpriseSearchServiceApplication +New-SPEnterpriseSearchFileFormat -SearchApplication $ssa FileNameExtension FileFormat application/FileApplication + ``` + + + Where: + + FileNameExtension is the file name extension of the file type. + + FileFormat is the format of the file type. The format is often the name of the application. + + application/FileApplication is the mime type of the file type. The mime type must consist of a type and a subtype. In this example, application is the type and FileApplication is the subtype. For example, for Word files, the type is application and the subtype is msword. Together they form the complete mime type: application/msword. + + + + +4. Restart the SharePoint Search Host Controller service to apply the changes: + +1. Open a command prompt window on the server that hosts the content processing component. On the **Start** menu, click **All Programs**, click **Accessories**, right-click **Command Prompt** and then click **Run as administrator**. + + +2. To stop the SharePoint Search Host Controller, type this command: **net stop spsearchhostcontroller** + + +3. To restart the SharePoint Search Host Controller, type this command: **net start spsearchhostcontroller** + + +5. **Verification:** show the list of file name extensions and file formats that the content processing component can parse and make sure that the file name extension is there. See [View information about file formats that can be parsed](#ViewInformationFileFormats). + + + +## + + **To disable parsing of a file format using a third-party filter-based format handler** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. Start a SharePoint 2016 Management Shell on the server that hosts the content processing component. + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://technet.microsoft.com/en-us/library/hh831491.aspx). + + +3. At the Microsoft PowerShell command prompt, type the following commands: + + ``` + +$ssa = Get-SPEnterpriseSearchServiceApplication +Remove-SPEnterpriseSearchFileFormat -SearchApplication $ssa -Identity FileNameExtension + ``` + + + Where: + + FileNameExtension is the file name extension of the file type. + + +4. Restart the SharePoint Search Host Controller service to apply the changes: + +1. Open a command prompt window on the server that hosts the content processing component. On the **Start** menu, click **All Programs**, click **Accessories**, right-click **Command Prompt** and then click **Run as administrator**. + + +2. To stop the SharePoint Search Host Controller, type this command: **net stop spsearchhostcontroller** + + +3. To restart the SharePoint Search Host Controller, type this command: **net start spsearchhostcontroller** + + +5. **Verification:** show the list of file name extensions and file formats that the content processing component can parse and make sure that the file name extension is not there. See [View information about file formats that can be parsed](#ViewInformationFileFormats). + + + diff --git a/SharePoint/add-or-remove-service-application-connections-from-a-web-application-in-sharepoi.md b/SharePoint/add-or-remove-service-application-connections-from-a-web-application-in-sharepoi.md new file mode 100644 index 0000000000..930847833a --- /dev/null +++ b/SharePoint/add-or-remove-service-application-connections-from-a-web-application-in-sharepoi.md @@ -0,0 +1,128 @@ +--- +title: Add or remove service application connections from a web application in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 6a7cfa97-f4b1-4b3f-9b98-303ee1e836c2 +--- + + +# Add or remove service application connections from a web application in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Search Server 2013, SharePoint Foundation 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-25* **Summary:** Learn how to add or remove service application connections to a service application connection group in SharePoint Server 2016 and SharePoint 2013.When you create a service application in SharePoint Server, a *service application connection* is created. A service application connection is also referred to as an *application proxy* . A service application connection associates the service application to web applications via membership in a *service application connection group* (also referred to as *application proxy group* ). +> [!IMPORTANT:] + + + + + +By default, a new service application connection is added to the farm’s Default group of service application connections when you create the service application by using Central Administration. You can override this default membership. If a new service application is created by using Microsoft PowerShell instead of by using Central Administration, the new service application does not automatically become a member of the Default service application connections group unless the **default** parameter is supplied. +> [!NOTE:] + + + + + +By default, all web applications are associated with the farm’s Default group of service application connections, although you can change this setting. You can also create one custom connection group for each web application in the farm. You can change the service applications with which a web application is associated at any time, and you can change the service applications that are included in the Default service application connection group. +## Editing a service connection group + + +You can add or remove service application connections to a service application connection group by using Central Administration or by using PowerShell cmdlets. **To edit a service connection group by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. + + +2. Start Central Administration. + + +3. On the Central Administration Home page, click **Application Management**. + + +4. On the Application Management page, in the **Service Applications** section, click **Configure service application associations**. + + +5. On the Service Application Associations page, select **Web Applications** from the **View** drop-down menu. + + +6. In the list of Web applications, in the **Application Proxy Group** column, click the name of the service application connection group that you want to change. + + +7. To add a service connection to the group, select the check box that is next to the service application that you want to add to the connection group. To remove a service application connection from the connection group, clear the check box next to the service application that you want to remove from the connection group. When you have made the changes that you want, click **OK**. + + > [!NOTE:] + + **To add a service application connection to a service application connection group by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Add-SPServiceApplicationProxyGroupMember -Identity < the service application proxy group > -Member + ``` + + + For more information, see **Add-SPServiceApplicationProxyGroupMember**. + + + **To remove a service application connection from a service application connection group by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + - Add memberships that are required beyond the minimums above. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Remove-SPServiceApplicationProxyGroupMember -Identity -Member + ``` + + + For more information, see **Remove-SPServiceApplicationProxyGroupMember**. + + + +# See also + +#### + + [Share service applications across farms in SharePoint Server](html/share-service-applications-across-farms-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/add-sharepoint-server-to-a-farm-in-sharepoint-server-2016.md b/SharePoint/add-sharepoint-server-to-a-farm-in-sharepoint-server-2016.md new file mode 100644 index 0000000000..c8f102ce0a --- /dev/null +++ b/SharePoint/add-sharepoint-server-to-a-farm-in-sharepoint-server-2016.md @@ -0,0 +1,288 @@ +--- +title: Add SharePoint server to a farm in SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 0926f63d-8dae-44c0-9e91-51209aa4c3ef +--- + + +# Add SharePoint server to a farm in SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-06-01* **Summary:** Learn how to add a server to an existing SharePoint Server 2016 farm.In this article: +- [Before you add a web or application server to a SharePoint farm](#begin) + + +- [Install prerequisite software](#prereq) + + +- [Install the SharePoint software ](#installSP) + + +- [Add the new SharePoint server to the farm](#addserver) + + + +## Before you add a server to a SharePoint farm + + + +## Determine server role + +To add a new server to the farm, you must know its intended role to plan for additional or specialized configurations and assess the potential effect of adding the server to a production environment.In SharePoint Server 2016, the concept of server roles has changed from previous versions. Server role types are now defined by MinRole which allow for better deployment and health of the server in the farm. For additional information about the MinRole feature and a description for each server role type, see [Overview of MinRole Server Roles in SharePoint Server 2016](html/overview-of-minrole-server-roles-in-sharepoint-server-2016.md). +## Additional tasks + +Before you start to install prerequisite software, you have to complete the following: +- Verify that the new server meets the hardware and software requirements described in [Hardware and software requirements for SharePoint Server 2016](html/hardware-and-software-requirements-for-sharepoint-server-2016.md). + + +- Verify that you have the minimum level of permissions that are required to install and configure SharePoint Server 2016 on a new server. You must be a member of the Farm Administrators SharePoint group and the Administrators group on the local server to complete the procedures in this article. For more information, see [Initial deployment administrative and service accounts in SharePoint Server](html/initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). + + +- Verify that you know the name of the database server on the farm to which you are connecting, and the name of the configuration database if you are adding the server by using Microsoft PowerShell commands. + + +- If you intend to use PowerShell commands to add the server, verify that you meet the following minimum memberships is installed. + + +- **Securityadmin** fixed server role on the SQL Server instance. + + +- **db_owner** fixed database role on all databases that are to be updated. + + +- Administrators group on the server on which you are running the PowerShell cmdlets. + + +- An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2016 cmdlets. + + > [!NOTE:] + +- Document the location of the SharePoint Server 2016 binary and log files on the existing farm servers. We recommend that the location of these files on the new server map to the locations used on the other servers in the farm. + + > [!IMPORTANT:] + + +## Install prerequisite software + + +Before you can install SharePoint Server 2016 and add a server to the farm, you must check for and install all the prerequisite software on the new server. You do this by using the Microsoft SharePoint Products Preparation Tool, which requires an Internet connection to download and configure SharePoint Server 2016 prerequisites. If you do not have an Internet connection for the farm servers, you can still use the tool to determine the software that is required. You will have to obtain installable images for the required software. For download locations, see [Access to applicable software](hardware-and-software-requirements-for-sharepoint-server-2016.md#section5) in "Hardware and software requirements (SharePoint Server 2016)." +> [!TIP:] + + + + + +For detailed instructions about how to install the prerequisites, see [Prepare the farm servers](install-sharepoint-server-2016-across-multiple-servers.md#PrepareServers) in the article, [Install SharePoint Server 2016 across multiple servers](html/install-sharepoint-server-2016-across-multiple-servers.md). +> [!TIP:] + + + + + + +## Install the SharePoint software + + +After you install the prerequisites, follow these steps to install SharePoint Server 2016 on the new server. For detailed instructions about how to install SharePoint Server 2016, see [Install SharePoint Server 2016 on a single server with SQL Server](html/install-sharepoint-server-2016-on-a-single-server-with-sql-server.md). **To install SharePoint Server 2016** +1. Verify that the user account that is performing this procedure is the Setup user account. For information about the Setup user account, see [Initial deployment administrative and service accounts in SharePoint Server](html/initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). + + +2. From the product media or a file share that contains the SharePoint Server 2016 Products installation files, run Setup.exe. + + +3. On the **Enter Your Product Key** page, enter your product key, and then click **Continue**. + + +4. Review and accept the Microsoft License Terms. + + +5. Accept the default file location where SharePoint Server 2016 will be installed or change the installation path in order to suit your requirements. + + > [!TIP:] + +6. Click **Install Now**. + + +7. When Setup finishes, a dialog box prompts you to run the **SharePoint Products Configuration Wizard**. You can start the wizard immediately or from the Windows command prompt later. + + + +## Add the new SharePoint server to the farm + + +You add the new server to the farm by using one of the following procedures: +- [To add a server by using the SharePoint Products Configuration Wizard](#addserverconfigwiz) + + +- [To add a new SharePoint Server 2016 server to the farm by using the PSConfig.exe command-line tool](#psconfig) + + +- [To add a server by using Windows PowerShell](#addserverpowershell) + + + **To add a new SharePoint Server 2016 server to the farm by using the SharePoint Products Configuration Wizard** +1. Verify that the user account that is performing this procedure is the Setup user account. For information about the Setup user account, see [Initial deployment administrative and service accounts in SharePoint Server](html/initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). + + +2. Start the **SharePoint 2016 Products Configuration Wizard**. + + - For Windows Server 2012 R2: + + - On the new server, on the **Start** screen, click **SharePoint 2016 Products Configuration Wizard**. + + + + For more information about how to interact with Windows Server 2012 R2, see [Common Management Tasks and Navigation in Windows Server 2012 R2 and Windows Server 2012](https://go.microsoft.com/fwlink/p/?LinkId=276950). + + +3. On the **Welcome to SharePoint Products** page, click **Next**. + + +4. On the **Connect to a server farm** page, click **Connect to an existing server farm.** + + +5. Click **Next**. + + +6. On the **Specify Configuration Database settings** page, type the name of the instance of SQL Server in the **Database server** box, and then click **Retrieve Database Names**. + + +7. Select the name of the configuration database in the **Database name** list, and then click **Next**. + + +8. On the **Specify Farm Security Settings** page, type the name of the farm passphrase in the **Passphrase** box, and then click **Next**. + + +9. On the **Specify Server Role** page, choose the appropriate role, and then click **Next**. + + > [!NOTE:] + +10. On the **Completing the SharePoint Products Configuration Wizard** page, click **Next**. + + +11. On the server that hosts Central Administration, click **Manage servers in this farm** to verify that the new server is part of the farm. + + > [!NOTE:] + +12. On the **Servers in Farm** page, click the name of the new server. Use the list of available services on the **Services on Server** page to start the services that you want to run on the new server. + + > [!NOTE:] + + **To add a new SharePoint Server 2016 server to the farm by using the PSConfig.exe command-line tool** +1. To create a farm by using the PSConfig.exe command-line tool, use the following syntax: + + ``` + +psconfig.exe -cmd configdb -connect -server -database -user -password -passphrase -admincontentdatabase -localserverrole -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd adminvs -provision -port -windowsauthprovider onlyusentlm -cmd applicationcontent -install + ``` + + + Where can be any of the following values: WebFrontEnd, Application, DistributedCache, Search, or Custom. + + > [!NOTE:] + + + > [!NOTE:] + + **To add a new SharePoint Server 2016 server to the farm by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2016 cmdlets. + + > [!NOTE:] + +2. Start the SharePoint 2016 Management Shell. + + - For Windows Server 2012 R2: + + - On the **Start** screen, click **SharePoint 2016 Management Shell**. + + + + For more information about how to interact with Windows Server 2012 R2, see [Common Management Tasks and Navigation in Windows Server 2012 R2 and Windows Server 2012](https://go.microsoft.com/fwlink/p/?LinkId=276950). + + +3. At the PowerShell command prompt, type the following command to connect the server to a configuration database: + + ``` + +Connect-SPConfigurationDatabase -DatabaseServer -DatabaseName -Passphrase -LocalServerRole + ``` + + + Where: + + - *<$DatabaseServer>* is the name of the server that hosts the configuration database + + + - ** is the name of the configuration database + + + - *<$Passphrase>* is the passphrase for the farm + + + - ** is the server role type + + Where can be any of the following values: WebFrontEnd, Application, DistributedCache, Search, or Custom. + + > [!NOTE:] + +4. At the PowerShell command prompt, type the following command to install the Help File Collections: + + ``` + +Install-SPHelpCollection -All + ``` + +5. At the PowerShell command prompt, type the following command to install the Security Resource for SharePoint Server 2016: + + ``` + Initialize-SPResourceSecurity + ``` + +6. At the PowerShell command prompt, type the following command to install the basic services: + + ``` + Install-SPService + ``` + +7. At the PowerShell command prompt, type the following command to install all the features: + + ``` + Install-SPFeature -AllExistingFeatures + ``` + +8. At the PowerShell command prompt, type the following command to set the port number of the SharePoint Central Administration website: + + ``` + New-SPCentralAdministration -Port -WindowsAuthProvider NTLM + ``` + + + > [!NOTE:] + +9. At the PowerShell command prompt, type the following command to install application content: + + ``` + +Install-SPApplicationContent + ``` + +10. At the PowerShell command prompt, type the following command to get a list of servers in the farm. + + ``` + Get-SPServer + ``` + + + > [!NOTE:] + + diff --git a/SharePoint/add-the-yammer-embed-widget-to-a-sharepoint-page.md b/SharePoint/add-the-yammer-embed-widget-to-a-sharepoint-page.md new file mode 100644 index 0000000000..1c74c75fab --- /dev/null +++ b/SharePoint/add-the-yammer-embed-widget-to-a-sharepoint-page.md @@ -0,0 +1,30 @@ +--- +title: Add the Yammer Embed widget to a SharePoint page +ms.prod: SHAREPOINT +ms.assetid: 48fa0391-b996-4a46-8744-4b1777db3d2f +--- + + +# Add the Yammer Embed widget to a SharePoint page + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, Yammer Enterprise* * **Topic Last Modified:** 2017-07-31* **Summary:** Learn how to use the Yammer Embed widget to include Yammer feeds on SharePoint pages.The Yammer Embed widget is a thin layer of JavaScript that renders HTML, which you can insert into a SharePoint Server 2013 page. The widget displays one of several types of Yammer feeds directly from Yammer, and it also handles authentication. If a user hasn’t yet logged on to Yammer, the widget provides a user interface to do this.To use Yammer Embed, just add the JavaScript snippet for the feed to your SharePoint site. You can use the [Yammer Embed configuration tool](https://go.microsoft.com/fwlink/p/?LinkId=507500), as depicted in the screenshot below, to select the feed type and settings that you want to use, and then get a JavaScript snippet that contains those settings to embed into a SharePoint page. **Yammer Embed configuration tool** + + + +![Screenshot of the Yammer Embed tool](images/) + + + +When you use this JavaScript snippet on a SharePoint page, you can add it to a Script Editor Web Part and place it anywhere on the page. The widget shows users the latest messages based on how Yammer Embed is configured.For more information about how to use the Yammer Embed widget, see [Embed](https://go.microsoft.com/fwlink/p/?LinkId=507501) in the [Yammer Developer Center](https://go.microsoft.com/fwlink/p/?LinkId=507502). +# See also + +#### + + [Integrate Yammer with on-premises SharePoint 2013 environments](html/integrate-yammer-with-on-premises-sharepoint-2013-environments.md) + + + + + + + + diff --git a/SharePoint/add-yammer-to-the-navigation-bar-for-sharepoint-2013.md b/SharePoint/add-yammer-to-the-navigation-bar-for-sharepoint-2013.md new file mode 100644 index 0000000000..7ab194c2b1 --- /dev/null +++ b/SharePoint/add-yammer-to-the-navigation-bar-for-sharepoint-2013.md @@ -0,0 +1,22 @@ +--- +title: Add Yammer to the navigation bar for SharePoint 2013 +ms.prod: SHAREPOINT +ms.assetid: 0d32d946-52d0-4913-bfdb-d3c1193cfc4a +--- + + +# Add Yammer to the navigation bar for SharePoint 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, Yammer Enterprise* * **Topic Last Modified:** 2017-07-31* **Summary:** Use a toggle switch to determine whether to show the SharePoint Newsfeed link or Yammer on the top navigation bar in SharePoint 2013 with Service Pack 1 (SP1).When you are running Service Pack 1 for SharePoint Server 2013, you can choose whether to show the SharePoint Newsfeed link or Yammer on the top navigation bar with a simple toggle switch. If you want to use Yammer, you select **Activate Yammer** in Central Administration. This replaces the Newsfeed link on the top navigation bar with a link to Yammer. **To add Yammer to SharePoint on-premises navigation** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. On the Central Administration website, choose **Office 365** > **Configure Yammer**. + + ![Yammer Configuration page in Central Admin](images/) + + + +3. On the **Yammer Configuration** page, select **Activate Yammer**. + + + diff --git a/SharePoint/administer-business-intelligence-in-sharepoint-server.md b/SharePoint/administer-business-intelligence-in-sharepoint-server.md new file mode 100644 index 0000000000..9e66fb610e --- /dev/null +++ b/SharePoint/administer-business-intelligence-in-sharepoint-server.md @@ -0,0 +1,20 @@ +--- +title: Administer business intelligence in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: e91d6339-549c-4620-a559-b7c3c7ecba5d +--- + + +# Administer business intelligence in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-27* **Summary:** Find resources to configure and maintain business intelligence tools in SharePoint Server 2013 and SharePoint Server 2016.The following articles about how to configure and maintain business intelligence tools in SharePoint Server are available to view online. +### + + + + + +![Building blocks](images/) + + + +  ContentDescription [Administer Excel Services in SharePoint Server 2013](html/administer-excel-services-in-sharepoint-server-2013.md)
Excel Services is a SharePoint Server 2013 service application that allows users to share and view Excel workbooks.
[PerformancePoint Services administration](html/performancepoint-services-administration.md)
PerformancePoint Services in SharePoint Server is a performance management service that you can use to monitor and analyze your business.
**Visio Graphics Service administration in SharePoint Server 2013**
Visio Services is a SharePoint Server service application that allows users to share and view Visio diagrams.
**Configure a Business Intelligence Center in SharePoint Server 2013**
The Business Intelligence Center gives you a central location to store items, such as reports and dashboards. When you enable Excel Services and PerformancePoint Services, you will already have a location to store reports and dashboard content.
diff --git a/SharePoint/administer-excel-services-in-sharepoint-server-2013.md b/SharePoint/administer-excel-services-in-sharepoint-server-2013.md new file mode 100644 index 0000000000..e2c0837b79 --- /dev/null +++ b/SharePoint/administer-excel-services-in-sharepoint-server-2013.md @@ -0,0 +1,12 @@ +--- +title: Administer Excel Services in SharePoint Server 2013 +ms.prod: SHAREPOINT +ms.assetid: a96cfa2d-87f8-4991-801c-fd5482d49d0b +--- + + +# Administer Excel Services in SharePoint Server 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-06* **Summary:**  A list of articles about Excel Services administration in SharePoint Server 2013.Excel Services is a SharePoint Server 2013 service application that allows users to share and view Excel workbooks. The service application also enables data-connected Excel workbooks and work sheets to be refreshed and updated from a variety of data sources.(Using SharePoint Server 2016? Excel Services features are now in [Excel Online in Office Online Server](https://technet.microsoft.com/library/jj219437%28v=office.16%29.aspx).)The following articles about Excel Services administration in SharePoint Server 2013 are available to view online. +### + +ContentDescription
![Building blocks](images/) [Configure Excel Services (SharePoint Server 2013)](html/configure-excel-services-sharepoint-server-2013.md)
Deploy Excel Services to your SharePoint Server 2013 farm by creating an Excel Services service application by using Central Administration.

[Manage Excel Services global settings (SharePoint Server 2013)](html/manage-excel-services-global-settings-sharepoint-server-2013.md)
Edit Excel Services settings for security, load balancing, memory, cache, and external data by using the SharePoint Central Administration website.

[Manage Excel Services trusted file locations (SharePoint Server 2013)](html/manage-excel-services-trusted-file-locations-sharepoint-server-2013.md)
Add, configure, or delete an Excel Services trusted file location by using the SharePoint Central Administration website.

[Manage Excel Services trusted data providers (SharePoint Server 2013)](html/manage-excel-services-trusted-data-providers-sharepoint-server-2013.md)
Add, configure, or delete Excel Services trusted data providers by using the SharePoint Central Administration website.

[Manage Excel Services trusted data connection libraries (SharePoint Server 2013)](html/manage-excel-services-trusted-data-connection-libraries-sharepoint-server-2013.md)
Add, configure, or delete trusted data connection libraries in Excel Services by using the SharePoint Central Administration website.

[Manage Excel Services user defined function assemblies (SharePoint Server 2013)](html/manage-excel-services-user-defined-function-assemblies-sharepoint-server-2013.md)
Add, edit or delete Excel Services user-defined function assemblies by using the SharePoint Central Administration website.

[Manage Excel Services data model settings (SharePoint Server 2013)](html/manage-excel-services-data-model-settings-sharepoint-server-2013.md)
Configure instances of SQL Server 2012 Analysis Services for Data Model functionality in Excel Services.
diff --git a/SharePoint/administer-search-in-sharepoint-server.md b/SharePoint/administer-search-in-sharepoint-server.md new file mode 100644 index 0000000000..e01cbc337c --- /dev/null +++ b/SharePoint/administer-search-in-sharepoint-server.md @@ -0,0 +1,27 @@ +--- +title: Administer search in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 820ace03-1fb7-41fd-a077-28b82ebddde3 +--- + + +# Administer search in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary: ** Learn how to manage the search schema and the search topology in SharePoint Server 2013 and SharePoint Server 2016.The following articles on TechNet provide information about how you operate and manage search in SharePoint Server. +## TechNet articles about administering search + +The following articles about administering search in SharePoint Server are available to view online. Writers update articles on a continuing basis as new information becomes available and as users provide feedback. +### + + + + + +![Building blocks](images/) + + + + + + + +ContentDescription
[Manage the Search Center in SharePoint Server](html/manage-the-search-center-in-sharepoint-server.md)
Learn about pages that are created in a Search Center site in SharePoint Server, and see articles about how to configure Web Parts.


[Manage the search index in SharePoint Server 2016](html/manage-the-search-index-in-sharepoint-server-2016.md)
Learn how to manage collection of content in the search index and retrieval from the search index.
[Manage crawling in SharePoint Server](html/manage-crawling-in-sharepoint-server.md)
Learn how to crawl content that you want users to be able to search for in SharePoint Server.
[Manage search relevance in SharePoint Server](html/manage-search-relevance-in-sharepoint-server.md)
Learn how you can configure settings to provide the most relevant search results.

[Manage the search topology in SharePoint Server](html/manage-the-search-topology-in-sharepoint-server.md)
Learn how to manage search components to scale out the search topology in SharePoint Server.
[View search diagnostics in SharePoint Server](html/view-search-diagnostics-in-sharepoint-server.md)
Learn about search and usage reports, query health reports, crawl health reports and the crawl log to analyze the health of the search system.
[Enable search alerts in SharePoint Server](html/enable-search-alerts-in-sharepoint-server.md)
Learn how to enable or disable search alerts.
[Enable query logging in SharePoint Server](html/enable-query-logging-in-sharepoint-server.md)
Learn how to enable or disable query logging.
[Export and import customized search configuration settings in SharePoint Server](html/export-and-import-customized-search-configuration-settings-in-sharepoint-server.md)
Learn how to import and export customized search configuration settings.
diff --git a/SharePoint/administer-sites-and-site-collections-in-sharepoint-server.md b/SharePoint/administer-sites-and-site-collections-in-sharepoint-server.md new file mode 100644 index 0000000000..95878e50cc --- /dev/null +++ b/SharePoint/administer-sites-and-site-collections-in-sharepoint-server.md @@ -0,0 +1,32 @@ +--- +title: Administer sites and site collections in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: d489421a-f6be-4ee4-8acf-8b79f917aa6b +--- + + +# Administer sites and site collections in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Search Server 2013, SharePoint Foundation 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-08-04* **Summary: ** Use these TechNet articles to learn how to manage sites, site collections, and Web Parts in SharePoint Server 2016 and SharePoint 2013.A SharePoint Server site collection is a hierarchical site structure that is made up of one top-level site and sites below it. This top-level website can have multiple subsites, and each subsite can have multiple subsites, for as many levels as required. Top-level websites and subsites allow different levels of control over the features and settings for sites. +## TechNet articles about site and site collection administration + +The following articles about how to manage sites, site collections, and Web Parts in SharePoint Server are available. +### + +ContentDescription [Manage site collections in SharePoint Server](html/manage-site-collections-in-sharepoint-server.md)
These articles explain how to create and delete site collections, how to manage site collection administrators, and how to use quota templates to manage site collection storage limits.
[Manage sites in SharePoint Server](html/manage-sites-in-sharepoint-server.md)
These articles explain how to determine when to lock or unlock sites, and how to use site usage data to determine whether an unused website should be deleted.
[Manage web parts in SharePoint Server](html/manage-web-parts-in-sharepoint-server.md)
These article helps you prepare to manage security for Web Parts pages and controls that are used with SharePoint Server.
+# See also + +#### + + [Operations for SharePoint Server](html/operations-for-sharepoint-server.md) + + + + [Fundamental site planning in SharePoint Server 2016](html/fundamental-site-planning-in-sharepoint-server-2016.md) + + + + + + + + diff --git a/SharePoint/administer-the-user-profile-service-in-sharepoint-server.md b/SharePoint/administer-the-user-profile-service-in-sharepoint-server.md new file mode 100644 index 0000000000..7e030391dc --- /dev/null +++ b/SharePoint/administer-the-user-profile-service-in-sharepoint-server.md @@ -0,0 +1,24 @@ +--- +title: Administer the User Profile service in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 215432d7-cb3b-4af4-beed-47492a6777f0 +--- + + +# Administer the User Profile service in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-08-02* **Summary:** Learn how to administer the User Profile service in SharePoint Server 2013 and SharePoint Server 2016.The User Profile service is a shared service in SharePoint Server that enables the creation and administration of user profiles that can be accessed from multiple sites and farms. Administration of User Profile service applications in SharePoint Server can be delegated to a service application administrator by the farm administrator.The following articles provide information about how to administer the User Profile service application in SharePoint Server. +### + + + + + +![Building blocks](images/) + + + + + + + +ContentDescription [Create a User Profile service applications in SharePoint Server](html/create-a-user-profile-service-applications-in-sharepoint-server.md)
Learn how to configure a User Profile service application in SharePoint Server.
[Delegate administration of User Profile service applications or features in SharePoint Server](html/delegate-administration-of-user-profile-service-applications-or-features-in-shar.md)
Learn how to delegate administration of a User Profile service application or selected features of a User Profile service application to a service application administrator in SharePoint Server.
[Add, edit, or delete custom properties in SharePoint Server user profiles](html/add-edit-or-delete-custom-properties-in-sharepoint-server-user-profiles.md)
Learn how to create, edit, and delete user profile properties in SharePoint Server.
[Manage user profile synchronization in SharePoint Server](html/manage-user-profile-synchronization-in-sharepoint-server.md)
Learn about articles and worksheets to help you manage User Profile synchronization in SharePoint Server.
diff --git a/SharePoint/all-state-service-databases-are-paused-for-a-state-service-application-sharepoin.md b/SharePoint/all-state-service-databases-are-paused-for-a-state-service-application-sharepoin.md new file mode 100644 index 0000000000..48d6ce6bf8 --- /dev/null +++ b/SharePoint/all-state-service-databases-are-paused-for-a-state-service-application-sharepoin.md @@ -0,0 +1,71 @@ +--- +title: All State Service databases are paused for a State Service Application (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: 8386d324-816a-42ee-aff2-ce135ca2f241 +--- + + +# All State Service databases are paused for a State Service Application (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "All State Service databases are paused for a State Service Application." **Rule Name:**    All State Service databases are paused for a State Service Application **Summary:**    All of the databases associated with a State Service service application are paused. This may result in errors when using some SharePoint Server 2016 components such as InfoPath Web browser forms and the Microsoft SharePoint Chart Web Part. **Cause:**    This might be caused by the administrator pausing all databases for the service application. **Resolution:   Resume the State Service service application databases by using Microsoft PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2016 cmdlets. + + > [!NOTE:] + +2. Start the SharePoint 2016 Management Shell. + + For more information about how to interact with Windows Server 2012 R2, see [Common Management Tasks and Navigation in Windows](http://go.microsoft.com/fwlink/?LinkID=715712&clcid=0x409). + + +3. To identify the paused database, type the following command at the PowerShell command prompt: + + ``` + +Get-SPStateServiceDatabase + ``` + +4. If you want to resume a paused database, type the following command at the Windows PowerShell command prompt: + + ``` + Resume-SPStateServiceDatabase -Identity + ``` + + + Where: + + - ** is the identifier for the State Service service application database as a GUID. + + +5. If you want to create a new database instead of using an existing database, type the following command at the Windows PowerShell command prompt: + + ``` + New-SPStateServiceDatabase -Name -ServiceApplication -DatabaseServer [-DatabaseCredentials ] + ``` + + + Where: + + - ** is name of the database as a string. + + + - ** is the identifier for the affected State Service service application as a string or a GUID. If there is only one State Service service application, you do not have to specify this parameter. + + + - ** is name of the database server. + + + - ** is SQL Server authentication credentials for the database server. If this parameter is not specified, Windows authentication will be used. + + +For more information, see Resume-SPStateServiceDatabase or New-SPStateServiceDatabase. diff --git a/SharePoint/alternate-access-urls-have-not-been-configured-sharepoint-server-2016.md b/SharePoint/alternate-access-urls-have-not-been-configured-sharepoint-server-2016.md new file mode 100644 index 0000000000..f5f178462d --- /dev/null +++ b/SharePoint/alternate-access-urls-have-not-been-configured-sharepoint-server-2016.md @@ -0,0 +1,28 @@ +--- +title: Alternate access URLs have not been configured (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: 7f65b235-8e0d-48d8-acca-e2e0295e6522 +--- + + +# Alternate access URLs have not been configured (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "Alternate access URLs have not been configured" for SharePoint Server 2016. **Rule Name:**  Alternate access URLs have not been configured. **Summary:**  A default zone URL must not point to the computer name of a front-end Web server. Because this installation has more than one front-end Web server, an incorrectly configured default zone URL can result in a variety of errors, including incorrect links and failed operations. **Cause:**  A default zone URL is pointing to the computer name of a front-end Web server. **Resolution: Change the default zone URL to a URL that differs from the computer name of any front-end Web server.** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. On the the SharePoint Central Administration website home page, in the **System Settings** section, click **Configure alternate access mappings**. + + +3. On the Alternate Access Mappings page, on the **Alternate Access Mapping Collection** menu, click **Change Alternate Access Mapping Collection**. + + +4. In the **Select An Alternate Access Mapping Collection** dialog box, click the alternate access mapping collection for which you want to change the default zone URL. + + +5. On the Alternate Access Mappings page, click **Edit Public URLs**. + + +6. On the Edit Public Zone URLs page, in the **Default** text box, type a new default zone URL that differs from the computer name of any front-end Web server, and then click **Save**. + + + diff --git a/SharePoint/application-management-and-governance-in-sharepoint.md b/SharePoint/application-management-and-governance-in-sharepoint.md new file mode 100644 index 0000000000..e7efd36cca --- /dev/null +++ b/SharePoint/application-management-and-governance-in-sharepoint.md @@ -0,0 +1,207 @@ +--- +title: Application management and governance in SharePoint +ms.prod: SHAREPOINT +ms.assetid: f8efdfaf-8ef6-445c-9fb9-8845667e478b +--- + + +# Application management and governance in SharePoint + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-20* **Summary:** Learn how to govern applications for SharePoint 2013 by creating a customization policy and understanding the app model, branding, and life-cycle management.How will you manage the applications that are developed for your environment? What customizations do you allow in your applications, and what are your processes for managing those applications?For effective and manageable applications, your organization should consider the following: +- [Customization policy](#Customization)   SharePoint Server 2016 includes customizable features and capabilities that span multiple product areas, such as business intelligence, forms, workflow, and content management. Customization can introduce risks to the stability, maintenance, and security of the environment. To support customization while controlling its scope, you should develop a customization policy. + + +- [Life-cycle management](#Lifecycle)   Follow best practices to manage applications and keep your environments in sync. + + +- [Branding](#Branding)   If you are designing an information architecture and a set of sites to use across an organization, consider including branding in your governance plan. A formal set of branding policies helps ensure that sites consistently use enterprise imagery, fonts, themes, and other design elements. + + +- [Solutions or apps for SharePoint?](#SolutionsApps)   Decide whether a solution or an app for SharePoint would be the best choice for specific customizations. + + + +### + +![Foundation icon](images/) This article is part of a set of articles about governance. The following articles describe other aspects of governance:
[What is governance in SharePoint?](html/what-is-governance-in-sharepoint.md)
[IT governance in SharePoint](html/it-governance-in-sharepoint.md)
**Information management and governance in SharePoint**
The What is governance? poster gives a summary of this content. Download the [PDF version](https://go.microsoft.com/fwlink/?LinkId=331051) or [Visio version](https://go.microsoft.com/fwlink/?LinkId=331050), or [Zoom into the model in full detail with Zoom.it from Microsoft](https://go.microsoft.com/fwlink/?LinkId=331052).
+## Customization policy + + +Determine the types of customizations you want to allow and how to manage them. Your customization policy should include: +- **Service-level descriptions**    What are the parameters for supporting and managing customizations in your environments? See [Service-level agreements](it-governance-in-sharepoint.md#SLA). + + +- **Guidelines for updating customizations**    How do you manage changes to customizations, and how do you roll out those changes to your environments? Consider ways to manage source code, such as a source control system and standards for documenting the code. + + +- **Processes for analyzing**    How do you understand whether a particular customization is working well in your environment, or how do you decide which ones to create, change, or retire? + + +- **Approved tools for customization**    Consider development standards, such as coding best practices and the tools that you will to use across your organization. For example, you should decide whether to allow the use of SharePoint Designer 2013 and [Design Manager](https://go.microsoft.com/fwlink/?LinkId=330805), and specify which site elements can be customized and by whom. + + +- **Process for piloting and testing customizations**    How do you test and deploy customizations? How many people should be in a pilot testing group? What are your standards for testing and validating customizations? + + +- **Who is responsible for ongoing support**    Who will be responsible for supporting customizations in your environments—individual teams or a central group? + + +- **Guidelines for packaging and deploying customizations**    Do you have individual packages for each, or do you include several in a feature or solution? Which customizations should be apps for SharePoint instead of solutions? How do you ensure that customizations in one environment do not affect the rest of your SharePoint implementation? + + +- **Specific policies regarding each potential type of customization**    What types of customizations do you allow? + + For more information about kinds of customizations and their potential risks, see the Customizations table later in this article. For more information about processes for managing customizations, see the white paper [SharePoint Products and Technologies customization policy](https://go.microsoft.com/fwlink/p/?linkid=92311). Most of this content still applies to SharePoint Server 2016. + + +- **Policies around using the App Catalog and SharePoint Store** Which apps for SharePoint do you want to make available to your organization? Can users purchase apps directly? See [Solutions or apps for SharePoint?](#SolutionsApps) later in this article for more information. + + +The highly customizable design of SharePoint products enables you to provide the look, behavior, or functionality that meets your business needs. Customizations can introduce risk to your environment, whether that risk is to the environment’s performance, availability, or supportability. Conversely, a "no customizations" policy severely restricts your organization’s ability to take advantage of the SharePoint platform.All customizations are not the same. You must decide carefully which kinds of customizations to allow in your environment. You must ensure the customizations support the performance, availability, and supportability you want for your environment. Your governance policy should balance a level of acceptable risk against the business needs for your organization.What is considered a customization? All of the following are considered kinds of customizations in SharePoint products: +- **Configuration**    Using the SharePoint user interface to configure SharePoint products. + + +- **Branding**    Changing logos, styles, colors, master pages and page layouts, and so on to create a custom look for your SharePoint sites. See more about [branding](#Branding). + + +- **Custom code**    Using developer tools to add or change functionality in SharePoint products or to interact with other applications. Risk can vary depending on kind of functionality and level of trust (full trust solutions should be rarely used; consider apps for SharePoint first). + + > [!TIP:] + +Some customizations have very little risk or impact on your environment. Others have the potential for much higher risk and impact. The following table provides examples of different kinds of customizations, the risk level associated with that kind of customization, and potential issues that you might face if you allow that kind of customization. +### Customizations + +Risk levelTypes of customizations and examplesConsiderations or impactUnsupported/High
Unsupported customizations such as direct changes to the database schema or modifying files on the file system.
Will not be supported through Microsoft Customer Support.
Will be unable to upgrade.
Do not use.
Moderate to high
Creating applications that interact with or redirect actions in key pipelines, such as events, claims, and so on. 
Potential for service outage or performance issues.
Might require rework at upgrade.
Moderate to low
Using a custom Web Part outside a sandbox environment, creating custom actions such as adding a menu item, or creating a custom site provisioning process.
Short or long-term performance issues or page errors.
Might require rework at upgrade.
Low
Using solutions in a sandbox environment.
Short-term performance issues; you can avoid some performance issues by using resource throttling and quotas.
Very low to no risk
Using apps for SharePoint or using functionality within the product or configurations, such as associating a workflow with a list or using an instance of a built in Web Part.
Minor configuration or page errors that would have to be addressed. Apps can be uninstalled or updated.
+> [!NOTE:] + + + + + +Also, when you think through the customizations to allow in your environment, consider carefully whether a particular customization is necessary. If it recreates functionality that is already available in the product (such as creating a Web Part that does the same thing as the Content Editor Web Part or the Content by Query Web Part), then that might be unnecessary work. Consider first whether the standard functionality can do what you want, or check the SharePoint Store to see if there is an app for SharePoint available that does what you need. +## Life-cycle management + + +Follow these best practices to manage applications based on SharePoint Server 2016 throughout their life cycle: +- Use separate development, preproduction, and production environments, and keep these environments as synchronized as possible so that you can accurately test your customizations. + + +- Test all customizations before releasing the first time and after any updates have been made before you release them to your production environment. + + +- Use source code control and solution and feature versioning to track changes to code. + + + + + + +![Development, test, and production environments](images/) + + + + + + + + + + + + +## Branding + + +Consistent branding with a corporate style guide makes for more cohesive-looking sites and easier development. Store approved themes in the theme gallery for consistency so that users will know when they visit the site that they are in the right place. SharePoint Server 2016 includes a new feature to use for branding, Design Manager. By using Design Manager, you can create a visual design for your website with whatever web design tool or HTML editor you prefer and then upload that design into SharePoint. Design Manager is the central hub and interface where you manage all aspects of a custom design. Creating the visual design of a site often fits into a larger process, in which multiple people or organizations are involved. For a roadmap of the tasks from a larger perspective, see [Design and branding in SharePoint 2013](https://go.microsoft.com/fwlink/?LinkId=262838). +## Solutions or apps for SharePoint? + + +SharePoint Server 2016 has a new development model based on apps for SharePoint. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint features such as lists, workflows, and site pages, but it can also use a remote web application and remote data in SharePoint. An app has few or no dependencies on any other software on the device or platform where it is installed, other than what is built into the platform. Apps have no custom code that runs on the SharePoint servers.The guidance for whether to use apps for SharePoint or SharePoint solutions is to: +- **Design apps for end users** + + Apps for SharePoint: + + - Are easy for users (tenant administrators and site owners) to discover and install. + + + - Use safe SharePoint extensions. + + + - Provide the flexibility to develop future upgrades. + + + - Can integrate with cloud-based resources. + + + - Are available for both SharePoint Online and on-premises SharePoint sites. + + +- **Use farm solutions for administrators** + + SharePoint solutions: + + - Can access the server-side object-model APIs that are needed to extend SharePoint management, configuration, and security + + + - Can extend Central Administration, Microsoft PowerShell cmdlets, timer jobs, custom backups, and so on. + + + - Are installed by administrators. + + + - Can have farm, web application, or site-collection scope. + + +Go to MSDN to get more information about the [new development model](https://go.microsoft.com/fwlink/?LinkId=330807), [Apps for SharePoint compared with SharePoint solutions](https://go.microsoft.com/fwlink/?LinkId=330806), and [Deciding between apps for SharePoint and SharePoint solutions](https://go.microsoft.com/fwlink/?LinkID=330807). Set a policy for using apps for SharePoint in your organization. Can users purchase and download apps? How do you make your organization’s apps available? How do you tell if they’re being used? +- **SharePoint Store**    Determine whether users can purchase or download apps from the SharePoint Store. + + +- **App Catalog**    Make specific apps for SharePoint available to your users by adding them to the App Catalog. + + +- **App requests**    Configure app requests to control which apps are purchased and how many licenses are available. + + +- **Monitor apps**    Monitor specific apps in SharePoint Server 2016 to check for errors and to track usage. + + +Get more information about apps for SharePoint and [governance for apps](plan-for-apps-for-sharepoint-server.md#AppPolicy) in the [Plan for apps for SharePoint Server](html/plan-for-apps-for-sharepoint-server.md) article. +# See also + +#### + + [What is governance in SharePoint?](html/what-is-governance-in-sharepoint.md) + + + + [IT governance in SharePoint](html/it-governance-in-sharepoint.md) + + + + +#### + + **Governance planning in SharePoint** + + + + **Information management and governance in SharePoint** + + + + [Build sites for SharePoint 2013](https://go.microsoft.com/fwlink/?LinkID=330803) + + + + [What is governance poster (Visio format)](https://go.microsoft.com/fwlink/?LinkId=331050) + + + + [What is governance poster (PDF format)](https://go.microsoft.com/fwlink/?LinkId=331051) + + + + + + + + diff --git a/SharePoint/application-pools-recycle-when-memory-limits-are-exceeded-sharepoint-server-2016.md b/SharePoint/application-pools-recycle-when-memory-limits-are-exceeded-sharepoint-server-2016.md new file mode 100644 index 0000000000..0cb29b6dc6 --- /dev/null +++ b/SharePoint/application-pools-recycle-when-memory-limits-are-exceeded-sharepoint-server-2016.md @@ -0,0 +1,50 @@ +--- +title: Application pools recycle when memory limits are exceeded (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: 9ccce076-f47b-44b8-9ec3-e0dcd46e9985 +--- + + +# Application pools recycle when memory limits are exceeded (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "Application pools recycle when memory limits are exceeded" for SharePoint Server 2016. **Rule Name:**    Application pools recycle when memory limits are exceeded. **Summary:**   Application pools recycle because memory limits have been enabled and exceeded. Recycling based on memory limits is not usually necessary in a 64-bit environment, and therefore recycling should not be enabled. Unnecessary recycling can result in dropped requests from the recycled worker process and slow performance for end users who are making requests to the new worker process. **Cause:** Application pools are configured to recycle when memory limits are exceeded. **Resolution: Change the application pool recycling settings in Internet Information Services (IIS).** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. Identify the server on which this event occurs. On the SharePoint Central Administration website, in the **Monitoring** section, click **Review problems and solutions**, and then find the name of the server in the **Failing Servers** column. If there are multiple failing servers in a server farm, you must repeat the following steps on each failing server. + + +3. Verify that the user account that is performing the following steps is a member of the Administrators group on the local computer that you identified in the previous step. + + +4. Log on to the server on which this event occurs. + + +5. In Server Manager, click **Tools**, and then click **Internet Information Services (IIS) Manager**. + + +6. In the Internet Information Services management console, in the **Connections** pane, expand the tree view, and then click **Application Pools**. + + +7. In the **Application Pools** list, right-click the application pool on which you want to disable the memory limits, and then click **Recycling**. + + +8. In the **Edit Application Pool Recycling Settings** dialog box, in the **Memory Based Maximums** section, clear the **Virtual memory usage (in KB)** and **Private memory usage (in KB)** check boxes, and then click **Next**. + + +9. In the **Recycling Events to Log** dialog box, click **Finish**. + + + +# See also + +#### + + [Recycling Settings for an Application Pool ](http://go.microsoft.com/fwlink/?LinkID=761158&clcid=0x409) + + + + + + + + diff --git a/SharePoint/assign-or-remove-administrators-of-service-applications-in-sharepoint-server.md b/SharePoint/assign-or-remove-administrators-of-service-applications-in-sharepoint-server.md new file mode 100644 index 0000000000..e59f1f2fff --- /dev/null +++ b/SharePoint/assign-or-remove-administrators-of-service-applications-in-sharepoint-server.md @@ -0,0 +1,197 @@ +--- +title: Assign or remove administrators of service applications in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 4fceb168-753a-4227-8a23-ab415f9abce7 +--- + + +# Assign or remove administrators of service applications in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-25* **Summary:** Learn how to assign or remove service administrators to a service application in SharePoint Server 2016 and SharePoint Server 2013.An administrator of a SharePoint Server service application can assign additional administrators to that service application. These users are granted security-trimmed access to the SharePoint Central Administration Web site and can manage settings related to the service application. An administrator of a SharePoint Server service application can also remove administrators from a service application. +> [!NOTE:] + + + + + +You can assign or remove service application administrators by using the SharePoint Central Administration websiteor by using Microsoft PowerShell. **To assign or remove administrators to a service application by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. On the Central Administration Home page, in the **Application Management** section, click **Manage service applications**. + + +3. On the Manage Service Applications page, select the row that contains the service application to which you want to add or remove administrators. The ribbon becomes available. + + +4. On the ribbon, click **Administrators**. + + +5. To add an administrator: + +1. In the first text box on the page, type the user accounts or groups that you want to add. You can click the **People** icon to validate a name. You can click the **Address book** icon to search for users to add. You can add multiple administrators into the text box. + + +2. After you have added the administrators, click **OK**. + + + + + + +6. To remove an administrator: + +1. In the second text box on the page, select the administrator whom you want to remove. Note that this step does not remove the user from the system—it merely revokes the user’s administrative permissions to the selected service application. + + +2. Click **Remove**. + + +3. After you have finished removing administrators, click **OK**. + + + **To assign or remove administrators to a service application by using PowerShell** +1. Verify that you meet the following minimum requirements: + + - You must have membership in the **securityadmin** fixed server role on the SQL Server instance + + + - You must have membership in the **db_owner** fixed database role on all databases that are to be updated. + + + - You must be a member of the Administrators group on the server on which you are running the PowerShell cmdlet. + + + + > [!NOTE:] + + + For additional information about PowerShell permissions, see [Permissions](ae4901b4-505a-42a9-b8d4-fca778abc12e.md#section3) and **Add-SPShellAdmin** + + +2. Start the SharePoint Management Shell. + + +3. To create a claims principal, at the PowerShell command prompt, type the following command: + + ``` + +$principal = New-SPClaimsPrincipal " " -IdentityType WindowsSamAccountName + + ``` + + + Where ** is the user name for which you want to assign administrative permissions. The user name should be entered in the form of **jane@contoso.com** or **contoso\\jane**. The new claims principal is stored in the *$principal* variable. + + +4. To retrieve the service application, type the following command: + + ``` + +$spapp = Get-SPServiceApplication -Name " " + ``` + + + Where ** is the display name of the service application. The service application identification is stored in the *$spapp* variable. + + > [!IMPORTANT:] + +5. To retrieve the administrator security object for the service application, type the following command: + + ``` + +$security = Get-SPServiceApplicationSecurity $spapp -Admin + ``` + + + The retrieved administrator security object is stored in the *$security* variable. + + > [!WARNING:] + +6. To assign or revoke administrative permissions for the user who is identified by the new claims principal *$principal* (created in step 6 of this procedure) to the service application administrator security object *$security* (obtained in step 8 of this procedure), use the appropriate command as shown in the following example: + +1. To assign administrative permissions, type the following command: + + ``` + +Grant-SPObjectSecurity $security $principal "Full Control" + + ``` + +2. To revoke administrative permissions, type the following command: + + ``` + +Revoke-SPObjectSecurity $security $principal + ``` + +7. To assign the updated *$security* security object to the service application, type the following command: + + ``` + Set-SPServiceApplicationSecurity $spapp $security -Admin + ``` + + + > [!WARNING:] + +8. To confirm that the service application’s security object is updated appropriately, type the following command: + + ``` + +(Get-SPServiceApplicationSecurity $spapp -Admin).AccessRules + + ``` + + +## Examples + +In the following example, the service account user "contoso\\jane" is added to the administrators security object for the service application named "Contoso Visio Graphics". +``` + +$principal = New-SPClaimsPrincipal "contoso\\jane" -IdentityType WindowsSamAccountName +$spapp = Get-SPServiceApplication -Name "Contoso Visio Graphics" +$security = Get-SPServiceApplicationSecurity $spapp -Admin +Grant-SPObjectSecurity $security $principal "Full Control" +Set-SPServiceApplicationSecurity $spapp $security -Admin +(Get-SPServiceApplicationSecurity $spapp -Admin).AccessRules +``` + +In the following example, the service account user "contoso\\jane" is removed from the administrators security object for the service application named "Contoso Visio Graphics". + + +``` + +$principal = New-SPClaimsPrincipal "contoso\\jane" -IdentityType WindowsSamAccountName +$spapp = Get-SPServiceApplication -Name "Contoso Visio Graphics" +$security = Get-SPServiceApplicationSecurity $spapp -Admin +Revoke-SPObjectSecurity $security $principal "Full Control" +Set-SPServiceApplicationSecurity $spapp $security -Admin +(Get-SPServiceApplicationSecurity $spapp -Admin).AccessRules +``` + +For more information, see the following Microsoft PowerShell articles: +- **New-SPClaimsPrincipal** + + +- **Get-SPServiceApplication** + + +- **Get-SPServiceApplicationSecurity** + + +- **Grant-SPObjectSecurity** + + +- **Revoke-SPObjectSecurity** + + +- **Set-SPServiceApplicationSecurity** + + + +> [!NOTE:] + + + + + + diff --git a/SharePoint/attach-and-restore-read-only-content-databases-in-sharepoint-server.md b/SharePoint/attach-and-restore-read-only-content-databases-in-sharepoint-server.md new file mode 100644 index 0000000000..c15407fafe --- /dev/null +++ b/SharePoint/attach-and-restore-read-only-content-databases-in-sharepoint-server.md @@ -0,0 +1,94 @@ +--- +title: Attach and restore read-only content databases in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 5417b04a-c7d9-4e9a-86fb-ee1d1c63508b +--- + + +# Attach and restore read-only content databases in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to attach and restore a read-only content database in SharePoint Server 2013 and SharePoint Server 2016.You can attach and restore a read-only content database in SharePoint Server by using PowerShell.In this article: +- [Before you begin](#begin) + + +- [Using Windows PowerShell to attach and restore a read-only content database](#proc1) + + - [To attach and restore a read-only content database by using Windows PowerShell](#PS) + + + +## Before you begin + + +A SharePoint Server farm in which content databases are set to be read-only can be part of a failure recovery environment that runs against mirrored or log-shipped content databases or part of a highly available maintenance or patching environment that provides user access when another version of the farm is being updated.Before you begin this operation, review the following information about prerequisites: +- When you re-attach the read-only databases, they become read-write. + + +- For more information about how to use read-only databases, see [Run a farm that uses read-only databases in SharePoint Server](html/run-a-farm-that-uses-read-only-databases-in-sharepoint-server.md). + + + +## Using PowerShell to attach and restore a read-only content database + + +You can use only PowerShell to attach and restore a read-only content database. **To attach and restore a read-only content database by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Mount-SPContentDatabase -Name -WebApplication [-Verbose] + ``` + + + + + Where: + + - ** is name of the read-only database. + + + - ** is ID assigned to the read-only database. + + + + > [!NOTE:] + +For more information, see **Mount-SPContentDatabase**. +> [!NOTE:] + + + + + + +# See also + +#### + + [Overview of backup and recovery in SharePoint Server](html/overview-of-backup-and-recovery-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/attach-or-detach-content-databases-in-sharepoint-server.md b/SharePoint/attach-or-detach-content-databases-in-sharepoint-server.md new file mode 100644 index 0000000000..79897b2479 --- /dev/null +++ b/SharePoint/attach-or-detach-content-databases-in-sharepoint-server.md @@ -0,0 +1,200 @@ +--- +title: Attach or detach content databases in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: bfa2f924-f411-4b13-8c24-bf251d7e4c91 +--- + + +# Attach or detach content databases in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-21* **Summary:** Learn how to attach and detach content databases to your SharePoint Server 2016 and SharePoint Server 2013 farm.You can attach or detach SharePoint Server content databases by using the SharePoint Central Administration website or Windows PowerShell 3.0In this article: +- [Before you begin](#begin) + + +- [Attaching and detaching content databases](#proc1) + + - [To attach a content database by using Central Administration](#CA) + + + - [To detach a content database by using Central Administration](#detachCA) + + + - [To attach or detach a content database by using Windows PowerShell](#PS) + + + +## Before you begin + + +Before you begin this operation, review the following information: +- If you want to create a new content database while you attach it, the SharePoint farm service account must be a member of the SQL Server **dbcreator** fixed server role. To attach a content database to a web application, the SharePoint farm service account must have **db_owner** permission for the content database. + + +- If the database already exists, it must be the same version as the SharePoint Server 2016 farm or this operation will fail. To attach a content database that is a different version than the farm, use the [To attach or detach a content database by using Windows PowerShell](#PS) procedure in the following section. + + + +## Attaching and detaching content databases + + +You might want to attach or detach content databases for the following reasons. You want to add a new content database for new site collections to keep content databases at a manageable size. You are restoring a content database from another farm and you want the sites that it contains to be accessed from a web application. You have archived site collections out of a content database and then detach the content database from the web application. For more information, see [Move site collections between databases in SharePoint Server](html/move-site-collections-between-databases-in-sharepoint-server.md)The steps to add a database and to attach a database are very similar. For more information about how to add a database, see [Add content databases in SharePoint Server](html/add-content-databases-in-sharepoint-server.md). **To attach a content database by using Central Administration** +1. Verify that the user account that is being used to perform this operation is a member of the Farm Administrators SharePoint group. + + +2. Start Central Administration. + + +3. On the SharePoint Central Administration website, click **Application Management**. + + +4. On the **Application Management** page, in the **Databases** section, click **Manage content databases**. + + +5. On the **Manage Content Databases** page, click **Add a content database**. + + +6. On the **Add Content Database** page: + +1. Use the Web Application drop-down menu to select the web application to which you want to attach a content database. + + +2. Specify the database server that hosts the database. + + +3. Specify the database name. If the database does not already exist, it will be created. + + +4. Specify the authentication method for the database, and supply an account name and password if you are using SQL authentication. + + + + > [!IMPORTANT:] + + + + + +5. Click **OK**. + + + **To detach a content database by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. + + +2. On the SharePoint Central Administration website, click **Application Management**. + + +3. On the **Application Management** page, in the **Databases** section, click **Manage content databases**. + + +4. Select the web application for which you want to detach a content database. + + +5. Click the content database that you want to detach. + + +6. On the **Manage Content Database Settings** page, select the **Remove content database** check box. + + If the content database contains data, you will receive a warning. Click **OK** to continue with the operation. + + +7. Click **OK** to confirm the detachment, or click **Cancel** to stop the operation without detaching the database. + + After detaching the content database in Central Administration, the content database still exists in SQL Server. If you want to permanently remove the content database, you must do so by using a SQL Server procedure. + + + **To attach or detach a content database by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Open **SharePoint Management Shell**. + + +3. At the PowerShell command prompt, type the appropriate command + + **To attach an existing content database:** + + + + ``` + +Mount-SPContentDatabase " " -DatabaseServer " " -WebApplication http://SiteName + ``` + + + + + Where: + + - ** is the content database to be attached. + + + - ** is the name of the database server. + + + - *http://SiteName* is the name of the web application to which the content database is being attached. + + + + + + **To detach a content database:** + + + + ``` + Dismount-SPContentDatabase " " + ``` + + + + + Where ** is the name of the content database. + + > [!IMPORTANT:] + + + The **Dismount-SPContentDatabase** cmdlet detaches the content database from the web application, but it does not delete the content database from SQL Server. After a content database is detached, you cannot delete it by using PowerShell. You can only remove it by using SQL Server tools. If you want to delete the content database from SQL Server while you detach it, use the **Remove-SPContentDatabase** cmdlet instead. + + +For more information, see **Dismount-SPContentDatabase** and **Mount-SPContentDatabase**. +> [!NOTE:] + + + + + + +# See also + +#### + + **Get-SPContentDatabase** + + + + **New-SPContentDatabase** + + + + **Remove-SPContentDatabase** + + + + + + + + diff --git a/SharePoint/authentication-for-mobile-devices-in-sharepoint-2013.md b/SharePoint/authentication-for-mobile-devices-in-sharepoint-2013.md new file mode 100644 index 0000000000..3252d36b2f --- /dev/null +++ b/SharePoint/authentication-for-mobile-devices-in-sharepoint-2013.md @@ -0,0 +1,70 @@ +--- +title: Authentication for mobile devices in SharePoint 2013 +ms.prod: SHAREPOINT +ms.assetid: ad6a501d-5d8c-4b87-af69-7f655b8c3d1e +--- + + +# Authentication for mobile devices in SharePoint 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Internet Explorer, OneDrive, SharePoint Server 2013* * **Topic Last Modified:** 2017-07-20* This article contains information about the supported authentication types for select devices in SharePoint Server 2013.In this article: +- [Plan for mobile device security](#PlanMobileDeviceSecurity) + + +- [Authentication for mobile devices](#AuthenticationMobileDevices) + + + +## Plan for mobile device security + + +Authentication is one aspect of security that you must consider to make sure that SharePoint Server 2013 is not compromised. We recommend that you consult the following articles to make sure that your corporate data is safe: +- [Mobile security and authentication in SharePoint 2013](html/mobile-security-and-authentication-in-sharepoint-2013.md) (http://technet.microsoft.com/en-us/library/fp161350(v=office.15).aspx) + + +- [Microsoft Safety & Security Center – Mobile and wireless](http://go.microsoft.com/fwlink/?LinkID=533039&clcid=0x409 ) (http://go.microsoft.com/fwlink/?LinkID=533039&clcid=0x409) + + +- [Microsoft Safety & Security Center – Get smart about mobile phone safety](https://www.microsoft.com/security/online-privacy/mobile-phone-safety.aspx) (https://www.microsoft.com/security/online-privacy/mobile-phone-safety.aspx) + + +SharePoint Server 2013 supports multiple authentication methods and authentication modes. Not all mobile browsers and devices work with all the available authentication methods. When you plan for mobile device access, you must do the following: +- Determine the mobile devices that you must support. Then, learn the authentication methods that are supported by the mobile devices. This information varies by manufacturer. + + +- Determine the sites that you want to make available to your mobile device users. + + +- Determine whether you want to make SharePoint sites available for mobile devices when the devices are used outside the corporate firewall. If you do, the method that you use to enable external access can also affect mobile device authentication. + + + +## Authentication for mobile devices + + +The following tables detail the authentication types for browsers and Office Hub Windows Phone experience in SharePoint Server 2013. +### Table: Mobile authentication support for SharePoint browsers + +SharePoint InfrastructureAuthentication modeAuthentication providerWindows Phone 7.5 or later versions (Internet Explorer Mobile)iOS 5.0 or later versions (iPad, iPhone using Safari)SharePoint on-premises
NTLM
Active Directory
Supported
Supported
SharePoint on-premises
Basic authentication
Active Directory
Supported
Supported
SharePoint on-premises
SAML
WS-Federation 1.1 compatible Identity Provider
Supported
Supported
SharePoint Online
Forms-based authentication
Org-ID
Supported
Supported
+### Table: Mobile authentication support for Office Hub + +SharePoint infrastructureAuthentication modeAuthentication providerWindows Phone 7.5 or later versionsSharePoint on-premises
NTLM
Active Directory
Supported
SharePoint on-premises
Basic authentication
Active Directory
Not supported
SharePoint on-premises
SAML
WS-Federation 1.1 compatible Identity Provider
Not supported
SharePoint Online
Forms-based authentication
Org-ID
Supported
+> [!IMPORTANT:] + + + + + + +# See also + +#### + + [Overview of mobile devices and SharePoint Server 2013](html/overview-of-mobile-devices-and-sharepoint-server-2013.md) + + + + + + + + diff --git a/SharePoint/authentication-overview-for-sharepoint-server.md b/SharePoint/authentication-overview-for-sharepoint-server.md new file mode 100644 index 0000000000..64187e0701 --- /dev/null +++ b/SharePoint/authentication-overview-for-sharepoint-server.md @@ -0,0 +1,211 @@ +--- +title: Authentication overview for SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 403e75f3-9e53-4d5b-a476-365e6e4bc92e +--- + + +# Authentication overview for SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-06-21* **Summary:** Learn about how user authentication, app authentication, and server-to-server authentication work in SharePoint Server 2013 and SharePoint Server 2016 .SharePoint Server requires authentication for the following types of interactions: +- Users who access on-premises SharePoint resources + + +- Apps that access on-premises SharePoint resources + + +- On-premises servers that access on-premises SharePoint resources, or vice versa + + +In this article: +- [User authentication](#userauth) + + +- [App authentication](#appauth) + + +- [Server-to-server authentication](#s2sauth) + + + +## User authentication in SharePoint Server + + +User authentication is the validation of a user's identity against an authentication provider, which is a directory or database that contains the user’s credentials and can verify that the user submitted them correctly. User authentication occurs when a user attempts to access a SharePoint resource.SharePoint Server supports claims-based authentication.The result of a claims-based authentication is a claims-based security token, which the SharePoint Security Token Service (STS) generates. SharePoint Server supports Windows, forms-based, and Security Assertion Markup Language (SAML)-based claims authentication. For information about how these three authentication methods work, see the following videos. +> [!NOTE:] + + + + + + **Windows claims authentication in SharePoint Server 2013 and 2016 video** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + **Forms-based claims authentication in SharePoint Server 2013 and 2016 video** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + **SAML-based claims authentication in SharePoint Server 2013 and 2016 video** + + + +![Video (play button) icon](images/) + + + + + + + + + + + +For more information, see [Plan for user authentication methods in SharePoint Server](html/plan-for-user-authentication-methods-in-sharepoint-server.md). +## App authentication in SharePoint Server + + +App authentication is the validation of a remote SharePoint app's identity and the authorization of the app and an associated user of a secured SharePoint resource request. App authentication occurs when an external component of a SharePoint Store app or an App Catalog app, such as a web server that is located on the intranet or the Internet, attempts to access a secured SharePoint resource. For example, suppose that a user opens a SharePoint page that contains an IFRAME of a SharePoint app, and that IFRAME needs an external component, such as a server on the intranet or the Internet, to access a secured SharePoint resource in order to render the page. The external component of the SharePoint app must be authenticated and authorized so that SharePoint provides the requested information and the app can render the page for the user.Note that if the SharePoint app does not require a SharePoint secured resource to render the page for the user, app authentication is not needed. For example, a SharePoint app that provides weather forecast information and only has to access a weather information server on the Internet does not have to use app authentication. App authentication is a combination of two processes: +- Authentication + + Verifying that the application has registered correctly with a commonly trusted identity broker + + +- Authorization + + Verifying that the application and the associated user for the request has the appropriate permissions to perform its operation, such as accessing a folder or list or executing a query + + +To perform app authentication, the application obtains an access token either from the Microsoft Azure Access Control Service (ACS) or by self-signing an access token using a certificate that SharePoint Server trusts. The access token asserts a request for access to a specific SharePoint resource and contains information that identifies the app and the associated user, instead of the validation of the user’s credentials. The access token is not a logon token. For SharePoint Store apps, an example of the authentication process is as follows: +1. A user opens a SharePoint web page that contains an IFRAME that has to be rendered by a SharePoint Store app, which is hosted on the Internet and uses ACS as its trust broker. To render the IFRAME for the user, the SharePoint Store app must access a SharePoint resource. + + +2. The SharePoint STS requests and receives a context token from ACS. + + +3. SharePoint sends the requested web page together with the context token to the user’s web browser. + + +4. The user’s web browser sends a request for the IFRAME’s content and the context token to the SharePoint Store app server on the Internet. + + +5. The SharePoint Store app server requests and receives an access token from ACS. + + +6. The SharePoint Store app server sends the SharePoint resource request and the access token to the SharePoint server. + + +7. The SharePoint server authorizes the access, checking both the app’s permissions, which were specified when the app was installed, and the associated user’s permissions. + + +8. If permitted, SharePoint sends the requested data to the SharePoint Store app server on the Internet. + + +9. The SharePoint Store app server on the Internet sends the IFRAME results to the web browser, which renders the IFRAME portion of the page for the user. + + +Notice how the SharePoint Store app has accessed SharePoint server resources without having to obtain the user’s credentials. The access was authenticated through ACS, which is trusted by the server running SharePoint Server, and authorized through the set of app and user permissions.For SharePoint App Catalog apps, an example of the authentication process is as follows: +1. A user opens a SharePoint web page that contains an IFRAME that has to be rendered by an App Catalog app that is hosted on the intranet and uses a self-signed certificate for its access tokens. To render the IFRAME for the user, the App Catalog app must access a SharePoint resource. + + +2. SharePoint sends the requested page along with the IFRAME to the user’s web browser. + + +3. The user’s web browser sends a request for the IFRAME’s content to the App Catalog app server on the intranet. + + +4. The App Catalog app server authenticates the user and generates an access token, signed with its self-signed certificate. + + +5. The App Catalog app server sends the SharePoint resource request and the access token to the SharePoint server. + + +6. The SharePoint server authorizes the access, checking both the app’s permissions, which were specified when the app was installed, and the associated user’s permissions. + + +7. If permitted, the SharePoint server sends the requested data to the App Catalog app server on the intranet. + + +8. The App Catalog app server sends the IFRAME results to the web browser, which renders the IFRAME portion of the page for the user. + + + +> [!NOTE:] + + + + + +For more information, see **Plan for app authentication in SharePoint 2013**. +## Server-to-server authentication in SharePoint Server + + +Server-to-server authentication is the validation of a server's request for resources that is based on a trust relationship established between the STS of the server that runs SharePoint Server and the STS of another server that supports the OAuth server-to-server protocol, such as on-premises running SharePoint Server, Exchange Server 2016, Skype for Business 2016, or Azure Workflow Service, and SharePoint Server running in Office 365. Based on this trust relationship, a requesting server can access secured resources on the SharePoint server on behalf of a specified user account, subject to server and user permissions.For example, a server running Exchange Server 2016 can request resources of a server running SharePoint Server for a specific user account. This contrasts with app authentication, in which the app does not have access to user account credential information. The user can be currently signed in to the server making the resource request or not, depending on the service and the request.When a server running SharePoint Server attempts to access a resource on a server or a server attempts to access a resource on a server running SharePoint Server, the incoming access request must be authenticated so that the server accepts the incoming access request and subsequent data. Server-to-server authentication verifies that the server running SharePoint Server and the user whom it is representing are trusted.The token that is used for a server-to-server authentication is a server-to-server token, not a logon token. The server-to-server token contains information about the server that requests access and the user account on whose behalf the server is acting.For on-premises servers, an example basic process is as follows: +1. A user opens a SharePoint web page that requires information from another server (for example, display the list of tasks from both SharePoint Server and Exchange Server 2016). + + +2. SharePoint Server generates a server-to-server token. + + +3. SharePoint Server sends the server-to-server token to the other server. + + +4. The other server validates the SharePoint server-to-server token. + + +5. The other server sends a message to SharePoint Server to indicate that the sent server-to-server token was valid. + + +6. The service on the server running SharePoint Server accesses the data on the server. + + +7. The service on the server running SharePoint Server renders the page for the user. + + +When both servers are running in Office 365, an example process is as follows: +1. A user opens a SharePoint web page that requires information from another server (for example, display the list of tasks from both SharePoint Online and Exchange Online). + + +2. SharePoint Online requests and receives a server-to-server token from ACS. + + +3. SharePoint Online sends the server-to-server token to the Office 365 server. + + +4. The Office 365 server verifies the user identity in the server-to-server token with ACS. + + +5. The Office 365 server sends a message to SharePoint Online to indicate that the sent server-to-server token was valid. + + +6. The service on SharePoint Online accesses the data on the Office 365 server. + + +7. The service on SharePoint Online renders the page for the user. + + +For more information, see [Plan for server-to-server authentication in SharePoint Server](html/plan-for-server-to-server-authentication-in-sharepoint-server.md). diff --git a/SharePoint/automatic-update-setting-inconsistent-across-farm-servers-sharepoint-server-2016.md b/SharePoint/automatic-update-setting-inconsistent-across-farm-servers-sharepoint-server-2016.md new file mode 100644 index 0000000000..adadb759b8 --- /dev/null +++ b/SharePoint/automatic-update-setting-inconsistent-across-farm-servers-sharepoint-server-2016.md @@ -0,0 +1,20 @@ +--- +title: Automatic Update setting inconsistent across farm servers (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: 2ddb9cfe-38fc-477c-88d1-beb190e36ab0 +--- + + +# Automatic Update setting inconsistent across farm servers (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "Automatic update setting inconsistent across farm servers", for SharePoint Server 2016. **Rule Name:**   Automatic update setting inconsistent across farm servers. **Summary:**    Servers in the SharePoint farm do not have the same Automatic Update settings configured. **Cause:**   One or more servers in the farm have update settings that are different from the other servers in the farm. **Resolution: Ensure all servers in the farm have the same update settings** +1. Verify that you are a member of the Administrators group on the local computer. + + +2. In Control Panel, click **System and Security**, and then under **Windows Update**, click **Turn automatic updating on or off**. + + +3. On the Choose your Windows Update settings page, make sure that the update settings are the same as other servers in your farm. Change the update settings if needed. + + > [!NOTE:] + + diff --git a/SharePoint/back-up-apps-for-sharepoint-in-sharepoint-server.md b/SharePoint/back-up-apps-for-sharepoint-in-sharepoint-server.md new file mode 100644 index 0000000000..0897040078 --- /dev/null +++ b/SharePoint/back-up-apps-for-sharepoint-in-sharepoint-server.md @@ -0,0 +1,156 @@ +--- +title: Back up apps for SharePoint in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: a193cfdb-ac5e-45fa-bf83-87849e38ac27 +--- + + +# Back up apps for SharePoint in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** apps for SharePoint, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Learn how to back up apps for SharePoint Server in SharePoint Server 2013 and SharePoint Server 2016.We recommend that you regularly back up at the farm level. However, business or IT requirements might require you to back up the apps for SharePoint in addition to normal farm backups. If you regularly back up the apps for SharePoint environment, you reduce the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that helps make sure that data and configurations that compose the apps for SharePoint environment are available for recovery, if that is required. The app for SharePoint content and packages are in the SharePoint ServerUNRESOLVED_TOKEN_VAL() content databases in individual site collections. All app for SharePoint license and security data is stored in the App Management Service and the Secure Store Service application databases. Additional app for SharePoint data is stored in the SharePoint Server configuration database, in the form of Internet Information Services (IIS) web sites or web applications, and Web Part packages. You must back up the following SharePoint Server databases at the same time: +- Content - WSS_Content + + +- Configuration - SharePoint_Config + + +- Secure Store Service application - Secure_Store_Service_DB_ + + +- App Management service application - App_Management_ + + +If you have to eventually restore the databases, you have to restore the same version of each database that you backed up. In other words, don't restore a content database that's six months older than the configuration database.For more information about the SharePoint Server databases, see [Database types and descriptions in SharePoint Server](html/database-types-and-descriptions-in-sharepoint-server.md). You can back up an apps for SharePoint environment by using the SharePoint Central Administration website, Microsoft PowerShell, or SQL Server tools.In this article: +- [Back up content databases](#proc1) + + +- [Back up the configuration database](#proc2) + + +- [Back up the Secure Store Service application database](#proc3) + + +- [Back up the App Management service application database](#proc4) + + +- [Back up a site collection](#proc5) + + - [To back up a site collection by using Windows PowerShell](#PS) + + + +## Back up content databases + + +Content databases can store data for multiple site collections. However, if you have many site collections, we recommend that you add enough content databases to keep the size of each database below 200 GB for optimal system performance. For more information, see [Back up content databases in SharePoint Server](html/back-up-content-databases-in-sharepoint-server.md). +> [!NOTE:] + + + + + + +## Back up the configuration database + + +The SharePoint Server configuration database stores data about all SharePoint databases and Internet Information Services (IIS) web sites or web applications. This includes trusted solutions, web part packages, site templates, and web application settings, and farm settings that are specific to SharePoint Server, such as default quota and blocked file types. For more information, see [Back up farm configurations in SharePoint Server](html/back-up-farm-configurations-in-sharepoint-server.md). +## Back up the Secure Store Service application database + + +The Secure Store Service database stores and maps credentials such as account names and passwords. To back up the Secure Store database for an apps for SharePoint environment, see [Back up the Secure Store Service in SharePoint Server](html/back-up-the-secure-store-service-in-sharepoint-server.md). +> [!NOTE:] + + + + + + +## Back up the App Management service application database + + +The App Management service application database stores the app licenses and permissions for all apps downloaded from the App Catalog site in SharePoint Server. To back up the App Management database, follow the same procedures as most other SharePoint Server service applications. For more information, see [Back up service applications in SharePoint Server](html/back-up-service-applications-in-sharepoint-server.md). +## Back up a site collection + + +You may have multiple site collections that host apps for SharePoint in your environment. When you backup apps for SharePoint you must also back up all site collections where the apps are hosted. **To back up a site collection by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPSite -Identity -Path [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose] + ``` + + + + + Where: + + - ** is the ID or URL for the site collection you want to back up. + + + - ** is the path of where the backup file is located. + + + + If you want to overwrite a previously used backup file, use the Force parameter. You can use theNoSiteLock parameter to keep the read-only lock from being set on the site collection while it is being backed up. However, using this parameter can enable users to change the site collection while it is being backed up and could lead to possible data corruption during backup. To display the site collection GUID or URL at the PowerShell command prompt, type the following command: + + + + ``` + Get-SPSite | format-list -property id,url + ``` + + + If the database server is running an Enterprise Edition of SQL Server, we recommend that you also use the UseSqlSnapshot parameter for more consistent backups. You can also export sites or lists from these snapshots. + + > [!NOTE:] + + + For more information about how to use SQL snap-shots, see [Back up databases to snapshots in SharePoint Server](html/back-up-databases-to-snapshots-in-sharepoint-server.md). + + For more details, see [Back up site collections in SharePoint Server](html/back-up-site-collections-in-sharepoint-server.md) + + +For more information, see **Backup-SPSite**. +> [!NOTE:] + + + + + + +# See also + +#### + + [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md) + + + + [Restore apps for SharePoint in SharePoint Server](html/restore-apps-for-sharepoint-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/back-up-content-databases-in-sharepoint-server.md b/SharePoint/back-up-content-databases-in-sharepoint-server.md new file mode 100644 index 0000000000..297dadacce --- /dev/null +++ b/SharePoint/back-up-content-databases-in-sharepoint-server.md @@ -0,0 +1,160 @@ +--- +title: Back up content databases in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: db44c8d7-e081-42a3-a42a-2ee1b369dd47 +--- + + +# Back up content databases in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to back up a single content database in SharePoint Server 2016 and SharePoint Server 2013.You can back up a content database by using the SharePoint Central Administration website, Microsoft PowerShell, or SQL Server tools. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requires, and service level agreements that you have made with your organization. +## Before you begin + + +SharePoint Server content databases can grow to be very large. Therefore, you might want to back them up separately from farm backups. Regularly backing up content databases reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps make sure that all the data is available for recovery, if that is required. You can only back up one content database at a time.Before you begin this operation, review the following information: +- You must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. + + +- SharePoint Server backup backs up remote Binary Large Objects (BLOB) stores but only if you are using the SQL Filestream remote BLOB store provider to place data in remote BLOB stores. + + If you are using another provider you must manually back up these remote BLOB stores. + + +- If you are using SQL Server with Transparent Data Encryption (TDE), and you are backing up your environment by using either SharePoint Server tools or SQL Server tools, the TDE encryption key in not backed up or restored. You must back up the key manually. When restoring, you must manually restore the key before restoring the data. For more information, see [Transparent Data Encryption (TDE)](http://go.microsoft.com/fwlink/p/?LinkID=715778&clcid=0x409). + + + +## Use PowerShell to back up a content database in SharePoint Server + + +You can use PowerShell to back up a content database manually or as part of a script that can be run at scheduled intervals. **To back up a content database by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPFarm -Directory -BackupMethod {Full | Differential} -Item [-Verbose] + ``` + + + + + Where: + + - ** is the path of the backup folder. + + + - ** is the name of the database that you want to back up. To display the name of the content database, type the following command at the PowerShell command prompt:Get-SPContentDatabase. + + + + To view the progress of the backup operation, use the **Verbose** parameter. + + > [!NOTE:] + +For more information, see **Backup-SPFarm**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up a content database in SharePoint Server + + +You can use Central Administration to back up a content database. **To back up a content database by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. + + +2. Start Central Administration. + + +3. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the content database that you want to back up from the list of components, and then click **Next**. + + > [!NOTE:] + +5. On the Start Backup — Step 2 of 2: Select Backup Options page, in the **Backup Type** section, select either **Full** or **Differential**. + + > [!NOTE:] + +6. In the **Backup File Location** section, type the Universal Naming Convention (UNC) path of the backup folder, and then click **Start Backup**. + + +7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the **Readiness** section. You can view the status of the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, review the **Failure Message** column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5. + + + +## Use SQL Server tools to back up a content database in SharePoint Server + + +You can use SQL Server tools to back up a content database. **To back up a content database by using SQL Server tools** +1. Verify that the user account that is performing this procedure is a member of the SQL Server  **db_owner** fixed database role on all databases that are to be backed up. + + +2. Open SQL Server Management Studio and connect to the correct instance of the SQL Server Database Engine. + + +3. In Object Explorer, expand **Databases**. + + +4. Right-click the database that you want to back up, point to **Tasks**, and then click **Back Up**. + + +5. In the **Back Up Database** dialog box, confirm the database name. + + +6. Next, select the kind of backup that you want to perform from the **Backup type** list. For more information about which backup type to use, see [Recovery Models (SQL Server)]( http://go.microsoft.com/fwlink/p/?LinkID=715706&clcid=0x409). + + +7. In the **Backup component** area, click **Database**. + + +8. Either use the default name that is provided or specify a name for the backup set in the **Name** text box. + + +9. In the **Destination** area, specify where you want to store the backup. + + +10. Click **OK** to back up the database. + + +11. Repeat steps 1-10 for each content database. + + + +# See also + +#### + + [Restore content databases in SharePoint Server](html/restore-content-databases-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/back-up-customizations-in-sharepoint-server.md b/SharePoint/back-up-customizations-in-sharepoint-server.md new file mode 100644 index 0000000000..d69bc8db34 --- /dev/null +++ b/SharePoint/back-up-customizations-in-sharepoint-server.md @@ -0,0 +1,267 @@ +--- +title: Back up customizations in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 8f98a750-19bb-4ea0-9ff5-719b85febbb3 +--- + + +# Back up customizations in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to back up customizations that are made to SharePoint Server 2016 and SharePoint Server 2013 sites.You can back up customizations that are made to SharePoint Server sites by using the SharePoint Central Administration website or Microsoft PowerShell. Which backup tool you use depends on what kind of environment you have deployed, what your backup schedule requires, and what service level agreements you have made with your organization. In this article: +- [Before you begin](#begin) + + +- [Back up solution packages in SharePoint](#proc1) + + +- [Back up sandboxed solutions in SharePoint](#SandboxedSolutions) + + +- [Back up authored site elements in SharePoint](#AuthoredSite) + + +- [Back up workflows in SharePoint](#Workflows) + + +- [Back up changes to the Web.config file in SharePoint](#WebConfig) + + +- [Back up third-party products in SharePoint](#ThirdParty) + + +- [Back up developed customizations that are not packaged as solutions in SharePoint](#DevelopedCustomizations) + + + +## Before you begin + + +Before you begin this operation, review the following list of possible customizations that you can make to your sites: +- Customizations packaged as solutions (.wsp files). Solutions contain *developed site elements* , and are typically created by developers. Developed site elements include the following: + + - Web Parts + + + - Workflows + + + - Site and list definitions + + + - Document converters + + + - Event receivers + + + - Timer jobs + + + - Assemblies + + +- Authored site elements, which are typically created by web designers, are not explicitly compiled and are located in a content database. Authored site elements include the following: + + - Master pages + + + - Cascading style sheets + + + - Forms + + + - Layout pages + + +- Changes to the Web.config file + + +- Third-party solutions and their associated binary files and registry keys, such as IFilters + + +- Changes to sites created by direct editing through the browser + + +- Developed customizations that are not packaged as solutions + + + +> [!NOTE:] + + + + + + +## Back up solution packages in SharePoint Server + + +Solution packages can be created by using SharePoint Designer or Visual Studio. We strongly recommend that all customizations be deployed as solution packages. For more information, see [Creating SharePoint Solution Packages](https://docs.microsoft.com/en-us/visualstudio/sharepoint/creating-sharepoint-solution-packages).A solution package is a deployable, reusable file that can contain a set of features, site definitions, and assemblies that apply to sites, and that you can enable or disable individually. Solution packages can include Web Parts, site or list definitions, custom columns, new content types, custom fields, custom actions, coded workflows, or workflow activities and conditions.The method that you use to back up solution packages is determined by whether the customizations are deployed as *trusted solutions* or *sandboxed solutions* (partially trusted code).Trusted solutions are solution packages that farm administrators deploy. Trusted solutions are deployed to the entire farm and can be used on any site within the farm. Trusted solutions are stored in the configuration database. Trusted solutions are backed up when a farm is backed up by using SharePoint Server backup, and are included in configuration-only backups. You can also back up trusted solutions as a group or individually. Trusted solutions are visible in the backup hierarchy.Sandboxed solutions are solution packages that site collection administrators can deploy to a single site collection. Sandboxed solutions are stored in the content database that is associated with the site collection to which the solution packages are deployed. They are included in SharePoint Server farm, web application, content database, and site collection backups, but are not visible in the backup hierarchy and cannot be selected or backed up individually.We recommend that you keep a backup of the original .wsp file and the source code used to build the .wsp file for both trusted solutions and sandboxed solutions. **To back up trusted solutions by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. Start Central Administration. + + +3. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +4. On the **Perform a Backup — Step 1 of 2: Select Component to Back Up** page, select **Solutions**, and then click **Next**. + + You can also select an individual solution, if you only want to back up a single solution. + + +5. On the **Start Backup — Step 2 of 2: Select Backup Options** page, in the **Backup Type** section, select either **Full** or **Differential**. + + > [!NOTE:] + +6. In the **Backup File Location** section, type the Universal Naming Convention (UNC) path of the backup folder, and then click **Start Backup**. + + +7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the **Readiness** section. You can view the status of the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, review the **Failure Message** column of the **Backup and Restore Job Status** page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4. + + + **To back up trusted solutions by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command to back up all of the solutions in the farm. To back up a single solution, add the name of the solution to the item path "farm\\solutions". + + ``` + +Backup-SPFarm -backupmethod full -directory -item "farm\\solutions" + ``` + + + + + Where: + + - ** is the UNC location of the directory where you store the backup file. + + +For more information, see **Backup-SPFarm**. +> [!NOTE:] + + + + + + +## Backing up sandboxed solutions in SharePoint Server + + +You cannot back up only sandboxed solutions. Instead, you must back up the farm, Web application, or content database with which the sandboxed solution is associated. For more information about these methods of backing up, see [Related Topics](#Related). +## Back up authored site elements in SharePoint Server + + +You cannot back up only authored site elements. Instead, you must back up the farm, Web application, or content database with which the authored site element is associated. For more information about these methods of backing up, see [Related Topics](#Related). +## Back up workflows in SharePoint Server + + +Workflows are a special case of customizations that you can back up. Make sure that your backup and recovery plan addresses any of the following scenarios that apply to your environment: +- Declarative workflows, such as those that were created in SharePoint Designer, are stored in the content database for the site collection to which they are deployed. Backing up the content database protects these workflows. + + +- Custom declarative workflow actions have components in the following three locations: + +1. The Visual Studio 2013 assemblies for the actions are stored in the global assembly cache (GAC). + + +2. The XML definition files (.ACTIONS files) are stored in the 16\\TEMPLATE\\< *LCID* >\\Workflow directory. + + +3. An XML entry to mark the action as an authorized type is stored in the Web.config file for the Web applications in which it is used. + + + + If the farm workflows use custom actions, you should use a file backup system to protect these files and XML entries. Similar to SharePoint Server features such as Web Parts and event receivers, these files should be reapplied to the farm as needed after recovery. + + +- Workflows that depend on custom code, such as those that are created by using Visual Studio, are stored in two locations. The Visual Studio assemblies for the workflow are stored in the GAC, and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Server features such as Web Parts and event receivers. If the workflow was installed as part of a solution package, backing up the farm, Web application, content database, or site collection protects these workflows. + + +- If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must back up both site collections to protect the workflow. This includes workflows that write to a history list or other custom list in another site collection. Performing a farm backup is sufficient to back up all site collections in the farm and all workflows that are associated with them. + + +- Workflows that are not yet deployed must be backed up and restored separately. When you are developing a new workflow but have not yet deployed it to the SharePoint Server farm, make sure that you back up the folder where you store the workflow project files by a file system backup application. + + + +## Back up changes to the Web.config file in SharePoint Server + + +A common customization to SharePoint Server is to change the Web.config file. We strongly recommend that you make changes to the Web.config file by using Central Administration or the SharePoint Server APIs and object model. Because these changes are stored in the configuration database, they can be recovered from a farm or configuration-only backup. Changes to the Web.config file that are not made by using Central Administration or the SharePoint Server APIs and object model should be protected by using a file system backup. +> [!NOTE:] + + + + + + +## Back up third-party products in SharePoint Server + + +If third-party products are deployed as solution packages, they are protected by SharePoint Server backup. We recommend that you keep all the original files, distribution media, documentation, and the license and product keys that are required for installation. +## Back up developed customizations that are not packaged as solutions in SharePoint Server + + +Backing up developed customizations that are not deployed as solution packages can be a complex process because the customization file locations might not be stored in standardized places and SharePoint Server does not automatically back them up.Consult with the development team or customization vendor to determine whether the customizations involve additional add-in software or files in other locations. We recommend that you back up these directories with a file system backup solution. The following table lists locations where developed customizations are typically stored on Web servers. +### + +Location Description %PROGRAMFILES%\\Common files\\Microsoft Shared\\Web Server Extensions\\16
Commonly updated files, custom assemblies, custom templates, custom site definitions
Inetpub
Location of IIS virtual directories
%WINDIR%\\Assembly
Global assembly cache (GAC): a protected operating system location where the Microsoft .NET Framework code assemblies are installed to provide full system access
+# See also + +#### + + [Restore customizations in SharePoint Server](html/restore-customizations-in-sharepoint-server.md) + + + + [Back up farms in SharePoint Server](html/back-up-farms-in-sharepoint-server.md) + + + + [Back up farm configurations in SharePoint Server](html/back-up-farm-configurations-in-sharepoint-server.md) + + + + [Back up web applications in SharePoint Server](html/back-up-web-applications-in-sharepoint-server.md) + + + + [Back up content databases in SharePoint Server](html/back-up-content-databases-in-sharepoint-server.md) + + + + [Back up site collections in SharePoint Server](html/back-up-site-collections-in-sharepoint-server.md) + + + + [Update Workflow in SharePoint Server 2013](html/update-workflow-in-sharepoint-server-2013.md) + + + + + + + + diff --git a/SharePoint/back-up-databases-to-snapshots-in-sharepoint-server.md b/SharePoint/back-up-databases-to-snapshots-in-sharepoint-server.md new file mode 100644 index 0000000000..218ac7ca81 --- /dev/null +++ b/SharePoint/back-up-databases-to-snapshots-in-sharepoint-server.md @@ -0,0 +1,73 @@ +--- +title: Back up databases to snapshots in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 101dd661-8843-4b98-bab7-89c14abe65b8 +--- + + +# Back up databases to snapshots in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to back up databases to snapshots in SharePoint Server 2016 and SharePoint Server 2013 by using SQL Server Enterprise.You can only back up databases to snapshots in SharePoint Server by using SQL Server Enterprise tools. +## Before you begin + + +We recommend that you regularly back up the complete farm. Regularly backing up the farm reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps make sure that all the farm data and configurations are available for recovery, if that is required. For more information, see [Back up farms in SharePoint Server](html/back-up-farms-in-sharepoint-server.md). However, IT requirements might require you to backup databases to snapshots. Although you can back up any farm database to a snapshot, you typically back up content databases. +> [!IMPORTANT:] + + + + + +Before you begin this operation, review the following information: +- You must first create a folder on the database server for your backup files. If you want to store the snapshots at another location, you can move the backup files to a backup folder on the network after the operation is completed. + + +- A database snapshot provides a read-only, static view of a source database as it existed at snapshot creation, minus any uncommitted transactions. Uncommitted transactions are rolled back in a newly created database snapshot because the Database Engine runs recovery after the snapshot was created (transactions in the database are not affected). For more information about database snapshots, see [Database Snapshots (SQL Server)](http://go.microsoft.com/fwlink/p/?LinkID=715786&clcid=0x409). + + + +## Use SQL Server tools to back up a database to a snapshot in SharePoint Server + + +If you want to back up databases to snapshots, you must use SQL Server tools. The databases that are associated with the farm are determined by the service applications and features that you have installed on the farm. **To back up a database to a snapshot by using SQL Server tools** +1. Verify that the user account that is performing this procedure is a member of the SQL Server **db_owner** fixed database role. + + +2. Open SQL Server Management Studio and connect to the database server. + + +3. In Object Explorer, expand **Databases**. + + +4. Select the database that you want to back up, and then click **New Query**. + + +5. Copy the following text, and then paste it to the query pane. + + ``` + +CREATE DATABASE +ON +( +NAME=, +FILENAME = 'c:\\WSS_Backup1.ss') +AS SNAPSHOT OF ; + ``` + + +# See also + +#### + + [Database Snapshots (SQL Server)](http://go.microsoft.com/fwlink/p/?LinkID=715786&clcid=0x409) + + + + [Database Snapshots with AlwaysOn Availability Groups (SQL Server)](http://go.microsoft.com/fwlink/p/?LinkID=715787&clcid=0x409) + + + + + + + + diff --git a/SharePoint/back-up-farm-configurations-in-sharepoint-server.md b/SharePoint/back-up-farm-configurations-in-sharepoint-server.md new file mode 100644 index 0000000000..66ac617edc --- /dev/null +++ b/SharePoint/back-up-farm-configurations-in-sharepoint-server.md @@ -0,0 +1,120 @@ +--- +title: Back up farm configurations in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: a6d383c0-3817-4acd-afa9-ad7a9b7e6b5a +--- + + +# Back up farm configurations in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to back up farm configurations in SharePoint Server 2016 and SharePoint Server 2013.You can back up a farm configuration by using the SharePoint Central Administration website or Microsoft PowerShell. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have with your organization. +## Before you begin + + +We recommend that you regularly back up the complete farm by backing up both the configuration and content. However, you might want to perform configuration-only backups in test or development environments. Similarly, if you are using SQL Server tools to back up the databases for the farm, you will want to back up the configuration. Regularly backing up the farm reduces the possibility of data losses that can occur from hardware failures, power outages, or other problems. It helps make sure that all the farm data and configurations are available for recovery. For more information about what to back up, see [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md).For information about which tool to use for backups, see [Overview of backup and recovery in SharePoint Server](html/overview-of-backup-and-recovery-in-sharepoint-server.md).Before you begin this operation, review the following information: +- You must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see [Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md). + + +- Backing up the farm configuration will not back up the information that you need to restore service applications. If you want to restore a service application, you must perform a configuration and content backup of the farm. For more information about how to back up service applications, see [Back up service applications in SharePoint Server](html/back-up-service-applications-in-sharepoint-server.md). + + +- You cannot use either SQL Server tools or Data Protection Manager to back up the farm configuration. + + + +## Use PowerShell to back up a SharePoint farm configuration + + +You can use PowerShell to back up the configuration from any configuration database on the current farm, on another farm, or from a configuration database that is not associated with any farm. You can back up a farm configuration manually or as part of a script that can be run at scheduled intervals. **To back up the configuration from any configuration database by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server Products cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPConfigurationDatabase -Directory -DatabaseServer -DatabaseName -DatabaseCredentials [-Verbose] + ``` + + + + + Where: + + - ** is the path to the folder that has the correct backup files. + + + - ** is the name of the database server for the farm that you are backing up. + + + - ** is the name of the farm configuration database. + + + - If you are not logged on with an account with **db_backupoperator** fixed database role on the database server where the configuration database is stored, you must specify the value forDatabaseCredentials parameter. + + +For more information, see **Backup-SPConfigurationDatabase**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up a SharePoint farm configuration + + +You can use Central Administration to back up the configuration of the farm that Central Administration is running on. To back up the configuration of a remote farm, you must use the Central Administration Web site that is running on the remote farm. You cannot use Central Administration to back up an unattached configuration database. **To back up a farm configuration by using Central Administration** +1. Verify that the user account performing this procedure is a member of the Farm Administrators group. + + +2. On the Central Administration home page, in the **Backup and Restore** section, click **Perform a backup**. + + +3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click **Next**. + + > [!NOTE:] + +4. On the Start Backup — Step 2 of 2: Select Backup Options page, in the ** Backup Type** section, select **Full**. + + +5. In the **Backup Only Configuration Settings** section, select the **Backup only configuration settings** option. + + +6. In the **Backup File Location** section, type the Universal Naming Convention (UNC) path of the backup folder, and then click **Start Backup**. + + +7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the **Readiness** section. You can view the status for the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually refresh the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, you can review them in the **Failure Message** column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5. + + + +# See also + +#### + + [Restore farm configurations in SharePoint Server](html/restore-farm-configurations-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/back-up-farms-in-sharepoint-server.md b/SharePoint/back-up-farms-in-sharepoint-server.md new file mode 100644 index 0000000000..08fba097de --- /dev/null +++ b/SharePoint/back-up-farms-in-sharepoint-server.md @@ -0,0 +1,171 @@ +--- +title: Back up farms in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 8daa31a5-0f8c-4bd6-84c9-ee1f5074594d +--- + + +# Back up farms in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to back up a SharePoint Server 2016 and SharePoint Server 2013 farm.You can back up a SharePoint Server farm by using the SharePoint Central Administration website, Microsoft PowerShell, or SQL Server tools. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have with your organization. +## Before you begin + + +We recommend that you regularly back up the complete farm by backing up both the configuration and content. Regularly backing up the farm reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps so that all the farm data and configurations are available for recovery, if that is required.For information about which tool to use for backups, see [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md).Before you begin this operation, review the following information to help you prepare your farm backup: +- You must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see [Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md). + + +- Performing a backup does not affect the state of the farm. However, it does require resources and might slightly affect farm performance when the backup is running. You can avoid performance issues by backing up the farm during hours when farm use is lowest, such as outside office hours. + + +- The farm backup process does not back up any certificates that you used to form trust relationships. Ensure that you have copies of these certificates before you back up the farm. You must re-establish these trust relationships after restoring the farm. + + +- Backing up the farm backs up the configuration and Central Administration content databases, but these cannot be restored using SharePoint Server tools. For more information about how to back up and restore all the farm databases, see [Move all databases in SharePoint Server](html/move-all-databases-in-sharepoint-server.md). + + +- When you back up a farm that contains a Web application that is configured to use forms-based authentication, you must also use a file backup system to protect the Web.config files because the Web.config files were updated manually to register the membership and role providers, and manual changes to the Web.config files are not backed up. Similarly, Web.config files are not restored when you restore a Web application. After recovery, you must update the Web.config files and redeploy the providers. For more information, see [Plan for user authentication methods in SharePoint Server](html/plan-for-user-authentication-methods-in-sharepoint-server.md). + + +- SharePoint Server backup backs up the Business Data Connectivity service external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the Business Data Connectivity service or the farm. + + If you restore the Business Data Connectivity service or the farm and then restore the data service to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity service might be unable to locate the data source. + + +- SharePoint Server backup backs up remote Binary Large Object (BLOB) stores but only if you are using the FILESTREAM remote BLOB store provider to put data in remote BLOB stores. + + If you are using another provider, you must manually back up the remote BLOB stores. + + +- If you are using SQL Server with Transparent Data Encryption (TDE), and you are backing up your environment by using either SharePoint Server tools or SQL Server tools, the TDE encryption key in not backed up or restored. You must back up the key manually. When restoring, you must manually restore the key before you restore the data. For more information, see [Understanding Transparent Data Encryption (TDE)](http://go.microsoft.com/fwlink/p/?LinkID=715703&clcid=0x409). + + + +## Use PowerShell to back up a farm in SharePoint Server + + +You can use PowerShell to back up the farm manually or as part of a script that can be run at scheduled intervals. **To back up a farm by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPFarm -Directory -BackupMethod {Full | Differential} [-Verbose] + ``` + + + + + Where: + + - ** is the path of a folder on the local computer or the network in which you want to store the backups. + + + + > [!NOTE:] + +For more information, see **Backup-SPFarm**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up a SharePoint Server farm + + +You can use Central Administration to back up the farm. **To back up a farm by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. + + +2. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click **Next**. + + +4. On the Start Backup — Step 2 of 2: Select Backup Options page, in the **Backup Type** section, select either **Full** or **Differential**. + + > [!NOTE:] + +5. In the **Back Up Only Configuration Settings** section, click **Back up content and configuration settings**. + + +6. In the **Backup File Location** section, type the UNC path of the backup folder, and then click **Start Backup**. + + +7. You can view the general status of all backup jobs at the top of the Backup and Restore Status page in the **Readiness** section. You can view the status for the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, you can review them in the **Failure Message** column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6. + + + +## Use SQL Server tools to back up a SharePoint Server farm + + +If you want to back up the complete farm, you must use either PowerShell or Central Administration. You cannot back up the complete farm by using the SQL Server tools because you cannot use the tools to back up the farm’s configuration. However, you can back up all the databases that are associated with the farm. The databases that are associated with the farm are determined by the services and features that you have installed on the farm. **To back up the databases associated with a farm by using SQL Server tools** +1. Verify that the user account that is performing this procedure is a member of the SQL Server  **db_owner** fixed database role on all databases that are to be backed up. + + +2. Open SQL Server Management Studio and connect to the correct instance of the SQL Server Database Engine. + + +3. In Object Explorer, expand **Databases**. + + +4. Right-click the database that you want to back up, point to **Tasks**, and then click **Back Up**. + + +5. In the **Back Up Database** dialog box, confirm the database name. + + +6. Next, select the kind of backup that you want to perform from the **Backup type** list. For more information about which backup type to use, see [Recovery Models (SQL Server)]( http://go.microsoft.com/fwlink/p/?LinkID=715706&clcid=0x409). + + +7. In the **Backup component** area, click **Database**. + + +8. Either use the default name that is provided or specify a name for the backup set in the **Name** text box. + + +9. In the **Destination** area, specify where you want to store the backup. + + +10. Click **OK** to back up the database. + + +11. Repeat steps 1-10 for each farm database. + + + +# See also + +#### + + [Backup and restore in SharePoint Server](html/backup-and-restore-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/back-up-search-service-applications-in-sharepoint-server.md b/SharePoint/back-up-search-service-applications-in-sharepoint-server.md new file mode 100644 index 0000000000..3374c79878 --- /dev/null +++ b/SharePoint/back-up-search-service-applications-in-sharepoint-server.md @@ -0,0 +1,270 @@ +--- +title: Back up Search service applications in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 59c0540e-1238-4138-b98d-0d74ca59b9db +--- + + +# Back up Search service applications in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-20* **Summary:** Learn how to back up Search service applications in SharePoint Server 2016 and SharePoint Server 2013.You can back up a Search service application in a farm by using the SharePoint Central Administration website, Microsoft PowerShell, or SQL Server tools. Which backup tool you use depends on what kind of environment you have deployed, what your backup schedule requires, and what service level agreements you have made with your organization.In this article: +- [Before you begin](#begin) + + +- [Backing up a thesaurus file](#back_up_thesaurus_files) + + +- [Use Windows PowerShell to back up search in SharePoint](#proc1) + + +- [Use Central Administration to back up search in SharePoint](#proc2) + + +- [Use SQL Server tools to back up search](#proc3) + + + +## Before you begin + + +We recommend that you regularly back up at the farm level. However, business or IT requirements might require you to back up the search service and related resources. Regularly backing up the search system reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that helps make sure that data and configurations that compose the search system are available for recovery, if that is required.Before you begin this operation, review the following information: +- You must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. + + +- You cannot use SQL Server tools or Data Protection Manager to back up all of the search components. + + +- Backing up search does not affect the state of the farm. However, it does require resources. Therefore, backing up search might affect farm performance while the backup is running. You can avoid performance issues by backing up search during hours when farm use is lowest. + + + +## Back up a thesaurus file + + +Thesaurus files are used to specify synonyms for words or phrases that occur in search queries. You create and maintain the thesaurus files in systems external to SharePoint Server before you import them into SharePoint Server to make them available to the search system. The thesaurus files are therefore not included in the SharePoint Server search backup procedures outlined below.To back up your thesaurus files, you need to make sure that they are included in the backup procedures for the external system you are using to create and maintain the thesaurus files. +## Use PowerShell to back up search in SharePoint Server + + +You can use PowerShell to back up search manually or as part of a script that can be run at scheduled intervals. This procedure backs up all of the search components including the databases, the search service configuration, and all of the index files. **To back up search by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + - Farm Administrators SharePoint group. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server Products cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPFarm -Directory -BackupMethod {Full | Differential} -Item "Farm\\Shared Services\\Shared Services Applications\\" [-Verbose] + ``` + + + + + Where: + + - ** is the path of the folder that you use for storing backup files. + + + - ** is the name of the Search service application that you are backing up. + + + + > [!NOTE:] + +For more information, see **Backup-SPFarm**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up search in SharePoint Server + + +You can use Central Administration to back up search. This procedure backs up all of the search components including the databases, the search service configuration, and all of the index files. **To back up search by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. + + +2. Start **Central Administration**. + + +3. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, in the list of components, expand **Shared Services** and then expand **Shared Services Applications** to view the list of service applications in the farm. Select the search service application from the list of components, and then click **Next**. + + > [!NOTE:] + +5. On the Start Backup — Step 2 of 2: Select Backup Options page, in the ** Backup Type** section, select either **Full** or **Differential**. + + > [!NOTE:] + +6. In the **Backup File Location** section, in the **Backup location** box, type the path of the backup folder, and then click **Start Backup**. + + +7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the **Readiness** section. You can view the status for the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are timer service jobs. Therefore, it might take several seconds for the backup to start. + + If you receive any errors, you can review them in the **Failure Message** column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6. + + + +## Use SQL Server tools to back up search + + +You cannot back up the complete SharePoint Search service application by using SQL Server tools. However, you can use SQL Server tools to back up the databases that are associated with the Search service application. To back up the complete Search service application, use either PowerShell or Central Administration.To use SQL Server to back up the databases that are associated with the Search service application, you must follow these steps: +1. Pause the Search service application. + + +2. Back up all the Search service application databases with SQL Server tools. + + +3. Resume the Search service application. + + + **To pause the Search service application by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint 2016 cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +$ssa = Get-SPEnterpriseSearchServiceApplication -Identity Suspend-SPEnterpriseSearchServiceApplication -Identity $ssa + ``` + + + + + Where: + + - ** is the name of the Search service application that you are backing up. + + + **To back up all the Search service application databases by using SQL Server tools** +1. Verify that the user account that is performing this procedure is a member of the SQL Server **db_backupoperator** fixed database role on the database server where each database is stored. + + +2. Start SQL Server Management Studio and connect to the database server. + + +3. In Object Explorer, expand **Databases**. + + +4. Right-click the database that you want to back up, point to **Tasks**, and then click **Back Up**. + + +5. In the **Back Up Database** dialog box, confirm the database name. + + +6. Next, select the kind of backup that you want to perform from the **Backup type** list. For more information about which backup type to use, see [Recovery Models (SQL Server)](http://go.microsoft.com/fwlink/p/?LinkID=626889&clcid=0x409) in SQL Server Books Online. + + +7. In the **Backup component** area, click **Database**.. + + +8. Either use the default name that is provided or specify a name for the backup set in the **Name** text box. + + +9. In the Destination area, specify where you want to store the backup. + + +10. Click **OK** to back up the database. + + +11. Repeat steps 1-10 for the following databases: + + - Search Administration + + + - Analytics Reporting + + + - Crawl + + + - Link + + + **To resume the Search service application by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +$ssa = Get-SPEnterpriseSearchServiceApplication -Identity Resume-SPEnterpriseSearchServiceApplication -Identity $ssa + ``` + + + + + Where: + + - ** is the name of the Search service application. + + + +# See also + +#### + + [Restore Search service applications in SharePoint Server](html/restore-search-service-applications-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/back-up-service-applications-in-sharepoint-server.md b/SharePoint/back-up-service-applications-in-sharepoint-server.md new file mode 100644 index 0000000000..c6468b7a80 --- /dev/null +++ b/SharePoint/back-up-service-applications-in-sharepoint-server.md @@ -0,0 +1,144 @@ +--- +title: Back up service applications in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 96dc4ef1-cec8-47d0-b995-46bca3e8eda2 +--- + + +# Back up service applications in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Search Server 2013, SharePoint Foundation 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-20* **Summary:** Learn how to back up a service application in SharePoint Server 2016 and SharePoint Server 2013.You can back up a service application by using the SharePoint Central Administration website or Microsoft PowerShell. Which backup tool you use depends on what kind of environment you have deployed, what your backup schedule requires, and what service level agreements you have made with your organization.In this article: +- [Before you begin](#begin) + + +- [Use Windows PowerShell to back up a service application in SharePoint](#proc1) + + +- [Use Central Administration to back up a service application in SharePoint](#proc2) + + + +## Before you begin + + +We recommend that you regularly back up at the farm level. However, business or IT requirements might require you to back up a service application. Regularly backing up a service application reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that helps make sure that all the service application-related data and configurations are available for recovery, if that is required. You can back up one service application at a time, or you can back up all service applications at the same time. For information about what to back up and which tools to use, see [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md). For more information, see [Back up farms in SharePoint Server](html/back-up-farms-in-sharepoint-server.md).Backing up a service application does not affect the state of the farm. However, it does require resources. Therefore, backing up a service application might affect farm performance while the backup is running. You can avoid performance issues by backing up the service application during hours when farm use is lowest. +> [!NOTE:] + + + + + +Before you begin this operation, review the following information about prerequisites: +- You must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see [Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md). + + +- SharePoint Server backup backs up the SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2 external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2 or the farm. + + +- If you back up the SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2 or the farm and then restore the data source to a different location, you must change the location information in the external content type definition. If you do not, the SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2 might be unable to locate the data source. + + + +## Use PowerShell to back up a service application in SharePoint + + +You can use PowerShell to back up one or more service applications manually or as part of a script that can be run at scheduled intervals. **To back up a service application by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2016 cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPFarm -Directory -BackupMethod {Full | Differential} -Item [-Verbose] + ``` + + + + + Where: + + - ** is the path of a folder on the local computer or on the network in which you want to store the backups. + + + - ** is the name of the service application that you want to back up. To display the name of the service application, at the PowerShell command prompt, type the following command:Backup-SPFarm -ShowTree. + + + + To back up all the service applications, at the PowerShell command prompt, type the following command: + + + + ``` + Backup-SPFarm -Directory -BackupMethod {Full | Differential} -Item "Farm\\Shared Services" [-Verbose] + ``` + + + > [!NOTE:] + +For more information, see **Backup-SPFarm**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up a service application in SharePoint + + +You can use Central Administration to back up a service application. **To back up a service application by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. + + +2. Start Central Administration. + + +3. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the service application from the list of components, and then click **Next**. To back up all the service applications, select the **Shared Service Applications** node. + + > [!NOTE:] + +5. On the Start Backup — Step 2 of 2: Select Backup Options page, in the ** Backup Type** section, select either **Full** or **Differential**. + + > [!NOTE:] + +6. In the **Backup File Location** section, in the **Backup location box**, type the path of the backup folder, and then click **Start Backup**. + + +7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the **Readiness** section. You can view the status for the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, you can review them in the **Failure Message** column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5. + + + +# See also + +#### + + [Restore service applications in SharePoint Server](html/restore-service-applications-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/back-up-site-collections-in-sharepoint-server.md b/SharePoint/back-up-site-collections-in-sharepoint-server.md new file mode 100644 index 0000000000..32e72da6be --- /dev/null +++ b/SharePoint/back-up-site-collections-in-sharepoint-server.md @@ -0,0 +1,146 @@ +--- +title: Back up site collections in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 45acdd33-b322-4f36-97f1-0701159e15f0 +--- + + +# Back up site collections in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-06-27* **Summary:** Learn how to back up a single site collection in SharePoint Server 2016 and SharePoint Server 2013.You can back up a site collection in SharePoint Server by using the SharePoint Central Administration website or Microsoft PowerShell. In this article: +- [Before you begin](#begin) + + +- [Use Windows PowerShell to back up a site collection in SharePoint](#proc1) + + +- [Use Central Administration to back up a site collection in SharePoint](#proc2) + + + +## Before you begin + + +We recommend that you regularly back up the complete farm. However, IT practices might require you to also back up a site collection. For more information about what to back up, see [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md).Before you begin this operation, review the following information: +- You must first create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see [Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md). + + +- If the site collection’s **Lock status** is set to **Not locked** or **Adding content prevented**, SharePoint Server temporarily sets the site to **Read-Only** while the backup operation is occurring. SharePoint Server does this to reduce the possibilities of users changing the site collection while it is being backed up. After the backup is complete, the setting is changed back its normal status. + + +- Performing a site collection backup might require resources and might slightly affect farm performance when the backup is running. You can help avoid performance issues by backing up the farm during hours when farm use is lowest, such as outside office hours. + + + +## Use PowerShell to back up a site collection in SharePoint Server + + +You can use PowerShell to back up a site collection manually or as part of a script that can be run at scheduled intervals. **To back up a site collection by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2016 cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPSite -Identity -Path [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose] + ``` + + + + + Where: + + - ** is the ID or URL for the site collection you want to back up. + + + - ** is the path to where the backup file is located. + + + + If you want to overwrite a previously used backup file, use the Force parameter. You can use theNoSiteLock parameter to keep the read-only lock from being set on the site collection while it is being backed up. However, using this parameter can enable users to change the site collection while it is being backed up and could lead to possible data corruption during backup. To display the site collection GUID or URL at the PowerShell command prompt, type the following command: + + + + ``` + Get-SPSite | format-list -property id,url + ``` + + + If the database server is running an Enterprise Edition of SQL Server, we recommend that you also use the UseSqlSnapshot parameter for more consistent backups. You can also export sites or lists from these snapshots. + + > [!NOTE:] + + + For more information about how to use SQL snap-shots, see [Back up databases to snapshots in SharePoint Server](html/back-up-databases-to-snapshots-in-sharepoint-server.md). + + +For more information, see **Backup-SPSite**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up a site collection in SharePoint Server + + +You can use Central Administration to back up a site collection. **To back up a site collection by using Central Administration** +1. Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service has Full Control permissions on the backup folder. + + +2. Start Central Administration. + + +3. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a site collection backup**. + + +4. On the **Site collection backup** page, select the site collection from the **Site Collection** list. + + +5. Type the local path of the backup file in the **Filename** box. + + > [!NOTE:] + +6. Click **Start Backup**. + + +7. You can view the general status of all backup jobs at the top of the Granular Backup Job Status page in the **Readiness** section. You can view the status for the current backup job in the lower part of the page in the **Site Collection Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, you can review them in the **Failure Message** column of the Granular Backup Job Status page. + + + +# See also + +#### + + [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md) + + + + [Restore site collections in SharePoint Server](html/restore-site-collections-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/back-up-the-secure-store-service-in-sharepoint-server.md b/SharePoint/back-up-the-secure-store-service-in-sharepoint-server.md new file mode 100644 index 0000000000..7b595ff8a3 --- /dev/null +++ b/SharePoint/back-up-the-secure-store-service-in-sharepoint-server.md @@ -0,0 +1,130 @@ +--- +title: Back up the Secure Store Service in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: d08d6d65-23c2-48cb-a871-1e021a382e5e +--- + + +# Back up the Secure Store Service in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to back up the Secure Store Service Application in SharePoint Server 2016 and SharePoint Server 2013.You can back up the Secure Store Service by using the SharePoint Central Administration website, or Microsoft PowerShell. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have made with your organization.In this article: +- [Before you begin](#begin) + + +- [Use Windows PowerShell to back up the Secure Store Service in SharePoint](#proc1) + + +- [Use Central Administration to back up the Secure Store Service in SharePoint](#proc2) + + + +## Before you begin + + +The Secure Store Service provides the capability of securely storing credential sets and associating credentials to specific identities or a group of identities. Every time that you enter a new passphrase, Sharepoint_Server creates a new Master Key and re-encrypts the credentials sets with that key. The passphrase gives you access to the Master Key created by Sharepoint_Server that is used to encrypt the credential sets.You should back up the Secure Store Service and record the passphrase after the Secure Store Service is first configured and again every time that you make configuration changes to the Secure Store Service or re-encrypt the credential information.Before you begin this operation, review the following information: +- You must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. + + +- Record the passphrase. You will need the passphrase when you access the restored Secure Store Service. + + +- Ensure that you back up the Secure Store Service every time that you change or refresh the Master Key. When you change or refresh the Master key, the database is automatically re-encrypted with the new key. Backing up the Secure Store Service makes sure that the database and the Master key are synchronized. + + +- Keep the passphrase in a secure location. + + + +## Use PowerShell to back up the Secure Store Service in SharePoint + + +You can use PowerShell to back up the Secure Store Service manually or as part of a script that can be run at scheduled intervals. **To back up the Secure Store Service by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint 2016 Products cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPFarm -Directory -BackupMethod Full -Item [-Verbose] + ``` + + + + + Where: + + - ** is the path of a folder on the local computer or on the network in which you want to store the backups. + + + - ** is the name of the Secure Store Service application that you want to back up. + + + + > [!NOTE:] + +For more information, see **Backup-SPFarm**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up the Secure Store Service in SharePoint + + +You can use Central Administration to back up the Secure Store Service. **To back up the Secure Store Service by using Central Administration** +1. Verify that the user account that performs this procedure is a member of the Farm Administrators SharePoint group. + + +2. Start Central Administration. + + +3. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, expand the **Shared Services Applications** node, select the Secure Store Service application from the list of components, and then click **Next**. + + > [!NOTE:] + +5. On the Start Backup — Step 2 of 2: Select Backup Options page, in the ** Backup Type** section, select **Full**. + + +6. In the **Backup File Location** section, in the **Backup location box**, type the path of the backup folder, and then click **Start Backup**. + + +7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the **Readiness** section. You can view the status for the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, you can review them in the **Failure Message** column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5. + + + +# See also + +#### + + [Restore Secure Store Service applications in SharePoint Server](html/restore-secure-store-service-applications-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/back-up-user-profile-service-applications-in-sharepoint-server.md b/SharePoint/back-up-user-profile-service-applications-in-sharepoint-server.md new file mode 100644 index 0000000000..9dfc16d901 --- /dev/null +++ b/SharePoint/back-up-user-profile-service-applications-in-sharepoint-server.md @@ -0,0 +1,238 @@ +--- +title: Back up User Profile service applications in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 80f7df54-738e-49ba-9ff9-2f312d77a271 +--- + + +# Back up User Profile service applications in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Search Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-20* **Summary:** Learn how to back up the User Profile Service service application in SharePoint Server 2016 and SharePoint Server 2013.You can back up the User Profile service application by using the SharePoint Central Administration website, Microsoft PowerShell, or SQL Server tools. Which backup tool you use depends on what kind of environment you have deployed, what your backup schedule requires, and what service level agreements you have made with your organization. +> [!IMPORTANT:] + + + + + +In this article: +- [Before you begin](#begin) + + +- [Use Windows PowerShell to back up a User Profile service application](#proc1) + + +- [Use Central Administration to back up a User Profile service application](#proc2) + + +- [Use SQL Server tools to back up a User Profile service application database](#proc3) + + + +## Before you begin + + +We recommend that you regularly back up at the farm level. However, business or IT requirements might require you to back up the User Profile Service service application. Regularly backing up the User Profile service application reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that helps make sure that all service application-related data and configurations are available for recovery, if that is required.For information about what to back up and which tools to use, see [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md). You can back up all the service applications in the farm by backing up the complete farm. For more information, see [Back up farms in SharePoint Server](html/back-up-farms-in-sharepoint-server.md).Before you begin this operation, review the following information: +- Backing up the User Profile service application does not affect the state of the farm. However, it does require resources. Therefore, backing up the service application might affect farm performance while the backup is running. You can avoid performance issues by backing up the service application during hours when farm use is lowest. + + +- You must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see [Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md). + + + +## Use PowerShell to back up a User Profile service application + + +You can use PowerShell to back the User Profile service application manually or as part of a script that can be run at scheduled intervals. +> [!NOTE:] + + + + + + **To back up the User Profile service application by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint 2013 Products cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPFarm -Directory -BackupMethod Full -Item Farm\\Shared Services\\Shared Service Applications\\ [-Verbose] + ``` + + + + + Where: + + - ** is the path of a folder on the local computer or on the network in which you want to store the backups. + + + - ** is the name of the User Profile Service service application that you want to back up. + + The User Profile Service service application always requires a full backup, + + > [!NOTE:] + +4. You must also back up the service application proxy. To do this, at the PowerShell command prompt, type the following command: + + ``` + +Backup-SPFarm -Directory -BackupMethod Full -Item Farm\\Shared Services\\Shared Service Proxies\\ [-Verbose] + ``` + + + + + Where: + + - ** is the path of a folder on the local computer or on the network in which you want to store the backups. + + + - ** is the name of the User Profile Service service application proxy that you want to back up. + + +For more information, see **Backup-SPFarm**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up a User Profile Service application + + +You can use Central Administration to back up the User Profile service application. +> [!NOTE:] + + + + + + **To back up the User Profile service application by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. + + +2. Start **Central Administration**. + + +3. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the User Profile Service service application from the list of components, and then click **Next**. + + +5. On the Start Backup — Step 2 of 2: Select Backup Options page, in the ** Backup Type** section, select **Full**. + + > [!NOTE:] + +6. In the **Backup File Location** section, in the **Backup location box**, type the path of the backup folder, and then click **Start Backup**. + + +7. You must also back up the service application proxy. To do this, in Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +8. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the User Profile Service service application proxy from the list of components, and then click **Next**. + + +9. On the Start Backup — Step 2 of 2: Select Backup Options page, in the ** Backup Type** section, select **Full**. + + +10. In the **Backup File Location** section, in the **Backup location box**, type the path of the backup folder, and then click **Start Backup**. + + +11. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the **Readiness** section. You can view the status for the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, you can review them in the **Failure Message** column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5. + + + +## Use SQL Server tools to back up a User Profile service application database + + +You cannot back up the whole User Profile service application or service application proxy. You must use either PowerShell or Central Administration. However, you can back up all the databases that are associated with the User Profile Service service application. **To back up a User Profile service application database by using SQL Server** +1. Verify that the user account that is performing this procedure is a member of the SQL Server **db_backupoperator** fixed database role on the database server where each database is stored. + + +2. Before you back up the User Profile Service service application databases, you must export the Microsoft Identity Integration Server Key (MIIS) encryption key. You will import this exported key before you restore the databases. By default, the key is located on the server that runs SharePoint Server 2016 that is hosting the Microsoft Forefront Identity Manager services in the following directory: ** \\Program Files\\Microsoft Office Servers\\16.0\\Synchronization Service\\Bin or ** \\Program Files\\Microsoft Office Servers\\15.0\\Synchronization Service\\Bin. To export the key, type the following at the command prompt: + + ``` + +miiskmu.exe + ``` + + + Use the Microsoft Identity Integration Server Key Management Utility Wizard to export the key set. + + +3. Open SQL Server Management Studio and connect to the database server. + + +4. In Object Explorer, expand **Databases**. + + +5. Right-click the database that you want to back up, point to **Tasks**, and then click **Back Up**. + + +6. In the **Back Up Database** dialog box, confirm the database name. + + +7. Next, select the kind of backup that you want to perform from the **Backup type** list. For more information about which backup type to use, see [Recovery Models (SQL Server)]( http://go.microsoft.com/fwlink/p/?LinkID=715706&clcid=0x409). + + +8. In the **Backup component** area, click **Database**. + + +9. Either use the default name that is provided or specify a name for the backup set in the **Name** text box. + + +10. In the **Destination** area, specify where you want to store the backup. + + +11. Click **OK** to back up the database. + + +12. Repeat steps 1-10 for each User Profile service application database. + + + +# See also + +#### + + [Backup solutions in SharePoint Server](html/backup-solutions-in-sharepoint-server.md) + + + + [Restore service applications in SharePoint Server](html/restore-service-applications-in-sharepoint-server.md) + + + + +#### + + **Windows PowerShell for SharePoint Server 2016 reference** + + + + + + + + diff --git a/SharePoint/back-up-web-applications-in-sharepoint-server.md b/SharePoint/back-up-web-applications-in-sharepoint-server.md new file mode 100644 index 0000000000..ad1c4fbcf4 --- /dev/null +++ b/SharePoint/back-up-web-applications-in-sharepoint-server.md @@ -0,0 +1,181 @@ +--- +title: Back up web applications in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: e0ad657d-f5d1-4cae-bb0d-d2b619eed261 +--- + + +# Back up web applications in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to back up a web application in SharePoint Server 2016 and SharePoint Server 2013 by using Central Administration or Microsoft PowerShell.You can back up a web application by using the SharePoint Central Administration website, PowerShell, or SQL Server tools. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have with your organization. +## Before you begin + + +Regularly backing up a web application reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that can help make sure that all the web application-related data and configurations are available for recovery, if that is required. We recommend that web application backups be created in addition to regular backups at the farm level.Before you begin this operation, review the following information: +- Before you begin, you must create a network folder in which to store the backups. Both the SharePoint Timer Service (SPTimerV4) service account and the server farm user account must have Full Control permissions to this folder. For more information about how to create a backup folder, see [Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md). + + +- You can back up only one web application at a time by using the procedures in this article. You can back up all web applications by backing up the complete farm. + + +- Backing up a web application does not affect the state of the farm. However, it does require resources and might slightly affect farm performance when the backup is running. You can avoid performance issues by backing up the web application during hours when farm use is lowest, such as outside office hours. + + +- If the web application uses the object cache, you must manually configure two special user accounts for the web application after you restore the web application. + + +- When you back up a web application, the Internet Information Services (IIS) settings and all content databases that are associated with the web application are also backed up. + + +- When you back up a web application that is configured to use forms-based authentication, you must also use a file backup system to protect the Web.config files because the Web.config files were updated manually to register the membership and role providers, and manual changes to the Web.config files are not backed up. Similarly, Web.config files are not restored when you restore a Web application. After recovery, you must update the Web.config files and redeploy the providers. For more information, see [Plan for user authentication methods in SharePoint Server](html/plan-for-user-authentication-methods-in-sharepoint-server.md). + + + +## Use PowerShell to back up a web application + + +You can use PowerShell to back up a web application manually or as part of a script that can be run at scheduled intervals. **To back up a web application by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + > [!NOTE:] + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Backup-SPFarm -Directory -BackupMethod {Full | Differential} -Item [-Verbose] + ``` + + + + + Where: + + - ** is the path of the folder that you use for storing backup files. + + + - ** is the name of the web application. To display the name of the web application, at the PowerShell command prompt, type the following command:Backup-SPFarm -ShowTree + + + + > [!NOTE:] + +For more information, see **Backup-SPFarm**. +> [!NOTE:] + + + + + + +## Use Central Administration to back up a web application + + +You can use Central Administration to back up a web application. **To back up a web application by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. Start Central Administration. + + +3. In Central Administration, on the home page, in the **Backup and Restore** section, click **Perform a backup**. + + +4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the web application from the list of components, and then click **Next**. + + > [!NOTE:] + +5. On the Start Backup — Step 2 of 2: Select Backup Options page, in the ** Backup Type** section, select either **Full** or **Differential**. + + > [!NOTE:] + +6. In the **Back Up Only Configuration Settings** section, click **Back up content and configuration settings**. + + +7. In the **Backup File Location** section, type the Universal Naming Convention (UNC) path of the backup folder, and then click **Start Backup**. + + +8. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the **Readiness** section. You can view the status for the current backup job in the lower part of the page in the **Backup** section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking **Refresh**. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. + + If you receive any errors, you can review them in the **Failure Message** column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6. + + + +## Use SQL Server tools to back up a databases that are associated with a web application + + +You cannot back up the complete web application by using SQL Server tools. However, you can back up all the databases that are associated with the web application. To back up the complete web application, use either PowerShell or Central Administration. **To back up a database associated with a web application by using SQL Server tools** +1. Verify that the user account that is performing this procedure is a member of the SQL Server  **db_owner** fixed database role on all databases that are to be backed up. + + +2. Open SQL Server Management Studio and connect to the correct instance of the SQL Server Database Engine. + + +3. In Object Explorer, expand **Databases**. + + +4. Right-click the database that you want to back up, point to **Tasks**, and then click **Back Up**. + + +5. In the **Back Up Database** dialog box, confirm the database name. + + +6. Next, select the kind of backup that you want to perform from the **Backup type** list. For more information about which backup type to use, see [Recovery Models (SQL Server)]( http://go.microsoft.com/fwlink/p/?LinkID=715706&clcid=0x409). + + +7. In the **Backup component** area, click **Database**. + + +8. Either use the default name that is provided or specify a name for the backup set in the **Name** text box. + + +9. In the **Destination** area, specify where you want to store the backup. + + +10. Click **OK** to back up the database. + + +11. Repeat steps 1-10 for each farm database. + + + +# See also + +#### + + [Restore web applications in SharePoint Server](html/restore-web-applications-in-sharepoint-server.md) + + + + [Back up farms in SharePoint Server](html/back-up-farms-in-sharepoint-server.md) + + + + [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md) + + + + [Backup and restore in SharePoint Server](html/backup-and-restore-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/backup-and-restore-best-practices-in-sharepoint-server.md b/SharePoint/backup-and-restore-best-practices-in-sharepoint-server.md new file mode 100644 index 0000000000..a98097bf63 --- /dev/null +++ b/SharePoint/backup-and-restore-best-practices-in-sharepoint-server.md @@ -0,0 +1,162 @@ +--- +title: Backup and restore best practices in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: d7d2dff9-c7a9-402b-958a-d233cbacab8f +--- + + +# Backup and restore best practices in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-20* **Summary:** Learn how to implement best practices before you back up and restore a SharePoint Server 2016 and SharePoint Server 2013 farm.Best practices for backup and restore help make sure that backup and restore operations in SharePoint Server are successful and that the environment is protected against data loss or continuity gaps.In this article: +- [Performance best practices](#section_perf) + + +- [Quality assurance best practices](#section_QA) + + +- [Procedural best practices](#section_PROC) + + + +## Performance best practices for SharePoint backup and restore operations + + +Backup and restore operations consume server resources and limit server performance while the operations are running. Follow these recommended practices to help reduce resource usage and increase the performance of servers and the backup or restore task. +## Minimize latency between SQL Server and the backup location + +In general, it is efficient to back up to a local disk on the database server instead of a network drive. You can then copy the data later to a shared folder on the network. Network drives with 1 millisecond or less latency between them and the database server perform well. +> [!NOTE:] + + + + + +To avoid I/O bottlenecks, perform the main backup to a separate disk from the disk running SQL Server 2014, SQL Server 2008 R2 with Service Pack 1 (SP1) and SQL Server 2012UNRESOLVED_TOKEN_VAL(). For more information, see [Define a Logical Backup Device for a Disk File (SQL Server)](http://go.microsoft.com/fwlink/p/?LinkID=717191&clcid=0x409).By design, most backup jobs consume all available I/O resources to complete the job. Therefore, you might see disk queuing, which can result in greater than usual latency for I/O requests. This is typical and should not be considered a problem. For more information, see [Monitor Disk Usage](http://go.microsoft.com/fwlink/p/?LinkID=717192&clcid=0x409). +## Avoid processing conflicts + +Do not run backup jobs during times when users need access to the system. Typically, systems run 24 hours a day, seven days a week. A best practice is to always run incremental backups to safeguard against server failure. Consider staggering backups so that all databases are not backed up at the same time. +## Keep databases small for faster recovery times + +Keep databases small to speed both backup and restore. For example, use multiple content databases for a web application instead of one large content database. For more information, see [Database types and descriptions in SharePoint Server](html/database-types-and-descriptions-in-sharepoint-server.md). For a graphical overview of the databases that support SharePoint Server 2016, see [Quick reference guide: SharePoint Server 2016 databases](https://doc.co/qrafhS). You can also download this SharePoint Server 2016 database poster, as either a [PDF](https://download.microsoft.com/download/D/5/D/D5DC1121-8BC5-4953-834F-1B5BB03EB691/DBrefguideSPS2016_tabloid.pdf) or [Visio](https://download.microsoft.com/download/D/5/D/D5DC1121-8BC5-4953-834F-1B5BB03EB691/DBrefguideSPS2016_tabloid.vsdx) file. +## Use incremental backups for large databases + +Use incremental backups for large databases because you can make them quickly and maintain performance of the environment. Although you can restore full backups faster than incremental backups, continuous incremental backups minimize data loss. For more information about types of backups, see [Backup Overview (SQL Server)](http://go.microsoft.com/fwlink/p/?LinkID=717240&clcid=0x409). +## Use compression during backup + +In some circumstances, you can use compression to decrease the size of backups and the time to complete each backup. Backup compression was introduced in SQL Server 2008 Enterprise. Backup compression increases CPU usage and this can affect SQL Server concurrent operations. +> [!IMPORTANT:] + + + + + +For more information about how backup compression affects performance in SQL Server, see [Backup Compression (SQL Server)](http://go.microsoft.com/fwlink/p/?LinkID=717243&clcid=0x409). +## Follow SQL Server backup and restore optimization recommendations + +SQL Server backups use a combination of full, differential, and transaction log backups (for the full or bulk-logged recovery model) to minimize recovery time. Differential database backups are usually faster to create than full database backups and reduce the number of transaction logs required to recover the database.If you are using the full recovery model, we recommend that you periodically truncate the transaction log files to avoid maintenance issues. For detailed recommendations about how to optimize SQL Server backup and restore performance, see [Optimizing Backup and Restore Performance in SQL Server](http://go.microsoft.com/fwlink/p/?LinkId=126630). +## Use RAID 10 if you use RAID + +Carefully consider whether to use redundant array of independent disks (RAID) on the device to which you back up data. For example, RAID 5 has slow write performance, approximately the same speed as for a single disk. This is because RAID 5 has to maintain parity information. RAID 10 can provide faster backups because it doesn't need to manage parity. Therefore, it reads and writes data faster. For more information about how to use RAID with backups, see [Configure RAID for maximum SQL Server I/O throughput](http://go.microsoft.com/fwlink/p/?LinkId=126632 ) and [RAID Levels and SQL Server](http://go.microsoft.com/fwlink/p/?LinkId=282316). +## Configure SharePoint settings to improve backup or restore performance + +You can only configure file compression and log file settings in PowerShell. You can configure backup and restore threads in both the SharePoint Central Administration website and PowerShell to increase backup or restore efficiency and performance.If you use the Export-SPWeb PowerShell cmdlet, you can use the NoFileCompression parameter. By default, SharePoint Server uses file compression while exporting web applications, site collection, lists, or document libraries. You can use this parameter to suppress file compression while exporting and importing. File compression can use up to 30% more resources. However, the exported file uses approximately 25% less disk space. If you use theNoFileCompression parameter when you export, you have to also use it when you import the same content.You can also use the NoLogFile parameter. By default, SharePoint Server always creates a log file when you export content. Although you can use this parameter to suppress log file creation to save resources, we recommend that you always create logs. Logs are important for troubleshooting and log creation does not use many resources such as CPU or memory.When you use the Backup-SPFarm cmdlet, you can also use theBackupThreads parameter to specify how many threads SharePoint Server will use during the backup process. A higher number of threads will consume more resources during backup. But the overall time to make the backup is decreased. Because each thread is recorded in the log files, the number of threads does affect log file interpretation. By default, three threads are used. The maximum number of available threads is 10. +> [!NOTE:] + + + + + + +## Consider site collection size when you determine the tools to use + +If the business requires site collection backups in addition to farm-level or database-level backups, choose a backup tool that is based on the size of the site collection. +- **15-100 GB:** UsetheBackup-SPSite, a SharePoint Server tool, a SQL Server tool, or other database backup tool to protect the content database that contains the site collection. For more information, see [Back up site collections in SharePoint Server](html/back-up-site-collections-in-sharepoint-server.md). + + +- **Larger than 100 GB:** Use a differential backup solution, such as SQL Server or System Center Data Protection Manager R2, instead of the built-in backup and recovery tools. + + + +## Quality assurance best practices to back up a SharePoint farm + + +Follow these best practices to help ensure the quality of the backups of the farm environment and reduce the chances of data loss. +## Ensure you have enough storage space + +Be certain that the system has enough disk space to accommodate the backup. Configure a backup job in Central Administration to verify the required disk space. +## Routinely test backup quality + +Routinely test backups and validate their consistency. Run practice recovery operations to validate the contents of the backup and to make sure that you can restore the complete environment. To prepare for disaster recovery of geographically dispersed environments, set up a remote farm. Then you can restore the environment by using the database-attach method to upload a copy of the database to the remote farm and redirect users. Periodically perform a trial data recovery action to verify that the process correctly backs up files. A trial restoration can expose hardware problems that do not come up with software verifications and can also to make sure that the recovery time objectives (RTO) are met. +## Back up ULS trace logs + +The SharePoint Server backup process doesn't back up the Unified Logging Service (ULS) trace logs. Data in ULS trace logs can be useful for performance analysis, troubleshooting, and monitoring compliance with service level agreements. Therefore, protect this data as part of the routine maintenance.By default, SharePoint log files are at C:\\Program files\\Common Files\\Microsoft Shared\\Web Server Extensions\\16\\Logs. The files are named with the server name followed by the date and time stamp. The SharePoint trace logs are created at set intervals and when you use the IISRESET command. +## Store a copy of backup files off-site + +To safeguard against loss from a natural disaster that destroys the primary data center, maintain duplicate copies of backups in separate locations from the servers. Duplicate copies can help prevent the loss of critical data. As a best practice, keep three copies of the backup media, and keep at least one copy offsite in a controlled environment. This should include all backup and recovery materials, documents, database and transaction log backups, and usage and trace log backups. +## Procedural best practices to back up and restore SharePoint Server + + +Use the following procedural best practices to plan and perform backup and restore operations. +## Use FQDN server names + +When you refer to servers in a different domain, always use fully qualified domain names (FQDN). +## Keep accurate records + +When you deploy SharePoint Server, record the accounts that you create, the computer names, passwords, and setup options. Keep this information in a safe and secure location. Possibly, keep multiple records to make sure this information is always available. +## Have a recovery environment ready + +Use a farm in a secondary location to validate the success of restore operations as part of your disaster recovery strategy. For more information, see [Choose a disaster recovery strategy for SharePoint Server](html/choose-a-disaster-recovery-strategy-for-sharepoint-server.md). In a disaster recovery situation, you can then restore the environment by using the database-attach method to upload a copy of the database to the remote farm and redirect users. For more information, review and follow the steps in [Restore farms in SharePoint Server](html/restore-farms-in-sharepoint-server.md). Also for a high availability solution, you can set up a standby environment that runs the same version of software as the production environment so that you can restore the databases and recover documents quickly. For more information, see [Describing high availability](high-availability-and-disaster-recovery-concepts-in-sharepoint-server.md#DescHA). +## Schedule backup operations + +Use PowerShell backup and recovery cmdlets to create a script file (*.ps1) and then schedule it to run with Windows Task Scheduler. This makes sure that all backup operations are run at the best time when the system is least busy and users are not accessing it. For more information, see the following: +- [Running Scripts](https://go.microsoft.com/fwlink/p/?LinkID=178144) + + +- **Backup and recovery cmdlets in SharePoint Server 2016** + + + +## Use the SQL FILESTREAM provider with BLOB storage + +Remote BLOB Storage (RBS) is supported in a SharePoint Server farm. There are both pros and cons associated with using RBS in SharePoint Server. One related limitation of RBS with a SharePoint farm is that System Center Data Protection Manager cannot use the FILESTREAM provider to back up or restore RBS. SharePoint Server supports the FILESTREAM provider for backup and restore operations. A benefit of RBS with a SharePoint farm is that you can use either SharePoint tools or SQL Server tools to back up and restore the content database with the Remote BLOB Store (RBS) defined. This backs up and restores both the RBS and the content database. We do not recommend that you use RBS with other restore methods. For more information about the benefits and limitations of using RBS, see [Deciding to use RBS in SharePoint Server](html/deciding-to-use-rbs-in-sharepoint-server.md). Download [Microsoft SQL Server 2014 Feature Pack](http://go.microsoft.com/fwlink/p/?LinkID=733635&clcid=0x409)that includes RBS. +> [!NOTE:] + + + + + + +> [!NOTE:] + + + + + + +# See also + +#### + + [Overview of backup and recovery in SharePoint Server](html/overview-of-backup-and-recovery-in-sharepoint-server.md) + + + + [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md) + + + + [Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md) + + + + +#### + + [Database Backup Encryption](http://go.microsoft.com/fwlink/p/?LinkID=733741&clcid=0x409) + + + + + + + + diff --git a/SharePoint/backup-and-restore-in-sharepoint-server.md b/SharePoint/backup-and-restore-in-sharepoint-server.md new file mode 100644 index 0000000000..e2240251ee --- /dev/null +++ b/SharePoint/backup-and-restore-in-sharepoint-server.md @@ -0,0 +1,15 @@ +--- +title: Backup and restore in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 71abd06e-6730-442e-b2c1-e3ba9c04d497 +--- + + +# Backup and restore in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-08-04* **Summary: ** Learn about how to prepare to back up and restore and complete specific operations for SharePoint Server 2016 and SharePoint 2013.The following articles on TechNet and related resources provide information that information technology (IT) professionals must have to plan, design, and deploy backup and restore solutions for SharePoint Server. +## TechNet articles about backup and restore + +The following articles about backup and restore solutions are available to view online. The solutions that these articles describe might be in enterprise, corporate, or branch-office environments. The IT professionals who are responsible for backup and restore solutions are expected to have an understanding of the technical details that are contained in this section. However, service-level expertise is not required to understand the enterprise-level discussions and decisions.A backup is a copy of data that is used to restore and recover that data after a system failure. Backups enable you to restore data after a failure. Recovery enables you to quickly restore the farm when a problem arises. You can recover the complete farm or one or more components of the farm from a backup. +### + +ContentDescription [Overview of backup and recovery in SharePoint Server](html/overview-of-backup-and-recovery-in-sharepoint-server.md)
Understand the backup and recovery scenarios for SharePoint Server.
[Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md)
Plan backup and recovery strategies for SharePoint Server.
[Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md)
Provides information to help you understand the backup and restore process in your environment.
[Configure backup and restore permissions in SharePoint Server](html/configure-backup-and-restore-permissions-in-sharepoint-server.md)
Provides the appropriate permissions and group memberships required for backup and restore operations.
[Backup solutions in SharePoint Server](html/backup-solutions-in-sharepoint-server.md)
Provides backup solutions for your environment.
[Restore solutions in SharePoint Server](html/restore-solutions-in-sharepoint-server.md)
Provides restore solutions for your environment.
[Backup and restore best practices in SharePoint Server](html/backup-and-restore-best-practices-in-sharepoint-server.md)
Learn how to implement best practices before you back up and restore a SharePoint Server farm.
diff --git a/SharePoint/backup-solutions-in-sharepoint-server.md b/SharePoint/backup-solutions-in-sharepoint-server.md new file mode 100644 index 0000000000..778adcddb5 --- /dev/null +++ b/SharePoint/backup-solutions-in-sharepoint-server.md @@ -0,0 +1,41 @@ +--- +title: Backup solutions in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 79d47308-a90a-4c51-a1ae-93567e978236 +--- + + +# Backup solutions in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-08-07* **Summary: ** Learn how to back up solutions for a SharePoint Server 2016 or a SharePoint 2013 environment.The following articles provide information about backup solutions for SharePoint Server. These articles are written to meet the requirements of information technology (IT) professionals who are responsible for the planning, design, deployment, and operations of backup and recovery solutions. These solutions might be in enterprise, corporate, or branch office environments. The IT professionals who are responsible for backup and recovery solutions are expected to have an understanding of the technical details that are contained in this section.A backup is a copy of data that is used to restore and recover that data after a system failure. While backups allow you to restore data after a failure they are also useful to keep for routine purposes. These purposes include copying a database from one server to another, setting up database mirroring, and archiving to comply with regulatory requirements.If you make appropriate backups, you can recover from many system failures, such as the following: +- Media failure + + +- User errors (such as deleting a file by mistake) + + +- Hardware failures (such as a damaged hard disk or permanent loss of a server) + + +- Natural disasters + + + +## Articles about backup for SharePoint Server + +The following articles about backup are available to view online. Writers update articles on a continuing basis as new information becomes available and as users provide feedback. +### + +ContentDescription [Back up farms in SharePoint Server](html/back-up-farms-in-sharepoint-server.md)
Back up complete farms.
[Back up farm configurations in SharePoint Server](html/back-up-farm-configurations-in-sharepoint-server.md)
Back up farm configuration settings.
[Back up web applications in SharePoint Server](html/back-up-web-applications-in-sharepoint-server.md)
Back up web application that are associated with the farm and include configuration and content databases.
[Back up service applications in SharePoint Server](html/back-up-service-applications-in-sharepoint-server.md)
Back up service applications that are associated with the farm and include configuration and content databases.
[Back up User Profile service applications in SharePoint Server](html/back-up-user-profile-service-applications-in-sharepoint-server.md)
Back up User Profile Service applications that are associated with the farm and include configuration and content databases.
[Back up Search service applications in SharePoint Server](html/back-up-search-service-applications-in-sharepoint-server.md)
Back up Search service applications that are associated with the farm and include configuration and indexes.
[Back up the Secure Store Service in SharePoint Server](html/back-up-the-secure-store-service-in-sharepoint-server.md)
Back up the Secure Store service application that is associated with the farm and includes configuration and content databases.
[Back up content databases in SharePoint Server](html/back-up-content-databases-in-sharepoint-server.md)
Back up content databases that are associated with the farm.
[Back up databases to snapshots in SharePoint Server](html/back-up-databases-to-snapshots-in-sharepoint-server.md)
Back up databases to snapshots in the farm.
[Back up customizations in SharePoint Server](html/back-up-customizations-in-sharepoint-server.md)
Back up customizations that are associated with the farm. This article includes how to back up workflows in SharePoint Server.
[Back up site collections in SharePoint Server](html/back-up-site-collections-in-sharepoint-server.md)
Back up site collections that are associated with the farm.
[Back up apps for SharePoint in SharePoint Server](html/back-up-apps-for-sharepoint-in-sharepoint-server.md)
Back up apps for SharePoint in SharePoint Server.
[Export sites, lists, or document libraries in SharePoint Server](html/export-sites-lists-or-document-libraries-in-sharepoint-server.md)
Export a list, site, or document library that is associated with the farm. Then import the items into another farm or move them to another place in the existing farm.
+# See also + +#### + + [Restore solutions in SharePoint Server](html/restore-solutions-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/best-practices-for-crawling-in-sharepoint-server.md b/SharePoint/best-practices-for-crawling-in-sharepoint-server.md new file mode 100644 index 0000000000..94630649c7 --- /dev/null +++ b/SharePoint/best-practices-for-crawling-in-sharepoint-server.md @@ -0,0 +1,317 @@ +--- +title: Best practices for crawling in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 73f19541-9321-4abd-b014-98df79f84d2a +--- + + +# Best practices for crawling in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* Learn about best practices for crawling in SharePoint Server 2016 and SharePoint Server 2013.The Search system crawls content to build a search index that users can run search queries against. This article contains suggestions as to how to manage crawls most effectively.In this article: +- [Use the default content access account to crawl most content](#BKMK_UseDefault) + + +- [Use content sources effectively](#BKMK_UseContentSources) + + +- [Crawl user profiles before you crawl SharePoint sites](#BKMK_CrawlUserProfiles) + + +- [Use continuous crawls to help ensure that search results are fresh](#BKMK_UseContinuousCrawls) + + +- [Use crawl rules to exclude irrelevant content from being crawled](#BKMK_UseCrawlRules) + + +- [Crawl the default zone of SharePoint web applications](#BKMK_CrawlDefaultZone) + + +- [Reduce the effect of crawling on SharePoint crawl targets](#BKMK_ReduceEffect) + + +- [Use Active Directory groups instead of individual users for permissions](#BKMK_UseADGroups) + + +- [Add a second crawl component to provide fault tolerance](#BKMK_AddSecond) + + +- [Manage environment resources to improve crawl performance](#BKMK_ManageEnvironment) + + +- [Make sure no crawls are active before you change the search topology](#BKMK_MakeSureNoCrawls) + + +- [Remove crawl components from a crawl host before you remove the host from a farm](#BKMK_RemoveCrawlComponents) + + +- [Test crawl and query functionality after you change the crawl configuration or apply updates](#BKMK_TestCrawl) + + +- [Use the crawl log and crawl-health reports to diagnose problems](#BKMK_UseCrawlLog) + + + +## Use the default content access account to crawl most content + + +The default content access account is a domain account that you specify for the SharePoint Server Search service to use by default for crawling. For simplicity, it is best to use this account to crawl as much as possible of the content that is specified by your content sources. To change the default content access account, see [Change the default account for crawling in SharePoint Server](html/change-the-default-account-for-crawling-in-sharepoint-server.md).When you cannot use the default content access account for crawling a particular URL (for example, for security reasons), you can create a crawl rule to specify one of the following alternatives for authenticating the crawler: +- A different content access account + + +- A client certificate + + +- Form credentials + + +- A cookie for crawling + + +- Anonymous access + + +For more information, see [Manage crawl rules in SharePoint Server](html/manage-crawl-rules-in-sharepoint-server.md). +## Use content sources effectively + + +A content source is a set of options in a Search service application that you use to specify each of the following: +- One or more start addresses to crawl. + + +- The type of content in the start addresses (such as SharePoint Server sites, file shares, or line-of-business data). You can specify only one type of content to crawl in a content source. For example, you would use one content source to crawl SharePoint Server sites, and a different content source to crawl file shares. + + +- A crawl schedule and a crawl priority for full or incremental crawls that will apply to all of the content repositories that the content source specifies. + + +When you create a Search service application, the search system automatically creates and configures one content source, which is named **Local SharePoint sites**. This preconfigured content source is for crawling user profiles, and for crawling all SharePoint Server sites in the web applications with which the Search service application is associated. You can also use this content source for crawling content in other SharePoint Server farms, including SharePoint Server 2007 farms, SharePoint Server 2010 farms, SharePoint Server 2013 farms, or other SharePoint Server farms.Create additional content sources when you want to do any of the following: +- Crawl other types of content + + +- Limit or increase how much content to crawl + + +- Crawl certain content more or less frequently + + +- Set different priorities for crawling certain content (this applies to full and incremental crawls, but not to continuous crawls) + + +- Crawl certain content on different schedules (this applies to full and incremental crawls, but not to continuous crawls) + + +However, to keep administration as easy as possible, we recommend that you limit the number of content sources that you create and use. +## Using content sources to schedule crawls + +You can edit the preconfigured content source **Local SharePoint sites** to specify a crawl schedule; it does not specify a crawl schedule by default. For any content source, you can start crawls manually, but we recommend that you schedule incremental crawls or enable continuous crawls to make sure that content is crawled regularly.Consider using different content sources to crawl content on different schedules for the following reasons. +- To accommodate server down times and periods of peak server usage. + + +- To crawl content that is hosted on slower servers separately from content that is hosted on faster servers. + + +- To frequently crawl content that is updated more often. + + +Crawling content can significantly decrease the performance of the servers that host the content. The effect depends on whether the host servers have sufficient resources (especially CPU and RAM) to handle the load. Therefore, when you plan crawl schedules, consider the following best practices: +- Schedule crawls for each content source during times when the servers that host the content are available and when there is low demand on the server resources. + + +- Stagger crawl schedules so that the load on crawl servers and host servers is distributed over time. You can optimize crawl schedules in this manner as you become familiar with the typical crawl durations for each content source by checking the crawl log. For more information, see [Crawl log](view-search-diagnostics-in-sharepoint-server.md#proc3) in [View search diagnostics in SharePoint Server](html/view-search-diagnostics-in-sharepoint-server.md). + + +- Run full crawls only when it is necessary. For more information, see [Reasons to do a full crawl](plan-crawling-and-federation-in-sharepoint-server.md#Plan_full_crawl) in [Plan crawling and federation in SharePoint Server](html/plan-crawling-and-federation-in-sharepoint-server.md). For any administrative change that requires a full crawl to take effect, such as creation of a crawl rule, perform the change shortly before the next full crawl so that an additional full crawl is not necessary. For more information, see [Manage crawl rules in SharePoint Server](html/manage-crawl-rules-in-sharepoint-server.md). + + + +## Crawl user profiles before you crawl SharePoint Server sites + + +By default, in the first Search service application in a farm, the preconfigured content source **Local SharePoint sites** contains at least the following two start addresses: +- http://Web_application_public_URL, which is for crawling all SharePoint Server sites in a web application + + +- sps3:// *My_Site_host_URL* , which is for crawling user profiles + + +However, if you are deploying "people search", we recommend that you create a separate content source for the start address sps3:// *My_Site_host_URL* and run a crawl for that content source first. The reason for doing this is that after the crawl finishes, the search system generates a list to standardize people's names. This is so that when a person's name has different forms in one set of search results, all results for that person are displayed in a single group (known as a **result block** ). For example, for the search query "Anne Weiler", all documents authored by Anne Weiler or A. Weiler or alias AnneW can be displayed in a result block that is labeled "Documents by Anne Weiler". Similarly, all documents authored by any of those identities can be displayed under the heading "Anne Weiler" in the refinement panel if "Author" is one of the categories there. **To crawl user profiles and then crawl SharePoint Server sites** +1. Verify that the user account that performs this procedure is an administrator for the Search service application that you want to configure. + + +2. Follow the instructions in [Deploy people search in SharePoint Server](html/deploy-people-search-in-sharepoint-server.md). As part of those instructions, you do the following: + +1. Create a content source that is only for crawling user profiles (the profile store). You might give that content source a name such as **People**. In the new content source, in the **Start Addresses** section, type sps3:// *My_Site_Host_URL* , where *My_Site_host_URL* is the URL of the My Site host. + + +2. Start a crawl for the **People** content source that you just created. + + +3. Delete the start address sps3:// *My_Site_Host_URL* from the preconfigured content source **Local SharePoint sites**. + + +3. Wait about two hours after the crawl for the **People** content source finishes. + + +4. Start the first full crawl for the content source **Local SharePoint sites**. + + + +## Use continuous crawls to help ensure that search results are fresh + + + **Enable continuous crawls** is a crawl schedule option that you can select when you add or edit a content source of type **SharePoint Sites**. A continuous crawl crawls content that was added, changed, or deleted since the last crawl. A continuous crawl starts at predefined time intervals. The default interval is every 15 minutes, but you can set continuous crawls to occur at shorter intervals by using Microsoft PowerShell. Because continuous crawls occur so often, they help ensure search-index freshness, even for SharePoint Server content that is frequently updated. Also, while an incremental or full crawl is delayed by multiple crawl attempts that are returning an error for a particular item, a continuous crawl can be crawling other content and contributing to index freshness, because a continuous crawl does not process or retry items that return errors more than three times. (For content sources that have continuous crawls enabled, a "clean-up" incremental crawl automatically runs every four hours to re-crawl any items that repeatedly return errors.)A single continuous crawl includes all content sources in a Search service application for which continuous crawls are enabled. Similarly, the continuous crawl interval applies to all content sources in the Search service application for which continuous crawls are enabled. For more information, see [Manage continuous crawls in SharePoint Server](html/manage-continuous-crawls-in-sharepoint-server.md).Continuous crawls increase the load on the crawler and on crawl targets. Make sure that you plan and scale out accordingly for this increased consumption of resources. For each large content source for which you enable continuous crawls, we recommend that you configure one or more front-end web servers as dedicated targets for crawling. For more information, see [Manage crawl load (SharePoint Server 2010)](https://technet.microsoft.com/en-us/library/dd335962%28v=office.14%29.aspx). +## Use crawl rules to exclude irrelevant content from being crawled + + +Because crawling consumes resources and bandwidth, during initial deployment it might be better to crawl a small amount of content that you know is relevant, instead of crawling a larger amount of content, some of which might not be relevant. To limit how much content that you crawl, you can create crawl rules for the following reasons: +- To avoid crawling irrelevant content by excluding one or more URLs. + + +- To crawl links on a URL without crawling the URL itself. This is useful for sites that do not contain relevant content but have links to relevant content. + + +By default, the crawler will not follow complex URLs, which are URLs that contain a question mark followed by additional parameters — for example, http://contoso/page.aspx?x=y. If you enable the crawler to follow complex URLs, this can cause the crawler to gather many more URLs than is expected or appropriate. This can cause the crawler to gather unnecessary links, fill the crawl database with redundant links, and result in an index that is unnecessarily large.These measures can help reduce the use of server resources and network traffic, and can increase the relevance of search results. After the initial deployment, you can review the query and crawl logs and adjust content sources and crawl rules to include more content if it is necessary. For more information, see [Manage crawl rules in SharePoint Server](html/manage-crawl-rules-in-sharepoint-server.md). +## Crawl the default zone of SharePoint Server web applications + + +When you crawl the default zone of a SharePoint Server web application, the query processor automatically maps and returns search-result URLs so that they are relative to the alternate access mapping (AAM) zone from which queries are performed. This makes it possible for users to readily view and open search results.However, if you crawl a zone of a web application other than the default zone, the query processor does not map search-result URLs so that they are relative to the AAM zone from which queries are performed. Instead, search-result URLS will be relative to the non-default zone that was crawled. Because of this, users might not readily be able to view or open search results.For example, assume that you have the following AAMs for a web application named WebApp1: +### + +Default Public URL Authentication provider Default
https://contoso
Windows authentication: NTLM
Extranet
https://fabrikam
Forms-based authentication
Intranet
http://fabrikam
Windows authentication: NTLM
Now, say that you crawl the default zone, https://contoso. When users perform queries from https://contoso/searchresults.aspx, URLs of results from WebApp1 will all be relative to https://contoso, and therefore will be of the form https://contoso/ *path* / *result* .aspx.Similarly, when queries originate from the Extranet zone—in this case, https://fabrikam/searchresults.aspx—results from WebApp1 will all be relative to https://fabrikam, and therefore will be of the form https://fabrikam/ *path* / *result* .aspx.In both of the previous cases, because of the zone consistency between the query location and the search-result URLs, users will readily be able to view and open search results, without having to change to the different security context of a different zone.However, now instead say that you crawl a non-default zone such as the Intranet zone, http://fabrikam. In this case, for queries from any zone, URLs of results from WebApp1 will always be relative to the non-default zone that was crawled. That is, a query from https://contoso/searchresults.aspx, https://fabrikam/searchresults.aspx, or http://fabrikam/searchresults.aspx will yield search-result URLs that begin with the non-default zone that was crawled, and therefore will be of the form http://fabrikam/ *path* / *result* .aspx. This can cause unexpected or problematic behavior such as the following: +- When users try to open search results, they might be prompted for credentials that they don't have. For example, forms-based authenticated users in the Extranet zone might not have Windows authentication credentials. + + +- The results from WebApp1 will use HTTP, but users might be searching from the Extranet zone at https://fabrikam/searchresults.aspx. This might have security implications because the results will not use secure sockets layer (SSL) encryption. + + +- Refinements might not filter correctly, because they filter on the public URL for the default zone instead of the URL that was crawled. This is because URL-based properties in the index will be relative to the non-default URL that was crawled. + + + +## Reduce the effect of crawling on SharePoint Server crawl targets + + +You can reduce the effect of crawling on SharePoint Server crawl targets (that is, SharePoint Server front-end web servers) by doing the following: +- For a small SharePoint Server environment, redirect all crawl traffic to a single SharePoint Server front-end web server. For a large environment, redirect all crawl traffic to a specific group of front-end web servers. This prevents the crawler from using the same resources that are being used to render and serve web pages and content to active users. + + +- Limit search database usage in Microsoft SQL Server to prevent the crawler from using shared SQL Server disk and processor resources during a crawl. + + +For more information, see [Manage crawl load (SharePoint Server 2010)](https://technet.microsoft.com/en-us/library/dd335962%28v=office.14%29.aspx). +## Using crawler impact rules to limit the effect of crawling + +To limit crawler impact, you can also create crawler impact rules, which are available from the Search_service_application_name: Search Administration page. A crawler impact rule specifies the rate at which the crawler requests content from a start address or range of start addresses. Specifically, a crawler impact rule either requests a specified number of documents at a time from a URL without waiting between requests, or it requests one document at a time from the URL and waits a specified time between requests. Each crawler impact rule applies to all crawl components.For servers in your organization, you can set crawler impact rules based on known server performance and capacity. However, this might not be possible for external sites. Therefore, you might unintentionally use too many resources on external servers by requesting too much content or requesting content too frequently. This could cause administrators of those external servers to limit server access so that it becomes difficult or impossible for you to crawl those repositories. Therefore, set crawler impact rules to have as little effect on external servers as possible while you still crawl enough content frequently enough to make sure that that the freshness of the index meets your requirements. +## Use Active Directory groups instead of individual users for permissions + + +The ability of a user or group to perform various activities on a site is determined by the permission level that you assign.  If you add or remove users individually for site permissions, or if you use a SharePoint Server group to specify site permissions and you change the membership of the group, the crawler must perform a "security-only crawl", which updates all affected items in the search index to reflect the change. Similarly, adding or updating web application policy with different users or SharePoint Server groups will trigger a crawl of all content covered by that policy. This increases crawl load and can reduce search-results freshness. Therefore, to specify site permissions, it is best to use Active Directory Domain Services (AD DS) groups, because this does not require the crawler to update the affected items in the search index. +## Add a second crawl component to provide fault tolerance + + +When you create a Search service application, the default search topology includes one crawl component. A crawl component retrieves items from content repositories, downloads the items to the server that hosts the crawl component, passes the items and associated metadata to a content processing component, and adds crawl-related information to associated crawl databases. You can add a second crawl component to provide fault tolerance. If one crawl component becomes unavailable, the remaining crawl component will take over all of the crawling. For most SharePoint Server farms, a total of two crawl components is sufficient.For more information, see the following TechNet articles: +- [Overview of search architecture in SharePoint Server](html/overview-of-search-architecture-in-sharepoint-server.md) + + +- [Change the default search topology in SharePoint Server](html/change-the-default-search-topology-in-sharepoint-server.md) + + +- [Manage search components in SharePoint Server](html/manage-search-components-in-sharepoint-server.md) + + +- **New-SPEnterpriseSearchCrawlComponent** + + + +## Manage environment resources to improve crawl performance + + +As the crawler crawls content, downloads the content to the crawl server (the server that hosts the crawl component), and feeds the content to content processing components, several factors can adversely affect performance. To improve crawl performance, you can do the following: +### + +To address this potential performance bottleneck Implement this solution Slow response time from crawled servers
Provide more CPU and RAM and faster disk I/O
Low network bandwidth
Install one or two one-gigabit-per-second network adapters on each crawl server
Content processing
Provide more content processing components, and more CPU resources for each content processing component
Slow processing by the index components
Add I/O resources for servers that host index components
For more information, see the following resources: +- [Scale search for Internet sites in SharePoint Server](html/scale-search-for-internet-sites-in-sharepoint-server.md) + + +- [SharePoint 2013: Crawl scaling recommendations](https://social.technet.microsoft.com/wiki/contents/articles/16490.sharepoint-2013-crawl-scaling-recommendations.aspx) + + + +## Make sure no crawls are active before you change the search topology + + +We recommend that you confirm that no crawls are in progress before you initiate a change to the search topology. Otherwise, it is possible that the topology change will not occur smoothly.If necessary, you can manually pause or stop full or incremental crawls, and you can disable continuous crawls. For more information, see the following articles: +- [Start, pause, resume, or stop a crawl in SharePoint Server](html/start-pause-resume-or-stop-a-crawl-in-sharepoint-server.md) + + +- [Manage continuous crawls in SharePoint Server](html/manage-continuous-crawls-in-sharepoint-server.md) + + + +> [!NOTE:] + + + + + +To confirm that no crawls are in progress, on the *Search_service_application_name* : Manage Content Sources page, make sure that the value in the **Status** field for each content source is either **Idle** or **Paused**. (When a crawl is completed, or when you stop a crawl, the value in the **Status** field for the content source will change to **Idle**.) +## Remove crawl components from a crawl host before you remove the host from a farm + + +When a server hosts a crawl component, removing the server from the farm can make it impossible for the Search system to crawl content. Therefore, before you remove a crawl host from a farm, we strongly recommend that you do the following: +1. Make sure that no crawls are active. + + For more information, see the previous section, [Make sure no crawls are active before you change the search topology](#BKMK_MakeSureNoCrawls). + + +2. Remove or relocate crawl components that are on that host. + + +For more information, see the following resources: +- [Manage the search topology in SharePoint Server](html/manage-the-search-topology-in-sharepoint-server.md) + + +- [Change the default search topology in SharePoint Server](html/change-the-default-search-topology-in-sharepoint-server.md) + + +- [Remove a search component](manage-search-components-in-sharepoint-server.md#Search_Comp_Remove) or [Move a search component](manage-search-components-in-sharepoint-server.md#Search_Comp_Move) in [Manage search components in SharePoint Server](html/manage-search-components-in-sharepoint-server.md) + + +- [Remove a server from a farm in SharePoint Server 2016](html/remove-a-server-from-a-farm-in-sharepoint-server-2016.md) + + +- [SP2010: Removing/Re-joining Server to a Farm Can Break Search](https://blogs.msdn.com/b/sharepoint_strategery/archive/2013/07/08/sp2010-broken-topology-and-hung-crawls-can-be-caused-by-serverid-mismatch.aspx) + + + +## Test crawl and query functionality after you change the crawl configuration or apply updates + + +We recommend that you test the crawl and query functionality in the server farm after you make configuration changes or apply updates. The following procedure is an example of an easy way to perform such a test. **To test the crawl and query functionality** +1. Verify that the user account that performs this procedure is an administrator for the Search service application that you want to configure. + + +2. Create a content source that you will use temporarily just for this test. + + In the new content source, in the **Start Addresses** section, in the **Type start addresses below (one per line)** box, specify a start address that contains several items that are not already in the index — for example, several TXT files that are on a file share. For more information, see [Add, edit, or delete a content source in SharePoint Server](html/add-edit-or-delete-a-content-source-in-sharepoint-server.md). + + +3. Start a full crawl for that content source. + + For more information, see [Start, pause, resume, or stop a crawl in SharePoint Server](html/start-pause-resume-or-stop-a-crawl-in-sharepoint-server.md). When the crawl is complete, on the *Search_service_application_name* : Manage Content Sources page, the value in the **Status** column for the content source will be **Idle**. (To update the **Status** column, refresh the Manage Content Sources page by clicking **Refresh**.) + + +4. When the crawl is complete, go to the Search Center and perform search queries to find those files. + + If your deployment does not already have a Search Center, see [Create a Search Center site in SharePoint Server](html/create-a-search-center-site-in-sharepoint-server.md). + + +5. After you finish testing, delete the temporary content source. + + This removes the items specified by that content source from the search index so that they do not appear in search results after you finish testing. + + + +## Use the crawl log and crawl-health reports to diagnose problems + + +The crawl log tracks information about the status of crawled content. The log includes views for content sources, hosts, errors, databases, URLs, and history. For example, you can use this log to determine the time of the last successful crawl for a content source, whether crawled content was successfully added to the index, whether it was excluded because of a crawl rule, or whether crawling failed because of an error. Crawl-health reports provide detailed information about crawl rate, crawl latency, crawl freshness, content processing, CPU and memory load, continuous crawls, and the crawl queue.You can use the crawl log and crawl-health reports to diagnose problems with the search experience. The diagnostic information can help you determine whether it would be helpful to adjust elements such as content sources, crawl rules, crawler impact rules, crawl components, and crawl databases.For more information, see [View search diagnostics in SharePoint Server](html/view-search-diagnostics-in-sharepoint-server.md). diff --git a/SharePoint/best-practices-for-organizing-content-for-search-in-sharepoint-server.md b/SharePoint/best-practices-for-organizing-content-for-search-in-sharepoint-server.md new file mode 100644 index 0000000000..d0afd7291a --- /dev/null +++ b/SharePoint/best-practices-for-organizing-content-for-search-in-sharepoint-server.md @@ -0,0 +1,71 @@ +--- +title: Best practices for organizing content for search in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: e913bd67-b50b-47d7-9784-2d312b97de0b +--- + + +# Best practices for organizing content for search in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Learn how to organize SharePoint Server 2016 and SharePoint Server 2013 content and metadata to make the content easier to find.These best practices for organizing SharePoint Server content and applying useful metadata will help make sure that the right content is included in the search index and that the right content is returned in search results. In this article: +- [Keep your most important content in SharePoint](#Keep_content_in_SP) + + +- [Organize content in hierarchies and use natural language](#Organize_hierarchies) + + +- [Encourage users to enter rich and consistent metadata for their sites and content](#Encourage_metadata) + + +- [Managing multilingual content](#Multillingual_content) + + +- [Specify authoritative pages](#Rel_Auth) + + + +## Keep your most important content in SharePoint Server + + +If possible, keep your most important content in SharePoint Server, and crawl and index as much premium content as possible. If you cannot crawl and index the content, consider federating results from other sources into your local search results. Try to organize content with similar value and importance into nearby site structures. The search system will automatically infer the relative importance, but you can also influence the importance of sites directly by defining authoritative pages. For more information, see the section [Specify authoritative pages](#Rel_Auth).It is important to know what content to crawl and include in the search index, but it is also important to know what content **not** to crawl. For example, you do not want to crawl and index backup file shares. You should also establish routines for archiving obsolete content, deleting low-quality content and encourage users to add expiration dates to announcements. +## Organize content in hierarchies and use natural language + + +By organizing SharePoint Server content in **natural hierarchies**, you not only make it is easier for users to understand where they can find and file their content, but you also make it easier for the search system to rank the content and return search results that better match the user’s intent. +### + +Flat structureStructure with hierarchyhttp://Europe
http://Asia
http://sales
http://sales/Europe
http://sales/Asia
URLs and other metadata of files, such as file names, are analyzed linguistically by the search system. If you use natural language for URLs and for metadata, the search system can more easily understand what information is in the site or file and give it an appropriate ranking in the results. It is much easier for the search system (and users) to understand a URL and file name like http://sales/Europe/presentations/phones.ppt than it is to make sense ofhttp://slseur/p_phones.ppt. +## Encourage users to enter rich and consistent metadata for their sites and content + + +Metadata is data that provides additional information about one or more aspects of sites and content, such as who created the content or site, when was it created, and what the purpose of the content or the site is. Consistent and rich metadata increases the quality of the content itself, and it also enables the search system to more easily discover relationships between content, and to provide more targeted and relevant search results.These are some examples of important metadata that you should encourage users to provide: +- Title of a document + + +- Description of a site + + +- The author(s) of a document + + +- The date the content was created + + +For some document types, such as PowerPoint and Word, the search system extracts additional metadata such as headings and subheadings from inside the content, and uses this information to return the right search results and to provide rich document summaries and previews. To provide the right search results for people, it is also important that My Sites and user profile data is entered so that this information can be used as metadata by the search system. +## Managing multilingual content + + +The search system detects the language of most content automatically. These recommendations help prevent that the search system detects the wrong language: +- If possible, keep content in different languages on different sites. If the search system cannot detect the language of a particular content item, it assumes that it is in the language of the site where it is stored. + + +- Avoid mixing languages in content and that content's metadata. Use the same language in the metadata as the language that is used in the content itself. + + +- Avoid mixing languages in a single piece of metadata. This is mostly applicable to URLs. + + + +## Specify authoritative pages + + +You can use the **Authoritative Pages** feature in the Search service application to specify SharePoint Server sites that contain the most relevant information. Search results from authoritative pages are ranked higher in the search results.You can specify three degrees of authority, and you can also specify non-authoritative sites. When you identify a site as an authority, sites that are connected to the authoritative page via hyperlinks are also boosted in the results, based on their proximity to the authoritative page. A most-authoritative page contains or links to the most relevant information. URLs designated as non-authoritative are ranked lower than other sites.We recommend that you only specify a small number (four-five) of authoritative pages. If you specify lots of authoritative pages, it is difficult to predict the effects on the ranking of search results.For more information, see [Configure authoritative pages in SharePoint Server](html/configure-authoritative-pages-in-sharepoint-server.md). diff --git a/SharePoint/best-practices-for-sql-server-in-a-sharepoint-server-farm.md b/SharePoint/best-practices-for-sql-server-in-a-sharepoint-server-farm.md new file mode 100644 index 0000000000..d7e581e431 --- /dev/null +++ b/SharePoint/best-practices-for-sql-server-in-a-sharepoint-server-farm.md @@ -0,0 +1,234 @@ +--- +title: Best practices for SQL Server in a SharePoint Server farm +ms.prod: SHAREPOINT +ms.assetid: d1c43543-2363-4762-882f-13f06295d0d5 +--- + + +# Best practices for SQL Server in a SharePoint Server farm + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-08-07* **Summary:** Learn how to implement best practices for SQL Server in a SharePoint Server 2016 and SharePoint Server 2013 farm.When you configure and maintain SharePoint Server 2016 relational databases on SQL Server 2014 with Service Pack 1 (SP1) or SQL Server 2016, you have to choose options that promote performance and security. Likewise, you have to choose options that promote performance and security when you configure and maintain SharePoint Server 2013 relational databases on SQL Server 2008 R2 with Service Pack 1 (SP1), SQL Server 2012, and SQL Server 2014.The best practices in this article are ordered based on the sequence in which they would apply, from installing and configuring SQL Server, to deploying SharePoint Server, and then maintaining the farm. Most of the practices apply to all versions of SQL Server. Practices that are unique to SQL Server versions are shown in separate sections. +> [!NOTE:] + + + + + + +> [!NOTE:] + + + + + + +> [!IMPORTANT:] + + + + + + +## Use a dedicated server for SQL Server + +To ensure optimal performance for farm operations, we recommend that you install SQL Server on a dedicated server that does not run other farm roles and does not host databases for other applications. The only exception is deployment of SharePoint Server 2016 in a Single-Server farm role or SharePoint 2013 on a stand-alone server, which is meant for development or testing, and is not recommended for production use. For more information, see [Description of MinRole and associated services in SharePoint Server 2016](html/description-of-minrole-and-associated-services-in-sharepoint-server-2016.md) and [Install SharePoint Server 2016 on a single server with SQL Server](html/install-sharepoint-server-2016-on-a-single-server-with-sql-server.md). +> [!NOTE:] + + + + + + +## Configure specific SQL Server settings before you deploy SharePoint Server + +To ensure consistent behavior and performance, configure the following options and settings before you deploy SharePoint Server. +- Do not enable auto-create statistics on SharePoint content databases. Enabling auto-create statistics is not supported for SharePoint Server. SharePoint Server configures the required settings during provisioning and upgrade. Manually enabling auto-create statistics on a SharePoint database can significantly change the execution plan of a query. The SharePoint databases either use a stored procedure that maintains the statistics (proc_UpdateStatistics) or rely on SQL Server to do this. + + +- Set max degree of parallelism (MAXDOP) to 1 for instances of SQL Server that host SharePoint databases to make sure that a single SQL Server process serves each request. + + > [!IMPORTANT:] + +- To help simplify maintenance, such as to make it easier to move databases to another server, create DNS aliases that point to the IP address for all instances of SQL Server. For more information about DNS or Hostname aliases, see [How to Add a Hostname Alias for a SQL Server Instance](https://go.microsoft.com/fwlink/p/?LinkID=279159). + + +For more information about these SQL Server settings and options, see [Set SQL Server options](storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md#Section6_3). +## Harden the database server before you deploy SharePoint Server + +We recommend that you plan for, and harden the database server before you deploy SharePoint Server. For more information, see: +- [Securing SQL Server](http://go.microsoft.com/fwlink/?LinkID=809089&clcid=0x409) + + +- [Configure SQL Server security for SharePoint Server 2016](html/configure-sql-server-security-for-sharepoint-server-2016.md) + + +- [Securing SharePoint: Harden SQL Server in SharePoint Environments](https://blogs.technet.com/b/rycampbe/archive/2013/10/14/securing-sharepoint-harden-sql-server-in-sharepoint-environments.aspx) + + +- [Security Center for SQL Server Database Engine and Azure SQL Database](http://go.microsoft.com/fwlink/?LinkID=800298&clcid=0x409) + + + +## Configure database servers for performance and availability + +As is the case with front-end servers and application servers, the configuration for database servers affects how well SharePoint Server performs. Some databases have to be on the same server as other databases. Conversely, some databases cannot be on the same server as other databases. For more information, see [Description of MinRole and associated services in SharePoint Server 2016](html/description-of-minrole-and-associated-services-in-sharepoint-server-2016.md) and [Storage and SQL Server capacity planning and configuration (SharePoint Server)](html/storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md).For guidance about highly available databases that use mirroring, see [Database Mirroring (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=718062&clcid=0x409). +## SQL Server Failover Clustering and Always On Availability Groups + +SQL Server 2012 introduced the AlwaysOn Availability Groups feature. This feature is a high availability and disaster recovery solution that's an alternative to database mirroring and log shipping solutions. AlwaysOn Availability Groups now support up to nine availability replicas. +> [!NOTE:] + + + + + +AlwaysOn Availability Groups require a Windows Server Failover Clustering (WSFC) cluster. A WSFC resource group is created for every availability group that is created. For more information, see the following resources: +- [AlwaysOn Availability Groups (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=718032&clcid=0x409) + + +- [Overview of AlwaysOn Availability Groups (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=809090&clcid=0x409) + + +- [Failover Clustering and Always On Availability Groups (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=800301&clcid=0x409) + + + +## Design storage for optimal throughput and manageability + +We recommend that you separate, and prioritize your data among the drives on the database server. Ideally, you should place the tempdb database, content databases, usage database, search databases, and transaction logs on separate physical hard disks. The following list provides some guidance. For more information, see [Configure databases](storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md#Section6_5). +- For collaboration or update-intensive sites, use the following ranking for storage distribution. + + The highest ranked item should be in the fastest drives. + +1. tempdb data files and transaction logs + + +2. Content database transaction log files + + +3. Search databases, except for the Search administration database + + +4. Content database data files + + +- In a heavily read-oriented portal site, prioritize data and search over transaction logs as follows. + + The highest ranked item should be in the fastest drives. + +1. tempdb data files and transaction logs + + +2. Content database data files + + +3. Search databases, except for the Search administration database + + +4. Content database transaction log files + + +- Testing and user data shows that insufficient disk I/O for tempdb can significantly impede overall farm performance. To avoid this issue, allocate dedicated disks for the drive that stores tempdb data files. + + +- For best performance, use a RAID 10 array for the drive that stores tempdb data files. The number of tempdb data files should equal the number of CPU cores, and each tempdb data file should be set to the same size. + + +- Separate database data and transaction log files across different disks. If data and log files must share disks due to space limitations, put files that have different usage patterns on the same disk to minimize concurrent access requests. + + +- Use multiple data files for heavy-use content databases, and put each on its own disk + + +- To improve manageability, monitor and make adjustments as needed to keep content databases below 200 GB, rather than restrict the database size. + + > [!NOTE:] + +Proper configuration of I/O subsystems is very important to the optimal performance and operation of SQL Server systems. For more information, see [Monitoring Disk Usage](https://social.technet.microsoft.com/wiki/contents/articles/3214.monitoring-disk-usage.aspx) +> [!TIP:] + + + + + + +## Proactively manage the growth of data and log files + +Following are recommendations to proactively manage the growth of data and log files: +- When possible, increase all data files and log files to their expected final size, or periodically increase these at set periods, for example, every month or every six months, or before rollout of a new storage-intensive site such as during file migrations. + + +- Enable database autogrowth as a protective measure to make sure that you do not run out of space in data and log files. Consider the following: + + > [!IMPORTANT:] + + + - The default settings for a new database are to grow by 1 MB increments. Because this default setting for autogrowth results in increases in the size of the database, do not rely on the default setting. Instead, use the guidance provided in [Set SQL Server options](storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md#Section6_3). + + + - Set autogrowth values to a fixed number of megabytes instead of to a percentage. The bigger the database, the bigger the growth increment should be. + + > [!NOTE:] + + + Consider for example, a scenario where content is gradually increased, say at 100MB increments, and autogrowth is set at 10MB. Then suddenly a new document management site requires a very large amount of data storage, perhaps with initial size of 50 GB. For this large addition, growth at 500 MB increments is more appropriate than 10MB increments. + + + - For a managed production system, consider autogrowth to be merely a contingency for unexpected growth. Do not use the autogrow option to manage your data and log growth on a day-to-day basis. Instead, set the autogrowth to allow for an approximate size in one year and then add a 20 percent margin for error. Also set an alert to notify you when the database runs low on space or approaches a maximum size. + + +- Maintain a level of at least 25 percent available space across drives to accommodate growth and peak usage patterns. If you add drives to a RAID array or allocate more storage to manage, monitor capacity closely to avoid running out of space. + + + +## Continuously monitor SQL Server storage and performance + +We recommend that you continuously monitor SQL Server storage and performance to make sure that each production database server is adequately handling the load put on it. Additionally, continuous monitoring enables you to establish benchmarks that you can use for resource planning. Take a comprehensive view of resource monitoring. Do not limit monitoring to resources that are specific to SQL Server. It is equally important to track the following resources on computers that are running SQL Server: CPU, memory, cache/hit ratio, and the I/O subsystem.When one or more of the server resources seems slow or overburdened, consider the following performance guidelines based on the current and projected workload. +- [Monitor and Tune for Performance](http://go.microsoft.com/fwlink/?LinkID=718063&clcid=0x409) + + +- [Performance Monitoring and Tuning Tools](http://go.microsoft.com/fwlink/?LinkID=809092&clcid=0x409) + + +- [Server Performance and Activity Monitoring](http://go.microsoft.com/fwlink/?LinkID=809093&clcid=0x409) + + +- [Windows Performance Monitor](http://go.microsoft.com/fwlink/?LinkID=809094&clcid=0x409) + + + +## Use backup compression to speed up backups and reduce file sizes + +Backup compression can speed up SharePoint backup operations. It is available in SQL Server Standard and Enterprise Edition. If you set the compression option in your backup script or configure SQL Server to compress by default, you can significantly reduce the size of your database backups and shipped logs. For more information, see [Backup Compression (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=717243&clcid=0x409) and [Data Compression](http://go.microsoft.com/fwlink/?LinkID=718120&clcid=0x409), or [Enable Compression on a Table or Index](http://go.microsoft.com/fwlink/?LinkID=798229&clcid=0x409) +## Acknowledgements + +The SharePoint Server Content Publishing team thanks the following contributors to this article: +- Kay Unkroth, Senior Program Manager, SQL Server + + +- Chuck Heinzelman, Senior Program Manager, SQL Server + + + +# See also + +#### + + [Overview of SQL Server in a SharePoint Server 2016 environment](html/overview-of-sql-server-in-a-sharepoint-server-2016-environment.md) + + + + [Storage and SQL Server capacity planning and configuration (SharePoint Server)](html/storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md) + + + + +#### + + [Securing SharePoint: Harden SQL Server in SharePoint Environments](https://blogs.technet.com/b/rycampbe/archive/2013/10/14/securing-sharepoint-harden-sql-server-in-sharepoint-environments.aspx) + + + + + + + + diff --git a/SharePoint/best-practices-for-upgrading-to-sharepoint-server-2016.md b/SharePoint/best-practices-for-upgrading-to-sharepoint-server-2016.md new file mode 100644 index 0000000000..6164d80dce --- /dev/null +++ b/SharePoint/best-practices-for-upgrading-to-sharepoint-server-2016.md @@ -0,0 +1,117 @@ +--- +title: Best practices for upgrading to SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 1c3b661f-7d88-4b2c-bc3a-3337253f3f30 +--- + + +# Best practices for upgrading to SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2016-09-16* **Summary: ** Understand how to get the most out of testing upgrade and how to guarantee a successful upgrade to SharePoint Server 2016.To increase your chances of a successful and faster upgrade to SharePoint Server 2016, follow these best practices to test and complete an upgrade. +## Best practices for testing upgrade + +To understand your environment before you upgrade it, and to plan for the time that an upgrade will require, you should try one or more trial upgrades. The goal of testing upgrade is to find and fix issues and develop confidence in the outcome before the real upgrade. To develop an accurate trial of the upgrade process from SharePoint Server 2013 with Service Pack 1 (SP1) to SharePoint Server 2016, follow these best practices: +1. Know what is in your environment. Do a full survey first. + + Document the hardware and software in your environment, where server-side customizations are installed and used, and the settings that you need. This helps you plan the trial environment and also helps you recover if upgrade fails. + + +2. Make your test environment as similar as possible to your real environment. + + If possible, use the same kind of hardware and use the same settings, the same URLs, and so on to configure it. Minimize the differences between your test environment and your real environment. As you introduce more differences, you are likely to spend time resolving unrelated issues to make sure that they will not occur during the actual upgrade. + + +3. Use real data. + + Use copies of your actual databases to run the tests. When you use real data, you can identify trouble areas and also determine upgrade performance. You can also measure how long different upgrade sequences and actions take on different kinds of data. If you cannot test all the data, test a representative subset of the data. Make sure that you find issues with the different kinds and sizes of sites, lists, libraries, and customizations that are present in your environment. If you cannot test all data because of storage concerns, try going over the data in several passes, removing the old trial copies before going on to the next batch. + + +4. Run multiple tests. + + A single test can tell you whether you will encounter big problems. Multiple tests will help you find all the issues that you might face and help you estimate a more accurate timeline for the process. By running multiple tests, you can determine the following: + + - The upgrade approaches that will work best for your environment + + + - The downtime mitigation techniques that you should plan to use + + + - How the process or performance may change after you address the issues that you uncovered in your first tests + + + + Your final test pass can help you validate whether you have addressed the errors and are ready to upgrade your production environment. + + +5. Do not ignore errors or warnings. + + Even though a warning is not an error, a warning could lead to problems in the upgrade process. Resolve errors, but also investigate warnings to make sure that you know the results that a warning might produce. + + +6. Test the upgraded environment, not just the upgrade process. + + Check your service applications and run a search crawl and review the log files. + + + +## Best practices for upgrading to SharePoint Server 2016 + +To guarantee a smooth upgrade from SharePoint Server 2013 with Service Pack 1 (SP1) to SharePoint Server 2016, follow these best practices: +1. Ensure that the environment is fully functioning before you begin to upgrade. + + An upgrade does not solve problems that already exist in your environment. Therefore, make sure that the environment is fully functioning before you start to upgrade. For example, if you are not using web applications, unextend them before you upgrade. If you want to delete a web application in Internet Information Services (IIS), unextend the web application before you delete it. Otherwise, SharePoint Server 2016 will try to upgrade the web application even though it does not exist, and the upgrade will fail. If you find and solve problems beforehand, you are more likely to meet the estimated upgrade schedule. + + +2. Perform a trial upgrade on a test farm first. + + Copy your databases to a test environment and perform a trial upgrade. Examine the results to determine the following: + + - Whether the service application data was upgraded as expected + + + - The appearance of upgraded sites + + + - The time to allow for post-upgrade troubleshooting + + + - The time to allow for the upgrade process + + + + Try a full search indexing crawl. + + +3. Plan for capacity. + + Ensure that you have enough disk, processor, and memory capacity to handle upgrade requirements. For more information about system requirements, see [System requirements for SharePoint Server 2016](html/system-requirements-for-sharepoint-server-2016.md). + + +4. Clean up before you upgrade + + Issues in your environment can affect the success of upgrade, and unnecessary or very large amounts of data can affect upgrade performance for both databases and site collections. If you don't need something in your environment, consider removing it before upgrade. If there are issues detected, try to resolve them before you start to upgrade. . + + +5. Back up your databases. + + Perform a full backup of your databases before you upgrade. That way, you can try upgrade again if it fails. + + +6. Optimize your environment before upgrade. + + Be sure to optimize your SharePoint Server 2013 with Service Pack 1 (SP1) environment to meet any limits or restrictions, either from your business or governance needs or from the SharePoint Server 2016 boundaries and limits before upgrade. This will help reduce errors during the upgrade process and prevent broken lists or sites after upgrade. + + +7. (Optional) Set the original databases to read-only if you want to keep your original environment available while you upgrade. + + If you expect a long outage period while you upgrade, you can set the databases in the original environment to read-only. Users can continue to access the data but cannot change it. For more information, see [Upgrade content databases to SharePoint Server 2016](html/upgrade-content-databases-to-sharepoint-server-2016.md). + + +8. After upgrade, review the Upgrade Status page and upgrade logs to determine whether you must address issues. Then review the upgraded sites. + + The Upgrade Status page reports on the upgrade progress, and the upgrade logs list any errors or warnings that occurred during the upgrade process. Verify all the sites and test them before you consider the upgrade finished. For more information, see [Verify database upgrades in SharePoint Server 2016](html/verify-database-upgrades-in-sharepoint-server-2016.md) and the **Review site collections upgraded** section in [Upgrade site collections to SharePoint Server 2016](html/upgrade-site-collections-to-sharepoint-server-2016.md). + + +9. Make sure that the appropriate service pack or update is applied to your 2013 environment. If you are using remote blob storage (RBS) in your environment, you must be running SharePoint Server 2013 with Service Pack 1 (SP1) in your environment before you start the upgrade process. + + + diff --git a/SharePoint/built-in-accounts-are-used-as-application-pool-or-service-identities-sharepoint.md b/SharePoint/built-in-accounts-are-used-as-application-pool-or-service-identities-sharepoint.md new file mode 100644 index 0000000000..c7d5ae046c --- /dev/null +++ b/SharePoint/built-in-accounts-are-used-as-application-pool-or-service-identities-sharepoint.md @@ -0,0 +1,30 @@ +--- +title: Built-in accounts are used as application pool or service identities (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: 5ed9fe7c-48c5-4511-aab4-aa58a440954d +--- + + +# Built-in accounts are used as application pool or service identities (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "Built-in accounts are used as application pool or service identities" for SharePoint Server 2016. **Rule Name:**   Built-in accounts are used as application pool or service identities. **Summary:**    Built-in or local computer accounts are used as an application pool identity or service identity. **Cause:**   Using built-in accounts as application pool identities or as service identities is not supported in a farm configuration. Build-in accounts include Network Service, Local Service, and Local System. **Resolution: Change the identity that is used for the service or application pool** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. On the SharePoint Central Administration website, click **Security**. + + +3. On the Security page, in the **General Security** section, click **Configure service accounts**. + + +4. On the Service Accounts page, in the **Credential Management** section, in the upper drop-down list, click the service or application pool for which you want to change the identity. + + +5. In the **Select an account for this component** list, click the domain user account that you want to associate with the service or application pool. + + If you want to register the account that you selected on the SharePoint Server 2016 farm, click **Register new managed account**. + + +6. Click **OK**. + + + diff --git a/SharePoint/business-connectivity-service.md b/SharePoint/business-connectivity-service.md new file mode 100644 index 0000000000..b5d5e60a58 --- /dev/null +++ b/SharePoint/business-connectivity-service.md @@ -0,0 +1,28 @@ +--- +title: Business Connectivity Service +ms.prod: SHAREPOINT +ms.assetid: 9cf64bff-f52b-46c9-bf25-d38d6b15e25d +--- + + +# Business Connectivity Service + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-07* **Summary:** Learn how to create and use reports and dashboards using downloadable AdventureWorks sample data and Excel Services in SharePoint Server 2013.Are you or people in your organization new to business intelligence with Office? Have you or your colleagues wanted to learn, step by step, how to create and consume reports, scorecards, and dashboards? The articles in this section can help. +## In this section + +This section contains detailed information about how to create and consume reports, scorecards, and dashboards using downloadable AdventureWorks sample data. Each article describes how to perform specific tasks so you’ll know your way around business intelligence applications, such as Excel Services. The following table describes the articles that are included in this section. +### Table: Summary of articles in this section + +ArticleDescription [Create an Excel Services dashboard using an OData data feed](html/create-an-excel-services-dashboard-using-an-odata-data-feed.md)
This scenario shows how to create a basic dashboard that contains two reports and two slicers using data that is imported into Excel. This scenario also covers how to publish a workbook to a Documents library in either Office 365 or SharePoint Server 2013.
By following the steps in this article, you’ll learn how to perform the following tasks:
Import data into Excel using an OData data feed
Create a relationship between two tables in a simple Data Model
Create and configure a basic dashboard that contains two reports and two slicers
Publish a dashboard to a Documents library in SharePoint Server 2013 (on premises) or Office 365 (online)
View and navigate a dashboard in a browser window
[Create an Excel Services dashboard using SQL Server Analysis Services data](html/create-an-excel-services-dashboard-using-sql-server-analysis-services-data.md)
Learn how to create a basic dashboard in Excel using a single external data connection to a cube that is stored in SQL Server Analysis Services.
This scenario shows how to create a dashboard that contains four reports and a timeline control in Excel. This scenario also covers how to publish content to SharePoint Server 2013, and how to consume the content in a browser window.
By following the steps in this article, you’ll learn how to perform the following tasks:
Create and share an external data connection using Excel Services
Create and configure a dashboard that includes two PivotChart reports, two PivotTable reports, and a timeline control
View and navigate a dashboard in a browser window by using Excel Services
[Create an Excel Services dashboard using a Data Model (SharePoint Server 2013)](html/create-an-excel-services-dashboard-using-a-data-model-sharepoint-server-2013.md)
Learn how to create a basic dashboard in Excel using a simple Data Model.
This scenario shows how to create a basic Data Model that contains several tables that are stored in SQL Server, and how to use that Data Model to create two reports and a slicer. This scenario also covers how to configure the reports to display meaningful information, and how to specify how you want a dashboard to be displayed in a browser window.
By following the steps in this article, you’ll learn how to perform the following tasks:
Create a Data Model that consists of several tables of data
Create and configure a dashboard that includes two reports and a slicer
Configure a PivotChart chart report to display meaningful information in the chart legend
Format numeric information in a PivotTable report
Configure a dashboard to be displayed using worksheet view or gallery view in a browser window
+# See also + +#### + + [Configure AdventureWorks for Business Intelligence solutions](html/configure-adventureworks-for-business-intelligence-solutions.md) + + + + + + + + diff --git a/SharePoint/business-data-connectivity-connectors-are-currently-enabled-in-a-partitioned-env.md b/SharePoint/business-data-connectivity-connectors-are-currently-enabled-in-a-partitioned-env.md new file mode 100644 index 0000000000..c78a3efd80 --- /dev/null +++ b/SharePoint/business-data-connectivity-connectors-are-currently-enabled-in-a-partitioned-env.md @@ -0,0 +1,13 @@ +--- +title: Business Data Connectivity connectors are currently enabled in a partitioned environment (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: e4b1234e-2b69-4c44-9621-398d20122cab +--- + + +# Business Data Connectivity connectors are currently enabled in a partitioned environment (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "Business Data Connectivity connectors are currently enabled in a partitioned environment" for SharePoint Server 2016. **Rule Name:** Business Data Connectivity connectors are currently enabled in a partitioned environment **Summary:**  Business Data Connectivity (BDC) Models containing External Content Types with database, WCF, Web service or custom connectors can be used by tenants to elevate their user permissions. In a partitioned environment, we recommend you disable the Business Data Connectivity connectors. **Cause:** Business Data Connectivity connectors are currently enabled in a partitioned environment. **Resolution: Disable unwanted connectors by using Microsoft PowerShell.** +- To disable the unwanted connectors, follow the instructions in [Business Data Connectivity connectors in a partitioned environment in SharePoint Server](https://support.microsoft.com/kb/983546). + + + diff --git a/SharePoint/business-intelligence-capabilities-in-excel-service-sharepoint-server-2013.md b/SharePoint/business-intelligence-capabilities-in-excel-service-sharepoint-server-2013.md new file mode 100644 index 0000000000..493d22810b --- /dev/null +++ b/SharePoint/business-intelligence-capabilities-in-excel-service-sharepoint-server-2013.md @@ -0,0 +1,96 @@ +--- +title: Business intelligence capabilities in Excel Service (SharePoint Server 2013) +ms.prod: SHAREPOINT +ms.assetid: cdd1d3d6-034e-458f-9324-c51d90fa9273 +--- + + +# Business intelligence capabilities in Excel Service (SharePoint Server 2013) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-06-23* **Summary: ** Excel 2013 offers a wide range of business intelligence capabilities. Learn which capabilities are supported in Excel Services (on premises).Excel offers certain business intelligence capabilities that make it easier than ever to explore and analyze data. Many of these features are supported by Excel Services. Read this article to learn about which capabilities in Excel are supported in SharePoint Server 2013 and Office Web Apps Server. +> [!IMPORTANT:] + + + + + +In this article: +- [Business intelligence capabilities in Excel 2013 ](#part1) + + +- [Business intelligence capabilities supported in Excel Services in SharePoint Server ](#part2) + + +- [Business intelligence capabilities supported in Office Web Apps Server 2013 alongside SharePoint Server 2013](#part3) + + + +## Business intelligence capabilities in Excel 2013 + + +Using Excel 2016, you can create powerful reports, scorecards, and dashboards. You can bring data into Excel, sort, and organize data, and use it to create reports and scorecards. You can also use powerful analytic capabilities in Excel to visualize and explore data. The following table describes business intelligence features in Excel. +### Table: Overview of business intelligence capabilities in Excel 2013 + +Task areaCapabilityDescriptionGet data
Native data
*Native data* is data that was imported into Excel and lives in Excel without maintaining an external data connection. This is useful for working with static data, working with data that is updated manually, and creating workbooks that are published in locations where external data connections are not supported.
Get data
External data
*External data* is data that resides on another computer and is accessed in Excel through one or more external data connections. Excel can connect to many kinds of data sources.
Work with data
Data Models
A *Data Model* is a dataset that consists of multiple tables. You can use Data Models to bring together data from different databases and create relationships between tables of data. You can use a Data Model as a source for reports, scorecards, and dashboards. For more information, see [PowerPivot: Powerful data analysis and data modeling in Excel](https://go.microsoft.com/fwlink/p/?LinkId=263500).
Work with data
Flash Fill
Flash Fill is functionality that enables you to quickly and easily format data that is displayed in a table in Excel. For example, suppose that you have imported data into Excel and you have a column that lists dates and times, and you only want to use dates. You can insert a new column, type the date that corresponds to the first item in the format that you want to use, and then use Flash Fill to automatically do this for all the rows in your table.
Create reports
Quick Analysis
Quick Analysis is functionality that enables you to select a range of data and see recommended ways to visualize that information. When you use Quick Analysis, you can see what your chart or table will resemble before actually selecting which chart type to use.
Create reports
Reports
Reports can include tables, line charts, bar charts, scatter plots, radar charts, and many other kinds of charts. You can use Excel to create powerful, interactive PivotChart reports and PivotTable reports to display relevant information by using lots of data sources.
Create reports
Scorecards
*Scorecards* are a special kind of report designed to show whether performance is on- or off-target for one or more metrics at a glance. Scorecards typically contain one or more key performance indicators (KPIs) that compare actual values to target values and use a graphical indicator, such as colors or symbols, to show performance at a glance.
In Excel, you can use KPIs that were defined in an external database or use Power Pivot to create your own KPIs.
Create reports
Power View
Power View is an add-in for Excel that you can use to create highly interactive views. Power View enables you to quickly and easily create reports, scorecards, and dashboards. You can configure connections between items in a view so that values in one report can be used as parameters for other reports in the view. For more information about Power View, see [Power View: Explore, visualize, and present your data](https://go.microsoft.com/fwlink/p/?LinkId=263501).
Create or edit reports
Field List and Field Well
When you create a PivotChart or PivotTable report, you use the **Fields** section to specify what information to display in the reports. The Fields section contains the **Field List** and **Field Well**.
The **Field List** lists items such as dimensions and members from the data source that you are using for the PivotChart or PivotTable report. You can also use the Field List to determine whether you are using native data or external data.
The **Field Well** shows which items from the **Field List** are displayed in the report. You can change what information is displayed in a PivotChart or PivotTable report by selecting (or clearing) different items and measures.
Apply filters
Timeline control
The Timeline control is a special kind of time filter that you can use in Excel. To add a timeline control to a worksheet, at least one report on the worksheet must use data that contains a calendar date/time hierarchy. You can use the timeline control to select a single time period or a range of time, and any reports that are connected to the timeline are automatically updated to show information for that time period.
Apply filters
Slicers
*Slicers* are a kind of filter that you can use to select one or more items to use as a filter for reports and scorecards in a worksheet. For example, suppose that you want to see sales information for different colors of items, such as shirts that your company carries. You can create a slicer that lists shirt colors, connect it to a sales report, and then use the slicer to view sales information for the colors that are selected in the slicer.
Explore and analyze data
Quick Explore
Quick Explore is functionality that enables you to click a value in a PivotChart or PivotTable report that uses SQL Server Analysis Services data or Power Pivot data, and then see additional information about that value displayed as a chart type. You can also use Quick Explore to drill up (or down) to view higher (or lower) levels of detail in a PivotChart or PivotTable report.
Use advanced analytic capabilities
Calculated Members and Calculated Measures
Calculated Members and Calculated Measures are items that you can define by using Multidimensional Expressions (MDX) queries in Excel. You can create calculated members and calculated measures for PivotChart or PivotTable reports that use multidimensional data that is stored in Analysis Services.
+> [!IMPORTANT:] + + + + + +Use advanced analytic capabilities
Calculated Fields
Calculated Fields enable you to change a Data Model that was created by using Power Pivot. When you create Calculated Fields, custom columns are added to the Data Model. You can then use those columns in reports that you create using that Data Model.
+> [!NOTE:] + + + + + + +## Business intelligence capabilities supported in Excel Services in SharePoint Server + + +After you have created reports, scorecards, and dashboards using Excel, you can publish those items to SharePoint Server 2013 to make them available to people in your organization. The following table summarizes which business intelligence features are supported by Excel Services (on premises). +### Table: Overview of business intelligence capabilities in Excel Services + +ItemSupported in Excel Services in the on-premises version of SharePoint Server 2013?External data connections
Most external data connections are supported in Excel Services. Excel Services supports SQL Server Analysis Services (SSAS), SQL Server databases, and OLE DB and ODBC data sources. For more information, see **Data authentication for Excel Online in Office Online Server**.
Data Models
Data Models are supported in Excel Services as long as an instance of SQL Server Analysis Services is specified for Excel Services. For more information, see [Plan Excel Services Data Model settings in SharePoint Server 2013](html/plan-excel-services-data-model-settings-in-sharepoint-server-2013.md).
Flash Fill
Flash Fill is not supported when you view a workbook in a browser window. You can edit a workbook in Excel to use Flash Fill.
Quick Analysis
Quick Analysis is not supported when you view a workbook in a browser window. You can edit a workbook in Excel to use Quick Analysis.
Reports and scorecards
Reports, scorecards, and dashboards that were created by using Excel are supported in Excel Services. You can view, sort, filter, and interact with PivotTable reports and PivotChart reports in a browser window much such as you would by using the Excel client. This includes views that were created by using Power View.
**Field List** and **Field Well** (for PivotChart and PivotTable reports)
The ability to open and use the **Field List** and **Field Well** in a browser window is supported in Excel Services.
Timeline control
The ability to use an existing timeline control is supported in Excel Services. However, to add a timeline control to a workbook, you must use the Excel client.
Slicers
The ability to use existing slicers is supported in Excel Services. However, to add slicers to a workbook, you must use the Excel client.
Quick Explore
The ability to use Quick Explore is supported in Excel Services. You can use Quick Explore to drill up and down to view higher or lower levels of information. However, you can’t create new views using Quick Explore in a browser window.
Calculated Members and Calculated Measures
The ability to use existing calculated members and calculated measures is supported in Excel Services. However, to create calculated members and calculated measures, you must use the Excel client.
Calculated Fields
The ability to use existing calculated fields is supported in Excel Services. However, to create calculated fields, you must use Power Pivot for Excel.
Business Intelligence Center
A Business Intelligence Center site template is available in SharePoint Server 2013. This enables you to create a site that serves as a central location to store business intelligence content, such as reports, scorecards, and dashboards. For more information, see **Configure a Business Intelligence Center in SharePoint Server 2013**.
Excel Web Access Web Part
An Excel Web Access Web Part is available in SharePoint Server 2013. This enables you to display all or part of an Excel workbook that was published to SharePoint Server 2013. For more information about how to use the Excel Web Access Web Part, see [Display Excel content in an Excel Web Access Web Part](https://go.microsoft.com/fwlink/p/?LinkId=296506).
+## Business intelligence capabilities supported in Office Web Apps Server 2013 and SharePoint Server 2013 + + +Office Web Apps Server is the online companion to Office Word, Excel, PowerPoint, and OneNote applications. Office Web Apps Server gives users a browser-based viewing and editing experience by providing a representation of an Office document in the browser. Organizations that have SharePoint Server 2013 might also be using Office Web Apps Server, and that has certain implications for which business intelligence capabilities are supported in a browser window. +> [!IMPORTANT:] + + + + + +The following table summarizes the business intelligence features that are supported by Office Web Apps Server and by SharePoint Server 2013. +### Table: Overview of business intelligence capabilities in Office Web Apps Server and SharePoint Server + +Excel CapabilityWhat’s supported when Office Web Apps Server is used to display workbooksWhat’s supported when SharePoint Server 2013 is used to display workbooksExternal data connections and authentication methods
Office Web Apps Server supports some, but not all, kinds of secure external data connections. Data connections that use Secure Store Service or an unattended service account are supported as long as SharePoint Server 2013 is configured to use these methods.
SharePoint Server 2013 supports most kinds of external data connections. These include SQL Server Analysis Services (SSAS), SQL Server databases, and OLE DB and ODBC data sources.
For more information about authentication methods, see **Data authentication for Excel Online in Office Online Server**.
Data Models
Office Web Apps Server enables you to view workbooks that contain Data Models that use native data. However, you can’t explore data in items such as PivotTable reports, PivotChart reports, and timeline controls that use a Data Model as the data source.
SharePoint Server 2013 enables you to view, interact with, and refresh workbooks that contain Data Models using native or external data. This includes the ability to explore data in PivotChart reports and PivotTable reports and to use timeline controls in a browser window.
Flash Fill
Office Web Apps Server does not support using Flash Fill when you edit a workbook in a browser window. However, you can open the workbook in Excel to use Flash Fill.
SharePoint Server 2013 does not support Flash Fill when you view a workbook in a browser window. However, you can open the workbook in Excel to use Flash Fill.
Quick Analysis
Office Web Apps Server does not support using Quick Analysis when you edit a workbook in a browser window. However, you can use open the workbook in Excel to use Quick Analysis.
SharePoint Server 2013 does not support Quick Analysis when you view a workbook in a browser window.
Reports and scorecards
Office Web Apps Server enables you to view, sort, and filter reports, scorecards, and dashboards that were created by using Excel. However, Office Web Apps Server does not support views that were created by using Power View.
SharePoint Server 2013 enables you to view, sort, and filter reports, scorecards, and dashboards that were created by using Excel. This includes views that were created by using Power View.
**Field List** and **Field Well** (for PivotChart and PivotTable reports)
Office Web Apps Server enables you to open and use the **Field List** and **Field Well** in a browser window.
SharePoint Server 2013 enables you to open and use the **Field List** and **Field Well** in a browser window.
Timeline control
Office Web Apps Server enables you to use an existing timeline control. To add a timeline control to a workbook you must use the Excel client.
SharePoint Server 2013 enables you to use an existing timeline control. To add a timeline control to a workbook you must use the Excel client.
Slicers
Office Web Apps Server enables you to use slicers.
SharePoint Server 2013 enables you to use slicers.
Quick Explore
Office Web Apps Server enables you to use Quick Explore.
SharePoint Server 2013 enables you to use Quick Explore.
Calculated Members and Calculated Measures
Office Web Apps Server supports workbooks that contain calculated members and calculated measures. However, to create calculated members and calculated measures, you must use the Excel client.
SharePoint Server 2013 enables you to use existing calculated members and calculated measures. However, to create calculated members and calculated measures, you must use the Excel client.
Calculated Fields
Office Web Apps Server does not support calculated fields.
SharePoint Server 2013 enables you to use existing calculated fields. However, to create calculated fields, you must use Power Pivot for Excel.
Business Intelligence Center
You can use the Business Intelligence Center site template to create a central location to store business intelligence content, such as reports, scorecards, and dashboards. For more information, see **Configure a Business Intelligence Center in SharePoint Server 2013**.
You can use the Business Intelligence Center site template to create a central location to store business intelligence content, such as reports, scorecards, and dashboards. For more information, see **Configure a Business Intelligence Center in SharePoint Server 2013**.
Excel Web Access Web Part
The Excel Web Access Web Part that is available in SharePoint Server 2013 enables you to display all or part of an Excel workbook that was published to a SharePoint library in a Web Part on a SharePoint page. Even if Office Web Apps Server is used to display workbooks in a browser window, the Excel Web Access Web Part uses Excel Services in SharePoint Server 2013 to display content in that Web Part.
For more information about how to use the Excel Web Access Web Part, see [Display Excel content in an Excel Web Access Web Part](https://go.microsoft.com/fwlink/p/?LinkId=296506).
The Excel Web Access Web Part that is available in SharePoint Server 2013 enables you to display all or part of an Excel workbook that was published to a SharePoint library in a Web Part on a SharePoint page.
For more information about how to use the Excel Web Access Web Part, see [Display Excel content in an Excel Web Access Web Part](https://go.microsoft.com/fwlink/p/?LinkId=296506).
To learn more about Office Web Apps Server, see **Office Online Server overview**. +# See also + +#### + + [Overview of Excel Services in SharePoint Server 2013](html/overview-of-excel-services-in-sharepoint-server-2013.md) + + + + +#### + + **What's new in business intelligence in SharePoint Server 2013** + + + + **Office Online Server** + + + + **Business intelligence capabilities in Excel, SharePoint Online, and Power BI for Office 365** + + + + + + + + diff --git a/SharePoint/business-intelligence-in-sharepoint-server-overview.md b/SharePoint/business-intelligence-in-sharepoint-server-overview.md new file mode 100644 index 0000000000..11943d3bb2 --- /dev/null +++ b/SharePoint/business-intelligence-in-sharepoint-server-overview.md @@ -0,0 +1,48 @@ +--- +title: Business intelligence in SharePoint Server overview +ms.prod: SHAREPOINT +ms.assetid: fae8ce7b-7c93-4cce-8a44-e3cf2f9f7b71 +--- + + +# Business intelligence in SharePoint Server overview + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-08-04* Learn about the Microsoft business intelligence (BI) tools for SharePoint Server 2016 and SharePoint Server 2013.The main requirement for SharePoint Server 2016 BI is that Microsoft SQL Server 2016 RTM is required. If you want to use Microsoft SQL Server Power Pivot for SharePoint or Microsoft Power View for SharePoint you must install the Power Pivot or Power View add-ins for SQL Server 2016 RTM. This requirement also applies to using Microsoft SQL Server Analysis Services (SSAS) and Microsoft SQL Server Reporting Services (SSRS) with SharePoint Server 2016. You must install SQL Server 2016 Analysis Services (SSAS) and SQL Server 2016 Reporting Services (SSRS).Power Pivot for SharePoint Server 2013 is only available with SQL Server 2012 SP1 Analysis Services (SSAS). +## SharePoint Server 2016 business intelligence planning + +The following SharePoint Server 2016 business intelligence planning articles are updated as new information becomes available and as users provide feedback. +### + +ContentDescription [Software requirements for business intelligence in SharePoint Server](html/software-requirements-for-business-intelligence-in-sharepoint-server.md)
Learn about the minimum software requirements to run Business Intelligence features in SharePoint Server 2016.
[Overview of Excel Services in SharePoint Server 2013](html/overview-of-excel-services-in-sharepoint-server-2013.md)
Learn how to share data-connected workbooks across an organization using Excel Services in SharePoint Server 2013.
**Plan Office Online Server**
Learn about Office Online Server requirements and prerequisites.
**Configure Office Online Server for SharePoint Server 2016**
Learn how to configure Office Online Server for SharePoint Server 2016.
[PerformancePoint Services in SharePoint Server 2016 overview](html/performancepoint-services-in-sharepoint-server-2016-overview.md)
Learn about PerformancePoint Services in SharePoint Server 2016.
[Plan for Visio Services in SharePoint Server](html/plan-for-visio-services-in-sharepoint-server.md)
Learn about planning considerations for Visio Services in SharePoint Server 2016.
[Overview of PerformancePoint reports and scorecards](html/overview-of-performancepoint-reports-and-scorecards.md)
Learn about reports and scorecards within PerformancePoint Dashboard Designer.
+# See also + +#### + + [Install SQL Server 2016 Business Intelligence Features](https://msdn.microsoft.com/en-us/library/hh231681.aspx) + + + + [SharePoint 2016 and SQL 2016 Business Intelligence](https://sharepointpromag.com/sharepoint/sharepoint-2016-and-sql-2016-business-intelligence) + + + + [Editions and Components of SQL Server 2016](https://msdn.microsoft.com/en-us/library/ms144275.aspx) + + + + [Features Supported by the Editions of SQL Server 2016](https://msdn.microsoft.com/en-us/library/cc645993.aspx) + + + + [Integration Services Features Supported by the Editions of SQL Server 2016](https://msdn.microsoft.com/en-us/library/mt736445.aspx) + + + + [BI and analytics](https://www.microsoft.com/en-us/cloud-platform/bi-analytics) + + + + + + + + diff --git a/SharePoint/cache-settings-operations-in-sharepoint-server.md b/SharePoint/cache-settings-operations-in-sharepoint-server.md new file mode 100644 index 0000000000..098353e4b8 --- /dev/null +++ b/SharePoint/cache-settings-operations-in-sharepoint-server.md @@ -0,0 +1,90 @@ +--- +title: Cache settings operations in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 0ae2f59b-309e-4853-8ce7-99bc40de4c03 +--- + + +# Cache settings operations in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-07-19* **Summary: ** Learn about the available caches and the settings that can be configured for the BLOB cache and cache profiles and object cache settings in SharePoint Server 2016 and SharePoint Server 2013.SharePoint Server provides four types of caches that help improve the speed at which web pages load in the browser: the BLOB cache, the page output cache, the object cache, and the anonymous search results cache. The BLOB cache is enabled and configured in the Web.config file in the web application to which you want to apply the cache. The page output cache and object cache areis usually configured in the user interface at the site collection level. Certain settings for these caches can also be configured at the web application level. The changes that you make to the Web.config file will be applied to all site collections and sites within the web application, and will supersede any configuration made at the site collection level or below. +> [!NOTE:] + + + + + + +## BLOB cache + + +SharePoint Server provides a disk-based cache that stores files that are used by web pages to help them load quickly in the browser, and reduces the load on the database server when it uses those files. These files are known as binary large objects (BLOBs), and the cache is known as the BLOB cache. The BLOB cache is stored directly on the hard disk drive of a front-end web server computer. The first time that a web page is called, these files are copied from the database to the cache on the server hard disk drive, and all subsequent requests for those files are then served from the hard disk drive cache of the server. By default, the BLOB cache is off and must be enabled to use the functionality it provides. When you enable the BLOB cache on your front-end web server, you reduce the load on the SharePoint Server database server created by read requests from web browsers.You enable the BLOB cache in the Web.config file of the web application to which you want to apply it. The changes that you make to the Web.config file will be applied to all site collections within the web application. For information about the BLOB cache, see [Plan for caching and performance in SharePoint Server](html/plan-for-caching-and-performance-in-sharepoint-server.md). +## Page output cache profiles + + +The page output cache stores the rendered output of a page. It also stores different versions of the cached page, based on the permissions of the users who are requesting the page. Page output cache settings can be configured at the site collection level, at the site level, and for page layouts. By default, the page output cache is turned off.The page output cache uses cache profiles that specify how long items should be held in the cache. You can specify different cache profiles to be used for anonymous and authenticated users, which optimizes the use of the cache based on the authentication methods that are allowed on the site.You can configure cache profile settings for a web application by editing the Web.config file on the application server. The cache profile settings that you configure at the web application level will be used for all cache profiles in the site collections for that web application. +> [!NOTE:] + + + + + + +> [!NOTE:] + + + + + + +## Object cache + + +The object cache reduces the amount of traffic between the web server and the SQL database by storing objects —such as lists and libraries, site settings, and page layouts —in memory on the front-end web server computer. As a result, the pages that require these items can be rendered quickly, increasing the speed with which pages are delivered to the client browser. Object cache settings can be configured at the web application level, and at the site collection level. By default, the object cache is on at the site collection level.You can optimize the object cache for a web application by specifying the size of the object cache. Specifying a larger number can enhance performance for some large sites at the cost of memory on each front-end web server. You can configure other settings for the object cache at site collection level. +> [!NOTE:] + + + + + + +## Anonymous search results cache + + +The anonymous search results cache is primarily used by publishing sites that allow access to anonymous users. It saves search results from anonymous users and reuses them for later queries that are the same as the original query. This improves performance on site pages that use the Content Search Web Part. +> [!NOTE:] + + + + + + +## TechNet articles about cache settings + +The following articles about cache settings are available to view online. Writers update articles on a continuing basis as new information becomes available and as users provide feedback. +- [Configure cache settings for a web application in SharePoint Server](html/configure-cache-settings-for-a-web-application-in-sharepoint-server.md) - Describes how to configure the disk-based BLOB cache, the page output cache profiles, and the object cache for a web application. + + +- [Configure object cache user accounts in SharePoint Server](html/configure-object-cache-user-accounts-in-sharepoint-server.md) - Describes how to configure the object cache user accounts. + + +- [Flush the BLOB cache in SharePoint Server](html/flush-the-blob-cache-in-sharepoint-server.md) - Describes how to clear the contents of the BLOB cache for a web application. + + + +# See also + +#### + + [Plan for caching and performance in SharePoint Server](html/plan-for-caching-and-performance-in-sharepoint-server.md) + + + + [Monitor cache performance in SharePoint Server 2016](html/monitor-cache-performance-in-sharepoint-server-2016.md) + + + + + + + + diff --git a/SharePoint/cached-objects-have-been-evicted-sharepoint-server-2016.md b/SharePoint/cached-objects-have-been-evicted-sharepoint-server-2016.md new file mode 100644 index 0000000000..d1e902cf72 --- /dev/null +++ b/SharePoint/cached-objects-have-been-evicted-sharepoint-server-2016.md @@ -0,0 +1,81 @@ +--- +title: Cached objects have been evicted (SharePoint Server 2016) +ms.prod: SHAREPOINT +ms.assetid: bdb3b575-7c20-490d-9a28-e7108edabad5 +--- + + +# Cached objects have been evicted (SharePoint Server 2016) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to resolve the SharePoint Health Analyzer rule "Cached objects have been evicted." **Rule Name:**  Cached objects have been evicted **Summary:**  When the memory consumption of the cache service on a cache host exceeds the low watermark threshold, objects that have already expired are evicted. When memory consumption exceeds the high watermark threshold, objects are evicted from memory, whether they have expired or not, until memory consumption returns to the low watermark. Subsequently cached objects may be rerouted to other hosts to maintain an optimal distribution of memory. **Cause:** There is not sufficient memory in the cache cluster. **Resolution: Add more RAM to the server** +- You can add more RAM to the server to increase the memory. To identify the failing server: in the SharePoint Central Administration website, in the **Monitoring** section, click **Review problems and solutions**, and then find the name of the server in the **Failing Servers** list. If there are multiple failing servers in a server farm, you must repeat this resolution on each failing server. + + + **Resolution: Increase the memory allocation of the distributed cache** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the Microsoft PowerShell cmdlets. + + + - Farm Administrators group. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2016 cmdlets. + + > [!NOTE:] + +2. Start the SharePoint 2016 Management Shell. + + For Windows Server 2012 R2, on the **Start** screen, click **SharePoint 2016 Management Shell**. + + For more information about how to interact with Windows Server 2012 R2, see [Common Management Tasks and Navigation in Windows](http://go.microsoft.com/fwlink/?LinkID=715712&clcid=0x409). + + +3. Check the current distributed cache settings from usage. To do this, run the following command: + + Get-SPDistributedCacheClientSetting + + For more information, see **Get-SPDistributedCacheClientSetting** + + +4. Stop the Distributed Cache service on all cache hosts in the farm. To do this, run the following command on each cache host: + + Stop-SPDistributedCacheServiceInstance -Graceful + + For more information, see "Perform a graceful shutdown of the Distributed Cache service" in [Manage the Distributed Cache service in SharePoint Server](html/manage-the-distributed-cache-service-in-sharepoint-server.md). + + +5. To increase the cache size of the Distributed Cache service, run the following command one time only on any cache host at the PowerShell command prompt: + + Update-SPDistributedCacheSize -CacheSizeInMB *CacheSize* + + Where: + + - *CacheSize* is the cache size's memory allocation assignment in megabytes (MB). The default value is 5 percent of total system RAM. This value should not be more than 40 percent of total system RAM with a maximum limit of 16 gigabytes (GB). + + + + +6. Start the Distributed Cache service on all cache hosts. To start the Distributed Cache service, go to the **Services on Server** page in Central Administration, and start the Distributed Cache service on all cache hosts in the farm. + + + +# See also + +#### + + **Update-SPDistributedCacheSize** + + + + + + + + diff --git a/SharePoint/capacity-management-and-sizing-overview-for-sharepoint-server-2013.md b/SharePoint/capacity-management-and-sizing-overview-for-sharepoint-server-2013.md new file mode 100644 index 0000000000..cca07d8afb --- /dev/null +++ b/SharePoint/capacity-management-and-sizing-overview-for-sharepoint-server-2013.md @@ -0,0 +1,554 @@ +--- +title: Capacity management and sizing overview for SharePoint Server 2013 +ms.prod: SHAREPOINT +ms.assetid: 97384552-ef3d-48ba-be57-1abc7d4c7f0a +--- + + +# Capacity management and sizing overview for SharePoint Server 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint 2013, SharePoint Foundation 2013, SharePoint Server 2013* * **Topic Last Modified:** 2017-07-19* **Summary:** Learn about how to use performance data to plan and manage the capacity of a SharePoint Server 2013 environment.This article provides an overview of how to effectively plan and manage the capacity of SharePoint Server 2013 environments. This article also describes how to maintain a good understanding of the capacity needs and capabilities of your deployment, by analysis of performance and volume data. It also reviews the major application impacts that affect capacity, including content characteristics and usage. +> [!IMPORTANT:] + + + + + + *Capacity management* is an ongoing process, because no implementation remains static with regard to content and usage. You need to plan for growth and change, so that your SharePoint Server 2013–based environment can continue to deliver an effective business solution. *Capacity Planning* is only one part of the capacity management cycle. It is the initial set of activities that brings the design architect to the point where there is an initial architecture that the architect believes will best serve the SharePoint Server 2013 deployment. The capacity management model includes additional steps to help you validate and tune the initial architecture, and provides a feedback loop for re-planning and optimizing the production environment until it can support design goals with optimal choices of hardware, topology, and configuration.In this article: +- [Glossary](#glossary) + + +- [Who should read capacity management articles?](#who_should_read) + + +- [Four fundamentals of performance](#fundamentals) + + +- [Capacity management versus capacity planning](#versus) + + +- [Oversizing versus undersizing](#over_vs_under) + + +- [Software limits and boundaries](#limits) + + +- [SharePoint Server 2013 deployment key differentiators](#differentiators) + + +- [Reference architectures](#reference) + + + +## Glossary + + +The following specialized terms are used in SharePoint Server 2013 capacity management documentation. +- **RPS**    Requests per second. The number of requests received by a farm or server in one second. This is a common measurement of server and farm load. The number of requests processed by a farm is greater than the number of page loads and end-user interactions. This is because each page contains several components, each of which creates one or more requests when the page is loaded. Some requests are lighter than other requests with regard to transaction costs. In our lab tests and case study documents, we remove 401 requests and responses (authentication handshakes) from the requests that were used to calculate RPS because they have insignificant impact on farm resources. + + +- **Peak hours**    The time or times during the day when load on the farm is at its maximum. + + +- **Peak load**    The average maximum daily load on the farm, measured in RPS. + + +- **Load spike**    Transient load peaks that fall outside usual peak hours. These can be caused by unplanned increases in user traffic, decreased farm throughput because of administrative operations, or combinations of such factors. + + +- **Scale up**    To scale up means to add resources such as processors or memory to a server. + + +- **Scale out**    To scale out means to add more servers to a farm. + + + +## Who should read capacity management articles? + + +Consider the following questions to determine whether you should read this content. +## Evaluating SharePoint Server 2013 + + +> [!IMPORTANT:] + + + + + + *I am an IT pro or business decision maker, and I am looking for a solution to specific business problems. SharePoint Server 2013 is an option for my deployment. Can it provide features and scalability that meet my specific requirements?* For information about how SharePoint Server 2013 scales to meet the demands of specific solutions and how to determine the hardware that will be required to support your requirements, see the following sections later in this article: +- [Hardware and software requirements for SharePoint 2013](html/hardware-and-software-requirements-for-sharepoint-2013.md) + + +For information about how to evaluate SharePoint Server 2013 for your specific business requirements, see the following articles: +- [Explore SharePoint Server](html/explore-sharepoint-server.md) + + +- [Hardware and software requirements for SharePoint 2013](html/hardware-and-software-requirements-for-sharepoint-2013.md) + + + +## Upgrading from Office SharePoint Server 2010 + + *I am currently using SharePoint Server 2010. What has changed in SharePoint Server 2013, and what do I have to consider if I upgrade? What effect will the upgrade have on my topology's performance and scale?* For information about more general upgrade considerations and guidance on how to plan and execute an upgrade from Office SharePoint Server 2007, see the following article: +- **Upgrade from SharePoint 2010 to SharePoint 2013** + + + +## Tuning and optimizing a live SharePoint-based environment + + *I have deployed SharePoint Server 2013, and I want to make sure I have the appropriate hardware and topology in place. How do I validate my architecture and maintain it correctly?* For information about monitoring and performance counters for SharePoint Server 2013 farms, see the following article: +- **Monitoring and maintaining SharePoint Server 2013** + + +For information about how to use the health monitoring tools built into the Central Administration interface, see the following article: +- [Monitoring and Reporting in SharePoint Server](html/monitoring-and-reporting-in-sharepoint-server.md) + + + *I have deployed SharePoint Server 2013, and I am experiencing performance issues. How do I troubleshoot and optimize my environment?* For information about monitoring and performance counters for SharePoint Server 2013 farms, see the following articles: +- **Monitoring and maintaining SharePoint Server 2013** + + +- **Plan for monitoring in SharePoint Server** + + +For information about tools and techniques for optimizing SharePoint Server 2013 farms, see the following article: +- **Optimize performance for SharePoint Server 2013** + + +For information about troubleshooting by using the health monitoring tools built into the Central Administration interface, see the following article: +- **Solving problems and troubleshooting in SharePoint Server** + + +For a list of capacity management articles that are available for specific SharePoint Server 2010 services and features (more articles will be added as they become available), see the following article: +- **Performance and capacity test results and recommendations (SharePoint Server 2013)** + + +For information about database sizing and performance, see the following article: +- [Storage and SQL Server capacity planning and configuration (SharePoint Server)](html/storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md) + + +For information about Remote BLOB Storage (RBS), see the following article: +- [Deciding to use RBS in SharePoint Server](html/deciding-to-use-rbs-in-sharepoint-server.md) + + + +## Beginning to end + + *I want to know everything about SharePoint Server 2013 capacity management. Where do I start?* For information about the general concepts behind capacity management and links to additional documentation and resources, see the following article: +- **Plan for performance planning in SharePoint Server 2013** + + +- **Plan logical architectures for SharePoint 2013** + + +For additional information about capacity management, see the following companion articles to this overview article: +- **Capacity planning for SharePoint Server 2013** + + +- **Performance testing for SharePoint Server 2013** + + +- **Monitoring and maintaining SharePoint Server 2013** + + +- **Optimize performance for SharePoint Server 2013** + + +You should now have a good understanding of the concepts. For information the limits and boundaries of SharePoint Server 2013, see the following article: +- [Software boundaries and limits for SharePoint 2013](html/software-boundaries-and-limits-for-sharepoint-2013.md) + + +When you are ready to identify a starting point topology for your SharePoint Server 2013–based environment, you can look through the library of available technical case studies to find the one that most closely matches your requirements. For a list of SharePoint Server 2010 case studies (SharePoint Server 2013 case studies will be published as they become available), see the following article: +- [Performance and capacity technical case studies (SharePoint Server 2010)](https://go.microsoft.com/fwlink/p/?LinkId=95813) + + +For information about health monitoring and troubleshooting by using the health monitoring tools built into the Central Administration interface, see the following articles: +- **Plan for monitoring in SharePoint Server** + + +- **Solving problems and troubleshooting in SharePoint Server** + + +For more information about how to virtualize SharePoint Server 2013–based servers, see the following article: +- **Plan for on-premises or hosted virtualization in SharePoint 2013** + + +For more information about high availability and disaster recovery, see the following article: +- [Plan for high availability and disaster recovery for SharePoint Server](html/plan-for-high-availability-and-disaster-recovery-for-sharepoint-server.md) + + + +## Four fundamentals of performance + + +Capacity management focuses on the following four major aspects of sizing your solution: +- **Latency**    For the purposes of capacity management, latency is defined as the duration between the time that a user initiates an action, such as clicking a hyperlink, and the time until the last byte is transmitted to the client application or web browser. + + +- **Throughput**    Throughput is defined as the number of concurrent requests that a server or server farm can process. + + +- **Data scale**    Data scale is defined as the content size and data corpus that the system can host. The structure and distribution of the content databases has a significant effect on the time that is required for the system to process requests (latency) and the number of concurrent requests it can serve (throughput). + + +- **Reliability**    Reliability is a measurement of the ability of the system to meet the targets set for the latency and throughput over time. + + +The main goal of managing your environment's capacity is to establish and maintain a system that meets your organization's latency, throughput, data scale, and reliability targets. +## Latency + + + *Latency* , also known as end-user perceived latency, is composed of three major components: +- The time it takes the server to receive and process the request. + + +- The time it takes the request and the server response to transfer over the network. + + +- The time it takes the response to render on the client application. + + +Different organizations define different latency goals based on business requirements and user expectations. Some organizations can afford latency of several seconds, whereas other organizations require very fast transactions. Optimizing for very fast transactions is usually costlier, and usually requires more powerful clients and servers, more recent browser and client application versions, high-bandwidth network solutions, and possibly development investments and page tuning.Some major factors that contribute to longer end-user perceived latencies, and examples of some common problems, are described in the following list. These factors are especially relevant in scenarios where the clients are geographically distant from the server farm, or are accessing the farm across a low-bandwidth network connection. +- Features, services, or configuration parameters that are not optimized might delay the processing of requests and impact latency for both remote and local clients. For more information, see [Throughput](45dc078f-de39-425c-a94f-1de78b68052e.md#throughput) and [Reliability](45dc078f-de39-425c-a94f-1de78b68052e.md#reliability) later in this article. + + +- Web pages that generate unnecessary requests to the server to download required data and resources. Optimization would include downloading the minimum number of resources to draw the page, reducing the sizes of images, storing the static resources in folders that enable anonymous access, clustering requests and enabling page interactivity while resources are downloaded asynchronously from the server. These optimizations are important for achieving an acceptable first time visit browse experience. + + +- Excessive volume of data being transmitted over the network contributes to latency and throughput degradation. For example, images and other binary objects on a page should use a compressed format such as .png or .jpg instead of bitmaps when it is possible. + + +- Web pages that are not optimized for second-access page loads. Page Load Time (PLT) improves for second-access page loads because some page resources are cached on the client, and the browser must only download dynamic non-cached content. Unacceptable second-access page load latencies are often caused by incorrect Binary Large Object (BLOB) cache configuration or local browser caching being disabled on client computers. Optimizations would include correct caching of resources on the client. + + +- Web pages that have non-optimized custom JavaScript code. This might slow rendering of the page on the client. Optimization would delay JavaScript from being processed on the client until the rest of the page has loaded, and preferably calling scripts instead of adding JavaScript inline. + + + +## Throughput + + + *Throughput* is described by the number of requests that a server farm can process in a unit of time, and is also often used to measure the scale of operations that the system is expected to sustain based on the size of the organization and its usage characteristics. Every operation has a specific cost in server farm resources. Understanding the demand and deploying a farm architecture that can consistently satisfy demand requires estimating the expected load, and testing the architecture under load to validate that latency does not fall below target when concurrency is high and the system is under stress.Some common examples of low throughput conditions include the following: +- **Inadequate hardware resources**    When the farm receives more requests than it can process concurrently, some requests are queued, which cumulatively delays the processing of each subsequent request until demand is reduced enough for the queue to be cleared. Some examples of optimizing a farm to sustain greater throughput include the following: + + - Ensure that the processors on farm servers are not over-utilized. For example, if CPU usage during peak hours or load spikes consistently exceeds 80 percent, add more servers or redistribute services to other farm servers. + + + - Ensure that there is sufficient memory on application servers and web servers to contain the complete cache. This will help avoid calls to the database to serve requests for uncached content. + + + - Ensure that database servers are free of bottlenecks. If total available disk IOPS are insufficient to support peak demand, add more disks or redistribute databases to underutilized disks. See the Removing Bottlenecks section of **Monitoring and maintaining SharePoint Server 2013** for more information. + + + - If adding resources to existing computers is insufficient to resolve throughput issues, add servers and redistribute affected features and services to the new servers. + + +- **Non-optimized custom web pages**    Adding custom code to frequently used pages in a production environment is a common cause of throughput issues. Adding custom code might generate additional round trips to the database servers or Web services to service data requests. Customization of infrequently used pages might not significantly impact throughput, but even well-optimized code can decrease farm throughput if it is requested thousands of times a day. SharePoint Server 2013 administrators can enable the Developer Dashboard to identify custom code that requires optimization. Some examples of optimizing custom code include the following: + + - Minimize the number of web service requests and SQL queries. + + + - Fetch the minimum required data in each trip to the database server while limiting the number of necessary round trips. + + + - Avoid adding custom code to frequently used pages. + + + - Use indexes when you are retrieving a filtered amount of data. + + +- **Untrusted solutions**    Deploying custom code in bin folders can cause slow server performance. Every time that a page that contains untrusted code is requested, SharePoint Server 2013 must perform security checks before the page can be loaded. Unless there is a specific reason to deploy untrusted code, you should install custom assemblies in the GAC to avoid unnecessary security checking. + + + +## Data scale + + + *Data scale* is the volume of data the server or server farm can store while meeting latency and throughput targets. Generally, the greater the data volume on the farm, the greater the impact on overall throughput and user experience. The method that is used to distribute data across disks and database servers can also affect farm latency and throughput.Database sizing, data architecture, and sufficient database server hardware are all very important to an optimal database solution. In an ideal deployment, content databases are sized according to limits guidance and are distributed across physical disks so that requests are not queued because of disk overutilization, and database servers can support peak loads and unexpected spikes without exceeding resource utilization thresholds.Also, certain operations can lock certain tables during the operation. An example of this is large site deletion, which can cause the related tables in the content database where the site resides to be locked until the delete operation is complete.Some examples of optimizing a farm for data and storage performance include the following: +- Ensure that databases are properly distributed across the database servers, and that database server resources are sufficient to support the volume and distribution of data. + + +- Separate database volumes into unique Logical Units (LUNs), consisting of unique physical disk spindles. Use multiple disks that have low seek time and appropriate RAID configurations to satisfy database server storage demands. + + +- You can use Remote BLOB Storage (RBS) if your corpus contains many Binary Large Objects (BLOBs). RBS can provide the following benefits: + + - BLOB data can be stored on less expensive storage devices that are configured to handle simple storage. + + + - The administration of the BLOB storage is controlled by a system that is designed specifically to work with BLOB data. + + + - Database server resources are freed for database operations. + + + + These benefits are not free. Before you implement RBS with SharePoint Server 2013, you should evaluate whether these potential benefits override the costs and limitations of implementing and maintaining RBS. + + +For more information about how to plan data scale, see [Storage and SQL Server capacity planning and configuration (SharePoint Server)](html/storage-and-sql-server-capacity-planning-and-configuration-sharepoint-server.md). +## Reliability + + + *Reliability* is the aggregate measurement of the server farm's capacity to meet established latency, throughput, and data capacity targets over time. A reliable farm is one for which uptime, responsiveness, failure rate, and frequency and amplitude of latency spikes are within established targets and operational requirements. A reliable farm can also consistently sustain latency and throughput targets during peak load and peak hours, or when system operations such as crawling or daily backups occur.A major factor in sustaining reliability is the effect of common administrative operations on performance targets. During certain operations, such as rebuilding the database indexes, maintenance timer jobs, or deleting multiple sites that have large volume of content, the system might be unable to process user requests as quickly. In this case, both latency and throughput of end-user requests can be affected. The impact on the farm depends on the frequency and transaction cost of such less common operations, and whether they are run during normal operating hours. Some examples of how to sustain a more reliable system include the following: +- Schedule resource-intensive timer jobs and administrative tasks during off-peak hours. + + +- Scale up hardware on existing farm servers, or scale out by adding web servers, application servers or additional database servers. + + +- Distribute resource-intensive services and features to dedicated servers. You can also use a hardware load balancer to direct feature-specific traffic to a web server dedicated to specific features or services. + + + +## Capacity management versus capacity planning + + +Capacity management extends the concept of capacity planning to express a cyclical approach in which the capacity of a SharePoint Server 2013 deployment is continually monitored and optimized to accommodate changing conditions and requirements.SharePoint Server 2013 offers increased flexibility and can be configured to sustain usage scenarios in a wide variety of different scale points. There is no single deployment architecture. Therefore, system designers and administrators must understand the requirements for their specific environments. +## SharePoint Server 2013 capacity management model + + + + + + +![Capacity Management Model](images/) + + + + +- **Step 1: Model**    Modeling is the process by which you decide the key solutions that you want your environment to support, and establish all important metrics and parameters. The output of the modeling exercise should be a list of all the key data that you must have to design your environment. + + - Understand your expected workload and dataset. + + + - Set farm performance and reliability targets. + + + - Analyze the SharePoint Server 2013 IIS logs. + + +- **Step 2: Design**    Once you have collected the data from Step 1, you can design your farm. Outputs are detailed data architecture and physical and logical topologies. + + - Determine your starting point architecture. + + + - Select your hardware. + + +- **Step 3: Pilot, Test, and Optimize**    If you have designed a new deployment, you must deploy a pilot environment for testing against your workload and expected usage characteristics. For an existing farm, testing is advised when major changes are being made to the infrastructure, but regular optimization based on monitoring results might be necessary to maintain performance targets. The output from this phase is analysis of test results against targets, and an optimized architecture able to sustain established performance and capacity targets. + + - **Pilot**    Deploy a pilot environment. + + + - **Test**    Test against latency and throughput targets. + + + - **Optimize**    Gather test results and make any required changes to the farm resources and topology. + + +- **Step 4: Deploy**    This step describes implementing the farm, or deploying changes to an existing farm. Output for a new design is a completed deployment to live production, including all content and user migrations. Output for an existing farm is revised farm maps and updates to maintenance plans. + + +- **Step 5: Monitor and maintain**    This step describes how to set up monitoring, and how to predict and identify bottlenecks and perform regular maintenance and bottleneck mitigation activities. + + + +## Oversizing versus undersizing + + + *Oversizing* describes an approach to farm design in which targets are achieved without full utilization of hardware, and the resources in the SharePoint Server 2013 farm are significantly and consistently underutilized. In an oversized deployment, memory, CPU, and other indicators on the farm's resources show that it can well serve the demand with fewer resources. The downside of oversizing is increased hardware and maintenance expenditures and can impose greater power and space demands. *Undersizing* describes an approach to farm design in which performance and capacity targets are not achievable because hardware resources in the SharePoint Server 2013 farm are over-utilized. Undersizing a farm is sometimes done to reduce hardware costs, but generally results in high latency leading to a poor user experience, low satisfaction, frequent escalations, high support costs, and unnecessary spending for troubleshooting and tuning the environment.When you design your farm, make sure that your farm can meet established performance and capacity targets, both under regular peak load and unexpected spikes. Design, testing, and optimization will help you to make sure that that your farm has the correct hardware. To maintain performance targets and accommodate growth, it is always more desirable to have more resources than you must have to meet your targets. The cost of overinvestment in hardware is usually far less than the cumulative expenses related to troubleshooting problems cause by undersizing. You should always size a system to respond adequately during peak demand, which might be different for specific services at different times. To effectively estimate capacity requirements, you must identify the worst case demand period for all resources. There might be increased load on various features and services at certain times of the day, such as first thing in the morning or after lunch. The farm must also be able to support unplanned peaks, such as when organization-wide announcements are made and an unusually high number of users access a site at the same time. During such periods of high demand, users will experience high latency or not get a response from the farm at all unless sufficient farm resources are available to satisfy the increased load on the farm.Farm capacity should also be revisited when additional users will be provisioned in the enterprise. Situations such as a merger or acquisition characterized by new employees or members accessing the farm can have adverse effects on performance if not planned and estimated in advance. +## Operational states: Green Zone and Red Zone + + +When we describe the load of a production system, we refer to two major operational states: the " *Green Zone* " state in which the system is operating under the normal, expected load range, and the " *Red Zone* " state, which is a state in which the farm experiences very high transient resource demand that can only be sustained for limited periods until failures and other performance and reliability issues occur. **Green Zone**    This is the state at which the server or farm is operating under normal load conditions, up to expected daily peak loads. A farm operating in this range should be able to sustain response times and latency within acceptable parameters. **Red Zone**    The operating range in which load is greater than normal peak load, but can still service requests for a limited period. This state is characterized by greater than normal latency and possible failures caused by saturation of system bottlenecks.The ultimate goal of farm design is to deploy an environment that can consistently support Red Zone load without service failure and within acceptable latency and throughput targets. +## Software limits and boundaries + + +In SharePoint Server 2013, there are certain limits that are by design and cannot be exceeded, and other limits that are set to default values that can be changed by the farm administrator. There are also certain limits that are not represented by a configurable value, such as the number of site collections per web application. *Boundaries* are absolute limits that cannot be exceeded by design. It is important to understand these limits to ensure that you do not make incorrect assumptions when you design your farm.An example of a boundary is the 2 GB document size limit. You cannot configure SharePoint Server 2013 to store documents that are larger than 2 GB. This is a built-in absolute value, and cannot be exceeded by design. *Thresholds* are those that have a default value that cannot be exceeded unless the value is changed. Thresholds can, in certain circumstances, be exceeded to accommodate variances in your farm design. However, you must understand that doing this might affect the performance of the farm and the effective value of other limits.The default value of certain thresholds can only be exceeded up to an absolute maximum value. A good example is the document size limit again. By default, the document size limit is set to 50 MB, but can be changed to a maximum value of 2 GB. *Supported limits* define the tested value for a given parameter. The default values for these limits were defined by testing, and represent the known limitations of the product. Exceeding supported limits could cause unexpected results, significant performance degradation, or other detrimental effects.Some supported limits are configurable parameters that are set by default to the recommended value, whereas other limits relate to parameters that are not represented by a configurable value.An example of a supported limit is the number of site collections per web application. The supported limit is the largest number of site collections per web application that met performance benchmarks during testing. It is important to be aware that many of the limit values that are provided in this document represent a point in a curve that describes an increasing resource load and concomitant performance degradation as the value increases. Therefore, exceeding certain limits, such as the number of site collections per web application, might only result in a fractional decrease in farm performance. However, in most cases, operating at or near an established limit is not a best practice, as acceptable performance and reliability targets are best achieved when a farm's design provides for a reasonable balance of limits values.Thresholds and supported limits guidelines are determined by performance. In other words, you can exceed the default values of the limits, but as you increase the limit value, farm performance and the effective value of other limits might be affected. Many limits in SharePoint Server 2013 can be changed. However, you should understand how changing a given limit affects other parts of the farm.If you contact Microsoft Customer Support Services about a production system that does not meet the published minimum hardware specifications as described in [Hardware and software requirements for SharePoint 2013](html/hardware-and-software-requirements-for-sharepoint-2013.md), support will be limited until the system is upgraded to the minimum requirements. +## How limits are established + +In SharePoint Server 2013, thresholds and supported limits are established through testing and observation of farm behavior under increasing loads up to the point where farm services and operations reach their effective operational limits. Some farm services and components can support a greater load than others. Therefore, in some cases, you must assign a limit value that is based on an average of several factors.For example, observations of farm behavior under load when site collections are added indicate that certain features exhibit unacceptably high latency while other features are still operating within acceptable parameters. Therefore, the maximum value assigned to the number of site collections is not absolute, but is calculated based on an expected set of usage characteristics in which overall farm performance would be acceptable at the given limit under most circumstances. If other services are operating under parameters that are greater than those used for limits testing, the maximum effective limits of other services will be reduced. Therefore, it is important to execute rigorous capacity management and scale testing exercises for specific deployments to establish effective limits for that environment.For more information about boundaries and limits and how they affect the capacity management process, see [Software boundaries and limits for SharePoint 2013](html/software-boundaries-and-limits-for-sharepoint-2013.md). +## SharePoint Server 2013 deployment key differentiators + + +Each SharePoint Server 2013 deployment has a key set of characteristics that will make it unique and different from other farms. These key differentiators can be described by these four major categories: +- **Specification**    Describes the farm's hardware, and the farm topology and configuration. + + +- **Workload**    Describes the demand on the farm, including the number of users and the usage characteristics. + + +- **Dataset**    Describes content sizes and distribution. + + +- **Health and performance**    Describes the farm's performance against latency and throughput targets. + + + +## Specifications + + **Hardware**Hardware is the computer's physical resources such as processors, memory, and hard disks. Hardware also includes physical network components such as NICs (Network Interface Cards), cables, switches, routers and hardware load balancers. Many performance and capacity issues can be resolved by making sure that the correct hardware is being used. Conversely, a single misapplication of a hardware resource, such as insufficient memory on a server, can affect performance across the entire farm. **Topology**Topology is the distribution and interrelationships of farm hardware and components. There are two kinds of topology: +- **Logical topology**    The map of software components such as services and features in a farm. + + +- **Physical topology**    The map of servers and physical resources. + + +Typically, the number of users and usage characteristics determine the physical topology of a farm, and business requirements such as the need to support specific features for expected load drives the logical topology. **Configuration**We use the term configuration to describe software settings and how parameters are set. Also, configuration refers to caching, RBS, how configurable limits are set, and any part of the software environment that can be set or modified to meet specific requirements. +## Workload + +Workload defines the key operational characteristics of the farm, including the user base, concurrency, features that are being used, and the user agents or client applications that are used to connect with the farm. Different SharePoint Server 2013 features have different associated costs on the farm's resources. Popularity of more costly features can potentially significantly impact the performance and the health of the system. Understanding your expected demand and usage characteristics will enable you to correctly size your implementation, and reduce the risk of constantly running the system in an unhealthy condition. **User Base**The user base of a SharePoint Server 2013–based application is a combination of the total number of users and how they are geographically distributed. Also, within the total user base, there are subgroups of users who might use given features or services more heavily than other groups. Concurrency of users is defined as the total percentage of users actively using the system at a given time. Indicators that define the user base include the number of total unique users and number of concurrent users. **Usage Characteristics**A farm's performance can be affected not only by the number of users interacting with the system, but also by their usage characteristics. Two organizations that have the same number of users might have significantly different requirements based on how often users access farm resources, and whether resource-intensive features and services are enabled on the farm. Indicators that describe the usage characteristics include the frequency of unique operations, the overall operational mix (the ratio of read and write operations and administrative operations), and the usage patterns and load against new features that are enabled on the farm (such as My Sites, Search, Workflows, and Office Online). +## Dataset + +The volume of content that is stored in the system and the characteristics of the architecture in which it is stored can have a significant effect on the overall health and performance of the system. Understanding the size, access frequency, and distribution of data will enable you to correctly size the storage in the system and prevent it from becoming the bottleneck that slows down user interactions with farm services and affects the end-user experience.To correctly estimate and design the storage architecture of a SharePoint Server 2013–based solution, you need to know the volume of data that you will store on the system, and how many users are requesting data from different data sources. The volume of the content is an important element of sizing disk capacity, because it can influence the performance of other features, and can also potentially affect network latency and available bandwidth. Indicators that define the dataset include total size of content, total number of documents, total number of site collections, and average and maximum sizes of site collection. +## Health and performance + +SharePoint Server 2013 farm health is basically a simplified measurement or score that reflects the reliability, stability, and performance of the system. How well the farm performs against targets is basically dependent on the first three differentiators. The health and performance score can be tracked and described by a distillation of a set of indicators. For more information, see **Monitoring and maintaining SharePoint Server 2013** and **Plan for monitoring in SharePoint Server**. These indicators include the system's uptime, end-user perceived latency, page failure rates, and resource utilization indicators (CPU, RAM).Any significant change in hardware, topology, configuration, workload, or dataset can significantly vary the reliability and responsiveness of the system. The health score can be used to track performance over time and to assess how changing operating conditions or system modifications affect farm reliability. +## Reference architectures + + +SharePoint Server 2013 is a complex and powerful product, and there is no one-size-fits-all architecture solution. Each SharePoint Server 2013 deployment is unique, and is defined by its usage and data characteristics. Every organization needs to perform a thorough capacity management process and effectively take advantage of the flexibility that the SharePoint Server 2013 system offers to customize a correctly sized solution that best satisfies the organizational needs. The concept of reference architectures is meant to describe and illustrate the different major categories of SharePoint Server 2013 deployments, and not to provide a recipe for architects to use to design their solutions. This section focuses on describing the vectors on which SharePoint Server 2013 deployments usually scale.The architectures listed here are provided as a useful way to understand the general differentiators between these generic categories, and to distinguish them by general cost factors and scale of effort. +## Single server deployment + +The single server deployment architecture consists of one server that is running SharePoint Server 2013 and a supported version of SQL Server. This architecture might be appropriate for evaluation purposes, developers or for an isolated non-mission-critical departmental implementation with only a few users. However, we do not recommend its use for a production environment. + + + +![Single-server Deployment Model](images/) + + + + + + + + + + + + +## Small farm deployment + +A small farm deployment consists of a single database server or cluster and one or two SharePoint Server 2013–based computers. The major architecture characteristics include limited redundancy and failover, and a minimal set of SharePoint Server 2013 capabilities enabled. A small farm is useful to serve only limited deployments, with a minimal set of service applications enabled, a relatively small user base, a relatively low usage load (a few requests per minute up to very few requests per second), and a relatively small volume of data (10 or more gigabytes). + + + +![Small Farm Deployment Model](images/) + + + + + + + + + + + + +## Medium farm deployment + +This architecture introduces the breakdown of the topology into three tiers: dedicated Web servers, dedicated application servers, and one or more database servers or clusters. Separating the front end server tier from the application server tier allows greater flexibility in service isolation and helps balancing the load across the system. This is the most common architecture, and includes a wide spectrum of service topologies and farm sizes. A medium farm deployment is useful to serve environments that have the following: +- Several service applications distributed across multiple servers. A typical set of features might include the Office Online Service, User Profile Service, Managed Metadata Service, and Excel Calculation Service. + + +- A user base of tens of thousands of users and a load of 10 to 50 requests per second. + + +- A data store of one or two terabytes. + + + + + + +![Capacity - Medium Farm Deployment Model](images/) + + + + + + + + + + + + +## Large farm deployment + +Large farm deployments introduce the breakdown of services and solutions across multiple farms, and additional scaling out the tiers on a single farm. Several SharePoint Server 2013 services can be deployed on a dedicated services farm that serves requests from multiple consuming farms. In these large architectures, there are typically Web servers, multiple application servers, depending on the usage characteristic of each of the local (non-shared) services, and multiple SQL Server–based servers or SQL Server clusters, depending on the content size and the application services databases that are enabled on the farm. Large farm architectures are expected to serve deployments that have the following: +- Several service applications federated and consumed from dedicated services farm, typically the User Profile Service, Search, Managed Metadata service, and Web Analytics. + + +- Most other service applications are enabled locally. + + +- A user base in the range of hundreds of thousands of users. + + +- A usage load in the range of hundreds of requests per second. + + +- A dataset in the range of ten or more terabytes. + + + + + + +![Capacity - Large Farm Deployment Model](images/) + + + + + + + + + + + + +# See also + +#### + + **Capacity planning for SharePoint Server 2013** + + + + **Performance testing for SharePoint Server 2013** + + + + **Monitoring and maintaining SharePoint Server 2013** + + + + **Plan for monitoring in SharePoint Server** + + + + [Software boundaries and limits for SharePoint 2013](html/software-boundaries-and-limits-for-sharepoint-2013.md) + + + + **Performance and capacity test results and recommendations (SharePoint Server 2013)** + + + + [Hardware and software requirements for SharePoint 2013](html/hardware-and-software-requirements-for-sharepoint-2013.md) + + + + [Performance and capacity technical case studies (SharePoint Server 2010)](https://go.microsoft.com/fwlink/p/?LinkId=95813) + + + + + + + + diff --git a/SharePoint/change-site-collection-administrators-in-sharepoint-server.md b/SharePoint/change-site-collection-administrators-in-sharepoint-server.md new file mode 100644 index 0000000000..27eca41f6c --- /dev/null +++ b/SharePoint/change-site-collection-administrators-in-sharepoint-server.md @@ -0,0 +1,119 @@ +--- +title: Change site collection administrators in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: b3d2f46d-783c-4f81-9c0a-d41a3486917e +--- + + +# Change site collection administrators in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary: ** How to change site collection administrators for SharePoint Server 2016 and SharePoint 2013 site collections by using the SharePoint Central Administration website or Microsoft PowerShell.A site collection administrator in SharePoint Server can configure the appearance and behavior of the site, configure search settings and site directory settings, and allocate storage space. A site collection must have one primary site collection administrator and can have one secondary site collection administrator. The primary and secondary site collection administrators receive administrative email alerts for the site collection. The primary and secondary site collection administrators are automatically added to the SharePoint Site Collection Administrators group. You can add as many additional accounts as you want to the SharePoint Site Collection administrators group, but only the primary and secondary site collection administrators will receive administrative alerts for the site collection. All members of the SharePoint Site Collection Administrators group have full administrative permissions to the site collection. In this article: +- [Add a site collection administrator](#section1) + + +- [Remove a site collection administrator](#section2) + + + +## Change the primary or secondary site collection administrator + + +Use this procedure when you want to make a user a primary or secondary site collection administrator for a specific site collection. +> [!CAUTION:] + + + + + + **To change the primary or secondary site collection administrator by using Central Administration** +1. Verify that you have the following administrative credentials: + + - To add a site collection administrator, you must be a member of the Farm Administrators group on the computer that is running Central Administration. + + +2. In Central Administration, click **Application Management**. On the **Application Management** page, in the **Site Collections** section, click **Change site collection administrators**. + + +3. On the **Site Collection Administrators** page, click the arrow next to the site collection name, and then select **Change Site Collection** if the site collection you want is not already selected. + + +4. If the site collection to which you want to add an administrator is listed, select the URL of the site collection, and then click **OK**. If the site collection is not listed, click the arrow next to the web application name, click **Change Web Application**, select the name of the web application that contains the site collection, select the URL of the site collection, and then click **OK**. + + +5. In the **Primary site collection administrator** or **Secondary site collection administrator** area, either type the name of the user whom you want to add by using the format ** \\ ** or select the user by using the address book. + + +6. Click **OK**. + + + **To add a primary or secondary site collection administrator by using Windows PowerShell** +1. Verify that you meet the following minimum requirements: See **Add-SPShellAdmin**. + + +2. Open the SharePoint Management Shell. + + +3. At the PowerShell command prompt, type the following command to replace the secondary site collection administrator: + + ``` + +Set-SPSite -Identity " " -SecondaryOwnerAlias " " + ``` + + + Where: + + - ** is the URL of the site collection to which you want to add a site collection administrator. + + + - ** is name of the user whom you want to add in the format ** \\ ** . + + +The previous procedure shows a common way to use the **Set-SPSite** cmdlet to add a secondary site collection administrator. You can specify different parameters to configure different settings for a site collection. For more information, see **Set-SPSite**. We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. +## Remove a site collection administrator + + +Use this procedure to specify the user to be removed from the site collection administrator list. This procedure does not remove the user from Active Directory Domain Services (AD DS). **To remove a site collection administrator by using Central Administration** +1. Verify that you have the following administrative credentials: + + - To remove a site collection administrator, you must be a member of the Farm Administrators group on the computer that is running Central Administration. + + +2. In Central Administration, select **Application Management**. On the **Application Management** page, in the **Site Collections** section, click **Change site collection administrators**. + + +3. On the **Site Collection Administrators** page, click the arrow next to the site collection name, and then click **Change Site Collection**. + + +4. If the site collection from which you want to remove an administrator is listed, select the URL of the site collection, and then click **OK**. If the site collection is not listed, click the arrow next to the web application name, click **Change Web Application**, select the name of the web application that contains the site collection, select the URL of the site collection, and then click **OK**. + + +5. Every site collection must have a primary site collection administrator. If you want to remove the primary site collection administrator, you must replace it with a different primary site collection administrator. To do so, select the current administrator's name, press the Delete key, and then either type the name of the replacement site collection administrator by using the format ** \\ ** or select a replacement site collection administrator by using the address book. + + +6. To remove the secondary site collection administrator, select the administrator's name, and then press the **Delete** key. + + +7. Click **OK**. + + + +# See also + +#### + + [Create a site collection in SharePoint Server](html/create-a-site-collection-in-sharepoint-server.md) + + + + +#### + + [Manage administrators for a site collection](https://go.microsoft.com/fwlink/?linkid=845358) + + + + + + + + diff --git a/SharePoint/change-the-default-account-for-crawling-in-sharepoint-server.md b/SharePoint/change-the-default-account-for-crawling-in-sharepoint-server.md new file mode 100644 index 0000000000..91e28a0628 --- /dev/null +++ b/SharePoint/change-the-default-account-for-crawling-in-sharepoint-server.md @@ -0,0 +1,61 @@ +--- +title: Change the default account for crawling in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: fa4625ab-9076-4506-aa7c-a19b6e45a847 +--- + + +# Change the default account for crawling in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Change the user name or password of the account that the SharePoint Server 2016 or SharePoint Server 2013 Search service uses by default for crawling.The account that the SharePoint Server Search service uses by default for crawling is called the *default content access account* . It must be a domain account with a password that is current in Active Directory Domain Services (AD DS). If the password of this domain account expires, the Search service is not able to use the account to crawl content.The password of the default content access account has two additional dependencies on the domain account password in AD DS: +- If you change the password of the account in AD DS, you must make the same change for the password of the default content access account in SharePoint Server. + + +- If you want to change the password of the default content access account in SharePoint Server, you must first change the password in AD DS. This is because the credentials that you enter for the default content access account in SharePoint Server are checked against those in AD DS. If you enter a new password for the default content access account before the account password is changed in AD DS, an error will result and the password of the default content access account will not be changed. + + + +## + +The following procedure changes the user name and password for the default content access account. You can specify a different account for crawling particular URLs by using a crawl rule. If you specify a different account in a crawl rule and you want to change the password of that account, you must change the crawl rule. For more information, see [Manage crawl rules in SharePoint Server](html/manage-crawl-rules-in-sharepoint-server.md). **To change the default content access account** +1. Verify that the account that performs this procedure is a service application administrator for the Search service application that you want to configure. + + +2. In Central Administration, in the **Application Management** section, click **Manage service applications**. + + +3. On the Manage Service Applications page, click the Search service application for which you want to change the default content access account. + + +4. On the Search Administration page for the Search service application, in the **System Status** section, find the **Default content access account**, which is of the form *Domain\\UserName* . + + ![Screen shot of default content access account in the System Status section on the Search Administration page](images/) + + + +5. Click the default content access account name. The **Default Content Access Account** dialog box appears. + + +6. (Optional) In the **Account** text box, type a new user name. + + +7. In the **Password** text box and in the **Confirm Password** text box, type the new password, and then click **OK**. + + + +# See also + +#### + + [Create and configure a Search service application in SharePoint Server 2016](html/create-and-configure-a-search-service-application-in-sharepoint-server-2016.md) + + + + [Manage crawl rules in SharePoint Server](html/manage-crawl-rules-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/change-the-default-search-topology-in-sharepoint-server.md b/SharePoint/change-the-default-search-topology-in-sharepoint-server.md new file mode 100644 index 0000000000..d5c333b63f --- /dev/null +++ b/SharePoint/change-the-default-search-topology-in-sharepoint-server.md @@ -0,0 +1,207 @@ +--- +title: Change the default search topology in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 7fa9730a-2d11-4c78-b546-60179c5bb646 +--- + + +# Change the default search topology in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Learn how to use Windows PowerShell to change from the default search topology with an empty search index in SharePoint Server 2016 and SharePoint Server 2013 to a new search topology.This article explains how to create and activate search components in a new search topology starting from the default search topology. The procedures and the examples in this article assume that SharePoint Server and the Search service application are newly installed and that there is no content in the SharePoint Server search index. You can also use the procedures and examples to manage the search topology in SharePoint Server when the topology is part of a cloud hybrid search solution.If there are items in the SharePoint Server search index, follow the procedures in [Manage search components in SharePoint Server](html/manage-search-components-in-sharepoint-server.md) and [Manage the index component in SharePoint Server](html/manage-the-index-component-in-sharepoint-server.md).In this article: +- [Before you begin](#begin) + + +- [Overview: changing a search topology without content in the search index](#Topology_OverviewDefault) + + +- [Example: Change from the default search topology to a small enterprise search topology](#Topology_ExampleDefaultSmall) + + + +## Before you begin + + +Before you begin, review the following prerequisites. +- SharePoint Server is installed on a single server and a Search service application with a default search topology is created. In the default search topology, all the search components are located on the server that hosts Central Administration. + + +- You are an administrator of the Search service application. + + +- You have planned a target search topology. [Plan enterprise search architecture in SharePoint Server 2016](html/plan-enterprise-search-architecture-in-sharepoint-server-2016.md) gives step-by-step guidance for search in enterprises, including hardware requirements. For example farm architectures and search topologies for Internet sites, see the technical diagram [Internet sites search architectures for SharePoint Server 2016](https://download.microsoft.com/download/D/9/4/D947D942-6BB5-4F28-A51B-1FAE16334C51/SP_2016_Internet_Site_Search_Model.pdf). We recommend that you plan a target search topology based on the expected number of items in the search index for search in enterprises. + + +- SharePoint Server is installed on all the servers that you want to host search components on. The servers have been added to the farm and you are an administrator on all these servers. You can create new application servers or define application servers in an existing deployment. + + + +## Overview: changing a search topology without content in the search index + + +The following list provides an overview of the tasks involved to change from the default search topology, without any content in the SharePoint Server search index, to a new search topology. +- Ensure that no crawls have been started and that the SharePoint Server search index is empty. + + +- Start a search service instance on all the servers that you want to host search components on. + + +- Create a new empty search topology. + + +- Add search components to the new search topology. + + +- Activate the new search topology. + + +- Verify that the search topology is active. + + + +## Example: Change from the default search topology to a small enterprise search topology + + +The following procedures will create and activate a small enterprise search topology on multiple servers, as planned for in the table **Target search topology**. The small enterprise search topology uses virtual machines on physical application servers. All search components in this example are set up with fault tolerance, which means that all search components and index partitions are deployed across more than one physical machine on separate failure domains. You can follow the same procedures using different variables if you want to scale out to a larger enterprise search topology or to a search topology for Internet Sites. +### Target search topology + +Virtual machine A (on physical application server X) myserver1.example.com Virtual machine B (on physical application server X) myserver2.example.com Virtual machine C (on physical application server Y) myserver3.example.com Virtual machine D (on physical application server Y) myserver4.example.com Admin component 1
Crawl component 1
Content processing component 1
Analytics processing component 1
Query processing component 1
Index component 1 (that belongs to index partition 0)

Admin component 2
Crawl component 2
Content processing component 2
Analytics processing component 2
Query processing component 2
Index component 2 (that belongs to index partition 0)

+1. Ensure that no crawls have been started and that the search index is empty on the server that hosts Central Administration. + +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. In Central Administration, in the **Application Management** section, click **Manage Service Applications**. + + +3. On the Manage Service Applications page, in the list of service applications, click the Search service application. + + +4. Verify that the search index is empty. On the **Search Administration** page, under **System Status**, verify that **Searchable items** displays "0". + + > [!WARNING:] + +5. Verify that no crawls have been started. On the **Search Administration** page, under **Crawling**, click **Content Sources**. On the **Manage Content Sources** page, verify that the **Status** column for any existing content source displays **Idle**. + + +2. Start a SharePoint 2016 Management Shell on one of the servers in the farm. + + - For Windows Server 2008 R2: + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://technet.microsoft.com/en-us/library/hh831491.aspx). + + +3. Specify the new servers you want to add search components to, start a search service instance (ssi) on these servers and create references to the search service instances. In this procedure we have used the example host names "myserver< *n* >" for the servers as listed in the **Target search topology** table. At the Windows PowerShell command prompt, type the following command(s): + + ``` + +$hostA = Get-SPEnterpriseSearchServiceInstance -Identity "myserver1" +$hostB = Get-SPEnterpriseSearchServiceInstance -Identity "myserver2" +$hostC = Get-SPEnterpriseSearchServiceInstance -Identity "myserver3" +$hostD = Get-SPEnterpriseSearchServiceInstance -Identity "myserver4" +Start-SPEnterpriseSearchServiceInstance -Identity $hostA +Start-SPEnterpriseSearchServiceInstance -Identity $hostB +Start-SPEnterpriseSearchServiceInstance -Identity $hostC +Start-SPEnterpriseSearchServiceInstance -Identity $hostD + + ``` + +4. Wait until all the search service instances are running. At the Windows PowerShell command prompt, type the following commands until the commands return the state "Online" for each of the search service instances: + + ``` + +Get-SPEnterpriseSearchServiceInstance -Identity $hostA +Get-SPEnterpriseSearchServiceInstance -Identity $hostB +Get-SPEnterpriseSearchServiceInstance -Identity $hostC +Get-SPEnterpriseSearchServiceInstance -Identity $hostD + ``` + +5. Create a new search topology and a reference to the new search topology. At the Windows PowerShell command prompt, type the following command(s): + + ``` + +$ssa = Get-SPEnterpriseSearchServiceApplication +$newTopology = New-SPEnterpriseSearchTopology -SearchApplication $ssa + + ``` + +6. Add all the search components to the new search topology. The following Windows PowerShell commands will create the search components of the new topology and assign them to the new servers. In this small enterprise search topology there is one index partition, index partition 0. This is indicated with the parameter -IndexPartition in the commandNew-SPEnterpriseSearchIndexComponent. The index partition has one index replica on virtual machine B and one index replica on virtual machine D. Each index replica will contain the exact same search index and is hosted on a different physical server to achieve fault tolerance. At the Windows PowerShell command prompt, type the following command(s): + + ``` + +New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostA +New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostA +New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostA +New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostA +New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostB +New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostB -IndexPartition 0 +New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostC +New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostC +New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostC +New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostC +New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostD +New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostD -IndexPartition 0 + + ``` + +7. Activate the new search topology. At the Windows PowerShell command prompt, type the following command: + + ``` + +Set-SPEnterpriseSearchTopology -Identity $newTopology + ``` + +8. Verify that the new search topology is active. At the Windows PowerShell command prompt, type the following command: + + ``` + +Get-SPEnterpriseSearchTopology -SearchApplication $ssa + + ``` + + + The command returns an overview of active and inactive topologies, in this example: + + + + ``` + +TopologyId : fce8507d-61c6-4498-8038-4fd2d0a62c6e +CreationDate : 1/30/2016 2:52:00 AM +State : Inactive +ComponentCount : 6 + +TopologyId : b63d48b2-df5c-41be-a7f4-9abaee483611 +CreationDate : 1/30/2016 4:30:00 AM +State : Active +ComponentCount : 12 + ``` + + + The previous topology, the default topology in this example, is listed as inactive. The new active topology from this example will have a component count of twelve. + + +9. Verify that all components of the new search topology are running correctly. At the Windows PowerShell command prompt, type the following command: + + ``` + +Get-SPEnterpriseSearchStatus -SearchApplication $ssa -Text + ``` + + + This command should return a list of all the active search components. The state of the active search components should be displayed as **Active**. + + + diff --git a/SharePoint/choose-a-disaster-recovery-strategy-for-sharepoint-server.md b/SharePoint/choose-a-disaster-recovery-strategy-for-sharepoint-server.md new file mode 100644 index 0000000000..cb18622d30 --- /dev/null +++ b/SharePoint/choose-a-disaster-recovery-strategy-for-sharepoint-server.md @@ -0,0 +1,184 @@ +--- +title: Choose a disaster recovery strategy for SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 723dba65-4887-4ef2-9971-c51c8669cbac +--- + + +# Choose a disaster recovery strategy for SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-08-01* **Summary:**  Understand the disaster recovery options and supported technologies for recovering a SharePoint Server 2016 and SharePoint 2013 farm if there is a disaster.We define disaster recovery as the ability to recover from a situation in which the primary data center that hosts a SharePoint Server farm is unable to continue to operate. Regardless of the nature of event and its cause, the data center outage is significant enough to set into motion the actions defined in your organization's disaster recovery plan. This means putting a fully operational farm into production using computer resources that are located in a data center that is not affected by the event.In this article: +- [Introduction](#Intro) + + +- [Standby data center recovery options](#Standby) + + +- [System requirements for recovery](#SysRequire) + + +SharePoint Server 2016 and SQL Server 2014 with Service Pack 1 (SP1) or SQL Server 2016, and SharePoint 2013 and SQL Server 2008 R2 with Service Pack 1 (SP1) or SQL Server 2012 provide configuration and content recovery options that can meet the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) that are required for your business if there is a disaster. For more information about these and other disaster recovery concepts, see [High availability and disaster recovery concepts in SharePoint Server](html/high-availability-and-disaster-recovery-concepts-in-sharepoint-server.md). +## Introduction + + +An effective disaster recovery strategy for a SharePoint Server farm must be sufficient to meet your organization's business requirements, which are typically expressed by using two measures: Recovery Time Objective (RTO) and Recovery Point Objective (RPO). RTO and RPO requirements are derived by determining the downtime cost to the organization if a disaster happens. +> [!IMPORTANT:] + + + + + +Downtime costs vary significantly between and within industries, especially due to the different effects of downtime. Business size is the most obvious factor. However, it is not the only one. Setting a measure means establishing the nature and implications of the failure. Reduced to the simplest level, a failure of a critical application could lead to the following types of losses: +- Loss of the application service. The effect of downtime varies with the application and the business. + + +- Loss of data. The potential loss of data due to a system outage can have significant legal and financial impact. + + +Most organizations will incur a downtime cost from both of the previous types of loss but the nature of the business will determine which type of loss has the biggest effect. The following article, written by Chris Preimesberger at eWEEK, highlights the financial effect of data center downtime. [Unplanned IT Downtime Can Cost $5K Per Minute: Report](https://go.microsoft.com/fwlink/p/?LinkId=272806).In most scenarios, SharePoint products is one of several applications that must be recovered in the event of a data center shutdown that qualifies as a disaster. For this reason we have not included information about disaster recovery planning but focus on options for making sure that you can recover your SharePoint Server 2016 farm at another location.Regardless of the type and scale of a disaster, recovery involves the use of a standby data center that you can recover the farm to. +## Standby data center recovery options + + +Standby data centers are required for scenarios where local redundant systems and backups cannot recover from the outage at the primary data center. The time and immediate effort to get a replacement farm up and running in a different location is often known as a hot, warm, or cold standby. Our definitions for these farm recovery data centers are as follows: +- **Cold standby**. A secondary data center that can provide availability within hours or days. + + +- **Warm standby**. A secondary data center that can provide availability within minutes or hours. + + +- **Hot standby**. A secondary data center that can provide availability within seconds or minutes. + + +Each of these standby data centers has specific characteristics and requirements, and also an associated cost to operate and maintain. +- Cold standby disaster recovery strategy: A business ships backups to support bare metal recovery to local and regional offsite storage regularly, and has contracts in place for emergency server rentals in another region. + + Pros: + + + + + +> Often the cheapest option to maintain, operationally. + + + + + + +> Often an expensive option to recover, because it requires that physical servers be configured correctly after a disaster has occurred. + + + + Cons: The slowest option to recover. + + +- Warm standby disaster recovery strategy: A business ships backups or virtual machine images to local and regional disaster recovery farms. + + Pros: Often fairly inexpensive to recover, because a virtual server farm can require little configuration upon recovery. + + Cons: Can be very expensive and time-consuming to maintain. + + +- Hot standby disaster recovery strategy: A business runs multiple data centers, but serves content and services through only one data center. + + Pros: Often fairly fast to recover. + + Cons: Can be very expensive to configure and maintain. + + + +> [!IMPORTANT:] + + + + + + +## Cold standby recovery + +In a cold standby disaster recovery scenario, you recover by setting up a new farm in a new location, (preferably by using a scripted deployment), and restoring backups. Or, you can recover by restoring the farm using a backup solution such as System Center 2016 - Data Protection Manager (DPM) or System Center 2012 - Data Protection Manager (DPM). System Center Data Protection Manager protects your data at the computer operating system level and lets you restore each server individually. This article does not contain detailed instructions for how to create and recover in cold standby scenarios. For more information, see: +- [Overview of backup and recovery in SharePoint Server](html/overview-of-backup-and-recovery-in-sharepoint-server.md) + + +- [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md) + + + +## Warm standby recovery + +In a warm standby disaster recovery scenario, you create a warm standby environment by creating a duplicate farm at the alternate data center and ensure that it is updated regularly by using full and incremental backups of the primary farm. **Virtual warm standby environments**Virtualization provides a workable and cost effective option for a warm standby recovery solution. You can use Hyper-V as an in-house solution or Azure as a hosted solution to provide necessary infrastructure for recovery.You can create virtual images of the production servers and ship these images to the standby data center. By using the virtual standby solution, you have to make sure that the virtual images are created often enough to provide the level of farm configuration and content freshness that you must have for recovering the farm. At the secondary location, you must have an environment available in which you can easily configure and connect the images to re-create your farm environment. For more information, see [Deploying SharePoint Server 2016 with SQL Server AlwaysOn Availability Groups in Azure](html/deploying-sharepoint-server-2016-with-sql-server-alwayson-availability-groups-in.md) +## Hot standby recovery + +In a hot standby disaster recovery scenario, you set up a failover farm in the standby data center so that it can assume production operations almost immediately after the primary farm goes offline. An environment that has a separate failover farm has the following characteristics: +- A separate configuration database and the SharePoint Central Administration website content database must be maintained on the failover farm. + + +- All customizations must be deployed on both farms. + + > [!TIP:] + +- Operating system, SQL Server and SharePoint Server software updates must be applied to both farms, to maintain a consistent configuration across both farms. + + +- You can copy SharePoint Server content databases to the failover farm by using asynchronous mirroring, asynchronous commit on an availability group replica, or log-shipping. + + > [!NOTE:] + +- Service applications vary in whether they can be log-shipped to a farm. For more information, see [Service application redundancy across data centers](#ServiceAppRedundancy) later in this article. + + +The hot standby farm topology can be repeated across more than one data center, as long as you configure SQL Server log shipping to one or more additional data centers. +> [!IMPORTANT:] + + + + + + +## Service application redundancy + + +To provide availability across data centers for service applications, we recommend that for the services that can be run cross-farm, you run a separate services farm that can be accessed from both the primary and the secondary data centers.For services that cannot be run cross-farm, and to provide availability for the services farm itself, the strategy for providing redundancy across data centers for a service application varies. The strategy employed depends on whether: +- There is business value in running the service application in the disaster recovery farm when it is not being used. + + +- The databases associated with the service application can be log-shipped, asynchronously mirrored, or replicated using asynchronous commit. + + +- The service application can run against read-only databases. + + +Review the [Supported high availability and disaster recovery options for SharePoint databases](html/supported-high-availability-and-disaster-recovery-options-for-sharepoint-databas.md) article before designing a disaster recovery solution that uses a warm or hot standby data center. +## System requirements for recovery + + +In an ideal scenario, the failover components and systems match the primary components and systems in all ways: platform, hardware, and number of servers. At a minimum, the failover environment must be able to handle the traffic that you expect during a failover. Keep in mind that only a subset of users may have to be served by the failover site. The systems must match in at least the following: +- Operating system version and all updates + + +- SQL Server versions and all updates + + +- SharePoint Server versions and all updates + + +In addition to the previous requirements, farm recovery time will also be affected by availability of facilities and infrastructure components. Make sure that the following requirements are met: +- Power, cooling, network, directory, and SMTP are fully redundant + + +- Choose a switching mechanism; whether DNS or hardware load balancing, that meets your needs. + + + +# See also + +#### + + [High availability and disaster recovery concepts in SharePoint Server](html/high-availability-and-disaster-recovery-concepts-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/co-authoring-administration-in-sharepoint-2013.md b/SharePoint/co-authoring-administration-in-sharepoint-2013.md new file mode 100644 index 0000000000..e707e551ff --- /dev/null +++ b/SharePoint/co-authoring-administration-in-sharepoint-2013.md @@ -0,0 +1,33 @@ +--- +title: Co-authoring administration in SharePoint 2013 +ms.prod: SHAREPOINT +ms.assetid: 0490bf49-4e23-475f-bf37-2000dca31845 +--- + + +# Co-authoring administration in SharePoint 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013* * **Topic Last Modified:** 2017-07-19* **Summary:** Find TechNet articles that will help you learn how to configure co-authoring for SharePoint Server 2013.Co-authoring simplifies collaboration by enabling multiple users to work productively on the same document without intruding on one another's work or locking one another out. By default, co-authoring functionality is enabled in SharePoint Server 2013 and requires no additional steps. The articles that are listed here describe tasks that administrators can use if they want to configure co-authoring for their organizations or to disable it, either on the server side by using server properties, or on the client side by using Group Policy. + + + +![Office 2013 logo](images/) + + + +The following table lists and describes articles about co-authoring in SharePoint Server 2013. +### Articles about co-authoring in SharePoint 2013 + +ArticleDescription [Overview of co-authoring in SharePoint 2013](html/overview-of-co-authoring-in-sharepoint-2013.md)
Provides information about co-authoring and the permissions and software versions that are required for co-authoring in SharePoint 2013 and SharePoint Online.
[Configure versioning for co-authoring in SharePoint 2013](html/configure-versioning-for-co-authoring-in-sharepoint-2013.md)
Provides information about how to configure SharePoint document library versioning settings to support co-authoring.
[Configure the co-authoring versioning period in SharePoint 2013](html/configure-the-co-authoring-versioning-period-in-sharepoint-2013.md)
Provides information about how to specify how often SharePoint Server 2013 stores a version of a document that is being edited.
[Configure the maximum number of co-authoring authors in SharePoint 2013](html/configure-the-maximum-number-of-co-authoring-authors-in-sharepoint-2013.md)
Provides information about how to limit the number of users who can co-author a Word document or PowerPoint presentation at the same time.
[Disable co-authoring in SharePoint 2013](html/disable-co-authoring-in-sharepoint-2013.md)
Provides information about how to disable co-authoring functionality in SharePoint Server 2013 by using Group Policy or by using Microsoft PowerShell.
+# See also + +#### + + [Overview of co-authoring in SharePoint 2013](html/overview-of-co-authoring-in-sharepoint-2013.md) + + + + + + + + diff --git a/SharePoint/configure-a-business-data-connectivity-service-application-in-sharepoint-server.md b/SharePoint/configure-a-business-data-connectivity-service-application-in-sharepoint-server.md new file mode 100644 index 0000000000..03a91e0f58 --- /dev/null +++ b/SharePoint/configure-a-business-data-connectivity-service-application-in-sharepoint-server.md @@ -0,0 +1,107 @@ +--- +title: Configure a Business Data Connectivity service application in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 41ec2552-43cd-471a-ba22-1962297758c0 +--- + + +# Configure a Business Data Connectivity service application in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Learn how to create a Microsoft Business Connectivity Services service application in SharePoint Server 2013 and SharePoint Server 2016.Microsoft Business Connectivity Services is a SharePoint Server service application. You must create it if it was not created during your farms initial configuration. +## Configure the Business Connectivity Services application pool account + + +The application pool for the Business Connectivity Services service application requires a SharePoint Server managed account (generally an Active Directory account) to run. This account must have access to the content databases containing the sites where Business Connectivity Services will be used.If you run the service application using the same application pool account as the web application where the content databases are located, this required database access is configured automatically. However, we recommend that you use a different account for the Business Connectivity Services application pool, especially in a large or complex farm. This allows for greater control over data and resource access.If you choose to use the same managed account for Business Connectivity Services as is being used for the web application, you can skip the procedures in this section. If you choose to create a new managed account, you must do the following: +1. Register a managed account in SharePoint Server. (You will need an Active Directory user account for this step. Have your Active Directory administrator create it.) + + +2. Grant access for this account to the content databases that contain the sites where Business Connectivity Services will be used. This process includes running a Microsoft PowerShell script from the SharePoint 2016 Management Shell. + + +The first step is to register a managed account. Use the following procedure to register the Active Directory account that you want to use for the Business Connectivity Services application pool. **To register a managed account** +1. In the SharePoint Server Central Administration Web site, click **Security**. + + +2. In the **General Security** section, click **Configure managed accounts**. + + +3. Click **Register Managed Account**. + + +4. In the **Service account credentials** section, type the user name and password for the Active Directory account that you want to register. + + +5. Optionally, if the account password is set to expire after a certain length of time, configure the automatic password change settings to have SharePoint Server change the password. + + +6. Click **OK**. + + +Once you have registered the managed account, you must grant that account access to the content databases containing the sites where you'll use Business Connectivity Services. Use the following procedure to grant database access to the account. Follow this procedure for each web application that contains a content database where you plan to use Business Connectivity Services. **To grant content database access to an account** +1. Open the **SharePoint 2016 Management Shell** as administrator. + + +2. At the Microsoft PowerShell command prompt, type the following, pressing Enter after each line: + + ``` + +$w = Get-SPWebApplication -identity +$w.GrantAccessToProcessIdentity("") + ``` + +Once you have finished granting content database access to the managed account, the next step is to create a Business Connectivity Services service application. +## Create a Business Data Connectivity Services service application + + +If you're using SharePoint Server 2013, you must start the Business Data Connectivity service on at least one server in your farm. (If you're using SharePoint Server 2016, service provisioning is handled automatically by MinRole.) **Start the Business Data Connectivity service (SharePoint Server 2013 only)** +1. Open the SharePoint Central Administration website for the server farm that contains your BCS solution. + + +2. On the Quick Launch, click **System Settings**. + + +3. On the **System Settings** page, under **Servers**, click **Manage services on server**. + + +4. Check the value in the **Server** field. If the server name shown there is not the server that you want running the **Business Data Connectivity Service** on, click on the down arrow, click **Change Server** and select the correct server. + + +5. If necessary, next to Business Data Connectivity Service, under the **Action** column, click **Start**. + + +Use the following procedure to create a Business Connectivity Services service application. **To create a Business Data Connectivity Services service application** +1. Open the SharePoint Central Administration website for with a farm administrator account. + + +2. Under **Application Management**, choose **Manage service applications**. + + +3. Click **New** and then click **Business Data Connectivity Service**. + + +4. Configure the setting in the **Create New Business Data Connectivity Service Application** configuration page as follows: + +1. In the **Service Application Name** box type a name for the service application. + + +2. In the **Database** area, leave the prepopulated values for **Database Server**, **Database Name**, and **Database authentication**, which is **Windows authentication (recommended)** unless you have specific design needs to change them. + + +3. If you have SQL Server database mirroring configured and you want to include the Business Data Connectivity Service database in mirroring, provide the name of the failover database server in the **Failover Database Server** box. + + +4. Type a name for a new application pool in the **Application pool name** box. + + +5. Select the managed account that you registered from the drop down list. + + +5. Click **OK** to create the new Business Data Connectivity Service Application and click **OK** again. + + +6. Select the row that the **Business Data Connectivity Service Application** is in, not the proxy row. + + +7. Click **Administrators** in the **Operations** area and add any accounts that you want to be able to administer the Business Data Connectivity service application granting them full control. When these individuals open Central Administration they will be able to administer the Business Data Connectivity service application. + + + diff --git a/SharePoint/configure-a-hybrid-solution-for-sharepoint-server.md b/SharePoint/configure-a-hybrid-solution-for-sharepoint-server.md new file mode 100644 index 0000000000..ba168de51c --- /dev/null +++ b/SharePoint/configure-a-hybrid-solution-for-sharepoint-server.md @@ -0,0 +1,17 @@ +--- +title: Configure a hybrid solution for SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: ad39b1b5-a73b-4a48-af5e-4f032ea52e1d +--- + + +# Configure a hybrid solution for SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-22* **Summary:** Configure a SharePoint hybrid solution between SharePoint Server and SharePoint Online in Office 365. + + + +![Configure a SharePoint hybrid solution](images/) + + + +Configuring and deploying one or more SharePoint hybrid solutions takes place in the final phase of the SharePoint hybrid environment deployment process and is the ultimate reason for configuring a SharePoint hybrid environment.Be sure you're [following a roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md) when you read the articles in this section. diff --git a/SharePoint/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md b/SharePoint/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md new file mode 100644 index 0000000000..10b0eee53e --- /dev/null +++ b/SharePoint/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md @@ -0,0 +1,125 @@ +--- +title: Configure a reverse proxy device for SharePoint Server hybrid +ms.prod: SHAREPOINT +ms.assetid: 1780ec27-19f8-4d77-b787-8abc23921258 +--- + + +# Configure a reverse proxy device for SharePoint Server hybrid + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-22* **Summary:** Learn about supported reverse proxy devices for SharePoint Server hybrid deployments. **This article is part of a roadmap of procedures for configuring SharePoint hybrid solutions. Be sure you're [following a roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md) when you do the procedures in this article.**This topic provides an overview of the role of reverse proxy devices in a SharePoint Server hybrid deployment and links to device-specific configuration guidance.In this article: +- [The role of a reverse proxy in a SharePoint Server 2013 hybrid deployment](#role) + + +- [General reverse proxy requirements](#requirements) + + +- [Supported reverse proxy devices](#devices) + + + +## The role of a reverse proxy in a SharePoint Server hybrid deployment + + +SharePoint Server and SharePoint Online can be configured in a hybrid configuration to securely combine search results and external data from Microsoft Business Connectivity Services. Reverse proxy devices play a role in the secure configuration of a hybrid SharePoint Server deployment when inbound traffic from SharePoint Online needs to be relayed to your on-premises SharePoint Server farm. For example, if a federated user uses a SharePoint Online search portal that is configured to return hybrid search results, a reverse proxy device intercepts and pre-authenticates the request for on-premises SharePoint Server content and then relays it to SharePoint Server. The reverse proxy device in a hybrid topology provides a secure endpoint for inbound traffic using SSL encryption and client certificate authentication. +## How inbound connectivity works + +The following diagrams show how a reverse proxy device is used for inbound connectivity.With an inbound search solution, only the SharePoint Online site has search results from both locations. **Inbound connectivity** + + + +![A graphic of an inbound proxy.](images/) + + + +In the example below, a federated user on the Internet uses the SharePoint Online search portal to search for content in both SharePoint Online and her company’s on-premises SharePoint Server server. **A federated user on the Internet searches for content that’s located on her company’s on-premises server.** + + + +![This graphic explains how extranet users access files through TMG.](images/) + + + +The following list describes the steps shown in the preceding picture. + + + + +1. From the Internet, a federated user browses to her SharePoint Online site. + + +2. SharePoint Online queries the search index in SharePoint Online and also sends the search query to the external URL of the on-premises SharePoint farm which resolves to the external endpoint of the reverse proxy device. + + +3. The reverse proxy device pre-authenticates the request using the Secure Channel SSL certificate and relays the request to the URL of the primary web application. + + +4. The SharePoint farm service account queries the on-premises search index and security trims the search results in the context of the user who sent the search request. + + +5. Security trimmed search results are returned to SharePoint Online and displayed on the search results page. This result set includes search results from the SharePoint Online search index and search results from the search index of the SharePoint Server farm. + + + + +> [!NOTE:] + + + + + +For a more detailed description of this process, that shows how certificates are used and authentication and authorization work in this topology, see [Poster: SharePoint 2013 Hybrid Topology: Certificate, Authentication, and Authorization flow](https://go.microsoft.com/fwlink/?LinkId=392320). +## General reverse proxy requirements + + +In a hybrid SharePoint Server scenario, the reverse proxy must be able to: +- Support client certificate authentication with a wildcard or SAN SSL certificate. + + +- Support pass-through authentication for OAuth 2.0, including unlimited OAuth bearer token transactions. + + +- Accept unsolicited inbound traffic on **TCP port 443** (HTTPS). + + > [!TIP:] + +- Bind a wildcard or SAN SSL certificate to a published endpoint. + + +- Relay traffic to an on-premises SharePoint Server farm or load balancer without rewriting any packet headers. + + + +## Supported reverse proxy devices + + +The table below lists the currently supported reverse proxy devices for SharePoint Server hybrid deployments. This list will be updated as new devices are tested for supportability. Follow the steps in the configuration article for the reverse proxy device that you want to use. When you've completed configuring the reverse proxy device, return to your [roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md). +### + +Supported reverse proxy devices Configuration article Additional information Windows Server 2012 R2 with Web Application Proxy (WA-P)
[Configure Web Application Proxy for a hybrid environment](html/configure-web-application-proxy-for-a-hybrid-environment.md)
Web Application Proxy (WA-P) is a Remote Access service in Windows Server 2012 R2 that publishes web applications that users can interact with from many devices.
+> [!IMPORTANT:] + + + + + +Forefront Threat Management Gateway (TMG) 2010
[Configure Forefront TMG for a hybrid environment](html/configure-forefront-tmg-for-a-hybrid-environment.md)
Forefront TMG 2010 is a comprehensive, secure, web gateway solution that provides secure reverse proxy functionality.
+> [!NOTE:] + + + + + +F5 BIG-IP
[Enabling SharePoint 2013 Hybrid Search with the BIG-IP](https://devcentral.f5.com/articles/enabling-sharepoint-2013-hybrid-search-with-the-big-ip)
External content managed by F5 Networks.
Citrix NetScaler
[Citrix NetScaler and Microsoft SharePoint 2013 Hybrid Deployment Guide](https://www.citrix.com/content/dam/citrix/en_us/documents/products-solutions/deployment-guide-netscaler-office-365-en.pdf)
External content managed by Citrix.
+# See also + +#### + + [Hybrid for SharePoint Server](html/hybrid-for-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-adventureworks-for-business-intelligence-solutions.md b/SharePoint/configure-adventureworks-for-business-intelligence-solutions.md new file mode 100644 index 0000000000..68a9554764 --- /dev/null +++ b/SharePoint/configure-adventureworks-for-business-intelligence-solutions.md @@ -0,0 +1,430 @@ +--- +title: Configure AdventureWorks for Business Intelligence solutions +ms.prod: SHAREPOINT +ms.assetid: 5e44cf6c-2271-4ff1-af7f-4e73849ffdf6 +--- + + +# Configure AdventureWorks for Business Intelligence solutions + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-07* **Summary:** Configure the AdventureWorks sample data for use with Excel, Excel Services in SharePoint Server 2013, and PerformancePoint Services business intelligence scenarios.The AdventureWorks sample data set provides a sample database, data warehouse, and OLAP cube. The subsequent articles in this section make use of this sample data to demonstrate Business Intelligence capabilities in Excel, Excel Services in SharePoint Server 2013, and PerformancePoint Services. This article describes how to install and configure the AdventureWorks sample data set and configure a Business Intelligence Center on your SharePoint Server 2013 farm. +> [!IMPORTANT:] + + + + + +In this article: +- [Scenario overview](#overview) + + +- [Before you begin](#begin) + + +- [Video demonstration](#VideoDemonstration) + + +- [Install the AdventureWorks sample data](#InstallAdventureWorks) + + +- [Create a Business Intelligence Center](#CreateABICenter) + + +- [Scenarios that use this configuration](#Scenarios) + + + +## Scenario overview + + +Installing the AdventureWorks sample data set consists of downloading the sample data, attaching the sample databases in SQL Server Management Studio, and deploying the sample OLAP cube using the SQL Server Data Tools.Creating a Business Intelligence Center consists of creating a new site collection with the Business Intelligence Center template using the SharePoint Central Administration website.The procedures for completing both of these tasks, plus procedures for configuring the required user access and permissions are included in this article. +## Before you begin + + +Before starting, read the following information about permissions and software requirements: +- To deploy the AdventureWorks sample data, you must be a SQL Server and Analysis Services administrator. + + +- To create a Business Intelligence Center, you must be a farm administrator on the SharePoint Server 2013 farm. + + +The subsequent articles make use of Excel Services and PerformancePoint Services. It is assumed that these are configured on your farm. For information about deploying Excel Services, see [Overview of Excel Services in SharePoint Server 2013](html/overview-of-excel-services-in-sharepoint-server-2013.md) and **Configure Excel Online administrative settings**. For information about deploying PerformancePoint Services, see [PerformancePoint Services administration](html/performancepoint-services-administration.md).When using Excel Services or PerformancePoint Services, user access can be provided using Windows Authentication with Kerberos delegation, the Secure Store Service, or, with OLAP data sources, the EffectiveUserName feature. It is assumed that one or more of these options are configured on your farm. For information about configuring Secure Store, see [Plan the Secure Store Service in SharePoint Server](html/plan-the-secure-store-service-in-sharepoint-server.md) and [Configure the Secure Store Service in SharePoint Server](html/configure-the-secure-store-service-in-sharepoint-server.md). For information about configuring the EffectiveUserName feature for OLAP data sources, see [Use Analysis Services EffectiveUserName in SharePoint Server](html/use-analysis-services-effectiveusername-in-sharepoint-server.md). +## Video demonstration + + +This video shows the steps involved in installing and configuring the AdventureWorks sample data set, as described in this article. **Video: Configure AdventureWorks for Business Intelligence solutions** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + +## Install the AdventureWorks sample data + + +The AdventureWorks sample data consists of: +- The AdventureWorks2012 database + + +- The AdventureWorksDW2012 database + + +- The AdventureWorksDW2012Multidimensional-EE OLAP cube + + +The following sections describe how to deploy each of these data sets. +## Deploy the AdventureWorks sample databases + + +Each of the two AdventureWorks sample databases must be downloaded separately.Use the following procedure to download and deploy the AdventureWorks2012 database. **To deploy the AdventureWorks2012 database** +1. Download [AdventureWorks2012_Data.mdf](https://msftdbprodsamples.codeplex.com/downloads/get/165399). + + > [!NOTE:] + +2. Copy AdventureWorks2012_Data.mdf to your default database directory (normally \\Program Files\\Microsoft SQL Server\\MSSQL11.MSSQLSERVER\\MSSQL\\DATA) or other location as designated by your database administrator. + + +3. Open SQL Server Management Studio. + + +4. Connect to the database engine. + + +5. Right-click **Databases**, and then click **Attach**. + + +6. On the **Attach Databases** dialog box, click **Add**. + + +7. Navigate to the location where you copied AdventureWorks2012_Data.mdf, select the file, and then click **OK**. + + +8. Under **"AdventureWorks2012" database details**, select the row where **File Type** is **Log**. + + +9. Click **Remove**. + + +10. Click **OK**. + + +Use the following procedure to download and deploy the AdventureWorksDW2012 data warehouse database. **To deploy the AdventureWorksDW2012 data warehouse** +1. Download [AdventureWorksDW2012_Data.mdf](https://msftdbprodsamples.codeplex.com/downloads/get/165405). + + > [!NOTE:] + +2. Copy AdventureWorksDW2012_Data.mdf to your default database directory (normally \\Program Files\\Microsoft SQL Server\\MSSQL11.MSSQLSERVER\\MSSQL\\DATA) or other location as designated by your database administrator. + + +3. Open SQL Server Management Studio. + + +4. Connect to the database engine. + + +5. Right-click **Databases**, and then click **Attach**. + + +6. On the **Attach Databases** dialog box, click **Add**. + + +7. Navigate to the location where you copied AdventureWorksDW2012_Data.mdf, select the file, and then click **OK**. + + +8. Under **"AdventureWorksDW2012" database details**, select the row where **File Type** is **Log**. + + +9. Click **Remove**. + + +10. Click **OK**. + + + +## Deploy the AdventureWorks sample OLAP cube + + +The following requirements must be met before you can deploy the sample OLAP cube. Procedures are provided to accomplish each of these tasks if they have not already been completed in your environment. +- The AdventureWorksDW2012 database must be deployed on the SQL Server database engine as covered in the section above. + + +- The SQL Server Data Tools must be installed as part of your SQL Server and Analysis Services deployment. + + > [!NOTE:] + +- The account running the Analysis Services service must have a login on the SQL Server database engine. + + +If you have not deployed the AdventureWorksDW2012 database, do so now using the procedures under [Business Connectivity Service](html/business-connectivity-service.md) before proceeding with the procedures in this section.If you have not deployed the SQL Server Data Tools, use the following procedure to deploy them. +> [!NOTE:] + + + + + + **To install the SQL Server Data Tools** +1. On the SQL Server 2012 DVD, run setup.exe. + + +2. In the SQL Server Installation Center, on the left pane, click **Installation**. + + +3. In the right pane, click **New SQL Server stand-alone installation or add features to an existing installation**. + + +4. On the Setup Support Rules page, click **OK**. + + +5. On the Product Updates page click **Next**. + + +6. On the Setup Support Rules page, click **Next**. + + +7. On the Installation Type page, select the **Add features to an existing instance of SQL Server 2012** option, and select the instance where you want to install the SQL Server Data Tools. + + +8. Click **Next**. + + +9. On the Feature Selection page, select the **SQL Server Data Tools** check box, and then click **Next**. + + +10. On the Installation Rules page, click **Next**. + + +11. On the Disk Space Requirements page, click **Next**. + + +12. On the Error Reporting page, click **Next**. + + +13. On the Installation Configuration Rules page, click **Next**. + + +14. On the Ready to Install page, click **Install**. + + +15. When the installation completes, click **Close**. + + +Once the SQL Server Data Tools have been installed, the next step is to create a login for the account running Analysis Services if one does not already exist.If you do not know what account is running Analysis Services, use the following procedure to determine the account. **To determine the Analysis Services service account** +1. On the computer running Analysis Services, click **Start**, click **All Programs**, click **Microsoft SQL Server 2012**, click **Configuration Tools**, and then click **SQL Server Configuration Manager**. + + +2. In the left pane, click **SQL Server Services**. + + +3. In the right pane, find the instance of Analysis Services that you will be using, and note the account listed in the **Log On As** column. This is the account for which you must add a logon in SQL Server. + + +If you do not already have a SQL Server login for the account running Analysis Services, use the following procedure to create one. **To add a login for the Analysis Services service account** +1. Open SQL Server Management Studio. + + +2. Connect to the database engine. + + +3. Expand **Security**. + + +4. Right-click **Logins** and click **New Login**. + + +5. In the **Login name** text box, type the name of the account running the Analysis Services service. + + +6. Click **OK**. + + > [!NOTE:] + +Once you have configured the login for the Analysis Services service account, the next step is to download and deploy the AdventureWorks OLAP cube. Use the following procedure to download and deploy the cube. **To configure the AdventureWorks OLAP cube** +1. Download [AdventureWorks Multidimensional Models SQL Server 2012.zip](https://msftdbprodsamples.codeplex.com/downloads/get/258486) + + > [!NOTE:] + +2. Unzip the file to a location on the computer running Analysis Services. + + +3. In the **Enterprise** folder, double-click AdventureWorksDW2012Multidimensional-EE.sln. + + +4. If the **Choose Default Environment Settings** dialog box appears, choose the **Business Intelligence Settings** option, and then click **Start Visual Studio**. + + +5. In Visual Studio, at the top of the **Solution Explorer** window, right click **AdventureWorksDW2012Multidimensional-EE** and click **Deploy**. + + +6. Close Visual Studio without saving changes. + + + +## Configure AdventureWorks user access + + +Once the databases and the cube have been deployed, you must grant your users access to them. The following access is required: +- Users who will be creating reports or dashboards in the subsequent articles in this section must have **db_datareader** access to the AdventureWorks databases and **Read** access to the AdventureWorks cube. + + +- If you are using the unattended service account with Excel Services or PerformancePoint Services, that account must have **db_datareader** access to the AdventureWorks databases and **Read** access to the AdventureWorks cube. + + +- If you are using Secure Store to refresh data in Excel Services or PerformancePoint Services, the target application credentials must have **db_datareader** access to the AdventureWorks databases and **Read** access to the AdventureWorks cube. + + +We recommend that you use an Active Directory group containing the users to whom you want to grant access.Use the following procedure to grant access to the AdventureWorks databases. If you choose to grant access to each user individually instead of using an Active Directory group, you must create a separate login for each user. **To grant access to the AdventureWorks databases** +1. In SQL Server Management Studio, connect to the database engine. + + +2. Expand **Security**. + + +3. Right-click **Logins**, and then click **New Login**. + + +4. Click **Search**. + + +5. If you are using an Active Directory group, click **Object Types**, select the **Groups** check box, and then click **OK**. + + +6. On the **Select User or Group** dialog box, type the name of the Active Directory group or user to whom you want to grant database access, and then click **OK**. + + +7. Under **Select a page**, click **User Mapping**. + + +8. Select the **Map** check box for **AdventureWorks2012**, and then select the **db_datareader** database role membership check box. + + +9. Select the **Map** check box for **AdventureWorksDW2012**, and then select the **db_datareader** database role membership check box. + + +10. Click **OK**. + + +Use the following procedure to grant access to the AdventureWorks OLAP cube. **To grant access to the AdventureWorks OLAP cube** +1. In SQL Server Management Studio, connect to Analysis Services. + + +2. Expand **Databases**, and then expand **AdventureWorksDW2012Multidimensional-EE**. + + > [!NOTE:] + +3. Right-click **Roles** and then click **New Role**. + + +4. In the **Role name** text box, type a name for the role. + + +5. In the **Select a page** pane, click **Membership**. + + +6. Click **Add**. + + +7. Type the name of the users or Active Directory group to whom you want to grant cube access. + + > [!NOTE:] + +8. On the **Select Users or Groups** dialog box, click **OK**. + + +9. In the **Select a page** pane, click **Cubes**. + + +10. In the right pane, in the **Access** column, click select **Read** from the dropdown list for **Adventure Works** and **Mined Customers**. + + +11. In the right pane, in the **Local Cube/Drillthrough Access** column, click select **Drillthrough** from the dropdown list for **Adventure Works** and **Mined Customers**. + + +12. Click **OK**. + + + +## Create a Business Intelligence Center + + +The subsequent articles in this section rely on a Business Intelligence Center site being present. If you have an existing Business Intelligence Center, you can use it. However, we recommend creating a new Business Intelligence Center that is not part of your production environment.Use the following procedure to create a Business Intelligence Center. **To create a Business Intelligence Center** +1. On the SharePoint Central Administration website, under **Application Management**, click **Create site collections**. + + +2. On the Create Site Collection page: + +1. Type a title in the **Title** text box. + + +2. Type the URL that you want to use in the **URL** text box. + + +3. Under **Select a template**, choose the **Enterprise** tab, and then select **Business Intelligence Center**. + + +4. In the **Primary Site Collection Administrator** section, type a name for the primary site collection administrator in the **User name** text box. + + +5. Optionally, type a name for the secondary site collection administrator. + + +6. Optionally, select a quota template. + + +7. Click **OK**. + + + +## Configure BI Center access + + +The following table describes the permissions available in a Business Intelligence Center. +### Business Intelligence Center permissions + +Account Permissions Visitors
Read
Read permissions enable users to view information in the Business Intelligence Center.
Members
Contribute
Contribute permissions enable users to view and create items, such as reports, and save them to this site.
Designers
Design
Design permissions enable users to view, create, and publish items that include dashboards.
Owners
Full Control
Full Control permissions enable users to view, create, and publish dashboard content, and to view or edit user permissions
For the scenarios described in the subsequent articles in this section, users will need the following permissions. +- Users publishing workbooks to the Business Intelligence Center from Excel require Contribute permissions and must be added to the Members group. + + +- Users publishing dashboards from PerformancePoint Dashboard Designer require Design permissions and must be added to the Designers group. + + +- Users who are only viewing reports or dashboards in the Business Intelligence Center but not publishing only require Read permission and can be added to the Visitors group. + + +Use the following procedure to configure permissions for the Business Intelligence Center. **To set permissions in the Business Intelligence Center** +1. In the Business Intelligence Center, click **Share**. + + +2. Type the names of the users or groups to whom you want to grant access. + + +3. Click **Show Options**. + + +4. On the **Select a group or permission level** dropdown list, select the permission level that you want. + + +5. Click **Share**. + + + +## Scenarios that use this configuration + + +The following scenarios use the AdventureWorks sample data and Business Intelligence Center as configured in this article: + + + + +> [Create an Excel Services dashboard using SQL Server Analysis Services data](html/create-an-excel-services-dashboard-using-sql-server-analysis-services-data.md) + + + diff --git a/SharePoint/configure-an-environment-for-apps-for-sharepoint-server.md b/SharePoint/configure-an-environment-for-apps-for-sharepoint-server.md new file mode 100644 index 0000000000..45e1cf0e3c --- /dev/null +++ b/SharePoint/configure-an-environment-for-apps-for-sharepoint-server.md @@ -0,0 +1,252 @@ +--- +title: Configure an environment for apps for SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: bf94ede1-79cc-4016-99f3-a1eef244fdf3 +--- + + +# Configure an environment for apps for SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-27* **Summary:** Configure domain names, service applications, and URLs for apps for SharePoint Server 2016 and SharePoint Server 2013.To enable users to install and use apps for SharePoint in their sites, you must configure your environment to support them. This article describes how to configure your environment to support apps. Use the [Plan for apps for SharePoint Server](html/plan-for-apps-for-sharepoint-server.md) article to review options and determine the values to use for configuration settings in this article. +## Before you begin + + + +- You must purchase a domain name from a domain name provider for your apps, for example, ContosoApps.com. + + +- You must be a member of the Farm Administrators group to perform the steps in this article. For some steps, you must also be a domain administrator. + + +- If you have a multi-tenant environment, you need to do some steps by using Microsoft PowerShell. Make sure you have **permissions to administer SharePoint Server using Windows PowerShell**. + + + +## Configure the domain names in DNS + + +You must configure a new domain in Domain Name Services (DNS) to host the apps. To help improve security, the domain name should not be a subdomain of the domain that hosts the SharePoint Server sites. For example, if the SharePoint Server sites are at Contoso.com, consider ContosoApps.com instead of App.Contoso.com as the domain name. When an app is provisioned, it provisions a unique DNS domain name (for example, Apps- *12345678ABCDEF* .ContosoApps.com, where *12345678ABCDEF* is a unique identifier for the app). You need a wildcard Canonical Name (CNAME) entry for your DNS domain to support these unique names.Depending on your configuration (for example, if you are using WINS forward lookup), you might have to create a new forward lookup zone first, or you can start with a wildcard CNAME entry in the same zone as the SharePoint Server site domain. In the following procedures, you create a forward lookup zone, and then create a wildcard alias record for the DNS domain name that allows for individual apps to create unique domain names within your app domain. In these procedures, we use DNS Manager for Windows Server 2012 R2. If you have a different type of DNS server, follow the procedures in the documentation for that server type. **To create a forward lookup zone for the app domain name** +1. Verify that the user account that performs this procedure is a domain administrator on the domain controller. + + +2. Click **Start**, point to **Administrative Tools**, and then click **DNS**. + + +3. In DNS Manager, right-click **Forward Lookup Zones**, and then click **New Zone…**. + + +4. In the New Zone Wizard, click **Next**. + + +5. In the **Zone Type** page, accept the default of **Primary zone**, and then click **Next**. + + +6. In the **Active Directory Zone Replication Scope** page, select the appropriate replication method for your environment (the default is **To all DNS servers in this domain** ), and then click **Next**. + + +7. In the **Zone Name** page, in the **Zone name** box type the name for your new app domain name (for example, ContosoApps.com), and then click **Next**. + + +8. On the **Dynamic Update** page, select the appropriate type of dynamic updates for your environment (the default is **Do not allow dynamic updates** ), and then click **Next**. + + +9. On the **Completing the New Zone Wizard** page, review the settings, and then click **Finish**. + + +You have now created a forward lookup zone (and a domain name) to use for apps in your environment. **To create a wildcard Alias (CNAME) record for the new domain name** +1. Verify that the user account that performs this procedure is a domain administrator on the domain controller. + + +2. In DNS Manager, under Forward Lookup Zones, right-click the new app domain name, and then click **New Alias (CNAME)**. + + +3. In the New Resource Record dialog box, in the **Alias name (uses parent domain if left blank)** box, type *****. + + The Fully qualified domain name (FQDN) box displays *. followed by the domain name that you created for apps. For example, *.ContosoApps.com or *.Contoso-Apps.com. + + +4. Next to the **Fully qualified domain name (FQDN) for target host** box, type the FQDN of the server that hosts the SharePoint Server sites. + + For example, SharePoint.Contoso.com. + + Or: + +1. Next to the **Fully qualified domain name (FQDN) for target host** box, click **Browse** and navigate to the Forward Lookup Zone for the domain that hosts the SharePoint Server sites. + + For example, Contoso.com. + + +2. And then navigate to the record that points to the server that hosts the SharePoint Server site. + + For example, SharePoint. + + + + **New Resource Record dialog box shows the wildcard alias for the app domain and the FQDN of the server that hosts the SharePoint sites.** + + ![Create a CNAME alias for the app domain](images/) + + + +5. Click **OK**. + + +You can verify the new domain name and alias by pinging them. **To verify the new domain name** +1. Verify that the user account that is performing this procedure is a domain administrator on the domain controller. + + +2. Click **Start**, and then click **Command Prompt**. + + +3. At the command prompt, type **ping** followed by a subdomain of the domain that you created, and then press **ENTER**. + + For example, **ping Apps-12345678ABCDEF.contosoapps.com** + + If the ping command returns the correct IP address, then your wildcard for the domain name was configured successfully. + + + +## Create a new wildcard SSL certificate + + +If you are using Secure Sockets Layer (SSL) for the SharePoint Server sites in your environment, or if you use any apps that use data external to the SharePoint Server sites, you should use SSL for your apps. To use SSL, you create an SSL certificate for your app domain (for example, ContosoApps.com). The domain should be added in the form of a wildcard (for example, *.ContosoApps.com). You need a wildcard certificate instead of individual certificates because each installed app has its own subdomain.Note that in order to allow support for SSL offloading with SharePoint Server App Domains you must enable support for multiple app domains by using the following Microsoft PowerShell commands: + + +``` + +$contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService + $contentService.SupportMultipleAppDomains = $true + $contentService.Update() + Iisreset + +``` + + +## Configure the Subscription Settings and App Management service applications + + +Apps rely on the App Management and Microsoft SharePoint Foundation Subscription Settings service applications. Use the following procedures to configure them. **To turn on the Microsoft SharePoint Foundation Subscription Settings Service** +1. In Central Administration, under **System Settings**, click **Manage services in this farm**. + + +2. For the **Microsoft SharePoint Foundation Subscription Settings Service**, click **Enable Auto Provision** + + +Next, create a Subscription Settings service application and proxy. These must be created by using Microsoft PowerShell. Use the example script provided at **New-SPSubscriptionSettingsServiceApplication**.You also need an App Management service application. The following procedures provide the steps to configure it. **To create a App Management service application** +1. In Central Administration, under **Application Management**, click **Manage service applications**. + + +2. Click **New**, and then click **App Management Service**. + + +3. Type a name for the service application in the **Service Application Name** box. + + +4. Under **Application Pool**, choose **SharePoint Web Services Default** from the **Use existing application pool list**. + + +5. Click **OK**. + + + +## Specify the app domain and app prefix + + +In this section, you specify the app domain and app prefix to use for apps in your environment. The app URL points to your app domain and a prefix that determines how each app is named. Use the following procedure to configure app URLs. **To configure app URLs** +1. In Central Administration, click **Apps**. + + +2. On the **Apps** page, click **Configure App URLs**. + + +3. In the **App domain** box, type the isolated domain that you created for hosting apps (for example, ContosoApps.com). + + +4. In the **App prefix** box, type a name to use for the URL prefix for apps. + + (For example, you could use "apps" as the prefix, and you would see a URL for each app such as "apps- *12345678ABCDEF* .ContosoApps.com".) + + +5. Click **OK**. + + +6. If you will install apps and you have changed the App prefix (also known as the site subscription name), you must perform additional steps that involve restarting the World Wide Web Publishing Service (WWW Service) that hosts the apps. + + > [!IMPORTANT:] + > Stop the SharePoint Timer service.> Restart the World Wide Web Publishing Service that hosts the apps.> Start the SharePoint Timer service. + +## Multi-tenant settings (Optional) + + +If you host multiple tenants in your environment, you must use Microsoft PowerShell to configure app URLs for each tenant. Use the following procedure to configure them. **To configure app URLs by using Windows PowerShell** +1. Open the SharePoint Management Shell. + + +2. At the Microsoft PowerShell command prompt, type the following commands and press **ENTER** after each one: + + ``` + +Set-SPAppDomain + ``` + + + + + + + ``` + Set-SPAppSiteSubscriptionName -Name "app" -Confirm:$false + ``` + + + + + Where: + + - ** is the domain name that you created. + + +3. If you will install apps and you have changed the App prefix (also known as the site subscription name), you must perform additional steps that involve restarting the World Wide Web Publishing Service (WWW Service) that hosts the apps. + + > [!IMPORTANT:] + > Stop the SharePoint Timer service.> Restart the World Wide Web Publishing Service that hosts the apps.> Start the SharePoint Timer service. +For more information, see Set-SPAppSiteSubscriptionName and Set-SPAppDomain. +## Configure the Internet-facing endpoints feature (Optional) + + +The SharePoint Store contains apps for SharePoint intended for use with sites that require Internet-facing endpoints. By default, these apps are not available (greyed out and cannot be purchased) because they are incompatible with most sites. However, if your farm is configured to allow internet-facing end points, you can turn on the Internet-facing endpoints feature to show these apps in the SharePoint Store. You turn this feature on in Central Administration. **To configure Internet-facing endpoints for apps** +1. In Central Administration, click **Application Management**. + + +2. On the **Application Management** page, click **Manage Web applications**. + + +3. On the **Manage Web Applications** page, select the web application that you want to change. + + +4. On the ribbon, click **Manage Features**. + + +5. In the feature list, next to **Apps that require accessible internet facing endpoints**, click **Activate**. + + +6. Click **OK**. + + +In some cases, for example, when you have an on-premises SharePoint Server farm where updates are installed infrequently, you will need to run a cmdlet to update the URL used to point to the SharePoint Store:Set-SPAppStoreConfiguration -Url http://office.microsoft.com -Enable $true +# See also + +#### + + [Plan for apps for SharePoint Server](html/plan-for-apps-for-sharepoint-server.md) + + + + [Install and manage apps for SharePoint Server](html/install-and-manage-apps-for-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-and-deploy-web-parts-in-sharepoint-server.md b/SharePoint/configure-and-deploy-web-parts-in-sharepoint-server.md new file mode 100644 index 0000000000..f7f6875d98 --- /dev/null +++ b/SharePoint/configure-and-deploy-web-parts-in-sharepoint-server.md @@ -0,0 +1,172 @@ +--- +title: Configure and deploy web parts in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 0810018d-188b-4d42-b908-d794faeacd0a +--- + + +# Configure and deploy web parts in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary: ** Learn about securing and deploying web parts in SharePoint Server 2016 and SharePoint 2013.SharePoint Server includes a set of web parts that users can add to pages after installing the product. If an organization needs custom web parts, a developer can write custom ASP.NET web parts and ask you to install them. This process typically requires testing and approval of the code before the web part can be deployed in a full-trust environment. A developer who uses Visual Studio can deploy a web part to SharePoint Server by right clicking the project and selecting **Deploy**. The destination for the web part is determined by the trust level established with the SharePoint server when the developer created the project in Visual Studio.SharePoint Server uses some of the configuration management settings that are provided by the Microsoft .NET Framework. Some of these settings are stored in XML configuration files and they provide a broad range of settings that server administrators use to manage the Web application and its environment. For more information about ASP.NET configuration files, see [Machine.Config and Web.Config Explained](https://go.microsoft.com/fwlink/p/?LinkId=103450) in "Securing Your ASP.NET Application and Web Services".In this article: +- [Configuration options](#BKMK_ConfigurationOptions) + + +- [Setting security attributes](#BKMK_SettingSecurity) + + +- [Safe Controls list](#BKMK_SafeControls) + + +- [Deploy and configure a web part ](#BKMK_DeployConfigure) + + +- [Add a component to the Web Part Gallery ](#BKMK_AddWebGallery) + + + +## Configuration options + + +ASP.NET web parts are deployed to either the SharePoint Server **bin directory** or to the **Global Assembly Cache (GAC)**. +- **Bin directory**    Stored in the bin folder under the root directory of your Web application. + + Advantages of this location: + + A partial-trust location. By default, code that runs from this directory has a low level of code access security permissions. If the web part requires access across applications or more access than the default permissions allow, the administrator must explicitly raise permissions that are granted to a web part so that it can function correctly. Administrators might prefer that assemblies run in the Bin directory, with a known minimum set of required code access security permissions. + + Disadvantages of this location: + + To run your web part everywhere, you must deploy your assembly to the Bin directory on each SharePoint Server 2016 server with the MinRole Front-end and Application server roles, and each SharePoint 2013 server with web and application role installed. + + +- **Global Assembly Cache (GAC)**    All standard web parts are automatically installed in the GAC, where the common language runtime of the .NET Framework is located, at %windir%\\assembly. web parts stored in the GAC can be shared across applications. + + Advantages of this location: + + A global location where you can deploy signed assemblies, which can run with full trust by default. Because the assemblies are installed globally, they work in any Web application. + + Disadvantages of this location: + + Generally, there are no code access security restrictions on code that is installed to the GAC; therefore, you lose the benefit of defense-in-depth security. + + Additionally, it can be difficult to deploy your program database (.pdb) files to assemblies in the GAC. + + + +## Setting security attributes + + +ASP.NET web parts that are stored in the Bin directory have additional security attributes. You can decide whether to set these attributes for your web part, depending on how you plan to use it.The Bin directory is a partial-trust location. Therefore, your web part is not automatically granted full trust code permissions when it is executed. Because the code that calls into your web part is granted only partial trust permissions, the web part developer must configure the **AllowPartiallyTrustedCallers** attribute on your ASP.NET web part.Marking a component as "safe" with the **AllowPartiallyTrustedCallers** attribute puts the responsibility for safe implementation on the development team.By default, the Bin directory and its contents are assigned minimal code access security permissions. You should test your web parts carefully to determine the correct level of permissions to assign, and to ensure that the web part does not present a security risk to your environment.You can elevate permissions in either of two ways: +- (Recommended) Create a trust policy file and point your Web.config file at the new file. This option is more complex, but it enables you to set precise permissions for your web parts. For more information about trust policy files, see [Microsoft Windows SharePoint Services and Code Access Security](https://go.microsoft.com/fwlink/p/?LinkID=103436). + + +- Raise the overall trust level of the Bin directory. In the Web.config file in the root directory of your Web application, locate the trust element. The default value for thetrust element'slevel attribute is **WSS_Minimal**. You can change this level to **WSS_Medium**. Although this option is simpler, it grants arbitrary new permissions that you might not need, and it is less secure than creating a trust policy file. + + + + + + > [!WARNING:] + + +## Safe Controls list + + +The Safe Controls list contains the names of controls and web parts, specific to your SharePoint site, that server administrators can designate as safe for use on any .aspx page within a site. This list is part of the Web.config file in your Web application root. +## Deploy and configure a web part + + +The method that you use to deploy a new web part will depend on the finished package that the developer provides. If the developer provided you with the web part as a single dynamic-link library (DLL) file, you can manually deploy the DLL by copying it to your Web application’s Bin folder. If the developer provides you with a CAB file containing the web part, you can use Microsoft PowerShell to deploy the web part. **To manually deploy and configure a web part** +1. Verify that you have the following administrative credentials: + + - You must be a member of the local Administrators group on the server hosting SharePoint Server. + + +2. Copy the ** .dll assembly in the project's Bin directory to the Bin directory in your Web application root directory. For example: C:\\inetpub\\wwwroot\\wss\\VirtualDirectories\\80\\. + + +3. Locate the Web.config file in your application root directory and open it for editing. + + +4. Add the following safe-control entry for your custom assembly to the Web.config file: + + ``` + + + ``` + + + Where: + +1. ** is the name of the web part that is being deployed. + + +2. ** is the namespace that is associated with your web part. + + +An alternative to manually installing a web part to the Bin folder or manually changing the Web.config file is to use UNRESOLVED_TOKEN_VAL(PowerShell_2nd_NoVerr) to install the web part package. For this process to work, a developer or system administrator must create a CAB solution package for the web part. After you create a CAB file, follow these steps to deploy the web part. **To deploy the web part by using Windows PowerShell** +1. Verify that you meet the following minimum requirements: See **Add-SPShellAdmin**. + + +2. Open SharePoint Management Shell. + + +3. At the PowerShell command prompt (PS C:\\>), type the following command, and then press ENTER: + + ``` + Install-SPWebPartPack -LiteralPath " " -Name " " + ``` + + + Where: + + - ** is the full path to the CAB file that is being deployed. + + + - ** is the name of the web part that is being deployed. + + +The previous procedure shows a common way to use **Install-SPWebPartPack** to deploy a web part. You can specify additional parameters to change the way the web part is deployed. For more information, see **Install-SPWebPartPack**. We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. +## Add a component to the Web Part Gallery + + +Every web part should have a .webpart file, which is an XML file that describes the web part. The .webpart file also causes your web part to appear in the Web Part gallery. The following procedure is the easiest way to create a .webpart file after you deploy your web part and register it in the Safe Control list. **To add a component to the Web Part Gallery** +1. Verify that you have the following administrative credentials: + + - You must be a member of the Farm Administrators group. + + +2. To create a .webpart file, navigate to http:// ** /_layouts/newdwp.aspx, where ** is the name of the server on which your SharePoint site is deployed. + + +3. Select the check box next to *.* . + + +4. Click **Populate Gallery** to add the *YourWebPartName* web part to the Team Site gallery. + + +5. In the Web Part gallery, select **Edit** to edit the web part, and then click **Import**. + + You are prompted to specify a location for the .webpart file. You can also export ASP.NET web parts and import them to SharePoint sites. + + + +# See also + +#### + + [Manage web parts in SharePoint Server](html/manage-web-parts-in-sharepoint-server.md) + + + + +#### + + [How to: Deploy, Publish, and Upgrade SharePoint Solutions on a Remote Server](https://msdn.microsoft.com/en-us/library/hh370987.aspx) + + + + + + + + diff --git a/SharePoint/configure-and-use-the-documentum-connector-in-sharepoint-server.md b/SharePoint/configure-and-use-the-documentum-connector-in-sharepoint-server.md new file mode 100644 index 0000000000..ee9460fa3a --- /dev/null +++ b/SharePoint/configure-and-use-the-documentum-connector-in-sharepoint-server.md @@ -0,0 +1,807 @@ +--- +title: Configure and use the Documentum connector in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: b17a56ea-2e7f-43c6-9a17-00ae1f5c4089 +--- + + +# Configure and use the Documentum connector in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* This article describes how to install and configure the Microsoft SharePoint Server 2016 Indexing Connector for Documentum.The Microsoft SharePoint Server 2016 Indexing Connector for Documentum enables you to index content that is stored in the EMC Documentum system. This article describes how to install and configure the Indexing Connector for Documentum for use with SharePoint Server 2016.The Indexing Connector for Documentum: +- Is a 64-bit connector based on the SharePoint Server 2016 Search Connector Framework. + + +- Supports multiple versions of EMC Documentum Content Server. + + +- Indexes Documentum objects and object metadata. See [Supported and unsupported Documentum object types and properties in SharePoint Server](html/supported-and-unsupported-documentum-object-types-and-properties-in-sharepoint-s.md). + + +- Supports Documentum security definitions and policies. + + +- Supports Microsoft PowerShell for automated configuration and administration. See [Using the SPEnterpriseSearchDCTMConnectorConfig cmdlet](#DCTM_cmdlet). + + +- Has a configurable search results URL to support multiple Documentum client applications. + + +- Supports file and folder exclusion for crawling. + + +In this article: +- [Before you begin](#begin) + + +- [Overview](#DCTM_Overview) + + +- [Prepare the SharePoint 2013 servers that host a crawl component](#DCTM_PrepareCrawlServer) + + +- [Install and register the Indexing Connector for Documentum](#DCTM_InstallCon) + + +- [Configure the Indexing Connector for Documentum](#DCTM_ConfigureConn) + + +- [Create the Documentum crawled properties category](#BKMK_CrawledPropertiesCategory) + + +- [Create a crawl rule for Documentum](#DCTM_Crawl_rule) + + +- [Create a Documentum content source](#DCTM_Content_source) + + +- [Using the SPEnterpriseSearchDCTMConnectorConfig cmdlet](#DCTM_cmdlet) + + + +## Before you begin + + +Before you begin this operation, review the following system prerequisites and requirements: +- The supported operating systems are Windows Server 2008 R2, Windows Server 2008 Service Pack 2, and Windows Server 2012. + + +- One of the following SharePoint 2016 Products is installed and configured: + + - Microsoft SharePoint Server 2016 Enterprise + + + - Microsoft SharePoint Server 2016 Standard + + +- A Search service application is installed and configured. + + +- A Documentum Foundation Services (DFS) Server with a version that is compatible with DFS Productivity Layer 6.7 SP2 is installed on a Windows host. + + +- DFS Productivity Layer 6.7 SP2 is installed and you have access to the .NET assemblies that are included in the DFS Productivity Layer 6.7 SP2. The Indexing Connector for Documentum uses DFS as the connectivity API to access Documentum repositories. + + +- Documentum Content Server is installed. The supported versions of Documentum Content Server are determined by DFS 6.7 SP2. You can find a detailed list in the DFS Productivity Layer 6.7 SP2 release notes. You can download the release notes from the EMC customer support site [https://powerlink.emc.com](https://powerlink.emc.com). + + +- Configure the Indexing Connector for Documentum with *-ACLTranslation "Claims"* if you have to crawl Documentum repositories that have Documentum Trusted Content Services (TCS) enabled. You can also use this connector configuration to enable automatic mapping between Windows Active Directory users and Documentum users, regardless of whether the repository has TCS enabled. + + + +## Overview + + +The following steps provide a high-level overview of the tasks that are involved to install and configure the Indexing Connector for Documentum for use with SharePoint Server 2016. +1. Preparation: + +1. Ensure that your system meets the system prerequisites and requirements in the section [Before you begin](#begin). + + +2. Download the SharePoint Server 2016 Indexing Connector for Documentum from the [Microsoft Download Center](https://go.microsoft.com/?linkid=9826867). + + +3. [Decide which Documentum content access account to use for crawling](#DCTM_ContentAccess). + + +4. [Prepare the SharePoint Server 2016 servers that host a crawl component](#DCTM_PrepareCrawlServer). On each server: + +1. [Set the DFS Productivity Layer .NET assemblies](#DCTM_Assemblies). + + +2. [Edit the machine.config file](#DCTM_machineconfig) to set the Documentum bindings. + + +2. Install the Indexing Connector for Documentum. + +1. [Install the Indexing Connector for Documentum](#DCTM_Deployconn) on each SharePoint Server 2016 server in the farm that hosts a crawl component. + + +2. [Register the Indexing Connector for Documentum to the Search service application](#DCTM_Registerconn) by using Microsoft PowerShell. + + +3. [Configure the Indexing Connector for Documentum](#DCTM_ConfigureConn) on each SharePoint Server 2016 server in the farm that hosts a crawl component by using the Indexing Connector for Documentum PowerShell cmdlet. Choose one of the following configurations: + +### + +Configuration ACL Translation Description See this section Support crawling EMC Documentum Trusted Content Services (TCS) content or regular Documentum content with automatic user mapping.
Claims
You enable automatic user mapping by configuring a separate Security Trimmer Sync Service and pre- and post-trimmers.
[Configure the Indexing Connector for Documentum to support TCS and automatic user mapping](#DCTM_Configure_TCS)
Support crawling Documentum content and use a manually created user mapping table.
UserMappingTable
You manually create a user mapping table in SQL Server to specify how the Documentum users are mapped to Active Directory Domain Services (AD DS) or Active Directory service users. You configure the connector by specifying in which database you have created the user mapping table by using Microsoft PowerShell.
[Configure the Indexing Connector for Documentum using a user mapping table](#DCTM_UserMapping)
Support crawling Documentum content when Documentum and Windows user accounts are the same.
SameAccountName
The Indexing Connector for Documentum assumes that Documentum and SharePoint users share the same account, such as a shared account in Active Directory. Once an account is found that is not valid, the Indexing Connector for Documentum discards the account permission.
[Using the SPEnterpriseSearchDCTMConnectorConfig cmdlet](#DCTM_cmdlet)
Support crawling Documentum content without security trimming the search results.
NoSecurity
All users will be able to see all Documentum search results. This can be useful if you have a public Documentum repository that everyone can access, for example.
[Using the SPEnterpriseSearchDCTMConnectorConfig cmdlet](#DCTM_cmdlet)
4. Configure a Documentum crawl rule and content source in the Search service application by using Central Administration. + +1. [Create a crawl rule for Documentum](#DCTM_Crawl_rule). + + +2. [Create a Documentum content source](#DCTM_Content_source) + + +3. Perform a full crawl. + + + +## Prepare the SharePoint Server 2016 servers that host a crawl component + + + **Decide which Documentum content access account to use for crawling** +1. You have to specify the Documentum content access account and the password later in the configuration procedure when you set up crawl rules. The Indexing Connector for Documentum uses the content access account to retrieve content from the Documentum repository. This account must have the following minimum permissions: + + - Read permission to documents that you want to crawl. + + + - Browse permission to cabinets, folders, and records (documents with only metadata) that you want to crawl. + + + **Set the DFS Productivity Layer .NET assemblies** +1. Locate the following DFS Productivity Layer .NET assemblies and verify that the version number is **6.7.2000.36** for all files. When extracted to the default path, these files are located in the%local%\\emc-dfs-sdk-6.7\\emc-dfs-sdk-6.7\\lib\\dotnet directory. + + - Emc.Documentum.FS.DataModel.Core.dll + + + - Emc.Documentum.FS.DataModel.Shared.dll + + + - Emc.Documentum.FS.runtime.dll + + + - Emc.Documentum.FS.Services.Core.dll + + +2. On each server that hosts a crawl component, log on with an account that is a member of the Administrators group on that server and deploy the DFS Productivity Layer .NET assemblies to the global assembly cache %windir%\\assembly. + + > [!NOTE:] + +The following procedure explains how to edit the machine.config file on each SharePoint Server 2016 server that hosts a crawl component to include WCF settings for the DFS Productivity Layer. This is done to make sure that the DFS Productivity Layer .NET assemblies function correctly.The WCF settings that you are about to set in [Edit the machine.config file](#DCTM_machineconfig) allow a maximum of 30 megabytes (MB) per Documentum content object (the document file plus its metadata) transferred. The administrator can increase *maxReceivedMessageSize* in *DfsDefaultService* binding for larger content. **Edit the machine.config file** +1. On each server that hosts a crawl component, open the machine.config file. This file is located in the directory %windir%\\Microsoft.NET\\Framework64\\v4.0.30319\\Config. + + +2. Copy the following XML snippet to the **** element: + + ``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ``` + + +## Install and register the Indexing Connector for Documentum + + + **Install the Indexing Connector for Documentum** +1. Download the Indexing Connector for Documentum from the [Microsoft Download Center](https://go.microsoft.com/?linkid=9826867). + + +2. On each server in the farm that hosts a crawl component, install the Indexing Connector for Documentum by running the file DCTMIndexConn.exe. Follow the steps in the installation wizard. + + + **Register the Indexing Connector for Documentum to the Search service application** +1. Run this procedure on a SharePoint Server 2016 server that hosts a crawl component to register the connector to the Search service application. + + +2. Start a SharePoint 2016 Management Shell. + + - For Windows Server 2008 R2: + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://go.microsoft.com/fwlink/p/?LinkId=276950). + + +3. At the Microsoft PowerShell command prompt, type the following command(s): + + ``` + +New-SPEnterpriseSearchCrawlCustomConnector -SearchApplication "" -Protocol "dctm" -ModelFilePath "<%CommonProgramFiles%\\Microsoft Shared\\Web Server Extensions\\15\\CONFIG\\SearchConnectors\\Documentum\\MODEL.xml>" -Name "Microsoft SharePoint 2016 Indexing Connector for Documentum" + + ``` + + + Where: + + - ** is the name of the Search service application that you are registering the connector to. + + + - *<%CommonProgramFiles%\\Microsoft Shared\\Web Server Extensions\\15\\CONFIG\\SearchConnectors\\Documentum\\MODEL.xml>* is the path of the Indexing Connector for Documentum model file. The default location is given in this example. + + + +## Configure the Indexing Connector for Documentum + + +You configure the connector settings with the Indexing Connector for Documentum PowerShell cmdlet (Set-SPEnterpriseSearchDCTMConnectorConfig). The settings are stored in %CommonProgramFiles%\\Microsoft Shared\\Web Server Extensions\\15\\CONFIG\\SearchConnectors\\Documentum\\DCTMConfig.xml and must be the same on each SharePoint Server 2016 server that hosts a crawl component.Which PowerShell cmdlet parameters you use and which additional configuration steps you must perform depends on configuration mode you choose. +## Configure the Indexing Connector for Documentum to support TCS and automatic user mapping + + +The following procedures explain how to configure the indexing connector for Documentum to support TCS. The procedures also show how to enable automatic user mapping by configuring the Security Trimmer Sync Service and create and deploy custom pre- and post-security trimmers. After completing these procedures, your Documentum user credentials will be automatically synced with Windows Active Directory Domain Services (AD), search results will be trimmed accordingly and users will only be able to retrieve Documentum search results that they have permission to see.The Security Trimmer Sync Service maps Documentum users to AD users by looking at the Documentum fields **user_os_domain**, **user_login_name**, **user_source** and **user_ldap_dn**. If the **user_ldap_dn** field is populated, the Security Trimmer Sync Service will try to extract a domain from the first DC value. For example, if the **user_ldap_dn** field is populated with " **CN=User Name, OU=Unit,DC=Domain,DC=Department,DC=Company**", the Security Trimmer Sync Service will extract the domain from **DC=Domain** and will ignore **DC=Department,DC=Company**. **To configure the connector to support TCS and automatic user mapping** +1. Start a SharePoint 2016 Management Shell on each server that hosts a crawl component. + + - For Windows Server 2008 R2: + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://go.microsoft.com/fwlink/p/?LinkId=276950). + + +2. At the Microsoft PowerShell command prompt, type the following command(s): + + ``` + +Set-SPEnterpriseSearchDCTMConnectorConfig -Shared -ACLTranslation "Claims" -DisplayURLPatternForDocument "http:///webtop/component/drl?objectId={ObjectId}&format={Format}&RepositoryName={RepositoryName}" -DisplayURLPatternForContainer "http:///webtop/component/drl?objectId={ObjectId}&RepositoryName={RepositoryName}" + +Set-SPEnterpriseSearchDCTMConnectorConfig -Repository -RepositoryName "" -DFSWebServiceURL @("http://:<30000>/services"), ("http://:<30000>/services") + +Set-SPEnterpriseSearchDCTMConnectorConfig -Repository -RepositoryName "" -DFSWebServiceURL @("http://:<30000>/services") + + ``` + + + Where: + + - ** is the name and the port number of the DFS Web Top Server you are using. + + + - ** is the name of Documentum repository that you want to crawl. + + + - *:<30000>* is the name and the port number of the Documentum Web Services server that hosts the Documentum repository that you want to crawl. + + +3. Restart the OSearch15 service. This must be done before you create a content source for Documentum. + + > [!IMPORTANT:] + + +1. Verify that the user account that is performing this procedure is an administrator for the server that hosts the crawl component. + + +2. Open a Command Prompt window. + + +3. To stop the OSearch15 service, type this command: **net stop osearch15** + + +4. To start the OSearch15 service, type this command: **net start osearch15** + + + **To set up the Security Trimming Sync Service** +1. Open the file Microsoft.Office.Server.Search.Connector.Documentum.TrimmerSync.exe.config. This file is stored in the folder where you have installed the Indexing Connector for Documentum connector. The default location is %CommonProgramFiles%\\Microsoft Shared\\Web Server Extensions\\15\\CONFIG\\SearchConnectors\\Documentum. + + +2. Using the same information that you provided when you configured the Indexing Connector for Documentum, edit the configuration file as follows. + +1. In the **Emc.Documentum** section, in the **ModuleInfo** element, do the following: + + - In the **host** attribute, type the host name of the Documentum server. + + + - In the **port** attribute, type the port number of the Documentum server. + + +2. In the **Data Source: Documentum Settings** section, in the **Repositories** element, do the following: + + - In the **repository id** attribute, type the Documentum repository id. + + + - In the **name** attribute, type the name of the Documentum repository. + + + - In the **login** attribute, type the Documentum login name. Use the same login name as the Documentum content access account. This should be a user who has elevated user permissions on the Documentum Content Server. For more information, see [Determine which Documentum content access account to use](#DCTM_ContentAccess). + + + - In the **dfs** attribute, type the location of the Documentum Foundation Services (DFS) by providing the URI for the DFS. + + +3. (Optional) If your Documentum connection requires SSL/HTTPS, you have to change the security mode. + + - In the **Data Source: Documentum Settings** section, subsection **Documentum**, in the **basicHttpBinding** element, set the security mode attribute from *None* to *Transport* for the following bindings: + + - **DfsAgentService** + + + - **DfsContextRegistryService** + + + - **DfsDefaultService** + + + - In the **Data Source: Documentum Settings** section, subsection **Documentum**, in the **netNamedPipeBinding** element, set the security mode attribute from *None* to *Transport* for the following bindings: + + - **localNamedPipeBinding** + + +3. Save and close the file. + + +4. Copy the DFS Productivity Layer .NET assemblies to the server running the Security Trimming Sync Service. + +1. Locate the following DFS Productivity Layer .NET assemblies and verify that the version number is **6.7.2000.36** for all files. When extracted to the default path, these files are located in the%local%\\emc-dfs-sdk-6.7\\emc-dfs-sdk-6.7\\lib\\dotnet directory. + + - Emc.Documentum.FS.DataModel.Core.dll + + + - Emc.Documentum.FS.DataModel.Shared.dll + + + - Emc.Documentum.FS.runtime.dll + + + - Emc.Documentum.FS.Services.Core.dll + + +2. On the server that hosts the Security Trimming Sync Service, log on with an account that is a member of the Administrators group on that server and deploy the DFS Productivity Layer .NET assemblies to the global assembly cache %windir%\\assembly. + + > [!NOTE:] + +5. Configure authentication for the Security Trimming Sync Service and install the service. + +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. Open a Command Prompt window on each server that hosts a query processing component. + + +3. Type the following command: **Microsoft.Office.Server.Search.Connector.Documentum.TrimmerSync.exe -p** + + When prompted, enter the password for the account that you provided in the **login** attribute. Use the same login name as the Documentum content access account. The password will now automatically be encrypted and added to the Security Trimming Sync Service config file. + + +4. Install the Security Trimming Sync Service. Type the following command: **Microsoft.Office.Server.Search.Connector.Documentum.TrimmerSync.exe -i** + + +6. Start the Security Trimming Sync Service. + +1. Open **Windows Server Manager**. + + +2. Expand the **Configuration** menu and click **Services**. + + +3. Right-click the **SharePoint Documentum Security Sync** service and then click **Properties**. In the **LogOn** tab, select **This account** and provide the account details and credentials for the account that runs the SharePoint services. Click **OK**. + + +4. Right-click the **SharePoint Documentum Security Sync** service and then click **Start**. + + +5. Verify that the **Status** column changes to **Started**. + + +7. Verify that the service is running and that the security sync is completed. + +1. Run the command **Microsoft.Office.Server.Search.Connector.Documentum.TrimmerSync.exe -d** to write the Security Trimming Sync Service memory to a text file. + + +2. Verify that the Security Trimming Sync Service connects to the Documentum server. Read the file DCTMSecuritySync.log that is located in the directory \\15.0\\Data\\Office Server\\Applications\\Search\\Nodes. + + +3. Verify that the membership information from the Documentum server is written to the file DCTMSecuritySync_Dump.txt that is located in the directory \\15.0\\Data\\Office Server\\Applications\\Search\\Nodes. + + +Before you can add the pre- and post- security trimmers, you must add one simple crawl rule for Documentum. Later, you can further specify or expand the crawl rules. **Create a simple crawl rule for Documentum** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. On the SharePoint Central Administration home page, in the **Application Management** section, click **Manage Service Applications**. + + +3. On the Manage Service Applications page, click the Search service application for which you want to create a crawl rule. + + +4. On the Search Administration page, in the **Crawling** section, click **Crawl Rules**. + + +5. On the Manage Crawl Rules page, click **New Crawl Rule**. + + +6. On the Add Crawl Rule page, specify the following information to create a crawl rule: + +1. In **Path** box, type **dctm://***. + + +2. In **Crawl Configuration** section, select **Include all items in this path**, and then select **Crawl complex URLs (URLs that contain a question mark - ?)**. + + +3. In the **Specify Authentication** section, select **Specify a different content access account**, and then type the Documentum content access account and password in the appropriate boxes. + + +4. Make sure that the **Do not allow Basic Authentication** check box is cleared. + + +7. Click **OK** to add the crawl rule. + + + **To add the Indexing Connector for Documentum pre- and post-security trimmers** +1. Start a SharePoint 2016 Management Shell on each server that hosts a query processing component. + + - For Windows Server 2008 R2: + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://go.microsoft.com/fwlink/p/?LinkId=276950). + + +2. At the Microsoft PowerShell command prompt, type the following command(s): + + ``` + +New-SPEnterpriseSearchSecurityTrimmer -SearchApplication -typeName "Microsoft.Office.Server.Search.Connector.Documentum.Trimmers.DctmTrimPre, Microsoft.Office.Server.Search.Connector.Documentum.Trimmers, Version=15.0.0.0,Culture=neutral, PublicKeyToken=48e046c834625a88, processorArchitecture=MSIL" -id 26 -RulePath dctm:\\* + +New-SPEnterpriseSearchSecurityTrimmer -SearchApplication -typeName "Microsoft.Office.Server.Search.Connector.Documentum.Trimmers.DctmTrimPost, Microsoft.Office.Server.Search.Connector.Documentum.Trimmers, Version=15.0.0.0,Culture=neutral, PublicKeyToken=48e046c834625a88, processorArchitecture=MSIL" -id 17 -RulePath dctm:\\* + + ``` + + + Where: + + - ** is the name of the Search service application. + + +3. Restart the SharePoint Search Host Controller. + +1. Open a Command Prompt window. + + +2. To stop the SharePoint Search Host Controller, type this command: **net stop spsearchhostcontroller** + + +3. To start the SharePoint Search Host Controller, type this command: **net start spsearchhostcontroller** + + +4. Continue with [Create a Documentum content source](#DCTM_Content_source). + + + +## Configure the Indexing Connector for Documentum using a user mapping table + + +The following procedures explain how to manually create a user mapping table that specifies how the Documentum users are mapped to Active Directory Domain Services (AD DS) or Active Directory service users, and how to configure the connector to support crawling Documentum content and use the user mapping table. +- The user mapping table must be in a SQL Server 2008 or a later version database. + + +- The OSearch15 service account must have at least read permission on the user mapping table data. + + + **To create a user mapping table** +1. Create a user mapping table in SQL Server 2008 or a later version. The user mapping table must have the following format: + +### + +Column name SQL datatype Description DCTMCredentialDomain
nvarchar(255) NOT NULL
Domain name of a Documentum account. Populate this column when the account comes from the local computer or an LDAP system. The *User Source* property of the Documentum account should equal *None* or *LDAP* . Otherwise, leave the column empty.
DCTMCredentialRepository
nvarchar (32) NOT NULL
Repository name of a Documentum account. Populate this column when the account comes from a Documentum repository.
DCTMCredentialLoginName
nvarchar (80) NOT NULL
Login name of the Documentum account.
NTCredential
nvarchar (255) NOT NULL
Windows domain user account that searches Documentum contents in SharePoint Server 2016.
+ Use the following script to create a user mapping table: + + + + ``` + +CREATE TABLE +( +DCTMCredentialDomain nvarchar (255) NOT NULL , +DCTMCredentialRepository nvarchar (32) NOT NULL , +DCTMCredentialLoginName nvarchar (80) NOT NULL , +NTCredential nvarchar (255) NOT NULL , +CONSTRAINT PK_CredentialMapping PRIMARY KEY CLUSTERED +( DCTMCredentialDomain, DCTMCredentialRepository, DCTMCredentialLogonName ) +) + + ``` + + + Alternatively, you can manually create the user mapping table using SQL Server Management Studio or an equivalent tool. If you create the table manually, make sure that you use the same schema as defined in the script. + + +2. Populate the user mapping table with Documentum/Windows NT credential pairs. The table in the previous step shows what kind of input is expected. + + Example: + + A Documentum repository user Dan Park has a logon that is linked to the Finance repository. Dan's Windows domain user account is Contoso\\dpark. In this case, the user mapping table entry for Dan should be: + +### + +DCTMCredentialDomain
''
DCTMCredentialRepository
Finance
DCTMCredentialLogonName
dpark
NTCredential
Contoso\\dpark
+ > [!NOTE:] + +3. Grant the OSearch15 account read access to the user mapping table. + + + **To configure the connector using a user mapping table** +1. Start a SharePoint 2016 Management Shell on each server that hosts a crawl component. + + - For Windows Server 2008 R2: + + - On the **Start** menu, click **All Programs**, click **SharePoint 2016**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + - For Windows Server 2012: + +1. On the **Start** screen, right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + If **SharePoint 2016 Management Shell** is not on the **Start** screen: + + +2. Right-click **Computer**, click **All apps**, then right-click **SharePoint 2016 Management Shell** and then click **Run as administrator**. + + + + For more information about how to interact with Windows Server 2012, see [Common Management Tasks and Navigation in Windows Server 2012](https://go.microsoft.com/fwlink/p/?LinkId=276950). + + +2. At the Microsoft PowerShell command prompt, type the following command(s): + + ``` + +Set-SPEnterpriseSearchDCTMConnectorConfig -Shared -ACLTranslation UserMappingTable -DisplayURLPatternForContainer "http:///webtop/component/drl?objectId={ObjectId}&RepositoryName={RepositoryName}" -DisplayURLPatternForDocument "http:///webtop/component/drl?objectId={ObjectId}&format={Format}&RepositoryName={RepositoryName}" -UnmappedAccount "DiscardACE" -UserMappingTableSQLServer "" -UserMappingTableSQLInstance "" -UserMappingTableDBName "" -UserMappingTableName "" + +Set-SPEnterpriseSearchDCTMConnectorConfig -Repository -RepositoryName "" -DFSWebServiceURL @("http://:<30000>/services", "http://:<30000>/services") + +Set-SPEnterpriseSearchDCTMConnectorConfig -Repository -RepositoryName "" -DFSWebServiceURL @("http://:<30000>/services") + ``` + + + Where: + + - ** is the name and the port number of the DFS Web Top Server you are using. + + + - ** is the name of the database server on which you created the user mapping table. + + + - ** is the name of the database instance of the database server on which you created the user mapping table. + + + - ** is the name of the database in which you created the user mapping table. + + + - ** is the name of the user mapping table that you created. + + + - ** is the name of Documentum repository that you want to crawl. + + + - *:<30000>* is the name and port number of the Documentum Web Services server that hosts the Documentum repository that you want to crawl. + + +3. Restart the OSearch15 service. The server administrator of the server that hosts the crawl component must restart the OSearch15 service before a content source can be created for Documentum. + + > [!IMPORTANT:] + + +1. Verify that the user account that is performing this procedure is an administrator for the server that hosts the crawl component. + + +2. Open a Command Prompt window. + + +3. To stop the OSearch15 service, type this command: **net stop osearch15** + + +4. To start the OSearch15 service, type this command: **net start osearch15** + + +Continue with [Create a crawl rule for Documentum](#DCTM_Crawl_rule) and then continue with [Create a Documentum content source](#DCTM_Content_source). +## Create the Documentum crawled properties category + + +You must create a crawled properties category that will contain the Documentum crawled properties. To do so, you use the **New-SPEnterpriseSearchMetadataCategory** cmdlet and specify the predefined value 34972762-7E3F-4f4f-AE5C-5ABBA92EC530 for the cmdlet's PropSet parameter. Use the following PowerShell code to create the crawled properties category in this way. +``` + +$ssa = Get-SPEnterpriseSearchServiceApplication +New-SPEnterpriseSearchMetadataCategory -Name "Documentum Connector" -SearchApplication $ssa -PropSet "34972762-7E3F-4f4f-AE5C-5ABBA92EC530" -DiscoverNewProperties $true +``` + + +## Create a crawl rule for Documentum + + +Before a crawl, you must create at least one crawl rule to authenticate the crawler with the DFS Server. You can create more than one crawl rule to include or exclude specific content in Documentum. **To create a crawl rule for the Indexing Connector for Documentum** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. On the SharePoint Central Administration home page, in the **Application Management** section, click **Manage Service Applications**. + + +3. On the Manage Service Applications page, click the Search service application for which you want to create a crawl rule. + + +4. On the Search Administration page, in the **Crawling** section, click **Crawl Rules**. + + +5. On the Manage Crawl Rules page, click **New Crawl Rule**. + + +6. On the Add Crawl Rule page, specify the following information: + +1. In the **Path** box, type the path to which the crawl rule will apply. You can use standard wildcard characters. To use regular expressions instead of wildcard characters, select **Use regular expression syntax for matching this rule**. For examples, see [Syntax to refer to a Documentum object](#DCTM_Syntax). + + +2. In **Crawl Configuration** section, select **Include all items in this path**, and then select **Crawl complex URLs (URLs that contain a question mark - ?)**. + + +3. In the **Specify Authentication** section, select **Specify a different content access account**, and then type the Documentum content access account and password in the boxes. See [Determine which Documentum content access account to use](#DCTM_ContentAccess) earlier in this article. + + +4. Make sure that the **Do not allow Basic Authentication** check box is cleared. + + +7. Click **OK** to add the crawl rule. + + > [!NOTE:] + > You can create multiple crawl rules for Documentum to include or exclude Documentum content.> You can use different crawl rules to specify different content access accounts for different Documentum content. For example, you have two repositories and two content access accounts for each repository. The Documentum content access account specified in a crawl rule will only be applied to Documentum content covered by the path in that crawl rule. If you use the Security Trimming Sync Service, you must set up this service for each Documentum server. + +## Create a Documentum content source + + +You create a content source for Documentum content to specify which Documentum content repositories you want to crawl. **To create a content source for the Indexing Connector for Documentum** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. On the SharePoint Central Administration home page, in the **Application Management** section, click **Manage Service Applications**. + + +3. Click the Search service application in which you want to create a content source. + + +4. On the Search Administration Page, in the **Crawling** section, click **Content Sources**. + + +5. On the Manage Content Sources page, click **New Content Source**. + + +6. On the Add Content Source page, do the following: + +1. In the **Name** box, type the name for the new content source. + + +2. In the **Content Source Type** section, select **Custom Repository**. + + +3. In the **Type of Repository** section, select **SharePoint 2016 Indexing Connector for Documentum**. Use the name that you specified when you registered the Indexing Connector for Documentum with the Search service application. + + +4. In the **Start Addresses** section, type the start addresses. The start address format is the same as the path pattern. You can type more than one start address for the content source, one per line. For examples, see [Syntax to refer to a Documentum object](#DCTM_Syntax). + + +5. In the **Crawl Schedules** section, select schedules from the **Full Crawl** and **Incremental Crawl** drop-down lists, or create schedules for each kind of crawl. + + +6. In the **Content Source Priority** section, assign a priority level to the content source according to your business requirements. + + +7. Click **OK**. + + +7. On the **Manage Content Sources** page, right-click the content source for Documentum and click **Start Full Crawl**. + + +The Documentum content source is configured and the system can crawl Documentum content repositories that are specified in the content source. SharePoint Server 2016 supports scalable architecture for performance scale-out. You can deploy more than one server that hosts a crawl component and you can configure multiple crawlers to crawl the EMC Documentum database at the same time. +## Syntax to refer to a Documentum object + + +The format to refer to a Documentum object that you use for the path (when you set up a crawl rule) and the start address (when you set up a content source) is defined in the following table: +### + +Type of Documentum object Syntax for the path or the start address Repository
dctm:///
Cabinet
dctm:////
Folder
dctm://///
Document
dctm://////…/?DocSysID= (where r_object_id is the object id of that document)
** is the host name of your Documentum client application such as Webtop or DA. The ** configured here must be the same as the one that is used in the content source. ** , ** , and ** are case-sensitive. +## Using the SPEnterpriseSearchDCTMConnectorConfig cmdlet + + +Use the following Microsoft PowerShell commands to display help and examples for the Indexing Connector for Documentum cmdlet: +- Get-help Set-SPEnterpriseSearchDCTMConnectorConfig -full shows full help. + + +- Get-help Set-SPEnterpriseSearchDCTMConnectorConfig -examples shows only examples. + + +The Set-SPEnterpriseSearchDCTMConnectorConfig cmdlet accepts three parameter sets. You use the *Shared* parameter set to change the configuration settings that affect all the Documentum repositories that you crawl. You use the *Repository* parameter set to change the configuration settings that affect only a specific repository. You use the *Remove* parameter set to remove a specific repository from the connector configuration.The following table shows which parameters are mandatory and which are optional. For parameter descriptions and examples, see **Set-SPEnterpriseSearchDCTMConnectorConfig**. +### + +Action Mandatory parameters Optional parameters Configure shared repository settings
Shared
DFSURL, UserMappingTableSQLServer, UserMappingTableSQLInstance, UserMappingTableDBName, UserMappingTableName, ACLTranslation, UnmappedAccount, DisplayURLPatternForDocument, DisplayURLPatternForContainer.
Configure settings for a specific repository
Repository, RepositoryName
DFSWebServiceURL, IndexAllVersions, ACLTranslation, UnmappedAccount, DisplayURLPatternForDocument, DisplayURLPatternForContainer.
Remove a repository from configuration
Remove, RepositoryName

+# See also + +#### + + [Supported and unsupported Documentum object types and properties in SharePoint Server](html/supported-and-unsupported-documentum-object-types-and-properties-in-sharepoint-s.md) + + + + +#### + + **Set-SPEnterpriseSearchDCTMConnectorConfig** + + + + + + + + diff --git a/SharePoint/configure-and-use-the-exchange-connector-for-sharepoint-server.md b/SharePoint/configure-and-use-the-exchange-connector-for-sharepoint-server.md new file mode 100644 index 0000000000..41d7b527a9 --- /dev/null +++ b/SharePoint/configure-and-use-the-exchange-connector-for-sharepoint-server.md @@ -0,0 +1,178 @@ +--- +title: Configure and use the Exchange connector for SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: ffec2e36-9142-45ae-866e-308d6efbc114 +--- + + +# Configure and use the Exchange connector for SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn how to create a crawl rule and add a content source to crawl Exchange Server public folders.In this article: +- [Before you begin](#begin) + + +- [Create a crawl rule](#proc1) + + +- [Add a content source for Exchange Server public folders](#proc2) + + + +## Before you begin + + +Before you begin this operation, review the following information about prerequisites: +- Create a Search service application + + +- Ensure that the crawler has at least Read permission to the Exchange Server public folder. + + + +## Create a crawl rule + + +This following procedure describes how to create a crawl rule. You must create a crawl rule if the default content access account does not have Read permission to the Exchange Server public folders that you want to crawl. **To create a crawl rule** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. In Central Administration, in the Application Management section, click **Manage Service Applications**. + + +3. On the Manage Service Applications page, in the list of service applications, click the Search service application. + + +4. On the Search Administration page, in the Crawling section, click **Crawl Rules**. + + +5. On the Manage Crawl Rules page, click **New Crawl Rule**. + + +6. On the Add Crawl Rule page, in the **Path** section, in the **Path** box, type the path to which the crawl rule will apply. You can use standard wildcard characters in the path. + + > [!NOTE:] + +7. In the **Crawl Configuration** section, select **Include all items in this path**. + + +8. In the **Specify Authentication** section, select the type of crawl authentication to use. This section is available only if **Include all items in this path** is selected. + + +9. Click **OK**. + + + +## Add a content source for Exchange Server public folders + + +Use one of the following procedures to create a content source for Exchange Server public folders. Which procedure you should follow depends on the Exchange Server version. You can choose to add a content source to crawl public folders in: +- Exchange Server 2007 and Exchange Server 2007 with Service Pack 1 (SP1) + + +- Exchange Server 2007 with Service Pack 2 (SP2) and Exchange 2010 + + + **To add a content source for Exchange Server 2007 and Exchange Server 2007 SP1 public folders** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. On the SharePoint Server Central Administration home page, in the **Application Management** section, click **Manage service applications**. + + +3. On the Manage Service Applications page, click the Search service application. + + +4. On the Search Administration page, in the **Crawling** section, click **Content Sources**. + + +5. On the Manage Content Sources page, click **New Content Source**. + + +6. On the Add Content Source page, in the **Name** box, type a name for the new content source. + + +7. In the **Content Source Type** section, select **Exchange Public Folders**. + + +8. In the **Start Addresses** section, in the **Type start addresses below (one per line)** box, type the URLs for the Exchange Server public folders that you want to crawl. These URLs are typically in one of the following forms: + + - ** :// *host name* /public + + Where ** can be http or https, and *host name* is the NetBIOS or fully qualified domain name (FQDN) of the server that is running Exchange Server. + + + - ** :// *host name* /public/ *subfolder* + + Where ** can be http or https, *host name* is the NetBIOS or FQDN of the server that is running Exchange Server, and *subfolder* is the name of the specific subfolder that you want to crawl. + + + + For example, if you want to crawl all subfolders in the public folder on a server that is named exch-01 and that is in the Contoso domain, and that server does not use SSL, you could type either **http://exch-01/public** or **http://exch-01.contoso.com**. To crawl only a specific subfolder named Bob in the same public folder, type **http://exch-01/public/bob** or **http://exch-01.contoso.com/bob**. + + > [!NOTE:] + +9. In the **Crawl Settings** section, select the crawling behavior that you want. + + +10. In the **Crawl Schedules** section, you can choose to specify when to start full and incremental crawls: + + - To create a full crawl schedule, click the **Create Schedule** link below the **Full Crawl** list. + + + - To create an incremental crawl schedule, click the **Create schedule** link below the **Incremental Crawl** list. + + +11. Click **OK**. + + + **To add content sources for Exchange Server 2007 SP2 and Exchange 2010 public folders** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. Open a web browser and go to the Outlook Web Access webpage for the Exchange Server that contains the public folders that you want to crawl. + + +3. Log on to Outlook Web Access using any user account that has Read permissions on the public folders that you want to crawl. + + +4. Go to the public folder that you want to crawl, right-click the folder, and then select **Open in New Window**. + + +5. When the new window opens, go to the address bar and copy the complete URL. This is the Outlook Web Access public folder address. + + +6. On the SharePoint Server Central Administration home page, in the **Application Management** section, click **Manage service applications**. + + +7. On the Manage Service Applications page, click the Search service application. + + +8. On the Search Administration page, in the **Crawling** section, click **Content Sources**. + + +9. Click **New Content Source**. + + +10. On the Add Content Source page, in the **Name** box, type a name for the new content source. + + +11. In the **Content Source Type** section, select **Exchange Public Folders**. + + +12. In the **Start Addresses** section, paste the Outlook Web Access public folder address that you copied in step 5. + + +13. In the **Crawl Settings** section, select the crawling behavior that you want. + + +14. In the **Crawl Schedules** section, you can choose to specify when to start full and incremental crawls: + + - To create a full crawl schedule, click the **Create Schedule** link below the **Full Crawl** list. + + + - To create an incremental crawl schedule, click the **Create schedule** link below the **Incremental Crawl** list. + + +15. Click **OK**. + + + diff --git a/SharePoint/configure-and-use-the-lotus-notes-connector-for-sharepoint-server.md b/SharePoint/configure-and-use-the-lotus-notes-connector-for-sharepoint-server.md new file mode 100644 index 0000000000..d8a61496e3 --- /dev/null +++ b/SharePoint/configure-and-use-the-lotus-notes-connector-for-sharepoint-server.md @@ -0,0 +1,528 @@ +--- +title: Configure and use the Lotus Notes connector for SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: a7960bf4-d5be-4ad7-a430-724ef194ad39 +--- + + +# Configure and use the Lotus Notes connector for SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-26* **Summary:** Learn about the administrative roles, required software, user accounts, and processes that are required to install and operate the Lotus Notes Client and the Lotus Notes Connector to work with SharePoint Server 2016 and SharePoint Server 2013 search.In this article: +- [Before you begin](#begin) + + +- [Prerequisites](#LN_Prereqs) + + +- [Install the Lotus Notes client application](#LN_Install_LN_Client) + + +- [Grant permissions on the data folder](#LN_GrantPerm) + + +- [Configure the Lotus Notes client application](#LN_ConfigClient) + + +- [Verify access to the Lotus Domino database that you want to crawl](#LN_VerifyAccess) + + +- [Configure security mappings](#LN_ConfigSecMap) + + +- [Restart the server that hosts the crawl component](#LN_RestartCrawl) + + +- [Register Lotus Notes with the server that hosts the crawl component](#LN_RegisterLN) + + +- [Provision the Lotus Notes Connector](#LN_ProvisionLN) + + +- [Restart the OSearch15 service](#LN_RestartSearch) + + + +## Before you begin + + +Before you begin this operation, review the following information about prerequisites: +- [Required administrative roles](#LN_AdminRoles) + + +- [Required software](#LN_SWReq) + + +- [User accounts required to crawl Lotus Domino databases](#LN_UserAcc) + + +The procedures in this article must be repeated on all the servers in the SharePoint Server farm that host a crawl component. +## Prerequisites + + +The following sections list the required administrative roles, software and user accounts. +## Required administrative roles + + +The following administrative roles are required to prepare any server that hosts a crawl component to crawl Lotus Notes content that is hosted by one or more Lotus Domino databases: +- Administrator of the Lotus Domino server that you want to crawl. + + +- Server administrator of the server that hosts a crawl component that you want to use to crawl Lotus Notes content. + + +- Service application administrator for the Search service application. + + + +## Required software + + +The following software is required: +- Lotus C++ API Toolkit for Notes. + + +- Lotus Notes client application, available for purchase from IBM. + + +- Lotus Notes Domino Server, available for purchase from IBM. + + +The following table shows combinations of versions of the Lotus Notes Domino server and Lotus Notes client that the Lotus Notes Connector works with. +### + +This server version
With client 6.x
With client 7.x
With client 8.x
Server 6.x
YES
NO
NO
Server 7.x
NO
YES
YES
Server 8.x
NO
NO
YES
+## User accounts required to crawl Lotus Domino databases + + +A Domino administrator must grant a Lotus Notes user ID (which represents a Domino user) at least the Reader permission to the Lotus Domino databases and individual documents that you want to crawl. The Domino administrator must also add this Lotus Notes user ID and the Windows domain user account that is assigned to the SharePoint Server Search 15 service (OSearch15) to a mappings database on the Lotus Domino server that you want to crawl. +> [!NOTE:] + + + + + +The following table summarizes the user accounts that are required to crawl Lotus Domino databases. +### + +Required account Comment Example Windows domain user account
The user account that is assigned to the OSearch15 service must also be a member of the Administrators group on the server that hosts the crawl component.
Contoso\\User1, where Contoso is the domain name and User1 is the name of the Windows domain user account.
Lotus Notes user ID
The Lotus Notes user ID must be granted at least Reader access on the Lotus Domino databases and on the individual documents that you want to crawl. The Domino certificate also contains this Lotus Notes user ID.
User2
+> [!NOTE:] + + + + + +More information about this mappings table is provided later in this article, see [Configure security mappings](#LN_ConfigSecMap). +## Install the Lotus Notes client application + + +Follow this procedure to install the Lotus Notes client application on the server that hosts the crawl component in the server farm that you want to use to crawl a Lotus Domino database. This client application serves as a protocol handler and is used to configure the Notes.ini file. Both are used by the crawler when crawling Lotus Domino databases. **To install Lotus Notes** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that hosts the crawl component and has at least Manager permissions on the Domino server. + + +2. Copy the Lotus Notes client application to the server that hosts the crawl component that you want to use to crawl Lotus Notes documents. + + +3. Start the Lotus Notes Installation Wizard. + + +4. In the **Welcome to the Installation Wizard for Lotus Notes** dialog box, click **Next**. + + +5. On the License Agreement page, click **I accept the terms in the license agreement**, and then click **Next** to continue. + + +6. On the Customer Information page, type a user name in the **User Name** box and the name of the organization in the **Organization** box, or accept the default settings, and then click **Next**. + + +7. On the Installation Path Selection page, specify the path for the program and data files, or accept the default installation paths, and then click **Next**. + + > [!NOTE:] + +8. On the Custom Setup page, select the program features that you want to install on the local hard disk drive, and then click **Next**. + + The following table shows the features and sub-features that are required by the Lotus Notes connector. + +### + +Feature Subfeature Notes Client
Client Help Files

Domino Enterprise Connection Services (DECS)
Domino Designer
Designer Help
9. On the Ready to Install the Program page, if you do not want Lotus Notes to be the default email program, clear the selection **Make Notes my default email program**. + + +10. Click **Install**. + + The Installing Lotus Notes page shows the status of the installation. + + +11. On the Install Wizard Completed page, click **Finish**. + + + +## Grant permissions on the data folder + + +Follow this procedure to grant Full Control permissions for the WSS_WPG group on the ** :\\Program Files (x86)\\Lotus\\Notes\\Data folder on the server that hosts the crawl component. **To grant permissions on the data folder** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that hosts the crawl component and has at least Manager permissions on the Domino server. + + +2. On the server that hosts the crawl component, click **Start**, point to **All Programs**, click **Accessories**, and then click **Windows Explorer**. + + +3. In Windows Explorer, go to the ** :\\Program Files (x86)\\Lotus\\Notes\\Data folder, where ** is the drive on which Lotus Notes is installed. + + +4. Right-click the **Data** folder, and then click **Sharing and Security**. + + +5. In the **Properties** dialog box, on the **Security** tab, click **Add**. + + +6. In the **Select the object names to select** box, do one of the following, and then click **OK**: + + - If search is installed on an Active Directory domain controller, type *domain* \\ **WSS_WPG**, where *domain* is the name of the domain that is associated with the domain controller. + + + - If search is installed on a server that is not an Active Directory domain controller, type *server* \\ **WSS_WPG**, where *server* is the NetBIOS name of the server that hosts the crawl component. + + +7. In the **Properties** dialog box, in the **Permissions for WSS_WPG** section, select the **Allow** box in the **Full control** row, and then click **OK**. + + + +## Configure the Lotus Notes client application + + +Follow this procedure to configure the Lotus Notes client application. The configuration settings selected in this procedure are written to the Notes.ini file, which the crawler uses to discover how to connect to the Lotus Domino server. **To configure Lotus Notes** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that hosts the crawl component and has at least Manager permissions on the Domino server. + + +2. On the server that hosts the crawl component, click **Start**, point to **All Programs**, point to **Lotus Applications**, and then click **Lotus Notes**. + + +3. On the Welcome page, click **Next**. + + +4. On the User Information page, in the **Your name** box, type the user name associated with the Domino certificate. + + +5. Type the hierarchical name of the Domino server that you want to crawl in the **Domino server** box. For example, **Contoso/marketing/west**. + + +6. Ensure that **I want to connect to a Domino server** is selected, and then click **Next**. + + +7. On the Notes ID File page, click **Browse**, and then locate where the certificate is stored. Select the certificate, click **Open**, and then click **Next**. + + +8. Click **Yes** to copy the certificate to the specified location. + + > [!NOTE:] + +9. If a dialog box appears that informs you that you are not authorized to access the specified directory, click **OK** to close the dialog box. This error is expected if the account that you are logged on with does not have access to the email folder on the Domino server. + + +10. On the Instant Messaging Setup page, cancel the selection **Setup instant messaging**. + + +11. Click **Next**. + + +12. On the Additional Services page, click **Next**. + + +13. In the **Lotus Notes message** box, click **OK**. + + The Lotus Notes Welcome screen appears. + + Leave the Lotus Notes client application open. You will need it for the next procedure. + + + +## Verify access to the Lotus Domino database that you want to crawl + + +Follow this procedure to verify that the certificate that you installed has access to the database that you want to crawl. **To verify access** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that hosts the crawl component and has at least Manager permissions on the Domino server. + + +2. In Lotus Notes, click **File**, point to **Database**, and then click **Open**. + + +3. In the **Open Database** dialog box, select the Lotus Domino server that you want to connect to from the **Server** list. + + +4. In the **Database** list, select the database that you want to connect to, and then click **Open**. + + The documents that are contained by the database that you selected are displayed in the **Document Name** section. This means that the server that hosts the crawl component as the necessary permissions to crawl these documents. + + +5. Repeat steps 1 to 3 for each additional database that you want to verify access to. + + +6. On the **File** menu, click **Exit Notes**. + + + +## Configure security mappings + + +Use the information in the following table to help you create the mappings database. +### + +Item Description Mappings database name
Name of the Lotus Domino database that maps Lotus Notes user IDs to Windows domain user accounts.
Lotus Notes field name
Name of the field in the Lotus Domino database file that stores Lotus Notes user IDs.
Windows user field name
Name of the field in the Lotus Domino database file that stores Windows user names.
Form name
Name of the form that stores the **Lotus Notes field name** and **Windows user field name** fields.
View name
Name of the view for the form that stores the Lotus Notes user IDs to Windows user name mappings.
+> [!NOTE:] + + + + + + +## Create the mappings database + +Follow this procedure to create a mappings database by using Domino Designer. You only require one mappings database for each forest of Domino servers that contain databases that you want to crawl. **To create a mappings database** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that hosts the crawl component and has at least Manager permissions on the Domino server that you want to crawl. + + +2. On the server that hosts the crawl component, open Domino Designer. + + +3. Click **File**, point to **Database**, and then click **New**. + + +4. In the **New Database** dialog box, do the following: + +1. Select the Domino server from the **Server name** list. + + +2. In the **Title** box, type a title for the new database. + + This content automatically populates the **File Name** box, and it is appended with the .nsf file name extension. + + If the title that you chose is more than eight characters long, the file name will be truncated. + + +3. Click **OK** to close the **New Database** dialog box. + + +5. Click **Create**, point to **Design**, and then click **Form**. + + +6. Click **Create**, and then click **Field**. + + +7. In the **Field** dialog box, in the **Name** box, type the name that you want to use for this field. This field will be used to store the Lotus Notes user IDs. + + +8. Close the dialog box to save the field. + + +9. Click **Create**, and then click **Field**. + + +10. In the **Field** dialog box, in the **Name** box, type the name that you want to use for this field. This field will be used to store the Windows domain user accounts. + + +11. Close the dialog box to save the field. + + +12. Click **File**, click **Save**, and then do the following: + +1. Type a name in the **Save Form as** box. + + +2. Click **OK** to close the dialog box. + + +13. On the **Create** menu, point to **Design**, and then click **View**. + + +14. In the **Create View** dialog box, do the following: + +1. In the **View name** box, type a name for this view. + + +2. Select **Shared** from the **View type** list. + + +3. Click **OK** to save the view. + + +15. Open the view that you created in step 14. + + +16. On the **Objects** tab, select the column that you created in step 7. In the lower right pane, select **Field** and then select the field that has the same name. + + +17. On the **Objects** tab, select the column that you created in step 10. In the lower right pane, select **Field** and then select the field of the same name. + + +18. Click **File** and then click **Save** to save the view, and then close Domino Designer. + + + +## Add user accounts to the mappings database + +Follow this procedure to add user accounts to the mappings database using the Lotus Notes client. You should add all accounts which require access to the mappings database and the Domino server. **To add user accounts to the mappings database** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that hosts the crawl component and has at least Manager permissions on the Domino server. + + +2. On the server that hosts the crawl component, open the Lotus Notes client application. + + +3. Click **File**, point to **Database**, and then click **Open**. + + +4. In the **Open Database** dialog box, do the following: + +1. Select the Domino server from the **Server name** list. + + +2. Select the mappings database that you created earlier. + + +3. Click **Open**. + + +5. In the left pane, select the view that you created for this database. + + +6. Click **Create**, and then click the name of the form that you created earlier. + + +7. In the form, in the field that you created to store the Lotus Notes user IDs, type a Lotus Notes user ID that you want to map to a Windows domain user account. For example, **ContosoUser**. This field is case-sensitive. + + +8. In the field that you created to map to the Lotus Notes user IDs, type the Windows domain user account that you want to map to the Lotus Notes user ID that you entered in step 7. This must be in the form of domain\\user, for example, **Contoso\\user1**. + + +9. Click **File**, and then click **Save** to save the document. + + +10. Repeat steps 6to 8 if you want to add more mappings. Otherwise, go to step 11. + + +11. When finished, save the form and then close the Lotus Notes client application. + + + +## Restart the server that hosts the crawl component + + +You must restart the server that hosts the crawl component before continuing to the next procedure. +> [!IMPORTANT:] + + + + + + +## Register Lotus Notes with the server that hosts the crawl component + + +Following this procedure to register Lotus Notes with the operating system of the server that hosts the crawl component. **To register Lotus Notes** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that hosts the crawl component. + + +2. Run Notessetup.exe on the server that hosts the crawl component by using the same credentials that are used to provision the Lotus Notes Connector. + + +3. On the server that hosts the crawl component, in Windows Explorer, go to the ** :\\Program Files\\Microsoft Office Servers\\15\\Bin\\1033 folder, where ** is the drive on which Microsoft SharePoint Server is installed. + + +4. Double-click **NotesSetup.exe**. + + +5. On the Welcome to the Lotus Notes Index Setup Wizard page, click **Next**. + + +6. In the **Register Lotus Notes for use with SharePoint Server** dialog box, do the following: + +1. In the **Location of the notes.ini file** box, ensure that the correct path of the Notes.ini file is specified. The default path of this file is ** :\\Program Files (x86)\\lotus\\notes\\notes.ini, where ** is the drive on which Lotus Notes is installed. + + +2. In the **Location of the Lotus Notes install directory** box, ensure that the correct path of the Lotus Notes installation directory is specified. By default, the path of this directory is ** :\\Program Files (x86)\\lotus\\notes. + + +3. In the **Password** box, type the password for the user name that is associated with the Domino certificate. + + +4. In the **Confirm Password** box, retype the password for the user name that is associated with the Domino certificate. + + +7. We recommend that you leave the **Ignore Lotus Notes security while building the index** box cleared. This allows the crawl to include all Lotus Notes documents in the search index without restriction. Security for these documents and objects is determined by the mappings table and provides security data without excluding documents from the index. + + +8. Click **Next**. + + +9. On the Specify Lotus Notes Owner Field to Windows User Name Mapping page, do the following: + +1. In the **Lotus Notes server name** box, type the NetBIOS name or IP address of the Domino server. + + +2. In the **Lotus Notes database file name** box, type the file name of the Lotus Domino database that maps the Lotus Notes user IDs to Windows domain user accounts. Ensure that you include the .nsf file name extension with this name, for example, **Mappings.nsf**. + + +3. In the **View name** box, type the view name of the Lotus Domino database that stores the Lotus Notes user IDs to Windows user name mappings. + + +4. In the **Lotus Notes field name column title** box, type the name of the column in the Lotus Notes database file that is used to store Lotus Notes user IDs. + + +5. In the **Windows user name column title** box, type the name of the column in the Lotus Notes database file that is used to store the Windows user accounts. + + +10. Click **Next**. + + +11. On the Completing the Lotus Notes Index Setup Wizard page, click **Finish**. + + + +## Provision the Lotus Notes Connector + + +Follow this procedure to provision the Lotus Notes Connector with the operating system of the server that hosts the crawl component. **To provision Lotus Notes** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that hosts the crawl component. + + +2. Open SharePoint Central Administration. In the System Settings section, click **Manage services on Server**. + + +3. On the Services on Server page, in the Service column, find the Lotus Notes Connector service. + + +4. In the Action column, click **Start**. + + +5. On the Lotus Notes connector settings page, in the application pool section, select **Create new application pool**, and then enter a name for the new application pool. + + +6. In the Configurable drop-down, select or register the same security account used for installation of the NotesSetup.exe. + + +7. Click **Provision**. + + +The Lotus Notes connector is now provisioned and started. +## Restart the OSearch15 service + + +The server administrator of the server that hosts the crawl component must restart the OSearch15 service before a content source can be created for Lotus Domino databases. +> [!IMPORTANT:] + + + + + + **To restart the OSearch15 service** +1. Verify that the user account that is performing this procedure is an administrator for the server that hosts the crawl component. + + +2. Open a command prompt window. + + +3. To stop the OSearch15 service, type this command: **net stop osearch15** + + +4. To start the OSearch15 service, type this command: **net start osearch15** + + + diff --git a/SharePoint/configure-authoritative-pages-in-sharepoint-server.md b/SharePoint/configure-authoritative-pages-in-sharepoint-server.md new file mode 100644 index 0000000000..1cc6420abc --- /dev/null +++ b/SharePoint/configure-authoritative-pages-in-sharepoint-server.md @@ -0,0 +1,70 @@ +--- +title: Configure authoritative pages in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 6bf64b3d-edf0-4d2a-a1f5-b53318a24a1a +--- + + +# Configure authoritative pages in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Learn how to specify authoritative pages and non-authoritative URLs and sites. Search uses the list of authoritative pages to calculate the ranking of results.Static rank determines the relative importance of a page, and it is computed as the smallest number of clicks it would take a user to navigate from an authoritative page to a document. The closer a document is to the most authoritative page, the higher its static rank is.An administrator provides a small set of authoritative pages. An example of an authoritative page could be the home page of a company portal. An administrator with specific knowledge of an area can influence the relative importance of pages by specifying additional authoritative and non-authoritative pages. An example of non-authoritative pages could be URLs of sites that contain outdated information that are kept for record-keeping In this article: +- [Before you begin](#begin) + + +- [Specify pages as authoritative or non-authoritative](#BKMK_SpecifyWebPagesAsAuthoritative) + + + +## Before you begin + + + +> [!NOTE:] +> [Plan browser support](https://go.microsoft.com/fwlink/p/?LinkId=246502)> **Accessibility for SharePoint 2013**> [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)> [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504)> [Touch](https://go.microsoft.com/fwlink/p/?LinkId=246506) + + + + +Before you begin this operation, review the following information about prerequisites: +- Create a Search service application. + + + +## Specify pages as authoritative or non-authoritative + + +Use the following procedure to specify pages as authoritative or non-authoritative. **To specify pages as authoritative or non-authoritative** +1. Verify that the user account that is performing this procedure is an administrator for the Search service application. + + +2. In Central Administration, in the **Application Management** section, click **Manage service applications**. + + +3. Click the Search service application. + + +4. On the Search Administration page, in the Quick Launch, click **Authoritative Pages**. + + +5. On the Specify Authoritative Pages page, in the **Most authoritative pages** box in the **Authoritative Web Pages** section, type the URLs of pages that are the most authoritative. Separate the URLs with returns so that there is one URL per line. + + +6. In the **Second-level authoritative pages** box, type the URLs of any pages that should be seen as second-level. + + +7. In the **Third-level authoritative pages** box, type the URLs of any pages that should be seen as third-level. + + +8. In the **Non-authoritative Sites** section, in the **Sites to demote** box, type the URLs of any sites that you want to be ranked lower than all of the other sites. Type one URL per line. + + All URLs whose prefix matches the prefix of a URL in the **Sites to demote** box are demoted. Example: Entering **http://archive/** demotes the rank of all URLs that begin with **http://archive/**. + + +9. In the **Relevance Ranking Analytics** section, select the **Refresh now** check box to run the ranking analytics you have defined or that you have updated. + + If you clear the check box, ranking analytics run later according to a defined schedule. + + +10. Click **OK**. + + + diff --git a/SharePoint/configure-automatic-password-change-in-sharepoint-server.md b/SharePoint/configure-automatic-password-change-in-sharepoint-server.md new file mode 100644 index 0000000000..f0247e816c --- /dev/null +++ b/SharePoint/configure-automatic-password-change-in-sharepoint-server.md @@ -0,0 +1,233 @@ +--- +title: Configure automatic password change in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 5eccfa5b-05ec-46b6-935c-a2d8487965da +--- + + +# Configure automatic password change in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-25* **Summary:** Learn about how to configure the automatic password changes in SharePoint Server 2016 and SharePoint 2013.Automatic password change enables SharePoint Server to automatically generate long, encrypted passwords on a schedule that you can determine. In this article: +- [Configure managed accounts](#section1) + + +- [Configure automatic password change settings](#section2) + + +- [Troubleshooting automatic password change](#section3) + + + +## Configure managed accounts + + +You have to register managed accounts together with the farm to make the accounts available to multiple services. You can register a managed account by using the Register Managed Account page in the SharePoint Central Administration website. There are no options on the Register Managed Account page to create an account in Active Directory Domain Services, or on the local computer. The options can be used to register an existing account on the SharePoint Server farm. Perform the steps in the following procedure to use Central Administration to configure managed account settings. **To configure managed account settings by using Central Administration** +1. Verify that the user account that is performing this procedure is a farm administrator. + + +2. On the Central Administration, select **Security**. + + +3. Under **General Security**, click **Configure managed accounts**. + + +4. On the Managed Accounts page, click **Register Managed Account**. + + +5. In the **Account Registration** section of the Register Managed Account page, enter the service account credentials. + + +6. In the **Automatic Password Change** section, select the **Enable automatic password change** check box to allow UNRESOLVED_TOKEN_VAL(MOSS_2nd_NoVe) to manage the password for the selected account. Next, enter a numeric value that indicates the number of days before password expiration that the automatic password change process will be initiated. + + +7. In the **Automatic Password Change** section, select the **Start notifying by e-mail** check box, and then enter a numeric value that indicates the number of days before the initiation of the automatic password change process that an e-mail notification will be sent. You can then configure a weekly or monthly e-mail notification schedule. + + +8. Click **OK**. + + + +## Configure automatic password change settings + + +Use the Password Management Settings page of Central Administration to configure farm-level settings for automatic password changes. Farm administrators can configure the notification e-mail address that will be used to send all password change notification e-mails in addition to monitoring and scheduling options. Perform the steps in the following procedure to use Central Administration to configure automatic password change settings. **To configure automatic password change settings by using Central Administration** +1. Verify that the user account that is performing this procedure is a farm administrator. + + +2. On the Central Administration Home page, click **Security**. + + +3. Under **General Security**, click **Configure password change settings**. + + +4. In the **Notification E-Mail Address** section of the Password Management Settings page, enter the e-mail address of one person or group to be notified of any imminent password change or expiration events. + + +5. If automatic password change is not configured for a managed account, enter a numeric value in the **Account Monitoring Process Settings** section that indicates the number of days before password expiration that a notification will be sent to the e-mail address configured in the **Notification E-Mail Address** section. + + +6. In the **Automatic Password Change Settings** section, enter a numeric value that indicates the number of seconds that automatic password change will wait (after notifying services of a pending password change) before starting the change. Enter a numeric value that indicates the number of times a password change will be tried before the process stops. + + +7. Click **OK**. + + + +## Troubleshooting automatic password change + + +Use the following guidance to avoid the most common issues that can occur when you configure automatic password change. +## Password mismatch + +If the automatic password change process fails because there is a password mismatch between Active Directory Domain Services (AD DS) and UNRESOLVED_TOKEN_VAL(MOSS_2nd_NoVe), the password change process can result in access denial at logon, an account lockout, or AD DS read errors. If any of these issues occur, make sure that your AD DS passwords are configured correctly and that the AD DS account has read access for setup. Use Microsoft PowerShell to fix any password mismatch issues that might occur, and then resume the password change process. **To correct for a password mismatch by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + - Add memberships that are required beyond the minimums above. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2016 cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. From the PowerShell command prompt, type the following: + + ``` + +Set-SPManagedAccount [-Identity] -ExistingPassword -UseExistingPassword $true + ``` + + + For more information, see **Set-SPManagedAccount**. + + + +## Service account provisioning failure + +If service account provisioning or re-provisioning fails on one or more servers in the farm, check the status of the Timer Service. If the Timer Service has stopped, restart it. Consider using the following Stsadm command to immediately start Timer Service administration jobs: stsadm -o execadmsvcjobsIf restarting the Timer Service does not resolve the issue, use PowerShell to repair the managed account on each server in the farm that has experienced a provisioning failure. **To resolve a service account provisioning failure** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + - Add memberships that are required beyond the minimums above. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. From the PowerShell command prompt, type the following: + + ``` + +Repair-SPManagedAccountDeployment + ``` + + + For more information, see **Repair-SPManagedAccountDeployment**. + + +If the previous procedure does not resolve a service account provisioning failure, it is likely because the farm encryption key cannot be decrypted. If this is the issue, use PowerShell to update the local server pass phrase to match the pass phrase for the farm. **To update the local server pass phrase** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + - Add memberships that are required beyond the minimums above. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. From the PowerShell command prompt, type the following: + + ``` + +Set-SPPassPhrase -PassPhrase -ConfirmPassPhrase -LocalServerOnly $true + ``` + + + For more information, see **Set-SPPassPhrase**. + + + +## Imminent password expiration + +If the password is about to expire, but automatic password change has not been configured for this account, use PowerShell to update the account password to a new value that can be chosen by the administrator or automatically generated. After you have updated the account password, make sure that the Timer Service is started and the Administrator Service is enabled on all servers in the farm. Then, the password change can be propagated to all of the servers in the farm. +> [!NOTE:] + + + + + + **To update the account password** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + - Add memberships that are required beyond the minimums above. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint Management Shell. + + +3. To update the account password to a new automatically generated value, from the PowerShell command prompt, type the following: + + ``` + +Set-SPManagedAccount [-Identity] -AutoGeneratePassword $true + ``` + + + For more information, see **Set-SPManagedAccount**. + + + +## Requirement to change the farm account to a different account + +If you must change the farm account to a different account, use the following Stsadm command: stsadm.exe -o updatefarmcredentials -userlogin DOMAIN\\username -password password diff --git a/SharePoint/configure-availability-and-recovery-solutions-for-sharepoint-server-2016.md b/SharePoint/configure-availability-and-recovery-solutions-for-sharepoint-server-2016.md new file mode 100644 index 0000000000..d07b1c93a8 --- /dev/null +++ b/SharePoint/configure-availability-and-recovery-solutions-for-sharepoint-server-2016.md @@ -0,0 +1,33 @@ +--- +title: Configure availability and recovery solutions for SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: be4e1054-ada6-4eea-a92d-e35d1da61eb9 +--- + + +# Configure availability and recovery solutions for SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-09* **Summary: ** Learn about the options for providing high availability and disaster recovery solutions for SharePoint Server 2016.The following article on TechNet provides information about installing and configuring high availability and disaster recovery solutions for a SharePoint Server 2016 farm.The articles in this section assume that you are familiar with the concepts and terms presented in [High availability and disaster recovery concepts in SharePoint Server](html/high-availability-and-disaster-recovery-concepts-in-sharepoint-server.md) and [Plan for high availability and disaster recovery for SharePoint Server](html/plan-for-high-availability-and-disaster-recovery-for-sharepoint-server.md). +### + +ContentDescription
![Building blocks](images/) [Configure SQL Server AlwaysOn Availability Groups for SharePoint Server 2016](html/configure-sql-server-alwayson-availability-groups-for-sharepoint-server-2016.md)
Describes how to install and configure a Microsoft SQL Server 2014 with Service Pack 1 (SP1) or Microsoft SQL Server 2016 AlwaysOn Availability Group for a SharePoint farm.

[Replicate a multi-tier SharePoint application for disaster recovery using Azure Site Recovery](https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-sharepoint)
This Microsoft Azure topic describes how to protect a three-tier SharePoint Server 2016 farm using Azure Site Recovery.
+# See also + +#### + + [Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=718033&clcid=0x409) + + + + [Creation and Configuration of Availability Groups (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=724040&clcid=0x409) + + + + [Azure Site Recovery](https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-overview) + + + + + + + + diff --git a/SharePoint/configure-backup-and-restore-permissions-in-sharepoint-server.md b/SharePoint/configure-backup-and-restore-permissions-in-sharepoint-server.md new file mode 100644 index 0000000000..582da5b3e3 --- /dev/null +++ b/SharePoint/configure-backup-and-restore-permissions-in-sharepoint-server.md @@ -0,0 +1,168 @@ +--- +title: Configure backup and restore permissions in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 3a25437a-e994-42c7-b4df-ac9fa29f38f5 +--- + + +# Configure backup and restore permissions in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-06-20* **Summary:** Learn how to configure permissions for backup and restore operations in SharePoint Server 2016 and SharePoint Server 2013.You can configure backup and restore permissions for SharePoint Server by using the SharePoint Central Administration website or PowerShell. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have made with your organization.In this article: +- [Before you begin](#begin) + + +- [Permissions for the SPTimerV4 timer service and SQL Server account in SharePoint Server](#proc1) + + +- [Group memberships required to run backup and restore operations in Central Acministration](#proc2) + + +- [Setting permissions to run SharePoint backup and restore operations by using Windows PowerShell](#proc3) + + + +## Before you begin + + +Before you back up or restore SharePoint Server, you must make sure that the timer service account, SQL Server service account, and users who run the backup or restore operations have the correct permissions or are members of the correct Windows security groups or SharePoint groups. You must configure these permissions and group memberships when you first deploy SharePoint Server. You have to update permissions and group memberships when you add new farm components to the environment and if you want to add users who will perform backup and restore operations. +## Permissions for the SharePoint Timer service and SQL Server account in SharePoint Server + + +The SharePoint Timer Server and the SQL Server service account in SharePoint Server perform backup and restore operations on behalf of users. These service accounts require Full Control permissions on any backup folders. +## Group memberships required to run backup and restore operations in Central Administration + + +You must make sure all user accounts that use Central Administration to back up or restore your farm and farm components have the group memberships that are described in the following table. +### + +Farm component Member of Administrators group on the local computer Member of Farm Administrators SharePoint group Farm
Yes
No
Service Application
Yes
No
Content Database
Yes
No
Site Collection
No
Yes
Site, list, document library
No
Yes
+## Setting permissions to run SharePoint backup and restore operations by using PowerShell + + +You must make sure that all user accounts that use PowerShell to back up or restore your farm and farm components are added to the **SharePoint_Shell_Access** role for a specified database and have the permissions described in the table later in this section.You can run the **Add-SPShellAdmin** cmdlet to add a user account to this role. You must run the command for each user account. Moreover, you must run the command for all databases to which you want to grant access. +> [!NOTE:] + + + + + + +> [!IMPORTANT:] + + + + + + **To add a user to or remove a user from the SharePoint_Shell_Access role by using PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Start the SharePoint 2016 Management Shell or the SharePoint 2013 Management Shell. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Add-SPShellAdmin -Username -Database + ``` + + + + + Where: + + - ** is the GUID assigned to the database. + + + + To add a user account to all the databases in the farm, type the following command: + + + + ``` + ForEach ($db in Get-SPDatabase) {Add-SPShellAdmin -Username -Database $db} + ``` + + + + + Where: + + - ** is the user whose account you want to add. + + + + To remove a user account from all the databases in the farm, type the following command: + + + + ``` + ForEach ($db in Get-SPDatabase) {Remove-SPShellAdmin -Username -Database $db} + ``` + + + + + Where: + + - ** is the user whose account you want to remove. + + + + To view the user accounts currently added to the databases in the farm, type the following command: + + + + ``` + ForEach ($db in Get-SPDatabase) {Get-SPShellAdmin -Database $db} + ``` + + + + + +For more information, see **Add-SPShellAdmin**. +> [!NOTE:] + + + + + +You might also have to grant additional permissions to the users who run the backup or restore operation by using PowerShell. The following table shows the permissions that are required. +### + +Farm component Member of Administrators group on the local computer Member of Farm Administrators SharePoint group Full control on backup folder Farm
Yes
No
Yes
Service Application
Yes
No
Yes
Content Database
Yes
No
Yes
Site Collection
No
Yes
Yes
Site, list, document library
Yes
No
Yes
+# See also + +#### + + [Plan for backup and recovery in SharePoint Server](html/plan-for-backup-and-recovery-in-sharepoint-server.md) + + + + [Prepare to back up and restore farms in SharePoint Server](html/prepare-to-back-up-and-restore-farms-in-sharepoint-server.md) + + + + [Overview of backup and recovery in SharePoint Server](html/overview-of-backup-and-recovery-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-business-connectivity-services-solutions-for-sharepoint-server.md b/SharePoint/configure-business-connectivity-services-solutions-for-sharepoint-server.md new file mode 100644 index 0000000000..93147c8073 --- /dev/null +++ b/SharePoint/configure-business-connectivity-services-solutions-for-sharepoint-server.md @@ -0,0 +1,73 @@ +--- +title: Configure Business Connectivity Services solutions for SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: f255d39a-8231-42e7-957d-c4855b9ab529 +--- + + +# Configure Business Connectivity Services solutions for SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-07* **Summary: ** Find links to steps that will help you install and configure SharePoint Server Business Connectivity Services (BCS). Choose from on-premises, cloud-only, and hybrid BCS solutions.This article is your starting place for the procedures to install common Microsoft Business Connectivity Services scenarios for SharePoint Server 2016. The Business Connectivity Services solution that you deploy will most likely look different from the solutions presented here, but you can model your installation on these examples. Also, you can select the individual procedures from here to build your own procedural documents for your Business Connectivity Services solution scenario. +## Choose the Business Connectivity Services scenario that meets your needs + +Every Business Connectivity Services solution is unique because each business has unique data integration problems that it solves with Business Connectivity Services. The solutions can range from something simple and straightforward that a power user or IT professional (who has the appropriate permissions) can perform by themselves, to complex solutions that require developer, IT professional, and end-user solution development involvement.This guide presents the configuration choices for the common scenarios. +- ** [On-premises deployment](#sectiononprem)**    All the Business Connectivity Services components are under your organizations control behind your firewall. + + +- ** [Cloud-only deployment](#sectioncloud)**    All the Business Connectivity Services components are in SharePoint Online. + + +- ** [Hybrid deployment](#sectionhybrid)**    SharePoint Online uses Business Connectivity Services to connect to data that lives in the cloud. + + + +## Prerequisites + + +Before you begin with any Business Connectivity Services scenario configuration, make sure that you have read [Overview of Business Connectivity Services in SharePoint Server](html/overview-of-business-connectivity-services-in-sharepoint-server.md) and completed the steps in [Plan a Business Connectivity Services solution in SharePoint Server](html/plan-a-business-connectivity-services-solution-in-sharepoint-server.md). +## On-premises deployment + + +The procedures in [Deploy a Business Connectivity Services on-premises solution in SharePoint Server](html/deploy-a-business-connectivity-services-on-premises-solution-in-sharepoint-serve.md) show you how to deploy a solution that involves the following: +- A Business Connectivity Services infrastructure that is on your corporate network. + + +- Information workers who access the Business Connectivity Services solution are on your corporate network. + + +- External content that is surfaced in SharePoint as an external list. + + +- External content that is synchronized into Microsoft Outlook for offline use. + + +- Accessing external data that is in SQL Server database on your corporate network. + + +- SharePoint Designer 2013 to create the external content type for the SQL Server data source. + + +- The Secure Store Service to manage mapping of user credentials to group credentials for accessing the external systems. + + + +## Cloud-only deployment + + +The procedures in [Make an External List from a SQL Azure table with Business Connectivity Services and Secure Store](https://support.office.com/article/466f3809-fde7-41f2-87f7-77d9fdadfc95) **Deploy a Business Connectivity Services cloud-only solution in SharePoint 2013** show you how to deploy a solution that involves a Business Connectivity Services infrastructure that is in SharePoint Online. +## Hybrid deployment + + +The procedures in [Deploy a Business Connectivity Services hybrid solution in SharePoint](html/deploy-a-business-connectivity-services-hybrid-solution-in-sharepoint.md) shows you how to publish on-premises data to an external list or app for SharePoint in SharePoint Online. +# See also + +#### + + [Plan for Business Connectivity Services in SharePoint Server](html/plan-for-business-connectivity-services-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-cache-settings-for-a-web-application-in-sharepoint-server.md b/SharePoint/configure-cache-settings-for-a-web-application-in-sharepoint-server.md new file mode 100644 index 0000000000..6326afda92 --- /dev/null +++ b/SharePoint/configure-cache-settings-for-a-web-application-in-sharepoint-server.md @@ -0,0 +1,228 @@ +--- +title: Configure cache settings for a web application in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 478be4b7-1480-4f97-87c5-b18cd2436bce +--- + + +# Configure cache settings for a web application in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-19* **Summary: ** Learn how to configure the BLOB cache, page output cache profiles, and the object cache for a web application.This article describes how to configure the disk-based BLOB cache, the page output cache profiles, and the object cache for a web application in SharePoint Server 2016 and SharePoint Server 2013.You enable and configure the BLOB cache, and make configuration changes to the page output cache profiles and the object cache in the Web.config file in the web application to which you want to apply those changes. The changes you make to the Web.config file will be applied to all site collections within the web application. SharePoint Server 2016 includes cache performance monitors that let you verify that the farm cache settings are correct and that the caching is running at maximum performance. For more information, see [Monitor cache performance in SharePoint Server 2016](html/monitor-cache-performance-in-sharepoint-server-2016.md). +> [!NOTE:] + + + + + + +> [!TIP:] + + + + + +For more information, see [Cache settings operations in SharePoint Server](html/cache-settings-operations-in-sharepoint-server.md).In this article: +- [Configuring BLOB cache settings](#BLOB) + + +- [Configuring page output cache profile settings](#output) + + +- [Configuring object cache settings](#object) + + + +## Configure BLOB cache settings + + +By default, the disk-based BLOB cache is off and must be enabled on the front-end web server if you want to use it. Use the following procedure to configure disk-based cache settings for a web application. +> [!IMPORTANT:] + + + + + + **To configure BLOB cache settings** +1. Verify that you have the following administrative credentials: You must be a member of the Administrators group on the local computer to configure the BLOB cache settings. + + +2. Open **Server Manager**, click **Tools**, and then click **Internet Information Services (IIS) Manager**. + + +3. In Internet Information Services (IIS) Manager, in the **Connections** pane, expand the server name that contains the web application, and then expand **Sites** to view the web application or applications that have been created. + + +4. Right-click the name of the web application for which you want to configure the disk-based cache, and then click **Explore**. Windows Explorer opens, with the directories for the selected web application listed. + + +5. In the **Open With** dialog box, click **Notepad**, and then click **OK**. + + +6. In the web.config Notepad file, find the following line: + + > [!NOTE:] + +7. In this line, change the location attribute to specify a directory that has enough space to accommodate the cache size. + + > [!NOTE:] + +8. To add or remove file types from the list of file types to be cached, for the path attribute, modify the regular expression to include or remove the appropriate file extension. If you add file extensions, make sure to separate each file type with a pipe (|), as shown in this line of code. + + +9. To change the size of the cache, type a new number for maxSize. The size is expressed in gigabytes (GB), and 10 GB is the default. + + > [!IMPORTANT:] + +10. To enable the BLOB cache, change the enabled attribute, from"false" to"true". + + +11. Save the Notepad file, and then close it. + + + +> [!CAUTION:] + + + + + + +## Configure cache profile settings + + +Cache profile settings can be configured in the user interface at the site collection level by a site collection administrator, as well as at the web application level by an administrator on the front-end web server. The page output cache must be enabled at the site collection level before page output cache profiles can be configured at either the site collection level or web application level. If page output cache profiles are enabled at the web application level, the settings specified in Web.config will be used for all page output cache profiles, overriding any values that have been entered through the user interface at the site collection level. +> [!NOTE:] + + + + + + +> [!NOTE:] + + + + + +Use the following procedure to configure the cache profile settings for a web application. +> [!IMPORTANT:] + + + + + + **To configure page output cache profile settings** +1. Verify that you have the following administrative credentials: You must be a member of the Administrators group on the local computer to configure the cache profile settings. + + +2. Open **Server Manager**, click **Tools**, and then click **Internet Information Services (IIS) Manager**. + + +3. In Internet Information Services (IIS) Manager, in the **Connections** pane, expand the server name that contains the web application, and then expand **Sites** to view the web application or applications that have been created. + + +4. Right-click the name of the web application for which you want to configure the disk-based cache, and then click **Explore**. Windows Explorer opens, with the directories for the selected web application listed. + + +5. Right-click **web.config**, click **Open** and choose **Notepad** if you're asked to find a program to use to open this file. + + +6. In the web.config Notepad file, find the following line: + + +7. To enable the cache profile at the web application level, change the useCacheProfileOverrides attribute, from"false" to"true". + + > [!NOTE:] + +8. To override the varyByHeader attribute, type a custom parameter as specified in the .NET Framework Class Library entry [HttpCachePolicy.VaryByHeaders Property](https://msdn.microsoft.com/en-us/library/system.web.httpcachepolicy.varybyheaders%28v=vs.110%29.aspx). + + +9. To override the varyByParam attribute, type a custom parameter as specified in the .NET Framework Class Library entry [HttpCachePolicy.VaryByParams Property](http://go.microsoft.com/fwlink/p/?LinkId=164242&clcid=0x409). + + +10. To override the varyByCustom attribute, type a custom parameter as specified in the .NET Framework Class Library entry [HttpCachePolicy.SetVaryByCustom Method](http://go.microsoft.com/fwlink/p/?LinkId=164240&clcid=0x409). + + +11. To override the varyByRights attribute, change the value from"true" to"false". This will remove the requirement that users must have identical effective permissions on all securable objects to see the same cached page as any other user. + + +12. To override the cacheForEditRights attribute, change thecacheForEditRights attribute, from"false" to"true". This will bypass the normal behavior in which people with edit permissions have their pages cached. + + +13. Save the Notepad file, and then close it. + + + +> [!CAUTION:] + + + + + + +## Configure object cache settings + + +The object cache settings can be configured at the site collection level in the user interface by a site collection administrator, and is on by default. The maximum cache size can be configured at the web application level on the front-end web server to place a restriction on the maximum amount of memory that the cache will use for all site collections. For example, individual site collections might have the object cache set at 100 MB, while the web application might be set at 1 GB. In this case, no more than 1 GB of memory will be used by all the caches on the server. +> [!NOTE:] + + + + + +Use the following procedure to configure the object cache settings for a web application on a front-end web server. +> [!IMPORTANT:] + + + + + + **To configure object cache settings** +1. Verify that you have the following administrative credentials: You must be a member of the Administrators group on the local computer to configure the object cache settings. + + +2. Open **Server Manager**, click **Tools**, and then click **Internet Information Services (IIS) Manager**. + + +3. In Internet Information Services (IIS) Manager, in the **Connections** pane, expand the server name that contains the web application, and then expand **Sites** to view the web application or applications that have been created. + + +4. Right-click the name of the web application for which you want to configure the disk-based cache, and then click **Explore**. Windows Explorer opens, with the directories for the selected web application listed. + + +5. Right-click **web.config**, click **Open** and select **Notepad** if you're asked to find a program to use to open this file. + + +6. In the Web.config Notepad file, find the following line: + + +7. To change the size of the cache, type a new number for maxSize. The size is expressed in megabytes (MB), and 100 MB is the default. + + +8. Save the Notepad file, and then close it. + + + +> [!CAUTION:] + + + + + + +# See also + +#### + + [Cache settings operations in SharePoint Server](html/cache-settings-operations-in-sharepoint-server.md) + + + + [Plan for caching and performance in SharePoint Server](html/plan-for-caching-and-performance-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-cloud-hybrid-searchroadmap.md b/SharePoint/configure-cloud-hybrid-searchroadmap.md new file mode 100644 index 0000000000..86ce51e94e --- /dev/null +++ b/SharePoint/configure-cloud-hybrid-searchroadmap.md @@ -0,0 +1,329 @@ +--- +title: Configure cloud hybrid search - roadmap +ms.prod: SHAREPOINT +ms.assetid: 0bba350d-ec33-43db-a873-930559c78dee +--- + + +# Configure cloud hybrid search - roadmap + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Office 365, SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-21* Learn how to configure [cloud hybrid search](https://support.office.com/article/af830951-8ddf-48b2-8340-179c1cc4d291) for SharePoint Server by setting up a cloud Search service application in your SharePoint Server environment and connecting it to your search index in Office 365.This article describes how you set up cloud hybrid search in an environment with SharePoint Server and SharePoint OnlineSharePoint Online for Office 365 for enterprises. With the cloud hybrid search solution, you add crawled metadata from all your content, including on-premises content, to your search index in Office 365. When users search in Office 365, they get search results from both on-premises and from Office 365 content. +> [!NOTE:] + + + + + + +## Before you start + +To complete the configuration steps you’ll need these items: +- The [Hardware and software requirements for SharePoint Server 2016](html/hardware-and-software-requirements-for-sharepoint-server-2016.md) that’s needed in a SharePoint Server hybrid environment. + + +- A server or virtual machine for cloud hybrid search that has: + + - Minimum 100 GB storage, 16 GB RAM, and four 1.8 GHz CPUs. + + + - SharePoint Server installed. + + + - Is a member of a Windows Server Active Directory domain. + + +- (SharePoint Server 2013 only) You must have at least [Service Pack 1 and the January 2016 public update installed](https://technet.microsoft.com/library/mt715807.aspx). + + +- The [Accounts needed for hybrid configuration and testing](html/accounts-needed-for-hybrid-configuration-and-testing.md) that are needed in a SharePoint Server hybrid environment, a search account for cloud hybrid search in SharePoint Server, and a managed account for default content access in SharePoint Server. Ensure that the account has at least read access to the content to crawl. + + +- Your company's or organization’s SharePoint Online portal URL, such as https://.sharepoint.com + + +- The **CreateCloudSSA.ps1** and **Onboard-CloudHybridSearch.ps1** Microsoft PowerShell scripts, find them in the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=717902). + + +- The [search architecture plan](https://support.office.com/article/33926857-302c-424f-ba78-03286cf5ac30#Plan_search_architecture) you made for cloud hybrid search. + + + +## Follow these steps: + +If you already completed step 1 when you configured a different hybrid solution, skip that step and go to the next. +### + +Step
Description
**1. [Configure Office 365 for SharePoint hybrid](https://technet.microsoft.com/EN-US/library/mt125509.aspx)**
Configure your Office 365 tenant for a hybrid environment, including registering your domain, configuring UPN suffixes, and synchronizing your on-premises user accounts with Office 365.
**2. [Create a cloud Search service application in SharePoint Server 2016](#BKMK_CreateCloudSSA)**
Use the **CreateCloudSSA.ps1** PowerShellscript to create the cloud Search service application (cloud SSA) on the search farm that’s running SharePoint Server.
**3. [Set up search architecture in SharePoint Server 2016 for cloud hybrid search](#BKMK_SetupSearchArch) (Optional)**
If you planned a search architecture that’s different from the default one, set up the planned search architecture.
**4. [Connect your cloud Search service application to your Office 365 tenant](#BKMK_ConnectCloudSSAToO365)**
Use the **Onboard-CloudHybridSearch.ps1** PowerShell script to onboard your cloud SSA and Office 365 tenant to cloud hybrid search. The script sets up the cloud SSA to interact with the Office 365 tenant and also sets up server-to-server authentication.
**5. [Create a content source to crawl for cloud hybrid search](#BKMK_CreateOnPremContentSource)**
We recommend adding a small file share first, you can add more on-premises content later.
**6. [Set up a separate Search Center to validate hybrid search results in Office 365](#BKMK_SetupValidationSearchCenter)**
Keep the original search experience unchanged by setting up a separate Search Center in Office 365 for validation and tuning of the new search experience.
**7. [Start a full crawl of on-premises content for cloud hybrid search](#BKMK_StartFullCrawl)**
When the crawl completes, your on-premises content shows up in the search results in your validation Search Center in Office 365 and in Office Delve.
**8. [Verify that cloud hybrid search works](#BKMK_VerifyCloudHybridSearch)**
Go to your Search Center in SharePoint Online in Office 365 and enter this query: "IsExternalContent:true". The results you get should show content from the on-premises content source that you've crawled.
**9. [Tune cloud hybrid search](#BKMK_TuneCloudHybridSearch)**
Set up and tune the search experiences you’ve planned for your users.
**10. Remove the validation Search Center and expose all users to hybrid search results.**
Set your Search Center and any site search in Office 365 to use the default result source and set up the default result source with the search experiences that you’ve tuned. Your on-premises content shows up in the search results in your Search Center in Office 365, site search in Office 365, and in Office Delve.
+## Create a cloud Search service application in SharePoint Server 2016 + + +The cloud SSA lets you crawl and add metadata from on-premises content to the search index in Office 365. Each search farm can have only one cloud SSA, but can have multiple SSAs in combination with the cloud SSA. You can’t convert an existing SSA to a cloud SSA.You can create a cloud SSA in the SharePoint Central Administration website, just like an SSA. Here we describe how to create a cloud SSA by running the CreateCloudSSA.ps1 PowerShell script from the Microsoft Download Center. This script installs the cloud SSA and the default search architecture for cloud hybrid search. +> [!NOTE:] + + + + + +On the search server in SharePoint Server, follow these steps: +1. Run the **CreateCloudSSA.ps1** PowerShell script. + + +2. When prompted, type: + +1. The host name of the search server in SharePoint Server. + + +2. The Search service account in this format: domain\\username. + + +3. A name of your choice for the cloud SSA. + + +4. The name of the database server in SharePoint Server + + +3. Verify that you see the message that the cloud SSA was successfully created. + + + +## Can I make my own Windows PowerShell script for creating a cloud SSA? + +If you want to make your own PowerShellscript for creating a cloud SSA, first study the **CreateCloudSSA.ps1** PowerShell script we’ve provided. Notice that the difference between creating a cloud SSA and an SSA is the value of the property **CloudIndex**. You set **CloudIndex**: **true** when you create a cloud SSA (you can’t change this value later). When **CloudIndex** is true, crawled metadata **is not** added to the on-premises search index. However, this doesn’t mean that the metadata is added to the Office 365 search index, you have to onboard the cloud SSA to cloud hybrid search for that to happen (see [Connect your cloud Search service application to your Office 365 tenant](#BKMK_ConnectCloudSSAToO365)). Ensure that your PowerShell script: +- Tests that the Search service account is a managed account, and makes it a managed account if it isn’t. + + +- Includes -CloudIndex $true as an argument when it uses the New-SPEnterpriseSearchServiceApplication PowerShell cmdlet. + + + +## Set up search architecture in SharePoint Server 2016 for cloud hybrid search + + +If you planned to use the default search architecture that you get when creating a cloud SSA, you can skip this step.Otherwise, ensure that you have prepared the servers you need for your planned search architecture for cloud hybrid search, and follow the [guidance](https://technet.microsoft.com/en-us/library/jj862356.aspx) for setting up your [planned search architecture](https://support.office.com/article/33926857-302c-424f-ba78-03286cf5ac30#Plan_search_architecture). This guidance is applicable also for cloud hybrid search. +## Connect your cloud Search service application to your Office 365 tenant + + +This section guides you how to onboard your cloud SSA and Office 365 tenant to cloud hybrid search and covers: +- **Connecting your cloud SSA and your Office 365 tenant** - When your cloud SSA and your Office 365 tenant are correctly connected, the cloud hybrid search solution is ready to add crawled metadata from on-premises content to the search index in Office 365. When you’ve onboarded your cloud SSA, check to see that your cloud SSA has the value 1 for the property **IsHybrid**. You check by running this PowerShell command: $ssa.GetProperty("CloudIndex"). + + +- **Configuring server-to-server authentication** - Server-to-server authentication allows servers to access and request resources from one another on behalf of users. + + +On the search server in SharePoint Server follow these steps: +1. Ensure that the date and time of the server is synchronized with the other servers in the SharePoint Server farm. + + +2. Download and install the [Microsoft Online Services Sign-In Assistant for IT Professionals RTW](https://go.microsoft.com/fwlink/?LinkID=286152) from the Microsoft Download Center. + + +3. Download version 1.1.166.0 or newer of the [Azure Active Directory Module for Windows PowerShell](http://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=59185). Click **Run** to run the installer package. + + +4. Download the **OnBoard-CloudHybridSearch.ps1** PowerShell script from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=717902). + + +5. If your environment is Office 365 Business, Office 365 Enterprise, Office 365 Education, Office 365 operated by 21Vianet, Office 365 Germany, or Office 365 US Government Defense, open an elevated PowerShell prompt, and run the **OnBoard-CloudHybridSearch.ps1** PowerShell script as follows: + + ``` + +Import-Module MSOnline + ``` + + + ``` + +.\\OnBoard-CloudHybridSearch.ps1 -PortalUrl -CloudSsaId + ``` + + + **SPOTenantPortalUrl** is the URL of your company's or organization’s SharePoint Online portal, and ** CloudSsaID** is the name of the cloud SSA that you created earlier. + + +6. If your environment is Office 365 US Government Communication, open an elevated PowerShell prompt, and run the **OnBoard-CloudHybridSearch.ps1** PowerShell script as follows: + + ``` + +Import-Module MSOnline + ``` + + + ``` + +.\\OnBoard-CloudHybridSearch.ps1 -PortalUrl -CloudSsaId -IsPortalForUSGovernment $true + ``` + + + **SPOTenantPortalUrl** is the URL of your company's or organization’s SharePoint Online portal, and ** CloudSsaID** is the name of the cloud SSA that you created earlier. + + +7. When prompted, type the global admin credentials for your Office 365 tenant. + + + +## Create a content source to crawl for cloud hybrid search + + +We recommend that you start with a small on-premises content source, for example a small file share, to test. You can add more on-premises content sources later. +1. Verify that the user account that is performing this procedure is an administrator for the cloud SSA. + + +2. On the home page of Central Administration, in the **Application Management** section, click **Manage service applications**. + + +3. On the Manage Service Applications page, click the cloud SSA. + + +4. On the Search Administration Page, in the **Crawling** section, click ** Content Sources**. + + +5. On the Manage Content Sources page, click **New Content Source**. + + +6. On the Add Content Source page, in the **Name** section, in the **Name** box, type a name for the new content source. + + +7. In the **Content Source Type** section, select the type of content that you want to crawl. + + +8. In the **Start Addresses** section, in the **Type start addresses below (one per line)** box, type the URLs from which the crawler should begin crawling. + + +9. In the **Crawl Settings** section, select the crawling behavior that you want. + + +10. In the **Crawl Schedules** section, to specify a schedule for full crawls, select a defined schedule from the **Full Crawl** list. A full crawl crawls all content that is specified by the content source, regardless of whether the content has changed. To define a full crawl schedule, click **Create schedule**. + + +11. To specify a schedule for incremental crawls, select a defined schedule from the **Incremental Crawl list**. An incremental crawl crawls content that is specified by the content source that has changed since the last crawl. To define a schedule, click **Create schedule**. You can change a defined schedule by clicking **Edit schedule**. + + +12. To set the priority of this content source, in the **Content Source Priority** section, on the **Priority** list, select **Normal** or **High**. + + +13. Click **OK**. + + + +## Set up a separate Search Center to validate hybrid search results in Office 365 + + +After you’ve set up cloud hybrid search and completed a full crawl of your on-premises content, your Search Center in Office 365 will automatically show both on-premises and online search results. Before starting the full crawl, we recommend that you set up a separate Search Center to show the on-premises and online search results. This way you can keep the existing Search Center unchanged while you validate and tune the new search experience in the separate Search Center.Follow these steps to set up a separate Search Center in Office 365: +1. [Create a result source](https://support.office.com/en-au/article/Manage-result-sources-fd8d6ac6-c5d0-454d-80a9-51580902b25d) that retrieves search results from the search index of this tenant, but limits search results to Office 365 content by using a **Query Transform**. Change the default query transform to "(?(searchTerms) NOT IsExternalContent:true)". This works because content that has the managed property *IsExternalContent* set to true (see [About the IsExternalContent managed property](#BKMK_IsExternalContent)) in the SharePoint Online search schema, is on-premises content. + + +2. Modify the Search Results Web Part in your Office 365 Search Center to use the result source that you just created. Your users get the original search experience in this Search Center. + + +3. Create a second Office 365 Search Center that uses the default result source. This Search Center has hybrid search results when you’ve run a full crawl. Validate and tune your new search experience in this Search Center. + + +4. Set up access so only testers and administrators have access to the second Office 365 Search Center. + + +Here’s an example of a validation environment: + + + +![The illustration shows how content enters the Office 365 index from both a SharePoint Server content farm and from Office 365. The standard search center in Office 365 only retrieves Office 365 results from the search index, while the validation search ce](images/) + + + + + + + + + + + + +1. On-premises content. During crawl, content is added to the Office 365 index. + + +2. Office 365 content. During crawl, content is added to the Office 365 index. + + +3. Default (or existing) Office 365 Search Center. This Search Center uses the custom result source that limits search results to only Office 365 content. + + +4. Second Office 365 Search Center, where you validate and tune how hybrid search results are shown. This Search Center uses the default result source and shows search results from both on-premises and Office 365 content. + + + +## About the IsExternalContent managed property + + +An important part in this environment is the custom result source you use in the default or existing Office 365 Search Center. This result source keeps the search experience unchanged while you validate and tune how hybrid search results are displayed. An important piece in this custom result source is the *IsExternalContent* managed property in the SharePoint Online search schema. Before you set up cloud hybrid search, this managed property is empty. But, after you’ve set up cloud hybrid search and crawled your on-premises content, this property is set to true for all on-premises content. You limit search results to show only Office 365 content with *NOT IsExternalContent:true* . +## Start a full crawl of on-premises content for cloud hybrid search + + +Start a full crawl of the content source. See [Start, pause, resume, or stop a crawl in SharePoint Server 2013](https://technet.microsoft.com/en-us/library/jj219814%28v=office.15%29.aspx) or follow these steps: +1. Verify that the user account that is performing this procedure is an administrator for the Cloud Search service application. + + +2. On the home page of the SharePoint Central Administration website, in the **Application Management** section, click **Manage service applications**. + + +3. On the Manage Service Applications page, click the cloud Search service application. + + +4. On the Search Administration page, in the **Crawling** section, click **Content Sources**. + + +5. On the Manage Content Sources page, in the list of content sources, point to the name of the content source that you want to crawl, click the arrow and then click **Start Full Crawl**. The value in the **Status** column changes to **Crawling Full** for the selected content source. + + + +## Verify that cloud hybrid search works + + +After the full crawl completes, verify that your on-premises content shows up in the search results in your validation Search Center in Office 365. +1. Log in to Office 365 with your work or school account. Make sure that: + + - You have access to the validation Search Center. + + + - You have access to the content in the content source that you have crawled. If you performed step 1 of this roadmap, you should have access. + + + - Your organization hasn’t assigned user access rights to the on-premises content by using one of the default security groups in Windows Server Active Directory (AD), for example the Domain Users security group, see [Plan cloud hybrid search for SharePoint](https://support.office.com/article/33926857-302c-424f-ba78-03286cf5ac30). + + +2. Search for **IsExternalContent:1** in the validation Search Center. + + +3. Verify that your on-premises content shows up in the search results. + + + +## Tune cloud hybrid search + + +After you’ve set up cloud hybrid search and verified that you get search results from on-premises content in your validation Search Center in Office 365, set up the search experiences that you planned.You might find this guidance useful: +- With cloud hybrid search you manage the search schema in SharePoint Online in Office 365, just as you would in an Office 365 environment. Learn how in [Manage the Search Center in SharePoint Online](https://support.office.com/en-gb/article/Manage-the-Search-Center-in-SharePoint-Online-174d36e0-2f85-461a-ad9a-8b3f434a4213?ui=en-US&rs=en-GB&ad=GB). + + +- You manage how search results are displayed from the search schema in SharePoint Online, see [Manage the Search Center in SharePoint Online](https://support.office.com/en-us/article/Manage-the-Search-Center-in-SharePoint-Online-174D36E0-2F85-461A-AD9A-8B3F434A4213?ui=en-US&rs=en-US&ad=US). If you’ve set up site search in SharePoint Server to get search results the Office 365, you also manage how these results are displayed from the search schema in SharePoint Online. + + +- [Enable previews of on-premises search results in cloud hybrid search](html/enable-previews-of-on-premises-search-results-in-cloud-hybrid-search.md). + + +- [Show results from Office 365 in on-premises SharePoint with cloud hybrid search](html/show-results-from-office-365-in-on-premises-sharepoint-with-cloud-hybrid-search.md). + + +- To publish your SharePoint Server site and make it accessible for your users, follow the best practices in Plan for Internet, intranet, and extranet publishing sites in SharePoint Server + + +- To open a link from a search result that comes from on-premises content, users have to either be connected to the on-premises intranet via a Virtual Private Network (VPN) connection or be logged on to where the content is stored. Alternatively, you enable users to open such links by [installing a reverse proxy device](https://technet.microsoft.com/EN-US/library/dn607304.aspx) for SharePoint Server. + + +After setting up and validating the planned search experiences, you might want to clear your search index in Office 365 for metadata from the on-premises content you’ve used during this work. This works differently from what you might be familiar with from SharePoint Server.In the SharePoint Central Administration website you can use the option "Index reset" for an SSA to remove all content from the search index. This option does not work for cloud hybrid search because there is no direct communication between the cloud SSA in SharePoint Server and the search index in Office 365. If you only want to remove some on-premises metadata, remove that on-premises content source, or create a crawl rule that doesn’t crawl the URL of a file. If you need to remove all metadata from on-premises content from the search index in Office 365, open a ticket with [Microsoft Support](https://support.microsoft.com/en-us/assistedsupportproducts). +## Related Topics + + + [Learn about cloud hybrid search for SharePoint](https://support.office.com/article/af830951-8ddf-48b2-8340-179c1cc4d291) + + + + [Plan cloud hybrid search for SharePoint](https://support.office.com/article/33926857-302c-424f-ba78-03286cf5ac30) diff --git a/SharePoint/configure-connectivity-from-office-365-to-sharepoint-server.md b/SharePoint/configure-connectivity-from-office-365-to-sharepoint-server.md new file mode 100644 index 0000000000..7f0bc25b35 --- /dev/null +++ b/SharePoint/configure-connectivity-from-office-365-to-sharepoint-server.md @@ -0,0 +1,560 @@ +--- +title: Configure connectivity from Office 365 to SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 91274b73-f7be-4066-a4ab-ec30af30016e +--- + + +# Configure connectivity from Office 365 to SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-22* **Summary:** Learn how to configure inbound connectivity for SharePoint hybrid. **This article is part of a roadmap of procedures for configuring SharePoint hybrid solutions. Be sure you're [following a roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md) when you do the procedures in this article.**This article contains guidance the SharePoint hybrid environment deployment process, which integrates SharePoint Server and SharePoint Online. +## Before you begin + + + **Accessibility note:** SharePoint Server supports the accessibility features of common browsers to help you administer deployments and access sites. For more information, see **Accessibility for SharePoint 2013**.If you haven’t already done this, read [Plan connectivity from Office 365 to SharePoint Server](html/plan-connectivity-from-office-365-to-sharepoint-server.md) before you start to configure anything.This is important because the planning article helps you make important decisions and record them on the [SharePoint hybrid deployment worksheet](https://go.microsoft.com/fwlink/?LinkId=391835), referred to in the rest of this article as the *worksheet* . This in turn informs which procedures in this article to use and which you can skip over.If you’ve read the planning article, you should have already done the following: +- Decided which site collection strategy you’ll configure for hybrid. + + +- Decided whether to use an existing web application or create one for hybrid. + + + +### + +
![Edit icon](images/)These decisions are recorded in Table 2 of the worksheet. If not, go back and read [Plan connectivity from Office 365 to SharePoint Server](html/plan-connectivity-from-office-365-to-sharepoint-server.md) and make these decisions before you go any further.
+## Worksheet tips + +Things will go a lot easier if all of the applicable information is entered on the [SharePoint hybrid worksheet](https://go.microsoft.com/fwlink/?LinkId=391835) before you start to configure anything. At a minimum, you need to know the following things to use this article. +### Table: Decisions that should already be recorded on the SharePoint hybrid worksheet + +Decision Location on the worksheet Will you use an existing web application for hybrid or create one?
**New or existing web application** row of Table 2
What site collection strategy will you use?
**Site collection strategy** row of Table 2
What’s the External URL?
**External URL** row of Table 3
What’s the IP address of the Internet-facing endpoint on the reverse proxy device that the external URL is associated with?
**IP address of the external endpoint** row of Table 3
Verify that these decisions are entered on the worksheet before you continue. +## Configuration phases + +In order to configure the environment infrastructure, you'll need both SharePoint Server interfaces, such as the SharePoint Central Administration website, and the Administration pages in SharePoint Online. To prevent you from having to switch between these interfaces more than necessary, we've organized the configuration steps into the following phases: +- [Prepare your public domain](#preparedomain) + + +- [Configure SharePoint Server](#configureSPServer) + + +- [Create and configure a target application for the SSL certificate in SharePoint Online](#configurespo) + + +- [Validation and next steps](#more) + + +Please complete each configuration step in the order shown in this article. +> [!IMPORTANT:] + + + + + + +## Prepare your public domain + + +In order for Office 365 to send requests to the external endpoint of your reverse proxy device, you need to have the following things: +- A public domain registered with a domain registrar, such as GoDaddy.com, that the URL of the external endpoint of the reverse proxy device is associated with. + + +- An A record in your public domain’s DNS zone that's associated with the published SharePoint site (which is the External URL, such as spexternal.adventureworks.com). This enables Office 365 to send requests to the external endpoint on the reverse proxy device that’s configured for hybrid. This A record maps the External URL to the IP address of the Internet-facing endpoint of the reverse proxy device. For more information, see [Plan connectivity from Office 365 to SharePoint Server](html/plan-connectivity-from-office-365-to-sharepoint-server.md). + + +If you don’t yet have a public domain that you want to use for this purpose (such as adventureworks.com), get one now, and then create this A record. If you already took care of this during the planning phase, the name of your public domain and the IP address that you need to create this A Record are recorded in Table 3 of the worksheet.You have to complete the steps in the [Add your domain to Office 365](https://go.microsoft.com/fwlink/?LinkId=392208) article to add the host name of your public domain to Office 365. +## Configure SharePoint Server + + +This section tells you how to configure the SharePoint Server farm for use in an inbound hybrid solution. We’ve organized the steps for this section into the following phases. For the most reliable outcome, complete the procedures in the order shown. +- [Configure a site collection strategy](#configsitecoll) + + +- [Assign a UPN domain suffix](#assignupn) + + +- [Synchronize user profiles](#syncuserprofiles) + + +- [Configure OAuth over HTTP (if it's required)](#configOauth) + + + +> [!NOTE:] + + + + + + +## Configure a site collection strategy + + +In a hybrid environment, data is exchanged between the root site collection in SharePoint Online and a specific web application in the on-premises SharePoint farm that’s configured for hybrid. We call this the *primary web application* . This web application is the focal point on which your site collection strategy is configured.During the planning phase, you should have decided whether you'll use an existing web application or create one and which site collection strategy you'll configure. If so, your decisions are listed in the **Site collection strategy** row of Table 2 of the worksheet. If you haven't decided yet, review the [Plan connectivity from Office 365 to SharePoint Server](html/plan-connectivity-from-office-365-to-sharepoint-server.md) article and make these decisions before you go any further.Choose one of the following site collection strategies to configure: +- [Configure a site collection strategy by using a host-named site collection](#hostnamedsc) + + +- [Configure a site collection strategy by using a path-based web application (without AAM)](#pathbasedwoaam) + + +- [Configure a site collection strategy by using a path-based web application (with AAM)](#pathbasedwaam) + + + +#### Configure a site collection strategy by using a host-named site collection + + +If you want to configure a site collection strategy by using a host-named site collection for the SharePoint hybrid environment, complete these steps in the order shown: +1. Ensure that the web application and root site collection exist. + + +2. Ensure that an SSL binding exists on the primary web application. + + +3. Create the host-named site collection. + + +4. Configure split DNS. + + +5. Create an A record in the on-premises DNS. + + +For more information about site collection strategy decisions, see the [Choose a site collection strategy](plan-connectivity-from-office-365-to-sharepoint-server.md#scstrategy) section of [Plan connectivity from Office 365 to SharePoint Server](html/plan-connectivity-from-office-365-to-sharepoint-server.md). +##### Ensure that the primary web application and root site collection exist +The host-named site collection that you’ll create a bit later has to be created in a web application that’s configured to use the following: +- Integrated Windows Authentication with NTLM + + +- https protocol (Secure Sockets Layer) + + +You also need a path-based site collection to use as the root site collection in this web application. +### + +![Edit icon](images/)If you identified a web application that you want to use during planning, it should be listed in the **Primary web application URL** row of Table 5a of the worksheet.If the web application and root site collection don’t exist, you’ll have to create them. You can do this by using either Central Administration or the SharePoint 2016 Management Shell. If they already exist, go to [Ensure that an SSL binding exists on the primary web application](#hnsc_sslbinding). **Here’s an example for how to create a web application by using SharePoint 2016 Management Shell.** + + +``` + +New-SPWebApplication -Name 'Adventureworks Web app' -SecureSocketsLayer -port 443 -ApplicationPool AdventureworksAppPool -ApplicationPoolAccount (Get-SPManagedAccount 'adventureworks\\abarr') -AuthenticationProvider (New-SPAuthenticationProvider -UseWindowsIntegratedAuthentication) +``` + +Where: +- The name of the web application is **Adventureworks Web app**. + + +- The port number of the web application is 443. + +### + +![Edit icon](images/)Record the port number that you chose in the **Port number of the web application** row of Table 5a of the worksheet.- The new web application uses a web application pool named **AdventureworksAppPool**. + + +- The web application runs as the managed account **adventureworks\\abarr**. + + +- The web application is created by using Windows Integrated Authentication with NTLM. + + + **Here’s an example for how to create the root site collection by using the SharePoint 2016 Management Shell.** + + +``` + +New-SPSite 'https://sharepoint' -Name 'Portal' -Description 'Adventureworks Root site collection' -OwnerAlias 'adventureworks\\abarr' -language 1033 -Template 'STS#0' +``` + +Where: +- The host name of the SharePoint farm is "sharepoint". + + +- The primary administrator is **adventureworks\\abarr**. + + +- The site template uses the English language (1033). + + +- The template (STS#0) is the Team Site template. + + +For more information about how to create a web application and root site collection for a host-named site collection, see **Create claims-based web applications in SharePoint Server** and **Host-named site collection architecture and deployment (SharePoint 2013)**. +##### Ensure that an SSL binding exists on the primary web application +Because this web application is configured to use SSL, you have to ensure that an SSL certificate is bound to the primary web application. For production environments, this certificate should be issued by a public certification authority (CA). For test and development environments, this can be a self-signed certificate. We call this the *on-premises SharePoint SSL certificate* . +> [!TIP:] + + + + + +After the certificate is bound to the web application, you’ll be able to see this host name in the **Issued To** field in the **Server Certificates** dialog box in Internet Information Services (IIS). For more information, see [How to Set Up SSL on IIS 7.0](https://go.microsoft.com/fwlink/p/?LinkId=187887). +##### Create the host-named site collection +After the web application and root site collection are in place, the next step is to create a host-named site collection within the primary web application. The public URL of this site collection must be identical to the external endpoint URL. +> [!NOTE:] + + + + + + **Here’s an example of how to create a host-named site collection by using the SharePoint 2016 Management Shell.** + + +``` + +New-SPSite 'https://spexternal.adventureworks.com' -HostHeaderWebApplication 'https://sharepoint' -Name 'https://spexternal.adventureworks.com' -Description 'Site collection for hybrid' -OwnerAlias 'adventureworks\\abarr' -language 1033 -Template 'STS#0' +``` + +Where: +- **https://spexternal.adventureworks.com** is the URL of the host-named site collection. This URL must be identical to the External URL. + + +- **https://sharepoint** is the web application that the site collection is created in. + + +For more information, see **Host-named site collection architecture and deployment (SharePoint 2013)**. +##### Configure split DNS +You have to configure split DNS. This is a common configuration that's used to help ensure that on-premises client computers resolve a server name to internal IP addresses, even though public DNS resolution resolves the same service name to a completely different public IP address. This enables users to be redirected to an endpoint that uses standard SharePoint security-enhanced mechanisms for authentication, but queries from Office 365 can be directed through a reverse proxy configured to use certificate authentication.For more information about how to use split DNS in a hybrid topology, see [Architecture Design Recommendation for SharePoint 2013 Hybrid Search Features](https://go.microsoft.com/fwlink/?LinkId=392219). For information about how to configure a split DNS, see [A faulty split-brain DNS configuration can prevent a seamless SSO sign-in experience](https://support.microsoft.com/kb/2715326). +##### Create an A record in the on-premises DNS +The reverse proxy device must be able to resolve the internal URL of the host-named site collection. You can do this by creating an A record in the desired on-premises DNS namespace. This doesn’t have to be in the same namespace as the reverse proxy device. However, the reverse proxy device must be able to resolve this namespace. This A record maps the host name of the External URL to the IP address of the on-premises SharePoint farm. Here’s an example of an A record where the External URL is https://spexternal.adventureworks.com, and the IP address of the network load balancer for the SharePoint farm is 10.0.0.13. + + + +![This figure illustrates an example of an A Record](images/) + + + + +### + +![Edit icon](images/)The External URL is recorded in the **External URL** row of Table 3 of the worksheet.You have finished configuring the site collection strategy by using a host-named site collection for hybrid. Now, skip ahead to [Assign a UPN domain suffix](#assignupn). +#### Configure a site collection strategy by using a path-based web application without AAM + + +If you want to configure a site collection strategy by using a path-based web application without the need to create an Alternate Access Mapping (AAM) for the SharePoint hybrid environment, complete these steps in the order shown: +1. Ensure that the web application exists. + + +2. Ensure that an SSL binding exists on the primary web application. + + +3. Configure split DNS. + + +4. Create an A record in the on-premises DNS. + + + +> [!NOTE:] + + + + + +For more information, see the [Choose a site collection strategy](plan-connectivity-from-office-365-to-sharepoint-server.md#scstrategy) section of [Plan connectivity from Office 365 to SharePoint Server](html/plan-connectivity-from-office-365-to-sharepoint-server.md). +##### Ensure that the primary web application exists +You can use an existing web application as the primary web application, or you can create one. You should have made this decision during planning and recorded it in the **New or existing web application** row of Table 2 of the worksheet. If you haven’t made this decision yet, refer to [Plan connectivity from Office 365 to SharePoint Server](html/plan-connectivity-from-office-365-to-sharepoint-server.md) and decide before you go any further. Remember that when you configure a site collection strategy without AAM, the public URL of the primary web application must be identical to the External URL.If during planning, you decided which existing web application to use as the primary web application, its URL should be recorded in the **Primary web application URL** row of Table 5b of the worksheet. If so, skip ahead to [Ensure that an SSL binding exists on the primary web application](#ensuresslwoaam). Otherwise, to create a web application to use as the primary web application, use the procedures in **Create claims-based web applications in SharePoint Server**.In general, you should use the default settings. However, the following configuration settings are required. +### Required configuration settings + +Location Description In the **IIS Web Site** section, in the **Port** box
Type the port number that you want this web application to use—for example, 443.
+### + +![Edit icon](images/)Record this port number in the **Port number of the web application** row of Table 5b of the worksheet.
In the **Security Configuration** section
Ensure that **Allow Anonymous** is set to **No**.
In the **Security Configuration** section
Ensure that **Use Secure Sockets Layer (SSL)** is set to **Yes**. You’ll have to bind an SSL certificate to the web application, which we discuss more in the next section.
+### + +![Edit icon](images/)Record **https** in the **Protocol of the web application** row of Table 5b of the worksheet.
In the **Claims Authentication Types** section
Select the **Enable Windows Authentication** check box, select the **Integrated Windows authentication** check box, and in the drop-down menu, select **NTLM**.
In the **Public URL** section, in the **URL** box
Type the External URL—for example, https://spexternal.adventureworks.com.
+> [!IMPORTANT:] + + + + + + +### + +![Edit icon](images/)This URL is recorded in the **External URL** row of Table 3 of the worksheet.
To make things easier for yourself in later procedures, we recommend that you do the following. +### + +![Edit icon](images/)Get the URL from the **Public URL** section of the **Create New Web Application** page in Central Administration, and record it in the **Primary web application URL** row of Table 5b of the worksheet. +##### Ensure that an SSL binding exists on the primary web application +You have to ensure that an SSL certificate is bound to the primary web application. For production environments, this certificate should be issued by a public certification authority (CA). For test and development environments, this can be a self-signed certificate. We call this the on-premises SharePoint SSL certificate. +> [!TIP:] + + + + + +The host name of the web application must be in the **Subject** field of the SSL certificate. After the certificate is bound to the web application, you can see this host name in the **Issued To** field in the **Server Certificates** dialog box in Internet Information Services (IIS). For more information, see [How to Set Up SSL on IIS 7.0](https://go.microsoft.com/fwlink/p/?LinkId=187887). +##### Configure split DNS +You have to configure split DNS. This is a common configuration that's used to help ensure that on-premises client computers resolve a server name to internal IP addresses, even though public DNS resolution resolves the same service name to a completely different public IP address. This enables users to be redirected to an endpoint that uses standard SharePoint security-enhanced mechanisms for authentication, but queries from Office 365 can be directed through a reverse proxy that's configured to use certificate authentication.For more information about how to use split DNS in a hybrid topology, see [Architecture Design Recommendation for SharePoint 2013 Hybrid Search Features](https://go.microsoft.com/fwlink/?LinkID=392219). For information about how to configure a split DNS, see [A faulty split-brain DNS configuration can prevent a seamless SSO sign-in experience](https://support.microsoft.com/kb/2715326). +##### Create an A record in the on-premises DNS +The reverse proxy device must be able to resolve the internal URL of the host-named site collection. You can do this by creating an A record in the desired on-premises DNS namespace. This doesn’t have to be in the same namespace as the reverse proxy device. However, the reverse proxy device must be able to resolve this namespace. This A record maps the host name of the External URL to the IP address of the on-premises SharePoint farm. Here’s an example of an A record where the External URL is https://spexternal.adventureworks.com and the IP address of the network load balancer for the SharePoint farm is 10.0.0.13. + + + +![This figure illustrates an example of an A Record](images/) + + + + +### + +![Edit icon](images/)The External URL is recorded in the **External URL** row of Table 3 of the worksheet.You have finished configuring the site collection strategy by using a path-based site collection without AAM for hybrid. Now, skip ahead to [Assign a UPN domain suffix](#assignupn). +#### Configure a site collection strategy by using a path-based web application with AAM + + +If you want to use a path-based web application with Alternate Access Mapping (AAM) for your site collection strategy, complete these steps in the order shown: +1. Ensure that the primary web application exists. + + +2. Extend the primary web application, and configure AAM. + + +3. Ensure that an SSL binding exists on the primary web application (if it is needed). + + +4. Configure AAM. + + +5. Create a CNAME record. + + +If you’ve already configured a different name mapping type, go to [Assign a UPN domain suffix](#assignupn).The following video demonstrates how a site collection strategy works with a path-based web application with AAM. **Video: Understanding URLs and host names** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + +##### Ensure that the primary web application exists +You can use an existing web application as the primary web application, or you can create one. If you haven’t made this decision yet, refer to [Plan connectivity from Office 365 to SharePoint Server](html/plan-connectivity-from-office-365-to-sharepoint-server.md) and decide before you go any further.If during planning, you decided which existing web application to use as the primary web application, its URL should be recorded in the **Primary web application URL** row of Table 5c of the worksheet. If so, skip ahead to [Extend the primary web application](#waam_extendwebapp). Otherwise, to create a web application to use as the primary web application, use the procedures in **Create claims-based web applications in SharePoint Server**. The SharePoint hybrid configuration is not affected by the initial configuration of this web application when you configure this site collection strategy. This is because you’ll apply the settings that you need for hybrid when you extend the web application a bit later. So you can use any settings that you want when you create a web application. +### + +![Edit icon](images/) To make things easier for yourself in later procedures, we recommend that you record this information when you create the web application:
Get the URL from the **Public URL** section of the **Create New Web Application** page in Central Administration, and record it in the **Primary web application URL** row of Table 5c of the worksheet.
+##### Extend the primary web application +This section explains how to extend your web application. Extending the web application creates a new IIS website that you’ll assign the External URL to as the public URL.When you’ve completed the procedures in this section, you’ll have two IIS websites. Both are connected to the same content database. The original IIS website will be unchanged and can continue to be accessed by internal users. The extended web application will use a different zone, such as the Internet zone, and will be configured to use the External URL as the public URL. This extended web application is used only for servicing SharePoint hybrid requests. +> [!IMPORTANT:] + + + + + +To extend the web application, use the procedures in [Extend claims-based web applications in SharePoint](html/extend-claims-based-web-applications-in-sharepoint.md). In general, you should use the default settings. But, the following configuration settings are required. +### Required configuration settings + +Location Description In the **IIS Web Site** section, in the **Port** box Ensure that the value is set to the appropriate port number for one of the following: If you decide to extend the primary web application for unencrypted **HTTP** connections, use port **80** or the HTTP port specified by the network administrator who configures the reverse proxy device. All inbound service connections from the reverse proxy device to the web application's site collection have to use **HTTP**. If you decide to configure the primary web application for encrypted **HTTPS** connections, use port **443** or the SSL port specified by the network administrator who configures the reverse proxy device. All inbound service connections from the reverse proxy device to the web application's site collection have to use **HTTPS**. +### + +![Edit icon](images/) Record the port number in the **Port number of the extended web application** row of Table 5c of the worksheet.In the **Security Configuration** sectionEnsure that **Allow Anonymous** is set to **No**.In the **Security Configuration** sectionChoose the appropriate value for **Use Secure Sockets Layer (SSL)**. If you choose **No**, the web application will use unencrypted **HTTP**. If you choose **Yes**, the web application will use encrypted **HTTPS**, and you must bind an SSL certificate to the extended web application. We discuss this certificate more in the next section. +### + +![Edit icon](images/)Record the protocol that you chose in the **Protocol of the extended web application** row of Table 5c of the worksheet.In the **Claims Authentication Types** sectionSelect the **Enable Windows Authentication** check box, select the **Integrated Windows authentication** check box, and in the drop-down menu, select **NTLM**.In the **Public URL** section, in the **URL** boxType the External URL—for example, https://spexternal.adventureworks.com. +> [!IMPORTANT:] + + + + + + +### + +![Edit icon](images/)This URL is recorded in the **External URL** row of Table 3 of the worksheet.In the **Public URL** section, in the **Zone** listSelect the zone that you want to assign to this extended web application. We recommend that you set the **Zone** value to **Internet** if it’s available. +### + +![Edit icon](images/)Record the zone that you selected in the **AAM Zone of the extended web application** row of Table 5c of the worksheet. +##### Ensure that an SSL binding exists on the primary web application (if it's needed) +If you configured the extended web application to use SSL, you’ll have to ensure that an SSL certificate is bound to the web application that you extended in the previous section. Otherwise, if you configured the extended web application for **HTTP** (unencrypted), skip ahead to [Configure AAM](#waam_configureaam).For production environments, this certificate should be issued either by a public or an enterprise certification authority (CA). For test and development environments, this can be a self-signed certificate. We call this the *on-premises SharePoint SSL certificate* . +> [!IMPORTANT:] + + + + + + +> [!TIP:] + + + + + +For more information about how to set up SSL, see [A guide to https and Secure Sockets Layer in SharePoint 2013](https://go.microsoft.com/fwlink/?LinkId=392233). +##### Configure AAM +To enable SharePoint Server to dynamically translate links in requests by using the External URL, follow these steps. **To configure AAM** +1. In Central Administration, in the Quick Launch, click **Application Management**. + + +2. In the **Web Applications** section, click **Configure alternate access mappings**. + + +3. On the **Alternate Access Mappings** page, click **Add Internal URLs**. + + +4. In the **Alternate Access Mapping Collection** section, click the down arrow, and then click **Change Alternate Access Mapping Collection**. In the dialog box that is displayed, select the primary web application that you’re configuring for hybrid. + +### + +![Edit icon](images/)The URL of this web application is recorded in the **Primary web application URL** row of Table 5c of the worksheet.5. In the **Add Internal URL** section, in the **URL protocol, host and port** box, type the URL you want to use as the bridging URL. This URL must have the same protocol as the extended web application, either **http** or **https**. For example, if you configured the extended web application by using **https**, the URL will resemble **https://bridge**. + +### + +![Edit icon](images/) +The protocol that you used is recorded in the Protocol of the extended web application row of Table 5c of the worksheet. Record this URL in the Bridging URL row of Table 5c of the worksheet. 6. In the **Zone** drop-down menu, select the same zone that you used when you extended the web application. + +### + +![Edit icon](images/)This zone is recorded in the **Zone of the extended web application** row of Table 5c of the worksheet7. Click **Save**. + + The URL that you specified in step 5 appears in the **Internal URL** column of the **Alternate Access Mappings** page. + + + +##### Create a CNAME record +You need to create a CNAME record in the on-premises DNS. This record maps the host name of the Bridging URL to the fully qualified domain name of the on-premises SharePoint farm. The Bridging URL is the one that you assigned to the AAM in the previous section. The reverse proxy device must be able to query DNS to resolve the alias to the IP address of the on-premises SharePoint farm.Here’s an example CNAME record where the host name is **Bridge**, based on the bridging URL, **https://bridge**. + + + +![This figure illustrates a CName record in a hybrid environment in SharePoint Server 2013](images/) + + + +To verify that the alias name you chose for your CNAME record is resolving to the SharePoint Server farm, do the following verification step. **Verification step** + + + + +1. Log on to the reverse proxy device as administrator and open a Windows command prompt. + + +2. Ping the alias name in the CNAME record. For example, if the alias name is *Bridge* , then type the following and press Enter. + + ``` + +ping bridge + + ``` + + + The command prompt should return the IP address of the SharePoint farm that’s specified in the CNAME record. If not, verify that the fully qualified domain name of the SharePoint farm is correctly specified in the CNAME record and then repeat these verification steps. + + > [!NOTE:] + + +## Create and configure a target application for the SSL certificate in SharePoint Online + + +In this section, you create and configure a Secure Store target application in SharePoint Online. This target application is used to store the Secure Channel SSL certificate and enable it so that it can be used by SharePoint Online services when users request data from the on-premises SharePoint farm. We refer to this target application as the *Secure Channel Target Application* . +### + +![Edit icon](images/)To follow these steps, you need the information recorded in Table 4a of the worksheet. +> [!NOTE:] + + + + + +When you configure SharePoint hybrid solutions in Phase 4: Configure a hybrid solution, you’ll provide the name of the target application that you created so that SharePoint Online Search and Business Connectivity Services can get the Secure Channel SSL certificate that's needed to authenticate with the reverse proxy device. **To create a target application to store the Secure Channel SSL certificate** +1. Verify that you’re logged on to Office 365 as a global administrator. + + +2. In the SharePoint Online Administration Center, in the navigation pane, choose **secure store**. + + +3. On the **Edit** tab, choose **New**. + + +4. In the **Target Application Settings** section, do the following: + +1. In the **Target Application ID** box, type the name (which will be the ID) that you want to use for the target application—for example, we recommend that you name it **SecureChannelTargetApplication**. Do not use spaces in this name. + + > [!NOTE:] + + +### + +![Edit icon](images/)Record this name in the **Target Application ID** row of Table 6 of the worksheet.2. In the **Display Name** box, type the name that you want to use as the display name for the new target application. For example, **Secure Channel Target App**. + +### + +![Edit icon](images/)Record this name in the **Target Application Display Name** row of Table 6 of the worksheet.3. In the **Contact E-mail** box, type the name of the primary contact for this target application. + + +5. In the **Credential Fields** section, do the following: + +1. In the **Field Name** column, in the first row, delete any existing text that is in the box, and then type **Certificate**. + + +2. In the **Field Type** column, in the first row, in the drop-down list, select **Certificate**. + + +3. In the **Field Name** column, in the second row, delete any existing text that is in the box, and then type **Certificate Password**. + + > [!NOTE:] + +4. In the **Field Type** column, in the second row, in the drop-down list, select **Certificate Password**. + + The credentials section should resemble the following illustration. + + ![This figure illustrates the credentials setting of a Secure Store Service Target Application](images/) + + + +6. In the **Target Application Administrators** section, in the box, type the names of users who will have access to manage the settings of this target application. Make sure to add any users who will test the hybrid configuration so that they can make changes, if it's needed. + + +7. In the **Members** section, in the box, type the names of the Azure AD users and groups that you want to enable to use hybrid solutions. + + The Office 365 global administrator can create Azure AD groups. These are domain groups, not SharePoint groups. + +### + +![Edit icon](images/)A list of these users, or the group they were added to, is listed in the **Federated Users** row of Table 1 of the worksheet.8. Click **OK**. + + +9. Select the check box next to the ID of the target application that you created—for example, **SecureChannelTargetApp**. + +### + +![Edit icon](images/)This name is listed in the **Target Application Display Name** row of Table 6 of the worksheet.10. On the **Edit** tab, in the **Credentials** group, click **Set**. + + +11. In the **set credentials for secure store target application** dialog box, do the following: + +1. Next to the **Certificate** field, click **Browse**. + + +2. Browse to the location of the Secure Channel SSL certificate, select the certificate, and then click **Open**. + +### + +![Edit icon](images/)The name and location of this certificate is recorded in the **Secure Channel SSL Certificate location and filename** row of Table 4b of the worksheet.3. If the certificate you’re using contains a private key, such as a Private Information Exchange (.pfx) file, then in the **Certificate Password** field, type the password of the certificate. Otherwise, go to step 12. + +### + +![Edit icon](images/)The password is recorded in the **Secure Channel SSL Certificate password** row of Table 4b of the worksheet.4. In the **Confirm Certificate Password** field, retype the password of the certificate. + + +12. Click **OK**. + + +For more information, see [Configure the Secure Store Service in SharePoint Server](html/configure-the-secure-store-service-in-sharepoint-server.md). +## Validation and next steps + + +After you complete the configuration tasks in this topic, you should validate the following items: +- Verify that your public Internet domain name can be resolved in DNS. + + +- Verify that you can connect to the primary web application by using both the internal and external URLs. + + +- Verify that you can successfully access an on-premises site collection within the primary web application from the Internet by using the external URL of your reverse proxy endpoint. The computer that you use for this validation step must have the Secure Channel SSL certificate installed in the Personal certificate store of the computer account. + + +After you have completed and validated the configuration tasks in this topic, return to your [configuration roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md). diff --git a/SharePoint/configure-diagnostic-logging-in-sharepoint-server.md b/SharePoint/configure-diagnostic-logging-in-sharepoint-server.md new file mode 100644 index 0000000000..a4e2ddf6bc --- /dev/null +++ b/SharePoint/configure-diagnostic-logging-in-sharepoint-server.md @@ -0,0 +1,233 @@ +--- +title: Configure diagnostic logging in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: faab1eb4-5848-4970-b13f-ba6df14272fe +--- + + +# Configure diagnostic logging in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-07-31* **Summary:** Learn to configure diagnostic logging in SharePoint Server 2013 and SharePoint Server 2016 from the SharePoint Central Administration website or by using Windows PowerShell.In this article: +- [Before you begin](#begin) + + +- [Diagnostic logging setting best practices](#section1) + + +- [Configure diagnostic logging by using Central Administration](#section2) + + +- [Configure diagnostic logging by using Windows PowerShell](#section3) + + + +## Prerequisites + +The user account that is performing procedures from Central Administrationmust be a member of the Farm Administrators SharePoint group. +## Diagnostic logging setting best practices + + +The SharePoint Server environment might require configuration of the diagnostic logging settings after initial deployment, after upgrade, and if a change is made to the environment, such as adding or removing a server. The guidelines in the following list can help you form best practices for the specific environment. +- **Change the drive to which the server writes logs.** + + By default, SharePoint Server writes diagnostic logs to the same drive and partition on which it was installed. Because diagnostic logging can use a large amount of drive space and compromise drive performance, you should configure SharePoint Server to write to another drive on which SharePoint Server is not installed. You should also consider the connection speed to the drive on which SharePoint Server writes the logs. If verbose-level logging is configured, the server records a large amount of data. Therefore, a slow connection might result in poor log performance. + + +- **Restrict log disk space usage.** + + By default, the amount of disk space that diagnostic logging can use is unlimited. Therefore, restrict the disk space that logging uses, especially if you configure logging to write verbose-level events. When the disk reaches the restriction, SharePoint Server removes the oldest logs before it records new logging data. + + +- **Use the Verbose setting sparingly.** + + You can configure diagnostic logging to record verbose-level events. This means that SharePoint Server records every action that it takes. Verbose-level logging can quickly use drive space and affect drive and server performance. You can use verbose-level logging to record more detail when you are making critical changes and then reconfigure logging to record only higher-level events after you make the change. + + +- **Regularly back up logs.** + + Diagnostic logs contain important data. Therefore, back up the logs regularly to ensure that this data is preserved. When you restrict log drive space usage, or if you keep logs for only a few days, SharePoint Server automatically deletes log files, starting with the oldest files first, when the threshold is met. + + +- **Enable event log flooding protection.** + + When you enable this setting, SharePoint Server detects repeating events in the Windows event log, and suppresses them until conditions return to a typical state. + + +You can set the level of diagnostic logging for the event log and for the trace log. This limits the types and amount of information that are written to each log. The following tables define the levels of logging that are available for the event log and trace log. +### Event log levels + +Level Definition None
No logging occurs.
Critical
This message type indicates a serious error that has caused a major failure in the solution.
Error
This message type indicates an urgent condition. You should investigate all error events.
Warning
This message type indicates a potential problem or issue that might require attention. You should review and track warning messages for patterns over time.
Information
Information messages do not require any action. However, they can provide valuable data for monitoring the state of your solution.
Verbose
This event log level corresponds to lengthy events or messages.
+### Trace log levels + +Level Definition None
No trace logs are written.
Unexpected
This level records messages about events that cause solutions to stop processing. When set to this level, the log will include events at the Unexpected, Exception, Assert, and Critical levels.
Monitorable
This level records messages about all unrecoverable events that limit the functionality of the solution but do not stop the application. When set to this level, the log also includes events that the Unexpected setting records.
High
This level records all events that are unexpected but which do not stop the processing of a solution. When set to log at this level, the log also includes all events that the Monitorable setting records.
Medium
When set to this level, the trace log includes all messages except Verbose and VerboseEx messages. This level records all high-level information about operations that were performed. This level provides enough detail to construct the data flow and sequence of operations. Administrators or support professionals could use this level of logging to troubleshoot issues. When set to this level, the log will also include all events that the High setting records.
Verbose
When set to this level, the log includes most actions. Verbose tracing produces many log messages. This level is typically used only for debugging in a development environment. When set to log at this level, the log will also include all events that the Medium setting records.
VerboseEx
This level is only supported by the **Set-SPLogLevel** PowerShell cmdlet, and includes very low-level diagnostic data. This level should only be used in a development environment. When set to this level, the log includes all events that the Verbose setting records.
+## Configure diagnostic logging by using Central Administration + + +You can use the SharePoint Central Administration website to configure diagnostic logging. **To configure diagnostic logging by using Central Administration** +1. In Central Administration, on the home page, click **Monitoring**. + + +2. On the Monitoring page, in the **Reporting** section, click **Configure diagnostic logging**. + + +3. On the Diagnostic Logging page, in the **Event Throttling** section, configure event throttling as follows: + + To configure event throttling for all categories: + +1. Select the **All Categories** check box. + + +2. Select the event log level from the **Least critical event to report to the event log** list. + + +3. Select the trace log level from the **Least critical event to report to the trace log** list. + + + + + + To configure event throttling for one or more categories: + +1. Select the check boxes of the categories that you want. + + +2. Select the event log level from the **Least critical event to report to the event log** list. + + +3. Select the trace log level from the **Least critical event to report to the trace log** list. + + + + + + To configure event throttling for one or more subcategories (you can expand one or more categories and select any subcategory): + +1. Click the plus **(+)** next to the category to expand the category. + + +2. Select the check box of the subcategory. + + +3. Select the event log level from the **Least critical event to report to the event log** list. + + +4. Select the trace log level from the **Least critical event to report to the trace log** list. + + + + + + To return event throttling for all categories to default settings: + +1. Select the **All Categories** check box. + + +2. Select **Reset to default** from the **Least critical event to report to the event log** list. + + +3. Select **Reset to default** from the **Least critical event to report to the trace log** list. + + + + +4. In the **Event Log Flood Protection** section, select the **Enable Event Log Flood Protection** check box. + + +5. In the **Trace Log** section, in the **Path** box, type the path of the folder to which you want logs to be written. + + +6. In the **Number of days to store log files** box, type the number of days (1-366) that you want logs to be kept. After this time, logs will automatically be deleted. + + +7. To restrict the disk space that logs can use, select the **Restrict Trace Log disk space usage** check box, and then type the number gigabytes (GB) you want to restrict log files to. When logs reach this value, older logs will automatically be deleted. + + +8. After you have made the changes that you want on the Diagnostic Logging page, click **OK**. + + + +## Configure diagnostic logging by using Windows PowerShell + + +You can use PowerShell to configure diagnostic logging. **To configure diagnostic logging by using Windows PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use PowerShell cmdlets. + + > [!NOTE:] + +2. From the SharePoint Management Shell, change the drive to which the server writes logs. + + +3. At the PowerShell command prompt, type the following command: + + ``` + +Set-SPDiagnosticConfig -LogLocation D:\\DiagnosticLogs + ``` + +4. To restrict log disk space usage, at the PowerShell command prompt, type the following command: + + ``` + Set-SPDiagnosticConfig -LogMaxDiskSpaceUsageEnabled + ``` + + + Or assign the maximum disk space for logs: + + + + ``` + Set-SPDiagnosticConfig -LogDiskSpaceUsageGB 500 + ``` + +5. To view the current logging level, at the PowerShell command prompt, type the following command: + + ``` + Get-SPLogLevel + ``` + +6. To change the logging level, at the PowerShell command prompt, type the following command: + + ``` + Set-SPLogLevel -TraceSeverity Monitorable + ``` + + + To set all categories back to default levels, at the PowerShell command prompt, type the following command, and then press ENTER: + + + + ``` + Clear-SPLogLevel + ``` + +7. To enable event log flooding protection, at the PowerShell command prompt, type the following command: + + ``` + Set-SPDiagnosticConfig -EventLogFloodProtectionEnabled + ``` + +For more information, see **Set-SPDiagnosticConfig**, **Set-SPLogLevel** and [Get-SPLogLevel](https://technet.microsoft.com/en-us/library/ff607576). +# See also + +#### + + [Overview of monitoring in SharePoint Server](html/overview-of-monitoring-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-ediscovery-in-sharepoint-server.md b/SharePoint/configure-ediscovery-in-sharepoint-server.md new file mode 100644 index 0000000000..972cf978d7 --- /dev/null +++ b/SharePoint/configure-ediscovery-in-sharepoint-server.md @@ -0,0 +1,86 @@ +--- +title: Configure eDiscovery in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 5cdce2aa-fa6e-4888-a34f-de61713f5096 +--- + + +# Configure eDiscovery in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-07-18* **Summary:** Learn the steps to set up and configure eDiscovery in SharePoint Server 2013, SharePoint Server 2016, Exchange Server 2016, and Exchange Server 2013.This article identifies the steps that are required to configure eDiscovery in SharePoint Server. When you complete the steps that are listed in this article, users will be able to create and work with eDiscovery cases.Before you configure eDiscovery, you should understand the concepts that are presented in the article [Overview of eDiscovery and in-place holds in SharePoint Server](html/overview-of-ediscovery-and-in-place-holds-in-sharepoint-server.md).You must perform the following tasks to configure eDiscovery: +- Configure communication between SharePoint Server and Exchange Server 2016. + + +- Configure Search to crawl all discoverable content. + + +- Grant permissions. + + +- Create an eDiscovery Center. + + + +## Configure communication between SharePoint Server and Exchange Server 2016 + + +If you will use a SharePoint eDiscovery Center to discover content in Exchange Server, you must configure SharePoint Server and Exchange Server to interact. +> [!IMPORTANT:] + + + + + +Perform the following steps: +1. Ensure that the Exchange Web Service managed API is installed on every front-end server that is running SharePoint Server. + + +2. Configure a trust relationship between SharePoint Server and Exchange Server. For information about the trust relationship, see [Plan for server-to-server authentication in SharePoint Server](html/plan-for-server-to-server-authentication-in-sharepoint-server.md). + + +3. If you want content from Skype for Business Server to be discoverable, configure the server to archive to Exchange Server 2016. For information about how to configure Skype for Business Server 2015 archiving, see [Configure Skype for Business Server 2015 to use Exchange Server archiving](https://technet.microsoft.com/en-us/library/jj679896.aspx). + + +4. Perform the eDiscovery configuration steps for Exchange. For information about how to configure Exchange Server 2013 for eDiscovery, see [Integration with SharePoint](https://technet.microsoft.com/en-us/library/dd298021%28v=exchg.160%29.aspx#SP). + + + +## Configure Search to crawl all discoverable content + + +Content is only discoverable if it is crawled and indexed by the Search service application that is associated with the web application that the eDiscovery Center is in. You should have identified this Search service application when you planned for eDiscovery. To configure the Search service application to crawl the appropriate content, follow these steps: +1. If content in Exchange Server 2013 must be discoverable, add Exchange Server 2013 as a result source. For information about how to configure a result source, see [Configure result sources for search in SharePoint Server](html/configure-result-sources-for-search-in-sharepoint-server.md). + + +2. Ensure that all websites that contain discoverable content are being crawled. For information about how to configure a location to be crawled, see [Add, edit, or delete a content source in SharePoint Server](html/add-edit-or-delete-a-content-source-in-sharepoint-server.md). + + +3. Ensure that all file shares that contain discoverable content are being crawled. + + + +## Grant permissions + + +We recommend that you create a security group to contain all users of the eDiscovery Center. After you create the security group, grant the security group permissions to access all discoverable content. +1. If you will grant permissions at the web application level, create a user policy that gives the security group full read permissions for each web application that contains discoverable content. For information about how to create a policy for a web application, see [Manage permission policies for a web application in SharePoint Server](html/manage-permission-policies-for-a-web-application-in-sharepoint-server.md). + + > [!NOTE:] + +2. If you will grant permissions at the site collection level, make the security group a site collection administrator for each site collection that contains discoverable content. For information about how to add a site collection administrator, see [Add, change, or remove a site collection administrator](https://support.office.com/en-US/article/Create-and-manage-SharePoint-groups-B1E3CD23-1A78-4264-9284-87FED7282048). + + > [!IMPORTANT:] + +3. Ensure that the security group has permissions to access all file shares and other websites that contain discoverable content. + + +4. If you will use a SharePoint eDiscovery Center to discover content in Exchange Server, grant the security group permissions to access Exchange Server mailboxes. For information about how to grant permissions in Exchange, see [Integration with SharePoint](https://technet.microsoft.com/en-us/library/dd298021%28v=exchg.160%29.aspx#SP). + + +5. Grant the security group permissions to view the crawl log. For information about how to grant permissions to access the crawl log, see **Set-SPEnterpriseSearchCrawlLogReadPermission**. + + + +## Create an eDiscovery center + + +An eDiscovery Center is a site collection from which users can create and manage eDiscovery cases. To create an eDiscovery Center, follow the procedure in the article [Create a site collection in SharePoint Server](html/create-a-site-collection-in-sharepoint-server.md), and choose the **eDiscovery Center** site collection type from the **Enterprise** tab. Be aware that an eDiscovery Center must be in a web application that supports claims authentication. diff --git a/SharePoint/configure-email-integration-for-a-sharepoint-server-farm.md b/SharePoint/configure-email-integration-for-a-sharepoint-server-farm.md new file mode 100644 index 0000000000..3f69ee07ac --- /dev/null +++ b/SharePoint/configure-email-integration-for-a-sharepoint-server-farm.md @@ -0,0 +1,32 @@ +--- +title: Configure email integration for a SharePoint Server farm +ms.prod: SHAREPOINT +ms.assetid: 354706a8-a7f0-4e83-b2b0-bfccd1753c2e +--- + + +# Configure email integration for a SharePoint Server farm + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-02-17* **Summary: ** Use these TechNet articles to learn how to configure incoming and outgoing email for a SharePoint Server 2016 farm.The following articles on TechNet provide information about email integration. After you install SharePoint Server 2016, you can configure incoming and outgoing email. These optional settings are useful if you want to work with email in the server farm. +## TechNet articles about email integration + +The following articles about configuring email integration in SharePoint Server 2016are available in this section. +- [Configure incoming email for a SharePoint Server farm](html/configure-incoming-email-for-a-sharepoint-server-farm.md) - This article describes how to configure incoming email so that SharePoint Server 2016 sites accept and archive incoming email. It also describes how to configure incoming email so that SharePoint sites can archive email discussions as they happen, save attachments, and show meetings that were sent and received by email on site calendars. In addition, this article describes how to configure the SharePoint Directory Management Service to provide support for email distribution list creation and management. + + +- [Configure outgoing email for a SharePoint Server farm](html/configure-outgoing-email-for-a-sharepoint-server-farm.md) - This article describes how to configure outgoing email so that your Simple Mail Transfer Protocol (SMTP) server sends email alerts to site users and notifications to site administrators. + + + +# See also + +#### + + [Plan email integration for a SharePoint Server 2016 farm](html/plan-email-integration-for-a-sharepoint-server-2016-farm.md) + + + + + + + + diff --git a/SharePoint/configure-enterprise-search-in-sharepoint-server-2016.md b/SharePoint/configure-enterprise-search-in-sharepoint-server-2016.md new file mode 100644 index 0000000000..7dfecef222 --- /dev/null +++ b/SharePoint/configure-enterprise-search-in-sharepoint-server-2016.md @@ -0,0 +1,15 @@ +--- +title: Configure enterprise search in SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: a61b531f-218e-4edf-ab90-f2f30f490900 +--- + + +# Configure enterprise search in SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-02-14* **Summary:** Learn how to configure enterprise search in a SharePoint Server 2016 environment.Enterprise search finds the information that's most relevant to an organization's customers, employees, and partners. Enterprise search empowers them to take action and drive business outcomes. +## TechNet articles about configuring enterprise search + +The following articles reflect the steps to get started with enterprise search in SharePoint Server 2016. The articles are available to view online and writers update articles on a continuing basis as new information becomes available and as users provide feedback. +### + + [Create and configure a Search service application in SharePoint Server 2016](html/create-and-configure-a-search-service-application-in-sharepoint-server-2016.md)
The Search service application crawls content and provides search results. You can either create it as part of a new deployment of SharePoint Server 2016, or as needed.
[Create a Search Center site in SharePoint Server](html/create-a-search-center-site-in-sharepoint-server.md)
The Search Center is the interface where users submit search queries and view search results.
[Deploy people search in SharePoint Server](html/deploy-people-search-in-sharepoint-server.md)
People search lets users get information about people in the organization and to get links to the documents that they have authored. Users search for people by entering a search query in the enterprise Search Center search box and clicking the link for the People search vertical.
diff --git a/SharePoint/configure-excel-services-data-refresh-by-using-embedded-data-connections-in-shar.md b/SharePoint/configure-excel-services-data-refresh-by-using-embedded-data-connections-in-shar.md new file mode 100644 index 0000000000..d08ae99e1f --- /dev/null +++ b/SharePoint/configure-excel-services-data-refresh-by-using-embedded-data-connections-in-shar.md @@ -0,0 +1,155 @@ +--- +title: Configure Excel Services data refresh by using embedded data connections in SharePoint Server 2013 +ms.prod: SHAREPOINT +ms.assetid: 2be5291e-b6cc-4730-bc58-78b14ea1984b +--- + + +# Configure Excel Services data refresh by using embedded data connections in SharePoint Server 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-14* **Summary:** Configure Excel Services in SharePoint Server 2013 to use a Secure Store target application for external data refresh.Excel Services in SharePoint Server 2013 supports three methods of using Secure Store Service to connect to external data: +- You can specify a Secure Store target application in a workbook. (This is known as an *embedded connection* .) This article describes how to do this. + + +- You can use an unattended service account. For more information, see [Configure Excel Services data refresh by using the unattended service account in SharePoint Server 2016](html/configure-excel-services-data-refresh-by-using-the-unattended-service-account-in.md). + + +- You can use an Office Data Connection (ODC) file that specifies a Secure Store target application. For more information, see **Configure Excel Online data refresh by using external data connections in Office Online Server**. + + +To configure Excel Services data access to use embedded data connections, you use the following process: +1. [Configure a data access account](#part1) + + +2. [Create a Secure Store target application](#part2) + + +3. [Configure a workbook to use an embedded data connection](#ConfigureWorkbook) + + + +## Configure a data access account + + +You must have an account that can be granted access to the data source to which you want to connect your Excel workbook. This can be a Windows Active Directory account, a SQL Server logon, or other set of credentials as required by your data source. This account will be stored in Secure Store.Once you have created the account, the next step is to grant that account read access to the required data. (In this article, we use the example of accessing a SQL Server database through an Active Directory account. If you are using a data source other than SQL Server, see the instructions for your data source to create a logon with data-read permissions for the data access account.)Follow these steps to create a SQL Server logon and grant Read access to the database. **To create a SQL Server logon for the data access account** +1. In SQL Server Management Studio, connect to the database engine. + + +2. In Object Explorer, expand **Security**. + + +3. Right-click **Logins**, and then click **New Login**. + + +4. In the **Login name** box, type the name of the Active Directory account that you created for data access. + + +5. In the **Select a page** section, click **User Mapping**. + + +6. Select the **Map** check box for the database that you want to provide access to, and then, under **Database role membership for: **, select the **db_datareader** check box. + + +7. Click **OK**. + + +Now that you have created a data access account and granted it access to a data source, the next step is to create a Secure Store target application. +## Create a Secure Store target application + + +You must create a target application in Secure Store that contains the credentials that you created for data access. This target application can then be specified in data-connected Excel workbooks and will be used by Excel Services when it refreshes data in the workbook.When you create the target application, you have to specify which users will be authorized to use the credentials stored in Secure Store. You can list users individually, or you can use an Active Directory group. We recommend that you use an Active Directory group for ease of administration. +> [!NOTE:] + + + + + +Use the following procedure to create a Secure Store target application. **To create a target application** +1. On the Central Administration home page, in the **Application Management** section, click **Manage service applications**. + + +2. Click the Secure Store service application. + + +3. On the ribbon, click **New**. + + +4. In the **Target Application ID** box, type a unique identifier for this target application (for example, **ExcelServicesDataAccess** ). + + +5. In the **Display Name** box, type a friendly name or short description. + + +6. In the **Contact E-mail** box, type the e-mail address for a contact for this target application. + + +7. In the **Target Application Type** drop-down list, select **Group**. + + +8. Click **Next**. + + +9. On the Credential Fields page, if you are using Windows credentials, leave the default credential fields. If you are using credentials other than Windows credentials, modify the **Field Type** drop-down lists to comply with the credentials that you are using. Click **Next**. + + +10. On the Specify the membership settings page: + + - In the **Target Application Administrators** box, type the account of the user who will administer this target application. + + > [!NOTE:] + + - In the **Members** box, type the users to whom you want to grant the ability to refresh data. + + > [!NOTE:] + +11. Click **OK**. + + +Use the following procedure to set the credentials for the target application. **To set the credentials for the target application** +1. On the Secure Store Service Application page, in the **Target Application ID** column, point to the target application that you just created, click the arrow that appears, and then click **Set Credentials**. + + +2. Type the user name and password of the data access account. + + +3. Click **OK**. + + +Once you have set the credentials for the target application, the target application is ready to use. The next step is to specify this target application in the Excel Services authentication settings in your data-connected Excel workbook. +## Configure a workbook to use an embedded data connection + + +You must configure the Excel Services Authentication Settings in the workbook before you publish it to SharePoint Server 2013. Doing so enables the workbook to use a Secure Store target application to refresh data that is rendered using Excel Services. Use the following procedure to configure the authentication settings. **To configure Excel Services authentication settings** +1. In a data-connected Excel workbook, on the **Data** tab, click **Connections**. + + +2. On the **Workbook Connections** dialog box, select the data connection that you want to update, and then click **Properties**. + + +3. On the **Connection Properties** dialog box, on the **Definition** tab, click **Authentication Settings**. + + +4. On the **Excel Services Authentication Settings** dialog box, select the **Use a stored account** option, type the Application ID of the target application in the text box, and then click **OK**. + + > [!NOTE:] + +5. On the **Connection Properties** dialog box, click **OK**. + + > [!NOTE:] + +6. On the Workbook Connections dialog box, click **Close**. + + +With the target application specified in the Excel Services Authentication Settings, Excel Services uses the credentials associated with that target application to refresh the data in the workbook after you have published it to SharePoint Server 2013. +# See also + +#### + + [Configure the Secure Store Service in SharePoint Server](html/configure-the-secure-store-service-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-excel-services-data-refresh-by-using-external-data-connections-in-shar.md b/SharePoint/configure-excel-services-data-refresh-by-using-external-data-connections-in-shar.md new file mode 100644 index 0000000000..b701964832 --- /dev/null +++ b/SharePoint/configure-excel-services-data-refresh-by-using-external-data-connections-in-shar.md @@ -0,0 +1,214 @@ +--- +title: Configure Excel Services data refresh by using external data connections in SharePoint Server 2013 +ms.prod: SHAREPOINT +ms.assetid: 0853bed9-1084-413b-bf91-427dc643a5e5 +--- + + +# Configure Excel Services data refresh by using external data connections in SharePoint Server 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-14* **Summary:** Configure Excel Services in SharePoint Server 2013 data refresh by using Secure Store and an external Office Data Connection (ODC) file.Excel Services in SharePoint Server 2013 provides three methods of using Secure Store Service to refresh the external data source in a workbook: +- You can use an unattended service account. For more information, see [Configure Excel Services data refresh by using the unattended service account in SharePoint Server 2016](html/configure-excel-services-data-refresh-by-using-the-unattended-service-account-in.md). + + +- You can specify a Secure Store target application in a workbook. (This is known as an *embedded connection* .) For more information, see **Configure Excel Online data refresh by using embedded data connections in Office Online Server**. + + +- You can use an Office Data Connection (ODC) file that specifies a Secure Store target application. This article describes how to do this. + + +By using an ODC file for your data connection, you separate your Excel workbooks from the data connection information. This allows you to share a single ODC file among multiple workbooks and also allows you to centrally manage your data connections.Using Excel Services with an ODC file consists of the following steps: +1. [Configure a data access account](#part1) + + +2. [Create a Secure Store target application](configure-excel-online-data-refresh-by-using-external-data-connections-in-office.md#part2) + + +3. [Create and publish an ODC file](#part3) + + +4. [Configure an Excel workbook to use the published ODC file as a data connection](configure-excel-online-data-refresh-by-using-external-data-connections-in-office.md#part4) + + + +## Configure a data access account + + +You must have an account that can be granted access to the data source to which you want to connect your Excel workbook. This can be an Active Directory account, a SQL Server logon, or other set of credentials as required by your data source. This account will be stored in Secure Store.After you have created the account, the next step is to grant that account read access to the required data. (in this article, we use the example of accessing a SQL Server database through an Active Directory account. If you are using a data source other than SQL Server, see the instructions for your data source to create a logon with data read permissions for the data access account.)Follow these steps to create a SQL Server logon and grant Read access to the database. **To create a SQL Server logon for the data access account** +1. In SQL Server Management Studio, connect to the database engine. + + +2. In Object Explorer, expand **Security**. + + +3. Right-click **Logins**, and then click **New Login**. + + +4. In the **Login name** box, type the name of the Active Directory account that you created for data access. + + +5. In the **Select a page** section, click **User Mapping**. + + +6. Select the **Map** check box for the database that you want to provide access to, and then, in the **Database role membership for: ** section, select the **db_datareader** check box. + + +7. Click **OK**. + + +Now that you have created a data access account and granted it access to a data source, the next step is to create a Secure Store target application. +## Create a Secure Store target application + + +You must create a target application in Secure Store that contains the credentials that you created for data access. This target application can then be specified in an ODC file and will be used by Excel Services when it refreshes data in the workbook.When you create the target application, you have to specify which users will be authorized to use the credentials stored in Secure Store. You can list users individually, or you can use an Active Directory group. We recommend that you use an Active Directory group for ease of administration. +> [!NOTE:] + + + + + +Use the following procedure to create a Secure Store target application. **To create a target application** +1. On the the SharePoint Central Administration website home page, in the **Application Management** section, click **Manage service applications**. + + +2. Click the Secure Store Service service application. + + +3. On the ribbon, click **New**. + + +4. In the **Target Application ID** box, type a unique identifier for this target application (for example, **ExcelServicesDataAccess** ). + + +5. In the **Display Name** box, type a friendly name or short description. + + +6. In the **Contact E-mail** box, type the email address for a contact for this target application. + + +7. In the **Target Application Type** drop-down list, select **Group**. + + +8. Click **Next**. + + +9. On the Credential Fields page, if you are using Windows credentials, leave the default credential fields. If you are using credentials other than Windows credentials, modify the **Field Type** drop-down list to comply with the credentials that you are using. Click **Next**. + + +10. On the Specify the membership settings page: + + - In the **Target Application Administrators** box, type the account of the user who will administer this target application. + + > [!NOTE:] + + - In the **Members** box, type the users to whom you want to grant the ability to refresh data. + + > [!NOTE:] + +11. Click **OK**. + + +Use the following procedure to set the credentials for the target application. **To set the credentials for the target application** +1. On the Secure Store Service Application page, in the **Target Application ID** column, point to the target application that you just created, click the arrow that appears, and then click **Set Credentials**. + + +2. Type the user name and password of the data access account. + + +3. Click **OK**. + + +Once you have set the credentials for the target application, the target application is ready to use. The next step is to create an ODC file that specifies this target application for Excel Services data refresh. +## Create and publish an ODC file + + +Now that the Secure Store target application is configured, the next step is to create the ODC file and publish it to a trusted data connection library. Use the following procedure to create an ODC file that specifies the target application that you just created. +> [!NOTE:] + + + + + + **To create and publish an ODC file** +1. In Excel, on the **Data** tab, in the **Get External Data** section, click **From Other Sources**, and then select your data source. + + +2. Complete the wizard to create a data connection to your data source. + + +3. On the **Data** tab, click **Connections**. + + +4. On the **Workbook Connections** dialog box, select the connection that you just created, and then click **Properties**. + + +5. On the **Connection Properties** dialog box, on the **Definition** tab, click **Authentication Settings**. + + +6. On the **Excel Services Authentication Settings** dialog box, select the **Use a stored account** option, and in the **Application ID** box, type the Application ID of the Secure Store target application that you created. + + > [!NOTE:] + +7. Click **OK**. + + +8. On the **Connection Properties** dialog box, click **Export Connection File**. + + +9. Save the ODC file to a trusted data connection library on your farm. + + + +## Configure an Excel workbook to use the published ODC file as a data connection + + +In order for a workbook to use the ODC file that you just created, you must connect to it as a data source. Once it is connected, you can publish the workbook to a SharePoint Server 2013 document library and it will maintain its connection to the ODC file. Excel Services then uses the connection information specified in the ODC file when it refreshes data in the workbook.Use the following procedure to connect to the ODC file in Excel. **To use an ODC file as a data source in Excel** +1. In Excel, on the **Data** tab, in the **Get External Data** section, click **Existing Connections**. + + +2. On the **Existing Connections** dialog box, click **Browse for More**. + + +3. On the **Select Data Source** dialog box, in the URL box, type the URL for the trusted data connection library where you saved the ODC file, and then press Enter. + + > [!NOTE:] + +4. On the list of **Data Connections**, select the ODC file that you saved, and then click **Open**. + + +5. On the **Import Data** dialog box, select the **PivotTable Report** or **PivotChart and PivotTable Report** option, and then click **OK**. + + +6. On the **Data** tab, click **Connections**. + + +7. On the **Workbook Connections** dialog box, select the connection that you just opened, and then click **Properties**. + + +8. On the **Connection Properties** dialog box, on the **Definition** tab, select the **Always use connection file** check box, and then click **OK**. + + > [!NOTE:] + +9. Click **Close**. + + +Once you have completed the data connection wizard, you can create your report and then publish it to a document library. When the workbook is rendered using Excel Services, Excel Services uses the connection information specified in the ODC file to refresh the data. +> [!NOTE:] + + + + + + +# See also + +#### + + [Configure the Secure Store Service in SharePoint Server](html/configure-the-secure-store-service-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-excel-services-data-refresh-by-using-the-unattended-service-account-in.md b/SharePoint/configure-excel-services-data-refresh-by-using-the-unattended-service-account-in.md new file mode 100644 index 0000000000..266a815b25 --- /dev/null +++ b/SharePoint/configure-excel-services-data-refresh-by-using-the-unattended-service-account-in.md @@ -0,0 +1,117 @@ +--- +title: Configure Excel Services data refresh by using the unattended service account in SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: fcfdb2ad-9d0e-43ca-8bfa-45064eeca5af +--- + + +# Configure Excel Services data refresh by using the unattended service account in SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-06* **Summary:** Configure Excel Services in SharePoint Server 2013 to use the unattended service account for authentication to external data.Excel Services in SharePoint Server 2013 provides three methods of using Secure Store Service to refresh the external data source in a workbook: +- You can use an unattended service account. This article describes how to do this. + + +- You can specify a Secure Store target application in a workbook. (This is known as an *embedded connection* .) For more information, see **Configure Excel Online data refresh by using embedded data connections in Office Online Server**. + + +- You can use an Office Data Connection (ODC) file that specifies a Secure Store target application. For more information, see **Configure Excel Online data refresh by using external data connections in Office Online Server**. + + +Using the unattended service account involves configuring an Active Directory account and granting it access to your data, storing the credentials for this account in Secure Store, and configuring Excel Services to use the stored credentials when it needs to refresh the data in a workbook.The following steps are required to configure the unattended service account in Excel Services. +1. [Configure a data access account](#section1) + + +2. [Configure Excel Services Global Settings](#section3) + + +3. [Configure a workbook to use the unattended service account](#section4) + + + +## Configure a data access account + + +The unattended service account requires an Active Directory account for data access. Have your domain administrator create an Active Directory account that you can use for data access. After the account has been created, you must grant this account read access to the data source that you will be using in your data-connected Excel workbook. Use the following procedure to create a logon for the data access account in SQL Server. (If you are using a data source other than SQL Server, see the instructions for your data source to create a logon with data-read permissions for the data access account.) **To create a SQL Server logon for the data access account** +1. In SQL Server Management Studio, connect to the database engine. + + +2. In Object Explorer, expand **Security**. + + +3. Right-click **Logins**, and then click **New Login**. + + +4. In the **Login name** box, type the name of the Active Directory account that you created for data access. + + +5. In the **Select a page** section, click **User Mapping**. + + +6. Select the **Map** check box for the database that you want to provide access to, and then, in the **Database role membership for: ** section, select the **db_datareader** check box. + + +7. Click **OK**. + + +Now that you have created a logon for the data access account and granted the account access to your data source, you must create a target application in Secure Store to contain the credentials for the data access account. +## Configure Excel Services Global Settings + + +The unattended service account configuration is part of the Excel Services Global Settings. Use the following procedure to configure the unattended service account in Excel Services. **To configure Excel Services Global Settings** +1. On the the SharePoint Central Administration website home page, in the **Application Management** section, click **Manage service applications**. + + +2. On the Manage Service Applications page, click the Excel Services service application. + + +3. On the Manage the Excel Services page, click **Global Settings**. + + +4. On the Excel Services Settings page, in the **External Data** section: + + - Select the **Create a new Unattended Service Account** option. + + + - Type the user name and password of the account that you created for data access. + + +5. Click **OK**. + + +With the Excel Services Global Settings configured, setup of the unattended service account is complete. The next section describes how to configure the Excel Services authentication settings in a data-connected Excel workbook to refresh the data with the unattended service account after the workbook has been published to a SharePoint document library. +## Configure a workbook to use the unattended service account + + +You must configure the Excel Services Authentication Settings in the workbook before you publish it to SharePoint Server 2013. Doing so enables the workbook to use the unattended service account to refresh data when the workbook is rendered in Excel Services. Use the following procedure to configure the authentication settings. **To configure Excel Services authentication settings** +1. In a data-connected Excel workbook, on the **Data** tab, click **Connections**. + + +2. On the **Workbook Connections** dialog box, select the data connection that you want to update, and then click **Properties**. + + +3. On the **Connection Properties** dialog box, on the **Definition** tab, click **Authentication Settings**. + + +4. On the **Excel Services Authentication Settings** dialog box, select the **None** option, and then click **OK**. + + +5. On the **Connection Properties** dialog box, click **OK**. + + > [!NOTE:] + +6. On the **Workbook Connections** dialog box, click **Close**. + + +With the Excel Services Authentication Settings set to **None**, Excel Services uses the unattended service account to refresh the data in the workbook after you have published it to SharePoint Server 2013. +# See also + +#### + + [Use Excel Services with Secure Store Service in SharePoint Server 2016](html/use-excel-services-with-secure-store-service-in-sharepoint-server-2016.md) + + + + + + + + diff --git a/SharePoint/configure-excel-services-sharepoint-server-2013.md b/SharePoint/configure-excel-services-sharepoint-server-2013.md new file mode 100644 index 0000000000..add75bc188 --- /dev/null +++ b/SharePoint/configure-excel-services-sharepoint-server-2013.md @@ -0,0 +1,185 @@ +--- +title: Configure Excel Services (SharePoint Server 2013) +ms.prod: SHAREPOINT +ms.assetid: a2ef35c4-6b29-4ad1-8652-48a019838ea0 +--- + + +# Configure Excel Services (SharePoint Server 2013) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-14* **Summary:** Deploy Excel Services to your SharePoint Server 2013 farm by creating an Excel Services service application by using Central Administration. +> [!IMPORTANT:] + + + + + +Excel Services is enabled by creating an Excel Services Application service application in Central Administration. This article walks you through the steps of deploying Excel Services in your SharePoint Server 2013 farm.In this article: +- [Before you begin](#begin) + + +- [Video demonstration](configure-excel-online-administrative-settings.md#VideoDemonstration) + + +- [Configure the application pool account](#proc1) + + +- [Start the Excel Calculation Services service](#proc2) + + +- [Create an Excel Services service application](#proc3) + + +- [Additional steps](#more) + + + +## Before you begin + + +Before you deploy Excel Services, we recommend that you review [Overview of Excel Services in SharePoint Server 2013](html/overview-of-excel-services-in-sharepoint-server-2013.md) and its associated Excel Services planning articles.Before you begin this operation, review the following information about prerequisites: +- A domain account is required to run the Excel Services application pool. + + +- You must be a member of the Farm Administrators group to perform the procedures in this article. + + + +## Video demonstration + + +This video shows the steps involved in creating an Excel Services service application, as described in this article. **Video: Configure Excel Services in SharePoint Server 2013** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + +## Configure the application pool account + + +For better security, we recommend that you use a separate domain account to run the Excel Services application pool. Have your domain administrator create a domain account to use in running the Excel Services application pool. No specific domain privileges are required for this account.Before you can use an account to run an application pool, you must register it as a managed account in SharePoint Server. Use the following procedure to register the account. **To register a managed account** +1. On the SharePoint Central Administration website home page, in the left navigation, click **Security**. + + +2. On the Security page, under **General Security**, click **Configure managed accounts**. + + +3. On the Managed Accounts page, click **Register Managed Account**. + + +4. Type the user name and password of the domain account that you are registering. + + +5. Optionally, select the **Enable automatic password change** check box if you want SharePoint Server to manage password changes for this account. + + +6. Click **OK**. + + + +## Grant content database access to the managed account + + +You must also grant access to the SharePoint content database for the account that you will use to run the Excel Services application pool. Use the following procedure for each web application that will be associated with Excel Services. **To grant content database access to the managed account** +1. On a SharePoint Server application server, click **Start**, click **All Programs**, click **Microsoft SharePoint 2013 Products**, right-click **SharePoint 2013 Management Shell**, and then click **Run as Administrator**. + + +2. At the Microsoft PowerShell Command Prompt, type the following (press Enter after each line): + + ``` + +$w = Get-SPWebApplication -identity http:// +$w.GrantAccessToProcessIdentity("\\") + ``` + + +> [!IMPORTANT:] + + + + + +Once you have granted content database access to the application pool account, the next step is to start the Excel Calculation Services service. +## Start the Excel Calculation Services service + + +In order to use Excel Services, you must start the Excel Calculation Services service on at least one application server in the farm. Use the following procedure to start the service. **To start the Excel Calculation Services service** +1. On the Central Administration home page, in the **System Settings** section, click **Manage services on server**. + + +2. To select the server where you want to start the service, above the **Service** list, click the **Server** drop-down list, and then click **Change Server** and choose the appropriate server. + + +3. In the **Service** list, click **Start** next to **Excel Calculation Services**. + + +After the Excel Calculation Services service has been started, the next step is to create an Excel Services service application. +## Create an Excel Services service application + + +Use the following procedure to create an Excel Services service application. **To create an Excel Services service application** +1. On the Central Administration home page, under **Application Management**, click **Manage service applications**. + + +2. On the Manage Service Applications page, click **New**, and then click **Excel Services Application**. + + +3. In the **Name** section, type a name for the service application in the text box. + + +4. Select the **Create new application pool** option and type a name for the application pool in the text box. + + +5. Select the **Configurable** option, and from the drop-down list, select the account that you created to run the application pool. + + +6. Click **OK**. + + + +## Additional steps + + +Once you have created the service application, you are ready to start using Excel Services. See the following articles for additional configuration steps. +- [Manage Excel Services global settings (SharePoint Server 2013)](html/manage-excel-services-global-settings-sharepoint-server-2013.md) + + +- [Manage Excel Services trusted file locations (SharePoint Server 2013)](html/manage-excel-services-trusted-file-locations-sharepoint-server-2013.md) + + +- [Manage Excel Services trusted data providers (SharePoint Server 2013)](html/manage-excel-services-trusted-data-providers-sharepoint-server-2013.md) + + +- [Manage Excel Services trusted data connection libraries (SharePoint Server 2013)](html/manage-excel-services-trusted-data-connection-libraries-sharepoint-server-2013.md) + + +- [Manage Excel Services user defined function assemblies (SharePoint Server 2013)](html/manage-excel-services-user-defined-function-assemblies-sharepoint-server-2013.md) + + +- [Manage Excel Services data model settings (SharePoint Server 2013)](html/manage-excel-services-data-model-settings-sharepoint-server-2013.md) + + + +# See also + +#### + + **Excel Services cmdlets in SharePoint Server 2013** + + + + + + + + diff --git a/SharePoint/configure-forefront-tmg-for-a-hybrid-environment.md b/SharePoint/configure-forefront-tmg-for-a-hybrid-environment.md new file mode 100644 index 0000000000..5ec72728c0 --- /dev/null +++ b/SharePoint/configure-forefront-tmg-for-a-hybrid-environment.md @@ -0,0 +1,223 @@ +--- +title: Configure Forefront TMG for a hybrid environment +ms.prod: SHAREPOINT +ms.assetid: 46aecccb-6196-48b4-a889-cbd408354d56 +--- + + +# Configure Forefront TMG for a hybrid environment + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-22* **Summary:** Learn how to configure Forefront TMG 2010 as a reverse proxy device in a SharePoint hybrid environment.This article tells you how to set up Forefront Threat Management Gateway (TMG) 2010 for use as a reverse proxy for a hybrid SharePoint Server environment.For complete information about Forefront Threat Management Gateway (TMG) 2010, see [Forefront Threat Management Gateway (TMG) 2010](https://technet.microsoft.com/en-us/library/ff355324.aspx).In this article: +- [Before you begin](#byb) + + +- [Install TMG 2010](#install) + + +- [Install the Secure Channel certificate](#cert) + + +- [Configure TMG 2010](#config) + + + +## Before you begin + + +Before you begin, there are a few things you need to know: +- TMG has to be deployed in an **edge configuration**, with at least one network adapter connected to the Internet and configured for the external network in TMG and at least one network adapter connected to the intranet network and configured for the internal network in TMG. + + +- The TMG server has to be a domain member in the Active Directory domain forest that contains your Active Directory Federation Services (AD FS) 2.0 server. The TMG server has to be joined to this domain to use SSL client certificate authentication, which is used for authenticating inbound connections from SharePoint Online. + + > [!SECURITY] + +- Deploying TMG 2010 for use in a SharePoint Server hybrid environment in a back-to-back configuration is theoretically possible but has not been tested and may not work. + + +- TMG 2010 includes both diagnostic logging and a real-time logging interface. Logging plays an important role in troubleshooting issues with connectivity and authentication between SharePoint Server and SharePoint Online. Identifying the component that is causing a connection failure can be challenging, and TMG logs are the first place you should look for clues. Troubleshooting can involve comparing log events from TMG logs, SharePoint Server ULS logs, Windows Server event logs, and Internet Information Services (IIS) logs on multiple servers. + + +For more information on how to configure and use logging in TMG 2010, see [Using diagnostic logging](https://technet.microsoft.com/en-us/library/dd897109.aspx).For more information on general TMG 2010 troubleshooting, see [Forefront TMG Troubleshooting](https://technet.microsoft.com/en-us/library/dd897100.aspx).For more information on troubleshooting techniques and tools for SharePoint Server hybrid environments, see **Troubleshooting hybrid environments**. +## Install TMG 2010 + + +If you have not already installed TMG 2010 and configured it for your network, use this section to install TMG 2010 and prepare the TMG system. **Install TMG 2010** +1. Install Forefront TMG 2010 if it is not already installed. For more information on installing TMG 2010, see [Forefront TMG Deployment](https://go.microsoft.com/fwlink/p/?LinkId=403873). + + +2. Install all the available service packs and updates for TMG 2010. For more information, see [Installing Forefront TMG Service Packs](https://technet.microsoft.com/en-us/library/ff717843.aspx). + + +3. Join the TMG server computer to the on-premises Active Directory domain if it is not already a domain member. + + For more information on deploying TMG 2010 in a domain environment, see [Workgroup and domain considerations](https://technet.microsoft.com/en-us/library/dd897048.aspx). + + + +## Import the Secure Channel SSL certificate + + +You must import the Secure Channel SSL certificate into both the Personal store of the local computer account and the Personal store of the Microsoft Forefront TMG Firewall service account (fwsvc). +### + +![Edit icon](images/)The location of the **Secure Channel SSL certificate** is recorded in **Row 1** (Secure Channel SSL Certificate location and Filename) of **Table 4b: Secure Channel SSL Certificate**.
If the certificate contains a private key, you will need to provide the certificate password, which is recorded in **Row 4** (Secure Channel SSL Certificate password) of **Table 4b: Secure Channel SSL Certificate**.
**Import the certificate** +1. Copy the certificate file from the location specified in the worksheet to a folder on the local hard disk. + + +2. On the reverse proxy server, open MMC and add the **Certificate Management** snap-in for both the local **computer account** and the local **fwsrv service account**. + + > [!NOTE:] + +3. Import the Secure Channel SSL certificate to the **Personal** certificate store of the computer account. + + +4. Import the Secure Channel SSL certificate to the **Personal** certificate store of the **fwsrv** service account. + + +For more information about how to import an SSL certificate, see [Import a Certificate](https://technet.microsoft.com/en-us/library/cc754489.aspx). +## Configure TMG 2010 + + +In this section, you configure a **web listener** and a **publishing rule** that will receive inbound requests from SharePoint Online and relay them to the primary web application of your SharePoint Server farm. The web listener and publishing rule work together to define the connection rules and to pre-authenticate and relay the requests. You configure the web listener to authenticate inbound connections using the Secure Channel certificate you installed in the last procedure.For more information on configuring publishing rules in TMG, see [Configuring Web publishing](https://technet.microsoft.com/en-us/library/cc441546.aspx).For more information on SSL bridging in TMG 2010, see [About SSL bridging and publishing](https://technet.microsoft.com/en-us/library/cc995200.aspx).Use the following procedure to create the publishing rule and web listener. **Create the publishing rule and web listener** +1. In the Forefront TMG Management Console, in the left navigation pane, right-click **Firewall Policy**, and then click **New**. + + +2. Select **SharePoint Site Publishing Rule**. + + +3. In the **New SharePoint Publishing Rule Wizard**, in the **Name** text box, type the name of the publishing rule (for example, "Hybrid Publishing Rule"). Click **Next**. + + +4. Select **Publish a single Web site or load balancer**, and then click **Next**. + + +5. To use **HTTP** for the connection between TMG and your SharePoint Server farm, select **Use non-secured connection to connect the published Web server or server farm**, and then click **Next**. + + To use **HTTPS** for the connection between TMG and your SharePoint Server farm, select **Use SSL to connect the published Web server or server farm**, and then click **Next**. + + > [!NOTE:] + +6. In the **Internal Publishing Details** dialog box, in the **Internal site name** text box, type the internal DNS name of the *bridging URL* , and then click **Next**. This is the URL that the TMG server will use to relay requests to the primary web application. + + > [!NOTE:] + + +### + +![Edit icon](images/) The Bridging URL is recorded in one the following locations in the SharePoint Hybrid worksheet:
If your primary web application is configured with a *host-named site collection* , use the value in **Row 1** (Primary web application URL) of **Table 5a: Primary web application (host-named site collection)**.
If your primary web application is configured with a *path-based site collection* , use the value in **Row 1** (Primary web application URL) of **Table 5b: Primary web application (path-based site collection without AAM)**.
If your primary web application is configured with a *path-based site collection with AAM* , use the value in **Row 5** (Primary web application URL) of **Table 5c: Primary web application (path-based site collection with AAM)**.
7. In the **Use a computer name or IP address to connect to the published server** box, optionally type the IP address or the fully qualified domain name (FQDN) of the primary web application or network load balancer, and then click **Next**. + + > [!NOTE:] + +8. In the **Public Name Details** dialog box, accept the default setting on the **Accept requests for** menu. In the **Public name** text box, type the host name of your *External URL* (for example, "sharepoint.adventureworks.com"), and then click **Next**. This is the host name in the external URL that SharePoint Online will use to connect with your SharePoint Server farm. + + > [!NOTE:] + + +### + +![Edit icon](images/)The External URL is recorded in **Row 3** (External URL) of **Table 3: Public Domain Info** in the SharePoint Hybrid worksheet.9. In the **Select a Web Listener** dialog box, select **New**. + + +10. In the **New Web Listener Wizard** dialog box, in the **Web listener name** text box, type a name for the web listener, and then click **Next**. + + +11. In the Client Connection Security dialog box, select **Require SSL secured connections with clients**, and then click **Next**. + + +12. In the **Web Listener IP Addresses** dialog box, select **External **, and then click **Next**. + + If you want to restrict the listener to listen only on a specific external IP address, click the **Select IP Addresses** button, and then in the **External Network Listener IP Selection** dialog box, select **Specified IP addresses on the Forefront TMG computer in the selected network**. Click **Add** to specify an IP address, and then click **OK**. + + +13. In the **Listener SSL Certificates** dialog box, select **Use a single certificate for this Web Listener**, and click the **Select Certificate** button. In the **Select Certificate** dialog box, select the **Secure Channel SSL certificate** you imported to the TMG computer, click **Select**, and then click **Next**. + + +14. In the **Authentication Settings** dialog box, select **SSL Client Certificate Authentication**, and then click **Next**. This setting enforces client certificate credentials for inbound connections using the Secure Channel certificate. + + +15. Click **Next** to bypass Forefront TMG single sign-on settings. + + +16. Review the **New Listener** summary page, and click **Finish**. This returns you to the Publishing Rule Wizard in which your newly created web listener is automatically selected. + + +17. In the **Select Web Listener** dialog box, in the **Web Listener** drop-down menu, make sure the correct web listener is selected, and click **Next**. + + +18. In the **Authentication Delegation** dialog box, select **No delegation, but client may authenticate directly** from the drop-down menu, and then click **Next**. + + +19. In the **Alternate Access Mapping Configuration** dialog box, select **SharePoint AAM is already configured on the SharePoint server**, and then click **Next**. + + +20. In the **User Sets** dialog box, select the **All Authenticated Users** entry, and click **Remove**. Then click **Add**, and in the **Add Users** dialog box, select **All Users**, and then click **Add**. Click **Close** to close the **Add Users** dialog box, and then click **Next**. + + +21. In the **Completing the New SharePoint Publishing Rule Wizard** dialog box, confirm your settings, and then click **Finish**. + + +There are several settings that you must now verify or change in the publishing rule you just created. **Finalize the publishing rule configuration** +1. In the Forefront TMG Management Console, in the left navigation pane, select **Firewall Policy**, and in the **Firewall Policy Rules** list, right-click the publishing rule you just created, and click **Configure HTTP**. + + +2. In the **Configure HTTP policy for rule** dialog box, on the **General** tab, under **URL Protection**, confirm that both **Verify normalization** and **Block high bit characters** are unchecked, and then click **OK**. + + +3. Right-click the publishing rule you just created again, and click **Properties**. + + +4. In the ** Properties** dialog box, on the **To** tab, uncheck the **Forward the original host header instead of the actual one** box. Under **Proxy requests to published site**, ensure that **Requests appear to come from the original client** is selected. + + +5. On the **Link Translation** tab, ensure that the **Apply link translation to this rule** check box is set correctly: + + - If the internal URL of your primary web application and the external URL are identical, uncheck the **Apply link translation to this rule** check box. + + + - If the internal URL of your primary web application and the external URL are different, check the **Apply link translation to this rule** check box. + + +6. On the **Bridging** tab, under **Web server**, ensure that the correct **Redirect requests to ** check box is checked and that the port in the text box corresponds to the port your internal site is configured to use. + + +7. Click **OK** to save your changes to the publishing rule. + + +8. In the Forefront TMG Management Console, on the top bar, click **Apply** to apply your changes to TMG. It might take one or two minutes for TMG to process your changes. + + +9. To validate your configuration, right-click the new publishing rule from the **Firewall Policy Rules** list, and click **Properties**. + + +10. In the ** Properties** dialog box, click the **Test Rule** button. TMG runs a series of tests to check for connectivity to the SharePoint site and displays the results of the tests in a list. Click each configuration test for a description of the test and its results. Fix any errors that appear. + + + +# See also + +#### + + [Hybrid for SharePoint Server](html/hybrid-for-sharepoint-server.md) + + + + [Configure a reverse proxy device for SharePoint Server hybrid](html/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md) + + + + +#### + + [Configuring Web publishing](https://technet.microsoft.com/en-us/library/cc441546.aspx) + + + + [Forefront Threat Management Gateway (TMG) 2010](https://technet.microsoft.com/en-us/library/ff355324.aspx) + + + + + + + + diff --git a/SharePoint/configure-hybrid-business-connectivity-servicesroadmap.md b/SharePoint/configure-hybrid-business-connectivity-servicesroadmap.md new file mode 100644 index 0000000000..1f9270c12e --- /dev/null +++ b/SharePoint/configure-hybrid-business-connectivity-servicesroadmap.md @@ -0,0 +1,25 @@ +--- +title: Configure hybrid Business Connectivity Services - roadmap +ms.prod: SHAREPOINT +ms.assetid: 405d8d1a-2952-4f51-9527-c2c305b76a29 +--- + + +# Configure hybrid Business Connectivity Services - roadmap + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-21* **Summary:** Learn how to configure hybrid Business Connectivity Services between SharePoint Server and SharePoint Online.This article provides the roadmap for configuring hybrid Microsoft Business Connectivity Services between SharePoint Online in Office 365 for enterprises and SharePoint Server.Follow these steps in the order shown. If you already completed a step when you did a different roadmap, skip that step and go to the next. +### + +StepDescription **1. [Configure Office 365 for SharePoint hybrid](html/configure-office-365-for-sharepoint-hybrid.md)**
Configure your Office 365 tenant for a hybrid environment, including registering your domain, configuring UPN suffixes, and synchronizing your user accounts.
**2. [Set up SharePoint services for hybrid environments](html/set-up-sharepoint-services-for-hybrid-environments.md)**
Configure the needed SharePoint services for hybrid search, including User Profiles, MySites, and the Application Management service.
**3. [Configure server-to-server authentication from SharePoint Server to SharePoint Online](html/configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o.md)**
Configure server-to-server authentication between SharePoint Server and Office 365.
**4. Synchronize user profiles**
Run SharePoint user profile synchronization to update the SharePoint User Profile Store with the new account UPNs that you added when you configured Office 365. For information about how to run profile sync, see [Manage user profile synchronization in SharePoint Server](html/manage-user-profile-synchronization-in-sharepoint-server.md).
**5. [Configure inbound connectivity](html/configure-connectivity-from-office-365-to-sharepoint-server.md)**
Configure authentication from Office 365 to SharePoint Server.
**6. [Configure a reverse proxy device for SharePoint Server hybrid](html/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md)**
Configure a reverse proxy device for your on-premises environment.
**7. [Deploy a Business Connectivity Services hybrid solution in SharePoint](html/deploy-a-business-connectivity-services-hybrid-solution-in-sharepoint.md)**
Deploy the Business Connectivity Services solution.
+# See also + +#### + + [Plan SharePoint Server hybrid](html/plan-sharepoint-server-hybrid.md) + + + + + + + + diff --git a/SharePoint/configure-hybrid-federated-search-from-sharepoint-online-to-sharepoint-serverroa.md b/SharePoint/configure-hybrid-federated-search-from-sharepoint-online-to-sharepoint-serverroa.md new file mode 100644 index 0000000000..3ab1589526 --- /dev/null +++ b/SharePoint/configure-hybrid-federated-search-from-sharepoint-online-to-sharepoint-serverroa.md @@ -0,0 +1,25 @@ +--- +title: Configure hybrid federated search from SharePoint Online to SharePoint Server - roadmap +ms.prod: SHAREPOINT +ms.assetid: f6d49e94-ad29-456d-8cd9-f940154d5a0e +--- + + +# Configure hybrid federated search from SharePoint Online to SharePoint Server - roadmap + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-21* **Summary:** Learn how to configure hybrid federated search from SharePoint Server to SharePoint Online.This article provides the roadmap for configuring hybrid search from SharePoint Online in Office 365 for enterprises to SharePoint Server, which allows your users to use see search results from SharePoint Server when searching from Office 365.Follow these steps in the order shown. If you already completed a step when you did a different roadmap, skip that step and go to the next. +### + +StepDescription **1. [Configure Office 365 for SharePoint hybrid](html/configure-office-365-for-sharepoint-hybrid.md)**
Configure your Office 365 tenant for a hybrid environment, including registering your domain, configuring UPN suffixes, and synchronizing your user accounts.
**2. [Set up SharePoint services for hybrid environments](html/set-up-sharepoint-services-for-hybrid-environments.md)**
Configure the needed SharePoint services for hybrid search, including User Profiles, MySites, and the Application Management service.
**3. [Configure server-to-server authentication from SharePoint Server to SharePoint Online](html/configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o.md)**
Configure server-to-server authentication between SharePoint Server and Office 365.
**4. Synchronize user profiles**
Run SharePoint user profile synchronization to update the SharePoint User Profile Store with the new account UPNs that you added when you configured Office 365. For information about how to run profile sync, see [Manage user profile synchronization in SharePoint Server](html/manage-user-profile-synchronization-in-sharepoint-server.md).
**5. [Configure inbound connectivity](html/configure-connectivity-from-office-365-to-sharepoint-server.md)**
Configure authentication from Office 365 to SharePoint Server.
**6. [Configure a reverse proxy device for SharePoint Server hybrid](html/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md)**
Configure a reverse proxy device for your on-premises environment.
**7. [Display hybrid federated search results in SharePoint Online](html/display-hybrid-federated-search-results-in-sharepoint-online.md)**
Configure your search service application to display search results from SharePoint Server in Office 365.
+# See also + +#### + + [Plan SharePoint Server hybrid](html/plan-sharepoint-server-hybrid.md) + + + + + + + + diff --git a/SharePoint/configure-hybrid-federated-search-from-sharepoint-server-to-sharepoint-onlineroa.md b/SharePoint/configure-hybrid-federated-search-from-sharepoint-server-to-sharepoint-onlineroa.md new file mode 100644 index 0000000000..2884bd2506 --- /dev/null +++ b/SharePoint/configure-hybrid-federated-search-from-sharepoint-server-to-sharepoint-onlineroa.md @@ -0,0 +1,32 @@ +--- +title: Configure hybrid federated search from SharePoint Server to SharePoint Online - roadmap +ms.prod: SHAREPOINT +ms.assetid: 445bce79-f6d6-4ab6-9d50-f0672cd093f4 +--- + + +# Configure hybrid federated search from SharePoint Server to SharePoint Online - roadmap + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-21* **Summary:** Learn how to configure hybrid federated search from SharePoint Server to SharePoint Online.This article provides the roadmap for configuring hybrid search from SharePoint Server to SharePoint Online in Office 365 for enterprises, which allows your users to use see search results from Office 365 when searching from SharePoint Server.Follow these steps in the order shown. If you already completed a step when you did a different roadmap, skip that step and go to the next. +### + +StepDescription **1. [Configure Office 365 for SharePoint hybrid](html/configure-office-365-for-sharepoint-hybrid.md)**
Configure your Office 365 tenant for a hybrid environment, including registering your domain, configuring UPN suffixes, and synchronizing your user accounts.
**2. [Set up SharePoint services for hybrid environments](html/set-up-sharepoint-services-for-hybrid-environments.md)**
Configure the needed SharePoint services for hybrid search, including User Profiles, MySites, and the Application Management service.
**3. [Configure server-to-server authentication from SharePoint Server to SharePoint Online](html/configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o.md)**
Configure server-to-server authentication between SharePoint Server and Office 365.
+> [!NOTE:] + + + + + + **4. [Display hybrid federated search results in SharePoint Server](html/display-hybrid-federated-search-results-in-sharepoint-server.md)**
Configure your search service application to display search results from Office 365.
+# See also + +#### + + [Plan SharePoint Server hybrid](html/plan-sharepoint-server-hybrid.md) + + + + + + + + diff --git a/SharePoint/configure-hybrid-onedrive-for-business.md b/SharePoint/configure-hybrid-onedrive-for-business.md new file mode 100644 index 0000000000..0c6a704d04 --- /dev/null +++ b/SharePoint/configure-hybrid-onedrive-for-business.md @@ -0,0 +1,106 @@ +--- +title: Configure hybrid OneDrive for Business +ms.prod: SHAREPOINT +ms.assetid: f1dfdac2-81ad-452f-b5b6-df9e5a8e976e +--- + + +# Configure hybrid OneDrive for Business + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Office 365, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-22* **Summary:** Connect your on-premises SharePoint Server environment with OneDrive for Business in Office 365. **This article is part of a roadmap of procedures for configuring SharePoint hybrid solutions. Be sure you're [following a roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md) when you do the procedures in this article.**You can redirect users to OneDrive for Business in Office 365 when they click **OneDrive** or **Sites** on the navigation bar. In this article are the steps you need to configure your on-premises environment to connect with OneDrive for Business in Office 365. You can find an overview of the process in [Plan for hybrid OneDrive for Business](html/plan-for-hybrid-onedrive-for-business.md). +## Some things that you need + +To use OneDrive for Business in Office 365, your users must have **Create Personal Site** and **Follow People and Edit Profile** permissions. Both are controlled by the user permissions in the User Profile service application. **** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. In your on-premises SharePoint Server environment, go to **Central Administration** > **Manage Service Applications**. + + +3. Click the User Profile Service Application. + + +4. On the **Manage Profile Service** page, under **People**, click **Manage User Permissions**. + + +5. In the **Permissions for User Profile Service Application** dialog box, click **All Authenticated Users** (or a specific audience that you intend to use as a pilot group of users). + + +6. Verify that the **Create Personal Site** and **Follow People and Edit Profile** permission check boxes are selected. + + +When you configure the OneDrive for Business link, you need to know the URLs for your My Sites site collection in SharePoint Server and in SharePoint Online.To find the My Sites URL in Office 365, on the **Admin** menu, click **SharePoint**. In the **Site Collections** list, look for the site collection that contains -my.sharepoint.com. +## Create an audience (if necessary) + + +If you want to redirect only a specific set of your users from your on-premises environment to OneDrive for Business in Office 365, you need to use an audience to identify that set of users. If you have an audience set up already that contains just those users, you can use that. Otherwise, you need to create an audience in SharePoint Server 2016. See **Create an audience for SharePoint 2013** for information about how to create an audience for SharePoint. You can also use Microsoft PowerShell cmdlets to create an audience.If you want all users to be redirected to Office 365 for OneDrive for Business, select **Everyone** instead of using a specific audience when you configure the settings.For specific steps to create an audience, see **Create an audience for SharePoint 2013**. +## Configure hybrid OneDrive for Business settings in Central Administration + + +Now you can configure the settings in Central Administration to set up the redirection to Office 365. **To configure OneDrive for Business redirection** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + +2. On the Central Administration website, choose **Office 365** > **Configure hybrid OneDrive and Sites features**. + + +3. On the **Configure hybrid OneDrive and Sites features** links page, in the **My Site URL** box, type the *My Site* *URL* that you got from Office 365 portal administration. + + +4. Specify an audience. Choose **Everyone** if you want all users to be redirected. Or choose **Use a specific audience** and type the *audience name* for the audience that contains your Office 365 users. + + +5. Choose the **OneDrive only** option. + + +6. Choose **OK**. + + + +## Verify that then OneDrive for Business links work as expected + + +It can take up to a minute for the changes to be updated in the User Profile service application for your on-premises farm. Because the link may be stored in the user’s browser cache, we recommend you wait 24 hours and then verify the links are working.To check that the links are working as expected, have one of the users in the audience that is using the Office 365 option for OneDrive for Business sign in to your on-premises environment. From the user's personal site, have the user choose **OneDrive** from the app launcher.If the user is redirected to Office 365 for OneDrive for Business, everything is working as expected.If users want to browse to their OneDrive for Business directory directly, they can go to https:// ** .onedrive.com in the browser. For example, https://contoso.onedrive.com will take users of Contoso tenancy to their OneDrive for Business document library. This is a simple way to bookmark the link for users of OneDrive for Business. Note that rich clients might not recognize this short URL. +## (Optional) Create a search vertical + + +You can set up a search vertical so that you can search content stored in OneDrive for Business. The specific steps to set up the search vertical are in the article [Set up Search of OneDrive for Business in Office 365 from SharePoint Server](html/set-up-search-of-onedrive-for-business-in-office-365-from-sharepoint-server.md). +## (Optional) Customize the Office 365 navigation experience + + +Now that your users are set up to be redirected to Office 365, you can customize what they see on the navigation bar there. By default, the navigation bar contains the following links: SkyDrive, Yammer or Newsfeed, and Sites. If you intend for your users to use only OneDrive for Business, you can remove the other links. If you want to allow your users to interact with Yammer or the SharePoint Newsfeed features or to create team sites in Office 365, you can leave those links on the navigation bar. +> [!NOTE:] + + + + + + **To customize the navigation bar** +1. Log on to Office 365 with a tenant administrator account. + + +2. On the **Admin** tab, choose **SharePoint**. + + +3. Choose **Settings** on the left. + + +4. In the **Top Navigation Bar User Experience** section, specify the links to show or hide on the navigation bar. + + +5. Choose **OK** to save the settings and update the navigation bar. + + + +# See also + +#### + + [Plan for hybrid OneDrive for Business](html/plan-for-hybrid-onedrive-for-business.md) + + + + + + + + diff --git a/SharePoint/configure-hybrid-onedrive-for-businessroadmap.md b/SharePoint/configure-hybrid-onedrive-for-businessroadmap.md new file mode 100644 index 0000000000..3837c53c20 --- /dev/null +++ b/SharePoint/configure-hybrid-onedrive-for-businessroadmap.md @@ -0,0 +1,29 @@ +--- +title: Configure hybrid OneDrive for Business - roadmap +ms.prod: SHAREPOINT +ms.assetid: 81ea6763-c331-453b-80f7-8028c3e551f8 +--- + + +# Configure hybrid OneDrive for Business - roadmap + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** OneDrive for Business, SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-21* **Summary:** Learn how to configure hybrid OneDrive for Business with Office 365.This article provides the roadmap for configuring OneDrive for Business hybrid, which allows your users to use OneDrive for Business in Office 365 with SharePoint Server.Follow these steps in the order shown. If you already completed a step when you did a different roadmap, skip that step and go to the next. +### + +StepDescription **1. [Configure Office 365 for SharePoint hybrid](html/configure-office-365-for-sharepoint-hybrid.md)**
Configure your Office 365 tenant for a hybrid environment, including registering your domain, configuring UPN suffixes, and synchronizing your user accounts.
**2. [Set up SharePoint services for hybrid environments](html/set-up-sharepoint-services-for-hybrid-environments.md)**
Configure the needed SharePoint services for hybrid search, including User Profiles, MySites, and the Application Management service.
**3. (SharePoint Server 2013 only) [Install Service Pack 1 for SharePoint Server 2013](https://go.microsoft.com/fwlink/p/?LinkId=521936)**
Be sure you've installed at least Service Pack 1 on your SharePoint Server 2013 farm or the OneDrive for Business redirect option will not be available.
**4. [Redirect OneDrive for Business users to Office 365](html/configure-hybrid-onedrive-for-business.md)**
Configure hybrid OneDrive for Business in the SharePoint Central Administration website.
**5. Quick test**
Check to make sure OneDrive for Business is being redirected to Office 365:
Log in to a SharePoint Server as a regular user. (Be sure you're a member of the correct audience if you used audiences.)
Click **OneDrive** in the app launcher.
The URL in the browser address bar should change from that of your on-premises farm, to the personal site URL of SharePoint Online.
+# See also + +#### + + [Hardware and software requirements for SharePoint hybrid](html/hardware-and-software-requirements-for-sharepoint-hybrid.md) + + + + [Accounts needed for hybrid configuration and testing](html/accounts-needed-for-hybrid-configuration-and-testing.md) + + + + + + + + diff --git a/SharePoint/configure-hybrid-sites-featuresroadmap.md b/SharePoint/configure-hybrid-sites-featuresroadmap.md new file mode 100644 index 0000000000..9a52caad8d --- /dev/null +++ b/SharePoint/configure-hybrid-sites-featuresroadmap.md @@ -0,0 +1,45 @@ +--- +title: Configure hybrid sites features - roadmap +ms.prod: SHAREPOINT +ms.assetid: 4bd426f4-105c-41cf-a4b8-815db62191ce +--- + + +# Configure hybrid sites features - roadmap + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Office 365 Enterprise, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-21* **Summary:** Learn how to configure hybrid sites features for SharePoint hybrid with Office 365.This article provides a roadmap for configuring [hybrid sites features](html/plan-for-hybrid-sites-features.md). Follow these steps in the order shown. If you already completed a step when you followed a different roadmap, skip that step, and go to the next one. +### + +StepDescription1. [Configure Office 365 for SharePoint hybrid](html/configure-office-365-for-sharepoint-hybrid.md)
Configure your Office 365 for enterprises tenant for a hybrid environment, including registering your domain, configuring UPN suffixes, and synchronizing your user accounts.
2. [Set up SharePoint services for hybrid environments](html/set-up-sharepoint-services-for-hybrid-environments.md)
Configure the needed SharePoint services for hybrid search, including User Profiles, MySites, and the Application Management service.
**3. (SharePoint Server 2013 only) [Install the September PU for SharePoint Server 2013](https://technet.microsoft.com/library/mt715807.aspx)**
Install the September 2015 PU or higher for SharePoint Server 2013. (We recommend installing the latest PU.)
3. [Run Hybrid Picker](html/run-hybrid-picker.md)
Configure hybrid sites features by running the Hybrid Picker in Office 365.
4. Quick test
Check to make sure hybrid sites features are working:
Log in to a SharePoint Server as a regular user. (Be sure you're a member of the correct audience if you used audiences.)
Click the Follow link at the top of the page.
You should see a small pop-up under **Follow** letting you know that you're following the site. Click this pop-up and notice that it navigates to your personal site, and the list of sites you're following in SharePoint Online.
+## The extensible hybrid app launcher + +The app launcher is included as part of SharePoint Server 2016. If you want to add it to SharePoint Server 2013, open the SharePoint 2013 Management Shell and run the following cmdlet:. +``` + +install-SPFeature SuiteNav +``` + +For each site collection where you want to use the feature, run the following cmdlet: + + +``` +Enable-SPFeature suitenav -url +``` + + +# See also + +#### + + [Hardware and software requirements for SharePoint hybrid](html/hardware-and-software-requirements-for-sharepoint-hybrid.md) + + + + [Accounts needed for hybrid configuration and testing](html/accounts-needed-for-hybrid-configuration-and-testing.md) + + + + + + + + diff --git a/SharePoint/configure-incoming-email-for-a-sharepoint-server-farm.md b/SharePoint/configure-incoming-email-for-a-sharepoint-server-farm.md new file mode 100644 index 0000000000..fc30f0ae81 --- /dev/null +++ b/SharePoint/configure-incoming-email-for-a-sharepoint-server-farm.md @@ -0,0 +1,575 @@ +--- +title: Configure incoming email for a SharePoint Server farm +ms.prod: SHAREPOINT +ms.assetid: 88317397-e0cb-47c7-9093-7872bc685213 +--- + + +# Configure incoming email for a SharePoint Server farm + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary: ** Learn how to install and configure the SMTP service, prepare your environment, and configure incoming email for a SharePoint Server 2016 farm.This article describes how to configure incoming email for SharePoint Server 2016. This article also describes how to install and configure the SMTP service to enable incoming email.When incoming email is enabled, SharePoint sites can receive and store email messages and attachments in lists and libraries. This article describes two scenarios, one basic and one advanced. The basic scenario applies to a single-server farm environment and is recommended if you want to use default settings. The advanced scenario applies to a single-server farm or a multiple-server farm and contains several advanced options from which to choose. For more information, see [Plan incoming email for a SharePoint Server 2016 farm](html/plan-incoming-email-for-a-sharepoint-server-2016-farm.md).In this article: +- [Before you begin](#begin) + + +- [Install and configure the SMTP service](#section2) + + +- [Configure incoming email in a basic scenario](#section3) + + +- [Configure incoming email in an advanced scenario](#section4) + + +- [Prepare your environment for incoming email in an advanced scenario](#section5) + + +- [Are attachments missing from email messages that are sent to a SharePoint document library?](#section6) + + + +## Before you begin + + +Before you begin this operation, make sure to review the following information: +- Your system is running SharePoint Server 2016. + + +- Read and understand [Plan incoming email for a SharePoint Server 2016 farm](html/plan-incoming-email-for-a-sharepoint-server-2016-farm.md). + + +- For the basic scenario, each SharePoint application server must be running the Simple Mail Transfer Protocol (SMTP) service and the SharePoint Foundation Web Application service. + + +- For the advanced scenario, you can use one or more servers in the server farm to run the SMTP service and to have a valid SMTP server address. Alternatively, you must know the name of a server outside the farm that is running the SMTP service and the location of the email drop folder. + + +If you have not installed and configured the SMTP service and do not choose to use an email drop folder, you must complete the steps in [Install and configure the SMTP service](#section2) before you configure incoming email. +## Install and configure the SMTP service + + +Incoming email for SharePoint Server 2016 uses the SMTP service. You can use the SMTP service in one of two ways. You can install the SMTP service on one or more servers in the farm, or administrators can provide an email drop folder for email that is forwarded from the service on another server. For more information about the email drop folder option, see [Plan incoming email for a SharePoint Server 2016 farm](html/plan-incoming-email-for-a-sharepoint-server-2016-farm.md). +## Install the SMTP service + +If you are not using a drop folder for email, the SMTP service must be installed on every application server in the farm that you want to configure for incoming email. To install the SMTP service, use the Add Roles and Features Wizard in Server Manager. After you complete the procedure, the SMTP service is installed on the application server. **To install the SMTP service** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the application server. + + +2. Open **Server Manager**, click **Manage**, and select **Add Roles and Features**. + + +3. Click **Next** until the Select features page appears, select **SMTP Server**, click **Add Features**, and then click **Next**.. + + +4. On the Confirm Installation Selections page, click **Install**. + + +5. On the Installation Results page, check that the installation finished successfully, and then click **Close**. + + + +## Install IIS 6.0 Management tools + +To manage the SMTP service on Windows Server 2012 R2 and Windows Server 2016, you must use Internet Information Services (IIS) 6.0 Manager. However, if you install the SMTP service on Windows Server 2016, the Add Roles and Features Wizard automatically installs the IIS 6 Management tools. **To install IIS 6.0 Manager** +1. Verify that you have the following administrative credentials: + + - You must be a member of the Administrators group on the front-end web server. + + +2. Open **Server Manager**, click **Manage**, and select **Add Roles and Features**. + + +3. Click **Next** until the Select server roles page appears, select **Management Tools** and **IIS 6 Management compatibility**, and then click **Install**. + + +4. In **Application Server** section, click **Add Role Services**. + + +5. On the Select Role Services page, select **Management Tools** and **IIS 6 Management compatibility**, and then click **Install**. + + + +## Configure the SMTP service + +After you install the SMTP service, you configure it to accept email from the mail server for the domain. You can decide to accept relayed email from all servers except those that you specifically exclude. Alternatively, you can block email from all servers except those that you specifically include. You can include servers individually, in groups by subnet, or in groups by domain.After you configure the service, set it to start automatically. **To configure the SMTP service** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the application server. + + +2. Open Server Manager, click **Tools**, and select **Internet Information Services (IIS) 6.0 Manager**. + + +3. In IIS Manager, expand the server name that contains the SMTP server that you want to configure. + + +4. Right-click the SMTP virtual server that you want to configure, click **Start**, and then right-click the server again and click **Properties**. + + +5. On the **Access** tab, in the **Access control** area, click ** Authentication**. + + +6. In the **Authentication** dialog box, verify that **Anonymous access** is selected, and click **OK**. + + +7. On the **Access** tab, in the **Relay restrictions** area, click **Relay**. + + +8. To enable relaying from any server, click **All except the list below**. + + +9. To accept relaying from one or more specific servers, follow these steps: + +1. Click **Only the list below**. + + +2. Click **Add**, and then add servers one at a time by IP address, or in groups by using a subnet or domain. + + +3. Click **OK** three times to close the **Computer**, **Relay Restrictions**, and **Properties** dialog boxes. + + + **To set the SMTP service to start automatically** +1. Open Server Manager, click **Tools**, and select **Services**. + + +2. In Services, right-click **Simple Mail Transfer Protocol (SMTP)**, and then select **Properties**. + + +3. In the **Simple Mail Transfer Protocol (SMTP) Properties** dialog box, on the **General** tab, in the **Startup type** list, select **Automatic**, and click **OK**. + + + +## Configure incoming email in a basic scenario + + +You can use the following procedure to configure incoming email in a basic scenario by selecting the **Automatic** settings mode and using the default settings. After you complete the procedure, users can send email to lists and libraries. **To configure incoming email in a basic scenario** +1. Make sure the user account that is performing this procedure is a member of the Administrators group on the server that is running the SharePoint Central Administration website. + + +2. In Central Administration, click **System Settings**, in the **E-Mail and Text Messages (SMS)** section, click **Configure incoming e-mail settings**. + + +3. To enable sites on this server to receive email, on the Configure Incoming E-Mail Settings page, in the **Enable Incoming E-Mail** section, click **Yes**. + + +4. Select the **Automatic** settings mode. + + +5. In the **Incoming E-Mail Server Display Address** section, in the **E-mail server display address** box, type a display name for the email server, for example, mail.fabrikam.com. + + +6. Use the default settings for all other sections, and then click **OK**. + + +After you configure incoming email, users who have Manage Lists permissions can configure email–enabled lists and document libraries. +## Configure incoming email in an advanced scenario + + +The following procedure explains how to configure incoming email in an advanced scenario by selecting the **Advanced** settings mode and additional options that you want to use for your incoming email environment. After you complete the procedure, users can send email to lists and libraries.You can also use the **Automatic** settings mode in an advanced scenario. In the **Automatic** settings mode, you can select to receive email that has been routed through a safe-email server application. In the **Advanced** settings mode, you can instead specify a drop folder. For more information, see [Plan incoming email for a SharePoint Server 2016 farm](html/plan-incoming-email-for-a-sharepoint-server-2016-farm.md).Several of these steps mention prerequisite procedures that are documented in [Prepare your environment for incoming email in an advanced scenario](#section5) later in this article. **To configure incoming email in an advanced scenario** +1. Make sure the user account that is performing this procedure is a member of the Administrators group on the server that is running the SharePoint Central Administration website. + + +2. In Central Administration, click **System Settings**, in the **E-Mail and Text Messages (SMS)** section, click **Configure incoming e-mail settings**. + + +3. To enable sites on this server to receive email, on the Configure Incoming E-mail Settings page, in the **Enable Incoming E-Mail** section, click **Yes**. + + +4. Select the **Advanced** settings mode. + + You can specify a drop folder instead of using an SMTP server. The default location of the drop folder is C:\\inetpub\\mailroot\\drop. You can configure a different location if you want but this drop folder must be the same on all SharePoint Servers. + + > [!NOTE:] + +5. If you want to connect to Directory Management Service, in the **Directory Management Service** section, click **Yes**. + + If you select this option, you must first configure Active Directory Domain Services (AD DS). If you use Exchange Server, you must also configure the DNS Manager and add an SMTP connector. For more information, see [Configure AD DS to be used with Directory Management Service](#ConfigureADDSwithDMS), [Configure DNS Manager](#ConfigureDNSManager), and [Add an SMTP connector in Microsoft Exchange Server 2016](#AddSMTPconnector) later in this article. + +1. In the **Active Directory container where new distribution groups and contacts will be created** box, type the name of the container in the format **OU=** *ContainerName* **, DC=** *domain* **, DC=** *com* , where *ContainerName* is the name of the OU in AD DS, *domain* is the second-level domain, and *com* is the top-level domain. + + The application pool identity account for Central Administration must be delegated the **Create, delete, and manage user accounts** task for the container. Access is configured in the properties for the OU in AD DS. + + +2. In the **SMTP mail server for incoming mail** box, type the name of the SMTP mail server. The server name must match the FQDN in the A resource record entry for the mail server in DNS Manager. + + +3. To accept messages only from authenticated users, click **Yes** for **Accept messages from authenticated users only**. Otherwise, click **No**. + + +4. To enable users to create distribution groups from SharePoint sites, click **Yes** for **Allow creation of distribution groups from SharePoint sites**. Otherwise, click **No**. + + +5. Under **Distribution group request approval settings**, select the actions that will require approval. Actions include the following: + + - **Create new distribution group** + + + - **Change distribution group e-mail address** + + + - **Change distribution group title and description** + + + - **Delete distribution group** + + +6. If you want to use a remote Directory Management Service, select **Use remote** and complete the remainder of this step. Otherwise, click **No** and proceed to step 8. + + If you select this option and you are using Exchange Server, you must configure the DNS Manager and add an SMTP connector. For more information, see [Configure DNS Manager](#ConfigureDNSManager) and [Add an SMTP connector in Microsoft Exchange Server 2016](#AddSMTPconnector) later in this article. The AD DS has most likely already been configured, so you do not need to do this. + +1. In the **Directory Management Service URL** box, type the URL of the Directory Management Service that you want to use. The URL is typically in the following format: http:// *server:adminport* /_vti_bin/SharePointEmailWS.asmx. + + +2. In the **SMTP mail server for incoming mail** box, type the name of the SMTP mail server. The server name must match the FQDN in the A resource record entry for the mail server in DNS Manager on the domain server. + + +3. To accept messages from authenticated users only, click **Yes** for **Accept messages from authenticated users only**. Otherwise, click **No**. + + +4. To allow creation of distribution groups from SharePoint sites, click **Yes** for **Allow creation of distribution groups from SharePoint sites**. Otherwise, click **No**. + + +7. In the **Incoming E-Mail Server Display Address** section, in the **E-mail server display address** box, type a display name for the email server (for example, mail.fabrikam.com). You typically use this option together with the Directory Management Service. + + > [!TIP:] + +8. In the **E-Mail Drop Folder** section, in the **E-mail drop folder** box, type the name of the folder from which the Windows SharePoint Services Timer service retrieves incoming email from the SMTP service. This option is available only if you selected **Advanced** settings mode. If you select this option, ensure that you configure the necessary permissions to the email drop folder. For more information, see [Configure permissions to the email drop folder](#ConfigureDropFolderPerms) later in this article. + + It is useful to have a dedicated email drop folder if the default email drop folder is full or almost full. The default location of the drop folder is C:\\inetpub\\mailroot\\drop. You can configure a different location if you want but this drop folder must be the same on all SharePoint Servers. + + Ensure that the logon account for the SharePoint Timer service has Modify permissions on the email drop folder. For more information, see [To configure e-mail drop folder permissions for the logon account for the SharePoint Timer service](#ToConfigDropFolderPerms) later in this article. + + +9. In the **Safe E-Mail Servers** section, select whether you want to accept email from all email servers or from specific email servers. + + This option is available only if you selected **Automatic** settings mode. + + +10. Click **OK**. + + +After you configure incoming email, site administrators can configure email–enabled lists and document libraries.If you selected Directory Management Service, contact addresses that are created for document libraries appear automatically in Active Directory Users and Computers. The addresses are displayed in the OU of AD DS for SharePoint Server 2016 and must be managed by the administrator of AD DS. The AD DS administrator can add more email addresses for each contact. For more information about AD DS, see [AD DS Getting Started](https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-ds/ad-ds-getting-started). Alternatively, you can configure the computer running Exchange Server by adding a new Exchange Server Global recipient policy. The policy automatically adds external addresses that use the second-level domain name and not the subdomain or host name for SharePoint Server 2016. +## Prepare your environment for incoming email in an advanced scenario + + +Before you configure incoming email in an advanced scenario, you need to perform additional procedures depending on how you want your incoming email environment to work.If you want to use Directory Management Service, you must first configure AD DS, and if you use Exchange Server, you must also configure the DNS Manager and add an SMTP connector.If you want to use a specific email drop folder, ensure that you configure the necessary permissions to the email drop folder.In this section: +- [Configure AD DS to be used with Directory Management Service](#ConfigureADDSwithDMS) + + +- [Configure DNS Manager](#ConfigureDNSManager) + + +- [Addan SMTP connector in Microsoft Exchange Server 2016](#AddSMTPconnector) + + +- [Configure permissions to the email drop folder](#ConfigureDropFolderPerms) + + + +## Configure AD DS to be used with Directory Management Service + + +If you plan to use Directory Management Service, you should first create an organizational unit (OU) and make the necessary configurations in AD DS.To use Directory Management Service on a SharePoint farm, you must configure the application pool identity account for the SharePoint Central Administration website to have the **Create, delete, and manage user accounts** user right to the container that you specify in AD DS. The preferred way to do this is to assign the right to the application pool identity account for the SharePoint Central Administration website. An AD DS administrator must set up the OU and assign the **Create, delete, and manage user accounts** right to the container. The advantage of using Directory Management Service on a remote server farm is that you do not have to assign rights to the OU for multiple farm service accounts.The following procedures are performed on a domain controller that runs Windows Server 2012 R2 with DNS Manager. In some deployments, these applications might run on multiple servers in the same domain. **To create an OU in AD DS** +1. Make sure the user account that is performing this procedure is a member of the Domain Administrators group or a delegated authority for domain administration on the domain controller that is running DNS Manager. + + +2. Open Server Manager, click **Tools**, and then select **Active Directory Users and Computers**. + + +3. In Active Directory Users and Computers, right-click the folder for the second-level domain that contains your server farm, point to **New**, and then click **Organizational Unit**. + + +4. Type the name of the OU, and then click **OK**. + + After you create the OU, you must delegate the **Create, delete, and manage user accounts** right to the container of the OU to manage the user accounts. + + + **To delegate the right to the application pool identity account for Central Administration** +1. Make sure the user account that is performing this procedure is a member of the Domain Administrators group or the Enterprise Administrators group in AD DS, or a delegated authority for domain administration. + + +2. In Active Directory Users and Computers, right-click the OU that you created, and then click **Delegate control**. + + +3. On the Welcome page of the Delegation of Control Wizard, click **Next**. + + +4. On the Users and Groups page, click **Add**, and then type the name of the application pool identity account that the Central Administration uses. + + +5. In the **Select Users, Computers, and Groups** dialog box, click **OK**. + + +6. On the Users or Groups page of the Delegation of Control Wizard, click **Next**. + + +7. On the Tasks to Delegate page of the Delegation of Control Wizard, select the **Create, delete, and manage user accounts** check box, and then click **Next**. + + +8. On the last page of the Delegation of Control Wizard, click **Finish** to exit the wizard. + + +To create and delete child objects, you must also delegate **Create all Child Objects** and **Delete all Child Objects** control of the OU to the application pool identity account for Central Administration. After you complete this procedure, the application pool identity account for Central Administration has **Create all Child Objects** and **Delete all Child Objects** control on the OU, and you can enable incoming email. **To delegate Create all Child Objects and Delete all Child Objects control of the OU to the application pool identity account for Central Administration** +1. Make sure the user account that is performing this procedure is a member of the Domain Administrators group or the Enterprise Administrators group in AD DS, or a delegated authority for domain administration. + + +2. Right-click the OU, and then click **Delegate control**. + + +3. In the Delegation of Control Wizard, click **Next**. + + +4. Click **Add**, and then type the name of the application pool identity account for Central Administration, click **OK**, and then click **Next**. + + +5. On the Tasks to Delegate page of the Delegation of Control Wizard, select **Create a custom task to delegate**, and then click **Next**. + + +6. Click **This folder, existing objects in this folder, and creation of new objects in this folder**, and then click **Next**. + + +7. In the **Permissions** section, select **Create all Child Objects** and **Delete all Child Objects**, and then click **Next**. + + +8. On the last page of the Delegation of Control Wizard, click **Finish** to exit the wizard. + + +Delegating Create all Child Objects and Delete all Child Objects control of the OU to the application pool identity account for Central Administration enables administrators to enable email for a list. After these controls have been delegated, administrators cannot disable email for the list or document library because the Central Administration account tries to delete the contact from the whole OU instead of from the list.To avoid this problem, you must add Delete Subtree permissions for the application pool identity account for Central Administration. Use the following procedure to add these permissions. After this procedure is complete, you can disable incoming email for a list. **To add Delete Subtree permissions for the application pool identity account for Central Administration** +1. Make sure the user account that is performing this procedure is a member of the Domain Administrators group or the Enterprise Administrators group in AD DS, or a delegated authority for domain administration. + + +2. In Active Directory Users and Computers, click the **View** menu, and then click **Advanced Features**. + + +3. Right-click the OU, and then click **Properties**. + + +4. In the **Properties** dialog box, click the **Security** tab, and then click **Advanced**. + + +5. In the **Permission Entries** area, double-click the application pool identity account for Central Administration. + + If the application pool identity account is listed more than once, select the first one. + + +6. In the **Permissions** area, select **Allow**, for **Delete Subtree**. + + +7. Click **OK** three times to close the **Permissions**, **Properties** dialog boxes, and Active Directory Users and Computers. + + +After you add these permissions, you must restart IIS_1st_NoVer for the farm. +## Configure DNS Manager + + +If you are using Exchange Server and are routing email internally in your organization, you must create a host (A) resource record in DNS Manager to associate DNS domain names of computers (or hosts) to their IP addresses. Your organization might already have a configured DNS Manager and an A resource record. If not, then use the following procedure. **To create an A resource record for a subdomain** +1. Make sure the user account that is performing this procedure is a member of the Administrators group on the local computer. + + +2. In DNS Manager, select the forward lookup zone for the domain that contains the subdomain for SharePoint Server 2016. + + +3. Right-click the zone, and then click **New Host (A or AAAA)**. + + +4. In the **New Host** dialog box, in the **Name** text box, type the host or subdomain name for SharePoint Server 2016. + + +5. In the **Fully qualified domain name (FQDN)** text box, type the FQDN for the server that is running SharePoint Server 2016. This is typically in the format *subdomain.domain.com* . + + +6. Ensure that the domains that are listed under the SMTP server in IIS match the FQDN of the server that receives email. If they do not match, you must create a local domain. For instructions, see [To create a local domain](#CreateALocalDomain) later in this article. + + +7. In the **IP address** text box, type the IP address to which you want the FQDN to resolve. + + +8. Click **Add Host**. + + +9. In the message that confirms the creation of the host record, click **OK**, and in the **New Host** dialog box, click **Done**. + + The A resource record now appears in DNS Manager. + + +If you use the **E-mail server display address** option andif the email address to which you are sending email messages is not the same as your server name, you must create a local domain. **To create a local domain** +1. Open Server Manager, click **Tools**, and then select **Internet Information Services (IIS) 6.0 Manager**. + + +2. In IIS Manager, expand the SMTP server right-click **Domains**, and on the **Action** menu, point to **New**, and then click **Domain**. + + +3. In the **New SMTP Domain Wizard** dialog box, select **Alias**, and then click **Next**. + + +4. In the **Domain Name** area, in the **Name** box, type the address of the mail that is to be received by this domain. + + This address must be the same as the one that you specified in step 4 in [To create an A resource record for a subdomain](#AResourceSubdomain), and in step 6b in [To configure incoming email in an advanced scenario](#ToConfigureEmailAdvanced). + + +5. Click **Finish**. + + +6. In the message that confirms the creation of the host record, click **OK**. + + +7. Restart the SMTP server so that all email messages that are still in the Queue folder move to the Drop folder. The messages are then sent by the Windows SharePoint Services Timer service to their destination list or library. + + + +> [!NOTE:] + + + + + + +## Add an SMTP connector in Microsoft Exchange Server 2016 + + +An SMTP connector gives you more controlover the message flow in your organization. Other reasons to use an SMTP connector are to set delivery restrictions or to specify a specific address space. If you use Exchange Server to route incoming email to SharePoint lists and libraries, you must have an SMTP connector so that all mail that is sent to the SharePoint domain uses the servers that are running the SMTP service.Use the following procedure to add an SMTP connector in Exchange Server. After you complete the procedure, the SMTP connector ensures that incoming email messages are sent to the correct list and library in the farm. **To add an SMTP connector in Exchange Server** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that is running Exchange Server. + + +2. In Exchange Admin Center, click **mail flow**, highlight **send connectors**, and then click the **+** (Add) icon to open the new send connector wizard. + + +3. On the Introduction page, do the following and then click **Next**: + +1. In the **Name** box, type a name for the SMTP connector. + + +2. In the **Select the intended use for this Send connector** box, select the **Custom** usage type for the connector. + + +4. On the Network settings page, select **MX record associated with recipient domain**, and then click **Next**. + + +5. On the Address Space page, click the **+** (Add) icon, and in the **Address Space** webpage dialog, do the following: + +1. In the **Full Qualified Domain Name (FQDN)** box, type an email domain for the connector. This is the FQDN for the SharePoint Server that runs the SMTP service. + + +2. In the **Cost** box, assign an appropriate cost. By default, the cost is 1. + + +6. Click **Save** to return to the Address Space page, and then click **Next**. + + +7. On the Source Server page, click the **+** (Add) icon, and the Select a Server page appears, click **add**, and then click **OK**, finally on the new send connector wizard, click **Finish**. + + The Source server page requires a server tht contains transport roles. + + +For more information, see [Learn more about Send connector types](https://technet.microsoft.com/en-us/library/ms.exch.eac.learnmorenewsendconnectorchoosetype%28v=exchg.160%29.aspx) in the Exchange Server Technical Library. +## Configure permissions to the email drop folder + + +You can specify a particular email drop folder, which enables SharePoint Server 2016 to retrieve incoming email from a network share on another server. You can use this option if you do not want to use an SMTP service. However, the drawback of using this option is that SharePoint Server 2016 cannot detect configuration changes on the remote email server that is delivering email to the drop folder. The result is that SharePoint Server 2016 cannot retrieve email if the location of the email messages has changed. However, this feature is useful if the default email drop folder is full or almost full.If you specified an email drop folder, you must ensure that the application pool identity accounts for Central Administration and for the web application have the required permissions to the email drop folder. +#### Configure email drop folder permissions for the application pool identity account for a web application + +If your deployment uses different application pool identity accounts for Central Administration and for one or more web applications, each application pool identity account must have permissions to the email drop folder. If the application pool identity account for the web application does not have the required permissions, email will not be delivered to document libraries on that web application.In most cases, when you configure incoming email and select an email drop folder, permissions are added for the following worker process groups: +- WSS_Admin_WPG, which includes the application pool identity account for Central Administration and the logon account for the SharePoint Timer service, and has Full Control permissions. + + +- WSS_WPG, which includes the application pool accounts for web applications, and has Read & Execute, List Folder Contents, and Read permissions. + + +In some cases, these groups might not be configured automatically for the email drop folder. For example, if Central Administration is running as the Network Service account, the groups or accounts that are needed for incoming email will not be added when the email drop folder is created. Check to determine whether these groups have been added automatically to the email drop folder. If the groups have not been added automatically, you can add them or add the specific accounts that are required. **To configure email drop folder permissions for the application pool identity account for a web application** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that contains the email drop folder. + + +2. In File Explorer, right-click the drop folder, click **Properties**, and then click the **Security** tab. + + +3. On the **Security** tab, under the **Group or user names** box, click **Edit**. + + +4. In the **Permissions for Drop** dialog box, click **Add**. + + +5. In the **Select Users, Computers, Service Accounts, or Groups** dialog box, in the **Enter the object names to select** box, type the name of the worker process group or application pool identity account for the web application, and then click **OK**. + + This account is listed on the **Identity** tab of the **Properties** dialog box for the application pool in IIS. + + +6. In the **Permissions for** *User or Group* box, next to **Modify**, select **Allow**. + + +7. Click **OK**. + + + +#### Configure email drop folder permissions for the logon account for the SharePoint Timer service + +Ensure that the logon account for the Windows SharePoint Services Timer service has Modify permissions on the email drop folder. If the logon account for the service does not have Modify permissions, email–enabled document libraries will receive duplicate email messages. **To configure email drop folder permissions for the logon account for the SharePoint Timer service** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the server that contains the email drop folder. + + +2. In File Explorer, right-click the drop folder, click **Properties**, and then click the **Security** tab. + + +3. On the **Security** tab, under the **Group or user names** box, click **Edit**. + + +4. In the **Permissions for Drop** dialog box, click **Add**. + + +5. In the **Select Users, Computers, Service Accounts, or Groups** dialog box, in the **Enter the object names to select** box, type the name of the logon account for the SharePoint Timer service, and then click **OK**. + + This account is listed on the **Log On** tab of the **Properties** dialog box for the service in the Services snap-in. + + +6. In the **Permissions for** *User or Group* box, next to **Modify**, select **Allow**. + + +7. Click **OK**. + + + +## Are attachments missing from email messages that are sent to a SharePoint document library? + + +If attachments are missing from email messages that are sent to a SharePoint document library, it might be because you associated the document library with an email address. When you do this, Directory Management Service may not add the following two attributes to the user associated with the email address: +- **internet Encoding = 1310720** + + +- **mAPIRecipient = false** + + +You must use Active Directory Service Interfaces (ADSI) to manually add these two missing attributes.On servers that are running Windows Server 2012 R2 or Windows Server 2016, ADSI Edit is installed when you configure a server as a domain controller by installing the AD DS role. **To add attributes by using ADSI Edit** +1. Click **Start**, and then click **Run**. + + +2. In the **Run** dialog box, type **Adsiedit.msc**, and then click **OK**. + + +3. In the ADSI Edit window, expand **ADSI Edit**, expand **Domain [DomainName]**, expand **DC=DomainName, DC=com**, and then expand **CN=Users**. + + +4. Right-click the user name to which you want to add the missing attributes, and then click **Properties**. + + +5. In the **Properties** dialog box, double-click **Internet Encoding** on the **Attribute Editor** tab. + + +6. In the **Integer Attribute Editor** dialog box, type **1310720** in the **Value** box, and then click **OK**. + + +7. In the **Properties** dialog box, double-click **mAPIRecipient** on the **Attribute Editor** tab. + + +8. In the **Boolean Attribute Editor** dialog box, click **False**, and then click **OK** two times. + + + +# See also + +#### + + [Plan incoming email for a SharePoint Server 2016 farm](html/plan-incoming-email-for-a-sharepoint-server-2016-farm.md) + + + + + + + + diff --git a/SharePoint/configure-monitoring-in-sharepoint-server-2016.md b/SharePoint/configure-monitoring-in-sharepoint-server-2016.md new file mode 100644 index 0000000000..df44ad3eea --- /dev/null +++ b/SharePoint/configure-monitoring-in-sharepoint-server-2016.md @@ -0,0 +1,45 @@ +--- +title: Configure monitoring in SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 274c4c7a-e635-4bc9-85b3-9737620f9909 +--- + + +# Configure monitoring in SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2016-09-16* **Summary:** Learn more about SharePoint diagnostic logging, SharePoint Health Analyzer timer jobs and rules, and usage and health data. +> [!NOTE:] + + + + + + +## Configure monitoring + +Included in this section: +- [Configure diagnostic logging in SharePoint Server](html/configure-diagnostic-logging-in-sharepoint-server.md) + + +- [Configure SharePoint Health Analyzer timer jobs in SharePoint Server 2016](html/configure-sharepoint-health-analyzer-timer-jobs-in-sharepoint-server-2016.md) + + +- [Configure usage and health data collection in SharePoint Server](html/configure-usage-and-health-data-collection-in-sharepoint-server.md) + + +- [Configure SharePoint Health Analyzer rules in SharePoint Server](html/configure-sharepoint-health-analyzer-rules-in-sharepoint-server.md) + + + +# See also + +#### + + [Monitoring and Reporting in SharePoint Server](html/monitoring-and-reporting-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-my-sites-and-onedrive-for-business-in-sharepoint-server.md b/SharePoint/configure-my-sites-and-onedrive-for-business-in-sharepoint-server.md new file mode 100644 index 0000000000..6ba7158838 --- /dev/null +++ b/SharePoint/configure-my-sites-and-onedrive-for-business-in-sharepoint-server.md @@ -0,0 +1,15 @@ +--- +title: Configure My Sites and OneDrive for Business in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 842d7420-32ee-4e82-a8db-2dbb3e01a36c +--- + + +# Configure My Sites and OneDrive for Business in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-07-07* **Summary:** Learn how to configure My Sites and OneDrive for Business in a SharePoint Server 2013 and SharePoint Server 2016 environment.SharePoint Server implements features that make enterprise social computing and collaboration easier. Social networking tools, such as My Sites, and it's associated services such as OneDrive for Business, newfeeds, and the ability to follow people and sites are examples of social computing features. These features enable users to easily capture and share the knowledge and expertise that is needed to do their work. This sharing of information encourages collaboration, improves innovation, and targets relevant content to the people who have to see it. You can adapt content to each user while enabling administrators to set policies to protect privacy. +## TechNet articles about configuring My Sites and OneDrive for Business + +The following articles about how to set up My Sites and OneDrive for Business in SharePoint Server are available to view online. Writers update articles on a continuing basis as new information becomes available and as users provide feedback. +### + +ContentDescription
![Building blocks](images/) [Set up OneDrive for Business in a SharePoint Server on-premises environment](html/set-up-onedrive-for-business-in-a-sharepoint-server-on-premises-environment.md)
Learn how to set up OneDrive for Business in SharePoint Server.

[Configure My Sites in SharePoint Server](html/configure-my-sites-in-sharepoint-server.md)
Learn how to set up My Sites for your users in SharePoint Server.
diff --git a/SharePoint/configure-my-sites-in-sharepoint-server.md b/SharePoint/configure-my-sites-in-sharepoint-server.md new file mode 100644 index 0000000000..69473c8ccf --- /dev/null +++ b/SharePoint/configure-my-sites-in-sharepoint-server.md @@ -0,0 +1,493 @@ +--- +title: Configure My Sites in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: e6600dfa-7f96-4c6f-a1be-b7ad348ac30f +--- + + +# Configure My Sites in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-08-01* **Summary: ** Learn how to set up and configure My Sites in SharePoint Server 2013 and SharePoint Server 2016.This article describes how to set up My Sites in SharePoint Server. Like other tasks in SharePoint Server, there are multiple ways to complete a task. This article provides ordered tasks with prerequisites and procedures to help you set up My Sites in your enterprise.Before you set up My Sites, ensure that you understand the concepts and terminology in [Overview of My Sites in SharePoint Server](html/overview-of-my-sites-in-sharepoint-server.md) and [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md).We recommend that you perform all of the procedures in the order listed for best results, although not all of them are required.In this article: +- [Prerequisites](#prereq) + + +- [Create a My Site host site collection](#mysitehost) + + +- [Add a wildcard inclusion managed path to the Web application](#wildcardpath) + + +- [Connect the Web application to service applications](#connectapps) + + +- [Enable self-service site creation for the Web application](#enableselfsvc) + + +- [Configure My Site settings for the User Profile service application](#configsettings) + + +- [Enable the User Profile Service Application - Activity Feed Job](#timerjobs) + + +- [Next Steps](#nextsteps) + + + +## Prerequisites + + +Because My Sites have dependencies on other service applications and features in SharePoint Server, ensure that you meet the prerequisites in this section before you perform the procedures in this task. +> [!NOTE:] + + + + + + +## Web application + + +Although you can use an existing web application, for optimal performance and security, we recommend that you create the My Site host site collection in a dedicated web application. For more information, see **Create a web application in SharePoint Server**. +> [!IMPORTANT:] + + + + + + +## User Profile service application and profile synchronization + + +Ensure you have a User Profile service application that you want to use for My Sites. +> [!IMPORTANT:] + + + + + + +> [!NOTE:] + + + + + + +## Create a My Site host site collection + + +The My Site host site collection is a site collection that uses the Enterprise site template named **My Site Host**. This site collection must be created in the web application that you want to host My Sites. Generally, this site collection can be created at the root path of the web application, although it can be created as an explicit inclusion managed path deeper in the URL as long as there is a site collection created at the web application root. For more information about how to select the path for the My Site host collection, see [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md). **To create a My Site host site collection** +1. Verify that you have the following administrative credentials: + + - To create a My Site host site collection, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website or a service application administrator for the services related to My Sites. If you are a service application administrator, you must also have permission to create site collections in the web application that you dedicate to host My Sites. + + +2. In Central Administration, click **Application Management**, and then click **Create site collections**. + + +3. On the **Create Site Collection** page, in the **Web Application** section, ensure that the selected web application is the web application that you want to host My Sites. If it is not, expand the list, and then click **Change Web Application**. In the **Select Web Application** dialog box, select a different web application. + + +4. In the **Title and Description** section, type a title and description for the site collection. + + +5. In the **Web Site Address** section, select the URL where you want this site collection created. Generally, you should use the default path (which is displayed as **/** in the user interface), which is the root of the web application. For more information about this path, see [My Sites architecture](plan-for-my-sites-in-sharepoint-server.md#mysitesarch) in [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md). + + +6. In the **Template Selection** section, on the **Enterprise** tab, click **My Site Host**. + + +7. In the **Primary Site Collection Administrator** section, and optionally in the **Secondary Site Collection Administrator** section, type an account in the format *domain\\username* to specify an administrator for the site collection. + + +8. Optionally, in the **Quota Template** section, select a quota template for the My Site host site collection. This quota template does not affect the individual site collections that users create for their My Sites. For more information, see [Planning for storage requirements](plan-for-my-sites-in-sharepoint-server.md#storage) in [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md). + + +9. Click **OK**. Copy this site collection URL for later reference. + + + +## Add a wildcard inclusion managed path to the web application + + +The wildcard inclusion managed path is the path under which separate site collections are created for a user's My Site. Creation of the site collection occurs the first time that a user views the user’s My Site. This functionality is available only when self-service site creation is also enabled. Enabling self-service site creation is discussed later in this article. **To add a wildcard inclusion managed path to the web application** +1. Verify that you have the following administrative credentials: + + - To add managed paths, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website. + + +2. In Central Administration, click **Application Management**, and then click **Manage Web applications**. + + +3. On the **Web Applications Management** page, select the web application that you created to host My Sites. + + +4. On the **Web Applications** tab, in the **Manage** group, click **Managed Paths**. + + +5. In the **Define Managed Paths** dialog box, in the **Add a New Path** section, in the **Path** box, type the path that you want to append to the URL namespace, and then select **Wildcard inclusion**. For example, if your web application URL is http://mysites.contoso.com/ and you want users' individual site collections created under a path named "personal", type **personal** in the **Path** box. Separate My Sites site collections will be created for each user under http://mysites.contoso.com/personal/. + + +6. Click **Add Path**, and then click **OK**. + + +7. Copy this managed path for later reference. + + + +## Connect the web application to service applications + + +The web application that hosts My Sites must be connected to service applications in SharePoint Server. The User Profile service application is required for My Sites. The managed metadata service application and Search service application are highly recommended. For more information, see [My Sites architecture](plan-for-my-sites-in-sharepoint-server.md#mysitesarch) in [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md). Additionally, if you have other SharePoint sites from which you want users to be able to access their My Site and **About Me** links from the upper-right corner menu, connect the web applications of those sites to the User Profile service application. **To connect the web application to service applications** +1. Verify that you have the following administrative credentials: + + - To connect a web application to a service application, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website. + + +2. In Central Administration, in the **Application Management** section, click **Manage Web applications**. + + +3. On the **Web Applications Management** page, select the web application that you created to host My Sites. + + +4. On the **Web Applications** tab, in the **Manage** group, click **Service Connections**. + + +5. In the **Configure Service Application Associations** dialog box, in the **Edit the following group of connections** list, select **default** if the default group contains the service applications that you want to connect to the web application. + + - If you choose **[Custom]**, select any service applications to which you want to connect the web application, including the User Profile service application, the managed metadata service application, and the Search service application. + + +6. Click **OK**. + + + +## Enable self-service site creation for the web application + + +Self-service site creation enables the automatic creation of a separate site collection for users when they first view their My Site. **To enable self-service site creation for the web application** +1. Verify that you have the following administrative credentials: + + - To enable self-service site creation, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website. + + +2. In Central Administration, in the **Application Management** section, click **Manage Web applications**. + + +3. On the **Web Applications** page, select the web application that you created to host My Sites. + + +4. On the **Web Applications** tab, in the **Security** group, click **Self-Service Site Creation**. + + +5. In the **Self-Service Site Creation Management** dialog box, in **Site Collections**, select **On**. Optionally, in **Quota template to apply**, select a quota template. + + +6. In **Start a Site**, choose one of the following options: + +1. **Be hidden from users** + + +2. **Prompt users to create a team site under** + + +3. **Prompt users to create a site collection under any managed path** + + +4. **Display the custom form at** + + +7. Click **OK** to finish. + + +Perform these additional steps to configure permissions for users to create team sites from their My Sites to use site feeds. +1. In the **Policy** group, click **Permission Policy.** + + +2. On **Manage Permission Policy Levels** dialog box, click **Add Permission Policy Level.** + + +3. Type a name for the permission policy. + + +4. Under **Permissions**, in **Site Permissions**, select the **Grant** option for **Create Subsites - Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites**. + + +5. Click **Save**. + + +6. In the **Policy** group, click **User Policy**. + + +7. On **Policy for Web Application** dialog box, click **Add Users**. + + +8. On **Add Users**, in **Zones** select **(All Zones)**, then click **Next**. + + +9. In **Choose Users**, enter the user names of the users that you want to create team sites from their My Site to use site feeds. If all users can create team sites from their My Site to use site feeds, click the **Browse** icon. In **Select People and Groups**, click **All Users**, then click **Everyone**. Click **Add**, and then click **OK**. + + +10. In the **Choose Permissions** section, select the name of the **Permission Policy** created previously. + + +11. Click **Finish**, and then click **OK**. + + + +## Configure My Site settings for the User Profile service application + + +After you have a My Site host site collection and wildcard inclusion managed path configured for My Sites, you can update the My Sites settings in the User Profile service application. Most of these settings are configured during initial deployment and only change infrequently during maintenance operations afterward. **To configure My Site settings for the User Profile service application** +1. Verify that you have the following administrative credentials: + + - To configure My Site settings for the User Profile service application, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website or a service application administrator for the User Profile service application. + + +2. In Central Administration, in the **Application Management** section, click **Manage service applications**. + + +3. Click the User Profile service application that you connected to the web application hosting My Sites earlier in this task. + + +4. On the **Manage Profile Service** page, in the **My Site Settings** section, click **Setup My Sites**. + + +5. On the **My Sites Settings** page, in the **Preferred Search Center** section, specify settings for the search center to direct users to when they search for people or documents from their **About Me** profile page. If you do not have a search center set up yet, you can skip this step and complete it later. For more information, see [Search service application](plan-for-my-sites-in-sharepoint-server.md#searchapp) in [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md). + + +6. In the **My Site Host** section, type the URL of the My Site host site collection that you created earlier in this task. + + +7. The **My Site Host URL in Active Directory** section uses Exchange Autodiscover to allow client and mobile phone applications to find a user's SharePoint Server 2016 My Site. + + +8. In the **Personal Site Location** section, type the wildcard inclusion managed path you configured earlier in this task. By default, **personal** is prepopulated in the box. However, if you chose a different path for your wildcard inclusion managed path, replace **personal** with your path. + + +9. In the **Site Naming Format** section, select a naming format for the My Sites site collections that will be created when users view their My Sites for the first time. For more information about these formats, see [My Sites architecture](plan-for-my-sites-in-sharepoint-server.md#mysitesarch) in [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md). + + +10. In the **Language Options** section, there is an option to specify whether users can select a preferred language for their My Site. However, the current behavior is to default to the installation language for SharePoint. [My Sites architecture](plan-for-my-sites-in-sharepoint-server.md#mysitesarch) in [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md) + + +11. In the **Read Permission Level** section, specify the users or groups that can view other users’ My Sites when they are created. By default, this includes all authenticated users. However, you can select a more specific group or users depending on the needs of your deployment. + + +12. In the **Security Trimming Options** section, specify how system generated posts are checked for permissions before they are displayed in feeds and on the **Tags and Notes** page. + + +13. In the **Newsfeed** section, enable system generated posts to the feed on My Sites by selecting **Enable activities in My Site newsfeeds**. This option is selected by default. This is important in hosted environments where tenants can share the same User Profile service but have different requirements on whether they can enable newsfeeds for their users. + + +14. In the **E-mail Notifications** section, specify an email address to use as the sender email address for My Site email notifications. This account does not have to be a real monitored email address. If you want to receive notifications for newsfeed activities, such as replies to your posts or when someone follows you, select **Enable newsfeed email notifications**. + + > [!IMPORTANT:] + +15. In the **My Site Cleanup** section, specify a new owner of a My Site if the existing My Site user is removed from the profile database. For example, if a user leaves the company and is no longer in the profile database, the user’s My Site will be deleted together with any content. However, before it is deleted, a new owner can recover any important content. Select **Enable access delegation** for the My Site cleanup job to first attempt to assign ownership of the My Site to the user’s manager. If no manager is found, the My Site is assigned to the user specified in **Secondary Owner**. The new owner has two weeks to retrieve content from the My Site before it is deleted. + + +16. In the **Privacy Settings** section, select **Make My Sites Public** to make all users' My Sites public. This option is not selected by default. + + > [!NOTE:] + +17. Click **OK**. + + +For more information about additional timer jobs for My Sites, see [Planning for jobs and schedules](plan-for-my-sites-in-sharepoint-server.md#jobs) in [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md). +## Enable the User Profile Service Application - Activity Feed Job + + +The **User Profile Service Application - Activity Feed Job** creates system generated posts in the feeds for the following events: +- Following a tag + + +- Tagging an item + + +- Birthday celebration + + +- Job title change + + +- Workplace anniversary + + +- Updates to Ask Me About + + +- Posting on a note board + + +After you configure My Sites, enable the **User Profile Service Application - Activity Feed Job** so that users receive system generated posts in the **Newsfeed** on their My Sites.There are other timer jobs related to My Sites that you might want to review and change default settings for. For more information about jobs related to My Sites functionality, see [Planning for jobs and schedules](plan-for-my-sites-in-sharepoint-server.md#jobs) in [Plan for My Sites in SharePoint Server](html/plan-for-my-sites-in-sharepoint-server.md). **To enable the User Profile Service Application - Activity Feed Job** +1. Verify that you have the following administrative credentials: + + - To configure timer jobs, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website. + + +2. In Central Administration, click **Monitoring**, and then click **Review job definitions**. + + +3. On the **Job Definitions** page, in the **View** list, select **Service**. The **Service** list appears. + + - If the **Service** list does not display **User Profile Service**, in **Service**, click **No selection**, then click **Change Service**. On the **Select Service** page, use the arrows in the upper-right corner to locate **User Profile Service**, and then click it. The **Job Definitions** page updates with the User Profile service jobs. + + +4. Click the activity feed job for the User Profile service application that you created in [Prerequisites](#prereq) earlier in this article. The job name is in the format *User_Profile_service_name* - **Activity Feed Job**, where *User_Profile_service_name* is the name that you specified for your User Profile service application. + + +5. On the **Edit Timer Job** page, in the **Recurring Schedule** section, select the interval that you want the job to run. Available intervals are **Minutes**, **Hourly**, **Daily**, **Weekly**, and **Monthly**. Selecting a shorter interval, such as **Minutes** or **Hourly**, ensures that activities appear on users' My Site newsfeeds more frequently. However, it increases load on the system depending on how many activities are available. Selecting a longer interval, such as **Daily**, **Weekly**, or **Monthly**, reduces the number of times the job runs and processes feeds. However, it also means that users receive less frequent updates to activities in their newsfeeds. + + +6. Click **Enable**. + + +7. Optionally, click **Run Now** to run the job immediately without waiting for the next scheduled interval. + + + +## Next steps + + +After you configure My Sites by using the procedures in this article, consider whether you require the following optional procedures: +- [Configure trusted My Site host locations](#trustedmysitehost) + + +- [Configure links to Office client applications](#officelinks) + + +- [Add personalization site links on My Sites (SharePoint Server 2010)](#personalizationsitelink) + + +- [Start related services](#startsvcs) + + + +## Configure trusted My Site host locations + + + **Trusted My Site Host Locations** is an optional feature that prevents a user from creating more than one My Site in an organization with multiple User Profile service applications.User Profile service application administrators can add links to trusted My Site host locations when they want to give users access to My Sites on multiple User Profile service applications. In most cases, links to trusted My Site host locations will be targeted to individual users or groups of users based on an identified business need. The links can be maintained and changed over time as business and user needs change. User Profile service application administrators can delete a link to a trusted My Site host locations when the users targeted by the link no longer require access to My Sites in multiple locations. **To add a trusted My Site host location by using Central Administration** +1. Verify that you have the following administrative credentials: + + - To use Central Administration to add a trusted My Site host location, you must be a member of the Farm Administrators group or a Service Application Administrator for the User Profile service application. + + +2. On the Central Administration Web site, under **Application Management**, click **Manage service applications**. + + +3. On the Manage Service Applications page, select the User Profile service application from the list of service applications. + + +4. On the ribbon, click **Manage**. + + +5. On the Manage Profile Service page, under **My Site Settings**, click **Configure Trusted Host Locations**. + + +6. On the Trusted My Site Host Locations page, click **New Link** to add a trusted My Site host location. + + +7. On the Add Trusted Host Location page, enter the URL of the trusted personal site location in the URL box. + + +8. In the **Description** box, enter a description for the trusted personal site location. + + +9. Optionally, in the **Target Audiences** box, either type the user names or group names in the corresponding box or click **Browse** to select audiences by browsing, and then click **OK**. + + + +## Configure links to Office client applications + + +Users’ My Sites are convenient locations for users to save files that they work on in Office client applications, such as Word, Excel, and PowerPoint. After you configure an environment for My Sites, you can add a link to the **Favorite Links** section that users see when they save documents in the **Save As** dialog box in Office client applications. Users can then select their My Site and save files to the **Documents** library available on their My Site. **To add a link to Office client applications** +1. Verify that you have the following administrative credentials: + + - To add a link to Office client applications, you must be a member of the Administrators group on the computer that is running the SharePoint Central Administration Web site. + + +2. On the Central Administration Web site, under **Application Management**, click **Manage service applications**. + + +3. On the Manage Service Applications page, select the User Profile service application from the list of service applications. + + +4. On the ribbon, click **Manage**. + + +5. On the Manage Profile Service page, under **My Site Settings**, click **Publish Links to Office Client Applications**. + + +6. On the Published links to Office client applications page, click **New Link**. + + +7. On the Add Published Link page, in the **URL** box, type the URL of the location where users will be able to publish links. + + +8. In the **Description** box, type a brief name for this location. + + This is the name that will appear in the Favorite Links section of the Save As dialog box. + + +9. Select the type of the location that this link represents. For example, if the target location is a SharePoint document library, select **Document Library**. + + +10. In the **Target Audiences** box, either type the name of the user or group to add or using the address book to find a user or group to add. Separate multiple user names or group names with a semicolon (;). You may also type All site users to select all users. + + > [!NOTE:] + +11. Click **OK**. + + The new link is displayed in the list of links on the Published links to Office client applications page. + + + +## Promote site links on My Sites + + +If your organization wants to provide important information to users, it can do so by promoting a site link to a user's My Site. When you promote a site link, it appears on all the My Sites in the site collection. They can be used to display important company information. For instance, your organization might want to give users quick access to a timesheet. The destination of the link can be a site within the company intranet or an external site on the Internet. **Add promote a site link to My Sites** +1. Verify that you have the following administrative credentials: + + - To use Central Administration to add a trusted My Site host location, you must be a member of the Farm Administrators group or a Service Application Administrator for the User Profile service application. + + +2. On the Central Administration Web site, under **Application Management**, click **Manage service applications**. + + +3. On the Manage Service Applications page, select the User Profile service application from the list of service applications. + + +4. On the ribbon, click **Manage**. + + +5. On the Manage Profile Service page, under **My Site Settings**, click **Manage promoted sites**. + + +6. On the Promoted Sites page, click **New Link**. + + +7. On the Promoted a Site page, in the **Properties** section, do the following: + +1. In the **URL** box, type the URL of the site to which you want to link. + + +2. In the **Description** box, type a description of the site. + + +3. In the **Owner** box, type the name of an owner for this link, or click Browse to select an owner from the People Picker. + + +4. Leave **Target Audiences** blank. + + When you leave this box blank, the link that you specified in the URL box appears on the My Sites top link bar for all users. + + > [!NOTE:] + +8. Click **OK**. + + + +## Start related services + + +If the related services for My Sites have not been started yet, start them so that My Sites functionality is available in your environment. For more information, see [Start or stop a service in SharePoint Server](html/start-or-stop-a-service-in-sharepoint-server.md). diff --git a/SharePoint/configure-object-cache-user-accounts-in-sharepoint-server.md b/SharePoint/configure-object-cache-user-accounts-in-sharepoint-server.md new file mode 100644 index 0000000000..9b43f035f4 --- /dev/null +++ b/SharePoint/configure-object-cache-user-accounts-in-sharepoint-server.md @@ -0,0 +1,141 @@ +--- +title: Configure object cache user accounts in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: cd646bb3-28c6-4040-866c-7d7936837ade +--- + + +# Configure object cache user accounts in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-19* **Summary: ** Learn how to configure the Portal Super User and Portal Super Reader accounts that are used by the object cache in SharePoint Server 2016 and SharePoint Server 2013.The object cache stores properties about items in SharePoint Server. Items in this cache are used by the publishing feature when it renders web pages. The goals of the object cache are to reduce the load on the computer on which SQL Server is running, and to improve request latency and throughput. The object cache makes its queries as one of two out-of-box user accounts: the Portal Super User and the Portal Super Reader. These user accounts must be properly configured to ensure that the object cache works correctly. The Portal Super User account must be an account that has Full Control access to the web application. The Portal Super Reader account must be an account that has Full Read access to the web application. +> [!IMPORTANT:] + + + + + +This article explains why these object cache user accounts must to be configured and describes how to configure the accounts. For information about the object cache, see [Cache settings operations in SharePoint Server](html/cache-settings-operations-in-sharepoint-server.md).In SharePoint Server, querying for items is linked with the user account that makes the query. Various parts of the publishing feature make queries for which the results are cached in the object cache. These results are cached based on the user making the query. To optimize the cache hit rate and memory requirements, the queries must be based on whether a user can see draft items. When a publishing control requests the object cache to make a query to get data for the control, the cache makes the query, not as the user making the request, but instead it makes the query twice: once as the Portal Super User account and once as the Portal Super Reader account. The results of these two queries are stored in the object cache. The results for the Portal Super User account include draft items, and the results for the Portal Super Reader account include only published items. The object cache then checks the access control lists (ACLs) for the user who initiated the request and returns the appropriate results to that user based on whether that user can see draft items. By adding the Portal Super User and Portal Super Reader accounts to the web application, the cache must store results for only two users. This increases the number of results that are returned for a query and decreases the amount of memory that is needed to store the cache.By default, the Portal Super User account is the site’s System Account, and the Portal Super Reader account is NT Authority\\Local Service. There are two main issues with using the out-of-box accounts. +1. The first issue is that some items get checked out to System Account, so when a query that includes these items is made, the checked out version of the item is returned instead of the latest published version. This is a problem because it is not what a user would expect to have returned, so the cache has to make a second query to fetch the correct version of the file. This negatively affects server performance for every request that includes these items. The same problem would occur for any user who has items checked out, if that user’s account was set to be the Portal Super User account. This is why the accounts configured to be the Portal Super User and the Portal Super Reader should not be user accounts that are used to log into the site. This ensures that the user does not inadvertently check items out and cause problems with performance. + + +2. The default Portal Super Reader account is NT Authority\\Local Service, which is not correctly resolved in a claims authentication application. As a result, if the Portal Super Reader account is not explicitly configured for a claims authentication application, browsing to site collections under this application will result in an "Access Denied" error, even for the site administrator. This error will occur on any site that uses any feature that explicitly uses the object cache, such as the SharePoint Server Publishing Infrastructure, metadata navigation, the Content Query Web Part, or navigation. + + + +## Configure object cache user accounts by using Central Administration and Windows PowerShell + + +You can configure the user accounts for the object cache by the the SharePoint Central Administration website and Microsoft PowerShell. You must first create the accounts in Central Administration and then add the accounts to the web application by using PowerShell. You must add the user accounts to each web application. +> [!CAUTION:] + + + + + + **To create the user accounts by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group on the computer that is running the SharePoint Central Administration website. + + +2. In Central Administration, in the **Application Management** section, click **Manage web applications**, and then click the name of the web application that you want to configure. + + +3. On the **Web Applications** tab, in the **Policy** group, click **User Policy**. + + +4. In the Policy for Web Application window, click **Add Users**. + + +5. From the **Zones** list, select **All zones**, and then click **Next**. + + +6. In the **Users** box, type the user name for the Portal Super User account and then click **Check Names** to ensure that the account name can be resolved by the authentication providers on the application server. + + +7. In the **Choose Permissions** section, check the **Full Control - Has full control** box and then click **Finish**. + + +8. Repeat Steps 5 through 7 for the Portal Super Reader account. + + +9. In the **Choose Permissions** section, check the **Full Read - Has full read-only access** box. + + +10. Click **Finish**. + + +11. Make note of how the names for the Object Cache Super Reader and Object Cache Super User accounts are displayed in the **User Name** column. The displayed strings will be different depending on whether you are using claims authentication for the web application. + + + **To add the user accounts to the web application by using Microsoft PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running PowerShell cmdlets. + + + - Add memberships that are required beyond the minimums above. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + + > [!NOTE:] + +2. Paste the following code into a text editor, such as Notepad: + + ``` + +$wa = Get-SPWebApplication -Identity " " +$wa.Properties["portalsuperuseraccount"] = " " +$wa.Properties["portalsuperreaderaccount"] = " " +$wa.Update() + ``` + +3. Replace the following placeholders with values: + + - ** is the name of the web application to which the accounts will be added. + + + - ** is the account to use for the Portal Super User account as you saw it displayed in the **User Column** field mentioned in Step 14 of the previous procedure. + + + - ** is account to use for the Portal Super Reader account as you saw it displayed in the **User Column** field mentioned in Step 14 of the previous procedure. + + +4. Save the file, naming it SetUsers.ps1. + + > [!NOTE:] + +5. Close the text editor. + + +6. Open **SharePoint Management Shell**. + + +7. Change to the directory where you saved the file. + + +8. At the PowerShell command prompt, type the following command: ./SetUsers.ps1 + + +9. Reset Internet Information Services (IIS). For more information about IISReset, see [Start or Stop the Web Server (IIS 8)](http://go.microsoft.com/fwlink/?LinkID=718159&clcid=0x409). + + + +# See also + +#### + + [Cache settings operations in SharePoint Server](html/cache-settings-operations-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-office-365-for-sharepoint-hybrid.md b/SharePoint/configure-office-365-for-sharepoint-hybrid.md new file mode 100644 index 0000000000..adb1f3bd41 --- /dev/null +++ b/SharePoint/configure-office-365-for-sharepoint-hybrid.md @@ -0,0 +1,82 @@ +--- +title: Configure Office 365 for SharePoint hybrid +ms.prod: SHAREPOINT +ms.assetid: eddba98c-dec8-4fc8-823d-d908bdf0bc83 +--- + + +# Configure Office 365 for SharePoint hybrid + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-21* **Summary:** Get Office 365 for enterprises set up for hybrid integration with SharePoint Server. **This article is part of a roadmap of procedures for configuring SharePoint hybrid solutions. Be sure you're [following a roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md) when you do the procedures in this article.** +## Configure Office 365 for SharePoint hybrid + +You have to set up some basic integration between Office 365 for enterprises and SharePoint Server before you can configure a hybrid environment. Do the following steps as described in this article: +1. Sign up for Office 365. + + +2. Register your domain with Office 365. + + +3. Assign UPN domain suffixes. + + +4. Synchronize accounts with Office 365. + + +5. Assign licenses to your users. + + +You might have already done some of these steps. If so, there's no need to repeat them. But be sure you do each of the steps in the order shown above before you configure a hybrid environment. +## 1. Sign up for Office 365 + +You need an [Office 365 subscription](https://go.microsoft.com/fwlink/p/?LinkID=532795) in order to set up a hybrid environment with SharePoint Server 2016. If you're planning to configure hybrid OneDrive for Business, be sure to subscribe to a plan that includes OneDrive for Business. All other hybrid SharePoint hybrid scenarios require an Enterprise plan that includes SharePoint Online. +## 2. Register your domain with Office 365 + +When you sign up for Office 365, you’re given an initial domain name that looks like contoso.onmicrosoft.com. However, in order to configure a hybrid environment with SharePoint Server 2016, you must register a public domain that you own (such as contoso.com) in Office 365. For detailed information on how to do this, see [Work with domain names in Office 365](https://go.microsoft.com/fwlink/p/?LinkID=534807). +## 3. Assign a UPN domain suffix + + +You have to create a UPN domain suffix in your on-premises Active Directory domain that matches the public domain—for example, contoso.com. Then, you have to assign the UPN domain suffix to each user account that you want to synchronize or federate.The following procedures show how to manually do these tasks. If you have many users whom you want to federate, we recommend that you put all federated user accounts into an organizational unit (OU), and then create a script that will change the UPN domain suffix for each user account in that OU. For supported guidance on DirSync filtering, see [Configure filtering for directory synchronization](https://go.microsoft.com/fwlink/?LinkID=392308). For information about how to create a script for this, see [How Can I Assign a New UPN to All My Users](https://go.microsoft.com/fwlink/?LinkId=392242). **To create the UPN suffix in your on-premises DNS** +1. On the Active Directory server, open **Active Directory Domains and Trusts**. + + +2. In the left pane, right-click the top-level node, and then click **Properties**. + + +3. In the **UPN suffixes** dialog box, enter the domain suffix in the **Alternative UPN suffixes** box that you want for hybrid, and then click **Add** > **OK**. + + +For more information, see [Add user principal name suffixes](https://go.microsoft.com/fwlink/?LinkId=392430) (https://go.microsoft.com/fwlink/?LinkId=392430). **To manually assign a UPN domain suffix to users** +1. In **Active Directory Users and Computers**, in the left pane, click the **Users** node. + + +2. In the **Name** column, right-click the user account that you want to federate, and then click **Properties**. + + +3. In the **Properties** dialog box, click the **Account** tab. + + +4. Select the UPN domain suffix that you added in the previous procedure from the drop-down list, as shown in the following picture. + + ![This figure illustrates the UPN Suffix setting](images/) + + + +5. Repeat steps 2 through 4 for each additional user account that you want to federate. + + + +## 4. Synchronize user accounts with Office 365 + + +In order to configure a hybrid environment, you must synchronize your on-premises Active Directory Domain Services user accounts with Office 365 by configuring one of the following: +- Directory synchronization with password synchronization + + +- Directory synchronization with single sign-on (SSO) + + +If you choose the SSO option, you can also configure password synchronization if you want to as a backup for SSO, but you must configure at least one of the two (password synchronization or SSO). For detailed information on how to configure these options, see [Office 365 integration with on-premises environments](https://go.microsoft.com/fwlink/p/?LinkID=524187). +## 5. Assign licenses to your users + + +Your users must each have a license in Office 365 in order to be able to use hybrid features. Once your accounts are synchronized, [assign licenses to your users](https://go.microsoft.com/fwlink/p/?LinkID=529809). diff --git a/SharePoint/configure-outgoing-email-for-a-sharepoint-server-farm.md b/SharePoint/configure-outgoing-email-for-a-sharepoint-server-farm.md new file mode 100644 index 0000000000..b3e46b30a5 --- /dev/null +++ b/SharePoint/configure-outgoing-email-for-a-sharepoint-server-farm.md @@ -0,0 +1,237 @@ +--- +title: Configure outgoing email for a SharePoint Server farm +ms.prod: SHAREPOINT +ms.assetid: f3ccc8bd-922e-49f6-9929-b5b8a6982d76 +--- + + +# Configure outgoing email for a SharePoint Server farm + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary: ** Learn how to install and configure the SMTP service and configure outgoing email for a SharePoint Server 2016 farm.This article describes how to configure outgoing email for a farm or for a specific web application for SharePoint Server 2016. This article also describes how to install and configure the SMTP service that you must use to enable outgoing email.After you have installed SharePoint Server 2016 and completed the initial configuration of your server farm, you can configure outgoing email. Doing so enables users to create alerts to track such site items as lists, libraries, and documents. In addition, site administrators can receive administrative messages about site administrator issues, such as the information that site owners have exceeded their specified storage space. For more information, see [Plan outgoing email for a SharePoint Server 2016 farm](html/plan-outgoing-email-for-a-sharepoint-server-2016-farm.md).To configure outgoing email for a specific web application, first configure the default outgoing email for all web applications in the farm. If you configure the outgoing email for a specific web application, that configuration will override the default configuration for all web applications in the farm.You can also configure outgoing email for a specific web application by using Microsoft PowerShell. For more information, see the Configure the settings for a specific web application section in [SharePoint Server 2016 outgoing email configuration settings](https://social.technet.microsoft.com/wiki/contents/articles/34167.sharepoint-2016-outgoing-email-configuration-settings.aspx#Configure_using_the_PowerShell).In this article: +- [Before you begin](#begin) + + +- [To install the SMTP service](#section1) + + +- [To install IIS 6.0 Management tools](#section2) + + +- [To configure the SMTP service](#section3) + + +- [To set the SMTP service to start automatically](#section4) + + +- [To configure outgoing email for a farm by using Central Administration](#section5) + + +- [To configure outgoing email for a specific web application by using Central Administration](#section7) + + + +## Before you begin + + +Before you begin this operation, review the following information about prerequisites: +- Your computer is running SharePoint Server 2016. + + +- One or more servers in the server farm are running the Simple Mail Transfer Protocol (SMTP) service and have a valid SMTP server address. Alternatively, you must know the name of a server outside the farm that is running the SMTP service. + + + +## Install and configure the SMTP service + + +Before you can enable outgoing email, you must determine which SMTP server to use. This SMTP server must be configured to allow anonymous SMTP email submissions. The SMTP server can be a server in the farm or outside the farm. +> [!NOTE:] + + + + + + +## Install the SMTP service + +To install the SMTP service, use the Add Features Wizard in Server Manager. The wizard creates a default SMTP configuration. You can customize this default SMTP configuration to meet the requirements of your organization.If you've already installed the SMTP service on a server, skip to [Configure the SMTP service](#ConfigureSMTPservice). **To install the SMTP service** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the application server. + + +2. Open **Server Manager**, click **Manage**, and select **Add Roles and Features**. + + +3. Click **Next** until the Select features page appears, select **SMTP Server**, click **Add Features**, and then click **Next**.. + + +4. On the Confirm Installation Selections page, click **Install**. + + +5. On the Installation Results page, check that the installation finished successfully, and then click **Close**. + + + +## Configure the SMTP service + + +After you install the SMTP service, you configure it to send email messages from servers in the farm.You can decide to send relayed email messages to all servers except those that you specifically exclude. Alternatively, you can block messages to all servers except those that you specifically include. You can include servers individually or in groups by subnet or domain.If you enable anonymous access and relayed email messages, you increase the possibility that the SMTP server will be used to relay unsolicited commercial email messages (spam). It is important to limit this possibility by carefully configuring mail servers to help protect against spam. One way that you can do this is by limiting relayed email messages to a list of specific servers or to a domain, and by preventing relayed email messages from all other servers. +> [!NOTE:] + + + + + + **To install IIS 6.0 Management tools** +1. Verify that you have the following administrative credentials: + + - You must be a member of the Administrators group on the front-end web server. + + +2. Open **Server Manager**, click **Manage**, and select **Add Roles and Features**. + + +3. Click **Next** until the Select server roles page appears, select **Management Tools** and **IIS 6 Management compatibility**, and then click **Install**. + + +4. In **Application Server** section, click **Add Role Services**. + + +5. On the Select Role Services page, select **Management Tools** and **IIS 6 Management compatibility**, and then click **Install**. + + + **To configure the SMTP service** +1. Verify that the user account that is performing this procedure is a member of the Administrators group on the application server. + + +2. Open Server Manager, click **Tools**, and select click **Internet Information Services (IIS) 6.0 Manager**. + + +3. In IIS Manager, expand the server name that contains the SMTP server that you want to configure. + + +4. Right-click the SMTP virtual server that you want to configure, and then click **Start**, and then right-click the server again and click **Properties**. + + +5. On the **Access** tab, in the **Access control** area, click **Authentication**. + + +6. In the **Authentication** dialog box, verify that **Anonymous access** is selected, and click **OK**. + + +7. On the **Access** tab, in the **Relay restrictions** area, click **Relay**. + + +8. To enable relayed email messages to any server, click **All except the list below**. + + +9. To accept relayed email messages from one or more specific servers, follow these steps: + +1. Click **Only the list below**. + + +2. Click **Add**, and then add servers one at a time by IP address, or in groups by using a subnet or domain. + + +3. Click **OK** three times to close the **Computer**, **Relay Restrictions**, and **Properties** dialog boxes. + + +Ensure that the SMTP service is running and set to start automatically. To do this, use the following procedure. **To set the SMTP service to start automatically** +1. Open Server Manager, click **Tools**, and then click **Services**. + + +2. In **Services**, right-click **Simple Mail Transfer Protocol (SMTP)**, and then select **Properties**. + + +3. In the **Simple Mail Transfer Protocol (SMTP) Properties** dialog box, on the **General** tab, in the **Startup type** list, select **Automatic**, and then click **OK**. + + + +## Configure outgoing email for a farm + + +You can configure outgoing email for a farm by using the SharePoint Central Administration website. Use the following procedures to configure outgoing email. After you complete the procedures, users can track changes and updates to individual site collections. In addition, site administrators can, for example, receive notices when users request access to a site. **To configure outgoing email for a farm by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group on the server that is running Central Administration. + + +2. In Central Administration, click **System Settings**. + + +3. On the System Settings page, in the **E-Mail and Text Messages (SMS)** section, click **Configure outgoing e-mail settings**. + + +4. On the Outgoing E-Mail Settings page, in the **Mail Settings** section, type the SMTP server name for outgoing email (for example, mail.example.com) in the **Outbound SMTP server** box. + + +5. In the **From address** box, type the email address as you want it to be displayed to email recipients. + + +6. In the ** Reply-to address** box, type the email address to which you want email recipients to reply. + + +7. In the **Use TLS connection encryption** box, select **Yes** or **No** in the drop-down box. + + +8. In the **SMTP server port** box, type the port number for your SMTP. By default, SMTP is configured on port 25. + + +9. In the **Character set** list, select the character set that is appropriate for your language. + + +10. Click **OK**. + + + +## Configure outgoing email for a specific web application + + +You can configure outgoing email for a specific web application by using the Central Administration website. Use the following procedures to configure outgoing email. +> [!NOTE:] + + + + + + **To configure outgoing email for a specific web application by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group on the server that is running the SharePoint Central Administration website. + + +2. In Central Administration, in the **Application Management** section, click **Manage web applications**. + + +3. On the Web Applications Management page, select a web application, and then in the **General Settings** group on the ribbon, click **Outgoing E-mail**. + + +4. On the Web Application Outgoing E-Mail Settings page, in the **Mail Settings** section, type the name of the SMTP server for outgoing email (for example, mail.fabrikam.com) in the **Outbound SMTP server** box. + + +5. In the **From address** box, type the email address (for example, the site administrator alias) as you want it to be displayed to email recipients. + + +6. In the **Reply-to address** box, type the email address (for example, a help desk alias) to which you want email recipients to reply. + + +7. In the **Use TLS connection encryption** box, select **Yes** or **No** in the drop-down box. + + +8. In the **SMTP server port** box, type the port number for your SMTP. By default, SMTP is configured on port 25. + + +9. In the **Character set** list, click the character set that is appropriate for your language. + + +10. Click **OK**. + + + +# See also + +#### + + [Plan outgoing email for a SharePoint Server 2016 farm](html/plan-outgoing-email-for-a-sharepoint-server-2016-farm.md) + + + + + + + + diff --git a/SharePoint/configure-performancepoint-services.md b/SharePoint/configure-performancepoint-services.md new file mode 100644 index 0000000000..a6d2197fc9 --- /dev/null +++ b/SharePoint/configure-performancepoint-services.md @@ -0,0 +1,127 @@ +--- +title: Configure PerformancePoint Services +ms.prod: SHAREPOINT +ms.assetid: ae626fda-efc1-4b99-9909-829346b04b6f +--- + + +# Configure PerformancePoint Services + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-14* **Summary:** Configure PerformancePoint Services in SharePoint Server.This article describes how to create and configure a PerformancePoint Services service application.To properly configure PerformancePoint Services, do the following steps in the order listed: +1. [Install ADOMD.NET from the SQL Server 2012 Feature Pack](https://go.microsoft.com/fwlink/p/?LinkId=275448) + + +2. [Configure the PerformancePoint Services application pool account](#section1) + + +3. [Start the PerformancePoint service](#section2) (SharePoint Server 2013 only) + + +4. [Create a PerformancePoint Services service application](#section3) + + +5. [Configure service application associations](#section4) + + + +## Configure the PerformancePoint Services application pool account + + +The application pool for the PerformancePoint Services service application requires a SharePoint Server managed account (generally an Active Directory account) to run. This account must have access to the content databases where PerformancePoint data will be stored.If you run the service application using the same application pool account as the web application where the content databases are located, this required database access is configured automatically. However, we recommend that you use a different account for the PerformancePoint Services application pool, especially in a large or complex farm. This allows for greater control over data and resource access.If you choose to use the same managed account for PerformancePoint Services as is being used for the web application, you can skip the procedures in this section. If you choose to create a new managed account, you must do the following: +1. Register a managed account in SharePoint Server. (You will need an Active Directory user account for this step. Have your Active Directory administrator create it.) + + +2. Grant access for this account to the content databases that will contain PerformancePoint data. This process includes running a Microsoft PowerShell script from the SharePoint 2016 Management Shell. + + +The first step is to register a managed account. Use the following procedure to register the Active Directory account that you want to use for the PerformancePoint Services application pool. **To register a managed account** +1. In the SharePoint Server Central Administration Web site, click **Security**. + + +2. In the **General Security** section, click **Configure managed accounts**. + + +3. Click **Register Managed Account**. + + +4. In the **Service account credentials** section, type the user name and password for the Active Directory account that you want to register. + + +5. Optionally, if the account password is set to expire after a certain length of time, configure the automatic password change settings to have SharePoint Server change the password. + + +6. Click **OK**. + + +Once you have registered the managed account, you must grant that account access to the content databases where PerformancePoint data will be stored. Use the following procedure to grant database access to the account. Follow this procedure for each web application that contains a content database where PerformancePoint Services data will reside. **To grant content database access to an account** +1. Open the **SharePoint 2016 Management Shell** as administrator. + + +2. At the Microsoft PowerShell command prompt, type the following, pressing Enter after each line: + + ``` + +$w = Get-SPWebApplication -identity +$w.GrantAccessToProcessIdentity("") + ``` + +Once you have finished granting content database access to the managed account, the next step is to create a PerformancePoint Services service application. +## Start the PerformancePoint service (SharePoint Server 2013 only) + + +If you are using SharePoint Server 2013, you must start the PerformancePoint service on the application server where you want to run PerformancePoint Services. (In SharePoint Server 2016 this is handled automatically by MinRole.) You can start the service on multiple application servers for better performance, if you want, but the service must be started on at least one server. Use the following procedure to start the PerformancePoint service. **To start the PerformancePoint Service** +1. In Central Administration, in the **System Settings** section, click **Manage services on server**. + + +2. Note the server specified in the **Server** box. If you want to run the PerformancePoint service on a different server, click the current server, and then click **Change Server** and select the server that you want. + + +3. Click **Start** next to **PerformancePoint Service**. + + + +## Create a PerformancePoint Services service application + + +Use the following procedure to create the service application. **To create a PerformancePoint Services service application** +1. In Central Administration, in the **Application Management** section, click **Manage Service Applications**. + + +2. Click **New**, and then click **PerformancePoint Service Application**. + + +3. Type a name for the service application and select the **Add this service application's proxy to the farm's default proxy list** check box. + + +4. Select the **Create new application pool** option and type a name for the application pool. + + +5. Under the **Configurable** option, select the managed account to run the application pool. + + +6. Click **Create**. + + +7. Click **OK**. + + +When you configure the service application in SharePoint Server 2016, the PerformancePoint Service will autoprovision on all servers in the farm that are running under the Front-end role. +## Configure PerformancePoint service application associations + + +For PerformancePoint Services to function, the PerformancePoint Services service application proxy must be associated with the default web application. Use the following procedure to confirm that the association is configured between the web application and the PerformancePoint Services proxy. **To configure service application associations** +1. In Central Administration, click **Application Management**. + + +2. In the **Service Applications** section, click **Configure service application associations**. + + +3. Under the **Application Proxy Group** column, click **default**. + + +4. Ensure that the **PerformancePoint Services** box is selected. + + +5. Click **OK**. + + + diff --git a/SharePoint/configure-power-pivot-for-sharepoint-2013.md b/SharePoint/configure-power-pivot-for-sharepoint-2013.md new file mode 100644 index 0000000000..e0fbb9eb82 --- /dev/null +++ b/SharePoint/configure-power-pivot-for-sharepoint-2013.md @@ -0,0 +1,376 @@ +--- +title: Configure Power Pivot for SharePoint 2013 +ms.prod: SHAREPOINT +ms.assetid: 9cea4a3d-c196-4d9e-942d-2677a6c15c13 +--- + + +# Configure Power Pivot for SharePoint 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-06* **Summary:** Learn how to configure Power Pivot for SharePoint Server 2013. +> [!IMPORTANT:] + + + + + +In this scenario, we’ll take a look at how to set up Power Pivot for SharePoint 2013. This includes installing Power Pivot for SharePoint on the servers in your farm, configuring a Power Pivot service application, and running some tests to make sure everything is working properly. +## Before you begin + + +Before getting started, make sure you have: +- [Configured Excel Services](html/administer-excel-services-in-sharepoint-server-2013.md) in your SharePoint Server farm. + + +- [Configured a data model server](html/manage-excel-services-data-model-settings-sharepoint-server-2013.md) in Excel Services. You’ll need an instance of [Analysis Services 2012 SP1 configured in Power Pivot mode](https://msdn.microsoft.com/en-us/library/jj219067.aspx) in order to do this. + + +- [Configured Secure Store](html/configure-the-secure-store-service-in-sharepoint-server.md) in your SharePoint Server farm. + + +- Downloaded [Microsoft SQL Server 2012 SP1 PowerPivot for Microsoft SharePoint](https://www.microsoft.com/en-us/download/details.aspx?id=35577) (spPowerPivot.msi). (We’ll be installing this program using the procedures in this article.) + + +- Created an Active Directory account for the Power Pivot application pool. This is a domain user account and doesn’t require any special permissions. It should be a unique account created for this purpose. + + +- Created an Active Directory account for the Power Pivot unattended data refresh account. This is a domain user account and must have read permissions to the data sources that you plan to use for your Power Pivot reports. It should be a unique account created for this purpose. + + +You may notice that the Power Pivot configuration tool that we’ll be using has options for deploying Excel Services and Secure Store. However, the Power Pivot configuration tool is not able to configure these services using the recommended accounts, so we recommend that you configure these services manually using the links above. +## Video demonstration + + +This video shows the steps involved in setting up Power Pivot for SharePoint 2013, as described in this article. **Video: Configure Power Pivot for SharePoint 2013** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + +## Prepare the farm + + +In this section, we will prepare the farm for Power Pivot installation. This includes registering a managed account and configuring some Secure Store settings in Central Administration, as well as configuring some security settings in SQL Server. You’ll need to be a farm administrator and a SQL Server administrator to do these steps, as well as a **Shell Administrator** to do the PowerShell steps. **Register a domain account as a managed account in SharePoint Server 2013** + + + +The first step is to register the domain account that you want to use to run the Power Pivot application pool as a managed account in SharePoint Server 2013. This will make the account available for us to use when we create the Power Pivot service application later on. **To register a managed account** +1. In Central Administration, click **Security**. + + +2. Under **General Security**, click **Configure managed accounts**. + + +3. Click **Register Managed Account**. + + +4. Type the username and password of the account that you created to run the Power Pivot application pool. + + +5. If you want SharePoint Server 2013 to handle account password changes for you, select the **Enable password change** check box, and then fill in the details on when you want the password changed. + + +6. Click **OK**. + + + **Grant the managed account access to the content database** + + + +You must also grant access to the SharePoint content database for this account. Use the following procedure for each web application that will be associated with Power Pivot. **To grant content database access to the managed account** +1. Click **Start**, click **All Programs**, click **Microsoft SharePoint 2013 Products**, right-click **SharePoint 2013 Management Shell**, and then click **Run as Administrator**. + + +2. At the Microsoft PowerShell Command Prompt, type the following syntax (press ENTER after each line): + + ``` + +$w = Get-SPWebApplication -identity http:// +$w.GrantAccessToProcessIdentity("\\") + ``` + + +> [!IMPORTANT:] + + + + + + **Create a target application in Secure Store** + + + +The next step is to create a target application in Secure Store for the Power Pivot unattended data refresh account. This target application will be used to refresh the data in your Power Pivot reports. **To create a target application** +1. In Central Administration, under **Application Management**, click **Manage service applications**. + + +2. Click the Secure Store service application. + + +3. In the ribbon, click **New**. + + +4. In the **Target Application ID** box, type **PowerPivotUnattendedAccount**. + + > [!NOTE:] + +5. Type a display name and email address. + + +6. For **Target Application Type**, make sure **Individual** is selected, and then click **Next**. + + +7. Ensure **Field Type** is set to **Windows User Name** and **Windows Password**, and click **Next**. + + +8. Type a name or group for the **Target Application Administrators**, and then click **OK**. + + +9. Select the target application that you just created, and then in the **Credentials** section of the ribbon, click **Set**. + + +10. For **Credential Owner**, type the account that you created for the Power Pivot application pool (the one that you just configured as a managed account). + + +11. Type the user name and password of the credentials that have access to your data sources. + + +12. Click **OK**. + + + **Grant access to the SharePoint Server admin content database** + + + +In order for the Power Pivot Management Dashboard reports to work, the account that runs the Excel Services application pool must have read access to the SharePoint Server 2013 admin content database. You configure this in SQL Server. **To grant admin content database access** +1. Open SQL Server Management Studio and connect to the database engine. + + +2. Expand **Security** and double-click the account that is used for the Excel Services application pool. + + +3. On the **User Mapping** page, click the SharePoint Admin content database (usually named SharePoint_AdminContent_). + + +4. Select the **SPDataAccess** database role check box. + + +5. Click **OK**. + + +The basic farm setup is now complete, so the next thing to do is to install and configure Power Pivot for SharePoint. +## Configure Power Pivot for SharePoint + + +In this section, we’ll configure Power Pivot itself, including installing the Power Pivot software and configuring a service application. **Install Power Pivot on each server in the farm** + + + +The first step in configuring Power Pivot in a SharePoint Server 2013 farm is to install SQL Server 2012 SP1 PowerPivot for Microsoft SharePoint (sppowerpivot.msi) on each server in the farm.Use the following procedure to run sppowerpivot.msi on each server in your farm. **To install Power Pivot for SharePoint 2013** +1. Double-click sppowerpivot.msi. + + +2. Follow the wizard to install Power Pivot for SharePoint 2013. When you see the Feature Selection page, leave all of the items selected (this is the default), and then complete the wizard. + + + **Run the Power Pivot for SharePoint configuration tool** + + + +Once you have installed sppowerpivot.msi on each server in the farm, the next step is to run the PowerPivot for SharePoint 2013 Configuration tool. Run this program on the server that is running the SharePoint Central Administration website. **To run the Power Pivot for SharePoint 2013 Configuration tool** +1. Click **Start** > **All Programs** > **Microsoft SQL Server 2012** > **PowerPivot for SharePoint 2013 Configuration**. + + +2. Choose the **Configure or Repair Power Pivot for SharePoint** option, and then click **OK**. + + +3. In the Power Pivot Configuration Tool, in the left pane, select **Create PowerPivot Service** application. + + +4. On the **Parameters** tab, clear the **Include this action in the task list** check box. This will prevent the tool from creating a service application for Power Pivot. We will create the Power Pivot service application manually later. + + + + + +![Screen shot of the checkbox unchecked.](images/) + + + + + + + + + + + + + + This will also prevent further configuration steps from being completed, but we’ll come back and do those later as well. + + +5. Click **Run**. + + +6. Click **Yes** to confirm. + + +7. When the action completes, click **OK**, and then click **Exit**. + + +If you have additional servers in your farm, we’ll eventually run the Power Pivot for SharePoint 2013 Configuration tool on those as well, but first there are a few more steps to do. **Create a Power Pivot service application** + + + +We prevented the Power Pivot configuration tool from creating a Power Pivot service application, so that we could create one manually and use the application pool account that we created earlier. Now, we need to go back and create the service application. **To create a Power Pivot service application** +1. In Central Administration, under **Application Management**, **click Manage service applications**. + + +2. In the ribbon, click **New**, and then click **SQL Server Power Pivot Service Application**. + + +3. Type a name for the service application in the **Name** text box. + + +4. Type a name for the new application pool in the **Application pool name** text box. + + +5. From the **Configurable** dropdown list, choose the account that you registered as a managed account for the Power Pivot application pool. + + +6. Click **OK**. + + +The Power Pivot service application has now been created, though you may need to refresh the page to see it. **Configure the Power Pivot unattended data refresh account** + + + +The next step is to configure the Power Pivot unattended data refresh account. We do this in the Power Pivot service application settings by specifying the unattended data refresh account that we created in Secure Store. **To configure the unattended data refresh account** +1. In Central Administration, under **Application Management**, click **Manage service applications**. + + +2. Click the Power Pivot service application. + + +3. Under **Actions**, click **Configure service application settings**. + + +4. Under **Data Refresh** (about a third of the way down), type the target application ID of the target application that you created (PowerPivotUnattendedAccount) in the **PowerPivot Unattended Data Refresh Account** box. + + +5. Click **OK**. + + + **Rerun the Power Pivot for SharePoint 2013 Configuration tool** + + + +Now that the service application has been created and we’ve configured the unattended data refresh account, we need to run the Power Pivot for SharePoint 2013 Configuration tool once again to complete the remainder of the steps. **To run the Power Pivot for SharePoint 2013 Configuration tool** +1. Click **Start** > **All Programs** > **Microsoft SQL Server 2012** > **Power Pivot for SharePoint 2013 Configuration**. + + +2. Choose the **Configure or Repair Power Pivot for SharePoint** option, and then click **OK**. + + +3. In the Power Pivot Configuration Tool, in the left pane, select **Activate Power Pivot Feature in a Site Collection**. + + +4. On the **Parameters** tab, choose the site collection where you want to active Power Pivot from the **Site URL** dropdown list. + + > [!NOTE:] + +5. If you changed the default site collection setting, click **Validate**. + + +6. Click **Run**, and then click **Yes** to confirm. + + +7. When the action completes, click **OK**, and then click **Exit**. + + +Power Pivot setup is now complete and Power Pivot is ready to use. **Run the Power Pivot for SharePoint Configuration tool on other servers in the farm** + + + +Because we’ve only run the Power Pivot for SharePoint 2013 Configuration tool on one server, the SQL Server Power Pivot System Service will only be available to run on this server. It’s fine to use Power Pivot this way, but if you have multiple servers in your farm, we recommend that you install the service on all of them. This will allow you to change which server you run the service on (for example, if you want to balance out the services on your farm) or to run the service on multiple servers for greater capacity.You install the SQL Server Power Pivot System Service by running the Power Pivot for SharePoint 2013 Configuration tool on the other servers in your farm.Use the following procedure on each server in your farm. **To run the Power Pivot for SharePoint 2013 Configuration tool** +1. Click **Start** > **All Programs** > **Microsoft SQL Server 2012** > **PowerPivot for SharePoint 2013 Configuration**. + + +2. Choose the **Configure or Repair Power Pivot for SharePoint** option, and then click **OK**. + + +3. If you see **Activate PowerPivot Feature in a Site Collection** in the left pane, click on it, and then select the site collection where you want to activate Power Pivot or uncheck the **Include this action in the task list** check box if you don’t want to activate Power Pivot in another site collection. + + +4. If you made any changes, click **Validate**. + + +5. Click **Run**, and then click **Yes** to confirm. + + +6. When the tasks complete, click **OK**, and then click **Exit**. + + +When you run the Power Pivot for SharePoint 2013 Configuration tool, it installs and turns on the SQL Server Power Pivot System Service on each server where you run it. You probably don’t want this service running on every server, so be sure to go to **Manage services on server** in Central Administration and stop the service on the servers where you don’t want to run it. +## Test the Power Pivot for SharePoint installation + + +Now that everything is configured, we can do a simple test to see if it’s working. We’ll build a data model in Excel and publish it to a document library in the site collection where we enabled Power Pivot. **To create a test workbook** +1. In Excel, on the **Data** tab, choose **From Other Sources**, then choose **From SQL Server**. + + +2. Type the name of the instance of SQL Server where your data resides. + + +3. Follow the wizard through to connect to the table that contains your data. + + +4. When the wizard completes, you should see the **Import Data** dialog box. Choose the **Only Create Connection** option and select the **Add this data to the Data Model** check box. + + +5. Click **OK**. + + +6. On the **Power Pivot** tab, click **Manage**. + + +7. In the **Power Pivot** ribbon, click **PivotTable**. + + +8. On the **Insert Pivot** dialog box, choose the **Existing Worksheet** option, and then click **OK**. + + +9. Select the fields that you want in the PivotTable report. + + +10. Save the workbook to a document library on the site collection where you enabled Power Pivot. + + +Once you’ve saved the workbook to the document library, you can access the Power Pivot settings by clicking the ellipsis (...) control twice, and then choosing **Manage Power Pivot Data Refresh**. + + + +![Screenshot of controls in document library.](images/) + + + +On the Manage Data Refresh page, select the **Enable** and **Also refresh as soon as possible** check boxes. Also, ensure that the **Use the data refresh account configured by the administrator** option is selected. (This is the default.) + + + +![Screenshot of Power Pivot data refresh settings.](images/) + + + +Repeat this several times while making some changes to your data. If the changes show up in the report when it’s rendered in the browser, then data refresh is working properly. diff --git a/SharePoint/configure-profile-synchronization-by-using-sharepoint-active-directory-import-in.md b/SharePoint/configure-profile-synchronization-by-using-sharepoint-active-directory-import-in.md new file mode 100644 index 0000000000..64b09fe323 --- /dev/null +++ b/SharePoint/configure-profile-synchronization-by-using-sharepoint-active-directory-import-in.md @@ -0,0 +1,233 @@ +--- +title: Configure profile synchronization by using SharePoint Active Directory Import in SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 73ceb46e-d3aa-45bd-ac3e-77f58a9ab34d +--- + + +# Configure profile synchronization by using SharePoint Active Directory Import in SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-08-01* **Summary:** Learn how to import user profiles from Active Directory to SharePoint Server 2016 by using the Active Directory import tool for SharePoint Server 2016 user profiles.You can use the SharePoint Active Directory import option (AD import) as an alternative to using Microsoft Identity Manager (MIM) to import user profile data from Active Directory Domain Services (AD DS) in your domain.Import operations that use AD import are significantly faster than the same operations that use MIM. However, AD import only works with Active Directory Domain Services (AD DS) and does not work with other directory services. Additionally, if you choose to use AD Import, MIM or other external identity managers are not available for connections to other data sources such as business applications.You must be a member of the Farm Administrators group to perform the procedures in this article. You also need domain credentials with synchronization permissions in order to configure the connection. +## Situations unsupported by AD import + +Consider the following situations and note what the AD import option does not support when you determine whether to use this option: +- The AD import option does not perform bidirectional synchronization. That means changes made to SharePoint user profiles will not be synchronized back to the domain controller. + + +- Referential integrity among users and groups is only maintained within a single Active Directory forest. + + +- The AD import option lets you configure and use only a single, farm-wide property mapping. + + +- The AD import option does not automatically synchronize photos from Active Directory to SharePoint Server 2016. + + +- The AD import option does not support generic (non-AD) LDAP sources. + + +- The AD import option does not support Source Schema Discovery. + + +- The AD import option does not support multi-Forest scenarios such as: + + - If you have a trust between two forests, the trusted forest objects will not be imported. + + + - If you need to import users from multiple domains, you must create multiple synchronization connections. If you have multiple domains to manage, using MIM. + + +- The AD import option does not support Contact objects (also known as cross-object pointers). + + +- The AD import option does not support custom object classes besides User and Group. + + +- The AD import option does not filter user interface to create complex Boolean expressions. + + +- The AD import option does not provide object filtering based on object property values (you must use simple LDAP filters). + + +- The AD import option does not provide Logon and Resource Forest support. That is, custom joins of data from multiple sources. + + +- The AD import option does not support Business Connectivity Services Import. + + +- The AD import option does not support property mappings for complex types like pictures and special AD types. + + +- The AD import option does not support exporting data from SharePoint to Directory Sources. + + +- The AD import option does not support Upgrading/Translating FIM based connections or synchronizing configuration to AD import (or in reverse order). + + +- The AD import option does not ensure single-master of each object property (currently, the last writer wins). + + +- The AD import option does not perform per-tenant property mapping. + + + +## Set up SharePoint Active Directory Import + + +You perform three procedures in Central Administration to configure AD import.In the first procedure, you configure SharePoint Server 2016 to use AD Import instead of an external identity manager such as MIM.In the second procedure, you create a synchronization connection to AD DS. The connection identifies the items to synchronize and contains the credentials that are used to interact with AD DS. In the third procedure, you determine how the properties of user profiles in SharePoint Server 2016 map to the user information that is retrieved from AD DS. **To configure SharePoint Server to use AD Import** +1. On the SharePoint Central Administration website, in the **Application Management** section, click **Manage service applications**. + + +2. On the **Manage Service Applications** page, click the link of the User Profile service application. + + +3. On the **Manage Profile Service** page, in the **Synchronization** section, click **Configure Synchronization Settings**. + + +4. On the **Configure Synchronization Settings** page, in the **Synchronization Options** section, select the **Use SharePoint Active Directory Import** option, and then click **OK**. + + +To import profiles, you must have at least one synchronization connection to AD DS. You may have connections to multiple AD DS servers. Using the following procedure, create a synchronization connection to each AD DS server from which you want to import profiles. You can synchronize after you create each connection, or you can synchronize one time, after you have created all of the connections. Although synchronizing after each connection takes longer, doing this makes it easier to troubleshoot any problems that you might encounter. **To create a connection to a directory service for import** +1. On the SharePoint Central Administration website, in the **Application Management** section, click **Manage service applications**. + + +2. On the **Manage Service Applications** page, click the link of the User Profile service application. + + +3. On the **Manage Profile Service** page, in the **Synchronization** section, click **Configure Synchronization Connections**. + + +4. On the **Synchronizations Connections** page, click **Create New Connection**. + + +5. On the **Add new synchronization connection** page, type the synchronization connection name in the **Connection Name** box. + + +6. From the **Type** list, select **Active Directory Import**. + + +7. Fill in the **Connection Settings** section by completing the following steps: + +1. In the **Fully Qualified Domain Name** box, type the fully-qualified domain name of the domain. + + +2. In the **Authentication Provider Type** box, select the type of authentication provider. + + +3. If you select **Forms Authentication** or **Trusted Claims Provider Authentication**, select an authentication provider from the **Authentication Provider Instance** box. + + The **Authentication Provider Instance** box lists only the authentication providers that are currently used by a web application. + + +4. In the **Account name** box, type the name of the account you want the AD import tool to use to perform the synchronization. Use the form ** \\ ** . The synchronization account must have Replicate Directory permissions or higher on the root OU of AD DS. + + +5. In the **Password** and **Confirm password** boxes, type the password for the account. + + +6. In the **Port** box, type the connection port you want the AD import tool to use to connect to AD DS when it performs the synchronization. + + +7. If a Secure Sockets Layer (SSL) connection is required to connect to the directory service, select **Use SSL-secured connection**. + + > [!IMPORTANT:] + +8. If you want to filter out users that are disabled in AD DS, select the **Filter out disabled users** check box. + + +9. If you want to filter the objects that you import from the directory service, in the **Filter in LDAP syntax for Active Directory Import** box, type a standard LDAP query expression to define the filter. + + +8. In the **Containers** section, click **Populate Containers**, and then select the containers from the directory service that you want to synchronize. All organizational units (OUs) that you select will be synchronized with their child OUs. There is currently no utility that allows you to select a parent OU while excluding any of its child OUs from synchronization. + + +9. Click **OK**. + + The newly created connection is listed on the **Synchronization Connections** page. + + > [!TIP:] + + **To map user profile properties** +1. On the SharePoint Central Administration website, in the **Application Management** section, click **Manage service applications**. + + +2. On the **Manage Service Applications** page, click link for the User Profile service application. + + +3. On the **Manage Profile Service** page, in the **People** section, click **Manage User Properties**. + + +4. On the **Manage User Properties** page, click the name of the property that you want to map to a directory service attribute, and then click **Edit**. + + +5. To remove an existing mapping, in the **Property Mapping for Synchronization** section, select the mapping that you want to remove, and then click **Remove**. + + +6. To add a new mapping, do the following: + +1. In the **Add New Mapping** section, in the **Source Data Connection** list, select the data connection that represents the directory service to which you want to map the user profile property. + + +2. In the **Attribute** box, type the name of the directory service attribute to which you want to map the property. + + +3. Click **Add**. + + > [!NOTE:] + +7. Click **OK**. + + +8. Repeat steps 4 through 7 to map additional properties. + + + **To start profile synchronization** +1. On the SharePoint Central Administration website, in the **Application Management** section, click **Manage service applications**. + + +2. On the **Manage Service Applications** page, click the link for the User Profile service application. + + +3. On the **Manage Profile Service** page, in the **Synchronization** section, click **Start Profile Synchronization**. + + +4. On the **Start Profile Synchronization** page, select **Start Full Synchronization** if this is the first time that you are synchronizing or if you have added or modified any synchronization connections since the last time that you synchronized. Select **Start Incremental Synchronization** to synchronize only information that has changed since the last time that you synchronized. + + +5. Click **OK**. + + The **Manage Profile Service** page is displayed, showing the profile synchronization status in the right pane. + + + +# See also + +#### + + [Manage user profile synchronization in SharePoint Server](html/manage-user-profile-synchronization-in-sharepoint-server.md) + + + + [Plan profile synchronization for SharePoint Server 2013](html/plan-profile-synchronization-for-sharepoint-server-2013.md) + + + + [Synchronize user and group profiles in SharePoint Server 2013](html/synchronize-user-and-group-profiles-in-sharepoint-server-2013.md) + + + + [Schedule profile synchronization in SharePoint Server](html/schedule-profile-synchronization-in-sharepoint-server.md) + + + + +#### + + **Update-SPProfilePhotoStore** + + + + + + + + diff --git a/SharePoint/configure-properties-of-the-refinement-web-part-in-sharepoint-server.md b/SharePoint/configure-properties-of-the-refinement-web-part-in-sharepoint-server.md new file mode 100644 index 0000000000..8bde39cb8d --- /dev/null +++ b/SharePoint/configure-properties-of-the-refinement-web-part-in-sharepoint-server.md @@ -0,0 +1,147 @@ +--- +title: Configure properties of the Refinement Web Part in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 9f039270-d426-4e79-b608-8db792de74ed +--- + + +# Configure properties of the Refinement Web Part in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-18* **Summary:** Learn how to configure properties of the Refinement Web Part, how to display refiner counts, and how to change the refiner display name.By default, the Refinement Web Part is used on all search vertical pages (results.aspx, peopleresults.aspx, conversationresults.aspx, videoresults.aspx). The Web Part filters search results from a Search Results Web Part into categories to help users narrow search results to help them find what they are looking for. By changing properties in the Refinement Web Part you can you can do the following: +- Specify a different Search Results Web Part from which to filter search results. + + +- Specify which refiners to show in the Web Part. + + +- Change the display template that is applied to each refiner. + + +Before you begin these procedures, verify the following: +- The managed properties that you want to use as refiners are set to refinable and queryable in the search schema. You can verify or change this by viewing or editing the **Main characteristics** of the managed property as described in [To add a managed property](manage-the-search-schema-in-sharepoint-server.md#proc2). + + +- You have done a full crawl of the content source that contains the managed properties that are enabled as refiners as described in [Start, pause, resume, or stop a crawl in SharePoint Server](html/start-pause-resume-or-stop-a-crawl-in-sharepoint-server.md). + + +In this article: +- [Before you begin](#begin) + + +- [Configure properties of the Refinement Web Part](#BKMK_Configure) + + +- [Change the refiner display name](#BKMK_DisplayName) + + +- [Add refiner counts to the Refinement Web Part](#BKMK_AddRefinerCounts) + + + +## Before you begin + + + +> [!NOTE:] +> [Plan browser support](https://go.microsoft.com/fwlink/p/?LinkId=246502)> **Accessibility for SharePoint 2013**> [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)> [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504)> [Touch](https://go.microsoft.com/fwlink/p/?LinkId=246506) + + + + + +## Configure properties of the Refinement Web Part + + + **To configure the properties of a Refinement Web Part** +1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the Enterprise Search Center site. + + +2. Browse to the page that contains the Refinement Web Part that you want to configure. + + +3. Click the **Settings** menu, and then click **Edit Page**. + + +4. In the Web Part, click the **Refinement Web Part Menu** arrow, and then click **Edit Web Part**. + + +5. In the Web Part tool pane, in the **Refinement Target** section, select the Web Part from which from which to filter search results. By default, the Search Results Web Part is selected. + + +6. In the Web Part tool pane, verify that the **Choose Refiners in this Web Part** is selected. + + +7. Click **Choose Refiners**. + + +8. On the **Refinement configuration** page, from the **Available refiners** section, use the buttons to select which refiners should be shown in the Web Part, and also in what order that they should be shown. If you have specified an **Alias** for a refinable managed property, this alias is shown in the **Configuration for** section. + + +9. In the **Configuration for** section, configure how you want each refiner to appear. + + > [!NOTE:] + + +## Change the refiner display name + + +By default, the name of the managed property that is enabled as a refiner will be used as display name for the refiner. In many cases, the managed property name is not user-friendly — for example, RefinableString00 or ColorOWSTEXT. You can change the display name of the refiner by changing a java script file in the master page gallery. **To change the refiner display name** +1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the Enterprise Search Center site. + + +2. On the **Settings** menu, click **Site Settings**. + + +3. On the **Site Settings** page, in the **Web Designer Galleries** section, click **Master pages and page layouts**. + + +4. On the **Master Page Gallery** page, click **Display Templates**. + + +5. On the **Display Templates** page, click **Language Files**. + + +6. On the **Language Files** page, click the folder that contains the language for which you want to change the refiner display name. + + +7. Open the **CustomStrings.js** file. + + +8. Add one line to the file for each managed property that is enabled as a refiner for which you want to change the display name by using the following syntax: + + "rf_RefinementTitle_ManagedPropertyName": "Sample Refinement Title for ManagedPropertyName" + + For example, you can add the following line to change the display name for the managed property RefinableInt00 to Price: + + "rf_RefinementTitle_RefinableInt00": "Price". + + + +## Add refiner counts to the Refinement Web Part + + +By default, the Refiner Web Part will not show refiner counts — that is, the number of items for each refiner value. For example, if you have enabled the managed property Color as a refiner, the refiner values will only show colors such as Red, Green, and Blue. You can add refiner counts by changing a value in an HTML file so that the refiner values are shown as Red (10), Green (12), and Blue (8). **To add refiner counts to the Refinement Web Part** +1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the Enterprise Search Center site. + + +2. On the **Settings** menu, click **Site Settings**. + + +3. On the **Site Settings** page, in the **Web Designer Galleries** section, click **Master pages and page layouts**. + + +4. On the **Master Page Gallery** page, click **Display Templates**. + + +5. On the **Display Templates** page, click **Filters**. + + +6. Open the **Filter_Default.html** file. + + +7. Change the value for **ShowCounts** to **true**. + + +8. Save the file. + + + diff --git a/SharePoint/configure-properties-of-the-search-box-web-part-in-sharepoint-server.md b/SharePoint/configure-properties-of-the-search-box-web-part-in-sharepoint-server.md new file mode 100644 index 0000000000..8dc884d3bd --- /dev/null +++ b/SharePoint/configure-properties-of-the-search-box-web-part-in-sharepoint-server.md @@ -0,0 +1,111 @@ +--- +title: Configure properties of the Search Box Web Part in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 766e0169-1a5d-4730-9c9f-7e2b27ba7d5d +--- + + +# Configure properties of the Search Box Web Part in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-18* **Summary:** Learn how to configure properties of the Search Box Web Part.By default, the Search Box Web Part is used on the home page for the Search Center (default.aspx), and all search results pages (results.aspx, peopleresults.aspx, conversationresults.aspx, videoresults.aspx). By changing properties in the Search Box Web Part you can you can do the following: +- Change the Web Part or page where the search results should be displayed — for example, a custom Search Results Web Part or a custom search results page. + + +- Turn off query suggestions and people suggestions. For more information about query suggestions, see [Manage query suggestions in SharePoint Server](html/manage-query-suggestions-in-sharepoint-server.md) + + +- Display links to a search preference page and an advanced search page. + + +- Change the display template that is applied to the Web Part. + + + +## Before you begin + + + +> [!NOTE:] +> [Plan browser support](https://go.microsoft.com/fwlink/p/?LinkId=246502)> **Accessibility for SharePoint 2013**> [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)> [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504)> [Touch](https://go.microsoft.com/fwlink/p/?LinkId=246506) + + + + + +## Configure properties of the Search Box Web Part + + + **To configure the properties of a Search Box Web Part** +1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the Enterprise Search Center site. + + +2. On the Search Center site home page, click the **Settings** menu, and then click **Edit Page**. + + +3. In the Web Part, click the **Search Box Web Part Menu** arrow, and then click **Edit Web Part**. + + +4. In the Web Part tool pane, in the **Properties for Search Box** section, expand the **Which search results page should queries be sent to** section, and then do the following: + + - To display the settings that are defined on the Search Settings page, select the **Use this site's Search Settings** check box. + + + - To override the settings that are defined on the Search Settings page, clear the **Use this site's Search Settings** check box, and then do the following: + + - To display search results in a Web Part on the page, in the section **Send queries to other Web Parts on this page**, select a Web Part. + + > [!NOTE:] + + - To send queries to a custom search results page, select **Send queries to a custom results page URL**, and then type the URL of the custom search results page. + + > [!NOTE:] + +5. In the Web Part tool pane, in the **Properties for Search Box** section, expand the **Query Suggestions** section, and then do the following: + + - To disable query suggestions, clear the **Show suggestions** check box. + + + - To specify additional properties for query suggestions, change the values in the following fields: + + - **Number of query suggestions:** How many query suggestions to display. + + + - **Minimum number of characters:** How many characters the user must type before query suggestions are displayed. + + + - **Suggestions delay (in milliseconds):** How many milliseconds elapse before query suggestions are displayed. + + + - **Number of personal favorites:** How many query suggestions are displayed to the user under the text **Are you looking for these again?** in the search results. These suggestions are based on search results that the user has clicked previously. To disable personal favorite results, clear the **Show personal favorite results** check box. + + + - To turn on people name suggestions, select **Show people name suggestions**. + + +6. In the Web Part tool pane, in the **Properties for Search Box** section, expand the **Settings** section, and then do the following: + + - To show a link to a search preference page, select **Show preferences link**. + + + - To show a link to an advanced search page, select **Show advanced link**, and then in the **Advanced search page URL** box, type the URL of the advanced search page that you want to link to. + + + - To apply another display template, in the **Search box control Display Template** list, select the display template that you want to apply to the Web Part. + + + - Select the **Make the search box have focus when the page is loaded** check box to make it possible for users to immediately type a query in the search box when the page is loaded without first having to click the search box. By default, this is selected. + + + +# See also + +#### + + [How to change the text that is displayed in the Search Box Web Part in SharePoint Server 2013](https://blogs.technet.com/b/tothesharepoint/archive/2013/09/19/how-to-change-the-text-that-is-displayed-in-the-search-box-web-part-in-sharepoint-server-2013.aspx) + + + + + + + + diff --git a/SharePoint/configure-properties-of-the-search-navigation-web-part-in-sharepoint-server.md b/SharePoint/configure-properties-of-the-search-navigation-web-part-in-sharepoint-server.md new file mode 100644 index 0000000000..9b4a3d04bb --- /dev/null +++ b/SharePoint/configure-properties-of-the-search-navigation-web-part-in-sharepoint-server.md @@ -0,0 +1,119 @@ +--- +title: Configure properties of the Search Navigation Web Part in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 79428586-0a1c-4fd8-ae49-e1e76eb022e1 +--- + + +# Configure properties of the Search Navigation Web Part in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-18* **Summary:** Learn how to configure properties of the Search Navigation Web Part, and how to add a link to a new search vertical page.The Search Navigation Web Part is configured to display links to the search verticals **Everything**, **People**, **Conversations** and **Videos**. It uses search results from the Search Results Web Part so that when users click a search vertical link, the search results are filtered and displayed following the configuration of the search vertical. You can also create your own search vertical and add it to be displayed in the Search Navigation Web Part.By changing properties on the Search Navigation Web Part you can do the following: +- Specify a different Web Part from which search results are received. + + +- Change the number of search vertical links to display. + + +The search vertical properties, such as display name and links, are configured on the Search Settings page for the corresponding site.In this article: +- [Before you begin](#begin) + + +- [Configure the properties of the Search Navigation Web Part](#BKMK_ConfigureSearchNavigation) + + +- [Change the properties of a search vertical in the Search Navigation Web Part](#BKMK_ChangeProperties) + + +- [Add a search vertical to the Search Navigation Web Part](#BKMK_AddSearchVertial) + + + +## Before you begin + + + +> [!NOTE:] +> [Plan browser support](https://go.microsoft.com/fwlink/p/?LinkId=246502)> **Accessibility for SharePoint 2013**> [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)> [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504)> [Touch](https://go.microsoft.com/fwlink/p/?LinkId=246506) + + + + + +## Configure the properties of the Search Navigation Web Part + + + **To configure the properties of a Search Navigation Web Part** +1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the Enterprise Search Center site. + + +2. On the search results page, click the **Settings** menu, and then click **Edit Page**. + + +3. In the Search Navigation Web Part, click the **Search Navigation Web Part** menu arrow, and then click **Edit Web Part**. + + +4. In the Web Part tool pane, in the **Control** section, do the following: + + - To receive search results from another Web Part on the page, in the **Use Current Query from** list, select a Web Part. + + + - To change the number of search vertical links to display before overflowing, in the **Maximum Links Before Overflow** box, type a number. + + + +## Change the properties of a search vertical in the Search Navigation Web Part + + + **To change the properties of a search vertical in the Search Navigation Web Part** +1. Verify that the user account that performs this procedure is a member of the Owners group on the Enterprise Search Center site. + + +2. On the **Settings** menu for the site, click **Site Settings**. + + +3. On the **Site Settings** page, in the **Search** section, click **Search Settings**. + + +4. On the **Search Settings** page, in the **Configure Search Navigation** section, click to select the search vertical for which you want to change the properties, and then click **Edit**. + + +5. In the **Navigation Link** dialog box, do the following: + + - To change the display name of a search vertical, in the **Title** field, type a display name. + + + - To change the URL of the search vertical, in the **URL** field, type a URL. + + > [!NOTE:] + +6. On the **Search Settings** page, click **OK** to save the changes. + + + +## Add a search vertical to the Search Navigation Web Part + + +Before you start this procedure, verify that you have created a new page for the search vertical. We recommend that you copy one of the existing search vertical pages — for example, **results.aspx**, and then modify the copy to create a new page. **To add a search vertical to the Search Navigation Web Part** +1. Verify that the user account that performs this procedure is a member of the Owners group on the Enterprise Search Center site. + + +2. On the **Settings** menu for the site, click **Site Settings**. + + +3. On the **Site Settings** page, in the **Search** section, click **Search Settings**. + + +4. On the **Search Settings** page, in the **Configure Search Navigation** section, click **Add Link**. + + +5. In the **Navigation Link** dialog box, do the following: + + - In the **Title** field, type a display name. + + + - In the **URL** field, type the URL to the new search vertical. + + + - Click **OK** to save the new search vertical. + + + diff --git a/SharePoint/configure-properties-of-the-search-results-web-part-in-sharepoint-server.md b/SharePoint/configure-properties-of-the-search-results-web-part-in-sharepoint-server.md new file mode 100644 index 0000000000..fd6eb16590 --- /dev/null +++ b/SharePoint/configure-properties-of-the-search-results-web-part-in-sharepoint-server.md @@ -0,0 +1,266 @@ +--- +title: Configure properties of the Search Results Web Part in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: d0e68cf4-80f6-4f1f-af49-a3b9c43408ac +--- + + +# Configure properties of the Search Results Web Part in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-18* **Summary:** Learn how to configure the query and properties of the Search Results Web Part, and how to disable stemming in the Web Part.The Search Results Web Part displays the search results of a query entered in a Search Box Web Part. By default, the Search Results Web Part is used on all search vertical pages (results.aspx, peopleresults.aspx, conversationresults.aspx, videoresults.aspx). The Search Results Web Part displays the actual search results and it also passes the search results to the Refinement Web Part and the Search Navigation Web Part on the same page.The Search Results Web Part uses a query that is specified in the Web Part to display search results. By default, the query defined in this Web Part uses the query variable {searchboxquery}. The query variable is a placeholder for a value. When a query is run, the placeholder is replaced with a value. For example, when a user types the search phrase *yellow* in the Search Box Web Part, the {searchboxquery} variable in the Search Results Web Part will resolve to search all items that contain the phrase *yellow* .By changing the properties and query in the Search Results Web Part you can you can do the following: +- Limit search results to a result source. + + +- Add query variables or property filters that customize search results for different users. + + +- Promote or demote items or pages within the search results. + + +- Change the sorting of the search results. + + +- Change the display template. + + +In this article: +- [Before you begin](#begin) + + +- [Configure properties of the Search Results Web Part](#BKMK_ConfigureProperties) + + +- [To disable stemming in a Search Results Web Part](#BKMK_DisableStemming) + + + +## Before you begin + + + +> [!NOTE:] +> [Plan browser support](https://go.microsoft.com/fwlink/p/?LinkId=246502)> **Accessibility for SharePoint 2013**> [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)> [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504)> [Touch](https://go.microsoft.com/fwlink/p/?LinkId=246506) + + + + + +## Configure properties of the Search Results Web Part + + + **To configure the properties of a Search Results Web Part** +1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the Enterprise Search Center site. + + +2. On the search results page, click the **Settings** menu, and then click **Edit Page**. + + +3. In the Search Results Web Part, click the **Search Results Web Part Menu** arrow, and then click **Edit Web Part**. + + +4. In the Web Part tool pane, in the **Search Criteria** section, click **Change query**. + + +5. On the **BASICS** tab, do one of the following: + + - To define your query by using Keyword Query Language (KQL), select options as described in the following table: + +### Advanced Mode (default) + + **Select a query**
Select a result source to specify which content should be searched.
By default, the following result sources are set for the different search vertical pages:
Everything (results.aspx): **Local SharePoint Results (System)**
People (peopleresults.aspx): **Local People Results (System)**
Conversations (conversationresults.aspx): **Conversations (System)**
Videos (videoresults.aspx): **Local Video Results (System)**
**Keyword filter**
You can use keyword filters to add query variables to your query. For a list of available query variables,see [Query variables in SharePoint Server](html/query-variables-in-sharepoint-server.md).
You can select pre-defined query variables from the drop-down list, and then add them to the query by clicking **Add keyword filter**.
**Property filter**
You can use property filters to query the content of managed properties that are set to *queryable* in the search schema.
You can select managed properties from the **Property filter** drop-down list. Click **Add property filter** to add the filter to the query.
**Query text**
By default, the query variable {searchboxquery} is defined for this field. You can change the query text by using KQL. For more information about KQL, see [Keyword Query Language (KQL) syntax reference](https://msdn.microsoft.com/en-us/library/ee558911%28v=office.15%29.aspx). Alternatively you can use the **Keyword filter** and **Property filter** lists to build the query.
The keyword query can consist of free-text keywords, property filters, or operators. Use braces to enclose query variables. The query variables will be replaced with an actual value when the query is run.
Keyword queries have a maximum length of 2,048 characters.
- To define your query by using pre-defined variables, click **Switch to Quick Mode**. Select options as described in the following table: + +### Quick Mode + + **Select a query**
Select a result source to specify which content should be searched. If you have shared a document library or list as catalog, the catalog result source will be displayed in this drop-down list.
**Restrict by app**
Select an option from the list to restrict results to a specific site, library, list, or URL.
**Restrict by tag**
You can limit results to content that is tagged with a term from a term set.
Select one of the following options:
+### + + **Don’t restrict by any tag**
Search results will not be limited based on tags (default).
**Restrict by navigation term of current page**
Search results will be limited to content that is tagged with the term of the current page. The current tag is displayed as the last part of the friendly URL. This option is only meaningful for sites that use managed navigation.
**Restrict by current and child navigation**
Search results will be limited to content that is tagged with the term of the current page (displayed as the last part of the friendly URL), and content that is tagged with sub-terms of the current page. This option is only meaningful for sites that use managed navigation.
**Restrict on this tag**
Search results will be limited to content that is tagged with the tag that you type inside the box.
+ > [!NOTE:] + +6. The **REFINERS** tab lists the managed properties that are enabled as refiners in the search schema. You can specify that the search results returned in the Search Results Web Part should be limited to one or more values from the refiners. Select a refiner in the list, and then click **Add** to add it to the query. + + Click **Show more** if you want to define grouping of results. Under **Group results**, you can specify that the results should be grouped based on one or more managed properties. This is useful when you are displaying several variants for a given item, and want to group them under a single result. + + +7. On the **SORTING** tab, you can specify how search results should be sorted. This tab is available only if you use **Advanced Mode**. If you use **Quick Mode**, you can define sorting options in the result source. + + In the **Sort by** drop-down list: + +1. Select a managed property from the list of managed properties that are set as sortable in the search schema, and then select **Descending** or **Ascending**. To add more sorting levels, click **Add sort level**. + + > [!NOTE:] + + + > [!IMPORTANT:] + +2. Select **Rank** to sort by relevance rank. You can then specify which ranking model to use or specify dynamic ordering rules. + + - (Optional) Select which ranking model to use for sorting in the **Ranking Model** list. + + + - Under **Dynamic ordering**, you can specify additional ranking by adding rules that will change the order of results when certain conditions apply. Click **Add dynamic ordering rule**, and then specify conditional rules. + + +8. On the **SETTINGS** tab, specify the settings that are listed in the following table. + +### + + **Query Rules**
Select whether to use Query Rules or not.
**URL Rewriting**
Select if the URL rewrite to the item details page should continue to be relative for each catalog item as defined when you set up the catalog connection. This option is only meaningful for sites that use managed navigation and have connected to a catalog that uses anonymous access for the catalog pages. If you select **Don’t rewrite URLs**, the URLs for catalog items are pointed directly to the library item of the connected catalog.
**Loading Behavior**
Select when the search results returned by the Search Results Web Part appear on the web page. The default option is **Async option: Issue query from the browser**. Queries will be issued from the end-users browser after the complete page is received. This option may be considered for secondary content on a page — for example, Recommendations or Popular Items. If you select **Sync option: Issue query from the server**, queries are issued from the server, and the search results are included in the page response that is sent back from SharePoint Server.
9. On the **TEST** tab, you can preview the query that is sent by the Search Results Web Part. + +### + + **Query text**
Shows the final query that will be run by the Search Results Web Part. It is based on the original query template where dynamic variables are substituted with current values. Other changes to the query may be made as part of a query rule.
+ Click **Show more** to display additional information. + +### + + **Query template**
Shows the content of the query template that is applied to the query.
**Refined by**
Shows the refiners applied to the query as defined on the **REFINERS** tab.
**Grouped by**
Shows the managed property on which search results should be grouped as defined on the **REFINERS** tab.
**Applied query rules**
Shows which query rules are applied to the query.
+ The **Query template variables** section shows the query variables that will be applied to the query, and the values of the variables that apply to the current page. You can type other values to test the effect they will have on the query. Click the **Test Query** button to preview the search results. + + You can also test how the query works for different user segment terms. Click **Add user segment term** to add terms to be added to the query. + + Click the **Test query** button to preview the search results. + +### + +Query text
Shows the final query that will be run by the Search Results Web Part. It is based on the original query template where dynamic variables are substituted with current values. Other changes to the query may be made as part of a query rule.
10. In the Web Part tool pane, in the **Display Templates** section, the default selection is **Use result types to display items**. This selection will apply different display templates according to the result type of the search result. For example, if the result type of a search result is a PDF file, the display template **PDF Item** will be applied. If the result type of a search result is an image, the **Picture Item** display template will be applied. To apply one display template to all result types of the search results, select **Use a single template to display items**, and then select the display template that you want to apply. + + +11. In the Web Part tool pane, in the **Settings** section, in the **Results Settings**, to further specify how search results should be shown, change the values in the following fields: + + - **Number of results per page** The number of search results to be displayed per page. + + + - **Show ranked results** Clear the check box if you want to show only promoted blocks (such as promoted results or personal favorites) or result controls (such as result counts) instead of the ranked results. + + + - **Show promoted results** Clear the check box if you do not want to show search results that you have promoted by using Query rules. + + + - **Show "Did you mean?"** Clear the check box if you do not want to show query spelling corrections as **Did you mean** suggestions. For more information about query spelling corrections, see [Manage query spelling correction in SharePoint Server](html/manage-query-spelling-correction-in-sharepoint-server.md). + + + - **Show personal favorites** Clear the check box if you do not want to show personal favorites. + + + - **Show View Duplicates link** Select the check box if you want to show a **View Duplicates** link. + + + - **Show link to search center** Select the check box if you want to show a link to the Search Center. + + +12. In the Web Part tool pane, in the **Settings** section, in the **Results control settings** section, to specify how search results should be shown, change the values in the following fields: + + - **Show advanced link** Clear the check box if you don’t want to show a link to the Advanced Search page in the Web Part. + + + - **Show result count** Clear the check box if you don't want to show the number of results found in the Web Part. + + + - **Show language dropdown** Clear the check box if you don't want to show the language drop-down in the Web Part. + + + - **Show sort dropdown** Select the check box if you want to show the sort drop-down in the Web Part. + + + - **Show paging** Clear the check box if you don't want to show paging in the Web Part. + + + - **Show preferences link** Clear the check box if you don't want to show a link to the preferences page in the Web Part. + + + - **Show AlertMe link** Clear the check box if you don't want to show a link to the **Alert Me** page in the Web Part. For more information about search alerts, see [Enable search alerts in SharePoint Server](html/enable-search-alerts-in-sharepoint-server.md). + + + +## To disable stemming in a Search Results Web Part + + +Stemming means that nouns and adjectives in a query are expanded to different possible inflections. For example, if a person enters the English word "foot" in a query, it is automatically expanded to {"feet"}. Similarly, the word "overview" is expanded to {"overviews"}. **To disable stemming in a Search Results Web Part** +1. Verify that the user account that performs this procedure is a member of the Designers SharePoint group on the Enterprise Search Center site. + + +2. On the search results page, click the **Settings** menu, and then click **Edit page**. + + +3. In the Search Results Web Part, click the **Search Results Web Part Menu** arrow, click **Export…**, and then save the Web Part to your computer. + + +4. Open the Web Part in a text editor — for example, Notepad. + + +5. Change the value for **EnableStemming** to **false**, and then save the file with a new name — for example, Search_Results_NoStemming.webpart. + + +6. On the search results page, in the **Main Zone**, click **Add a Web Part**. + + +7. In the **Categories** section, click the **Upload a Web Part** arrow. + + +8. In the **Upload a Web Part** section, click **Browse** to find the Web Part file that you have edited, and then click **Upload**. + + +9. To add the customized **Search Results Web Part** to the search results page, do the following: + + - Browse to the search results page. + + + - Click the **Settings** menu, and then click **Edit Page**. + + + - In the Web Part Zone where you want to add the Web Part, click **Add a Web Part**. + + + - In the **Categories** list, select **Imported Web Parts**. + + + - In the **Parts** list, select the Web Part that you uploaded, and then click **Add**. + + +10. To remove the default Search Results Web Part from the search results page, do the following: + + - Browse to the search results page. + + + - Click the **Settings** menu, and then click **Edit Page**. + + + - In the Web Part, click the **Search Results Web Part** menu arrow, and then click **Delete**. + + + +> [!NOTE:] + + + + + + +# See also + +#### + + [Query variables in SharePoint Server](html/query-variables-in-sharepoint-server.md) + + + + [Configure result sources for search in SharePoint Server](html/configure-result-sources-for-search-in-sharepoint-server.md) + + + + [Plan to transform queries and order results in SharePoint Server](html/plan-to-transform-queries-and-order-results-in-sharepoint-server.md) + + + + +#### + + [Blog series: How to change the way search results are displayed in SharePoint Server 2013](https://blogs.technet.com/b/tothesharepoint/archive/2013/09/03/how-to-change-the-way-search-results-are-displayed-in-sharepoint-server-2013.aspx) + + + + + + + + diff --git a/SharePoint/configure-proxy-server-settings-for-search-in-sharepoint-server.md b/SharePoint/configure-proxy-server-settings-for-search-in-sharepoint-server.md new file mode 100644 index 0000000000..569d6a5bf5 --- /dev/null +++ b/SharePoint/configure-proxy-server-settings-for-search-in-sharepoint-server.md @@ -0,0 +1,77 @@ +--- +title: Configure proxy server settings for Search in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 3e7b12cf-e9bb-48be-9484-950ba70f466c +--- + + +# Configure proxy server settings for Search in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-13* **Summary:** Specify a proxy server to send requests to crawl content or query federated content repositories.A farm administrator or Search service application administrator can specify proxy server settings for sending HTTP requests to crawl content or query federated content repositories. A *proxy server* is a computer that functions as an intermediary to forward a client request to another server and return the results to the client. Using a proxy server can help increase intranet security and can help improve response times for client search requests. +## + + + **To configure proxy server settings for crawling and federation** +1. Verify that the user account that is performing this procedure is a farm administrator or a Search service application administrator. + + +2. In Central Administration, in the Quick Launch, click **General Application Settings**. + + +3. On the **General Application Settings** page, in the **Search** section, click **Farm Search Administration**. + + +4. On the **Farm Search Administration** page, in the **Farm-Level Search Settings** section, in the **Proxy server for crawling and federation** row, click the value. + + The default value is **None**. + + +5. In the **Search Proxy Setting** dialog box, do one of the following: + + ![Search Proxy Setting dialog box](images/) + + + + + + + - Select **Do not connect by using a proxy server** if you do not want to use a proxy server for crawling or federation. + + + - Select **Use the proxy server specified** if you want to use a proxy server for crawling or federation, and then do the following: + +1. In the **Address** box, type the URL of the proxy server. + + +2. In the **Port** box, if the proxy server is not using the default port, type the port number that the proxy server is using. + + +3. Select the **Bypass proxy server for local (intranet) addresses** check box if you do not want the crawler to use the proxy server when crawling within the intranet. + + +4. In the **Do not use proxy server for addresses beginning with** box, type the appropriate addresses. Separate the addresses by using semicolons. + + +5. Select the **Use these proxy settings for access to federated sites** check box if you want the search system to use the proxy server when it queries external content repositories. + + +6. In the **Search Proxy Setting** dialog box, click **OK**. + + + +# See also + +#### + + [Manage crawling in SharePoint Server](html/manage-crawling-in-sharepoint-server.md) + + + + [Plan crawling and federation in SharePoint Server](html/plan-crawling-and-federation-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-result-sources-for-search-in-sharepoint-server.md b/SharePoint/configure-result-sources-for-search-in-sharepoint-server.md new file mode 100644 index 0000000000..1be7883496 --- /dev/null +++ b/SharePoint/configure-result-sources-for-search-in-sharepoint-server.md @@ -0,0 +1,210 @@ +--- +title: Configure result sources for search in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: d6845f9b-7c1e-4220-a24d-1e5cade8f0d8 +--- + + +# Configure result sources for search in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-18* **Summary:** Learn how to create and manage result sources in .SharePoint Server 2016 and SharePoint Server 2013. *Result sources* limit searches to certain content or to a subset of search results. SharePoint Server provides 16 pre-defined result sources. The pre-configured default result source is **Local SharePoint Results**. You can specify a different result source as the default. For more information, see [Understanding result sources for search in SharePoint Server](html/understanding-result-sources-for-search-in-sharepoint-server.md).In this article: +- [Before you begin](#BKMK_Before) + + +- [Create a result source](#BKMK_CreateResutlSource) + + +- [Set a result source as default](#BKMK_Default) + + + +## Before you begin + + + +> [!NOTE:] +> [Plan browser support](https://go.microsoft.com/fwlink/p/?LinkId=246502)> **Accessibility for SharePoint 2013**> [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)> [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504)> [Touch](https://go.microsoft.com/fwlink/p/?LinkId=246506) + + + + + +## Create a result source + + +You can create a result source for a Search service application, a site collection, or a site. The following table shows the permissions that are required to create a result source at each level, and where the result source can be used. +### Levels and permissions for result sources + +When you create a result source at this level You must have this permission The result source can be used in Search service application
Search service application administrator
All site collections in web applications that consume the Search service application
Site collection
Site collection administrator
All sites in the site collection
Site
Site owner
The site
**To create a result source** +1. Depending on the level at which you want to create the result source, do one of the following: + + - To create a result source for a Search service application: + +1. Verify that the user account that performs this procedure is an administrator on the Search service application. + + +2. In Central Administration, in the **Application Management** section, click **Manage service application**. + + +3. Click the Search service application for which you want to create a result source. + + +4. On the **Search Administration** page for the Search service application, on the Quick Launch, in the **Queries and Results** section, click **Result Sources**. + + + - To create a result source for a site collection: + +1. Verify that the user account that performs this procedure is an administrator for the site collection. + + +2. On the **Settings** menu for the site collection, click **Site Settings**. + + +3. On the **Site Settings** page, in the **Site Collection Administration** section, click **Search Result Sources**. + + + - To create a result source for a site: + +1. Verify that the user account that performs this procedure is a member of the Owners group for the site. + + +2. On the **Settings** menu for the site, click **Site Settings**. + + +3. On the **Site Settings** page, in the **Search** section, click **Result Sources**. + + +2. On the **Manage Result Sources** page, click **New Result Source**. + + +3. On the **Add Result Source** page, in the **General Information** section, do the following: + +1. In the **Name** box, type a name for the result source. + + +2. In the **Description** box, type a description of the result source. + + +4. In the ** Protocol** section, select one of the following protocols for retrieving search results: + + - **Local SharePoint**, the default protocol, provides results from the search index for this Search service application. + + + - **Remote SharePoint** provides results from the index of a search service in another farm. + + > [!IMPORTANT:] + + - **OpenSearch** provides results from a search engine that uses the OpenSearch 1.0/1.1 protocol. + + + - **Exchange** provides results from Exchange Server 2013 through a SharePoint Server eDiscovery Center. Click **Use AutoDiscover** to have the search system find an Exchange Server 2013 endpoint automatically, or type the URL of the Exchange web service to retrieve results from — for example, **https://contoso.com/ews/exchange.asmx**. + + > [!NOTE:] + > The Exchange protocol only enables you to discover Exchange Server 2013 content, and only from a SharePoint Server eDiscovery Center. For more information, see "Configure communication between SharePoint Server 2013 and Exchange Server 2013" in [Configure eDiscovery in SharePoint Server](html/configure-ediscovery-in-sharepoint-server.md). > The Exchange Web Services Managed API must be installed on the computer on which the search service is running. For more information, see [Optional software](hardware-and-software-requirements-for-sharepoint-server-2016.md#OptionalSoftware) in [Hardware and software requirements for SharePoint Server 2016](html/hardware-and-software-requirements-for-sharepoint-server-2016.md). +5. In the previous step (step 4), if you selected either **Local SharePoint** or **Remote SharePoint** for the protocol, then in the **Type** section, select **SharePoint Search Results** to search the whole index, or select **People Search Results** to enable query processing that is specific to people search. + + +6. If you selected **Remote SharePoint** for the protocol in step 4 of this procedure, then in the **Remote Service URL** section, type the address of the root site collection of the remote SharePoint farm. + + +7. If you selected **OpenSearch 1.0/1.1** for the protocol in step 4 of this procedure, then in the **Source URL** section, type the URL of the OpenSearch source. + + +8. If you selected **Exchange** for the protocol in step 4 of this procedure, then in the **Exchange Source URL** section, type the URL of the Exchange web service — for example, **https://contoso.com/ews/exchange.asmx**. + + +9. In the **Query Transform** section, do one of the following: + + - Leave the default query transform ( **searchTerms** ) as is. In this case, the query will be unchanged since the previous transform. + + + - Type a different query transform in the text box. For more information, see [Understanding query transforms](https://office.microsoft.com/en-us/sharepoint-server-help/understanding-query-transforms-HA102848843.aspx). + + + - Use the Query Builder to configure a query transform by doing the following: + +1. Click **Launch Query Builder**. + + +2. In the **Build Your Query** dialog box, optionally build the query by specifying filters, sorting, and testing on the tabs as shown in the following tables. + + + + - +### On the BASICS tab + + **Keyword filter**
You can use keyword filters to add pre-defined query variables to the query transform. You can select pre-defined query variables from the drop-down list, and then add them to the query by clicking **Add keyword filter**.
For an overview of query variables, see [Query variables in SharePoint Server](html/query-variables-in-sharepoint-server.md).
**Property filter**
You can use property filters to query the content of managed properties that are set to *queryable* in the search schema.
You can select managed properties from the **Property filter** drop-down list. Click **Add property filter** to add the filter to the query.
- +### On the SORTING tab + + **Sort results**
In the **Sort by** menu, you can select a managed property from the list of managed properties that are set as sortable in the search schema, and then select **Descending** or **Ascending**. To sort by relevance, that is, to use a ranking model, select **Rank**. You can click **Add sort level** to specify a property for a secondary level of sorting for search results.
+> [!NOTE:] + + + + + + **Ranking Model**
If you selected *Rank* from the **Sort by** list, you can select the ranking model to use for sorting.
**Dynamic ordering**
You can click **Add dynamic ordering rule** to specify additional ranking by adding rules that change the order of results within the result block when certain conditions are satisfied.
- +### On the TEST tab + + **Query text**
You can view the final query text, which is based on the original query template, the applicable query rules, and the variable values.
Click **Show more** to display the options in the following rows of this table.

**Query template**
You can view the query as it is defined in the **BASICS** tab or in the text box in the **Query transform** section on the Add Result Source page.
**Query template variables**
You can test the query template by specifying values for the query variables.
10. On the **Add Result Source** page, in the **Credentials Information** section, select the authentication type that you want for users to connect to the result source. + + + +## Set a result source as default + + + You can set any result source as the default result source. Specifying a result source as default can make it easier to edit the query in Search Web Parts. For example, when you add a Content Search Web Part to a page, the Web Part automatically uses the default result source. For more information, see **Configure Search Web Parts in SharePoint Server**. **To set a result source as default** +1. Perform the appropriate procedures in the following list depending on the level at which the result source was configured. + + - If the result source was created at the Search service application level, do the following: + +1. Verify that the user account that performs this procedure is an administrator for the Search service application. + + +2. In Central Administration, in the **Application Management** section, click **Manage service applications**. + + +3. Click the Search service application for which you want to set the result source as default. + + +4. On the **Search Administration** page, in the **Queries and Results** section, click **Result Sources**. + + + - If the result source is at the site collection level, do the following: + +1. Verify that the user account that performs this procedure is an administrator for the site collection administrator. + + +2. On the **Settings** menu for the site collection, click **Site Settings**. + + +3. On the **Site Settings** page, in the **Site Collection Administration** section, click **Search Result Sources**. + + + - If the result source is at the site level, do the following: + +1. Verify that the user account that performs this procedure is a member of the Owners group for the site. + + +2. On the **Settings** menu for the site, click **Site Settings**. + + +3. On the **Site Settings** page, in the **Search** section, click **Result Sources**. + + +2. On the **Manage Result Sources** page, point to the result source that you want to set as default, click the arrow that appears, and then click **Set as Default**. + + + +# See also + +#### + + [Query variables in SharePoint Server](html/query-variables-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh.md b/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh.md new file mode 100644 index 0000000000..ba054f3750 --- /dev/null +++ b/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh.md @@ -0,0 +1,202 @@ +--- +title: Configure scheduled data refresh for Power Pivot by using a specified account (SharePoint Server 2013) +ms.prod: SHAREPOINT +ms.assetid: 53598509-9821-4c0b-9ab4-a9e594ac8fec +--- + + +# Configure scheduled data refresh for Power Pivot by using a specified account (SharePoint Server 2013) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-06* **Summary:** Learn to configure scheduled data refresh in Power Pivot for SharePoint by using an account that you specify. +> [!IMPORTANT:] + + + + + +In this article, we’ll take a look at configuring scheduled data refresh in SQL Server 2012 Power Pivot for SharePoint 2013 by using an account that you specify.We recommend [using Secure Store to store your data refresh credentials](html/configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoin.md), but if Secure Store is not available or if you working in a test or pre-production environment, this article will show you how to easily configure the account of your choice for scheduled data refresh. +## Before you begin + + +Before starting, you will need: +- An Active Directory account that you can use to access the data sources used in your report. We’ll refer to this as the *data access account* . We’ll look at how to configure the account for access to your data sources in this article, so you just need the account itself to get started. + + +- Contribute access to the SharePoint document library that you will be using. + + +Additionally, be sure that [Excel Services](html/overview-of-excel-services-in-sharepoint-server-2013.md) is configured in your SharePoint Server 2013 farm. +## Video demonstration + + +This video shows the steps involved in configuring scheduled data refresh in SQL Server 2012 Power Pivot for SharePoint 2013 by using an account that you specify, as described in this article. **Video: Configure scheduled data refresh for Power Pivot by using a specified account** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + +## Configure access to your data source + + +The first step in setting up scheduled data refresh is to ensure that the data access account has the proper access to the data source used in your report. We’ll take a look at SQL Server and Analysis Services data sources. +## Use a SQL Server data source + +If you’re using SQL Server for your data source, you’ll need to make sure that your data access account has read permissions to the SQL Server database where your data resides. **To set read permission on a SQL Server database** +1. In SQL Server Management Studio, connect to the database engine. + + +2. Expand **Security**. + + +3. Right-click **Logins**, and then choose **New Login**. + + +4. In the **Login name** box, type the domain and user name of the account to which you want to grant database access. + + +5. On the **User Mapping** page, select the **Map** check box for the database to which you want to grant access. + + +6. Select the **db_datareader** check box. + + +7. Choose **OK**. + + +If you’re also using Analysis Services, see the next section for information about how to set up access to Analysis Services data sources. If you’re not using Analysis Services, skip ahead to [Set up a data refresh schedule in PowerPivot4SharePoint_2nd_NoVer](#ver). +## Use an Analysis Services data source + +If you’re using Analysis Services, you’ll need to make sure that your data access account is a member of the proper Analysis Services role and that the role has read access to the Analysis Services cube. **To set read permission on an Analysis Services cube** +1. In SQL Server Management Studio, connect to Analysis Services. + + +2. Expand **Databases**, and expand the database to which you want to grant access. + + +3. Right-click **Roles**, and then choose **New Role**. + + +4. Type a name for the role. + + +5. On the **Membership** page: + +1. Choose **Add**. + + +2. Type your data access account, and then choose **OK**. + + +6. On the **Cubes** page, select **Read** access for the cubes to which you want to grant access. + + +7. Choose **OK**. + + + +## Set up a data refresh schedule in Power Pivot for SharePoint + + +Now that everything is configured, we can set up the refresh schedule and other settings in Power Pivot for SharePoint. We’ll start by building a test workbook with a data model in Excel and publishing it to a document library in a site collection where Power Pivot for SharePoint is enabled. Then, we can configure the refresh settings. **To create a test workbook** +1. In Excel, on the **Data** tab, choose **From Other Sources**, and then choose **From SQL Server**. + + +2. Type the name of the instance of SQL Server where your data resides. + + +3. Follow the wizard through to connect to the table that contains your data. + + +4. When the wizard completes, you should see the **Import Data** dialog box. Choose the **Only Create Connection** option, and then select the **Add this data to the Data Model** check box. + + +5. Choose **OK**. + + +6. On the **Power Pivot** tab, choose **Manage**. + + +7. On the **Power Pivot** ribbon, choose **PivotTable**. + + +8. On the **Insert Pivot** dialog box, choose the **Existing Worksheet** option, and then choose **OK**. + + +9. Select the fields that you want in the PivotTable report. + + +10. Save the workbook to a document library on the site collection where you enabled Power Pivot. + + +Now that the workbook has been saved to a SharePoint document library, let’s configure the refresh settings. **To configure refresh settings for a workbook** +1. In the document library where your Excel workbook is stored, choose the ellipsis (...) control twice, and then choose **Manage Power Pivot Data Refresh**. + + + + + +![Screenshot of controls in document library.](images/) + + + + + + + + + + + + + + +2. On the **Manage Data Refresh** page, select the **Enable** check box. + + +3. In the **Schedule Details** section, choose the schedule options that you want for refreshing the data in this workbook. + + +4. Optionally, if you want the workbook to refresh right away, select the **Also refresh as soon as possible** check box. + + +5. In the **Credentials** section, choose the **Connect using the following Windows user credentials** option. + + +6. Type the user name and password of the data access account. + + +7. Choose **OK**. + + +You can test if data refresh is working properly by making some changes to your data, and then setting the workbook to refresh right away by using the **Also refresh as soon as possible** option.Note that anytime you make changes to the data refresh settings page, such as selecting the **Also refresh as soon as possible** check box, you’ll need to reenter the password of the data access account. +# See also + +#### + + [Configure Power Pivot for SharePoint 2013](html/configure-power-pivot-for-sharepoint-2013.md) + + + + [Configure scheduled data refresh for Power Pivot by using a specified account (SharePoint Server 2013)](html/configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh.md) + + + + [Configure scheduled data refresh for Power Pivot by using the unattended data refresh account (SharePoint Server 2013)](html/configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re.md) + + + + + + + + diff --git a/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoin.md b/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoin.md new file mode 100644 index 0000000000..65125f1e65 --- /dev/null +++ b/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-secure-store-sharepoin.md @@ -0,0 +1,262 @@ +--- +title: Configure scheduled data refresh for Power Pivot by using Secure Store (SharePoint Server 2013) +ms.prod: SHAREPOINT +ms.assetid: c8209ecc-59e4-4568-a7e6-782a6b0ab02f +--- + + +# Configure scheduled data refresh for Power Pivot by using Secure Store (SharePoint Server 2013) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-06* **Summary:** Learn to configure scheduled data refresh in Power Pivot for SharePoint by using Secure Store. +> [!IMPORTANT:] + + + + + +In this article, we’ll take a look at configuring scheduled data refresh in SQL Server 2012 Power Pivot for SharePoint 2013 by using the Secure Store Service.By using Secure Store, you can store your data access credentials in an encrypted database and Power Pivot for SharePoint can use these credentials to refresh the data in your reports on a schedule that you set up. +## Before you begin + + +Before starting, you will need: +- An Active Directory account that you can use to access the data sources used in your report. We’ll refer to this as the *data access account* . We’ll look at how to configure the account for access to your data sources in this article, so you just need the account itself to get started. + + +- An Active Directory group that contains all users who will trigger data refresh, either by setting the data refresh schedule or by manually starting a data refresh outside the normal schedule. We’ll refer to this group as the *data refresh users group* . + + +- Contribute access to the SharePoint document library that you will be using. + + +Additionally, be sure that [Excel Services](html/overview-of-excel-services-in-sharepoint-server-2013.md) and [Secure Store](html/plan-the-secure-store-service-in-sharepoint-server.md) are configured in your SharePoint Server 2013 farm. +## Video demonstration + + +This video shows the steps involved in configuring scheduled data refresh in SQL Server 2012 Power Pivot for SharePoint 2013 by using the Secure Store Service, as described in this article. **Video: Configure scheduled data refresh for Power Pivot by using Secure Store** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + +## Configure access to your data source + + +The first step in setting up scheduled data refresh by using Secure Store is to ensure that the data access account has the proper access to the data source used in your report. We’ll take a look at SQL Server and Analysis Services data sources. +## Use a SQL Server data source + +If you’re using SQL Server for your data source, you’ll need to make sure that your data access account has read permissions to the SQL Server database where your data resides. **To set read permission on a SQL Server database** +1. In SQL Server Management Studio, connect to the database engine. + + +2. Expand **Security**. + + +3. Right-click **Logins**, and then choose **New Login**. + + +4. In the **Login name** box, type the domain and user name of the account to which you want to grant database access. + + +5. On the **User Mapping** page, select the **Map** check box for the database to which you want to grant access. + + +6. Select the **db_datareader** check box. + + +7. Choose **OK**. + + +If you’re also using Analysis Services, see the next section for information about how to set up access to Analysis Services data sources. If you’re not using Analysis Services, skip ahead to [Store your data access account in Secure Store](#StoreAccountInSecureStore). +## Use an Analysis Services data source + +If you’re using Analysis Services, you’ll need to make sure that your data access account is a member of the proper Analysis Services role and that the role has read access to the Analysis Services cube. **To set read permission on an Analysis Services cube** +1. In SQL Server Management Studio, connect to Analysis Services. + + +2. Expand **Databases**, and expand the database to which you want to grant access. + + +3. Right-click **Roles**, and then choose **New Role**. + + +4. Type a name for the role. + + +5. On the **Membership** page: + +1. Click **Add**. + + +2. Type your data access account, and then choose **OK**. + + +6. On the **Cubes** page, select **Read** access for the cubes to which you want to grant access. + + +7. Choose **OK**. + + + +## Store your data access account in Secure Store + + +Once the data access account has been granted access to your data source, the next step is to store this account in Secure Store. First, we’ll create a Secure Store target application for the data access account. A target application is basically a way of defining some things about the account, like what kind of account it is and who’s allowed to use it. **To create a Secure Store target application** +1. In Central Administration, under **Application Management**, choose **Manage service applications**. + + +2. Click the Secure Store service application. + + +3. On the ribbon, on the **Edit** tab, choose **New**. + + +4. Type a **Target Application ID**. + + > [!NOTE:] + +5. Type a **Display Name** and **Contact E-mail**. + + +6. For **Target Application Type**, choose **Group**. + + +7. Choose **Next**. + + +8. Keep the default credential settings, and choose **Next**. + + +9. Specify a user to administer the target application, such as your farm administrator, in the **Target Application Administrators** box. + + +10. In the **Members** box, include: + + - The account that runs the application pool for the Power Pivot for SharePoint service application. + + + - The data refresh group that contains the users who will schedule or start a data refresh in Power Pivot for SharePoint. + + +11. Choose **OK**. + + +Once the target application has been created, the next step is to associate your data access account with it. **To associate the data access account with the target application** +1. On the Secure Store management page, select the check box for the target application for which you want to set the credentials. + + +2. On the ribbon, in the **Credentials** section, choose **Set**. + + +3. Type the user name and password of your access account. + + +4. Choose **OK**. + + +Secure Store setup is now complete. The next step is to set up a data refresh schedule in Power Pivot for SharePoint. +## Set up a data refresh schedule in Power Pivot for SharePoint + + +Now that everything is configured, we can set up the refresh schedule and other settings in Power Pivot for SharePoint. We’ll start by building a test workbook with a data model in Excel and publishing it to a document library in a site collection where Power Pivot for SharePoint is enabled. Then, we can configure the refresh settings. **To create a test workbook** +1. In Excel, on the **Data** tab, choose **From Other Sources**, and then choose **From SQL Server**. + + +2. Type the name of the instance of SQL Server where your data resides. + + +3. Follow the wizard through to connect to the table that contains your data. + + +4. When the wizard completes, you should see the **Import Data** dialog box. Choose the **Only Create Connection** option, and then select the **Add this data to the Data Model** check box. + + +5. Choose **OK**. + + +6. On the **Power Pivot** tab, choose **Manage**. + + +7. On the **Power Pivot** ribbon, choose **PivotTable**. + + +8. On the **Insert Pivot** dialog box, choose the **Existing Worksheet** option, and then choose **OK**. + + +9. Select the fields that you want in the PivotTable report. + + +10. Save the workbook to a document library on the site collection where you enabled Power Pivot. + + +Now that the workbook has been saved to a SharePoint document library, let’s configure the refresh settings. **To configure refresh settings for a workbook** +1. In the document library where your Excel workbook is stored, choose the ellipsis (...) control twice, and then choose **Manage Power Pivot Data Refresh**. + + + + + +![Screenshot of controls in document library.](images/) + + + + + + + + + + + + + + +2. On the Manage Data Refresh page, select the **Enable** check box. + + +3. In the **Schedule Details** section, choose the schedule options that you want for refreshing the data in this workbook. + + +4. Optionally, if you want the workbook to refresh right away, select the **Also refresh as soon as possible** check box. + + +5. In the **Credentials** section, choose the **Connect using the credentials saved in Secure Store Service** option. + + +6. Type the ID of the Secure Store target application that you created in the **ID** box. + + +7. Choose **OK**. + + +You can test if data refresh is working properly by making some changes to your data, and then setting the workbook to refresh right away by using the **Also refresh as soon as possible** option. +# See also + +#### + + [Configure Power Pivot for SharePoint 2013](html/configure-power-pivot-for-sharepoint-2013.md) + + + + [Configure scheduled data refresh for Power Pivot by using a specified account (SharePoint Server 2013)](html/configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh.md) + + + + [Configure scheduled data refresh for Power Pivot by using the unattended data refresh account (SharePoint Server 2013)](html/configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re.md) + + + + + + + + diff --git a/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re.md b/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re.md new file mode 100644 index 0000000000..375761df36 --- /dev/null +++ b/SharePoint/configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re.md @@ -0,0 +1,199 @@ +--- +title: Configure scheduled data refresh for Power Pivot by using the unattended data refresh account (SharePoint Server 2013) +ms.prod: SHAREPOINT +ms.assetid: 3fdbc40b-8562-4bec-be89-113a64e19911 +--- + + +# Configure scheduled data refresh for Power Pivot by using the unattended data refresh account (SharePoint Server 2013) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013* * **Topic Last Modified:** 2017-07-06* **Summary:** Learn to configure scheduled data refresh in Power Pivot for SharePoint by using the unattended data refresh account. +> [!IMPORTANT:] + + + + + +In this article, we’ll take a look at configuring scheduled data refresh in SQL Server 2012 Power Pivot for SharePoint 2013 by using the unattended data refresh account.By using the unattended data refresh account, you can have the data in your workbooks refreshed using an account that was configured by your administrator. +## Before you begin + + +Before starting, you will need: +- The user name of the unattended data refresh account that was configured [when you set up Power Pivot for SharePoint originally](html/configure-power-pivot-for-sharepoint-2013.md). + + +- Contribute access to the SharePoint document library that you will be using. + + +Additionally, be sure that [Excel Services](html/overview-of-excel-services-in-sharepoint-server-2013.md) is configured in your SharePoint Server 2013 farm. +## Video demonstration + + +This video shows the steps involved in configuring scheduled data refresh in SQL Server 2012 Power Pivot for SharePoint 2013 by using the unattended data refresh account, as described in this article. **Video: Configure scheduled data refresh for Power Pivot by using the unattended data refresh account** + + + +![Video (play button) icon](images/) + + + + + + + + + + + + +## Configure access to your data source + + +The first step in setting up scheduled data refresh by using the unattended data refresh account is to ensure that it has the proper access to the data source used in your report. We’ll take a look at SQL Server and Analysis Services data sources. +## Use a SQL Server data source + +If you’re using SQL Server for your data source, you’ll need to make sure that your unattended data refresh account has read permissions to the SQL Server database where your data resides. **To set read permission on a SQL Server database** +1. In SQL Server Management Studio, connect to the database engine. + + +2. Expand **Security**. + + +3. Right-click **Logins**, and then choose **New Login**. + + +4. In the **Login name** box, type the domain and user name of your unattended data refresh account. + + +5. On the **User Mapping** page, select the **Map** check box for the database to which you want to grant access. + + +6. Select the **db_datareader** check box. + + +7. Choose **OK**. + + +If you’re also using Analysis Services, see the next section for information about how to set up access to Analysis Services data sources. If you’re not using Analysis Services, skip ahead to [Set up a data refresh schedule in PowerPivot4SharePoint_2nd_NoVer](#ver). +## Use an Analysis Services data source + +If you’re using Analysis Services, you’ll need to make sure that your data access account is a member of the proper Analysis Services role and that the role has read access to the Analysis Services cube. **To set read permission on an Analysis Services cube** +1. In SQL Server Management Studio, connect to Analysis Services. + + +2. Expand **Databases**, and expand the database to which you want to grant access. + + +3. Right-click **Roles**, and then choose **New Role**. + + +4. Type a name for the role. + + +5. On the **Membership** page: + +1. Choose **Add**. + + +2. Type your unattended data refresh account, and then choose **OK**. + + +6. On the **Cubes** page, select **Read** access for the cubes to which you want to grant access. + + +7. Choose **OK**. + + + +## Set up a data refresh schedule in Power Pivot for SharePoint + + +Now that everything is configured, we can set up the refresh schedule and other settings in Power Pivot for SharePoint. We’ll start by building a test workbook with a data model in Excel and publishing it to a document library in a site collection where Power Pivot for SharePoint is enabled. Then, we can set the refresh schedule. **To create a test workbook** +1. In Excel, on the **Data** tab, choose **From Other Sources**, and then choose **From SQL Server**. + + +2. Type the name of the instance of SQL Server where your data resides. + + +3. Follow the wizard through to connect to the table that contains your data. + + +4. When the wizard completes, you should see the **Import Data** dialog box. Choose the **Only Create Connection** option, and then select the **Add this data to the Data Model** check box. + + +5. Choose **OK**. + + +6. On the **Power Pivot** tab, choose **Manage**. + + +7. On the **Power Pivot** ribbon, choose **PivotTable**. + + +8. On the **Insert Pivot** dialog box, choose the **Existing Worksheet** option, and then choose **OK**. + + +9. Select the fields that you want in the PivotTable report. + + +10. Save the workbook to a document library on the site collection where you enabled Power Pivot. + + +Now that the workbook has been saved to a SharePoint document library, let’s configure the refresh settings. **To configure refresh settings for a workbook** +1. In the document library where your Excel workbook is stored, choose the ellipsis (...) control twice, and then choose **Manage Power Pivot Data Refresh**. + + + + + +![Screenshot of controls in document library.](images/) + + + + + + + + + + + + + + +2. On the **Manage Data Refresh** page, select the **Enable** check box. + + +3. In the **Schedule Details** section, choose the schedule options that you want for refreshing the data in this workbook. + + +4. Optionally, if you want the workbook to refresh right away, select the **Also refresh as soon as possible** check box. + + +5. In the **Credentials** section, choose the **Use the data refresh account configured by the administrator** option. + + +6. Choose **OK**. + + +You can test if data refresh is working properly by making some changes to your data, and then setting the workbook to refresh right away by using the **Also refresh as soon as possible** option. +# See also + +#### + + [Configure Power Pivot for SharePoint 2013](html/configure-power-pivot-for-sharepoint-2013.md) + + + + [Configure scheduled data refresh for Power Pivot by using a specified account (SharePoint Server 2013)](html/configure-scheduled-data-refresh-for-power-pivot-by-using-a-specified-account-sh.md) + + + + [Configure scheduled data refresh for Power Pivot by using the unattended data refresh account (SharePoint Server 2013)](html/configure-scheduled-data-refresh-for-power-pivot-by-using-the-unattended-data-re.md) + + + + + + + + diff --git a/SharePoint/configure-secure-store-for-use-with-performancepoint-services.md b/SharePoint/configure-secure-store-for-use-with-performancepoint-services.md new file mode 100644 index 0000000000..2047cea5e3 --- /dev/null +++ b/SharePoint/configure-secure-store-for-use-with-performancepoint-services.md @@ -0,0 +1,154 @@ +--- +title: Configure Secure Store for use with PerformancePoint Services +ms.prod: SHAREPOINT +ms.assetid: 95e12c80-7a86-4655-ba11-a05b9587fee0 +--- + + +# Configure Secure Store for use with PerformancePoint Services + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-06* **Summary:** Configure PerformancePoint Services to use a Secure Store target application for external data refresh.PerformancePoint Services supports two methods of using Secure Store Service to connect to external data: +- You can specify a Secure Store target application in PerformancePoint Dashboard Designer. This article describes how to do this. + + +- You can use an unattended service account. For more information, see [Configure the unattended service account for PerformancePoint Services](html/configure-the-unattended-service-account-for-performancepoint-services.md). + + +To configure PerformancePoint Services data access to use a Secure Store target application, you use the following process: +1. [Configure a data access account](#part1) + + +2. [Create a Secure Store target application](#part2) + + +3. [Configure a data connection to use a Secure Store target application](#ConfigureWorkbook) + + + +## Configure a data access account + + +You must have a Windows Active Directory account that can be granted access to the data source to which you want to connect in Dashboard Designer. This account will be stored in Secure Store.Once you have created the account, the next step is to grant that account read access to the required data. (In this article, we use the example of accessing a SQL Server database. If you are using a data source other than SQL Server, see the instructions for your data source to create a logon with data-read permissions for the data access account.)Follow these steps to create a SQL Server logon and grant Read access to the database. **To create a SQL Server logon for the data access account** +1. In SQL Server Management Studio, connect to the database engine. + + +2. In Object Explorer, expand **Security**. + + +3. Right-click **Logins**, and then click **New Login**. + + +4. In the **Login name** box, type the name of the Active Directory account that you created for data access. + + +5. In the **Select a page** section, click **User Mapping**. + + +6. Select the **Map** check box for the database that you want to provide access to, and then, under **Database role membership for: **, select the **db_datareader** check box. + + +7. Click **OK**. + + +Now that you have created a data access account and granted it access to a data source, the next step is to create a Secure Store target application. +## Create a Secure Store target application + + +You must create a target application in Secure Store that contains the credentials that you created for data access. This target application can then be specified in the data source settings in Dashboard Designer.When you create the target application, you have to specify which users will be authorized to use the credentials stored in Secure Store. You can list users individually, or you can use an Active Directory group. We recommend that you use an Active Directory group for ease of administration. +> [!NOTE:] + + + + + +Use the following procedure to create a Secure Store target application. **To create a target application** +1. On the Central Administration home page, in the **Application Management** section, click **Manage service applications**. + + +2. Click the Secure Store service application. + + +3. On the ribbon, click **New**. + + +4. In the **Target Application ID** box, type a unique identifier for this target application (for example, **PerformancePointServicesDataAccess** ). + + +5. In the **Display Name** box, type a friendly name or short description. + + +6. In the **Contact E-mail** box, type the e-mail address for a contact for this target application. + + +7. In the **Target Application Type** drop-down list, select **Group**. + + +8. Click **Next**. + + +9. On the Credential Fields page, leave the default values of Windows User Name and Windows Password and click **Next**. + + +10. On the Specify the membership settings page: + + - In the **Target Application Administrators** box, type the account of the user who will administer this target application. + + > [!NOTE:] + + - In the **Members** box, type the users to whom you want to grant the ability to refresh data. + + > [!NOTE:] + +11. Click **OK**. + + +Use the following procedure to set the credentials for the target application. **To set the credentials for the target application** +1. On the Secure Store Service Application page, in the **Target Application ID** column, point to the target application that you just created, click the arrow that appears, and then click **Set Credentials**. + + +2. Type the user name and password of the data access account. + + +3. Click **OK**. + + +Once you have set the credentials for the target application, the target application is ready to use. The next step is to specify this target application in Dashboard Designer as part of the data source settings. +## Configure a data connection to use a Secure Store target application + + +You must configure your PerformancePoint Services data connection to use the Secure Store. After doing so, you can connect to the external data source in Dashboard Designer and create your dashboard. Use the following procedure to configure a PerformancePoint Services data connection. **To configure a data connection to use a Secure Store target application** +1. In Dashboard Designer, on the Create tab, click Data Source. + + +2. On the **Select a Data Source Template** dialog box, choose your data source and click OK. + + +3. In the Data Source Settings section, choose the Use a stored account option. + + +4. In the Application ID box, type the target application ID of the Secure Store target application that you created. + + +5. In the Connection Settings section, connect to your external data source. + + +6. Click **Test Data Source** to test the connection. + + +7. Create and publish your dashboard. + + > [!NOTE:] + +With the target application specified in Dashboard Designer, PerformancePoint Services uses the credentials associated with that target application to refresh the data in the dashboard after you have published it to SharePoint Server. +# See also + +#### + + [Configure the Secure Store Service in SharePoint Server](html/configure-the-secure-store-service-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o.md b/SharePoint/configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o.md new file mode 100644 index 0000000000..ff16cf0904 --- /dev/null +++ b/SharePoint/configure-server-to-server-authentication-from-sharepoint-server-to-sharepoint-o.md @@ -0,0 +1,439 @@ +--- +title: Configure server-to-server authentication from SharePoint Server to SharePoint Online +ms.prod: SHAREPOINT +ms.assetid: 9cd888dc-9104-422e-8d8a-d795f0b1c0d0 +--- + + +# Configure server-to-server authentication from SharePoint Server to SharePoint Online + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Online, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-06-21* **Summary:**  Learn how to build a server-to server trust between SharePoint Server and SharePoint Online. **This article is part of a roadmap of procedures for configuring SharePoint hybrid solutions. Be sure you're [following a roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md) when you do the procedures in this article.** +## Configure server-to-server authentication + +This article provides guidance for the SharePoint hybrid environment deployment process, which integrates SharePoint Server and SharePoint Online. +> [!TIP:] + + + + + + +## Verify web application settings + + +In SharePoint hybrid, federated users can send requests to SharePoint Online from any SharePoint Server web application that’s configured to use Integrated Windows authentication with NTLM.For example, you have to make sure that the on-premises search center site(s) that you want to use in your solution are configured to use Integrated Windows authentication with NTLM. If they’re not, you have to either reconfigure the web application to use Windows authentication with NTLM or use a search center site on a web application that meets this requirement. You also have to make sure that the users who expect search results to be returned from SharePoint Online are federated users. **To verify that a web application meets the requirement** +1. Confirm that the user account that will do this procedure is a member of the Farm Administrators SharePoint group. + + +2. In Central Administration, click **Application Management** > **Manage web applications**. + + +3. In the **Name** column, select the web application that you want to verify, and then on the ribbon, click **Authentication Providers**. + + +4. In the **Authentication Providers** dialog box, in the **Zone** column, click the zone the search center site is associated with. + + +5. In the **Edit Authentication** dialog box, verify that Integrated Windows authentication and NTLM are selected as shown in the following picture. + + ![This figure illustrates the authentication type setting for a web application](images/) + + + + +## Configure OAuth over HTTP (if it is required) + + +By default, OAuth in SharePoint Server requires **HTTPS**. If you configured your primary web application to use **HTTP** instead of SSL, you have to enable OAuth over **HTTP** on every web server in your SharePoint Server farm. +> [!NOTE:] + + + + + +To enable OAuth over HTTP, run the following commands as a farm administrator account from the SharePoint 2016 Management Shell command prompt on each web server in your SharePoint Server farm. + + +``` + +$serviceConfig = Get-SPSecurityTokenServiceConfig +$serviceConfig.AllowOAuthOverHttp = $true +$serviceConfig.Update() +``` + +If you have enabled OAuth over HTTP for testing but want to reconfigure your environment to use SSL, you can disable OAuth over HTTP by running the following commands as a farm administrator account from the SharePoint 2016 Management Shell command prompt on each web server in your SharePoint Server farm. + + +``` + +$serviceConfig = Get-SPSecurityTokenServiceConfig +$serviceConfig.AllowOAuthOverHttp = $false +$serviceConfig.Update() +``` + + +## Configure server-to-server authentication between on-premises SharePoint Server and SharePoint Online + + +This section will help you set up server-to-server authentication among: +- SharePoint Server + + +- SharePoint Online + + +- Azure Active Directory + + +When you set up server-to-server authentication for hybrid environments, you create a **trust relationship** between your **on-premises SharePoint farm** and your **SharePoint Online** **tenant**, which uses Azure Active Directory as a trusted token signing service. By adding the required PowerShell modules and snap-ins, this process can occur in a single PowerShell window on an on-premises SharePoint web server. +> [!TIP:] + + + + + +Here’s a high-level view of the procedures you have to complete in this section: +1. Configure the Security Token Service (STS) in SharePoint Server: + + - Create a new STS certificate. + + + - Replace the default STS certificate on each server in your SharePoint Server farm. + + +2. Install online service management tools on a web server in your SharePoint Server farm. + + +3. Configure server-to-server authentication: + + - Set variables you’ll be using in later steps. + + + - Upload the new on-premises STS certificate to SharePoint Online. + + + - Add a Service Principal Name (SPN) to Azure. + + + - Register the SharePoint Online application principal object ID with on-premises SharePoint Server. + + + - Configure a common authentication realm between your on-premises SharePoint Server farm and SharePoint Online. + + + - Configure an Azure Active Directory application proxy on-premises. + + + +## Install online service management tools and configure the Windows PowerShell window + + +To continue, you need to install these tools on an on-premises SharePoint Server web server: +- The Microsoft Online Services Sign-In Assistant + + +- The Azure Active Directory Module for Windows PowerShell + + +- The SharePoint Online Management Shell + + +This is most easily accomplished on a web server in your SharePoint farm because it’s easier to load the *Microsoft.SharePoint.PowerShell* snap-in on the web servers than on servers that don’t have SharePoint Server installed.Authentication to SharePoint Server, SharePoint Online, and Azure Active Directory requires different user accounts. For information about how to determine which account to use, see [Accounts needed for hybrid configuration and testing](html/accounts-needed-for-hybrid-configuration-and-testing.md). +> [!NOTE:] + + + + + +To install the online service management tools and configure the PowerShell window: +1. Install the online service management tools: + +1. Install the Microsoft Online Services Sign-In Assistant: + + [Microsoft Online Services Sign-In Assistant for IT Professionals BETA (64 bit version)](https://go.microsoft.com/fwlink/?LinkId=391943) (https://go.microsoft.com/fwlink/?LinkId=391943) + + For additional information, see [Microsoft Online Services Sign-In Assistant for IT Professionals RTW](https://go.microsoft.com/fwlink/?LinkId=392322) (https://go.microsoft.com/fwlink/?LinkId=392322). + + +2. Install the Azure Active Directory Module for Windows PowerShell: + + [Azure Active Directory Module for Windows PowerShell (64 bit version)](https://go.microsoft.com/fwlink/p/?linkid=236297) (https://go.microsoft.com/fwlink/p/?linkid=236297) + + For additional information about Azure Active Directory Module for Windows PowerShell, see [Manage Azure Active Directory by using Windows PowerShell](https://aka.ms/aadposh) (https://aka.ms/aadposh). + + +3. Install the SharePoint Online Management Shell: + + [SharePoint Online Management Shell (64 bit version)](https://go.microsoft.com/fwlink/?LinkId=392323) (https://go.microsoft.com/fwlink/?LinkId=392323) + + For additional information, see [Introduction to the SharePoint Online management shell](https://go.microsoft.com/fwlink/?LinkId=392324) (https://go.microsoft.com/fwlink/?LinkId=392324). + + +2. Open a PowerShell window. + + +3. To help ensure that you don’t fill the buffer and lose any of your command history, increase the buffer size of the PowerShell window: + +1. Click the upper-left corner of the PowerShell window, and then click **Properties**. + + +2. In the PowerShell Properties window, click the **Layout** tab. + + +3. Under Screen Buffer Size, set the **Height** field to **9999**, and then click **OK**. + + +4. This step loads the modules you downloaded so you can use them in your PowerShell session. Copy the following commands into your PowerShell session, and press **Enter**. + + ``` + +Add-PSSnapin Microsoft.SharePoint.PowerShell +Import-Module Microsoft.PowerShell.Utility +Import-Module MSOnline -force +Import-Module MSOnlineExtended -force +Import-Module Microsoft.Online.SharePoint.PowerShell -force + ``` + + + If you need to run any of the configuration steps again later, remember to run these commands again to load the required modules and snap-ins in PowerShell. + + +5. Configure remoting in Microsoft PowerShell: + + From the PowerShell command prompt, type the following commands. + + + + ``` + +enable-psremoting +new-pssession + ``` + + + For more information, see [about_Remote_Requirements](https://go.microsoft.com/fwlink/?LinkId=392326) (https://go.microsoft.com/fwlink/?LinkId=392326). + + +6. To log on to your SharePoint Online tenant, from the PowerShell command prompt, type the following commands. + + ``` + +$cred=Get-Credential +Connect-MsolService -Credential $cred + ``` + + + You are prompted to log on. You need to log on using an Office 365 global administrator account. + + Leave the PowerShell window open until you've completed all the steps in this article. You need it for a variety of procedures in the following sections. + + + +## Configure server-to-server (S2S) authentication + + +Now that you installed the tools to enable you to remotely administer Azure Active Directory and SharePoint Online, you’re ready to set up server-to-server authentication. +#### About the variables you’ll create + +This section describes the variables you will set in the procedure that follows. These variables contain important information used in many of the remaining configuration steps. +### + + **Variable**
**Comments**
$spcn
The root domain name of your public domain. This value should not be in the form of a URL; it should be the **domain name only**, with **no protocol**.
An example is adventureworks.com.
$spsite
The internal URL of your on-premises primary web application, such as **http://sharepoint** or **https://sharepoint.adventureworks.com**. This value is a full URL using the proper protocol (either **http:** // or **https://** ).
This is the internal URL of the web application that you are using for hybrid functionality.

An example is http://sharepoint or https://sharepoint.adventureworks.com.

$site
The object of your on-premises primary web application. The command that populates this variable gets the object of the site you specified in the **$spsite** variable.
This variable is automatically populated.
$spoappid
The SharePoint Online application principal ID is always 00000003-0000-0ff1-ce00-000000000000. This generic value identifies SharePoint Online objects in an Office 365 tenant.

$spocontextID
The context ID (ObjectID) of your SharePoint Online tenant. This value is a unique GUID that identifies your SharePoint Online tenant.
This value is automatically detected when you run the command to set the variable.
$metadataEndpoint
The URL that is used by your Azure Active Directory proxy to connect to your Azure Active Directory tenancy.
You don't need to input a value for this variable.
+#### Step 1: Set variables + + +Now that you identified the variables that you need to set, use these instructions to set them. Pre-populating the most commonly used variables should help you do the remaining steps faster. These variables remain populated as long as you don’t close the PowerShell session. Be careful to provide accurate information wherever you see angle brackets (< >), and always remove the angle brackets before you run the command. Don’t alter the code *outside* of the angle brackets. +> [!NOTE:] + + + + + +Copy the following variable declarations and paste them into a text editor like Notepad. Set the input values specific to your organization. From the PowerShell command prompt you configured with the online service management tools, run the commands. + + +``` + +$spcn="*..com" +$spsite=Get-Spsite +$site=Get-Spsite $spsite +$spoappid="00000003-0000-0ff1-ce00-000000000000" +$spocontextID = (Get-MsolCompanyInformation).ObjectID +$metadataEndpoint = "https://accounts.accesscontrol.windows.net/" + $spocontextID + "/metadata/json/1" +``` + +After you populate these variables, you can view their values by entering the variable name in the PowerShell window. For example, entering $metadataEndpoint returns a value similar to the following:https://accounts.accesscontrol.windows.net/00fceb75-246c-4ac4-a0ad-7124xxxxxxxx/metadata/json/1 +#### Step 2: Upload the STS certificate to SharePoint Online + + +In this step, you upload the STS certificate for your SharePoint Server farm to your SharePoint Online tenant, which enables SharePoint Server and SharePoint Online to connect to and consume each other’s service applications. + + + +![This figure illustrates the architecture involved when a STS certificate is uploaded to SharePoint Online](images/) + + + +The commands in this step add the new on-premises STS certificate (public key only) to the SharePoint Online *principal object* of your Office 365 tenancy.From the PowerShell command prompt, type the following commands. + + +``` + +$stsCert=(Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate +$binCert = $stsCert.GetRawCertData() +$credValue = [System.Convert]::ToBase64String($binCert); +New-MsolServicePrincipalCredential -AppPrincipalId $spoappid -Type asymmetric -Usage Verify -Value $credValue + +``` + + +#### Step 3: Add an SPN for your public domain name to Azure Active Directory + + +In this step, you add a service principal name (SPN) to your Azure Active Directory tenant. The SPN is comprised of the SharePoint Online principal object and your company’s public DNS namespace.Just like SPNs function in Active Directory, creating this SPN registers an object in Azure Active Directory that is used to support mutual authentication between SharePoint Server and your SharePoint Online tenant. The basic syntax for the SPN is: ** ** / ** **where: +- ** is the SharePoint Online principal object, which is the same for all SharePoint Online tenants. + + +- ** is the URL of your company’s public DNS domain namespace, which is always expressed as a wildcard, even if the Secure Channel SSL Certificate is a SAN certificate. + + +Here’s an example:00000003-0000-0ff1-ce00-000000000000/*..comIf the common name in your certificate is sharepoint.adventureworks.com, the syntax of the SPN will look like this:00000003-0000-0ff1-ce00-000000000000/*.adventureworks.comUsing a wildcard value lets SharePoint Online validate connections with *any host* in that domain. This is useful if you ever need to change the host name of the external endpoint (if your topology includes one) or if you want to change your SharePoint Server web application, in the future.To add the SPN to Azure Active Directory, enter the following commands in the Azure Active Directory Module for Windows PowerShell command prompt. + + +``` + +$msp = Get-MsolServicePrincipal -AppPrincipalId $spoappid +$spns = $msp.ServicePrincipalNames +$spns.Add("$spoappid/$spcn") +Set-MsolServicePrincipal -AppPrincipalId $spoappid -ServicePrincipalNames $spns +``` + +To validate that the SPN was set, enter the following commands in the Azure Active Directory Module for Windows PowerShell command prompt. + + +``` + +$msp = Get-MsolServicePrincipal -AppPrincipalId $spoappid +$spns = $msp.ServicePrincipalNames +$spns +``` + +You should see a current list of SPNs for SharePoint Online in your Office 365 tenancy, and one of the SPNs should include your public root domain name, prefaced by the SharePoint Online application principal ID. This registration is a wildcard registration and should look like the following example:00000003-0000-0ff1-ce00-000000000000/*..comThis should be the *only* SPN in the list that includes your public root domain name. +#### Step 4: Register the SharePoint Online application principal object ID with SharePoint Server + + +This step registers the SharePoint Online application principal object ID with the on-premises SharePoint Application Management Service, which allows SharePoint Server to authenticate to SharePoint Online using OAuth.From the PowerShell command prompt, type the following commands. + + +``` + +$spoappprincipalID = (Get-MsolServicePrincipal -ServicePrincipalName $spoappid).ObjectID +$sponameidentifier = "$spoappprincipalID@$spocontextID" +$appPrincipal = Register-SPAppPrincipal -site $site.rootweb -nameIdentifier $sponameidentifier -displayName "SharePoint Online" +``` + +To validate this step, from the PowerShell command prompt, type the $appPrincipal variable: + + +``` + +$appPrincipal | fl +``` + +The expected output is a description of the registered application principal with the name **SharePoint Online**, which should look something like this. + + + +![This figure illustrates the registered application principal for SharePoint Online](images/) + + + + + + + + + + + + +#### Step 5: Set the SharePoint authentication realm + + +This step sets the authentication realm of your SharePoint Server farm to the context ID of the organization’s Office 365 tenancy.From the PowerShell command prompt, type the following command. + + +``` +Set-SPAuthenticationRealm -realm $spocontextID +``` + +To validate this step, from the PowerShell command prompt, type the following commands. + + +``` +$spocontextID +``` + + + + +``` + Get-SPAuthenticationRealm +``` + +The output of each of these commands is the GUID that represents the context ID of the SharePoint Online tenancy. These GUIDs should be identical. +> [!IMPORTANT:] + + + + + + +#### Step 6: Configure an on-premises proxy for Azure Active Directory + + +In this step, you create an Azure Active Directory proxy service in the SharePoint Server farm. This enables Azure Active Directory as a *trusted token issuer* that SharePoint Server will use to sign and authenticate claims tokens from SharePoint Online.From the PowerShell command prompt, type the following commands. + + +``` + +New-SPAzureAccessControlServiceApplicationProxy -Name "ACS" -MetadataServiceEndpointUri $metadataEndpoint -DefaultProxyGroup +New-SPTrustedSecurityTokenIssuer -MetadataEndpoint $metadataEndpoint -IsTrustBroker:$true -Name "ACS" +``` + +To validate the **New-SPAzureAccessControlServiceApplicationProxy** command: +1. Browse the SharePoint 2016 Central Administration website, and click **Security** > **General Security** > **Manage trust**. + + +2. Make sure you have an entry with a name that begins with **ACS** and the type **Trusted Service Consumer**. + + +To validate this step, from the PowerShell command prompt, type the following command. + + +``` + +Get-SPTrustedSecurityTokenIssuer +``` + +The output that's expected is a description of the farm's trusted token issuer, where the value of the **RegisteredIssuerName** property is the following:00000001-0000-0000-c000-000000000000@where is the context ID of your SharePoint Online tenancy, which is the value in the $spocontextID variable. +## Validation and next steps + + + After finishing the tasks in this topic and its validation steps, you should check your SSO and Directory Synchronization setup by using the validation steps in [Validate your SSO configuration](#validatesso).So that you have a history of the steps you’ve taken, you should capture the entire contents of the PowerShell buffer into a file. This will be crucial if you need to reference your configuration history to troubleshoot, or for any other reasons. This will also help you pick up where you left off if the configuration spans multiple days or involves multiple people.After you have completed and validated the configuration tasks in this topic, continue with your [configuration roadmap](html/sharepoint-server-2016-hybrid-configuration-roadmaps.md). +# See also + +#### + + [Hybrid for SharePoint Server](html/hybrid-for-sharepoint-server.md) + + + + [Install and configure SharePoint Server hybrid](html/install-and-configure-sharepoint-server-hybrid.md) + + + + + + + + diff --git a/SharePoint/configure-services-and-service-applications-in-sharepoint-server.md b/SharePoint/configure-services-and-service-applications-in-sharepoint-server.md new file mode 100644 index 0000000000..9618281df4 --- /dev/null +++ b/SharePoint/configure-services-and-service-applications-in-sharepoint-server.md @@ -0,0 +1,15 @@ +--- +title: Configure services and service applications in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 2258fc12-68ad-4175-9735-812768a80093 +--- + + +# Configure services and service applications in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint 2013, SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-08-03* **Summary:** Learn how to configure services for SharePoint Server 2013 and SharePoint Server 2016.In SharePoint Server, you can configure individual services independently, and you can implement only the services that your organization needs.Deployed services are named *service applications* . A service application provides a resource that you can share across sites in a farm or sometimes across multiple farms, and users can access them through a hosting web application. Service applications are associated to web applications by *service application connections* . +## TechNet articles about how to configure services for SharePoint Server + +The following articles about how to configure services for SharePoint Server are available to view online. +### + +ContentDescription [Configure the Managed Metadata service](html/configure-the-managed-metadata-service.md)
Configure a Managed Metadata service application in SharePoint Server.
[Configure the Secure Store Service in SharePoint Server](html/configure-the-secure-store-service-in-sharepoint-server.md)
This article describes the SharePoint Server Secure Store Service operations that solution designers can use to create target applications that map user and group credentials to the credentials of external data sources.
[Configure a Business Data Connectivity service application in SharePoint Server](html/configure-a-business-data-connectivity-service-application-in-sharepoint-server.md)
Configure a service application for Business Connectivity Services in SharePoint Server.
**Visio Graphics Service administration in SharePoint Server 2013**
Learn how to create, configure, list, or delete Visio Services service applications by using Central Administration or Microsoft PowerShell.
[Configure PerformancePoint Services](html/configure-performancepoint-services.md)
Configure PerformancePoint Services in SharePoint Server before you make it available to users
diff --git a/SharePoint/configure-sharepoint-health-analyzer-rules-in-sharepoint-server.md b/SharePoint/configure-sharepoint-health-analyzer-rules-in-sharepoint-server.md new file mode 100644 index 0000000000..1d147aa126 --- /dev/null +++ b/SharePoint/configure-sharepoint-health-analyzer-rules-in-sharepoint-server.md @@ -0,0 +1,79 @@ +--- +title: Configure SharePoint Health Analyzer rules in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 937a136c-7cc1-4e61-8a2c-2161d484c13f +--- + + +# Configure SharePoint Health Analyzer rules in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-18* **Summary:** Learn to configure SharePoint Server 2016 and SharePoint Server 2013 Health Analyzer rules by using Central Administration. +## Before you begin + + +Because SharePoint Server runs as websites in Internet Information Services (IIS), administrators and users depend on the accessibility features that browsers provide. SharePoint Server supports the accessibility features of supported browsers. For more information, see the following resources: +- [Plan browser support](https://go.microsoft.com/fwlink/p/?LinkId=246502) + + +- [Accessibility features in SharePoint ](https://go.microsoft.com/fwlink/p/?LinkId=246501) + + +- [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504) + + +- [Touch](https://go.microsoft.com/fwlink/p/?LinkId=246506) + + + +## Configuring SharePoint Health Analyzer rules + + +You can accept the default settings for each health rule, or you can change settings for a health rule by using Central Administration. **To configure health rules by using Central Administration** +1. Verify that the user account performing this procedure is a member of the Farm Administrators group. + + + + +2. In Central Administration, on the home page, click **Monitoring**. + + +3. On the **Monitoring** page, under **Health Analyzer**, click **Review rule definitions**. + + +4. On the **Health Analyzer Rule Definitions** page, click the rule that you want to configure. + + +5. In the **Health Analyzer Rule Definitions** dialog, click **Edit Item**. + + +6. Edit one or more rule fields, and then click **Save**. + + To leave the rule unchanged, either dismiss the dialog or click **Cancel**. + + +Each health rule has configurable fields, which are described in the following table. +### Configurable fields for SharePoint Health Analyzer rules + +Configurable field Description Title
The name of the health rule. You can rename a health rule to clarify its functionality. The title is the name of the rule as it appears in the **Health Rule Definitions** list in Central Administration.
Changing the title does not affect how the rule runs.
Scope
You can set a health rule to run against all servers or any server. If set to any server, the rule will run on the first available server that the system encounters.
Schedule
You can schedule a health rule to run hourly, daily, weekly, monthly, or on demand only.
Enabled
You can select or clear this check box to enable or disable a health rule.
Repair Automatically
You can specify whether a health rule automatically attempts to repair errors that it finds. If this option is selected, SharePoint Server will repair errors as soon as they are found, as defined by the rule.
+> [!NOTE:] + + + + + +Version
Version history enables you to track the changes performed on each rule. The version number is updated every time that the rule is saved. The version number does not affect how the rule works.
Each health rule has read-only fields, which are described in the following table. +### Read-only fields for SharePoint Health Analyzer rules + +Read-only field Description Version
The current version number of the rule.
Created at
The date and time that the rule was originally created and the user account that created the rule.
Last modified at
The date and time that the rule was last changed and the user account that created the rule.
For more information about SharePoint Server monitoring configuration, see [Configure monitoring in SharePoint Server 2016](html/configure-monitoring-in-sharepoint-server-2016.md). +# See also + +#### + + [SharePoint Health Analyzer rules reference for SharePoint Server 2016](html/sharepoint-health-analyzer-rules-reference-for-sharepoint-server-2016.md) + + + + + + + + diff --git a/SharePoint/configure-sharepoint-health-analyzer-timer-jobs-in-sharepoint-server-2016.md b/SharePoint/configure-sharepoint-health-analyzer-timer-jobs-in-sharepoint-server-2016.md new file mode 100644 index 0000000000..90e040e632 --- /dev/null +++ b/SharePoint/configure-sharepoint-health-analyzer-timer-jobs-in-sharepoint-server-2016.md @@ -0,0 +1,146 @@ +--- +title: Configure SharePoint Health Analyzer timer jobs in SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 0fb9616f-3877-4ba8-a7a7-9f00b6d896cb +--- + + +# Configure SharePoint Health Analyzer timer jobs in SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-07-31* **Summary:** Learn to configure health data collection timer jobs by using the SharePoint Central Administration website or Windows PowerShell.SharePoint Health Analyzer uses timer jobs to collect health data and then writes the data to the logging folder and to the Logging database. This data is used in reports to display health of the farm servers. You can reschedule these timer jobs, run them immediately, or enable or disable them. On that page, you can also configure usage data collection, event selection, and usage data collection settings. For more information, see [Configure usage and health data collection in SharePoint Server](html/configure-usage-and-health-data-collection-in-sharepoint-server.md).In this article: +- [Use Central Administration to configure health data timer jobs](#section1) + + +- [Use Windows PowerShell to configure health data timer jobs](#section2) + + + +## Use Central Administration to configure health data collection timer jobs + + +You can use Central Administration to configure health data collection timer jobs. **To configure health data collection timer jobs by using Central Administration** +1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. + + > [!NOTE:] + +2. In Central Administration, on the home page, click **Monitoring**. + + +3. On the **Monitoring** page, in the **Reporting** section, click **Configure usage and health data collection**. + + +4. On the **Configure usage and health data collection** page, in the **Health Data Collection** section, click **Enable health data collection**. + + +5. In the **Health Data Collection** section, click **Health Logging Schedule**. The **Job Definitions** page opens. It lists all the timer jobs that collect health data. + + +6. On the **Job Definitions** page, click the timer job that you want to configure. + + +7. On the **Edit Timer Job** page, in the **Recurring Schedule** section, change the timer job schedule, and then click **OK**. + + + +## Use Windows PowerShell to configure health data collection timer jobs + + +You can configure the health data collection timer job schedule by using PowerShell. **To configure health data timer jobs by using Windows PowerShell** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running the PowerShell cmdlets. + + + - Add memberships that are required beyond the minimums above. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions. + + > [!NOTE:] + +2. On the **Start** menu, click **All Programs**. + + +3. Click **SharePoint 2016**. + + +4. Click **SharePoint 2016 Management Shell**. + + +5. At the PowerShell command prompt, type the following command: + + ``` + +Set-SPTimerJob -Identity -Schedule + ``` + + + The value of the **Identity** parameter specifies the timer job. If you do not use the **Identity** parameter, all timer jobs are configured. To see a list of all the timer jobs, type the following command: + + + + ``` + Get-SPTimerJob | Format-Table -property id,title + ``` + + + ** can be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a timer job (for example, TimerJob1); or an instance of a valid **SPTimerJob** object. + + Use the value of the **Schedule** parameter to specify the schedule, where ** is one of the following: + + - **Every 5 minutes between 0 and 59** + + + - **Hourly between 0 and 59** + + + - **Daily at 15:00:00** + + + - **Weekly between Fri 22:00:00 and Sun 06:00:00** + + + - **Monthly at 15 15:00:00** + + + - **Yearly at Jan 1 15:00:00** + + + + + + To see examples of timer job schedules, type the following command: + + + + ``` + Get-SPTimerJob | Format-Table -property id,title,schedule + ``` + +For more information, see **Get-SPTimerJob** and **Set-SPTimerJob**. +> [!NOTE:] + + + + + + +# See also + +#### + + [Overview of monitoring in SharePoint Server](html/overview-of-monitoring-in-sharepoint-server.md) + + + + + + + + diff --git a/SharePoint/configure-sharepoint-hybrid-auditing-in-sharepoint-2016-preview.md b/SharePoint/configure-sharepoint-hybrid-auditing-in-sharepoint-2016-preview.md new file mode 100644 index 0000000000..59911cce29 --- /dev/null +++ b/SharePoint/configure-sharepoint-hybrid-auditing-in-sharepoint-2016-preview.md @@ -0,0 +1,203 @@ +--- +title: Configure SharePoint Hybrid Auditing in SharePoint 2016 (Preview) +ms.prod: SHAREPOINT +ms.assetid: 86e0fc90-0ef8-4c22-9d3b-7af42bf882f1 +--- + + +# Configure SharePoint Hybrid Auditing in SharePoint 2016 (Preview) + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016, SharePoint Server 2016 Preview* * **Topic Last Modified:** 2017-05-30* Learn about how SharePoint 2016 Auditing generates reports for on-premises server users' file access logs for viewing in Office 365. +## Microsoft SharePoint Auditing (Preview) + +Microsoft SharePoint Hybrid Auditing is a new hybrid feature for SharePoint Server 2016 to help SharePoint administrators have visibility to user activities in their SharePoint environments. With this feature, SharePoint 2016 on-premise user activity logs can be uploaded to Office 365 and useful reports are generated. Configuration is simple and you can start viewing regularly updated reports in the Office 365 admin center.SharePoint Hybrid Auditing is currently in **Preview** mode: +- It is not recommended or supported to use this feature in production environments. + + +- No data completeness or latency SLA is guaranteed. + + +- As SharePoint Online is continually changing, may see differences between the audit events on SharePoint Online versus the ones from SharePoint Server (on-premises) + + + +## Prerequisites + +Before you configure the SharePoint Hybrid Auditing feature, ensure you are: +- A member of the Farm Administrators group  + + +- A service application administrator (Full Control) for the User Profile Service  + + +- An Office 365 Global Administrator or a SharePoint Online Administrator  + + +- Logged into Office 365 and SharePoint Server from a server in your SharePoint Server farm  + + +- Able to launch the Hybrid Picker as a Farm Administrator with elevated permissions  + + +The configuration of Hybrid Auditing uses the Hybrid Picker in the SharePoint Online admin center. Please read **Hybrid picker in the SharePoint Online admin center** to make sure you have met all the prerequisites before you configure the Hybrid Auditing feature. +## Part I: Turn On Audit Log Search Recording + + +1. Log in to your SharePoint Server 2016 on-premises as a Farm administrator. + + +2. Browse to your O365 online tenant admin website and login with your tenant admin username and password. + + +3. Select the app launcher icon + + + +![App launcher button](images/) + + + + in the upper left corner and choose **Admin**. + + +4. In the Office 365 Admin center, scroll down to Admin Centers select **Compliance**. + + +5. From the navigation pane, select **Search & investigation**, and then click **Audit log search**. + + +6. Under Audit log search, select **Start recording user and admin activities** link (if you have already performed this action, the link will not show up). + + +7. Click **Turn on**. + + ![Start recording user and admin activities](images/) + + + + +## Part II: Turn On SharePoint Hybrid Auditing + +Hybrid auditing uses the Hybrid Picker for configuration. Follow the steps in [Hybrid picker in the SharePoint Online admin center](https://go.microsoft.com/fwlink/?LinkID=537692). +## Part III: Check Audit Log Report + + +1. In the Office 365 Admin center, select **Compliance**. + + +2. In the Security & Compliance Center, click **Search & Investigation**. + + +3. Click **Audit Log Search**. + + +4. You can now start searching for on-premises auditing events in this same search UX alongside your Office365 auditing events. + + + +> [!NOTE:] +> You may need to wait approximately 30 minutes before on-premise auditing events show up in this display.> While SharePoint Hybrid Auditing is in preview mode, it is possible to have some missing auditing events.> Only a subset of the file activities is currently being uploaded from on-premises to Office 365. + + + + +To learn more about O365 Auditing log search and how to use filtering to get tailored results, see [Search the audit log in the Office 365 Security & Compliance Center](https://support.office.com/en-us/article/Search-the-audit-log-in-the-Office-365-Security-Compliance-Center-0d4d0f35-390b-4518-800e-0c7ec95e946c). +## How to turn off SharePoint Hybrid Auditing + +The SharePoint Hybrid Auditing feature uses the **Microsoft SharePoint Insights** service to upload activity logs to the O365. To discontinue uploading the logs to Office 365 you must stop the Microsoft SharePoint Insights service.Make sure you have SharePoint OnPrem Farm Administrator privilege and Local Administrator privilege in SharePoint OnPrem VM. + + + + + + + +Select one of the two following ways to stop the service in SharePoint 2016. **Stop the Insights Service using PowerShell** +1. Open **SharePoint 2016 Management Shell**. + + +2. Run the following cmdlet: + + + + + + ``` + +Add-PSSnapin Microsoft.SharePoint.PowerShell +(Get-SPService "Microsoft SharePoint Insights").Instances | Stop-SPServiceInstance + ``` + + **Stop the Insights Service in SharePoint Central Administration** +1. On the SharePoint Server 2016 Central Administration website, click System Settings. + + +2. On the System Settings page, in the Servers section, click **Manage services in this farm**. + + +3. Select **Microsoft SharePoint Insights** service, and then in the Action column click **Disable Auto Provision** + + +4. Click **OK**. + + ![Disable service in farm](images/) + + + +5. On the System Settings page, in the Servers section, click **Manage services on server**. + + +6. On the **Services on Server** page, switch server to each custom role server, and click **Stop** in the Action column. + + + +## What actions do I need to take after an In-Place-Upgrade? + +Microsoft SharePoint Insights service must be restarted after an in-place-upgrade. +1. Open "SharePoint 2016 Management Shell". + + +2. Run the following: + + ``` + +Add-PSSnapin Microsoft.SharePoint.PowerShell + +Stop-SPService -Identity "Microsoft SharePoint Insights" -IncludeCustomServerRole + +Start-SPService -Identity "Microsoft SharePoint Insights" -IncludeCustomServerRole + ``` + + +## What data/logs will be uploaded to Office 365? + +All the audit logs under the folder **SPUnifiedAuditEntry** are uploaded to Office 365 for generating reports. The location of the folder can be found in SharePoint 2016 Central Administration.For more information see [Search the audit log in the Office 365 Security & Compliance Center](https://support.office.com/en-us/article/Search-the-audit-log-in-the-Office-365-Security-Compliance-Center-0d4d0f35-390b-4518-800e-0c7ec95e946c) +1. On the SharePoint Server 2016 Central Administration website, click **Monitoring** under **Central Administration**. + + +2. In the **Reporting** section, click **Configure usage and health data collection**. + + +3. In the **Usage Data Collection Settings**, **Log file location** can be found as follows. + + ![Usage data collection file location](images/) + + + + +# See also + +#### + + [Search the audit log in the Office 365 Security & Compliance Center](https://support.office.com/en-us/article/Search-the-audit-log-in-the-Office-365-Security-Compliance-Center-0d4d0f35-390b-4518-800e-0c7ec95e946c) + + + + [TechNet Forums: Hybrid Auditing](https://social.technet.microsoft.com/Forums/office/en-US/home?forum=hybridauditing) + + + + + + + + diff --git a/SharePoint/configure-sharepoint-server-2016.md b/SharePoint/configure-sharepoint-server-2016.md new file mode 100644 index 0000000000..4b7c1241c1 --- /dev/null +++ b/SharePoint/configure-sharepoint-server-2016.md @@ -0,0 +1,15 @@ +--- +title: Configure SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 069bcdb5-f9bb-4346-8304-5be2f768e3dc +--- + + +# Configure SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-16* **Summary: ** Lists articles that describe how to configure settings (such as services, authentication, and specific features) after you install SharePoint Server 2016.After you install SharePoint Server 2016, you must configure several additional settings to enable key features in your farm. The articles in this section provide steps for configuring these settings. +## TechNet articles about how to configure settings for the server farm + +The following articles about how to configure settings for the server farm are available to view online. +### + +ContentDescription [Configure services and service applications in SharePoint Server](html/configure-services-and-service-applications-in-sharepoint-server.md)
These articles describe how to configure services and service applications.
[Configure My Sites and OneDrive for Business in SharePoint Server](html/configure-my-sites-and-onedrive-for-business-in-sharepoint-server.md)
Learn how to configure My Sites and OneDrive for Business in a SharePoint Server 2016 environment.
[Configure eDiscovery in SharePoint Server](html/configure-ediscovery-in-sharepoint-server.md)
Learn the steps to set up and configure eDiscovery in SharePoint Server 2016, Exchange Server 2016, and Exchange Server 2013.
[Configure enterprise search in SharePoint Server 2016](html/configure-enterprise-search-in-sharepoint-server-2016.md)
Learn how to configure the Search service application and set up a Search Center in SharePoint Server 2016.
[Manage the Distributed Cache service in SharePoint Server](html/manage-the-distributed-cache-service-in-sharepoint-server.md)
Learn how to configure and manage the Distributed Cache service in SharePoint Server 2016.
[Configure site mailboxes in SharePoint Server](html/configure-site-mailboxes-in-sharepoint-server.md)
Learn how to configure the Site Mailboxes feature in SharePoint Server 2016.
[Custom Tiles in SharePoint Server 2016](html/custom-tiles-in-sharepoint-server-2016.md)
Describes Custom Tiles, one of the new features in the November 2016 Public Update for SharePoint Server 2016 (Feature Pack 1).
[Configure availability and recovery solutions for SharePoint Server 2016](html/configure-availability-and-recovery-solutions-for-sharepoint-server-2016.md)
Learn about options for providing high availability and disaster recovery solutions for SharePoint Server 2016.
[Configure email integration for a SharePoint Server farm](html/configure-email-integration-for-a-sharepoint-server-farm.md)
Learn how to set up incoming and outgoing email in SharePoint Server 2016.
[Turn on automated document translation in SharePoint Server 2016](html/turn-on-automated-document-translation-in-sharepoint-server-2016.md)
Learn how to create and configure Machine Translation Service for SharePoint Server 2016.
diff --git a/SharePoint/configure-site-mailboxes-in-sharepoint-server.md b/SharePoint/configure-site-mailboxes-in-sharepoint-server.md new file mode 100644 index 0000000000..29f5bf9f45 --- /dev/null +++ b/SharePoint/configure-site-mailboxes-in-sharepoint-server.md @@ -0,0 +1,522 @@ +--- +title: Configure site mailboxes in SharePoint Server +ms.prod: SHAREPOINT +ms.assetid: 57b7618a-2ca4-450d-aa8b-77bce21a9884 +--- + + +# Configure site mailboxes in SharePoint Server + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** Exchange Server, SharePoint Server 2013, SharePoint Server 2016* * **Topic Last Modified:** 2017-07-18* **Summary:** Configure Exchange Server 2016, SharePoint Server 2016, and SharePoint Server 2013for team email by using the Site Mailboxes feature.This article describes how to configure Site Mailboxes in SharePoint Server and Exchange Server 2016. The Site Mailboxes feature provides SharePoint Server users with team email on a SharePoint Server site. Site Mailboxes also provides links to SharePoint Server document libraries in Outlook 2016, enabling users to share files and email messages with other members of a team that are working on a joint project. +## Before you begin + + +Before you begin this operation, review the following information about prerequisites: +- Site Mailboxes requires Exchange Server 2016. + + +- Any previous version of Exchange Web Services (EWS) will need to be uninstalled from the SharePoint Server servers. + + > [!NOTE:] + +- Site Mailboxes feature requires that user profile synchronization be configured in the farm. For information about configuring user profile synchronization, see [Plan user profiles and identities](html/plan-user-profiles-and-identities.md), and [Manage user profile synchronization in SharePoint Server](html/manage-user-profile-synchronization-in-sharepoint-server.md). + + +- Site Mailboxes feature requires that the app management service application be configured in the farm. For information about configuring the app management service application, see **New-SPAppManagementServiceApplication**. + + +- Secure Sockets Layer (SSL) configured for the Default Zone is a requirement for web applications that are deployed in scenarios that support server-to-server authentication and app authentication. This is such a scenario. As a prerequisite for configuring Site Mailboxes, the computer that is running SharePoint Server must have SSL configured. + + > [!NOTE:] + > Open Internet Explorer and navigate to Outlook Web App (if the deployment is on SharePoint Server) or the SSL SharePoint Server site (if the deployment is on Exchange Server): https:///owa or https://.> Accept to trust the certificate by clicking **Continue to website**.> Click **Certificate Error** info in Internet Explorer next to the Address bar, and then click **View Certificates**.> Select **Install Certificate** and then select **Place all certificates in the following store**.> Select the checkbox to show physical stores.> Install the certificate to Trusted Root Certification Authorities > Local Computer. +- In order to perform these procedures, you must be a member of the SharePoint and Exchange Server administrator groups and have an operational Exchange Server with end-user mailboxes. + + +- A SharePoint Server backup solution will not incorporate Exchange site mailboxes. An Exchange administrator will need to ensure timely backups of site mailboxes are taking place. + + +- Users who access files in a SharePoint Server document library from a Site Mailbox must have the document library configured as a trusted site in their browser or a warning will appear that asks the user if she or he wants to trust the file. + + + +## Configure SharePoint Server for Site Mailboxes in SharePoint Server + + +The first step in configuring Site Mailboxes is to install the Exchange Server Web Services API on each web and application server in the SharePoint Server farm. **Install Exchange Web Services API on SharePoint Server** +1. Download EWSManagedAPI.msi from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=42951) and save it to a folder on each web and application server. + + +2. Open a command window as administrator and navigate to the folder where you saved EWSManagedAPI.msi. + + +3. Run the following command: + + ``` + +msiexec /i EwsManagedApi.msi addlocal="ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac" + ``` + +4. Reset IIS from the command line by typing IISReset. + + + +## Establish OAuth Trust and Service Permissions on SharePoint Server + + +The next step is to copy the following two scripts. The first should be saved as Set-SiteMailboxConfig.ps1 and the second should be saved as Check-SiteMailboxConfig.ps1.Set-SiteMailboxConfig.ps1: + + +``` +# .SYNOPSIS +# +# Set-SiteMailboxConfig helps configure Site Mailboxes for a SharePoint farm +# +# .DESCRIPTION +# +# Establishes trust with an Exchange Server, sets Site Mailbox settings and enables Site Mailboxes for a farm. +# +# .PARAMETER ExchangeSiteMailboxDomain +# +# The FQDN of the Exchange Organization where Site Mailboxes will be created +# +# .PARAMETER ExchangeAutodiscoverDomain +# +# [Optional] The FQDN of an Exchange Autodiscover Virtual Directory +# +# .PARAMETER WebApplicationUrl +# +# [Optional] The URL of a specific web application to configure. If not specified all Web Applications will be configured +# +# .PARAMETER Force +# +# [Optional] Indicate that the script should ignore any configuration issues and enable Site Mailboxes anyway +# + +Param +( + [Parameter(Mandatory=$true)] + [ValidateNotNullOrEmpty()] + [string]$ExchangeSiteMailboxDomain, + [Parameter(Mandatory=$false)] + [ValidateNotNullOrEmpty()] + [string]$ExchangeAutodiscoverDomain, + [Parameter(Mandatory=$false)] + [ValidateNotNullOrEmpty()] + [string]$WebApplicationUrl, + [Parameter(Mandatory=$false)] + [switch]$Force +) + +$script:currentDirectory = Split-Path $MyInvocation.MyCommand.Path + +if($WebApplicationUrl -ne $NULL -and $WebApplicationUrl -ne "") +{ + $webapps = Get-SPWebApplication $WebApplicationUrl +} +else +{ + $webapps = Get-SPWebApplication +} + +if($webapps -eq $NULL) +{ + if($WebApplicationUrl -ne $NULL) + { + Write-Warning "No Web Application Found at $($WebApplicationUrl). Please create a web application and re-run Set-SiteMailboxConfig" + } + else + { + Write-Warning "No Web Applications Found. Please create a web application and re-run Set-SiteMailboxConfig" + } + + return +} + +$rootWeb = $NULL + +foreach($webapp in $webapps) +{ + if($rootWeb -eq $NULL) + { + $rootWeb = Get-SPWeb $webApp.Url -EA SilentlyContinue + } +} + +if($rootWeb -eq $NULL) +{ + Write-Warning "Unable to find a root site collection. Please create a root site collection on a web application and re-run Set-SiteMailboxConfig" + return +} + +$exchangeServer = $ExchangeAutodiscoverDomain + +if($exchangeServer -eq $NULL -or $exchangeServer -eq "") +{ + $exchangeServer = "autodiscover.$($ExchangeSiteMailboxDomain)" +} + +Write-Host "Establishing Trust with Exchange Server: $($exchangeServer)" + +$metadataEndpoint = "https://$($exchangeServer)/autodiscover/metadata/json/1" + +$exchange = Get-SPTrustedSecurityTokenIssuer | Where-Object { $_.MetadataEndpoint -eq $metadataEndpoint } + +if($exchange -eq $NULL) +{ + $exchange = New-SPTrustedSecurityTokenIssuer -Name $exchangeServer -MetadataEndPoint $metadataEndpoint +} + +if($exchange -eq $NULL) +{ + Write-Warning "Unable to establish trust with Exchange Server $($exchangeServer). Ensure that $($metadataEndpoint) is accessible." + + if($ExchangeAutodiscoverDomain -eq $NULL -or $ExchangeAutodiscoverDomain -eq "") + { + Write-Warning "If $($metadataEndpoint) does not exist you may specify an alternate FQDN using ExchangeAutodiscoverDomain." + } + return +} + +Write-Host "Granting Permissions to Exchange Server: $($exchangeServer)" +$appPrincipal = Get-SPAppPrincipal -Site $rootWeb.Url -NameIdentifier $exchange.NameId +Set-SPAppPrincipalPermission -AppPrincipal $appPrincipal -Site $rootWeb -Scope SiteSubscription -Right FullControl -EnableAppOnlyPolicy + +Write-Host +Write-Host + +Write-Host "Verifying Site Mailbox Configuration" +$warnings = & $script:currentDirectory\\Check-SiteMailboxConfig.ps1 -ReturnWarningState + +if($warnings -and -not $Force) +{ + Write-Warning "Pre-requisites not satisfied. Stopping Set-SiteMailboxConfig. Use -Force to override" + return +} +elseif($warnings) +{ + Write-Warning "Pre-requisites not satisfied. -Force used to override" +} + +foreach($webapp in $webapps) +{ + Write-Host "Configuring Web Application: $($webapp.Url)" + Write-Host "Setting Exchange Site Mailbox Domain to $($ExchangeSiteMailboxDomain)" + $webapp.Properties["ExchangeTeamMailboxDomain"] = $ExchangeSiteMailboxDomain + + if($ExchangeAutodiscoverDomain -ne $NULL -and $ExchangeAutodiscoverDomain -ne "") + { + Write-Host "Setting Exchange Autodiscover Domain to $($ExchangeAutodiscoverDomain)" + $webapp.Properties["ExchangeAutodiscoverDomain"] = $ExchangeAutodiscoverDomain; + } + + $webapp.Update() +} + +$feature = Get-SPFeature CollaborationMailboxFarm -Farm -ErrorAction Ignore + +if($feature -eq $NULL) +{ + Write-Host "Enabling Site Mailboxes for Farm" + Enable-SPFeature CollaborationMailboxFarm +} +else +{ + Write-Host "Site Mailboxes already enabled for Farm" +} +``` + +Check-SiteMailboxConfig.ps1: + + +``` + +Param +( + [Parameter(Mandatory=$false)] + [ValidateNotNullOrEmpty()] + [switch]$ReturnWarningState +) + +Add-PSSnapin Microsoft.SharePoint.Powershell + +$anyWarnings = $false + +Write-Host "Step 1: Checking for Exchange Web Services" + +try +{ + $assm = [System.Reflection.Assembly]::Load("Microsoft.Exchange.WebServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35") + if($assm.GlobalAssemblyCache) + { + Write-Host -Foreground Green "Found Exchange Web Services in Global Assembly Cache" + Write-Host "Exchange Web Services Version: $([System.Diagnostics.FileVersionInfo]::GetVersionInfo($assm.Location).FileVersion)" + } + else + { + Write-Warning "Unable to find Exchange Web Services in Global Assembly Cache" + $anyWarnings = $true + } +} +catch +{ + Write-Warning "Unable to find Exchange Web Services in Global Assembly Cache" + $anyWarnings = $true +} + + +Write-Host +Write-Host + +Write-Host "Step 2: Checking for https web application" + +$webapps = Get-SPWebApplication -EA SilentlyContinue + +$rootWeb = $NULL + +if($webapps -ne $NULL) +{ + $sslWebAppExists = $false + foreach($webapp in $webapps) + { + if($rootWeb -eq $NULL) + { + $rootWeb = Get-SPWeb $webApp.Url -EA SilentlyContinue + } + + if(-not $webapp.Url.StartsWith("https://")) + { + Write-Warning "Web Application at $($webapp.Url) does not use HTTPS. Site Mailboxes will not work on this Web Application." + } + else + { + $sslWebAppExists = $true + Write-Host -Foreground Green "Found Web Application at $($webapp.Url) that uses HTTPS" + } + } + + if(-not $sslWebAppExists) + { + Write-Warning "At least one Web Application must be configured for HTTPS in the default zone." + $anyWarnings = $true + } +} +else +{ + Write-Warning "No Web Applications Found. Please create a web application and re-run Check-SiteMailboxConfig" + $anyWarnings = $true + if($ReturnWarningState) + { + return $anyWarnings + } + return; +} + +if($rootWeb -eq $NULL) +{ + Write-Warning "Unable to find any Sites. Please create a root site collection on a web application and re-run Check-SiteMailboxConfig" + $anyWarnings = $true + if($ReturnWarningState) + { + return $anyWarnings + } + return; +} + +# Get App Permissions Management Objects +$appPrincipalManager = [Microsoft.SharePoint.SPAppPrincipalManager]::GetManager($rootWeb) +$appPrincipalPermissionsManager = New-Object -TypeName Microsoft.SharePoint.SPAppPrincipalPermissionsManager -ArgumentList $rootWeb + +Write-Host +Write-Host +Write-Host "Step 3: Checking for trusted Exchange Servers" + +$trustedIssuers = Get-SPTrustedSecurityTokenIssuer +$trustedIssuerHosts = @() + +if($trustedIssuers -ne $NULL) +{ + $foundTrustedIssuer = $false + foreach($trustedIssuer in $trustedIssuers) + { + if($trustedIssuer.RegisteredIssuerName.StartsWith("00000002-0000-0ff1-ce00-000000000000@")) + { + if($trustedIssuer.IsSelfIssuer) + { + $foundTrustedIssuer = $true + + $uri = New-Object -TypeName System.Uri -ArgumentList $trustedIssuer.MetadataEndPoint + + Write-Host -Foreground Green "Found trusted Exchange Server at $($uri.Host)" + $appPrincipalName = [Microsoft.SharePoint.SPAppPrincipalName]::CreateFromNameIdentifier($trustedIssuer.RegisteredIssuerName) + $appPrincipal = $appPrincipalManager.LookupAppPrincipal([Microsoft.SharePoint.SPAppPrincipalIdentityProvider]::External, $appPrincipalName); + + + + if($appPrincipal -ne $NULL) + { + $isValidAppPrincipal = $true; + + if($appPrincipalPermissionsManager.GetAppPrincipalSiteSubscriptionContentPermission($appPrincipal) -eq [Microsoft.SharePoint.SPAppPrincipalPermissionKind]::FullControl) + { + Write-Host -Foreground Green "Exchange Server at $($uri.Host) has Full Control permissions" + + } + else + { + Write-Warning "Exchange Server at $($uri.Host) does not have Full Control permissions" + $isValidAppPrincipal = $false; + $anyWarnings = $true + } + + if($appPrincipalPermissionsManager.IsAppOnlyPolicyAllowed($appPrincipal)) + { + Write-Host -Foreground Green "Exchange Server at $($uri.Host) has App Only Permissions" + } + else + { + Write-Warning "Exchange Server at $($uri.Host) does not have App Only Permissions" + $isValidAppPrincipal = $false; + $anyWarnings = $true + } + + if($isValidAppPrincipal) + { + $trustedIssuerHosts += $uri.Host + } + + } + else + { + Write-Warning "Unable to get App Principal for $($uri.Host). Unable to check permissions for this Exchange Server" + $anyWarnings = $true + } + } + else + { + Write-Warning "Found trusted Exchange Server at $($uri.Host) but it is not a Self Issuer" + $anyWarnings = $true + } + } + } + + if(-not $foundTrustedIssuer) + { + Write-Warning "Unable to find any trusted Exchange Servers" + $anyWarnings = $true + } +} +else +{ + Write-Warning "Unable to find any trusted Exchange Servers" + $anyWarnings = $true +} + +Write-Host +Write-Host +Write-Host "Step 4: Report current Site Mailbox Configuration" + +if($webapps -ne $NULL) +{ + foreach($webapp in $webapps) + { + Write-Host + Write-Host "Web Application Site Mailbox Configuration: $($webapp.Url)" + Write-Host "Exchange Site Mailbox Domain: $($webapp.Properties["ExchangeTeamMailboxDomain"])" + + if($webapp.Properties["ExchangeAutodiscoverDomain"] -ne $NULL) + { + Write-Host "Exchange Autodiscover Domain: $($webapp.Properties["ExchangeAutodiscoverDomain"])" + } + } +} + +Write-Host +Write-Host "Trusted Exchange Services: $([String]::Join(", ", $trustedIssuerHosts))" + +$feature = Get-SPFeature CollaborationMailboxFarm -Farm -ErrorAction Ignore + +if($feature -eq $NULL) +{ + Write-Host -ForegroundColor Red "Site Mailboxes are NOT enabled for Farm" +} +else +{ + Write-Host -ForegroundColor Green "Site Mailboxes are enabled for Farm" +} + +if($ReturnWarningState) +{ + return $anyWarnings +} +``` + +Save the two .ps1 files to the same folder on a SharePoint ServerFront-end or Application server, as one script calls the other during execution. In a Windows PowerShell window (right-click the PowerShell icon and choose **Run As Administrator** to open), navigate to the folder containing the .ps1 files and run the Set-SiteMailboxConfig.ps1 script. This allows users to do the following: +- Retrieve and install the Exchange metadata, giving the Exchange service principal full control permissions to the SharePoint Server site subscription + + +- Enable the site mailbox feature in the SharePoint Server environment + + +- (optional) Set the Exchange site mailbox target domain, if DNS for the domain hasn't been configured for AutoDiscover + + +The Check-SiteMailboxConfig.ps1 is called as part of the Set-SiteMailboxConfig script, and it confirms that the configuration has been successful (it can also be run separately).The format should be as follows:.\\Set-SiteMailboxConfig.ps1 -ExchangeSiteMailboxDomain -ExchangeAutodiscoverDomain [Exchange Server] -WebApplicationUrl [URL]Where equals the FQDN of the domain your Exchange Server is in, and is the Exchange Server that you intend to connect to. This is a required parameter.Optional parameters are [Exchange Server], which is the Exchange Server you intend to connect to (this is needed if Autodiscover is not enabled or properly configured) and [URL], which would be a specific URL that you may be configuring (typically used in an environment with SSL and non-SSL web applications). +> Example: + + +> .\\Set-SiteMailboxConfig.ps1 -ExchangeSiteMailboxDomain tailspintoys.com -ExchangeAutodiscoverDomain exchange1.tailspintoys.com -WebApplicationUrl https://tailspintoys.com + +If you encounter an error while running the script, refer to the "Troubleshooting" section in this article for guidance. +## Configure Exchange Server 2016 for Site Mailboxes + + +The final step is to establish OAuth trust, and service permissions, on the Exchange server. **Establish OAuth Trust and Service Permission on Exchange** +1. On your instance of Exchange Server open the Exchange Management PowerShell window as Administrator and change to the "C:\\Program Files\\Microsoft\\Exchange Server\\V16\\Scripts" directory. + + +2. Run the following command: + + ``` + +.\\Configure-EnterprisePartnerApplication.ps1 -ApplicationType Sharepoint -AuthMetadataUrl https:///_layouts/16/metadata/json/1 + ``` + + + Where is the URL to the SharePoint SSL root site collection that you want to configure. + + + +## Troubleshooting + + +Please review the following table if you encounter issues. +### Table of error codes for reference when you run a configuration checklist script + +Error Code Error Notes 0
NoError
Review Prerequisites.
1
ExchangeClientNotAvailable
EWS client was not found on the SharePoint Server WFE. Run the Check script and ensure the entries are properly in the GAC; you may need to reinstall the EWS client.
2
UnsupportedVersion
EWS client version is incompatible with SharePoint Server. Run the Check script to ensure the version meets minimum requirements. Alternatively, the Exchange server may be 2010 or earlier.
3
InvalidUser
The TeamMailboxDomain parameter is not a valid FQDN or SMTP address.
4
UnauthorizedUser
The script received a 401 from the Exchange Server, review the Exchange setup steps.
5
ServerBusy
Exchange timed out during AutoDiscovery. It should be intermittent, please retry, but if it is persistent, follow-up with the Exchange Administrator.
6
URLNotAvailable
AutoDiscovery failed to return a URL for ECP/OWA, which means typically that the EWS client version is incompatible with SharePoint Server. It may also mean Site Mailboxes are not enabled on Exchange, which would require follow-up with the Exchange Administrator.
7
OAuthNotSupported
Unsuccessful in generating an OAuth token on behalf of SharePoint Server. This is typically caused by claims-based authentication being disabled on the SharePoint Server web application.
8
OAuthException
An error occurred during the OAuth handshake between SharePoint Server and Exchange. This is typically caused by server to server configuration issues, such as a realm value mismatch on either side, certificate issues for Exchange or SharePoint Server, etc. Review certificates and attempt to establish or reestablish trust.
9
InvalidAutodiscoverDomain
The AutoDiscover domain property is not set to a valid FQDN.
10
UnknownError
An unknown error condition has occurred. Run the Check script and confirm that a valid, trusted instance of SharePoint Server is available, review prerequisites, confirm AutoDiscover has been set-up properly with the Exchange Administrator.
101
OAuthNotSupportedOverHttp
If this error is thrown, your web application’s default zone is not set to SSL, and AllowOauthoverHttp is also set to false. Run the Check script to ensure that any web application you intend to host site mailboxes are set with SSL in the default zone, as outlined in the prerequisites.
102
AssociatedOwnersGroupNull
One or both of the default Owners and Members groups for the site have been deleted. Each of these two default groups are required to exist on any site where users install site mailboxes. A site administrator should be able to direct a site owner to recreated these required groups.
103
ExchangeTeamMailboxDomainNotSet
The ExchangeTeamMailboxDomain property has not been set.
104
ExchangeAppPrincipalNotFound
No Exchange app principals were found to be trusted. Typically, this means the New-SPTrustedSecureTokenService step was missed. Run the Check script and ensure that the app principal URL(s) outputted are the correct one(s).
105
ExchangeAppPrincipalMissingPermissions
The Exchange app principal being connected to doesn’t have the right permissions on the SharePoint Server farm. Run the Check script and ensure that the Exchange app principal has the required permissions on the farm.
+# See also + +#### + + [Plan email integration for a SharePoint Server 2016 farm](html/plan-email-integration-for-a-sharepoint-server-2016-farm.md) + + + + [Configure email integration for a SharePoint Server farm](html/configure-email-integration-for-a-sharepoint-server-farm.md) + + + + +#### + + [Site mailboxes](https://technet.microsoft.com/en-us/library/mt577268%28v=exchg.160%29.aspx) + + + + [Collaboration](https://technet.microsoft.com/en-us/library/mt577263%28v=exchg.160%29.aspx) + + + + + + + + diff --git a/SharePoint/configure-sql-server-alwayson-availability-groups-for-sharepoint-server-2016.md b/SharePoint/configure-sql-server-alwayson-availability-groups-for-sharepoint-server-2016.md new file mode 100644 index 0000000000..7519e2a0d6 --- /dev/null +++ b/SharePoint/configure-sql-server-alwayson-availability-groups-for-sharepoint-server-2016.md @@ -0,0 +1,557 @@ +--- +title: Configure SQL Server AlwaysOn Availability Groups for SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 18fedf59-f293-4c15-953e-c42ec66fa13f +--- + + +# Configure SQL Server AlwaysOn Availability Groups for SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:**  Learn how to create and configure a SQL Server 2014 with Service Pack 1 (SP1) or SQL Server 2016 Always On Availability Group for a SharePoint Server 2016 farm.This article provides the required information and detailed procedures to create and configure a Microsoft SQL Server 2014 (SP1) or Microsoft SQL Server 2016 Always On Availability Group for a SharePoint Server 2016 farm. +> [!IMPORTANT:] + + + + + +In this article: +- [Process overview](#overview) + + +- [Before you begin](#begin) + + +- [Detailed steps to configure an AlwaysOn Availability Group for SharePoint ](#SPscenario) + + +- [Use failover tests to validate the AlwaysOn installation](#Testfailover) + + +- [Monitor the AlwaysOn environment](#Monitor) + + + +## Process overview + + +We recommend following the installation and configuration steps in the order shown to deploy a SharePoint farm that uses an Always On availability group: +- Select or create a Windows Server failover cluster. + + +- Install SQL Server 2014 (SP1) or SQL Server 2016 on each cluster node. + + +- Create and configure an availability group. + + +- Install and configure SharePoint Server 2016. + + +- Add the SharePoint databases to the availability group. + + +- Test failover for the availability group. + + + +## Before you begin + + +Before you begin deployment, review the following information about SQL Server Always On, the technologies that support Always On, and SharePoint Server 2016: +- Knowledge and skill requirements + + +- Always On Availability Group concepts + + +- Hardware and software requirements + + +- Permissions + + + +## Knowledge and skill requirements + +To implement SQL Server Always On Availability Groups as a high availability and disaster recovery solution, several technologies interact and have to be installed and configured correctly. We recommend that the team responsible for setting up an Always On environment for SharePoint products has a working knowledge of, and hands-on skills with the following technologies: +- Windows Server Failover Clustering (WSFC) services + + +- SQL Server 2014 (SP1) or SQL Server 2016 + + +- SharePoint Server 2016 + + + +## SQL Server Always On Availability Group concepts + +An availability group consists of the following components: +- Replicas, which are a discrete set of user databases called availability databases that fail over together as a single unit. Every availability group in SQL Server 2014 (SP1) and SQL Server 2016 supports one primary replica and up to eight secondary replicas. + + +- A specific instance of SQL Server to host each replica and to maintain a local copy of each database that belongs to the availability group. + + + [Always On Availability Groups (SQL Server)](https://technet.microsoft.com/en-us/library/hh510230.aspx) and [Overview of Always On Availability Groups (SQL Server)](https://technet.microsoft.com/en-us/library/ff877884%28v=sql.130%29.aspx) **Replicas and failover**The primary replica makes the availability databases available for read-write connections from clients and sends transaction log records for each primary database to every secondary replica. Each secondary replica applies transaction log records to its secondary databases.All replicas can run under asynchronous-commit mode, or up to three of them can run under synchronous-commit mode. For more information about synchronous and asynchronous commit mode, see [Availability Modes (AlwaysOn Availability Groups)](https://msdn.microsoft.com/en-us/library/ff877931%28v=sql.130%29.aspx). +> [!NOTE:] + + + + + +Read the following articles to learn important concepts about SQL Server Always On technology: +- For details about the benefits of Always On Availability Groups and an overview of Always On Availability Groups terms, see [AlwaysOn Availability Groups (SQL Server)](https://technet.microsoft.com/en-us/library/hh510230%28v=sql.130%29.aspx). + + +- For detailed information about prerequisites, see [Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)](https://technet.microsoft.com/en-us/library/ff878487.aspx). + + + +## Windows Server Failover Clustering + +To create and use SQL Server 2014 (SP1) or SQL Server 2016 Always On Availability Groups, you have to install both SQL Server versions on a Windows Server Failover Clustering (WSFC) cluster. For more information, see [Windows Server Failover Clustering (WSFC) with SQL Server](http://go.microsoft.com/fwlink/?LinkID=626888&clcid=0x409) and for SQL Server 2016, [Windows Server Failover Clustering (WSFC) with SQL Server](https://msdn.microsoft.com/en-us/library/hh270278%28v=sql.130%29.aspx).Although configuring a WSFC cluster is out of the scope for this article, you should be aware of the following requirements before you install and configure a cluster: +- All the cluster nodes must be in the same Active Directory Domain Services (AD DS) domain. + + +- Each availability replica in an availability group must reside on a different node of the same Windows Server Failover Clustering (WSFC) cluster. + + +- The cluster creator must have the following accounts and permissions: + + - Have a domain account in the domain where the cluster will exist. + + + - Have local administrator permissions on each cluster node. + + + - Have **Create Computer objects** and **Read All Properties** permissions in AD DS. For more information, see [Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory](https://go.microsoft.com/fwlink/p/?LinkId=213267) and [How to Create a Cluster in a Restrictive Active Directory Environment](http://go.microsoft.com/fwlink/?LinkID=786442&clcid=0x409). + + +A very important aspect of configuring failover clustering and Always On is determining the quorum votes that are needed for the cluster nodes.Failover clustering is based on a voting algorithm where more than one half of the voters, or quorum, must be online and able to communicate with each other. Because a given cluster has a specific number of nodes and a specific quorum configuration, the cluster service is able to determine what constitutes a quorum. The cluster service will stop on all the nodes if the number of voters drops below the required majority.For more information, see [WSFC Quorum Modes and Voting Configuration (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=723838&clcid=0x409) and [Configure Cluster Quorum NodeWeight Settings](http://go.microsoft.com/fwlink/?LinkID=723839&clcid=0x409). +## SharePoint Server 2016 + +Some SharePoint Server 2016 databases do not support SQL Server Always On Availability Groups. We recommend that you review [Supported high availability and disaster recovery options for SharePoint databases](html/supported-high-availability-and-disaster-recovery-options-for-sharepoint-databas.md) before you configure an Always On environment. You should also review [Hardware and software requirements for SharePoint Server 2016](html/hardware-and-software-requirements-for-sharepoint-server-2016.md). +## Detailed steps to configure an Always On Availability Group for SharePoint + + +The following illustration shows a SharePoint Server 2016 farm (SPHA_farm) that uses an availability group named SP_AG1. We'll use SPHA_farm as reference example in our steps to configure Always On. + + + +![A SharePoint Server 2016 farm that uses an AlwaysOn Availability Group](images/) + + + + + + + + + + + + +## Prepare the Windows Server cluster environment + +Obtain access to or create a three node Windows Server Failover Clustering (WSFC) cluster that you can use to install SQL Server 2014 (SP1) or SQL Server 2016 on each cluster node. For information and detailed steps to configure a Windows Server 2012 R2 failover cluster, see [Failover Clustering Overview](http://go.microsoft.com/fwlink/?LinkID=724032&clcid=0x409). +## Prepare the SQL Server environment + + +Before you can create an Availability Group for SharePoint Server 2016, you must prepare the SQL Server 2014 (SP1) or SQL Server 2016 environment. +> [!NOTE:] +> [Hardware and software requirements for SharePoint Server 2016](html/hardware-and-software-requirements-for-sharepoint-server-2016.md)> [Install and configure SharePoint Server 2016](html/install-and-configure-sharepoint-server-2016.md)> [Configure SQL Server security for SharePoint Server 2016](html/configure-sql-server-security-for-sharepoint-server-2016.md) + + + + +To prepare the environment, complete the following tasks: +- Install the SQL Server prerequisites. + + +- Install SQL Server 2014 (SP1) or SQL Server 2016. + + +- Enable Always On. + + + +#### Install SQL Server 2014 (SP1) + +Use the following procedure to install SQL Server 2014 (SP1). **To install SQL Server 2014 (SP1)** +1. Install SQL Server 2014 (SP1) prerequisites on each cluster node. + + For more information, see [Hardware and Software Requirements for Installing SQL Server 2014](http://go.microsoft.com/fwlink/?LinkID=799531&clcid=0x409) and [Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=718033&clcid=0x409). + + +2. Install SQL Server on each cluster node. + + For more information, see [Quick-Start Installation of SQL Server 2014](http://go.microsoft.com/fwlink/?LinkID=723753&clcid=0x409) and [Installing SQL Server 2014 Step by Step Tutorial](http://go.microsoft.com/fwlink/?LinkID=724036&clcid=0x409). + + + +#### Install SQL Server 2016 + +Use the following procedure to install SQL Server 2016. **To install SQL Server 2016** +1. Install SQL Server 2016 prerequisites on each cluster node. + + For more information, see [Install SQL Server 2016](http://go.microsoft.com/fwlink/?LinkID=735052&clcid=0x409). + + +2. Install SQL Server 2016 on each cluster node. + + For more information, see [SQL Server Failover Cluster Installation](https://technet.microsoft.com/en-us/library/hh231721.aspx). + + + +#### Enable Always On + +You must enable Always On for each database server in the cluster. +> [!NOTE:] + + + + + + **To enable Always On** +1. Your logon account must have the permission levels to create an availability group. The account must have membership in the **db_owner** fixed database role and either CREATE AVAILABILITY GROUP server permission, CONTROL AVAILABILITY GROUP permission, ALTER ANY AVAILABILITY GROUP permission, or CONTROL SERVER permission. + + +2. Log on to the server that will host the primary replica and start SQL ServerConfiguration Manager. + + +3. In Object Explorer, select **SQL Server Services**, right-click **SQL Server (** ** **)**, where ** is the name of a local server instance for which you want to enable Always On Availability Groups, and then click **Properties**. + + +4. Select the **AlwaysOn High Availability** tab. + + +5. Select the **Enable AlwaysOn Availability Groups** check box, and then click **OK**. + + +6. Although the change is saved you must manually restart the SQL Server service (MSSQLSERVER) to commit the change. The manual restart enables you to choose a restart time that is best for your business requirements. + + +7. Repeat the previous steps to enable Always On for SQL Server on the other cluster nodes. + + +For more information, see [Enable and Disable AlwaysOn Availability Groups (SQL Server)](https://technet.microsoft.com/en-us/library/ff878259%28v=sql.130%29.aspx). +## Create and configure the availability group + + +Depending on the SQL Server 2014 (SP1) or SQL Server 2016 environment where you plan to create the Availability Group, you might have to create a temporary database to use before you create the Availability Group. The process that creates an availability group requires you to provide a name for the availability group and then select an eligible user database on the connected server instance as an availability database. +> [!NOTE:] + + + + + +If there are no user databases on the instance of the connected server, which is the case in our example, you need to create one. Use the following procedure to create a temporary user database that will be a temporary primary replica for the group. **To create a temporary user database** +1. Make sure that your logon account has the correct permissions for this task. You require one of the following permissions in the master database to create the new database: + + - CREATE DATABASE + + + - CREATE ANY DATABASE + + + - ALTER ANY DATABASE + + +2. Log on to the server that will host the primary replica, which is SP-SRV1 in our example. + + +3. Start Management Studio. + + +4. In Object Explorer, right-click **Databases** and then click **New Database**. + + +5. In the New Database dialog box, type the **Database name:**, which is "TemporaryUserDB" for this example. + + Because this is a temporary database that you delete after you create the availability group, you can use the default settings. Click **OK**. + + Because the New Availability Group Wizard will not create an availability group unless the user database was backed up, you have to back up the temporary database. + + +6. In Object Explorer expand **Databases** and right-click the temporary database that you just created. Pick **Tasks** and then choose **Back Up**. + + +7. In the **Back Up Database** dialog box, click **OK** to accept all the default settings and create the back up. + + + +#### About replicas and data synchronization + +You should be familiar with the following information about replicas and data synchronization before creating and configuring the availability groups for your SharePoint farm. **About replicas**Every availability replica is assigned an initial role—either the primary role or the secondary role, which the availability databases of that replica inherit. The role of a given replica determines whether it hosts read-write databases or read-only databases, the type of failover and whether it uses synchronous commit or asynchronous commit. +> [!NOTE:] + + + + + +The following table shows the information that you have to provide for each replica, either when you first create the availability group, or when you add secondary replicas. +### Replica configuration requirements + +Replica information Description **Server Instance**
Displays the name of the instance of the server that will host the availability replica.
**Initial Role**
Indicates the role that the new replica will first perform: Primary or Secondary.
**Automatic Failover (Up to 2)**
Indicates the type of failover that the replica uses: automatic or manual.
**Synchronous Commit (Up to 3)**
Indicates the type of commit that is used for the replica.
**Readable Secondary**
Indicates whether a secondary replica can be read.
The configuration options are unavailable for read access, read-only, and read-only intent. For more information, see [Active Secondaries: Readable Secondary Replicas (AlwaysOn Availability Groups)](http://go.microsoft.com/fwlink/?LinkID=724041&clcid=0x40b) and [Configure Read-Only Access on an Availability Replica (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=626915&clcid=0x409).
+> [!NOTE:] + + + + + + +> [!NOTE:] + + + + + + **Data synchronization**As part of the availability group creation process, you have to make an exact copy of the data on the primary replica and install the copy on the secondary replica. This is the initial data synchronization for the Availability Group. For more information, see [Select Initial Data Synchronization Page (AlwaysOn Availability Group Wizards)](http://go.microsoft.com/fwlink/?LinkID=691235&clcid=0x409).A network share must exist and must be accessed by all the nodes in the Always On configuration to do the initial data synchronization between all the cluster nodes that host a replica. For more information, see [Network Shares Extension](https://go.microsoft.com/fwlink/p/?LinkId=245722) and [File and Storage Services Overview](http://go.microsoft.com/fwlink/?LinkID=724044&clcid=0x).The following restrictions exist when you use the New Availability Group wizard to start data synchronization: +- If the file paths on the secondary replica location differ from the file paths on the primary location, you have to start data synchronization manually. + + +- If any secondary database exists on a secondary replica, you have to manually delete the secondary databases before you start data synchronization in the New Availability Group. However, if you want to use existing secondary databases, exit the New Availability Group wizard and start data synchronization manually. + + +- To use the availability group wizard to synchronize data, you have to have a backup share that all the replicas can write to. You can specify the share by browsing to it or by entering its fully qualified universal naming convention (UNC) path name, \\\\Systemname\\ShareName\\Path\\, in the **Specify a shared network location accessible by all replicas** box. + + +For each database in the availability group, the **Start Data Synchronization** page shows the progress of the following operations: +- Creating a full database backup of the primary database on the network share. + + +- Restoring these backups to the secondary replica location. + + These restore operations both use RESTORE WITH NORECOVERY option and leave the new secondary database in the RESTORING state. + + +- Joining the secondary database to the availability group. + + This step puts the secondary database in the ONLINE state and starts data synchronization for this database. + + + **Login replication**SharePoint logins that are created by using the same approach as in previous releases of SQL Server are not replicated in an availability group. This occurs because login information is stored in the MasterDB database, which is not replicated. Although the farm accounts are created when replicas are synchronized, login information is not available after a failover.If you have already created an availability group and synchronized the primary and secondary replicas, the workaround is to manually copy the logins from the primary replica to the secondary replicas.SQL Server 2012 introduced the concept of *Users with Passwords for Contained Databases* . The database itself stores all the database metadata and user information, and a user who is defined in this database does not have to have a corresponding login. The information in this database is replicated by the availability group and is available after a failover. For more information, see [Contained Databases](http://go.microsoft.com/fwlink/?LinkID=724064&clcid=0x409). +> [!IMPORTANT:] + + + + + + +#### Create and configure the availability group + +Use the following procedure to create an availability group on the primary replica, which is SP-SRV1 in our example. **Create the availability group** +1. Make sure that your logon account has the required permissions to create an availability group. This requires membership in the **db_owner** fixed database role and either CREATE AVAILABILITY GROUP server permission, CONTROL AVAILABILITY GROUP permission, ALTER ANY AVAILABILITY GROUP permission, or CONTROL SERVER permission. + + +2. Log on to the server that will host the primary replica and start SQL Server Management Studio. + + +3. To start the New Availability Group Wizard, right-click **AlwaysOn High Availability** and then click **New Availability Group Wizard**. + + +4. Click **Next** to advance to the **Specify Name** page. Enter SP-AG1 as the name of the new availability group in the **Availability group name:** box. + + This name must be: a valid SQL Server identifier, unique on the Windows Server Failover Clustering cluster and unique on the domain. + + +5. On the **Select Databases** page, all user databases that are eligible to become the primary database for the new availability group are listed on the **User databases on this instance of SQL Server** grid. Select **TemporaryUserDB**, and then click **Next**. + + +6. On the **Specify Replicas** page, use the following tabs to configure the replicas for SP-AG1: **Replicas**, **Endpoints**, and **Backup Preferences**. + + +7. An availability group listener is a virtual network name that provides client connectivity to the database a given availability group. Availability group listeners direct incoming connections to the primary replica or to a read-only secondary replica. The listener provides fast application failover after an availability group fails over. For more information, see [Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=724065&clcid=0x409). + + On the **Listener** tab, configure an availability group listener for our example, use the name AGListener. + + > [!IMPORTANT:] + + + You cannot directly specify **MultiSubnetFailover=True** because a SharePoint client cannot directly modify a connection string. You must use PowerShell to set this value on the **MultiSubnetFailover** database property. The following example shows how you can do this. + + + + ``` + +$dbs = Get-SPDatabase | ?{$_.MultiSubnetFailover -ne $true} + foreach ($db in $dbs) + { + $db.MultiSubnetFailover = $true + $db.Update() + } + ``` + +8. Select the desired configuration for each instance in the **Selected instances** grid, and then click **Next**. + + +9. Click **Finish** to create the availability group. + + +10. The **Select Initial Data Synchronization** page lets you select a synchronization preference and specify the shared network location that all replicas can access. For our environment accept the default, **Full**, which performs full database and log backups. Click **Next**. + + +11. The **Validation** page of the wizard displays the results of six checks before it lets you continue with availability group creation. If all checks pass, click **Next** to continue. If any tests fail, you cannot continue until you correct the error and then click **Re-run Validation** to run the validation tests again. When all the tests pass, click **Next** to continue. + + +12. On the **Summary** page, verify the configuration of the replica that you are adding and then click **Finish** to save it. To change the configuration, click **Previous** to return to previous wizard pages. + + + +## Install and configure SharePoint Server 2016 + + +At this point in the process, you can install SharePoint Server 2016 and create the farm. Use the following procedure as a guide to install and configure SharePoint Server 2016. +> [!NOTE:] + + + + + + **To install SharePoint Server 2016** +1. Copy the SharePoint Server 2016 program files to a local disk on the computer where you plan to install SharePoint products or to a network file share. + + +2. Run the **Microsoft SharePoint Products and Technologies 2016 Preparation Tool,** to install all the prerequisites to set up and use SharePoint Server 2016. + + +3. Run Setup to install binaries, configure security permissions, and edit registry settings for SharePoint Server 2016. + + +4. Run the SharePoint Products Configuration Wizard to install and configure the configuration database, install and configure the content database, and install Central Administration. + + +5. On the **Specify Configuration Database Settings** page, in the **Database server** box, type **AGListener** as the name of the computer that is running SQL Server. + + > [!IMPORTANT:] + + +## Add SharePoint databases to the availability group + + +To finalize setup of Always On for a SharePoint Server 2016 farm, add the SharePoint databases to the availability group and synchronize secondary replicas to the primary replica. +> [!IMPORTANT:] + + + + + +On the server that hosts the primary replica, you have to run the Add Databases to Availability Group wizard to add all the SharePoint databases to the availability group. The following procedure is the same as the procedure that we described earlier about how to create the availability group. **To add SharePoint databases to the availability group** +1. Log on to the server that will host the primary replica and start SQL Server Management Studio. + + The account that you use must be a member of the Local Administrators group for each server where you install SharePoint Server 2016 + + In addition, the account must have at least one of the following permissions: + + - ALTER AVAILABILITY GROUP permission on the availability group + + + - CONTROL AVAILABILITY GROUP permission + + + - ALTER ANY AVAILABILITY GROUP permission + + + - CONTROL SERVER permission + + + + To join a database to an availability group requires membership in the **db_owner** fixed database role. + + +2. In Object Explorer, browse to, and if it is necessary expand the Availability Groups. + + +3. Right-click the example group, SP-AG1, and then click **Add Database**. + + +4. On the **Select Databases** page, all user databases that are eligible to become the primary database for the new availability group are listed on the **User databases on this instance of SQL Server** grid. Use the checkboxes to select all the databases that you want to add to the group, and then click **Next**. + + +5. The **Select Initial Data Synchronization** page lets you select a synchronization preference and specify the shared network location that all replicas can access. For our environment we'll accept the default, **Full**, which performs full database and log backups. Click **Next**. + + +6. The **Validation** page of the wizard displays the results of six checks before it lets you continue with availability group creation. If any tests fail, you cannot continue until you correct the error and then click **Re-run Validation** to run the validation tests again. When all the tests pass, click **Next** to continue. + + +7. On the **Summary** page, verify the configuration of the replica that you are adding, and then click **Finish** to keep it. To change the configuration, click **Previous** to return to previous wizard pages. + + + +> [!IMPORTANT:] + + + + + + +## Use failover tests to validate the Always On installation + + +After you synchronize the SharePoint data with the secondary replicas, the final step is to test failover.You must run extensive failover tests to make sure that the behavior of the Always On environment is as expected and that you completely understand the configuration requirements and procedures related to SQL Server 2014 (SP1) or SQL Server 2016 Availability Groups. These tests include but aren't limited to the following: +- Verify that all the farm services and features are completely functional. + + +- Verify that SharePoint Server 2016 data is preserved and not corrupted. + + +Test availability group failover by using either the planned manual failover or the forced manual failover described in the following articles: **SQL Server 2014 (SP1)** +- [Perform a Planned Manual Failover of an Availability Group (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=724067&clcid=0x409) + + +- [Perform a Forced Manual Failover of an Availability Group (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=724068&clcid=0x409) + + + **SQL Server 2016** +- [Perform a Planned Manual Failover of an Availability Group (SQL Server)](https://msdn.microsoft.com/en-us/library/hh231018%28v=sql.130%29.aspx) + + +- [Perform a Forced Manual Failover of an Availability Group (SQL Server)](https://msdn.microsoft.com/en-us/library/ff877957.aspx) + + +You can perform either of the previous failovers by using the Failover Wizard in SQL Server Management Studio, Transact-SQL, or PowerShell in SQL Server 2014 (SP1) and SQL Server 2016. +> [!NOTE:] + + + + + + +## Monitor the Always On environment + + +You have to monitor an Always On environment for performance, health, and capacity. **Performance**The following new performance objects are available to monitor an Always On environment. **SQL Server 2014 (SP1)** +- [SQL Server, Database Replica](http://go.microsoft.com/fwlink/?LinkID=724069&clcid=0x409) + + +- [SQL Server, Availability Replica](http://go.microsoft.com/fwlink/?LinkID=724070&clcid=0x409) + + + **SQL Server 2016** +- [SQL Server, Database Replica](https://msdn.microsoft.com/en-us/library/ff878356%28v=sql.130%29.aspx) + + +- [SQL Server, Availability Replica](https://msdn.microsoft.com/en-us/library/ff878472%28v=sql.130%29.aspx) + + + **Health and capacity**For general health monitoring you can use the Availability Groups Dashboard to obtain the health of the availability groups in the system. For more information, see [AlwaysOn Policies for Operational Issues with AlwaysOn Availability Groups (SQL Server)](http://go.microsoft.com/fwlink/?LinkID=724071&clcid=0x409) for SQL Server 2014 (SP1) and [AlwaysOn Policies for Operational Issues with AlwaysOn Availability Groups (SQL Server)](https://technet.microsoft.com/en-us/library/hh510235%28v=sql.130%29.aspx) for SQL Server 2016.You can also use Transact-SQL to monitor availability groups by using the set of catalog and dynamic management views that are provided for Always On Availability Groups. For more information, see [Monitor Availability Groups (Transact-SQL)](http://go.microsoft.com/fwlink/?LinkID=724072&clcid=0x409) for SQL Server 2014 (SP1) and [Monitor Availability Groups (Transact-SQL)](https://msdn.microsoft.com/en-us/library/ff878305%28v=sql.130%29.aspx) for SQL Server 2016. +# See also + +#### + + [Install and configure SharePoint Server 2016](html/install-and-configure-sharepoint-server-2016.md) + + + + +#### + + [Deploying SharePoint Server 2016 with SQL Server AlwaysOn Availability Groups in Azure](html/deploying-sharepoint-server-2016-with-sql-server-alwayson-availability-groups-in.md) + + + + + + + + diff --git a/SharePoint/configure-sql-server-security-for-sharepoint-server-2016.md b/SharePoint/configure-sql-server-security-for-sharepoint-server-2016.md new file mode 100644 index 0000000000..aaabaa1583 --- /dev/null +++ b/SharePoint/configure-sql-server-security-for-sharepoint-server-2016.md @@ -0,0 +1,228 @@ +--- +title: Configure SQL Server security for SharePoint Server 2016 +ms.prod: SHAREPOINT +ms.assetid: 2c727311-e83e-4f7b-b02c-9a0699a81e64 +--- + + +# Configure SQL Server security for SharePoint Server 2016 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Server 2016* * **Topic Last Modified:** 2017-05-30* **Summary:** Learn how to improve the security of SQL Server for SharePoint Server 2016environments.When you install SQL Server, the default settings help to provide a safe database. In addition, you can use SQL Server tools and Windows Firewall to add additional security to SQL Server for SharePoint Server 2016 environments. In this article: +- [Before you begin](#begin) + + +- [Configuring a SQL Server instance to listen on a non-default port](#proc1) + + - [To configure a SQL Server instance to listen on a non-default port](#nondef) + + +- [Blocking default SQL Server listening ports](#proc2) + + +- [Configuring Windows Firewall to open manually assigned ports](#proc3) + + - [To configure Windows Firewall to open manually assigned ports](#openports) + + +- [Configuring SQL Server client aliases](#proc4) + + - [To configure a SQL Server client alias](#clientalias) + + + +## Before you begin + + +Before you begin this operation, review the following tasks about how to secure your server farm: +- Block UDP port 1434. + + +- Configure named instances of SQL Server to listen on a nonstandard port (other than TCP port 1433 or UDP port 1434). + + +- For additional security, block TCP port 1433 and reassign the port that is used by the default instance to a different port. + + +- Configure SQL Server client aliases on all front-end web servers and application servers in the server farm. After you block TCP port 1433 or UDP port 1434, SQL Server client aliases are necessary on all computers that communicate with the computer that is running SQL Server. + + + +## Configuring a SQL Server instance to listen on a non-default port + + +SQL Server provides the ability to reassign the ports that are used by the default instance and any named instances. In SQL Server Service Pack 1 (SP1), you reassign the TCP port by using SQL Server Configuration Manager. When you change the default ports, you make the environment more secure against hackers who know default assignments and use them to exploit your SharePoint environment. **To configure a SQL Server instance to listen on a non-default port** +1. Verify that the user account that is performing this procedure is a member of either the sysadmin or the serveradmin fixed server role. + + +2. On the computer that is running SQL Server, open SQL Server Configuration Manager. + + +3. In the navigation pane, expand **SQL Server Network Configuration**. + + +4. Click the corresponding entry for the instance that you are configuring. + + The default instance is listed as **Protocols for MSSQLSERVER**. Named instances will appear as **Protocols for named_instance**. + + +5. In the main window in the **Protocol Name** column, right-click **TCP/IP**, and then click **Properties**. + + +6. Click the **IP Addresses** tab. + + For every IP address that is assigned to the computer that is running SQL Server, there is a corresponding entry on this tab. By default, SQL Server listens on all IP addresses that are assigned to the computer. + + +7. To globally change the port that the default instance is listening on, follow these steps: + + - For each IP address except **IPAll**, clear all values for both **TCP dynamic ports** and **TCP Port**. + + + - For **IPAll**, clear the value for **TCP dynamic ports**. In the **TCP Port** field, enter the port that you want the instance of SQL Server to listen on. For example, enter 40000. + + +8. To globally change the port that a named instance is listening on, follow these steps: + + - For each IP address including **IPAll**, clear all values for **TCP dynamic ports**. A value of 0 for this field indicates that SQL Server uses a dynamic TCP port for the IP address. A blank entry for this value means that SQL Server will not use a dynamic TCP port for the IP address. + + + - For each IP address except **IPAll**, clear all values for **TCP Port.** + + + - For **IPAll**, clear the value for **TCP dynamic ports**. In the **TCP Port** field, enter the port that you want the instance of SQL Server to listen on. For example, enter 40000. + + +9. Click **OK**. + + A message indicates that that the change will not take effect until the SQL Server service is restarted. Click **OK**. + + +10. Close SQL Server Configuration Manager. + + +11. Restart the SQL Server service and confirm that the computer that is running SQL Server is listening on the port that you selected. + + You can confirm this by looking in the Event Viewer log after you restart the SQL Server service. Look for an information event similar to the following event: + + Event Type:Information + + Event Source:MSSQL$MSSQLSERVER + + Event Category:(2) + + Event ID:26022 + + Date:3/6/2008 + + Time:1:46:11 PM + + User:N/A + + Computer: *computer_name* + + Description: + + Server is listening on [ 'any' 50000] + + +12. **Verification:** Optionally, include steps that users should perform to verify that the operation was successful. + + + +## Blocking default SQL Server listening ports + + +Windows Firewall with Advanced Security uses Inbound Rules and Outbound Rules to help secure incoming and outgoing network traffic. Because Windows Firewall blocks all incoming unsolicited network traffic by default, you do not have to explicitly block the default SQL Server listening ports. For more information, see [Windows Firewall with Advanced Security](http://go.microsoft.com/fwlink/p/?LinkID=718056&clcid=0x409) and [Configuring the Windows Firewall to Allow SQL Server Access](http://go.microsoft.com/fwlink/p/?LinkID=718059&clcid=0x409). +## Configuring Windows Firewall to open manually assigned ports + + +To access a SQL Server instance through a firewall, you must configure the firewall on the computer that is running SQL Server to allow access. Any ports that you manually assign must be open in Windows Firewall. **To configure Windows Firewall to open manually assigned ports** +1. Verify that the user account that is performing this procedure is a member of either the sysadmin or the serveradmin fixed server role. + + +2. In **Control Panel**, open **System and Security**. + + +3. Click **Windows Firewall**, and then click **Advanced Settings** to open the **Windows Firewall with Advanced Security** dialog box. + + +4. In the navigation pane, click **Inbound Rules** to display the available options in the **Actions** pane. + + +5. Click **New Rule** to open the **New Inbound Rule Wizard**. + + +6. Use the wizard to complete the steps that are required to allow access to the port that you defined in [Configure a SQL Server instance to listen on a non-default port](#proc1). + + > [!NOTE:] + + +## Configuring SQL Server client aliases + + +If you block UDP port 1434 or TCP port 1433 on the computer that is running SQL Server, you must create a SQL Server client alias on all other computers in the server farm. You can use SQL Server client components to create a SQL Server client alias for computers that connect to SQL Server. **To configure a SQL Server client alias** +1. Verify that the user account that is performing this procedure is a member of either the sysadmin or the serveradmin fixed server role. + + +2. Run Setup for SQL Server on the target computer, and install the following client components: + + - **Connectivity Components** + + + - **Management Tools** + + +3. Open SQL Server Configuration Manager. + + +4. In the navigation pane, click **SQL Native Client Configuration**. + + +5. In the main window under Items, right-click **Aliases**, and select **New Alias**. + + +6. In the **Alias - New** dialog box, in the **Alias Name** field, enter a name for the alias. For example, enter SharePoint *_alias* . + + +7. In the **Port No** field, enter the port number for the database instance. For example, enter 40000. Make sure that the protocol is set to TCP/IP. + + +8. In the **Server** field, enter the name of the computer that is running SQL Server. + + +9. Click **Apply**, and then click **OK**. + + +10. **Verification:** You can test the SQL Server client alias by using SQL Server Management Studio, which is available when you install SQL Server client components. + + +11. Open SQL ServerManagement Studio. + + +12. When you are prompted to enter a server name, enter the name of the alias that you created, and then click **Connect**. If the connection is successful, SQL ServerManagement Studio is populated with objects that correspond to the remote database. + + +13. To check connectivity to additional database instances from SQL ServerManagement Studio, click **Connect**, and then click **Database Engine**. + + + +# See also + +#### + + [Securing SharePoint: Harden SQL Server in SharePoint Environments](https://blogs.technet.com/b/rycampbe/archive/2013/10/14/securing-sharepoint-harden-sql-server-in-sharepoint-environments.aspx) + + + + [Configure a Windows Firewall for Database Engine Access](http://go.microsoft.com/fwlink/p/?LinkID=718060&clcid=0x409) + + + + [Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)](http://go.microsoft.com/fwlink/p/?LinkID=718061&clcid=0x409) + + + + + + + + diff --git a/SharePoint/configure-the-co-authoring-versioning-period-in-sharepoint-2013.md b/SharePoint/configure-the-co-authoring-versioning-period-in-sharepoint-2013.md new file mode 100644 index 0000000000..22bdba56cf --- /dev/null +++ b/SharePoint/configure-the-co-authoring-versioning-period-in-sharepoint-2013.md @@ -0,0 +1,77 @@ +--- +title: Configure the co-authoring versioning period in SharePoint 2013 +ms.prod: SHAREPOINT +ms.assetid: 59f3af85-89f9-43ba-b364-28a810cae42e +--- + + +# Configure the co-authoring versioning period in SharePoint 2013 + **We are in the process of combining the SharePoint Server 2013 and SharePoint Server 2016 content into a single content set. We appreciate your patience while we reorganize things. See the Applies To tag at the top of each article to find out which version of SharePoint an article applies to.** * **Applies to:** SharePoint Foundation 2013, SharePoint Server 2013* * **Topic Last Modified:** 2017-07-20* **Summary:**  Learn how to specify how often SharePoint Server 2013 stores a version of a document that is being edited.The CoauthoringVersionPeriod property specifies, in minutes, how often SharePoint stores a version of a document that is being edited. This article describes how to use Microsoft PowerShell to configure the CoauthoringVersionPeriod property. For more information about document library versioning, see [Configure versioning for co-authoring in SharePoint 2013](html/configure-versioning-for-co-authoring-in-sharepoint-2013.md). +## Configure the co-authoring versioning period in SharePoint Server 2013 + +When versioning is turned on, SharePoint Server 2013 takes periodic snapshots of documents, saving them for later reference. This information can provide an edit trail that may be useful for seeing who changed a document, rolling back to an earlier version, or for compliance reasons. You can configure the CoauthoringVersionPeriod property by using the Microsoft PowerShell. If the value is set to 0, SharePoint Server 2013 captures every change made by a new user in a different version of the document. If the value is set to a very large number, SharePoint Server 2013 creates one version for the whole editing session. This latter behavior matches the behavior of files that are not co-authored and files that were created in earlier versions of SharePoint Server 2013 or SharePoint Foundation. **To configure the co-authoring versioning period by using Windows PowerShell (save as script and run script)** +1. Verify that you have the following memberships: + + - **securityadmin** fixed server role on the SQL Server instance. + + + - **db_owner** fixed database role on all databases that are to be updated. + + + - Administrators group on the server on which you are running PowerShell cmdlets. + + + + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server 2013 cmdlets. + + > [!NOTE:] + +2. Paste the following code into a text editor, such as Notepad: + + ``` + +$siteurl =" " +$mysite=new-object Microsoft.SharePoint.SPSite($siteurl) +$mysite.WebApplication.WebService.CoauthoringVersionPeriod =