### Microsoft Teams Essentials Purchase and Setup Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/get-started-with-teams-essentials.md Steps to purchase and set up Microsoft Teams Essentials, including signing up with an existing email and managing licenses. ```APIDOC APIDOC: title: Microsoft Teams Essentials Purchase and Setup description: Guide for acquiring and configuring Microsoft Teams Essentials. steps: - step: 1 action: Purchase the subscription details: Navigate to Microsoft Teams Business Plans and select 'Buy now' under Microsoft Teams Essentials. url: https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-options - step: 2 action: Sign up with existing email details: Use an existing email address to purchase user licenses. - step: 3 action: Review service description details: Learn more about Microsoft Teams features and capabilities. url: /office365/servicedescriptions/teams-service-description - step: 4 action: Install the Teams app details: Download and install the Teams client on your PC or mobile device. url: https://www.microsoft.com/microsoft-teams/download-app - step: 5 action: Manage licenses details: Assign Microsoft Teams Essentials seats to users via the Microsoft admin center. ``` -------------------------------- ### Getting Started with Microsoft Teams Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/navigate-teams.md Provides guidance on initiating the transition from Kaizala to Microsoft Teams, including sign-in and profile setup. Links to a detailed guide for starting the Teams journey. ```APIDOC Getting Started: - **Purpose**: Guide users on starting their Microsoft Teams journey, covering sign-in and profile setup. - **Reference**: See [Getting started with Teams](https://support.microsoft.com/office/start-and-pin-chats-a864b052-5e4b-4ccf-b046-2e26f40e21b5?wt.mc_id=otc_microsoft_teams&ui=en-us&rs=en-us&ad=us). - **Note**: This section is for users transitioning from Kaizala. ``` -------------------------------- ### Microsoft Teams Automated Setup Guide Link Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/deploy-enterprise-overview.md Provides a link to the Microsoft Teams automated setup guide, which customizes the experience based on the user's environment when accessed while signed into the Microsoft 365 admin center. ```APIDOC Microsoft Teams automated setup guide: https://go.microsoft.com/fwlink/?linkid=2224815 ``` -------------------------------- ### Microsoft Teams Retail Team Templates Link Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/get-started-with-teams-templates-in-the-admin-console.md Provides a link to documentation for getting started with retail team templates in Microsoft Teams. ```APIDOC Retail Team Templates: Link: get-started-with-retail-teams-templates.md ``` -------------------------------- ### Install Skype for Business Server System Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/install/install-skype-for-business-server.md This section guides users through installing Skype for Business Server and setting up server roles for Front End pools and collocated server roles. It emphasizes the use of the Deployment Wizard to complete four key deployment steps: installing the Local Configuration store, installing Front End Servers, configuring certificates, and starting services. It also highlights prerequisites like publishing the topology and ensuring the Windows Firewall Service is running. ```APIDOC SkypeForBusinessServerInstallation: Prerequisites: - Topology must be published using Topology Builder. - Logged in with a domain user account that is a local administrator and a member of the RTCUniversalServerAdmins group. - Windows Server must be up-to-date via Windows Update. - Windows Firewall Service must be running on the server when starting services for the first time. Process: 1. Run the Skype for Business Server Deployment Wizard on each computer where a server role is being installed. 2. Use the Deployment Wizard to complete the following four deployment steps: a. Install Local Configuration store. b. Install Front End Servers. c. Configure certificates. d. Start services. Installation Location: - Users can specify a drive and path for the installation files, allowing installation on drives other than the system drive. - The installation location path for Skype for Business Server files can be changed in the **Setup** dialog box. Important Notes: - This procedure must be completed for all servers in the topology. - The order of steps 6, 7, and 8 in the overall deployment process must be maintained, following steps 1 through 5. ``` -------------------------------- ### Install Skype for Business Server Administrative Tools Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/management-tools/install-and-open-administrative-tools.md This snippet outlines the steps to install the administrative tools for Skype for Business Server. It involves running the setup executable and accepting license agreements. ```powershell Locate the installation media on your computer, and then double-click \Setup\amd64\Setup.exe. If you are prompted to install the Microsoft Visual C++ distributable, click **Yes**. On the Installation Location page, click **OK**. Change this path to another location or drive if you need to have the files installed to another location. On the End User License Agreement page, review the license terms, click **I accept**, and then click **OK**. On the Deployment Wizard page, click **Install Administrator Tools**. When the installation successfully completes, click **Exit**. ``` -------------------------------- ### Install Skype for Business Stress and Performance Tool Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/management-tools/stress-and-performance-tool/prerequisites-and-setup.md Instructions for installing the Skype for Business Server 2015 Stress and Performance Tool. This involves running the Windows Installer file on client computers and Front End Servers. ```powershell CapacityPlanningTool.msi ``` -------------------------------- ### Skype for Business Server Installation and Configuration Guides Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/deploy.md Documentation links for installing and configuring various aspects of Skype for Business Server, including server requirements, topology, installation, upgrades, client experience, hybrid connectivity, and specific server roles. ```markdown [Requirements for your Skype for Business environment](../plan-your-deployment/requirements-for-your-environment/requirements-for-your-environment.md) [Topology Basics for Skype for Business Server 2015](../plan-your-deployment/topology-basics/topology-basics.md) [Install Skype for Business Server 2015](install/install.md) [Upgrade to Skype for Business Server 2015](upgrade-to-skype-for-business-server.md) [Configure the client experience with Skype for Business](deploy-clients/configure-the-client-experience.md) [Deploy hybrid connectivity between Skype for Business Server and Skype for Business Online](../../SfbHybrid/hybrid/configure-hybrid-connectivity.md?bc=%2fSkypeForBusiness%2fbreadcrumb%2ftoc.json&toc=%2fSkypeForBusiness%2ftoc.json) [Deploy Edge Server in Skype for Business Server 2015](deploy-edge-server/deploy-edge-server.md) [Deploy Enterprise Voice in Skype for Business Server 2015](deploy-enterprise-voice/deploy-enterprise-voice.md) [Deploy Persistent Chat Server in Skype for Business Server 2015](deploy-persistent-chat-server/deploy-persistent-chat-server.md) [Deploy Video Interop Server in Skype for Business Server 2015](deploy-video-interop-server/deploy-video-interop-server.md) ``` -------------------------------- ### Office Setup Command-Line Options Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/deploy-clients/use-setup-command-line-options.md This section details the command-line options recognized by Office Setup.exe for operations like customization, applying configuration files, and managing installations. It covers options for running the Office Customization Tool, applying customization files, specifying configuration files, modifying installations, repairing, and uninstalling Skype for Business. ```APIDOC Setup Command-Line Options: /admin - Runs the Office Customization Tool to create a Setup customization file (.msp file). /adminfile [path] - Applies the specified Setup customization file to the installation. You can specify a path of a specific customization file (.msp file) or to the folder where you store customization files. /config [path] - Specifies the Config.xml file that Setup uses during the installation. Example: `/config \server\share\Skype15\Skype.WW\Config.xml` /modify Skype - Used with a modified Config.xml file to run Setup in maintenance mode and make changes to an existing Office installation, such as adding or removing features. /repair Skype - Runs Setup from the user's computer to repair Skype for Business. /uninstall Skype - Runs Setup to remove Skype for Business from the user's computer. ``` -------------------------------- ### Install Local Configuration Store Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/install/install-skype-for-business-server.md This procedure guides through the installation of the Local Configuration Store, which is a read-only copy of the Central Management Store. It explains the prerequisites and the process of retrieving data directly from the Central Management store. ```APIDOC Install Local Configuration Store: 1. Review prerequisites. 2. Click Run next to Step 1: Install Local Configuration Store. 3. On the Install Local Configuration Store page, select 'Retrieve directly from the Central Management store'. 4. Click Next. 5. SQL Server Express Edition is installed on the local server. 6. When installation is complete, click Finish. ``` -------------------------------- ### Skype for Business Server 2019 Pilot Pool Deployment Steps Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfBServer2019/migration/deploy-pilot-pool.md This documentation details the sequential steps required to deploy a pilot pool for Skype for Business Server 2019. It guides users through the Topology Builder interface, from initial setup to publishing the topology and subsequent installation. ```APIDOC Project: /microsoftdocs/officedocs-skypeforbusiness Deployment Steps: 1. Sign in with appropriate administrative privileges (Domain Admins, RTCUniversalServerAdmins). 2. Navigate Topology Builder: Skype for Business Server 2019 > Enterprise Edition Front End pools. 3. Create New Front End Pool: - Right-click 'Enterprise Edition Front End pools' and select 'New Front End Pool'. - Enter a unique, fully qualified domain name (FQDN) for the pool. 4. Select Features: - Choose desired features (e.g., Conferencing for multiparty IM). - Avoid selecting voice/video features if not intended for the pilot. 5. Collocate Server Roles: - Recommend collocating the Mediation Server. - For merging topologies, collocate the legacy Mediation Server first. 6. Associate Server Roles: - Crucially, *do not* enable Edge pool media component usage for the pilot pool. 7. Select Office Web Apps Server: - Choose 'New' and specify the application server FQDN. 8. Define Archiving SQL Server Store: - Select the pre-created SQL Server instance for Archiving and Monitoring. 9. Publish Topology: - Right-click the 'Skype for Business Server' node and select 'Publish Topology'. 10. Finalize: - Click 'Finish' upon successful publication. 11. Install Front End Pilot Pool: - Follow installation procedures (referenced: [Install Skype for Business Server on servers in the topology](../../SfbServer/deploy/install/install-skype-for-business-server.md)). 12. Verify Coexistence: - Proceed to verify pilot pool coexistence with the legacy pool. ``` -------------------------------- ### Video Demonstration of Call Queue Creation Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/includes/create-call-queue-steps.md A link to a video tutorial demonstrating the basic process of creating a call queue in Microsoft Teams. ```en > [!VIDEO https://learn-video.azurefd.net/vod/player?id=c5394239-b79f-4f41-9a85-78e6ff7087b6] ``` -------------------------------- ### Microsoft Teams Plan Comparison Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/get-started-with-teams-essentials.md Provides links to compare Microsoft Teams Essentials with other Microsoft 365 plans for business and home users. ```APIDOC APIDOC: title: Microsoft Teams Plan Comparison description: Links to resources for comparing different Microsoft Teams subscription plans. endpoints: - url: https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-business-options method: GET description: Compare Teams Essentials, Microsoft 365 Business Basic, and Microsoft 365 Business Standard. - url: https://www.microsoft.com/microsoft-teams/compare-microsoft-teams-home-options method: GET description: View features of Microsoft Teams (free) for home plans. ``` -------------------------------- ### Install Operations Manager Agent Files Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/management-tools/use-scom-management-pack/configure-computers-to-monitor.md Step-by-step guide to install the Operations Manager Agent files on a Skype for Business Server 2015 computer. This process involves running the System Center setup, configuring management group information, and selecting the agent action account. ```APIDOC Install Operations Manager Agent Files: 1. Run Setup.exe from System Center setup media. 2. Select 'Install Operations Manager Agent'. 3. Proceed through the wizard, specifying Destination Folder. 4. Configure Management Group information: Specify Management Group Name and Management Server hostname/port. 5. Select 'Local System' for Agent Action Account. 6. Choose 'I don't want to use Microsoft Update'. 7. Click 'Install' on the Ready to Install page. 8. Click 'Finish' on the completion page. 9. Click 'Exit'. ``` -------------------------------- ### Topology Builder Database Installation Steps Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/help-topics/help-topobld/create-database.md This outlines the steps within Topology Builder for installing databases. It involves selecting the SQL Server instance, choosing between automatic or default file locations, and completing the installation wizard. ```APIDOC Topology Builder Database Installation: 1. Navigate to the Skype for Business Server 2015 node. 2. Click 'Install Database'. 3. In the 'Install Databases' dialog, select the SQL Server FQDN. 4. Click 'Advanced' to configure database file locations: - 'Automatically determine database file location' - 'Use SQL Server instance defaults' 5. Click 'OK' and then 'Next' to proceed. 6. Click 'Finish' on the 'Database Creation Complete' page. ``` -------------------------------- ### Install Local Configuration Store (Invoke) Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/help-topics/2019/depwiz/ms.lync.dep.DeployReplicaInvoke.md This section details the invocation process for installing the local configuration store. It explains how to monitor the execution of commands, review task statuses, and examine log files for any errors or warnings. The process concludes with a 'Finish' action to complete the installation. ```APIDOC Install Local Configuration Store (Invoke): Purpose: Installs the local read-only replica of the Central Management store. Process: 1. Monitor the 'Execute Commands' pane for task status updates. 2. Review task status for errors or warnings. 3. Upon completion, the message 'Task status: Completed' will be displayed. 4. Select log files from the drop-down list and click 'View Log' to review their content. 5. After reviewing all log files, click 'Finish' to complete the installation. ``` -------------------------------- ### Busy Options Server Application Output Example Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/deploy-enterprise-voice/install-and-configure-busy-options.md Example output from Get-CsServerApplication showing a correctly installed Busy Options server application. ```APIDOC Identity : Service:Registrar:pool0.vdomain.com/BusyOptions Priority : 5 Uri : https://www.microsoft.com/LCS/BusyOptions Name : BusyOptions Enabled : True Critical : False ScriptName : Script : ``` -------------------------------- ### Install Skype for Business Server System Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/install/install-skype-for-business-server.md This section details the initial steps for installing the Skype for Business Server system. It covers inserting the installation media, accepting license agreements, and initiating the installation process. ```APIDOC Install Skype for Business Server System: 1. Insert the Skype for Business Server installation media. 2. Double-click Setup if it doesn't start automatically. 3. Install Microsoft Visual C++ when prompted. 4. Accept the license agreement. 5. Click Install to begin the installation with Smart Setup. 6. On the Deployment Wizard page, click Install or Update Skype for Business Server System. 7. Perform the procedures in the following sections and click Exit to close the Deployment Wizard. ``` -------------------------------- ### Insights App Setup Policy Management Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/class-insights.md IT Admins can configure app setup policies in Microsoft Teams to automatically install and pin the Insights app for educators and leaders. This ensures users have immediate access to student analytics and engagement data within the Teams environment. The policy can be customized to highlight the app on the apps bar for better visibility and adoption. ```APIDOC TeamsAppSetupPolicy: - Name: "Install Insights by Default" Description: "Installs and pins the Insights app for all educators and leaders." AppIds: ["InsightsAppId"] PinnedAppIds: ["InsightsAppId"] DisplayOption: "Full" Priority: 1 - Name: "Insights Tab for Classes" Description: "Enables educators to manually add the Insights tab to individual Teams classes." AppIds: [] PinnedAppIds: [] AdditionalTabs: - ClassId: "*" TabName: "Insights" TeamsAppId: "InsightsAppId" Configuration: ContentUrl: "https://teams.microsoft.com/app/InsightsAppId" RemoveTabs: [] Notes: - The 'InsightsAppId' is a placeholder and should be replaced with the actual application ID for the Insights app. - The 'PinnedAppIds' array ensures the app appears on the Teams app bar. - The 'AdditionalTabs' configuration allows for manual addition of the Insights tab to class Teams. - Educators can also manually install the Insights tab from the top navigation menu within a class. - By default, Insights is turned on. Opting out deletes all collected data and stops future collection. - If Insights is turned back on, data collection resumes from the re-enablement time. ``` -------------------------------- ### Install Local Configuration Store Steps Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/help-topics/help-depwiz/install-local-configuration-store.md Provides the sequential steps to initiate and complete the installation of the local configuration store for Skype for Business Server 2015. This includes running the installation wizard and selecting the appropriate configuration retrieval option. ```powershell 1. On the Skype for Business Server 2015 page, next to **Step1: Install Local Configuration Store**, click **Run**. 2. On the **Local Server Configuration** page, be sure that the **Retrieve configuration automatically from the Central Management Store** option is selected, and then click **Next**. 3. When the local server configuration installation is complete, click **Finish**. ``` -------------------------------- ### Government Cloud Support Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/CQD-Power-BI-connector.md Provides guidance for customers using Government cloud environments (GCC, GCC-High, and DoD) with the Microsoft Call Quality connector. It explains the need for an on-premises data gateway and references guides for installation and custom connector setup. It also mentions the requirement for an appropriate Power BI US Government license. ```Power BI For customers in Government cloud environments, the Microsoft Call Quality connector can be used with an [on-premises data gateway](/power-bi/connect-data/service-gateway-onprem) for compatibility with Power BI service. Simply follow the guide for [installing custom connectors with an on-premises data gateway](/power-bi/connect-data/service-gateway-custom-connectors) using the latest version of the Microsoft Call Quality connector to enable access. Additionally, an appropriate Power BI US Government license is required for government cloud. For more information on licensing, see the latest guidance for [Power BI for US government customers](/power-bi/enterprise/service-govus-overview#buy-a-power-bi-pro-subscription-for-government-customers). ``` -------------------------------- ### Microsoft Graph API for Creating Class Teams Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/remote-learning-edu.md This section details how to use the Microsoft Graph API to create class teams. It references specific API endpoints for creating education classes and provides examples for both HTTP GET and POST requests, including request bodies and responses. It also touches upon creating teams from groups and syncing membership changes. ```APIDOC POST /education/classes Description: Create a new education class. Request Body: { "classCode": "string", "displayName": "string", "mailNickname": "string", "externalId": "string", "termId": "string", "teacher": { "@odata.type": "#microsoft.graph.identitySet", "application": { "displayName": "string", "id": "string" }, "device": { "displayName": "string", "id": "string" }, "user": { "displayName": "string", "id": "string" } }, "teachers": [ { "@odata.type": "#microsoft.graph.identitySet", "application": { "displayName": "string", "id": "string" }, "device": { "displayName": "string", "id": "string" }, "user": { "displayName": "string", "id": "string" } } ], "students": { "addEdge": [ { "@odata.type": "#microsoft.graph.identitySet", "application": { "displayName": "string", "id": "string" }, "device": { "displayName": "string", "id": "string" }, "user": { "displayName": "string", "id": "string" } } ] } } Responses: 201 Created: Returns the newly created educationClass object. 400 Bad Request: Invalid request. 401 Unauthorized: Authentication required. POST /groups/{group-id}/teams Description: Create a team from an existing group. Request Body: { "memberSettings": { "allowCreateUpdateChannels": true, "allowAddRemoveApps": true, "allowCreateUpdateRemoveTabs": true, "allowCreateUpdateRemoveHooks": true, "allowPinUnpinMessage": true }, "messagingSettings": { "allowUserEditMessages": true, "allowUserDeleteMessages": true }, "funSettings": { "allowGiphy": true, "giphyContentRating": "strict", "allowStickersAndMemes": true, "allowCustomMemes": true }, "guestSettings": { "allowAddGuests": true, "allowGuestInviteList": true, "allowGuestChangeName": true }, "securitySettings": { "tokenLifetime": "P365D" } } Responses: 201 Created: Returns the created team object. POST /groups/{group-id}/team/members Description: Add a member to a team. Request Body: { "@odata.type": "#microsoft.graph.aadUserConversationMember", "roles": ["owner"], "additionalData": { "user@odata.bind": "https://graph.microsoft.com/v1.0/users/{user-id}" } } Responses: 201 Created: Returns the added conversation member. Related API Endpoints: - GET /education/classes/{educationClass-id} - PATCH /education/classes/{educationClass-id} - DELETE /education/classes/{educationClass-id} - GET /teams/{team-id} - PATCH /teams/{team-id} - DELETE /teams/{team-id} ``` -------------------------------- ### Teams for Education - Quick start for admins Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/planning-workshop-practical-guide.md A tutorial to guide administrators through a Microsoft Teams rollout for education organizations. ```link ./teams-quick-start-edu.yml ``` -------------------------------- ### Install Local Configuration Store Steps Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/help-topics/2019/depwiz/ms.lync.dep.DeployMainInstallReplica.md This section details the step-by-step process for installing the local configuration store for Skype for Business Server. It includes prerequisites and actions to perform within the Skype for Business Server interface. ```APIDOC Install Local Configuration Store: Prerequisites: - Logged on as local administrator on the server. - Membership in RTCUniversalServerAdmins or RTCUniversalGlobalReadOnlyGroup (unless on an Edge Server). - For Edge Servers: Topology Builder definition document must be exported and available. Steps: 1. Navigate to the Skype for Business Server page. 2. Click 'Run' next to 'Step 1: Install Local Configuration Store'. 3. On the 'Local Server Configuration' page, ensure 'Retrieve configuration automatically from the Central Management Store' is selected. 4. Click 'Next'. 5. Upon completion, click 'Finish'. Notes: - SQL Server installation can take time and may not show progress in the summary screen. Monitor using Task Manager. ``` -------------------------------- ### Install Teams MSI (Per-User) Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/teams-for-vdi.md Installs the Teams MSI package for per-user installation on a VDI VM. This is the default installation method and installs Teams to the %AppData% user folder. It is not suitable for non-persistent setups. ```console msiexec /i /l*v ALLUSERS=1 ``` -------------------------------- ### Setup Command-Line Options for Skype for Business Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/deploy-clients/customize-windows-client-installation.md Utilize Setup command-line options to specify the Config.xml file to be used during the installation of Skype for Business Server. This allows for automated and customized deployments. ```APIDOC Setup Command-Line Options: Purpose: Control the Skype for Business Server installation process via command line. Usage: setup.exe [/config ] Parameters: /config: Specifies the path to the Config.xml file to use for the installation. Dependencies: Requires a volume licensed version of Skype for Business. ``` -------------------------------- ### Setup or Remove Skype for Business Server Components Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/install/install-skype-for-business-server.md This section details the process of setting up or removing Skype for Business Server components. It involves running the setup, reviewing the execution commands, and verifying the completion status. ```APIDOC Setup or Remove Skype for Business Server Components: 1. Review prerequisites. 2. Click Run next to Step 2: Setup or Remove Skype for Business Server Components. 3. On the Set Up Skype for Business Server Components page, click Next. 4. The Executing Commands page displays installation progress. View logs as needed. 5. Click Finish to complete the step. 6. Restart the server if prompted and rerun the procedure. 7. If prerequisites are not satisfied, satisfy them and restart the procedure. 8. Verify that the first two steps show a green checkmark with 'Complete'. 9. Run Windows Update again to check for new updates. ``` -------------------------------- ### Install Microsoft Teams PowerShell Modules Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/edu-parents-app.md Installs the necessary PowerShell modules for managing Microsoft Teams. It first ensures the latest PowerShellGet is installed, then installs the MicrosoftTeams module, allowing pre-release versions. ```powershell Install-Module -Name PowerShellGet -Force -AllowClobber Install-Module -Name MicrosoftTeams -AllowPrerelease -Force –AllowClobber ``` -------------------------------- ### Planning Teams with Teams Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/teams-quick-start-guide-edu.md This tip suggests using Microsoft Teams itself to plan the deployment of Teams. It recommends creating a dedicated team with channels for different workloads like Exchange, Microsoft Teams, Pilot Feedback, SharePoint, and Training and Adoption. ```APIDOC APIDOC: Topic: Plan Teams with Teams Description: Use Teams to plan your deployment by creating a team (e.g., 'Microsoft 365 Deployment') with channels for various workloads. Suggested Channels: - Exchange - Microsoft Teams - Pilot Feedback - SharePoint - Training and Adoption ``` -------------------------------- ### Mac Teams Client Installation Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/get-clients.md Describes the process for installing the Microsoft Teams client on macOS using a PKG file. It requires administrative access and installs the application to the /Applications folder. It also covers updating from a DMG installation to a PKG installation. ```text 1. Download the PKG file from the Teams download page. 2. Double-click the PKG file. 3. Follow the installation wizard. To replace DMG with PKG: 1. Exit Teams. 2. Uninstall Teams. 3. Install the PKG file. ``` -------------------------------- ### Running SYSPrep.ps1 Script Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/management-tools/resource-kit-tools.md This example demonstrates how to execute the SYSPrep.ps1 script with the -SetupFolder parameter to install Skype for Business Server 2015 prerequisites. Ensure you run this from an elevated command prompt. ```Console ./SysPrep.PS1 -SetupFolder D:\Setup ``` -------------------------------- ### Install Teams MSI (Per-Machine) Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/teams-for-vdi.md Installs the Teams MSI package for per-machine installation on a VDI VM. This method installs Teams to the %ProgramFiles(x86)% or %ProgramFiles% folder and is required for non-persistent setups. The ALLUSERS=1 parameter ensures the installation appears in 'Programs and Features' for all users. ```console msiexec /i /l*v ALLUSER=1 ALLUSERS=1 ``` -------------------------------- ### Start Services Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/help-topics/2019/depwiz/ms.lync.dep.DeployMainStartServices.md This section describes the action of starting services on a deployed server role. It highlights the user interface element 'Run' within 'Step 4: Start Services' and the prerequisite of being logged in as a local administrator. ```APIDOC Start Services: Action: Click 'Run' in 'Step 4: Start Services'. Prerequisites: - Logged on as a member of the local Administrators group or an equivalent. Notes: - If 'Start Services' has been run, you can rerun the command by clicking 'Run Again'. ``` -------------------------------- ### Start Skype for Business Server Services Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/deploy-enterprise-voice/install-and-configure-busy-options.md This cmdlet starts the Skype for Business Server Windows services on all Front End servers in pools where Busy Options have been installed and enabled. This action is necessary to make the Busy Options feature operational. ```powershell Start-CsWindowsService ``` -------------------------------- ### Adoption Resources Downloads Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/adopt-tools-and-downloads.md Provides links to various downloadable resources for driving adoption of Microsoft Teams, including project plans, persona examples, workstream templates, quicksheets, and video resources. ```download Adoption Project Plans: https://download.microsoft.com/download/3/b/f/3bf2f240-de41-47f4-9c9c-0cb3597c8300/teams-adopt-service-adoption-plans-oct-2018.zip Example personas and work styles: https://download.microsoft.com/download/a/b/0/ab091b25-8477-4e34-83e8-5fdb04cee840/teams-adopt-example-personas.zip Work assignment and stakeholder communication template: https://download.microsoft.com/download/5/2/b/52b946c8-fe0f-409c-8c32-84e0763e8170/teams-adopt-work-assign-and-stakeholders.zip Day in the Life quicksheets: https://download.microsoft.com/download/1/f/3/1f3e4e44-ffee-44cb-a5f2-600b351016b9/teams-adopt-day-in-the-life-quicksheets.zip Embeddable video resources: https://aka.ms/CoffeeintheCloud ``` -------------------------------- ### Install or Update Skype for Business Server Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/help-topics/2019/depwiz/ms.lync.dep.DeployMainDeploySystem.md Initiates the installation or update process for Skype for Business Server components. This process is guided by the Topology Builder document and installs role-specific components. Ensure you have administrative privileges and the computer is domain-joined before proceeding. ```PowerShell Install-CsSkypeForBusinessServer Update-CsSkypeForBusinessServer ``` -------------------------------- ### Monitoring SQL Server Express Installation Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/help-topics/2019/depwiz/ms.lync.dep.DeployAIOInvoke.md Provides guidance on how to monitor the SQL Server Express installation process, which may not show visible progress on the screen or task pane. It suggests using Windows Task Manager to observe MSIExec processes and SQL Server Setup files. ```APIDOC Monitoring SQL Server Express Installation: - Use Windows Task Manager. - Look for MSIExec processes. - Look for Setup files for SQL Server. - Installation can take up to 15 minutes or more. ``` -------------------------------- ### Install or Update Skype for Business Server Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/help-topics/help-depwiz/install-or-update-skype-for-business-server-system.md Initiates the installation or update process for Skype for Business Server 2015. This action installs server role-specific components based on the Topology Builder document. Ensure you have administrative privileges and the computer is domain-joined before starting. ```en Install or Update Skype for Business Server ``` -------------------------------- ### Deploy School Data Sync Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/teams-quick-start-guide-edu.md This section outlines the initial step for deploying Microsoft Teams for Education, which involves using School Data Sync to facilitate the automatic creation of Teams. It also provides a contact for deployment assistance. ```APIDOC APIDOC: Endpoint: /SchoolDataSync Method: Deploy Description: Deploy School Data Sync to make it easier for educators to automatically create Teams. Parameters: None Support: Contact https://aka.ms/sdssupport for deployment assistance. ``` -------------------------------- ### Group Policy for Teams Autostart Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/msi-deployment.md This API documentation describes the Group Policy setting to prevent Microsoft Teams from starting automatically after installation. It is recommended for managing Teams' startup behavior. ```APIDOC Policy: Prevent Microsoft Teams from starting automatically after installation Location: User Configuration\Policies\Administrative Templates\Microsoft Teams Description: Controls whether Microsoft Teams starts automatically after installation. When enabled before installation, Teams will not launch automatically on user login. After the first manual sign-in, it will start automatically on subsequent logins. Related: Use Group Policy to prevent Microsoft Teams from starting automatically after installation (link to documentation) ``` -------------------------------- ### Microsoft Teams Adoption Phases Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/teams-adoption-get-started.md Details the three distinct phases for implementing Microsoft Teams adoption: Startup, Experiment, and Enable. Each phase outlines key activities and goals for a successful rollout. ```APIDOC Adoption Phases: Startup Phase: - Gather team, set up initial teams, plan adoption. - Increase technical familiarity and build necessary skills. Experiment Phase: - Onboard internal champions and early adopters. - Identify business scenarios benefiting from Teams collaboration. - Gather feedback for broad-scale adoption. - Make service decisions on governance and lifecycle management. Enable (Scale) Phase: - Deploy Teams capabilities to all employees. - Deployment strategy can be 'go big' or segmented by region/business unit. - Transition to a continuous delivery model. - Provide ongoing training and engagement for users to maximize Teams and Microsoft 365 usage. ``` -------------------------------- ### Install Skype for Business Server Components Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Skype/SfbServer/deploy/deploy-persistent-chat-server/install-persistent-chat-components.md This section details the steps involved in installing Skype for Business Server components using the Deployment Wizard. It includes installing the local configuration store, setting up server components, managing certificates, and starting services. ```powershell 1. Install Local Configuration Store 2. Setup or Remove Skype for Business Server Components 3. Request, Install or Assign Certificates 4. Start services ``` -------------------------------- ### How to roll out Teams Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/planning-workshop-practical-guide.md Follow the recommended path for rolling out Microsoft Teams. ```link ./deploy-overview.md ``` -------------------------------- ### Choose a Team Type for Collaboration Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/teams-quick-start-guide-edu.md This guide helps users understand the different team types available in Microsoft Teams for Education, explaining their use cases and differences to aid in choosing the most suitable type for collaboration. ```APIDOC APIDOC: Topic: Choose a team type to collaborate in Teams Description: Understand the differences and use cases of each team type in Microsoft Teams for Education. Reference: - https://support.office.com/article/Choose-a-team-type-to-collaborate-in-Microsoft-Teams-0a971053-d640-4555-9fd7-f785c2b99e67 ``` -------------------------------- ### Windows Teams Client Installation Paths Source: https://github.com/microsoftdocs/officedocs-skypeforbusiness/blob/public/Teams/get-clients.md Details the default installation directories for the Microsoft Teams client on Windows, which are located within the user's AppData folder. This allows for installation without elevated permissions. ```text %LocalAppData%\Microsoft\Teams %LocalAppData%\Microsoft\TeamsMeetingAddin %AppData%\Microsoft\Teams %LocalAppData%\SquirrelTemp ```