SPGlobalAdmin Properties
Include Protected Members
Include Inherited Members
NOTE: This API is now obsolete.
The SPGlobalAdmin type exposes the following members.
Properties
| Name | Description | |
|---|---|---|
.gif "Public property") |
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.) |
.gif "Static member") |
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