1. 2.5 Operating With Decimalsmr. Mac's Page Manager
  2. 2.5 Operating With Decimalsmr. Mac's Page Shortcut
  3. 2.5 Operating With Decimalsmr. Mac's Page Numbering
  4. 2.5 Operating With Decimalsmr. Mac's Page Number

Welcome to the landing page for Firefox OS for TV and connected devices. This is written for web developers who are interested in Firefox OS for TV current and future work, and developing web apps for TV. The articles linked below provide everything you need to build and run a Firefox OS TV simulator, get started writing apps and deploying them to TV, understand TV implementation and UX differences, and more.

The supported operating systems for i7-9700K are Windows® 10 64-bit, OS X, and Linux. OS Note: If you have any questions related to the operating system support for your OEM (original equipment manufacturer) PC, contact the OEM for support. MBAM Server operating system requirements. We strongly recommend that you run the MBAM Client and MBAM Server on the same line of operating systems. For example, Windows 10 with Windows Server 2016, Windows 8.1 with Windows Server 2012 R2, and so on. The following table lists the operating systems that are supported for the MBAM Server.

Current status and future plans

Gaia 2.1 and above contains facilities for running on TV. There have been smart TVs on the market running Firefox OS since mid 2015, the first of which is the Panasonic VIERA Smart TV.

The newest version of Firefox OS (2.5) is currently available to partners and developers and adds some new features, which will be made available in the new range of Panasonic DX900 UHD TVs later this year. This update will include new ways to discover Web apps and save them to your TV, and sync Firefox features across TV and other platforms (such as bookmarks, etc.) Most prominent is a “send to TV” feature to easily share Web content from Firefox for Android to a Firefox OS powered TV.

The Firefox OS effort across TVs is part of the wider effort to provide Firefox OS as an open platform choice for managing and controlling the wider range of connected devices available in the physical world (i.e. the Internet of Things.)

TV environment setup and tools

2.5 Operating With Decimalsmr. Mac's Page Manager

TV web application development

In brief, the main differences between using Firefox OS on a TV versus a phone (or a desktop computer) are:

  • Control mechanisms: Firefox OS on TV likely only has a TV remote available to control it, which is not as convenient as a keyboard, mouse or touch screen.
  • Resolution: Modern smart TVs are usually Full HD (1920x1080) or Ultra HD (4K). The Device Pixel Ratio on TVs is also different to that of most mobile devices.

App development articles

  • Q&A for TV apps (to be started)

TV UX overview

Firefox OS basics

API support on TV

Firefox OS for TV is based on Gecko, so therefore it supports most of the APIs available for the web platform, and Firefox OS-specific APIs. There are some exceptions, however, and this list outlines those:

  • DeviceStorage: Not supported on VIErA TV.
  • Geolocation: Not supported on VIErA TV.
  • WebRTC: Not supported on VIErA TV.
-->

You can run Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 in a Stand-alone topology or in a Configuration Manager Integration topology that integrates MBAM with System Center Configuration Manager. If you use the recommended configuration for either topology in a production environment, MBAM supports up to 500,000 MBAM clients. For information about the recommended architecture and features that are configured on each server for each topology, see High-Level Architecture for MBAM 2.5.

For additional configurations that are specific to the Configuration Manager Integration topology, see Versions of Configuration Manager that MBAM supports.

Note
Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the Lifecycle Supported Service Packs. For additional information about Microsoft Support Lifecycle Policy, see Microsoft Support Lifecycle Support Policy FAQ.

MBAM Supported Languages

The following tables show the languages that are supported for the MBAM Client (including the Self-Service Portal) and the MBAM Server in MBAM 2.5 and MBAM 2.5 SP1.

Supported Languages in MBAM 2.5 SP1:

Client LanguagesServer Languages

Czech (Czech Republic) cs-CZ

Danish (Denmark) da-DK

Dutch (Netherlands) nl-NL

English (United States) en-US

Finnish (Finland) fi-FI

French (France) fr-FR

German (Germany) de-DE

Greek (Greece) el-GR

Hungarian (Hungary) hu-HU

Italian (Italy) it-IT

Japanese (Japan) ja-JP

Korean (Korea) ko-KR

Norwegian, Bokmål (Norway) nb-NO

Polish (Poland) pl-PL

Portuguese (Brazil) pt-BR

Portuguese (Portugal) pt-PT

Russian (Russia) ru-RU

Slovak (Slovakia) sk-SK

Spanish (Spain) es-ES

Swedish (Sweden) sv-SE

Turkish (Turkey) tr-TR

Slovenian (Slovenia) sl-SI

Simplified Chinese (PRC) zh-CN

Traditional Chinese (Taiwan) zh-TW

  • English (United States) en-US

  • French (France) fr-FR

  • German (Germany) de-DE

  • Italian (Italy) it-IT

  • Japanese (Japan) ja-JP

  • Korean (Korea) ko-KR

  • Portuguese (Brazil) pt-BR

  • Russian (Russia) ru-RU

  • Spanish (Spain) es-ES

  • Simplified Chinese (PRC) zh-CN

  • Traditional Chinese (Taiwan) zh-TW

Supported Languages in MBAM 2.5:

Client LanguagesServer Languages
  • English (United States) en-US

  • French (France) fr-FR

  • German (Germany) de-DE

  • Italian (Italy) it-IT

  • Japanese (Japan) ja-JP

  • Korean (Korea) ko-KR

  • Portuguese (Brazil) pt-BR

  • Russian (Russia) ru-RU

  • Spanish (Spain) es-ES

  • Simplified Chinese (PRC) zh-CN

  • Traditional Chinese (Taiwan) zh-TW

  • English (United States) en-US

  • French (France) fr-FR

  • German (Germany) de-DE

  • Italian (Italy) it-IT

  • Japanese (Japan) ja-JP

  • Korean (Korea) ko-KR

  • Portuguese (Brazil) pt-BR

  • Russian (Russia) ru-RU

  • Spanish (Spain) es-ES

  • Simplified Chinese (PRC) zh-CN

  • Traditional Chinese (Taiwan) zh-TW

MBAM Server system requirements

MBAM Server operating system requirements

We strongly recommend that you run the MBAM Client and MBAM Server on the same line of operating systems. For example, Windows 10 with Windows Server 2016, Windows 8.1 with Windows Server 2012 R2, and so on.

The following table lists the operating systems that are supported for the MBAM Server installation.

Operating systemEditionService packSystem architecture

Windows Server 2019

Standard or Datacenter

64-bit

Windows Server 2016

Standard or Datacenter

64-bit

Windows Server 2012 R2

Standard or Datacenter

64-bit

Windows Server 2012

Standard or Datacenter

64-bit

Windows Server 2008 R2

Standard, Enterprise, or Datacenter

SP1

64-bit

The enterprise domain must contain at least one Windows Server 2008 (or later) domain controller.

MBAM Server processor, RAM, and disk space requirements – Stand-alone topology

These requirements are for the MBAM Stand-alone topology. For the requirements for the Configuration Manager Integration topology, see MBAM Server Processor, RAM, and Disk Space Requirements - Configuration Manager Integration Topology.

Hardware itemMinimum requirementRecommended requirement

Processor

2.33 GHz

2.33 GHz or greater

RAM

8 GB

12 GB

Free disk space

1 GB

2 GB

MBAM Server processor, RAM, and disk space requirements - Configuration Manager Integration topology

The following table lists the server processor, RAM, and disk space requirements for MBAM servers when you are using the Configuration Manager Integration topology. For the requirements for the Stand-alone topology, see MBAM Server Processor, RAM, and Disk Space Requirements – Stand-alone Topology.

Hardware itemMinimum requirementRecommended requirement

Processor

2.33 GHz

2.33 GHz or greater

RAM

4 GB

8 GB

Free disk space

1 GB

2 GB

Versions of Configuration Manager that MBAM supports

MBAM supports the following versions of Configuration Manager.

Supported versionService packSystem architecture

Microsoft System Center Configuration Manager (Current Branch), versions up to 1902

64-bit

Microsoft System Center Configuration Manager 1806

64-bit

Microsoft System Center Configuration Manager (LTSB - version 1606)

64-bit

Microsoft System Center 2012 Configuration Manager

SP1

64-bit

Microsoft System Center Configuration Manager 2007 R2 or later

64-bit

>Note Although Configuration Manager 2007 R2 is 32 bit, you must install it and SQL Server on a 64-bit operating system in order to match the 64-bit MBAM software.

For a list of supported configurations for the Configuration Manager Server, see the appropriate TechNet documentation for the version of Configuration Manager that you are using. MBAM has no additional system requirements for the Configuration Manager Server.

SQL Server database requirements

Page

The following table lists the Microsoft SQL Server versions that are supported for the MBAM Server features, which include the Recovery Database, Compliance and Audit Database, and the Reports feature. The required versions apply to the Stand-alone or the Configuration Manager Integration topologies.

You must install SQL Server with the SQL_Latin1_General_CP1_CI_AS collation.


https://www.microsoft.com/download/details.aspx?id=54967
SQL Server versionEditionService packSystem architecture

Microsoft SQL Server 2019

Standard, Enterprise, or Datacenter

64-bit

Microsoft SQL Server 2017

Standard, Enterprise, or Datacenter

64-bit

Microsoft SQL Server 2016

Standard, Enterprise, or Datacenter

SP1

64-bit

Microsoft SQL Server 2014

Standard, Enterprise, or Datacenter

SP1, SP2

64-bit

Microsoft SQL Server 2012

Standard, Enterprise, or Datacenter

SP3

64-bit

Microsoft SQL Server 2008 R2

Standard or Enterprise

SP3

64-bit

Note
MBAM has a maximum supported compatibility level of 140. The default compatibility level for new databases created on SQL Server 2019 is 150 which will need to be altered to 140 or lower, using the ALTER DATABASE command, after the database has been created. Existing databases migrated from SQL server 2017 or below will remain at their previous compatibility level and do not need to be altered.

In order to support SQL 2016 you must install the March 2017 Servicing Release for MDOP https://www.microsoft.com/download/details.aspx?id=54967 and to support SQL 2017 you must install the July 2018 Servicing Release for MDOP https://www.microsoft.com/download/details.aspx?id=57157. In general stay current by always using the most recent servicing update as it also includes all bugfixes and new features.

SQL Server processor, RAM, and disk space requirements – Stand-alone topology

The following table lists the recommended server processor, RAM, and disk space requirements for the SQL Server computer when you are using the Stand-alone topology. Use these requirements as a guide. Your specific requirements will vary based on the number of client computers you are supporting in your enterprise. To view the requirements for the Configuration Manager Integration topology, see SQL Server Processor, RAM, and Disk Space Requirements - Configuration Manager Integration Topology.

Hardware itemMinimum requirementRecommended requirement

Processor

2.33 GHz

2.33 GHz or greater

RAM

8 GB

12 GB

Free disk space

5 GB

5 GB or greater

2.5 Operating With Decimalsmr. Mac's Page Shortcut

SQL Server processor, RAM, and disk space requirements - Configuration Manager Integration topology

The following table lists the server processor, RAM, and disk space requirements for the Microsoft SQL Server computer when you are using the Configuration Manager Integration topology, see SQL Server Processor, RAM, and Disk Space Requirements – Stand-alone Topology.

Hardware itemMinimum requirementRecommended requirement

Processor

2.33 GHz

2.33 GHz or greater

RAM

4 GB

8 GB

Free disk space

5 GB

5 GB

MBAM Client system requirements

Client operating system requirements

We strongly recommend that you run the MBAM Client and MBAM Server on the same line of operating systems. For example, Windows 10 with Windows Server 2016, Windows 8.1 with Windows Server 2012 R2, and so on.

The following table lists the operating systems that are supported for MBAM Client installation. The same requirements apply to the Stand-alone and the Configuration Manager Integration topologies.


Operating systemEditionService packSystem architecture

Windows 10 IoT

Enterprise

32-bit or 64-bit

Windows 10

Enterprise

32-bit or 64-bit

Windows 8.1

Enterprise

32-bit or 64-bit

Windows 7

Enterprise or Ultimate

SP1

32-bit or 64-bit

Windows To Go

Windows 8.1 and Windows 10 Enterprise

32-bit or 64-bit

2.5 Operating With Decimalsmr. Mac

2.5 Operating With Decimalsmr. Mac's Page Numbering

Client RAM requirements

There are no RAM requirements that are specific to the MBAM Client installation.

MBAM Group Policy system requirements

The following table lists the operating systems that are supported for MBAM Group Policy Templates installation.

Operating systemEditionService packSystem architecture

Windows 10 IoT

Enterprise

32-bit or 64-bit

Windows 10

Enterprise

32-bit or 64-bit

Windows 8.1

Enterprise

32-bit or 64-bit

Windows 7

Enterprise, or Ultimate

SP1

32-bit or 64-bit

Windows Server 2012 R2

Standard or Datacenter

64-bit

Windows Server 2012

Standard or Datacenter

64-bit

Windows Server 2008 R2

Standard, Enterprise, or Datacenter

SP1

64-bit

MBAM In Azure IaaS

The MBAM server can be deployed in Azure Infrastructure as a Service (IaaS) on any of the supported OS versions listed above, connecting to an Active Directory hosted on premises or an Active Directory also hosted in Azure IaaS. Documentation for setting up and configuring Active Directory on Azure IaaS is here.

The MBAM client is not supported on virtual machines and is also not supported on Azure IaaS.

2.5 Operating With Decimalsmr. Mac's Page Number

Service releases

Related topics

Got a suggestion for MBAM?

  • Add or vote on suggestions here.
  • For MBAM issues, use the MBAM TechNet Forum.