SPGlobalAdmin Members
Include Protected Members
Include Inherited Members
NOTE: This API is now obsolete.
In Windows SharePoint Services 2.0, SPGlobalAdmin represented the top-level object for administration of a deployment, and is maintained for backward compatibility. Use the new SPFarm and SPWebService classes instead, to manage a SharePoint Foundation deployment.
The SPGlobalAdmin type exposes the following members.
Constructors
Name | Description | |
---|---|---|
SPGlobalAdmin | Obsolete. Obsolete. Initializes a new instance of the SPGlobalAdmin class. |
Top
Properties
Name | Description | |
---|---|---|
AccountCreationModeEnabled | Obsolete. Use the CreateActiveDirectoryAccounts property of the SPWebService class to specify whether Active Directory Domain Services accounts are created instead. (In Windows SharePoint Services 2.0, the AccountCreationModeEnabled property indicated whether account creation mode for Active Directory Domain Services is enabled, and is maintained for backward compatibility.) | |
AdminFormDigest | Obsolete. Use the FormDigest class instead to implement security validation. (In Windows SharePoint Services 2.0, the AdminFormDigest property got the security validation that was used for a request in a SharePoint Central Administration page, and is maintained for backward compatibility.) | |
AdminPortApplicationPoolId | Obsolete. Use the Name property of the SPApplicationPool class to identify the application pool instance instead. (In Windows SharePoint Services 2.0 the AdminPortApplicationPoolId property got the administrative application pool ID, and is maintained for backward compatibility.) | |
AdminPortIISInstanceId | Obsolete. Use the IisSettings property of the SPAdministrationWebApplication class to access the instance ID of the administration port instead. (In Windows SharePoint Services 2.0 the AdminPortIISInstanceId property got the administrative ID of the instance of Internet Information Services (IIS), and is maintained for backward compatibility.) | |
AdminPortUrl | Obsolete. Use the GetResponseUri method of the SPWebApplication class to return the abolute root of the URI instead. (In Windows SharePoint Services 2.0 the AdminPortUrl property got the administration port used on the administration virtual server, and is maintained for backward compatibility.) | |
AllowUnsafeUpdates | Obsolete. Obsolete. Gets or sets a Boolean value that specifies whether to allow updates to the database as a result of a GET request or without requiring a security validation. | |
ApplicationPools | Obsolete. Use the ApplicationPools property of the SPWebService class to get the collection of Internet Information Services (IIS) application pools that are available to the service instead. (In Windows SharePoint Services 2.0, the ApplicationPools property got the IIS application pools for the virtual server, and is maintained for backward compatibility.) | |
Config | Obsolete. Obsolete. In Windows SharePoint Services 2.0, the Config property got a global configuration object that contained configuration settings in the SharePoint Foundation deployment, and is maintained for backward compatibility. | |
ConfigDatabase | Obsolete. The configuration database should not be accessed directly. (In Windows SharePoint Services 2.0, the ConfigDatabase property got the configuration database in the SharePoint Foundation deployment, and is maintained for backward compatibility.) | |
ConfigDatabaseName | Obsolete. The configuration database should not be accessed directly. (In Windows SharePoint Services 2.0, the ConfigDatabaseName property got the name of the configuration database, and is maintained for backward compatibility.) | |
ConfigDatabaseServer | Obsolete. The configuration database should not be accessed directly. (In Windows SharePoint Services 2.0, the ConfigDatabaseServer property got the name of the configuration database server, and is maintained for backward compatibility.) | |
ConfigDatabaseUser | Obsolete. The configuration database should not be accessed directly. (In Windows SharePoint Services 2.0, the ConfigDatabaseUser property got the user name of the administrator account for the configuration database, and is maintained for backward compatibility.) | |
InstalledLanguages | Obsolete. Use the GlobalInstalledLanguages property of the SPRegionalSettings class to get the languages installed in the SharePoint Foundation deployment instead. (In Windows SharePoint Services 2.0, the InstalledLanguages property got the collection of installed languages, and is maintained for backward compatibility.) | |
MailCodePage | Obsolete. Use the UpdateMailSettings method of the SPAdministrationWebApplication class to update default mail settings instead. (In Windows SharePoint Services 2.0, the MailCodePage property got the language code page used for e-mail messages, and is maintained for backward compatibility.) | |
MailFromAddress | Obsolete. Use the UpdateMailSettings method of the SPAdministrationWebApplication class to update default mail settings instead. (In Windows SharePoint Services 2.0, the MailFromAddress property got the From address used for e-mail in the SharePoint Foundation deployment, and is maintained for backward compatibility.) | |
MailReplyToAddress | Obsolete. Use the UpdateMailSettings method of the SPAdministrationWebApplication class to update default mail settings instead. (In Windows SharePoint Services 2.0, the MailReplyToAddress property got the To address used for e-mail in the SharePoint Foundation deployment, and is maintained for backward compatibility.) | |
OutboundSmtpServer | Obsolete. Use the UpdateMailSettings method of the SPAdministrationWebApplication class to update default mail settings instead. (In Windows SharePoint Services 2.0 the OutboundSmtpServer property got the name of the SMTP server used for e-mail messages in the SharePoint Foundation deployment, and is maintained for backward compatibility.) | |
ServerCulture | Obsolete. Obsolete. In Windows SharePoint Services 2.0 the ServerCulture property got information about the culture represented on the virtual server, and is maintained for backward compatibility. | |
ServerLanguage | Obsolete. Use the ServerLanguage property of the SPRegionalSettings class to get the language used in the Web application instead. (In Windows SharePoint Services 2.0 the ServerLanguage property got the language used on the virtual server, and is maintained for backward compatibility.) | |
TimeZones | Obsolete. Use the TimeZones property of the SPRegionalSettings class to get the collection of time zones used in a server farm instead. (In Windows SharePoint Services 2.0, the TimeZones property got the collection of time zones, and is maintained for backward compatibility.) | |
UsageSettings | Obsolete. Use the UsageSettings property of the SPWebService class to get the collection of usage settings for the Web service instead. (In Windows SharePoint Services 2.0, the UsageSettings property got a usage settings object that encapsulated the settings for logging and usage processing, and is maintained for backward compatibility.) | |
UseHostHeaderAsSiteName | Obsolete. Use the HostHeaderIsSiteName property of the SPSite class to indicate whether the host header is used to uniquely identify the site collection instead. (In Windows SharePoint Services 2.0, the UseHostHeaderAsSiteName property got a Boolean value that indicated whether the host header was used as the name for the site collection on the virtual server, and is maintained for backward compatibility.) | |
UseNtAuthenticationForDatabase | Obsolete. The authentication mode can vary for each database, and a database uses NT authentication if the Username property is null. (In Windows SharePoint Services 2.0, the UseNtAuthenticationForDatabase property got a Boolean value that indicated whether Microsoft Windows NT authentication is used for the database, and is maintained for backward compatibility.) | |
Version | Obsolete. Obsolete. In Windows SharePoint Services 2.0, the Version property got the version of SharePoint Foundation that is installed in the deployment, and is maintained for backward compatibility. | |
VirtualServerNames | Obsolete. Use the WebApplications property of the SPWebService class to get the collection of Web applications in the Web service instead. (In Windows SharePoint Services 2.0, the VirtualServerNames property got the names of the virtual servers in the SharePoint Foundation deployment, and is maintained for backward compatibility.) | |
VirtualServers | Obsolete. Use the WebApplications property of the SPWebService class to get the collection of Web applications in the Web service instead. (In Windows SharePoint Services 2.0, the VirtualServerNames property got the collection of virtual server objects in the SharePoint Foundation deployment, and is maintained for backward compatibility.) |
Top
Methods
Name | Description | |
---|---|---|
AddCustomGlobalWebTemplate | Obsolete. Use the Add method of the SPPersistedCustomWebTemplateCollection class to add a template to the collection of custom site collection templates instead. (In Windows SharePoint Services 2.0, the AddCustomGlobalWebTemplate method added a site template to the site template gallery, and is maintained for backward compatibility.) | |
AddWPPack | Obsolete. Use the SPSolution class and other related solution objects to deploy Web Parts instead. (In Windows SharePoint Services 2.0, the AddWPPack method either enabled a Web Part package that was already installed on the virtual server and added it to the Web Part gallery, or installed and enabled a Web Part package and added it to the Web Part gallery, and is maintained for backward compatibility.) | |
CheckVirtualServerState | Obsolete. Obsolete. In Windows SharePoint Services 2.0, the CheckVirtualServerState method verified whether the virtual server was in the specified state, and is maintained for backward compatibility. | |
Close | Obsolete. In Windows SharePoint Services 2.0, the Close method closed the global administration object and is maintained for backward compatibility. | |
CreateAdminVirtualServer | Obsolete. The Administration Web application is created when the server farm is created. To provision the Central Administration Web site on a server, enable the Central Administration Web service instead. (In Windows SharePoint Services 2.0 the CreateAdminVirtualServer method created an administration virtual server, and is maintained for backward compatibility.) | |
CreateConfigDatabase(String, String, String, String) | Obsolete. Use the Create() method of the SPFarm class to create a configuration database instead. (In Windows SharePoint Services 2.0, the CreateConfigDatabase method was used to create a configuration database based on the specified database server, database name, account name, and password, and is maintained for backward compatibility.) | |
CreateConfigDatabase(String, String, String, String, Boolean, Boolean, String, String) | Obsolete. Use the Create() method of the SPFarm class to create a configuration database instead. (In Windows SharePoint Services 2.0, the CreateConfigDatabase method was used to create a configuration database based on the specified database server, database name, user name, password, account information for Active Directory Domain Services (AD DS), and a Boolean value that specifies whether to use the host header as the name for a site, and is maintained for backward compatibility.) | |
DeleteAdminVirtualServer | Obsolete. Use the Unprovision method of the SPWebServiceInstance class to remove the Web service from the server. (In Windows SharePoint Services 2.0, the DeleteAdminVirtualServer method was used to delete the administration virtual server, and is maintained for backward compatibility.) | |
DeleteConfigDB | Obsolete. Use the Unjoin method of the SPFarm class to remove the local server from the server farm instead. (In Windows SharePoint Services 2.0, the DeleteConfigDB method was used to delete the configuration database and all associated information, and is maintained for backward compatibility.) | |
DeleteCustomGlobalWebTemplate | Obsolete. Use the Remove method of the SPPersistedCustomWebTemplateCollection class to delete the template instead. (In Windows SharePoint Services 2.0, the DeleteCustomGlobalWebTemplate method was used to delete the specified global site template, and is maintained for backward compatibility.) | |
Dispose | Obsolete. In Windows SharePoint Services 2.0, the Dispose method was used to release all unmanaged resources used by the global administration object, and is maintained for backward compatibility. | |
EnumWPPacks | Obsolete. Use the SPSolution class and other related solution objects to deploy Web Parts instead. (In Windows SharePoint Services 2.0, the EnumWPPacks method returned a string that contained the URL and file name of the specified installed Web Part package, or a string that contained a list of all the Web Part packages currently installed on the specified virtual server or front-end Web server, and is maintained for backward compatibility.) | |
Equals | (Inherited from Object.) | |
ExtendVirtualServer(Uri, Boolean, String, Boolean, String, String) | Obsolete. Use the SPWebApplicationBuilder class to create a new Web application instead. (In Windows SharePoint Services 2.0 the ExtendVirtualServer method extended an Internet Information Services (IIS) Web site with SharePoint Foundation, and is maintained for backward compatibility.) | |
ExtendVirtualServer(Uri, Boolean, String, Boolean, String, String, Boolean, Boolean) | Obsolete. Use the SPWebApplicationBuilder class to create a new Web application instead. (In Windows SharePoint Services 2.0 the ExtendVirtualServer method extended an Internet Information Services (IIS) Web site with SharePoint Foundation, and is maintained for backward compatibility.) | |
ExtendVirtualServer(String, String, String, String, Uri, Boolean, String, Boolean, String, String) | Obsolete. Use the SPWebApplicationBuilder class to create a new Web application instead. (In Windows SharePoint Services 2.0 the ExtendVirtualServer method extended an Internet Information Services (IIS) Web site with SharePoint Foundation, and is maintained for backward compatibility.) | |
ExtendVirtualServer(String, String, String, String, Uri, Boolean, String, Boolean, String, String, Boolean, Boolean) | Obsolete. Use the SPWebApplicationBuilder class to create a new Web application instead. (In Windows SharePoint Services 2.0 the ExtendVirtualServer method extended an Internet Information Services (IIS) Web site with SharePoint Foundation, and is maintained for backward compatibility.) | |
ExtendVirtualServerInWebFarm(Uri, String, SPUrlZone, Boolean, Boolean) | Obsolete. To extend a Web application to a new Internet Information Services (IIS) Web site, add a new entry to the IIS settings through the IisSettings property of the SPWebApplication class. SharePoint Foundation automatically handles duplication of IIS Web sites on other computers in the server farm. (In Windows SharePoint Services 2.0, the ExtendVirtualServerInWebFarm method extended a virtual server in a server farm with SharePoint Foundation, and is maintained for backward compatibility.) | |
ExtendVirtualServerInWebFarm(Uri, String, Boolean, String, Boolean, String, String) | Obsolete. To extend a Web application to a new Internet Information Services (IIS) Web site, add a new entry to the IIS settings through the IisSettings property of the SPWebApplication class. SharePoint Foundation automatically handles duplication of IIS Web sites on other computers in the server farm. (In Windows SharePoint Services 2.0, the ExtendVirtualServerInWebFarm method extended a virtual server in a server farm with SharePoint Foundation, and is maintained for backward compatibility.) | |
ExtendVirtualServerInWebFarm(Uri, String, Boolean, String, Boolean, String, String, Boolean, Boolean) | Obsolete. To extend a Web application to a new Internet Information Services (IIS) Web site, add a new entry to the IIS settings through the IisSettings property of the SPWebApplication class. SharePoint Foundation automatically handles duplication of IIS Web sites on other computers in the server farm. (In Windows SharePoint Services 2.0, the ExtendVirtualServerInWebFarm method extended a virtual server in a server farm with SharePoint Foundation, and is maintained for backward compatibility.) | |
Finalize | (Inherited from Object.) | |
GetHashCode | (Inherited from Object.) | |
GetType | (Inherited from Object.) | |
IIS6EnableSTS | Obsolete. In Windows SharePoint Services 2.0, the IIS6EnableSTS method specified whether to enable SharePoint Foundation in Internet Information Services (IIS) version 6, and is maintained for backward compatibility. | |
IsCurrentUserGlobalAdmin | Obsolete. In Windows SharePoint Services 2.0, the IsCurrentUserGlobalAdmin method returned a Boolean value that indicated whether the current user is a member of the SharePoint administrators group account in the SharePoint Foundation deployment, and is maintained for backward compatibility. | |
IsCurrentUserMachineAdmin | Obsolete. Obsolete. In Windows SharePoint Services 2.0, the IsCurrentUserGlobalAdmin method returned a Boolean value that indicated whether the current user is a member of the local administrators group for the computer running SharePoint Foundation, and is maintained for backward compatibility. | |
ListCustomGlobalWebTemplates | Obsolete. In Windows SharePoint Services 2.0, the ListCustomGlobalWebTemplates method returned a list of the global site templates available for instantiating sites across virtual servers on a front-end Web server, and is maintained for backward compatibility. | |
Log | Obsolete. In Windows SharePoint Services 2.0, the Log method created an entry in the SharePoint Foundation error log, and is maintained for backward compatibility. For information about how to log errors in Windows SharePoint Services 3.0, see Trace Logs. | |
MemberwiseClone | (Inherited from Object.) | |
OpenVirtualServer | Obsolete. Use the Lookup method of the SPWebApplication class to return a specified Web application instead. (In Windows SharePoint Services 2.0 the OpenVirtualServer method opened the virtual server, and is maintained for backward compatibility.) | |
RefreshConfigCache() | Obsolete. The configuration cache is now refreshed automatically by the timer service. (In Windows SharePoint Services 2.0 the RefreshConfigCache method refreshed the configuration cache, and is maintained for backward compatibility.) | |
RefreshConfigCache(Guid, Boolean) | Obsolete. The configuration cache is now refreshed automatically by the timer service. (In Windows SharePoint Services 2.0 the RefreshConfigCache method refreshed the configuration cache based on the specified virtual server and on a Boolean value that indicated whether the SharePoint administrators group account had changed, and is maintained for backward compatibility.) | |
RefreshConfigCacheOnRemoteServers() | Obsolete. The configuration cache is now refreshed automatically by the timer service. (In Windows SharePoint Services 2.0 the RefreshConfigCacheOnRemoteServers method refreshed the configuration cache on remote servers in the server farm, and is maintained for backward compatibility.) | |
RefreshConfigCacheOnRemoteServers(Guid, Boolean) | Obsolete. The configuration cache is now refreshed automatically by the timer service. (In Windows SharePoint Services 2.0 the RefreshConfigCacheOnRemoteServers method refreshed the configuration cache on remote servers in the server farm based on the specified virtual server and on a Boolean value that specified whether the SharePoint administrators group account had changed, and is maintained for backward compatibility.) | |
RegisterASPNETClient | Obsolete. In Windows SharePoint Services 2.0 the RegisterASPNETClient method installed script files for validating the client computer, and is maintained for backward compatibility. | |
RemoveWPPack | Obsolete. Use the SPSolution class and other related solution objects to deploy Web Parts instead. (In Windows SharePoint Services 2.0, the RemoveWPPack method disabled the specified Web Part package and removed it from the Web Part gallery of the server, and is maintained for backward compatibility.) | |
SetAdminPort | Obsolete. To change the port number of the administration site, update the SPIisSettings object associated with the administration Web application that is returned by SPAdministrationWebApplication.Local, and call the Provision method of the SPWebApplication class. (In Windows SharePoint Services 2.0 the SetAdminPort method set the port number for the administration virtual server.) | |
SetAdminPortAppPool | Obsolete. Use SPAdministrationWebApplication.Local to return the administration Web application through which to change the application pool. (In Windows SharePoint Services 2.0 the SetAdminPortAppPool method specified an application pool in Internet Information Services (IIS) for the administration server.) | |
SetLogThreshold | Obsolete. Use the SetAll(TraceSeverity) method of the SPDiagnosticsService class instead. (In Windows SharePoint Services 2.0 the SetLogThreshold method got a logging threshold value that specified the highest level for which messages are logged in the SharePoint Foundation error log, and is maintained for backward compatibility.) | |
StartDBService | Obsolete. Use the Provision method of the SPWindowsServiceInstance class to provision the database service instead. (In Windows SharePoint Services 2.0 the StartDBService method started the specified database server as a service in the SharePoint Foundation deployment, and is maintained for backward compatibility.) | |
StartTimerService | Obsolete. Use the Provision method of the SPWindowsServiceInstance class to provision the timer service instead. (In Windows SharePoint Services 2.0 the StartTimerService started the SharePoint Timer service for scheduled background processes in the SharePoint Foundation deployment, and is maintained for backward compatibility.) | |
ToString | (Inherited from Object.) | |
UnextendVirtualServer(Uri, Boolean) | Obsolete. To remove SharePoint Foundation from an Internet Information Services (IIS) Web site, remove the IISSettings object from the Web application that the site is serving, and call the Unprovision method of the SPWebApplication class. (In Windows SharePoint Services 2.0 the UnextendVirtualServer method removed SharePoint Foundation from the virtual server, and is maintained for backward compatibility.) | |
UnextendVirtualServer(SPVirtualServer, Boolean) | Obsolete. To remove SharePoint Foundation from an Internet Information Services (IIS) Web site, remove the IISSettings object from the Web application that the site is serving, and call the Unprovision method of the SPWebApplication class. (In Windows SharePoint Services 2.0 the UnextendVirtualServer method removed SharePoint Foundation from the virtual server, and is maintained for backward compatibility.) | |
UpdateConfigDatabaseConnection | Obsolete. Use the Join method of the SPFarm class to add a local computer to the server farm instead. (In Windows SharePoint Services 2.0 the UpdateConfigDatabaseConnection method was used to update the connection to the configuration database, and is maintained for backward compatibility.) | |
UpdateMailSettings | Obsolete. Use the UpdateMailSettings method of the SPAdministrationWebApplication class to update default mail settings instead. (In Windows SharePoint Services 2.0 the UpdateMailSettings method updated the default e-mail settings in the configuration database with the specified values, and is maintained for backward compatibility.) | |
UpgradeApplication | Obsolete. In Windows SharePoint Services 2.0 the UpgradeApplication method upgraded the administrative virtual server, and is maintained for backward compatibility. | |
UpgradeConfigDB() | Obsolete. In Windows SharePoint Services 2.0 the UpgradeConfigDB method upgraded the configuration database, and is maintained for backward compatibility. | |
UpgradeConfigDB(Boolean) | Obsolete. In Windows SharePoint Services 2.0 the UpgradeConfigDB method upgraded the configuration database, and is maintained for backward compatibility. |
Top
Fields
Name | Description | |
---|---|---|
AdminPortMaxValue | Obsolete. Obsolete. In Windows SharePoint Services 2.0 the AdminPortMaxValue field indicated the maximum value that could be used for the administrative port, and is maintained for backward compatibility. | |
AdminPortMinValue | Obsolete. Obsolete. In Windows SharePoint Services 2.0 the AdminPortMaxValue field indicated the minimum value that could be used for the administrative port, and is maintained for backward compatibility. | |
RequestFromAdminPort | Obsolete. Obsolete. In Windows SharePoint Services 2.0 the AdminPortMaxValue field indicated the name of the administration port, and is maintained for backward compatibility. |
Top