Microsoft Docs - Latest Articles

Get started using MySQL MongoDB, PostgreSQL, SQLite, Microsoft SQL Server, or Redis to set up a database on Windows Subsystem for Linux

https://docs.microsoft.com/en-us/windows/wsl/tutorials/wsl-database Learn how to set up MySQL MongoDB, PostgreSQL, SQLite, Microsoft SQL Server, or Redis on the Windows Subsystem for Linux.
Published Date : Tuesday, July 7, 2020

Comparing WSL 2 and WSL 1

https://docs.microsoft.com/en-us/windows/wsl/compare-versions Compare version 1 and version 2 of the Windows Subsystem for Linux. WSL 2 runs an actual Linux kernel, increasing speed and full system call compatibility. WSL 1 works better if your working across BOTH Windows and Linux file systems.
Published Date : Wednesday, July 22, 2020

Serverless REST API with Azure Functions, Node and Azure SQL - Code Samples

https://docs.microsoft.com/en-us/samples/azure-samples/azure-sql-db-node-rest-api/azure-sql-db-node-rest-api/ Creating a modern REST API with Python and Azure SQL, using Flask and Visual Studio Code
Published Date : Tuesday, August 18, 2020

Uninstall-CsMirrorDatabase (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/uninstall-csmirrordatabase Mirror databases enable you to simultaneously maintain two copies of a database: when data is written to Database A, a copy of that data is also written to its mirror database. This provides the ability to instantly replace Database A should that database become unavailable: you can "failover" to the mirror database with minimal disruption to your users and with minimal data loss. Mirror databases can be installed and configured by using the Install-CsMirrorDatabase cmdlet. If you ever need to remove a mirror database, you can do so by using the Uninstall-CsMirrorDatabase cmdlet. Skype for Business Server Control Panel: The functions carried out by the Uninstall-CsMirrorDatabase cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Uninstall-CsDatabase (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/uninstall-csdatabase Skype for Business Server makes extensive use of SQL Server databases such as the Central Management store and the Archiving database. These databases are set up at the same time you install Skype for Business Server or at the same time you install a Skype for Business Server role that requires a database back end. After the databases have been installed, you will rarely need to uninstall them. However, it is possible that you might need to uninstall a Skype for Business Server database at some point; for example, a hardware failure or an issue with network connectivity might make an existing database unusable. Regardless of the reason, the Uninstall-CsDatabase cmdlet provides a way for you to remove or detach any of the SQL Server databases used by Skype for Business Server.
Published Date : Monday, September 25, 2017

Unlock-CsClientPin (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/unlock-csclientpin Skype for Business Server enables users to connect to the system or to join public switched telephone network (PSTN) conferences by using a telephone. Typically, logging on to the system or joining a conference requires the user to enter a user name or password. However, entering a user name and password can be a problem if you are using a phone that does not have an alphanumeric keypad. Because of that, Skype for Business Server enables you to supply users with numeric-only PINs; when prompted, users can then log on to the system or join a conference by entering the PIN instead of a user name and password. This is true, however, only if the user's PIN is unlocked. If a PIN has been locked (either because the user repeatedly failed to log on or because an administrator explicitly locked the PIN), the user will not be able to access the system or join a conference by using PIN authentication. (However, that user will still be able to use an application such as Skype for Business to log on to the system by supplying a user name and password.) If a PIN has been locked, there is only one way to restore the user's ability to access the system by using PIN authentication: the locked PIN must be unlocked by an administrator. This can be done by using the Unlock-CsClientPin cmdlet. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. That means that you will not be able to run the Unlock-CsClientPin cmdlet from a remote instance of Windows PowerShell; that's because your command will not be able to traverse the firewall and access the SQL Server Express database. (However, you can still run the cmdlet locally on the Standard Edition server itself.) To run the Unlock-CsClientPin cmdlet remotely against a Standard Edition server you will need to manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Test-CsDatabase (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/test-csdatabase The Test-CsDatabase cmdlet verifies connectivity to one or more Skype for Business Server databases. When run, the Test-CsDatabase cmdlet reads the Skype for Business Server topology, attempts to connect each of the relevant databases, and then reports back the success or failure of each attempt. If a connection can be made, the cmdlet will also report back such information as the database name, SQL Server version information, and the location of any installed mirror databases. Skype for Business Server Control Panel: The functions carried out by the Test-CsDatabase cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Set-CsUserDatabaseState (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/set-csuserdatabasestate Skype for Business Server employs the user database (also known as the user store) to maintain presence and routing information for Skype for Business Server users. The Set-CsUserDatabaseState cmdlet provides a way for you change the state of one or more user databases: you can use the cmdlet to take a database offline or to bring a disabled database back online. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. In turn, that means that you will not be able to run the Set-CsUserDatabaseState cmdlet from a remote instance of Windows PowerShell. That's because your command will not be able to traverse the firewall and access the SQL Server Express database. You can still run the cmdlet locally (that is, on the Standard Edition server itself). However, to run the Set-CsUserDatabaseState cmdlet remotely you will need to manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Set-CsReportingConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/set-csreportingconfiguration Reporting configuration settings are used to specify the home page for the Skype for Business Server Monitoring Reports; if you are not using Monitoring Reports then there is no reason for you to modify the reporting configuration settings. If you do not know the URL for the Monitoring Reports home page you can determine that URL by doing the following: Open the SQL Server Reporting Services Configuration Manager for the SQL Server instance that contains your monitoring database. In the Configuration Manager, click Report Manager URL and then click the URL for your Monitoring Reports. If you see two URLs, click the one that uses the https protocol. In SQL Server Reporting Services, click LyncServerReports. On the LyncServerReports page, click Reports Home Page. That will take you to the home page for the Monitoring Reports. You can then copy the URL and use that URL in conjunction with the CsReportingConfiguration cmdlets. Skype for Business Server Control Panel: The functions carried out by the Set-CsReportingConfiguration cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Set-CsManagementConnection (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/set-csmanagementconnection Configuration data for Skype for Business Server is stored in the Central Management store. It is crucial that both Windows PowerShell and the management replica services be able to locate this database. When you install Skype for Business Server, a service control point is created in Active Directory Domain Services that provides location information for this database. Typically, computers rely on this service control point in order to connect to the Central Management store. To see the details behind this connection (that is, if you want to know which computer the Central Management store is running on, as well as information about the SQL Server connection to that Central Management store) all you have to do is run the Get-CsManagementConnection cmdlet. For the most part, after your management connection has been set you will not need to change it. However, in case of hardware or software failure, you might need to temporarily use a connection; for example, you can configure a computer to work from the local replica. The Set-CsManagementConnection cmdlet provides a way for you to provide a new location for the Central Management store. Note that any changes you make to Skype for Business Server while using a temporary management connection will not persist if and when you switch back to your original connection. (You can switch back by running the Remove-CsManagementConnection cmdlet.) For example, suppose you decide to temporarily use the file system as your store provider. You change the management connection, and then create several new voice policies (each of which will be instantiated as XML files). When you switch back to your original management connection, these new voice policies will disappear because they were never recorded in the Central Management store now being used. You should also keep in mind that any changes made by running this cmdlet only affect the local computer. You cannot use the Set-CsManagementConnection cmdlet to change the management connection on other computers.
Published Date : Monday, September 25, 2017

Set-CsMonitoringServer (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/set-csmonitoringserver Monitoring Server provides you with two important capabilities. For one, it enables you to maintain information about how, and how often, Enterprise Voice is used in your organization. This information is tracked by using call detail recording (CDR), which records such things as who made a call, who that person called and how long the call lasted. (The actual conversation itself is not recorded.) In addition to that, you can also use Monitoring Server to keep track of Quality of Experience (QoE) data for your Enterprise Voice calls. As the name implies, Quality of Experience data provides information about the quality of a call, measuring such items as packet loss, call degradation, network bitrate and jitter. When you install Monitoring Server you must specify the location of the SQL Server database used to store CDR and QoE data. Optionally, you can also install SQL Server Reporting Services and the Monitoring Server Report Pack; these two items enable you to access a website that generates standard monitoring reports for you. As a general rule, after Monitoring Server has been installed and configured you will not need to change the location of either the back-end database or the reporting URL. However, if you do need to change the location of one (or both) of these items, you can do so by running the Set-CsMonitoringServer cmdlet.
Published Date : Monday, September 25, 2017

Set-CsConfigurationStoreLocation (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/set-csconfigurationstorelocation Active Directory Domain Services uses service control points (SCP) to help computers locate services. For example, when you install Skype for Business Server, a service control point is created that provides location information for the Central Management store used to maintain Skype for Business Server data. Computers that need access to the database connect to Active Directory and use the information contained in the SCP to help them locate the correct computer and the correct instance of SQL Server. As noted, when you install Skype for Business Server an SCP that for the Central Management store is automatically created for you. If you need to move that database to another computer or if you need to move that database to a different instance of SQL Server, then you will need to update the corresponding service control point. That's a task that can be carried out by using the Set-CsConfigurationStoreLocation cmdlet. When you run it, the Set-CsConfigurationStoreLocation cmdlet searches Active Directory for the computer specified by the SqlServer parameter. The cmdlet then sets the store location to the FQDN of that computer.
Published Date : Monday, September 25, 2017

Set-CsArchivingConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/set-csarchivingconfiguration Many organizations find it useful to keep a transcript of all the IM sessions and conferences their users participate in. For other organizations, it's mandatory to keep such transcripts; for example, many organizations in the financial world are required by law to keep copies of all their electronic communications. In order to archive instant messages, you must set up at least one Archiving Server. After the Archiving Server is set up, you must perform two additional steps. First, you need to enable archiving at the global scope (for details, see the Set-CsArchivingConfiguration cmdlet help topic). Optionally, you can also configure custom archiving settings for different sites. Second, you must use archiving policies to indicate which users will have their IM sessions archived. IM sessions will not be archived unless a policy is in force that requires IM sessions to be archived. When you install Skype for Business Server, a collection of global archiving configuration settings will be created for you; by default, these settings will apply to your entire organization. Alternatively, you can use the New-CsArchivingConfiguration cmdlet to create custom configuration settings on a site-by-site basis. Either way, you can use the Set-CsArchivingConfiguration cmdlet to modify the property values of an existing collection or archiving configuration settings.
Published Date : Monday, September 25, 2017

Set-CsClientPin (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/set-csclientpin Skype for Business Server enables users to connect to the system or to join public switched telephone network (PSTN) conferences by using a telephone. Typically, logging on to the system or joining a conference requires the user to enter a user name or password. However, entering a user name and password can be a problem if you are using a phone that does not have an alphanumeric keypad. Because of that, enables you to supply users with numeric-only PINs; when prompted, users can then log on to the system or join a conference by entering the PIN instead of a user name and password. Users are not assigned a PIN when they are enabled for Skype for Business Server; that means that, by default, users cannot access the system by using PIN authentication. Users can obtain a PIN from the Dial-In Conferencing webpage; alternatively, administrators can assign each user a PIN by using the Set-CsClientPin cmdlet. With the Set-CsClientPin cmdlet you can either assign a user a specific PIN or you can allow Skype for Business Server to generate a PIN for you. To auto-generate a PIN, simply omit the PIN parameter when calling the Set-CsClientPin cmdlet. If you do that, a new PIN will be generated and the user's Identity and his or her new PIN will be displayed on the screen when the command completes. Note that the PINs you explicitly assign must meet the conditions specified in the PIN authentication policy governing the user in question; for example, the PIN must have at least as many digits as specified by the MinPasswordLength property. Also note that PINs can contain only numbers; letters or other non-numeric characters are not allowed. When you set a client PIN using the Set-CsClientPin cmdlet, the PIN history count is not enforced. For example, suppose a user has a PIN number of 12345 and their client PIN policy prevents them from immediately reusing the same PIN number. If that user tries to renew his or her client PIN using the Dial-In Conferencing Web page, any attempt to reuse the same PIN number (12345) will be rejected. However, by using the Set-CsClientPin cmdlet an administrator can issue that user the PIN 12345. That's because the Set-CsClientPin cmdlet is not bound by the PIN policy history count. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. That means that you will not be able to run the Set-CsClientPin cmdlet from a remote instance of Windows PowerShell; that's because your command will not be able to traverse the firewall and access the SQL Server Express database. (However, you can still run the cmdlet locally on the Standard Edition server itself.) To run the Set-CsClientPin cmdlet remotely against a Standard Edition server you will need to manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Set-CsArchivingServer (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/set-csarchivingserver Archiving Servers provide a way for you to save complete transcripts of the instant messaging (IM) sessions that take place in your organization. In some organizations, it can be useful to have copies of these IM sessions. In other organizations, where records must be kept of all electronic communications, it can be mandatory to have copies of these IM sessions. Archiving Server records the transcript of each IM session (as well as information about when the session took place and who participated in the session) in a SQL Server database. The location of this database must be specified when you install Archiving Server; in most cases, you will not need to change the location of that database. However, if a hardware failure or other problem should occur, you can point Archiving Server to a new database by using the Set-CsArchivingServer cmdlet.
Published Date : Monday, September 25, 2017

Revoke-CsClientCertificate (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/revoke-csclientcertificate Client certificates provide an alternate way for users to be authenticated by Skype for Business Server. Instead of providing a user name and password, users present the system with an X.509 certificate. (This certificate must have a subject name or subject alternative name that identifies the user.) To be authenticated, users only need to type in a personal identification number (PIN); it's typically easier for a mobile phone user to type in a PIN than to type in an alphanumeric user name and/or password. At any time administrators can revoke the client certificates that have been issued to a user by using the Revoke-CsClientCertificate cmdlet. The Revoke-CsClientCertificate cmdlet revokes all the client certificates issued to the user in question from the server. The Revoke-CsClientCertificate cmdlet does not delete certificates from the client device itself; certificates are only deleted from the server. However, this is sufficient to prevent a client from using certificates for authentication purposes: if a certificate cannot be found on the server than the authentication request will be denied. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. In turn, that means that you will not be able to run the Revoke-CsClientCertificate cmdlet from a remote instance of Windows PowerShell; that's because your command will not be able to traverse the firewall and access the SQL Server Express database. (However, you can still run the cmdlet locally; that is, on the Standard Edition server itself.) If you are using Standard Edition and need to run the Revoke-CsClientCertificate cmdlet remotely you must manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Search-CsClsLogging (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/search-csclslogging The centralized logging service (which replaces the OCSLogger and OCSTracer tools used in Microsoft Lync Server 2010) provides a way for administrators to manage logging and tracing for all computers and pools running Skype for Business Server. Centralized logging enables administrators to stop, start and configure logging for one or more pools and computers by using a single command; for example, you can use one command to enable Address Book service logging on all your Address Book servers. This differs from the OCSLogger and OCSTracer tools, which had to be individually managed (including individually stopped and started) on each server. In addition, the centralized logging service also provides a way for administrators to search trace logs from the command, using the Windows PowerShell command-line interface and the Search-CsClsLogging cmdlet. Centralized logging is built around a series of predefined scenarios that offer a more finely-targeted approach to logging than offered in previous versions of Skype for Business Server. These scenarios predetermine the server components and logging for you; as a result, an administrator enabling the RGS scenario can be confident that he or she will only log information relevant to the Response Group service and not to, say, the audio conferencing provider service. The Search-CsClsLogging cmdlet provides a command line option for searching the log files generated by the centralized logging service. Skype for Business Server Control Panel: The functions carried out by the Search-CsClsLogging cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Remove-CsReportingConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/remove-csreportingconfiguration Reporting configuration settings are used to specify the home page for the Skype for Business Server Monitoring Reports; if you are not using Monitoring Reports then there is no reason for you to modify the reporting configuration settings. Skype for Business Server Control Panel: The functions carried out by the Remove-CsReportingConfiguration cmdlet are not available in the Skype for Business Server.
Published Date : Monday, September 25, 2017

Remove-CsManagementConnection (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/remove-csmanagementconnection Configuration data for Skype for Business Server is stored in the Central Management store; it is crucial that both Windows PowerShell and the management replication services be able to locate this database. When you install Skype for Business Server, a service control point is created in Active Directory Domain Services that provides location information for this database. Typically, computers rely on this service control point in order to connect to the Central Management store. To see the details behind this connection (that is, if you want to know which computer the Central Management store is running on, as well information about the SQL Server connection to that Central Management store), you can run the Get-CsManagementConnection cmdlet. As a general rule, you will not need to change your management connection. However, it is possible that you might need to temporarily use a new management connection. When you are ready to switch back to the default connection all you need to do is run the Remove-CsManagementConnection cmdlet; this cmdlet erases the current connection information and replaces it with the connection information stored in the Active Directory service control point. This means you do not have to recreate the original connection information; the Remove-CsManagementConnection cmdlet will do that for you. Note that no problems will occur if you call this cmdlet while using the default connection. If you do so, you will simply continue to use the default connection information stored in Active Directory. Note, too that this cmdlet only affects the management connection information for your current Windows PowerShell session: any changes to the management connection are limited to your local computer and local instance of Windows PowerShell.
Published Date : Monday, September 25, 2017

Remove-CsConfigurationStoreLocation (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/remove-csconfigurationstorelocation Active Directory Domain Services uses service control points (SCP) to help computers locate services. For example, when you install Skype for Business Server, an SCP is created that provides location information for the Central Management store used to maintain Skype for Business Server data. Computers that need access to the database connect to Active Directory and use the information contained in the SCP to help them locate the correct computer and the correct instance of SQL Server. As noted, when you install Skype for Business Server, an SCP for the Central Management store is automatically created for you. Typically, you do not want to delete that SCP; if you do, computers will not be able to locate the database. However, there might be times (perhaps when troubleshooting a problem) when you will need to delete the SCP. To do that, use the Remove-CsConfigurationStoreLocation cmdlet. After the SCP has been deleted, you can recreate it (or create a new service control point) by using the Set-CsConfigurationStoreLocation cmdlet.
Published Date : Monday, September 25, 2017

New-CsReportingConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/new-csreportingconfiguration Reporting configuration settings are used to specify the home page for the Skype for Business Server Monitoring Reports; if you are not using Monitoring Reports then there is no reason for you to modify the reporting configuration settings. If you do not know the URL for the Monitoring Reports home page you can determine that URL by doing the following: Open the SQL Server Reporting Services Configuration Manager for the SQL Server instance that contains your monitoring database. In the Configuration Manager, click Report Manager URL and then click the URL for your Monitoring Reports. If you see two URLs, click the one that uses the https protocol. In SQL Server Reporting Services, click LyncServerReports. On the LyncServerReports page, click Reports Home Page. That will take you to the home page for the Monitoring Reports. You can then copy the URL and use that URL in conjunction with the CsReportingConfiguration cmdlets. Skype for Business Server Control Panel: The functions carried out by the New-CsReportingConfiguration cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

New-CsArchivingConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/new-csarchivingconfiguration Many organizations find it useful to keep a transcript of all the IM sessions carried out by their users. For other organizations, it's mandatory to keep such transcripts; for example, many organizations in the financial world are required by law to keep copies of all their electronic communications. Skype for Business Server gives you flexibility when it comes to archiving IM and web conferencing sessions. If you have deployed Archiving Server, you can use the various CsArchivingConfiguration cmdlets to enable and disable IM session archiving and to manage your archiving database. You can also suspend IM should archiving fail; this helps to ensure that you keep a record of all your electronic communications. When you install Skype for Business Server, a collection of global archiving settings will be created for you; by default, these settings will apply to your entire organization. Alternatively, you can use the New-CsArchivingConfiguration cmdlet to create custom configuration settings on a site-by-site basis.
Published Date : Monday, September 25, 2017

Invoke-CsArchivingDatabasePurge (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/invoke-csarchivingdatabasepurge Many organizations find it useful to keep a transcript of all the IM sessions carried out by their users (or a selected subset of users). For other organizations, it's mandatory to keep such transcripts. For example, many organizations in the financial world are required by law to keep copies of all their electronic communications. If you have enabled archiving in your organization and if you have chosen to use Skype for Business Server as your archiving backend, then your archiving records will be stored in the SQL Server database LcsLog. (Alternatively, archiving records can be stored using Microsoft Exchange instead. See the help topic for the New-CsArchivingConfiguration cmdlet for more information.) Over time, the archiving database has the potential to grow extremely large. Because of that, Skype for Business Server provides two ways for administrators to purge older records from the database: 1) you can configure Skype for Business Server to automatically delete older archiving records each day; and/or, 2) you can use the Invoke-CsArchivingDatabasePurge cmdlet at any time to delete archiving records from the LcsLog database. (The Invoke-CsArchivingDatabasePurge cmdlet does this by calling the SQL Server stored procedures RtcCleanupTempConference and RtcCleanupDB as well as deleted stored meeting content.) When you call the Invoke-CsArchivingDatabasePurge cmdlet you must specify the service location of the archiving database where the archiving records are stored (for example, ArchivingDatabase:atl-sql-001.litwareinc.com); you must also indicate the minimum age (in hours) of the archiving records to be deleted. For example, if you specify a minimum age of 24 hours then all archiving records older than 24 hours will be deleted from the database. Note that these records will be deleted even if the purging has been disabled for the specified database. (That is, the EnablePurging property in the archiving configuration settings has been set to False.) The EnablePurging property only controls the automated purging of archiving records; it has no effect on the Invoke-CsArchivingDatabasePurge cmdlet. Skype for Business Server Control Panel: The functions carried out by the Invoke-CsArchivingDatabasePurge cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Invoke-CsPoolFailOver (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/invoke-cspoolfailover The pool failover process provides a way for administrators to quickly restore service to users if the Registrar pool they have logged on to should suddenly become unavailable. If a pool fails, users will automatically be signed off from Skype for Business Server; if they immediately try to log back on, they will be redirected to their specified backup pool. To restore service to these users, administrators can run the Invoke-CsPoolFailOver cmdlet against the pool that is not currently available. Doing this will allow users to sign on to Skype for Business Server using the designated backup pool, and give these users access to all Skype for Business Server services and functionality. Note that users will not be rehomed on the backup pool; they will simply be allowed to log on and make use of that pool until their home pool has been restored. For example, if Pool A fails, users will be able to log on to Pool B (with complete functionality) until Pool A has been restored. When the failed pool is once more up and running, administrators can then run the Invoke-CsPoolFailBack cmdlet in order to "fail back" users of that pool. If a user is currently logged on to the backup pool then he or she will be redirected back to their home pool after service has been restored. Pool failover can only be invoked if you have assigned a backup pool to the failed pool. Skype for Business Server Control Panel: The functions carried out by the Invoke-CsPoolFailOver cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Install-CsDatabase (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/install-csdatabase Skype for Business Server makes extensive use of SQL Server databases, ranging from the Central Management store to the Archiving database. As a general rule, these databases are set up at the same time you Skype for Business Server or at the same time you install a Skype for Business Server role (such as Monitoring Server) that requires a database back end. After installation has taken place these databases typically will not need to be reinstalled or moved to new locations. On rare occasions, however, you might need to manually install a Skype for Business Server database; this could be because you need to move a database to another server, or because a setup-related problem failed to install the database for you. The Install-CsDatabase cmdlet provides a way for you to install any of the SQL Server databases used by Skype for Business Server. When running the Install-CsDatabase cmdlet there are basically three different ways to handle the configuration of the database being installed: Option 1 -- Run the cmdlet without including a parameter that specifies the database paths. When the Install-CsDatabase cmdlet is run without the DatabasePaths or the UseDefaultSqlPath parameter the cmdlet uses a built-on algorithm to choose the storage location for the database logs and data files. Note that this built-in algorithm works with a stand-alone SQL Server, it will not work with a SQL Server cluster. To install a database on a SQL Server cluster your command must include either the DatabasePaths or the UseDefaultSqlPath parameter Option 2 -- Run the cmdlet along with the DatabasePaths parameter. When the Install-CsDatabase is cmdlet run with the DatabasePaths parameter the built-in algorithm is not used to choose the storage location for the database logs and data files. Instead, administrators can select the location for these logs and data files. To install both data files and SQL Server logs in the same location, simply specify the path to the folder where this data should be stored. For example: -DatabasePaths C:\SqlData To store data files in one location and log files in a second location, specify the path to each folder, separating the two locations by using a comma (be careful not to put a blank space before or after the comma): -DatabasePaths C:\SqlLogs,D:\SqlData The log files will always be stored on the first location specified, while data files will be stored in the second location. In a pool backend, certain log files might be stored on a drive all by themselves. If you have a pool backend with a single drive, files will be distributed like this: Drive 1 - Rtcdyn log; Rtc log; other logs; other data. If you have two drives, files will be distributed like this: Drive 1 - Rtcdyn log; Rtc log. Drive 2 - Other logs; other data. With three drives: Drive 1 - Rtcdyn log. Drive 2 - Rtc log. Drive 3 - Other logs; other data. And with four drives: Drive 1 - Rtcdyn log. Drive 2 - Rtc log. Drive 3 - Other logs. Drive 4 - Other data. Option 3 -- Run the cmdlet along with the UseDefaultSqlPaths parameter. When the Install-CsDatabase cmdlet is run using the UseDefaultSqlPaths parameter, the built-in algorithm is not used to choose the storage locations for the database logs and data files. Instead, log and data files are stored in the locations specified by the SQL Server defaults path (these paths must be configured in advanced by a SQL Server administrator). Data files will be stored in the default SQL Server data file location while log files will be stored in the default SQL Server log file location. Before running the Install-CsDatabase cmdlet you should make sure that the RTCUniversalServerAdmins groups has not been assigned as the database owner. If that group is listed as the owner the group could possibly be deleted when you call the Install-CsDatabase cmdlet.
Published Date : Monday, September 25, 2017

Install-CsMirrorDatabase (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/install-csmirrordatabase Mirror databases enable you to simultaneously maintain two copies of a database: when data is written to Database A, a copy of that data is also written to its mirror database. This provides the ability to instantly replace Database A should that database become unavailable: you can "failover" to the mirror database with minimal disruption to your users and with minimal data loss. After you have installed your primary databases you can then install and configure mirror databases by using the Install-CsMirrorDatabase cmdlet. By default, the Install-CsMirrorDatabase cmdlet installs and configures mirror databases for all the Skype for Business Server databases housed on the specified server. However, you can use the DatabaseType or the ExcludeDatabaseList parameters to specify exactly which mirror databases should or should not be installed. DatabaseType enables you to specify only the databases that should be installed; ExcludeDatabaseList lets you specify the databases that should not be installed. Skype for Business Server Control Panel: The functions carried out by the Install-CsMirrorDatabase cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Move-CsRgsConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/move-csrgsconfiguration The Response Group application provides a way for you to automatically route phone calls to entities such as a help desk or customer support line. When someone calls a designated phone number, that call can be automatically routed to the appropriate set of Response Group agents. Alternatively, the call might be routed to an interactive voice response (IVR) queue. In that queue, the caller would be asked a series of questions (for example, "Are you calling about an existing order?") and then, based on the answers to those questions, be given the asked-for information or be routed to a Response Group agent. If you are currently running the Response Group application on legacy server, the Move-CsRgsConfiguration cmdlet provides a way for you to migrate this service to newer vesion server. To migrate the service, you need to call the Move-CsRgsConfiguration cmdlet and specify: 1) the fully qualified domain name (FQDN) for the existing version of the Response Group application (the Source); and, 2) the FQDN for the new Skype for Business Server version of the service (the Destination). Move-CsRgsConfiguration will then move all the configuration settings, audio files, and contact objects from the existing version (for example, Office Communications Server 2007 R2 or Lync Server 2010) to newer version. After the service has been migrated, all calls to a Response Group phone number will be handled by the newer server. Calls will no longer be handled by the previous version of the service. Note If you are running this service on Office Communications Server 2007 R2 or Lync Server 2010, before you can run Move-CsRgsConfiguration, you must first install the Windows Management Instrumentation (WMI) Backward Compatibility interfaces package; this application is installed by running OCSWMIBC.msi. The file OCSWMIBC.msi can be found on the installation DVD in the Setup folder. Note If Office Communications Server 2007 is running Microsoft SQL Server 2005 then, before you attempt to migrate the Response Group application, you must install the Microsoft SQL Server 2005 Native Client on the computer where you will be running the Move-CsRgsConfiguration cmdlet. If the Native Client is not installed you will receive the error message "Cannot access WMI settings" when you call Move-CsRgsConfiguration. Note The Move-CsRgsConfiguration cmdlet is only for migrating from legacy version to newer version; you cannot use this cmdlet to migrate between the same version (for example, one instance of Skype for Business Server 2015 to a new instance of Skype for Business Server 2015). That type of migration can only be done by using the new Import-CsRgsConfiguration and Export-CsRgsConfiguration cmdlets.
Published Date : Monday, September 25, 2017

Invoke-CsQoEDatabasePurge (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/invoke-csqoedatabasepurge Quality of Experience (QoE) metrics track the quality of audio and video calls made in your organization, including such things as the number of network packets lost, background noise, and the amount of "jitter" (differences in packet delay). These metrics are stored in a database apart from other data (such as call detail records), which allows you to enable and disable QoE independent of other data recording. Quality of Experience records are stored in the SQL Server database LcsQoEMetrics. Over time, this database has the potential to grow extremely large. Because of that, Lync Server provides two ways for administrators to purge older records from the database: 1) you can configure Skype for Business Server to automatically delete older QoE records each day; and/or, 2) you can use the Invoke-CsQoEDatabasePurge cmdlet at any time to delete Quality of Experience records from the LcsQoEMetrics database. (The Invoke-CsQoEDatabasePurge cmdlet does this by calling the SQL Server stored procedure QoePurgeOutdatedReports.) When you call the Invoke-CsQoEDatabasePurge cmdlet you must specify the service location of the monitoring database where the QoE records are stored (for example, MonitoringDatabase:atl-sql-001.litwareinc.com); you must also indicate the minimum age (in days) of the records to be deleted. For example, if you specify a minimum age of 10 days then all QoE records older than 10 days will be deleted from the database. Note that these records will be deleted even if the purging has been disabled for the specified database. (That is, the EnablePurging property in the QoE configuration settings has been set to False.) The EnablePurging property only controls the automated purging of archiving records; it has no effect on the Invoke-CsQoEDatabasePurge cmdlet. Skype for Business Server Control Panel: The functions carried out by the Invoke-CsQoEDatabasePurge cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Invoke-CsCdrDatabasePurge (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/invoke-cscdrdatabasepurge Call detail recording (CDR) provides a way for you to track usage of Skype for Business Server capabilities such as Voice over IP (VoIP) phone calls; instant messaging (IM); file transfers; audio/video (A/V) conferencing; and application sharing sessions. CDR keeps usage information: it logs information such as the parties involved in the call; the length of the call; and whether or not any files were transferred. However, CDR does not make a recording of the call itself. CDR also keeps track of call error information: detailed diagnostic data for both peer-to-peer sessions and for conferencing calls. Call detail records are stored in the SQL Server database LcsCDR. Over time, this database has the potential to grow extremely large. Because of that, Skype for Business Server provides two ways for administrators to purge older records from the database: 1) you can configure Skype for Business Server to automatically delete older CDR records each day; and/or, 2) you can use the Invoke-CsCdrDatabasePurge cmdlet at any time to delete CDR records from the LcsCDR database. (The Invoke-CsCdrDatabasePurge cmdlet does this by calling the SQL Server stored procedure RtcCleanupDB.) When you call the Invoke-CsCdrDatabasePurge cmdlet you must specify the service location of the monitoring database where the CDR records are stored (for example, MonitoringDatabase:atl-sql-001.litwareinc.com); you must also indicate the minimum age (in days) of the call detail and diagnostic data records to be deleted. For example, if you specify a minimum age of 10 days for call detail records, then all call detail records older than 10 days will be deleted from the database. Note that these records will be deleted even if the purging has been disabled for the specified database. (That is, the EnablePurging property in the CDR configuration settings has been set to False.) The EnablePurging property only controls the automated purging of CDR records; it has no effect on the Invoke-CsCdrDatabasePurge cmdlet. Skype for Business Server Control Panel: The functions carried out by the Invoke-CsCdrDatabasePurge cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Invoke-CsManagementServerFailover (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/invoke-csmanagementserverfailover The Invoke-CsManagementServerFailover cmdlet enables administrators to "failover" the Central Management Server (CMS). You can only invoke the failover to the database defined in the Topology Builder. The Invoke-CsManagementServerFailover cmdlet provides two methods for failing over the CMS: Failover when the CMS is available by running the cmdlet without any target database parameters as in Example 1. Failover when the CMS is unavailable (in disaster recovery mode) by specifying the BackupSqlServerFqdn parameter and the corresponding BackupSqlInstanceName parameter as in Example 2. If the database defined in the Topology Builder is mirrored, add the BackupMirrorSqlServerFqdn and BackupMirrorSqlInstanceName parameters. Skype for Business Server Control Panel: The functions carried out by the Invoke-CsManagementServerFailover cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Lock-CsClientPin (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/lock-csclientpin Skype for Business Server enables users to connect to the system, or to join public switched telephone network (PSTN) conferences by using a telephone. Typically, logging on to the system or joining a conference requires the user to enter a user name or password. However, entering a user name and password can be a problem if you are using a phone that does not have an alphanumeric keypad. Because of that, Skype for Business Server enables you to supply users with numeric-only PINs; when prompted, users can then log on to the system or join a conference by entering the PIN instead of a user name and password. As a security measure, Skype for Business Server enables you to lock a user's PIN. When a PIN is locked, the user will no longer be able to use that PIN to access the system or join a conference. (However, that user will still be able to access the system and join conferences by using an application such as Skype for Business and by supplying a user name and password.) After a PIN has been locked, the only way to restore the PIN (and the user's access privileges) is for an administrator to unlock the PIN. This can be done by using the Unlock-CsClientPin cmdlet. The Lock-CsClientPin cmdlet enables administrators to temporarily disable the ability of a user to access the system by using PIN authentication. PINs can also be locked by the system: if a user repeatedly fails to log on to the system, their PIN will automatically be locked and, again, will require unlocking by an administrator. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. That means that you will not be able to run the Lock-CsClientPin cmdlet from a remote instance of Windows PowerShell; that's because your command will not be able to traverse the firewall and access the SQL Server Express database. (However, you can still run the cmdlet locally on the Standard Edition server itself.) To run the Lock-CsClientPin cmdlet remotely you will need to manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Import-CsUserData (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/import-csuserdata The Import-CsUserData cmdlet is used to import previously-saved user data and/or conference directory data to Skype for Business Server. Note that this data must have been exported by using the Export-CsUserData cmdlet. To make sure changes happen after this cmdlet, FE services need to be stopped in all FE servers in the pool firstly then be restarted at the same time after executing Import-CsUserdata cmdlet. Skype for Business Server Control Panel: The functions carried out by the Import-CsUserData cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Import-CsPersistentChatData (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/import-cspersistentchatdata The Persistent Chat service (which replaces the Group Chat service used in Microsoft Lync Server 2010) provides organizations with messaging and collaboration capabilities similar to those found in Internet discussion forums: users can exchange messages in real-time, yet can also revisit and restart those conversations at any time. Conversations can be based around specific topics, and these conversations can be made available to everyone or to only a selected set of users. Likewise, individual chat rooms can be configured so that anyone can post a message or configured so that only designated presenters can post messages. If you are currently running Lync Server 2010, you can migrate your current Group Chat implementation by using the Export-CsPersistentChatData cmdlet to export your existing Group Chat configuration settings, then use the Import-CsPersistentChatData cmdlet to migrate that information to Lync Server 2013 and the Persistent Chat service. Note that the Export-CsPersistentChatData cmdlet gives you the option of importing all your Group Chat settings and data or only a portion of your Group Chat settings and data; for example, you can export (and then import) your Group Chat categories and chat rooms without exporting all the content associated with those categories and chat rooms. Although primarily intended for migration purposes, the CsPersistentChatData cmdlets can also be used to manage Persistent Chat data on Skype for Business Server. Skype for Business Server Control Panel: The functions carried out by the Import-CsPersistentChatData cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Get-CsUserDatabaseState (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/get-csuserdatabasestate Skype for Business Server employs the user database (also known as the user store) to maintain presence and routing information for Skype for Business Server users. The Get-CsUserDatabaseState cmdlet provides a way to verify the current status (either online or offline) for any of the user databases currently in use in your organization. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. In turn, that means that you will not be able to run the Get-CsUserDatabaseState cmdlet from a remote instance of Windows PowerShell. That's because your command will not be able to traverse the firewall and access the SQL Server Express database. You can still run the cmdlet locally (that is, on the Standard Edition server itself). However, to run the Get-CsUserDatabaseState cmdlet remotely you will need to manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Get-CsTopology (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/get-cstopology The Get-CsTopology cmdlet returns information about how Skype for Business Server has been set up and configured. Called without any additional parameters, the cmdlet provides an overview of your Skype for Business Server infrastructure; in that scenario, the cmdlet gives you an overall view of such things as your domains, your sites, and the computers running Skype for Business Server services and server roles. Alternatively, you can pass the output of the Get-CsTopology cmdlet to the Select-Object cmdlet; this enables you to access detailed information about a portion of your topology. For example, the following command provides detailed information regarding the SQL Server instances used by Skype for Business Server: Get-CsTopology | Select-Object -ExpandProperty SqlInstances You can also use the AsXml parameter to return detailed information about your entire topology in XML format.
Published Date : Monday, September 25, 2017

Get-CsReportingConfiguration (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/get-csreportingconfiguration Reporting configuration settings are used to specify the home page for the Skype for Business Server Monitoring Reports; if you are not using Monitoring Reports then there is no reason for you to modify the reporting configuration settings. The functions carried out by the Get-CsReportingConfiguration cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Get-CsManagementConnection (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/get-csmanagementconnection Configuration data for Skype for Business Server is stored in the Central Management store; it is crucial that both Windows PowerShell and the management replica services be able to locate this database. When you install Skype for Business Server, a service control point is created in Active Directory Domain Services that provides location information for this database. Typically, computers rely on this service control point in order to connect to the Central Management store. To see the details behind this connection (that is, if you want to know which computer the Central Management store is running on, as well information about the SQL Server connection to that Central Management store) you can run the Get-CsManagementConnection cmdlet. If you have used the Set-CsManagementConnection cmdlet to set up a temporary management connection for your current instance of Windows PowerShell (for example, in order to work from the local replica), the Get-CsManagementConnection cmdlet will report back information for that temporary connection. By comparison, the Get-CsConfigurationStoreLocation cmdlet always returns information for the service control point in Active Directory, regardless of where the local management connection is pointed.
Published Date : Monday, September 25, 2017

Get-CsConfigurationStoreLocation (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/get-csconfigurationstorelocation Active Directory Domain Services uses service control points (SCP) to help computers locate services. For example, when you install Skype for Business Server, a service control point is created that provides location information for the Central Management store used to maintain Skype for Business Server data. Computers that need access to the database connect to Active Directory and use the information contained in the SCP to help them locate the correct computer and the correct instance of SQL Server. The Get-CsConfigurationStoreLocation cmdlet is used to report back the SQL Server path (for example, atl-sql-001.litwareinc.com/rtc) to the computer running the Central Management store.
Published Date : Monday, September 25, 2017

Get-CsClientPinInfo (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/get-csclientpininfo Skype for Business Server enables users to connect to the system or to join public switched telephone network (PSTN) conferences by using a telephone. Typically, logging on to the system or joining a conference requires the user to enter a user name or password. However, entering a user name and password can be an issue if you are using a phone that does not have an alphanumeric keypad. Because of that, Skype for Business Server enables you to supply users with numeric-only PINs; when prompted, users can then log on to the system or join a conference by entering the PIN instead of a user name and password. Administrators can retrieve the PIN settings for a user, or a group of users, by running the Get-CsClientPinInfo cmdlet. Note that there is no way for an administrator to retrieve the PIN that has been assigned to a user. If a user forgets his or her PIN, that user will not be able to use PIN authentication to access the system until an administrator has assigned them a new PIN or the user has obtained a new PIN from the Dial-In Conferencing webpage. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. That means that you will not be able to run the Get-CsClientPinInfo cmdlet from a remote instance of Windows PowerShell; that's because your command will not be able to traverse the firewall and access the SQL Server Express database. (However, you can still run the cmdlet locally on Standard Edition server.) To run the Get-CsClientPinInfo cmdlet remotely against a Standard Edition server you will need to manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Get-CsClientAccessLicense (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/get-csclientaccesslicense The Get-CsClientAccessLicense cmdlet enables administrators to monitor use of their Skype for Business Server client licenses; this is done by showing client license usage (based on user registrations) during a specified period of time. Note that the cmdlet does not manage your client licenses for you; for example, it will not tell you that you need additional licenses. Instead, the cmdlet simply returns information about the number of licenses that were in use during the specified time period. You cannot use the Get-CsClientAccessLicense cmdlet unless you have enabled the Monitoring Service and call detail recording; that's because registration information is stored in the call detail recording database. Note, too that, as the name suggests, the Get-CsClientAccessLicense cmdlet only returns only returns information about your client licenses. If you need information about your server licenses, you can use the Get-CsService cmdlet to return the fully qualified domain names (FQDN) of all your Skype for Business Server databases. If the FQDN of a front End server matches the FQDN of a backend database that means you have a Standard license. If the two FQDNs do not match then that means that you have an Enterprise license. You might also encounter instances when the Get-CsClientAccessLicense cmdlet returns incorrect license counts. For example: Licenses can be overcounted if a mobile user logs on from more than one location using a desktop client. Licenses can be undercounted if a user connects with a mobile client, because the IP address for the device cannot be determined. In addition, licenses can be overcounted if the mobile device changes its IP address during a session. Licenses can be counted twice for PSTN calls to a Skype for Business client or for a call from a Skype for Business client to a PSTN phone. This is due to the fact that both the Skype for Business user account and the PSTN phone number are used when determining the number of licenses employed in the session. Licenses for Skype for Business phones might not be counted if the phone was logged on to the system before you ran the license usage query. If a user joins a conference using a PSTN phone, a single license usage will be recorded for that call. However, no license is actually required to join a conference using a PSTN phone. The functions carried out by the Get-CsClientAccessLicense cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Get-CsClientCertificate (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/get-csclientcertificate Client certificates provide an alternate way for users to be authenticated by Skype for Business Server. Instead of providing a user name and password, users present the system with an X.509 certificate. (This certificate must have a subject name or subject alternative name that identifies the user.) To be authenticated, users only need to type in a personal identification number (PIN); it's typically easier for mobile phone users to type in a PIN than to type in an alphanumeric user name and/or password. The Get-CsClientCertificate cmdlet provides a way for administrators to retrieve information about the Skype for Business Server client certificates that have been issued to their users. This information includes both the date and time that the certificate was issued in addition to the date and time when the certificate will expire. Note that, by default, the firewall exceptions for SQL Server Express are not enabled when you install the Standard Edition of Skype for Business Server. That means that you will not be able to run the Get-CsClientCertificate cmdlet from a remote instance of Windows PowerShell; that's because your command will not be able to traverse the firewall and access the SQL Server Express database. (However, you can still run the cmdlet locally on the Standard Edition server itself.) If you need to run the Get-CsClientCertificate cmdlet remotely against a Standard Edition server you must manually enable the firewall exceptions for SQL Server Express.
Published Date : Monday, September 25, 2017

Export-CsPersistentChatData (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/export-cspersistentchatdata The Persistent Chat service (which replaces the Group Chat service used in Microsoft Lync Server 2010) provides organizations with messaging and collaboration capabilities similar to those found in Internet discussion forums: users can exchange messages in real-time, yet can also revisit and restart those conversations at any time. Conversations can be based around specific topics, and these conversations can be made available to everyone or to only a selected set of users. Likewise, individual chat rooms can be configured so that anyone can post a message or configured so that only designated presenters can post messages. If you are currently running Lync Server 2010, you can migrate your current Group Chat implementation by using the Export-CsPersistentChatData cmdlet to export your existing Group Chat configuration settings, then use the Import-CsPersistentChatData cmdlet to migrate that information to Skype for Business Server and the Persistent Chat service. Note that the Export-CsPersistentChatData cmdlet gives you the option of importing all your Group Chat settings and data or only a portion of your Group Chat settings and data; for example, you can export (and then import) your Group Chat categories and chat rooms without exporting all the content associated with those categories and chat rooms. Although primarily intended for migration purposes, the CsPersistentChatData cmdlets can also be used to manage Persistent Chat data on Skype for Business Server. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt: Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Export-CsPersistentChatData"} The functions carried out by the Export-CsPersistentChatData cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Export-CsUserData (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/export-csuserdata The Export-CsUserData cmdlet provides a way for administrators to export user data and/or conference directory for a Skype for Business Server pool. That data, which can be saved in the user data format used by Skype for Business Server can then be imported by using the Import-CsUserData cmdlet. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt: Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Export-CsUserData"} The functions carried out by the Export-CsUserData cmdlet are not available in the Skype for Business Server Control Panel. NOTE: URNs that have the following characters back slash (\) and forward slash (/) will cause the powershell command to fail and stop the export of the user data until that point.The following error is reported: Export-CsUserData : "urn:hcd:User1/test" is not a valid uniform resource name (At line:1 char:1+ Export-CsUserData -PoolFqdn pool01.domain.com -FileName c:\temp\UserDataExport.zip+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Export-CsUserData], UriFormatException + FullyQualifiedErrorId : System.UriFormatException,Microsoft.Rtc.Management.BlobStor
Published Date : Monday, September 25, 2017

Debug-CsAddressBookReplication (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/debug-csaddressbookreplication Address Book servers are intermediaries between Active Directory Domain Services (AD DS) and Skype for Business Server. The Address Book server ensures that the user information stored in Skype for Business Server is in sync with the user information stored in Active Directory. This is done by periodically syncing Address Book files with information stored in the User database. The Debug-CsAddressBookReplication cmdlet enables administrators to verify that data is being replicated between Active Directory and Skype for Business Server. Fully testing replication between Active Directory and the Address Book server can potentially be time-consuming and resource-intensive; because of that, it is recommended that Debug-CsAddressBookReplication only be used in troubleshooting scenarios. If you want to periodically "spot check" the functioning of your Address Book server you should use the Test-CsAddressBookService cmdlet and/or the Test-CsAddressBookWebQuery cmdlet instead. The functions carried out by the Debug-CsAddressBookReplication cmdlet are not available in the Skype for Business Server Control Panel.
Published Date : Monday, September 25, 2017

Export-CsArchivingData (SkypeForBusiness)

https://docs.microsoft.com/en-us/powershell/module/skype/export-csarchivingdata Many organizations find it useful to keep a transcript of all the instant messaging (IM) sessions carried out by their users. Other organizations find it mandatory to keep such transcripts. For example, organizations in the financial world are often required by law to keep copies of all their electronic communications. Regardless of the reason, Skype for Business Server gives you flexibility when it comes to archiving IM and conferencing sessions. If you have deployed Archiving Server, you can use the various CsArchivingConfiguration cmdlets to enable and disable instant message archiving and to manage your Archiving database. You can also suspend IM should archiving fail, which helps ensure that you keep a record of all your electronic communications. If you have enabled archiving, records of your users' electronic communications are stored in the Archiving database. If you would like to view all of these records (or a selected subset of these records), you can use the Export-CsArchivingData cmdlet to extract these records from the database and save them as an Outlook Express Electronic Mail (EML) file (.EML file extension). By default, members of the following groups are authorized to run the Export-CsArchivingData cmdlet locally: RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt: Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Export-CsArchivingData"}
Published Date : Monday, September 25, 2017

Upgrade-SPContentDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/upgrade-spcontentdatabase This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet Parameter Sets. Use the Upgrade-SPContentDatabase cmdlet to resume a failed database upgrade or begin a build-to-build database upgrade against a SharePoint content database. The Upgrade-SPContentDatabase cmdlet initiates an upgrade of an existing content database that is attached to the current farm. This cmdlet begins a new upgrade session, which can be used either to resume a failed version-to-version or build-to-build upgrade of a content database or to begin a build-to-build upgrade of a content database. If the database is hosted on a version of SQL Server that supports creation and use of snapshots of the database, this cmdlet can use a database snapshot for build-to-build upgrades. During upgrade, users see a ready-only version of the database, which is the snapshot. After upgrade users see upgraded content. The default behavior of this cmdlet causes an upgrade of the schema of the database and initiates build-to-build upgrades for all site collections within the specified content database if required. To prevent build-to-build upgrades of site collections, use the NoB2BSiteUpgrade parameter. This cmdlet does not trigger version-to-version upgrade of any site collections.
Published Date : Tuesday, November 28, 2017

Upgrade-SPSingleSignOnDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/upgrade-spsinglesignondatabase The Upgrade-SPSingleSignOnDatabase cmdlet migrates the application definitions from SSO database to Secure Store database as target applications. Use the Upgrade-SPSingleSignOn cmdlet to convert an SSO database to a Secure Store database. SSO is a SharePoint Server feature. SSO functionality is performed by the Secure Store Service in SharePoint Server. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Uninstall-FASTSearchAdminDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/uninstall-fastsearchadmindatabase This cmdlet uninstalls the database used by the FAST Search Server 2010 for SharePoint administration services. All data is deleted. This cmdlet is primarily called during uninstallation, by the FAST Search Server 2010 for SharePoint installer. The administration database default name is "FASTSearchAdminDatabase" and is located in the Microsoft SQL Server instance specified by the DbServer or DbConnection parameters. For permissions and the most current information about FAST Search Server 2010 for SharePoint cmdlets, see the online documentation, (https://go.microsoft.com/fwlink/?LinkId=163227).
Published Date : Tuesday, November 28, 2017

Test-SPContentDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/test-spcontentdatabase This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet parameter sets. Use the Test-SPContentDatabase cmdlet to test a content database against a Web application to verify all customizations referenced within the content database are also installed in the web application. This cmdlet can be issued against a content database currently attached to the farm, or a content database that is not connected to the farm. It can be used to test content databases from SharePoint 2010 Products and from SharePoint Products and Technologies. The Test-SPContentDatabase cmdlet does not change any of the data or structure of the content database, but can cause load on the database while the checks are in progress, which could temporarily block use of the content database. This cmdlet should only be used against a content database that is currently under low or no usage. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPWordConversionServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spwordconversionserviceapplication The Set-SPWordConversionServiceApplication cmdlet sets global properties of a Word Automation Services application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPSubscriptionSettingsServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spsubscriptionsettingsserviceapplication Use the Set-SPSubscriptionSettingsServiceApplication cmdlet to set properties on a subscription settings service application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPTranslationServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-sptranslationserviceapplication Use the Set-SPTranslationServiceApplication cmdlet to set properties on a Machine Translation service application in the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPStateServiceDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spstateservicedatabase The Set-SPStateServiceDatabase cmdlet manages the credentials that are used to communicate with the database, sets the weight of the database, or changes the state service application with which it is associated. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPUsageApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spusageapplication The Set-SPUsageApplication cmdlet sets properties of a usage application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPServerScaleOutDatabaseDataSubRange (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spserverscaleoutdatabasedatasubrange This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see [Cmdlet Parameter Sets] (https://msdn.microsoft.com/library/dd878348(VS.85).aspx).
Published Date : Tuesday, November 28, 2017

Set-SPSecurityTokenServiceConfig (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spsecuritytokenserviceconfig This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet parameter sets. The Set-SPSecurityTokenServiceConfig cmdlet updates the settings of the SharePoint security token service (STS) identity provider. If a certificate file is used, the certificate must be an X509 certificate with private keys, otherwise an exception is raised. This cmdlet operates only with certificates that can be exported. To create a certificate which can be used in this cmdlet specify the X509KeyStorageFlags.Exportable bit in the keyStorageFlags parameter of the x509Certificate2 object constructor. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPScaleOutDatabaseDataSubRange (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spscaleoutdatabasedatasubrange Use the Set-SPScaleOutDatabaseDataSubRange cmdlet to create a subrange with the specified parameters for a specified scale-out database or a database which will be connected with a specified connection string. A subrange is a subset of a range of data. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPSessionStateService (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spsessionstateservice The Set-SPSessionStateService cmdlet updates the credentials that are used to communicate with the state service database. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPSecureStoreServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spsecurestoreserviceapplication The Set-SPSecureStoreServiceApplication cmdlet sets properties of a Secure Store Service application in the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPProjectQueueSettings (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spprojectqueuesettings Sets the value of one or multiple Project Server Queue settings for a specific Project Server service application. For permissions and the most current information about Windows PowerShell for Project Server, see the online documentation at https://go.microsoft.com/fwlink/p/?LinkId=251833 (https://go.microsoft.com/fwlink/p/?LinkId=251833).
Published Date : Tuesday, November 28, 2017

Set-SPMetadataServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spmetadataserviceapplication Use the Set-SPMetadataServiceApplication cmdlet to set the properties of a managed metadata service application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPProfileServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spprofileserviceapplication This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet parameter sets. The Set-SPProfileServiceApplication cmdlet sets properties of a User Profile Service application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPInfoPathFormsService (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spinfopathformsservice The Set-SPInfoPathFormsService cmdlet modifies the settings for InfoPath Forms Services in SharePoint Server. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPPerformancePointServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spperformancepointserviceapplication The Set-SPPerformancePointServiceApplication cmdlet updates global runtime properties for a PerformancePoint Service application. The changes made to properties by using this cmdlet affect all servers in the farm that run the instance of the specified PerformancePoint Service application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPEnterpriseSearchCrawlDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spenterprisesearchcrawldatabase The Set-SPEnterpriseSearchCrawlDatabase cmdlet sets properties of a specified crawl database for a Search service application. A crawl database stores crawl history for a Search service application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPEnterpriseSearchLinksDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spenterprisesearchlinksdatabase The Set-SPEnterpriseSearchLinksDatabase cmdlet sets properties of a specified links database for a search service application. A links database stores query logging and analytics information. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPContentDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spcontentdatabase The Set-SPContentDatabase cmdlet sets global properties of a SharePoint content database. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPBusinessDataCatalogServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spbusinessdatacatalogserviceapplication The Set-SPBusinessDataCatalogServiceApplication cmdlet sets global properties for a Business Data Connectivity service application in the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPEnterpriseSearchServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spenterprisesearchserviceapplication This cmdlet updates properties of a search service application. SPEnterpriseSearchServiceApplication represents a self-contained aggregation of indexed content and properties available for search and provides an anchor class for setting global search properties. A search application can include multiple search service applications. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPEnterpriseSearchMetadataManagedProperty (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spenterprisesearchmetadatamanagedproperty This cmdlet updates the properties of a managed property. It is typically used to change the name or description of a managed property. SPEnterpriseSearchMetadataManagedProperty represents a managed property in the enterprise search metadata property schema. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Set-SPAccessServicesDatabaseServer (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/set-spaccessservicesdatabaseserver Sets parameters associated with a database server hosting Access Services databases allowing you to control database creation, credentials, and failover database servers.
Published Date : Tuesday, November 28, 2017

Restore-SPSite (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/restore-spsite This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet parameter sets. The Restore-SPSite cmdlet performs a restoration of the site collection to a location specified by the Identity parameter. A content database may only contain one copy of a site collection. If a site collection is backed up and restored to a different URL location within the same Web application, an additional content database must be available to hold the restored copy of the site collection.
Published Date : Tuesday, November 28, 2017

Restore-SPEnterpriseSearchServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/restore-spenterprisesearchserviceapplication This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet parameter sets. This cmdlet is used by third parties to create a search application that uses existing data. Some third parties back up the application data and have to restore the application later. So, the data is restored and uses the Restore-SPEnterpriseSearchServiceApplication cmdlet to create a new search application that uses the restored data. This cmdlet supports parameter sets. The first set of parameters is for Application Configuration Attach mode and the second set of parameters is for Search Application Attach mode. Application Configuration Attach mode only restores configuration data that is stored in the administration database. However, Search Application Attach restores configuration, topology and all crawled data. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Restore-SPFarm (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/restore-spfarm This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet parameter sets. The Restore-SPFarm cmdlet restores one or more items from a backup such as an individual database, Web application, or the entire farm. This cmdlet can also be used to apply a farm template to the entire farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Restore-SPDeletedSite (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/restore-spdeletedsite This cmdlet was introduced in SharePoint Server with Service Pack 1 (SP1) and SharePoint Foundation with Service Pack 1 (SP1). Use the Restore-SPDeletedSite cmdlet to restore a previously deleted site collection. Unlike the Restore-SPSite cmdlet that uses the host name and scheme for the Identity parameter (that is, https://server_name), the value of the identity parameter for all SPDeletedSite cmdlets use a server-relative URL. Typically, the forward slash character (/) begins the relative URL and also denotes the root site. For additional information about a server-relative URL or understanding general concepts about absolute and relative URLs, see Server-relative URL Property (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsite.serverrelativeurl.aspx) or Understanding Absolute and Relative URL Addresses (https://msdn.microsoft.com/en-us/library/bb208688(office.12).aspx). For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Remove-SPSolutionDeploymentLock (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/remove-spsolutiondeploymentlock The Remove-SPSolutionDeploymentLock cmdlet removes the solution deployment lock for a server. If the Identity parameter is not specified, this cmdlet removes the solution deployment lock for all servers in the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Remove-SPStateServiceDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/remove-spstateservicedatabase The Remove-SPStateServiceDatabase cmdlet removes a state service database from a state service application and deletes the database. To remove a state service database and not delete the database, use the Dismount-SPStateServiceDatabase cmdlet. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Remove-SPShellAdmin (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/remove-spshelladmin Use the Remove-SPShellAdmin cmdlet to remove a user from the SharePoint_Shell_Access role in a specified database. When you use this cmdlet to remove a user from the role, you do not remove the user from the WSS_ADMIN_WPG group in the target database. When you run this cmdlet to add a user to the SharePoint_Shell_Access role, the user must have the following security permissions: Security_Admin role access on the instance of SQL Server and the db_owner role in the database. Administrative permission to the local computer. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Remove-SPContentDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/remove-spcontentdatabase The Remove-SPContentDatabase cmdlet deletes a content database permanently from SQL Server. In situations where data needs to be persisted, use the Dismount-SPContentDatabase cmdlet. This will remove the content database from SharePoint Products but not from SQL Server. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPWebApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spwebapplication Creates a new Web application specified by the Name parameter. The user specified by the DatabaseCredentials parameter must be a member of the dbcreator fixed server role on the database server. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Remove-DatabaseFromAvailabilityGroup (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/remove-databasefromavailabilitygroup This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see https://msdn.microsoft.com/library/dd878348(VS.85).aspx.
Published Date : Tuesday, November 28, 2017

Remove-SPActivityFeedItems (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/remove-spactivityfeeditems Use the Remove-SPActivityFeedItems cmdlet to remove an activity event.
Published Date : Tuesday, November 28, 2017

New-SPUsageApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spusageapplication The New-SPUsageApplication cmdlet creates a new usage application in the local farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPTranslationServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-sptranslationserviceapplication Use the New-SPTranslationServiceApplication cmdlet to provision a new instance of the Machine Translation service on the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPWordConversionServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spwordconversionserviceapplication The New-SPWordConversionServiceApplication cmdlet creates a new instance of a Word Automation Services application on the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPSecureStoreServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spsecurestoreserviceapplication The New-SPSecureStoreServiceApplication cmdlet creates a new Secure Store Service application in the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPSubscriptionSettingsServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spsubscriptionsettingsserviceapplication Use the New-SPSubscriptionSettingsServiceApplication cmdlet to create a subscription settings service application that can be used to store settings that are shared across all site collections in a single site subscription. This cmdlet is used only in an environment where site subscriptions are used to delegate administration or partition services that are used for storing settings that are shared across all site collections in a single site subscription. This cmdlet is used only in an environment where site subscriptions are used to delegate administration or partition services. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPProfileServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spprofileserviceapplication This cmdlet contains more than one parameter set. You may only use parameters from one parameter set and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet parameter sets. The New-SPProfileServiceApplication cmdlet adds and creates a new profile service application, or creates an instance of a profile service. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPStateServiceDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spstateservicedatabase The New-SPStateServiceDatabase cmdlet creates and a new state service database. This cmdlet installs the session state database schema in the state service database. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPStateServiceApplicationProxy (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spstateserviceapplicationproxy The New-SPStateServiceApplicationProxy cmdlet creates a proxy for a state service application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPPerformancePointServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spperformancepointserviceapplication The New-SPPerformancePointServiceApplication cmdlet creates a new PerformancePoint Service on the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPMetadataServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spmetadataserviceapplication Use the New-SPMetadataServiceApplication cmdlet to create a new managed metadata service application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPEnterpriseSearchServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spenterprisesearchserviceapplication This cmdlet is used when the search functionality is first configured or when a new shared search application is added to a farm. SPEnterpriseSearchServiceApplication represents a self-contained aggregation of indexed content and properties available for search and provides an anchor class for setting global search properties. A farm can include multiple search service applications. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPConfigurationDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spconfigurationdatabase The New-SPConfigurationDatabase cmdlet creates a new configuration database on the specified database server. This is the central database for a new SharePoint farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPEnterpriseSearchMetadataManagedProperty (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spenterprisesearchmetadatamanagedproperty This cmdlet creates a new managed property. SPEnterpriseSearchMetadataManagedProperty represents a managed property in the enterprise search metadata property schema. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPEnterpriseSearchCrawlDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spenterprisesearchcrawldatabase The New-SPEnterpriseSearchCrawlDatabase cmdlet is used during initial configuration and farm scale-out to create a new crawl database, which can be added to a search service application. A crawl database stores crawl history for a search application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPEnterpriseSearchLinksDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spenterprisesearchlinksdatabase Use the New-SPEnterpriseSearchLinksDatabase cmdlet during initial configuration and farm scale out to create a new links database, which can be added to a search service application. A links database stores query logging and analytics information. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPContentDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spcontentdatabase The New-SPContentDatabase cmdlet creates a new content database and attaches it to the specified Web application. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

New-SPBusinessDataCatalogServiceApplication (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/new-spbusinessdatacatalogserviceapplication The New-SPBusinessDataCatalogServiceApplication cmdlet creates a new Business Data Connectivity service application in the farm. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
Published Date : Tuesday, November 28, 2017

Migrate-SPProjectDatabase (SharePointServer)

https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/migrate-spprojectdatabase Copies the data from the Project Server 2013 database into the corresponding SharePoint Server 2016 content database containing the migrated site collection. Both the Project Server 2013 database and the SharePoint Server 2016 database must be on the same instance of SQL Server and the SharePoint farm account must have full access to the Project Server 2013 database. During the migration process the Project Server 2013 database will be modified and cannot be mounted back to a Project Server 2013.
Published Date : Tuesday, November 28, 2017