The Broken Links Analysis enables you to identify broken links in SharePoint linked lists. Included in the analysis is the reason why the link is considered "broken," as well as a link to the SharePoint Links Edit form, providing you with the opportunity to "fix" the link.
To generate a Broken Links Analysis:
1Select the object(s) for which you want to analyze broken links.
2Choose Content > Broken Links Analysis.
Now you can:
·run the operation immediately (by clicking the [Run Now] button)
OR
·schedule the operation to run at a later time or on a recurring basis.
OR
·save the operation as XML Instructions that can be run at a later time.
The top level of the analysis lists all of the Web applications within the scope of your analysis.
When expanded, the following information displays for each broken link:
·the name of the Site and List where the broken link is located
·the Web Address of the broken link
·the Reason for reported failure.
Some Reasons Why Links May Be Considered "Broken"
The following table describes some of the common reasons why a link on a SharePoint Linked List may be considered "broken."
Reason |
Description |
---|---|
The operation has timed out |
The request timed out before the page could be accessed. |
The remote name could not be resolved |
The url may be invalid. |
The remote server returned an error: (401). Unauthorized |
The ControlPoint Service Account does not have permissions to access the page. |
The remote server returned an error: (404) Not Found |
The page may not exist (or may no longer exist). |
To view/edit the broken link:
Click the Link hyperlink to open the SharePoint Links Edit page
The ControlPoint Solution Summary analysis lets you view details about solutions deployed within or across SharePoint farms:
·if you are a Farm Administrator, all deployed Farm Solutions
AND/OR
·sandboxed solutions deployed to site collections within your selected scope.
To generate a Solution Summary analysis:
1Select the object(s) you want to include in your analysis.
2Choose Content > Solution Summary.
3Specify the parameters of your analysis:
§If you want your results to include only solutions whose name matches a specific text string, enter the string in the Solution name contains: field.
§If you want results to include ONLY Farm solutions OR Sandboxed solutions, select the appropriate option from the drop-down.
REMINDER: Farm solutions will be included only if you are a Farm Administrator.
Now you can:
·run the operation immediately (by clicking the [Run Now] button)
OR
·schedule the operation to run at a later time or on a recurring basis.
OR
·save the operation as XML Instructions that can be run at a later time.
For each solution type you chose to include, the farm(s) within the selected scope display.
Farm Solutions section
If you are a Farm Administrator, the Farm Solutions section lists all of the solutions deployed to the entire farm (regardless of the selected scope), along with the following information:
·the Solution Name
·its current deployment Status
·where the solution is Deployed To
·the Last Operation Time that an action was taken
·whether the solution contains a Web Application Resource, Global Assembly, and/or Code Access Security (CAS) Policy:
·the Solution ID, and
·upon further drill-down, the Last Operation Detail.
Sandboxed Solutions section
If any sandboxed solutions have been installed in site collections within your selected scope, the Sandbox Solutions section lists each of these site collections, along with the following information about the installed solution(s):
·the Solution Name
·the solution's deployment Status
NOTE: A blank Status indicates that the solution is installed but has never been activated.
• the installed Version of the solution
·the solution's Last Modified date and time
·the solution's Resource Usage.
NOTE: For information on the concept of Resource Usage, consult your SharePoint documentation.
• the Solution ID
The Web Parts analysis provide detailed statistics about Web Parts used in your SharePoint environment.
To generate a Web Parts analysis:
1Select the object(s) on which you want to perform the analysis.
2Choose Change Management > Web Parts.
3Select the option you want to Group By: Parts or Sites.
4Specify additional parameters for your analysis.
In addition to the "standard" parameters, you can limit results to Web Parts that meet one or more specific criteria, as described in the following table.
If you want results to include ... |
Then ... |
---|---|
one or more specific Web Parts |
select from the Web Parts list box. NOTE: If you do not select specific Web Parts, all Web Parts will be returned. EXCEPTION: If the ControlPoint Application Administrator has chosen to exclude Web Parts from the ControlPoint Discovery process, the message No Values Available will display in the list box. |
Web Parts whose name contains a specific text string |
enter the text string in the Web Part Name contains field. NOTE: You can enter multiple text strings as a comma-separated list. |
only Web Parts that are currently in use |
check the Show only parts used in pages box. NOTE: If you leave this box unchecked and you do not select a specific Web Part, analysis results will also include Web Parts that are not currently in use. |
only Web Parts that are closed and hidden |
check the Show only Closed and Hidden box. |
Note that the option to Use cached data will be disabled if Web Parts have been excluded from the ControlPoint Discovery job. The inclusion or exclusion of Web Parts can be managed by the ControlPoint Application Administrators. Details can be found in the ControlPoint Administration Guide.
Now you can:
·run the operation immediately (by clicking the [Run Now] button)
OR
·schedule the operation to run at a later time or on a recurring basis.
OR
·save the operation as XML Instructions that can be run at a later time.
If you chose to group results ... |
Then .... |
---|---|
By part |
the top level of the analysis lists the Web Part(s) within the scope of your analysis, as well as the total number of pages in which each is used. When expanded, a list of sites that use each Web Part displays. |
By site |
the top level of the analysis lists the Web applications/site collections within the scope of your analysis. When expanded, a list of Web Parts used by each site displays.
|
Within the context of the site, the following information displays for each Web Part:
·the Title of the Web Partthat is, the name assigned to that instance of the Web Part
NOTE: If the same Web Part is used more than once on a page, the title of each instance is listed in a comma-separated list. Web Parts that are hidden or closed are annotated.
·the Page on which the Web Part is used
·the following values, which are the same as those reported in the SharePoint Web Gallery:
§the user account that the Web Part was Created by, well as the user account it was Last Modified by
§the dates when the Web Part was both Created and Last Updated
NOTE: The Created by, Last Modified by, Created, and Last Updated values refers to the Web Part itself, not its instance on a specific page. Often, the Created date is the date that the Web Part was installed on the system.
·the Size of the Web Part in kilobytes (KB).
Note that some commonly-built Web Parts that display in analysis results (such as the List View Web Part) are not listed in the Web Parts Gallery and are not associated with a specific creator or created by/modified by dates. Often, such Web Parts have names that begin with "Microsoft SharePoint."
The SharePoint Hierarchy Report lets you view and print the hierarchy of Web applications,site collections, sitesand optionally, listswithin a SharePoint farm. You can generate this report for the entire farm or for selected objects within the Hierarchy.
Information in this report is current as of the last ControlPoint Discovery.
EXCEPTION: If you ran the report at the site level and Include Children is checked, the report will be run on real-time data.
In a multi-farm environment, this analysis can only be run on the home farm.
To generate a SharePoint Hierarchy Report:
1Select the object(s) that you want to include in the report.
2Choose Configuration > SharePoint Hierarchy.
3Specify one or more parameters for your analysis:
If you want results to ... |
Then ... |
---|---|
include lists and libraries within sites |
check the Include Lists box. NOTE: If you check this box, ControlPoint must iterate through all lists. Depending on the scope of your analysis and the number of lists within that scope, processing time may increase noticeably. |
include folders and items within sites |
check the Include Folders and Items box. NOTE: If you check this box, ControlPoint must iterate through all list items. Depending on the scope of your analysis and the number of items within that scope, processing time may increase noticeably.
|
display the url for each site collection and site to the right of each site name |
check the Display URLs box. NOTE: If you leave this box unchecked, only the names of the site collections and sites will display. |
include objects whose permissions are unique (not inherited) |
check the Unique permissions only box. NOTE: If you check this box, objects will be shown within the context of the hierarchy, even if the parent object has inherited permissions. |
Now you can:
·run the operation immediately (by clicking the [Run Now] button)
OR
·schedule the operation to run at a later time or on a recurring basis.
OR
·save the operation as XML Instructions that can be run at a later time.
.
The top level displays all Web applications within the scope of your analysis.
When expanded:
·the name of the object and its Type (site collection, site, list, item, and so on) displays
NOTE: If you chose to Display URLs, the url for each site collection and site displays in parentheses to the right of its name.
·a plus sign (+) identifies each object whose permissions are unique (that is, not inherited from the parent objects).
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center