https://learn.microsoft.com/en-us/microsoftteams/rooms/xml-config-file

Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file

In this article

1. Manage console settings with an XML configuration file
2. Create an XML configuration file
3. Supported Meeting modes App version 4.9
4. Supported Meeting modes App version 4.8 or lower

This article discusses remote management of the default settings used by a Microsoft Teams Rooms device. It discusses how to create a master settings file and links to discussions of how to place them as needed on Teams Rooms.

It is possible for you to change default settings of Teams Rooms by updating a master XML file and sending copies to the remote Teams Rooms devices.

At startup, if a Microsoft Teams Rooms console finds an XML file named SkypeSettings.xml located at C:\Users\Skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem_8wekyb3d8bbwe\LocalState, it applies the configuration settings indicated by the XML file then deletes the XML file.

Depending on how many Microsoft Teams Rooms devices your enterprise has and how you choose to manage to configure them, there are several ways to place the XML configuration file. Once the file is pushed to the console, restart it to process the configuration changes. The XML configuration file is deleted after it is successfully processed. The management methods suggested for Microsoft Teams Rooms devices are discussed in:

• Configuring Group Policy for Microsoft Teams Rooms
• Remote Management using PowerShell and Configure a File Item

You can use any method you like so long as you can use it to transfer files and trigger a restart on the console device. The file must be readable, writable, and delete-able by the device's local user account. Preferably it is owned by, and has full privileges granted to, device's local user. If the file permissions are not set correctly, the software can fail to apply the settings, can fail to delete the file upon successful processing, and can even potentially crash.

Any text editor can be used to create a settings file. The XML Elements table explains the elements shown in this sample SkypeSettings.xml (required file name) configuration file.

