Microsoft To Do Mac Client
2019-6-21 Best to-do apps for Mac in 2020 Get serious about getting things done with these great to-do apps for your Mac! Microsoft To-Do also syncs with Outlook, giving you a seamless experience. And if you need to share your lists with friends, family, or coworkers, it's no problem! Feb 05, 2020 To install Skype for Business on Mac: Click the Download button. Click Save to copy the disc image file to your computer. Double click the PKG image file. Follow the on screen instructions. How can I get Microsoft To Do? How can I import my Wunderlist account to Microsoft To Do? What will happen to my Wunderlist data? How can I backup / export my Wunderlist data? Why can't I register a new Wunderlist account? Why can't you keep Wunderlist running? How do I see a list of devices that logged into my Wunderlist account?
-->Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2, Windows Server 2016
You can use the Remote Desktop client for Mac to work with Windows apps, resources, and desktops from your Mac computer. Use the following information to get started - and check out the FAQ if you have questions.
Note
- Curious about the new releases for the macOS client? Check out What's new for Remote Desktop on Mac?
- The Mac client runs on computers running macOS 10.10 and newer.
- The information in this article applies primarily to the full version of the Mac client - the version available in the Mac AppStore. Test-drive new features by downloading our preview app here: beta client release notes.
Get the Remote Desktop client
Follow these steps to get started with Remote Desktop on your Mac:
- Download the Microsoft Remote Desktop client from the Mac App Store.
- Set up your PC to accept remote connections. (If you skip this step, you can't connect to your PC.)
- Add a Remote Desktop connection or a remote resource. You use a connection to connect directly to a Windows PC and a remote resource to use a RemoteApp program, session-based desktop, or a virtual desktop published on-premises using RemoteApp and Desktop Connections. This feature is typically available in corporate environments.
What about the Mac beta client?
We're testing new features on our preview channel on AppCenter. Want to check it out? Go to Microsoft Remote Desktop for Mac and click Download. You don't need to create an account or sign into AppCenter to download the beta client.
If you already have the client, you can check for updates to ensure you have the latest version. In the beta client, click Microsoft Remote Desktop Beta at the top, and then click Check for updates.
Add a Remote Desktop connection
To create a remote desktop connection:
In the Connection Center, click +, and then click Desktop.
Enter the following information:
- PC name - the name of the computer.
- This can be a Windows computer name (found in the System settings), a domain name, or an IP address.
- You can also add port information to the end of this name, like MyDesktop:3389.
- User Account - Add the user account you use to access the remote PC.
- For Active Directory (AD) joined computers or local accounts, use one of these formats: user_name, domainuser_name, or user_name@domain.com.
- For Azure Active Directory (AAD) joined computers, use one of these formats: AzureADuser_name or AzureADuser_name@domain.com.
- You can also choose whether to require a password.
- When managing multiple user accounts with the same user name, set a friendly name to differentiate the accounts.
- Manage your saved user accounts in the preferences of the app.
- PC name - the name of the computer.
You can also set these optional settings for the connection:
- Set a friendly name
- Add a Gateway
- Set the sound output
- Swap mouse buttons
- Enable Admin Mode
- Redirect local folders into a remote session
- Forward local printers
- Forward Smart Cards
Click Save.
To start the connection, just double-click it. The same is true for remote resources.
Export and import connections
You can export a remote desktop connection definition and use it on a different device. Remote desktops are saved in separate .RDP files.
- In the Connection Center, right-click the remote desktop.
- Click Export.
- Browse to the location where you want to save the remote desktop .RDP file.
- Click OK.
Use the following steps to import a remote desktop .RDP file.
- In the menu bar, click File > Import.
- Browse to the .RDP file.
- Click Open.
Add a remote resource
Remote resources are RemoteApp programs, session-based desktops, and virtual desktops published using RemoteApp and Desktop Connections.
- The URL displays the link to the RD Web Access server that gives you access to RemoteApp and Desktop Connections.
- The configured RemoteApp and Desktop Connections are listed.
To add a remote resource:
- In the Connection Center click +, and then click Add Remote Resources.
- Enter information for the remote resource:
- Feed URL - The URL of the RD Web Access server. You can also enter your corporate email account in this field – this tells the client to search for the RD Web Access Server associated with your email address.
- User name - The user name to use for the RD Web Access server you are connecting to.
- Password - The password to use for the RD Web Access server you are connecting to.
- Click Save.
The remote resources will be displayed in the Connection Center.
Connect to an RD Gateway to access internal assets
A Remote Desktop Gateway (RD Gateway) lets you connect to a remote computer on a corporate network from anywhere on the Internet. You can create and manage your gateways in the preferences of the app or while setting up a new desktop connection.
To set up a new gateway in preferences:
- In the Connection Center, click Preferences > Gateways.
- Click the + button at the bottom of the table Enter the following information:
- Server name – The name of the computer you want to use as a gateway. This can be a Windows computer name, an Internet domain name, or an IP address. You can also add port information to the server name (for example: RDGateway:443 or 10.0.0.1:443).
- User name - The user name and password to be used for the Remote Desktop gateway you are connecting to. You can also select Use connection credentials to use the same user name and password as those used for the remote desktop connection.
Manage your user accounts
When you connect to a desktop or remote resources, you can save the user accounts to select from again. You can manage your user accounts by using the Remote Desktop client.
To create a new user account:
- In the Connection Center, click Settings > Accounts.
- Click Add User Account.
- Enter the following information:
- User Name - The name of the user to save for use with a remote connection. You can enter the user name in any of the following formats: user_name, domainuser_name, or user_name@domain.com.
- Password - The password for the user you specified. Every user account that you want to save to use for remote connections needs to have a password associated with it.
- Friendly Name - If you are using the same user account with different passwords, set a friendly name to distinguish those user accounts.
- Tap Save, and then tap Settings.
Customize your display resolution
You can specify the display resolution for the remote desktop session.
- In the Connection Center, click Preferences.
- Click Resolution.
- Click +.
- Enter a resolution height and width, and then click OK.
To delete the resolution, select it, and then click -.
Displays have separate spacesIf you are running Mac OS X 10.9 and disabled Displays have separate spaces in Mavericks (System Preferences > Mission Control), you need to configure this setting in the remote desktop client using the same option.
Drive redirection for remote resources
Drive redirection is supported for remote resources, so that you can save files created with a remote application locally to your Mac. The redirected folder is always your home directory displayed as a network drive in the remote session.
Note
In order to use this feature, the administrator needs to set the appropriate settings on the server.
Use a keyboard in a remote session
Mac keyboard layouts differ from the Windows keyboard layouts.
- The Command key on the Mac keyboard equals the Windows key.
- To perform actions that use the Command button on the Mac, you will need to use the control button in Windows (e.g.: Copy = Ctrl + C).
- The function keys can be activated in the session by pressing additionally the FN key (e.g.: FN + F1).
- The Alt key to the right of the space bar on the Mac keyboard equals the Alt Gr/right Alt key in Windows.
By default, the remote session will use the same keyboard locale as the OS you're running the client on. (If your Mac is running an en-us OS, that will be used for the remote sessions as well.) If the OS keyboard locale is not used, check the keyboard setting on the remote PC and change it manually. See the Remote Desktop Client FAQ for more information about keyboards and locales.
Support for Remote Desktop gateway pluggable authentication and authorization
Windows Server 2012 R2 introduced support for a new authentication method, Remote Desktop Gateway pluggable authentication and authorization, which provides more flexibility for custom authentication routines. You can now try this authentication model with the Mac client.
Important
Custom authentication and authorization models before Windows 8.1 are not supported, although the article above discusses them.
To learn more about this feature, check out https://aka.ms/paa-sample.
Tip
Questions and comments are always welcome. However, please do NOT post a request for troubleshooting help by using the comment feature at the end of this article. Instead, go to the Remote Desktop client forum and start a new thread. Have a feature suggestion? Tell us in the client user voice forum.
-->Applies to: Configuration Manager (current branch)
This article describes how to deploy and maintain the Configuration Manager client on Mac computers. To learn about what you have to configure before deploying clients to Mac computers, see Prepare to deploy client software to Macs.
When you install a new client for Mac computers, you might have to also install Configuration Manager updates to reflect the new client information in the Configuration Manager console.
In these procedures, you have two options for installing client certificates. Read more about client certificates for Macs in Prepare to deploy client software to Macs.
Use Configuration Manager enrollment by using the CMEnroll tool. The enrollment process doesn't support automatic certificate renewal. Re-enroll the Mac computer before the installed certificate expires.
Use a certificate request and installation method that is independent from Configuration Manager.
Important
To deploy the client to devices running macOS Sierra, correctly configure the Subject name of the management point certificate. For example, use the FQDN of the management point server.
Configure client settings
Use the default client settings to configure enrollment for Mac computers. You can't use custom client settings. To request and install the certificate, the Configuration Manager client for Mac requires the default client settings.
In the Configuration Manager console, go to the Administration workspace. Select the Client Settings node, and then select Default Client Settings.
On the Home tab of the ribbon, in the Properties group, choose Properties.
Select the Enrollment section, and then configure the following settings:
Allow users to enroll mobile devices and Mac computers: Yes
Enrollment profile: Choose Set Profile.
In the Mobile Device Enrollment Profile dialog box, choose Create.
In the Create Enrollment Profile dialog box, enter a name for this enrollment profile. Then configure the Management site code. Select the Configuration Manager primary site that contains the management points for these Mac computers.
Note
If you can't select the site, make sure that you configure at least one management point in the site to support mobile devices.
Choose Add.
In the Add Certification Authority for Mobile Devices window, select the certification authority server that issues certificates to Mac computers.
In the Create Enrollment Profile dialog box, select the Mac computer certificate template that you previously created.
Select OK to close the Enrollment Profile dialog box, and then the Default Client Settings dialog box.
Tip
If you want to change the client policy interval, use Client policy polling interval in the Client Policy client setting group.
The next time the devices download client policy, Configuration Manager applies these settings for all users. To initiate policy retrieval for a single client, see Initiate policy retrieval for a Configuration Manager client.
In addition to the enrollment client settings, make sure that you have configured the following client device settings:
Hardware inventory: Enable and configure this feature if you want to collect hardware inventory from Mac and Windows client computers. For more information, see How to extend hardware inventory.
Compliance settings: Enable and configure this feature if you want to evaluate and remediate settings on Mac and Windows client computers. For more information, see Plan for and configure compliance settings.
For more information, see How to configure client settings.
Download the client for macOS
Download the macOS client file package, Microsoft Endpoint Configuration Manager - macOS Client (64-bit). Save ConfigmgrMacClient.msi to a computer that runs Windows. This file isn't on the Configuration Manager installation media.
Run the installer on the Windows computer. Extract the Mac client package, Macclient.dmg, to a folder on the local disk. The default path is
C:Program FilesMicrosoftSystem Center Configuration Manager for Mac client.Copy the Macclient.dmg file to a folder on the Mac computer.
On the Mac computer, run Macclient.dmg to extract the files to a folder on the local disk.
In the folder, make sure that it contains the following files:
Ccmsetup: Installs the Configuration Manager client on your Mac computers using CMClient.pkg
CMDiagnostics: Collects diagnostic information related to the Configuration Manager client on your Mac computers
CMUninstall: Uninstalls the client from your Mac computers
CMAppUtil: Converts Apple application packages into a format that you can deploy as a Configuration Manager application
CMEnroll: Requests and installs the client certificate for a Mac computer so that you can then install the Configuration Manager client
Enroll the Mac client
Enroll individual clients with the Mac computer enrollment wizard.
To automate enrollment for many clients, use the CMEnroll tool.
Enroll the client with the Mac computer enrollment wizard
After you install the client, the Computer Enrollment wizard opens. To manually start the wizard, select Enroll from the Configuration Manager preference page.
On the second page of the wizard, provide the following information:
User name: The user name can be in the following formats:
domainname. For example:contosomnorthuser@domain. For example:mnorth@contoso.comImportant
When you use an email address to populate the User name field, Configuration Manager automatically populates the Server name field. It uses the default name of the enrollment proxy point server and the domain name of the email address. If these names don't match the name of the enrollment proxy point server, fix the Server name during enrollment.
The user name and corresponding password must match an Active Directory user account that has Read and Enroll permissions on the Mac client certificate template.
Server name: The name of the enrollment proxy point server.
Client and certificate automation with CMEnroll
Use this procedure for automation of client installation and requesting and enrollment of client certificates with the CMEnroll tool. To run the tool, you must have an Active Directory user account.
On the Mac computer, navigate to the folder where you extracted the contents of the Macclient.dmg file.
Enter the following command:
sudo ./ccmsetupWait until you see the Completed installation message. Although the installer displays a message that you must restart now, don't restart, and continue to the next step.
From the Tools folder on the Mac computer, type the following command:
sudo ./CMEnroll -s <enrollment_proxy_server_name> -ignorecertchainvalidation -u '<user_name>'After the client installs, the Mac Computer Enrollment wizard opens to help you enroll the Mac computer. For more information, see Enroll the client by using the Mac computer enrollment wizard.
Example: If the enrollment proxy point server is named server02.contoso.com, and you grant contosomnorth permissions for the Mac client certificate template, type the following command:
sudo ./CMEnroll -s server02.contoso.com -ignorecertchainvalidation -u 'contosomnorth'Note
If the user name includes any of the following characters, enrollment fails:
<>'+=,. Use an out-of-band certificate with a user name that doesn't include these characters.For a more seamless user experience, script the installation steps. Then users only have to supply their user name and password.
Type the password for the Active Directory user account. When you enter this command, it prompts for two passwords. The first password is for the super user account to run the command. The second prompt is for the Active Directory user account. The prompts look identical, so make sure that you specify them in the correct sequence.
Wait until you see the Successfully enrolled message.
To limit the enrolled certificate to Configuration Manager, on the Mac computer, open a terminal window and make the following changes:
Enter the command
sudo /Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain AccessIn the Keychain Access window, in the Keychains section, choose System. Then in the Category section, choose Keys.
Expand the keys to view the client certificates. Find the certificate with a private key that you installed, and open the key.
On the Access Control tab, choose Confirm before allowing access.
Browse to /Library/Application Support/Microsoft/CCM, select CCMClient, and then choose Add.
Choose Save Changes and close the Keychain Access dialog box.
Restart the Mac computer.
To verify that the client installation is successful, open the Configuration Manager item in System Preferences on the Mac computer. Also update and view the All Systems collection in the Configuration Manager console. Confirm that the Mac computer appears in this collection as a managed client.
Tip
Update onedrive for mac. To help troubleshoot the Mac client, use the CMDiagnostics tool included with the Mac client package. Use it to collect the following diagnostic information:
- A list of running processes
- The Mac OS X operating system version
- Mac OS X crash reports relating to the Configuration Manager client including CCM*.crash and System Preference.crash.
- The Bill of Materials (BOM) file and property list (.plist) file created by the Configuration Manager client installation.
- The contents of the folder /Library/Application Support/Microsoft/CCM/Logs.
The information collected by CmDiagnostics is added to a zip file that is saved to the desktop of the computer and is named cmdiag-<hostname>-<datetime>.zip
Manage certificates external to Configuration Manager
You can use a certificate request and installation method independent from Configuration Manager. Use the same general process, but include the following additional steps:
Microsoft Rdp Mac Client
When you install the Configuration Manager client, use the MP and SubjectName command-line options. Enter the following command:
sudo ./ccmsetup -MP <management point internet FQDN> -SubjectName <certificate subject name>. The certificate subject name is case-sensitive, so type it exactly as it appears in the certificate details.Example: The management point's internet FQDN is server03.contoso.com. The Mac client certificate has the FQDN of mac12.contoso.com as a common name in the certificate subject. Use the following command:
sudo ./ccmsetup -MP server03.contoso.com -SubjectName mac12.contoso.comIf you have more than one certificate that contains the same subject value, specify the certificate serial number to use for the Configuration Manager client. Use the following command:
sudo defaults write com.microsoft.ccmclient SerialNumber -data '<serial number>'.For example:
sudo defaults write com.microsoft.ccmclient SerialNumber -data '17D4391A00000003DB'
Renew the Mac client certificate
This procedure removes the SMSID. The Configuration Manager client for Mac requires a new ID to use a new or renewed certificate.
Important
Microsoft To Do Mac Client Get
After you replace the client SMSID, when you delete the old resource in the Configuration Manager console, you also delete any stored client history. For example, hardware inventory history for that client.
Create and populate a device collection for the Mac computers that must renew the computer certificates.
In the Assets and Compliance workspace, start the Create Configuration Item Wizard.
On the General page of the wizard, specify the following information:
Name: Remove SMSID for Mac
Type: Mac OS X
On the Supported Platforms page, select all Mac OS X versions.
On the Settings page, select New. In the Create Setting window, specify the following information:
Name: Remove SMSID for Mac
Setting type: Script
Data type: String
In the Create Setting window, for Discovery script, select Add script. This action specifies a script to discover Mac computers configured with an SMSID.
In the Edit Discovery Script window, enter the following shell script:
Choose OK to close the Edit Discovery Script window.
In the Create Setting window, for Remediation script (optional), choose Add script. This action specifies a script to remove the SMSID when it's found on Mac computers.
In the Create Remediation Script window, enter the following shell script:
Choose OK to close the Create Remediation Script window.
On the Compliance Rules page, choose New. Then in the Create Rule window, specify the following information:
Name: Remove SMSID for Mac
Selected setting: Choose Browse and then select the discovery script that you previously specified.
In the following values field: The domain/default pair of (com.microsoft.ccmclient, SMSID) does not exist.
Enable the option to Run the specified remediation script when this setting is noncompliant.
Complete the wizard.
Create a configuration baseline that contains this configuration item. Deploy the baseline to the target collection.
For more information, see How to create configuration baselines.
After you install a new certificate on Mac computers that have the SMSID removed, run the following command to configure the client to use the new certificate: