of9.netlify.com

1. Microsoft Server Manager Windows 10
2. Microsoft Server Virtual Machine Manager 2019
3. Microsoft Server Manager Tools
4. Microsoft Server Manager Mac Free

Applies to: Configuration Manager (current branch)

Mar 26, 2020  Manage Role Based Access Control with Server Manager. You can use the following topics to manage role based access control by using Server Manager, which has a graphical user interface. Alternately, you can use Windows PowerShell to manage IPAM role based access control.

Configuration Manager supports installing client software on Windows and macOS computers.

General requirements and limitations

Review the following requirements and limitations for all clients:

• Changing the startup type or Log on as settings for any Configuration Manager service isn't supported. This change can prevent key services from running correctly.

• Use Microsoft Remote Desktop for Mac to connect to a remote PC or virtual apps and desktops made available by your admin. With Microsoft Remote Desktop, you can be productive no matter where you are. GET STARTED Configure your PC for remote access using the information at https://aka.ms/rdsetup.
• Installing the Driver Manager for Microsoft ODBC Driver 11 for SQL Server. (SUSE and Red Hat Linux only.) These instructions refer to msodbcsql-11.0.2270.0.tar.gz, which is the installation file for Red Hat Linux. If you are installing the Preview for SUSE Linux, the file name is msodbcsql-11.0.2260.0.tar.gz.
• Ark Server Manager 1.0.0.211 is free to download from our software library. The latest installation package that can be downloaded is 3 MB in size. This free program is an intellectual property of Ark Server Manager. The software lies within Games, more precisely Utilities.
• Apr 12, 2018 This blog post was co-authored by Samuel Li, Principal Program Manager Lead, Windows Server and Vinicius Apolinario, Senior Product Marketing Manager, Windows Server. At Ignite 2017, we unveiled the technical preview of Project “Honolulu” to the world for the first time. It sparked a flame of excitement in IT admins’ hearts.
• I absolutely hated having a MS product installed on my Mac so I moved to using Office in my Win8 VM as well. I use to use Cord, but grew tired of it. I tried to MS RDP tool for MAC for all of 30Sec then uninstalled it. Like Alaerus I love the Server Manager on Win8. It to is the only reason I switch from Win7 to Win8 on my VM.
• Nov 27, 2017  ‎Use Microsoft Remote Desktop for Mac to connect to a remote PC or virtual apps and desktops made available by your admin. With Microsoft Remote Desktop, you can be productive no matter where you are.

Windows computers

To manage the following Windows OS versions, use the client that's included with Configuration Manager. For more information, see How to deploy clients to Windows computers.

Supported client OS versions

• Windows 10

  For more detailed information, see Support for Windows 10.

• Windows 8.1 (x86, x64): Professional, Enterprise

Windows Virtual Desktop

Windows Virtual Desktop is a desktop and app virtualization service that runs on Microsoft Azure. Starting in version 1906, use Configuration Manager to manage these virtual devices running Windows in Azure.

Similar to a terminal server, some of these virtual devices allow multiple concurrent active user sessions. To help with client performance, Configuration Manager now disables user policies on any device that allows these multiple user sessions. Even if you enable user policies, the client disables them by default on these devices, which include Windows 10 Enterprise multi-session and terminal servers.

The client only disables user policy when it detects this type of device during a new installation. For an existing client of this type that you update to this version, the previous behavior persists. On an existing device, it configures the user policy setting even if it detects that the device allows multiple user sessions.

If you require user policy in this scenario, and accept any potential performance impact, use one of the following methods to enable user policy:

• In version 1910 and later, use client settings. In the Client Policy group, configure the following setting: Enable user policy for multiple user sessions.

  Microsoft Office is also available for Mac, in which case you can open any Office document format. If you haven't bought iWork or Microsoft Office for Mac, you can use Apple's TextEdit application or download a free office software package such as OpenOffice. Mar 19, 2020  Word won't open on mac Please help! Suddenly Microsoft word will not open on my Macbook Pro. All over Microsoft apps will open without problems, but when I click to open word it just bounces as if its trying to open for a few minutes then stops bouncing. Quit Word (File Quit), or Force Quit, or go to activity monitor, shut down Word. Open microsoft word file on mac. Launch Pages (it’s in the Applications folder of your Mac). In the window that automatically opens when you launch the app, navigate to the location of your Word file. For example, if it’s in. Simply drag the file on to Pages or Word in your dock and it'll open in the chosen application. (Alternatively, you can right-click the file and select Open With. Open Microsoft Office documents on your Mac. Use Pages to open Microsoft Word documents. Open Pages for me (if installed) Use Numbers to open Microsoft Excel documents. Open Numbers for me (if installed) Use Keynote to open Microsoft PowerPoint presentations. Open Keynote for me (if installed).

• In version 1906, use the Configuration Manager SDK with the SMS_PolicyAgentConfig server WMI class. Set the new PolicyEnableUserPolicyOnTS property to true.

Note

You can't use co-management with a client running Windows 10 Enterprise multi-session.

Supported server OS versions

• Windows Server 2019: Standard, Datacenter ^{Note 1}
  (Starting with Configuration Manager version 1806.)

• Windows Server 2016: Standard, Datacenter ^{Note 1}

• Windows Storage Server 2016: Workgroup, Standard

• Windows Server 2012 R2 (x64): Standard, Datacenter ^{Note 1}

• Windows Storage Server 2012 R2 (x64)

• Windows Server 2012 (x64): Standard, Datacenter ^{Note 1}

• Windows Storage Server 2012 (x64)

Server Core

The following versions specifically refer to the Server Core installation of the OS. ^{Note 3}

Windows Server semi-annual channel versions are Server Core installations, such as Windows Server, version 1809. As a Configuration Manager client, they're supported the same as the associated Windows 10 semi-annual channel version. For more information, see Support for Windows 10.

• Windows Server 2019 (x64) ^{Note 2}

• Windows Server 2016 (x64) ^{Note 2}

• Windows Server 2012 R2 (x64) ^{Note 2}

• Windows Server 2012 (x64) ^{Note 2}

Note 1

Configuration Manager tests and supports Windows Server Datacenter editions, but isn't officially certified for Windows Server. Configuration Manager hotfix support isn't offered for issues that are specific to Windows Server Datacenter Edition. For more information on the Windows Server certification program, see Windows Server Catalog.

Note 2

To support client push installation, add the File Server service of the File and Storage Services server role. For more information about installing Windows features on Server Core, see Install roles, role services, and features by using Windows PowerShell cmdlets.

Note 3

The new Software Center app isn't supported on any version of Windows Server Core.

Windows Embedded computers

Manage Windows Embedded devices by installing the Configuration Manager client on the device. For more information, see Planning for client deployment to Windows Embedded devices.

Requirements and limitations

• All client features are supported on Windows Embedded systems that don't have write filters enabled.

• Clients that use one of the following are supported for all features except power management:

  • Enhanced Write Filters (EWF)

  • RAM File-Based Write Filters (FBWF)

  • Unified Write Filters (UWF)

• The application catalog isn't supported for any Windows Embedded device.

Supported OS versions

• Windows 10 Enterprise (x86, x64)

• Windows 10 IoT Enterprise (x86, x64)
  This version includes the long-term servicing channel (LTSC). For more information, see Overview of Windows 10 IoT Enterprise.

• Windows Embedded 8.1 Industry (x86, x64)

• Windows Embedded 8 Standard (x86, x64)

• Windows Thin PC (x86, x64)

• Windows Embedded POSReady 7 (x86, x64)

• Windows Embedded Standard 7 with SP1 (x86, x64)

Windows CE computers

Manage Windows CE devices with the Configuration Manager mobile device legacy client that is included with Configuration Manager.

Requirements and limitations

• The mobile device client requires 0.78 MB of storage space for installation. Sign-in can require up to 256 KB of additional storage space.

• Features for these mobile devices vary by platform and client type. For information about which management functions are supported, see Choose a device management solution.

  Interface: Bluetooth10. Microsoft express mouse mac. Product weight: 0.06kgs9.

Supported OS versions

• Windows CE 7.0 (ARM and x86 processors)

  Note

  Support is deprecated for Windows CE 7.0 in Configuration Manager. For more information, see Removed and deprecated items for Configuration Manager clients.

Supported languages include

• Chinese (simplified and traditional)

• English (US)

• French (France)

• German

• Italian

• Japanese

• Korean

• Portuguese (Brazil)

• Russian

• Spanish (Spain)

Extended Security Updates and Configuration Manager

The Extended Security Updates (ESU) program is a last resort option for customers who need to run certain legacy Microsoft products past the end of support. For example, Windows 7. It includes Critical and/or Important security updates (as defined by the Microsoft Security Response Center (MSRC)) for a maximum of three years after the product’s End of Extended Support date.

Products that are beyond their support lifecycle aren't supported for use with Configuration Manager. This includes any products that are covered under the ESU program. Security updates released under the ESU program will be published to Windows Server Update Services (WSUS). These updates will appear in the Configuration Manager console. While products that are covered under the ESU program are no longer supported for use with Configuration Manager, the latest released version of Configuration Manager current branch can be used to deploy and install Windows security updates released under the program. The latest released version can also be used to deploy Windows 10 to devices running Windows 7.

Client management features not related to Windows software update management or OS deployment will no longer be tested on the operating systems covered under the ESU program and we don't guarantee that they'll continue to function. It's highly recommended to upgrade or migrate to a current version of the operating systems as soon as possible to receive client management support.

Mac computers

Manage Apple Mac computers with the Configuration Manager client for macOS.

The macOS client installation package isn't supplied with the Configuration Manager media. Download it from the Microsoft Download Center, Microsoft Endpoint Configuration Manager - macOS Client (64-bit).

For more information, see How to deploy clients to Macs.

Requirements and limitations

• Installing or running the Configuration Manager client for macOS on computers under an account other than root isn't supported. Doing so can prevent key services from running correctly.

Supported versions

• macOS Catalina (10.15) (requires Configuration Manager site version 1910 or later, and Configuration Manager client for macOS version 5.0.8742.1000 or later)

• macOS Mojave (10.14)

• macOS High Sierra (10.13)

Linux and UNIX servers

Important

Configuration Manager version 1902 drops support for Linux and UNIX as a client. Deprecation was announced with version 1802. Consider Microsoft Azure Management for managing Linux servers. Azure solutions have extensive Linux support that in most cases exceed Configuration Manager functionality, including end-to-end patch management for Linux.

The Linux and UNIX client installation packages aren't supplied with the Configuration Manager media. Download the Clients for Additional Operating Systems from the Microsoft Download Center. In addition to client installation packages, the client download includes the script that manages the installation of the client on each computer.

Requirements and limitations

Microsoft Server Manager Windows 10

• To review OS file dependencies for the client for Linux and UNIX, see Prerequisites for client deployment to Linux and UNIX servers.

• For an overview of supported management capabilities for Linux or UNIX, see How to deploy clients to UNIX and Linux servers.

• For supported versions of Linux and UNIX, the listed version includes all subsequent minor versions. For example, CentOS version 6 includes CentOS 6.3. Similarly, support for an OS that uses service packs (such as SUSE Linux Enterprise Server 11 SP1) includes subsequent service packs for that OS version.

• For information about client installation packages and the Universal Agent, see How to deploy clients to UNIX and Linux servers.

Supported versions

The following versions are supported by using the indicated .tar file.

AIX

CentOS

Debian

HP-UX

Oracle Linux

Red Hat Enterprise Linux (RHEL)

Solaris

SUSE Linux Enterprise Server (SLES)

Ubuntu

On-premises MDM

Configuration Manager has built-in capabilities for managing mobile devices that are on-premises without installing client software. For more information, see Manage mobile devices with on-premises infrastructure.

Supported operating systems

• Windows 10 Pro (x86, x64)

• Windows 10 Pro Enterprise (x86, x64)

• Windows 10 IoT Enterprise (x86, x64)
  This version includes the long-term servicing channel (LTSC). For more information, see Overview of Windows 10 IoT Enterprise.

• Windows 10 IoT Mobile Enterprise

• Windows 10 Team for Surface Hub

• Windows 10 Mobile

• Windows 10 Mobile Enterprise

  Note

  Support is deprecated for Windows 10 Mobile and Windows 10 Mobile Enterprise in Configuration Manager. For more information, see Removed and deprecated items for Configuration Manager clients.

Exchange Server connector

Configuration Manager supports limited management of devices that connect to your Exchange Server, without installing the Configuration Manager client. For more information, see Manage mobile devices with Configuration Manager and Exchange.

Supported versions of Exchange Server

• Exchange Online (Office 365): This version includes Business Productivity Online Standard Suite

• Exchange Server 2016

• Exchange Server 2013

• Exchange Server 2010 SP1 or Exchange Server 2010 SP2

This article contains instructions to install the unixODBC Driver Manager for use with all the versions of Microsoft ODBC Driver for SQL Server on Linux and macOS.

Important

Delete any driver manager packages installed on your computer before you install the unixODBC Driver Manager. Installing the unixODBC Driver Manager could cause a failure of an existing Driver Manager.

Installing the Driver Manager for Microsoft ODBC Driver 13, 13.1, and 17

The driver manager dependency is resolved automatically by the package management system when you install the Microsoft ODBC Driver 13, 13.1, or 17 for SQL Server on Linux or macOS by following the instructions in the following articles:

Installing the Driver Manager for Microsoft ODBC Driver 11 for SQL Server

Microsoft Server Virtual Machine Manager 2019

(SUSE and Red Hat Linux only.)

Using the Installation Script

Important

These instructions refer to msodbcsql-11.0.2270.0.tar.gz, which is the installation file for Red Hat Linux. If you are installing the Preview for SUSE Linux, the file name is msodbcsql-11.0.2260.0.tar.gz.

To install the driver manager:

1. Make sure that you have root permission.

2. Go to the directory where the MicrosoftSQL Server ODBC Driver download placed the file called msodbcsql-11.0.2270.0.tar.gz. Make sure that you have the *.tar.gz file that matches your version of Linux. To extract the files, execute the following command: tar xvzf msodbcsql-11.0.2270.0.tar.gz.

3. Change to the msodbcsql-11.0.2270.0 directory and there you should see a file called build_dm.sh. You can run build_dm.sh to install the unixODBC Driver Manager.

4. To see a list of the available options, execute the following command: ./build_dm.sh --help.

5. When you are ready to install, and if your computer can access an external site via FTP, execute the following command: ./build_dm.sh.

If your computer cannot access an external site via FTP, get unixODBC-2.3.0.tar.gz. You can get unixODBC-2.3.0.tar.gz from http://www.unixodbc.org. Click the Download link on the left side of the page to go to the download page. Then click the appropriate link to download unixODBC-2.3.0 (not unixODBC-2.3.1). unixODBC-2.3.1 is not supported with this release of the Microsoft ODBC Driver 11 for SQL Server. Execute the following command to begin the unixODBC Driver Manager installation: ./build_dm.sh --download-url=file://unixODBC-2.3.0.tar.gz.

6. Type YES to proceed with unpacking the files. This part of the process can take up to five minutes to complete.

7. After the script stops running, follow the instructions on the screen to install the unixODBC Driver Manager.

You are now ready to install the driver. For more information, see the ODBC driver installation instructions for Linuxor macOS.

Manual Installation

If the installation script is unable to complete, configure and build the proper driver manager yourself.

Microsoft Server Manager Tools

1. Remove any older installed version of unixODBC (for example, unixODBC 2.2.11). On Red Hat Enterprise Linux 5 or 6, execute the following command: yum remove unixODBC. On SUSE Linux Enterprise, zypper remove unixODBC.

2. Go to http://www.unixodbc.org. Click the Download link on the left side of the page to go to the download page. Then click the appropriate link to save the file unixODBC-2.3.0.tar.gz to your computer. UnixODBC-2.3.1 is not supported with this release of the Microsoft ODBC Driver 11 for SQL Server.

3. On your Linux computer, execute the command: tar xvzf unixODBC-2.3.0.tar.gz.

4. Change to the unixODBC-2.3.0 directory.

5. At a command prompt, execute the command: CPPFLAGS='-DSIZEOF_LONG_INT=8'.

6. At a command prompt, execute the command: export CPPFLAGS.

7. At a command prompt, execute the command: './configure --prefix=/usr --libdir=/usr/lib64 --sysconfdir=/etc --enable-gui=no --enable-drivers=no --enable-iconv --with-iconv-char-enc=UTF8 --with-iconv-ucode-enc=UTF16LE'.

8. At a command prompt (logged in as root), execute the command: make.

9. At a command prompt (logged in as root), execute the command: make install.

You are now ready to install the driver. For more information, see the ODBC driver installation instructions for Linuxor macOS.

Microsoft Server Manager Mac Free

See Also