<SkypeSettings>  <AutoScreenShare>1</AutoScreenShare>  <HideMeetingName>0</HideMeetingName>  <AutoExitMeetingEnabled>true</AutoExitMeetingEnabled>  <AudioRenderDefaultDeviceVolume>50</AudioRenderDefaultDeviceVolume>  <AudioRenderCommunicationDeviceVolume>50</AudioRenderCommunicationDeviceVolume>  <UserAccount>    <SkypeSignInAddress>username@microsoft.com</SkypeSignInAddress>    <ExchangeAddress>username@microsoft.com</ExchangeAddress>    <DomainUsername>domain\username</DomainUsername>    <Password>Password!</Password>    <ConfigureDomain>domain1, domain2</ConfigureDomain>    <ModernAuthEnabled>true</ModernAuthEnabled>  </UserAccount>  <TeamsMeetingsEnabled>true</TeamsMeetingsEnabled>  <SfbMeetingEnabled>false</SfbMeetingEnabled>  <IsTeamsDefaultClient>true</IsTeamsDefaultClient>  <WebExMeetingsEnabled>true</WebExMeetingsEnabled>  <ZoomMeetingsEnabled>true</ZoomMeetingsEnabled>  <BlueJeansMeetingsEnabled>true</BlueJeansMeetingsEnabled>  <UseCustomInfoForThirdPartyMeetings>true</UseCustomInfoForThirdPartyMeetings>  <CustomDisplayNameForThirdPartyMeetings>guestname</CustomDisplayNameForThirdPartyMeetings>  <CustomDisplayEmailForThirdPartyMeetings>guest@microsoft.com</CustomDisplayEmailForThirdPartyMeetings>  <BluetoothAdvertisementEnabled>true</BluetoothAdvertisementEnabled>  <AutoAcceptProximateMeetingInvitations>true</AutoAcceptProximateMeetingInvitations>  <AllowRoomRemoteEnabled>true</AllowRoomRemoteEnabled>  <DualScreenMode>false</DualScreenMode>  <DuplicateIngestDefault>true</DuplicateIngestDefault>  <DisableTeamsAudioSharing>false</DisableTeamsAudioSharing>  <EnableRoomCapacityNotification>true</EnableRoomCapacityNotification>  <FrontRowEnabled>true</FrontRowEnabled>  <FrontRowVideoSize>medium</FrontRowVideoSize>  <FrontRowPanelDefaults>3,2</FrontRowPanelDefaults>  <SingleFoRDefaultContentLayout>1</SingleFoRDefaultContentLayout>  <DefaultFoRExperience>0</DefaultFoRExperience>  <ShowMeetingChat>true</ShowMeetingChat>  <EnablePublicPreview>false</EnablePublicPreview>  <NoiseSuppressionDefault>1</NoiseSuppressionDefault>  <SendLogs>    <EmailAddressForLogsAndFeedback>username@microsoft.com</EmailAddressForLogsAndFeedback>    <SendLogsAndFeedback>true</SendLogsAndFeedback>  </SendLogs>  <Devices>    <MicrophoneForCommunication>Device1</MicrophoneForCommunication>    <SpeakerForCommunication>DeviceX</SpeakerForCommunication>    <DefaultSpeaker>DeviceX</DefaultSpeaker>    <ContentCameraId>Camera1</ContentCameraId>    <ContentCameraEnhancement>true</ContentCameraEnhancement>    <ContentCameraInverted>false</ContentCameraInverted>  </Devices>  <Theming>       <ThemeName>Custom</ThemeName>       <CustomBackgroundMainFoRDisplay>file name</CustomBackgroundMainFoRDisplay>       <CustomBackgroundExtendedFoRDisplay>file name</CustomBackgroundExtendedFoRDisplay>       <CustomBackgroundConsole>file name</CustomBackgroundConsole>       <CustomThemeImageUrl>file name</CustomThemeImageUrl>  </Theming>  <TeamsRoomsNewExperience>true</TeamsRoomsNewExperience>  <RemoveFoRCalendar>false</RemoveFoRCalendar>  <CoordinatedMeetings enabled="true">    <TrustedAccounts>username1@microsoft.com,username2@contoso.com</TrustedAccounts>    <Settings>      <Audio default="true" enabled="true"/>      <Video default="true" enabled="true"/>      <Whiteboard default="true" enabled="true"/>    </Settings>  </CoordinatedMeetings>  <EnableResolutionAndScalingSetting>true</EnableResolutionAndScalingSetting>   <MainFoRDisplay>       <MainFoRDisplayResolution>1920,1080</MainFoRDisplayResolution>       <MainFoRDisplayScaling>100</MainFoRDisplayScaling>   </MainFoRDisplay>   <ExtendedFoRDisplay>       <ExtendedFoRDisplayResolution>1920,1080</ExtendedFoRDisplayResolution>       <ExtendedFoRDisplayScaling>100</ExtendedFoRDisplayScaling>   </ExtendedFoRDisplay>    <EnableDeviceEndToEndEncryption>false</EnableDeviceEndToEndEncryption>  <SplitVideoLayoutsDisabled>false</SplitVideoLayoutsDisabled>
</SkypeSettings>

If a variable value is of the wrong type, elements are out of order, elements are unclosed, or another error is found, the XML file is badly formed. While processing a badly formed XML file, settings found up to the point where the error occurs are applied, then the rest of the file is ignored. Any unknown elements in the XML are ignored. If a parameter is omitted, it remains unchanged on the device. If a parameter value is invalid, its prior value remains unchanged.

XML elements

❶ All of the first-level elements are optional. If a first-level element is omitted, all of its child parameters remain unchanged on the device.

❷ A boolean flag can be: true, false, 0, or 1. Leaving boolean or numeric values empty can render the XML malformed and prevent changes to the settings.

❸ If a string parameter is present and empty, and empty is a valid value, the parameter is cleared on the device.

Skype for Business (default) and Microsoft Teams

Skype for Business and Microsoft Teams (default)

Skype for Business only

Microsoft Teams only

Skype for Business (default) and Microsoft Teams

Skype for Business and Microsoft Teams (default)

Skype for Business only

To locate the instance path:

1. Go into Windows settings on the Microsoft Teams Rooms console.
2. Enter the admin password.
3. From a Command Prompt, type devmgmt.msc to bring up Device Manager.
4. In Device Manager, look in the Imaging devices node and locate the content camera.
5. Right-click the camera, and open Properties.
6. Select the Details tab, and locate the Device instance path property in the drop-down.
7. The value shown is the device instance path to set in the XML configuration file. When specifying the path in XML, replace the ampersand (&) with &.

Content cameras

Manage Microsoft Teams Rooms

Configure a File Item