-->![Setting Setting](/uploads/1/2/6/5/126562293/674630067.jpg)
We are cross platform so it is essential that all documents have the correct three or four letter extension. When setting up the initial user profile, we make sure that both Mac OS and Win XP are set to show extensions. After that it is up to the users. Beatings will continue until morale improves.
Intune includes built-in settings to customize features on your macOS devices. For example, administrators can add AirPrint printers, choose how users sign in, configure the power controls, use single sign-on authentication, and more.
Extension Settings. This extension contributes the following settings: r.rterm.windows: set to R.exe path for Windows. R.rterm.mac: set to R term's path for Mac OS X. R.rterm.linux: set to R term's path for Linux. R.rpath.lsp: set to R.exe path for Language Server Protocol. R.rterm.option: R command line options (i.e: -vanilla). If there’s an individual extension scope for that extension, those will be the settings that apply to that extension. If no individual extension scope exists, then it will use the default scope. Here is an example JSON that blocks any extension from running on.example.com and blocks any extension that requires the permission “USB”. Wow, two very complicated answers to such a simple thing! The answer is: save the file normally. Depending on the program, you may be able to save it directly with no extension. That us the case, for example, of BBEdit. Let’s say you use the built. System Extensions and DriverKit. System extensions on macOS Catalina allow software like network extensions and endpoint security solutions to extend the functionality of macOS without requiring kernel-level access. DriverKit provides a fully modernized replacement for IOKit to create device drivers. System extensions and drivers built with DriverKit run in user space, where they can’t.
Use these features to control macOS devices as part of your mobile device management (MDM) solution.
This article lists these settings, and describes what each setting does. It also lists the steps to get the IP address, path, and port of AirPrint printers using the Terminal app (emulator). For more information on device features, go to Add iOS/iPadOS or macOS device feature settings.
Note
The user interface may not match the enrollment types in this article. The information in this article is correct. The user interface is being updated in an upcoming release.
Before you begin
Create a macOS device features configuration profile.
Note
These settings apply to different enrollment types, with some settings applying to all enrollment options. For more information on the different enrollment types, see macOS enrollment.
AirPrint
Settings apply to: All enrollment types
- AirPrint destinations: Add one or more AirPrint printers users can print from their devices. Also enter:
- Port (iOS 11.0+, iPadOS 13.0+): Enter the listening port of the AirPrint destination. If you leave this property blank, AirPrint uses the default port.
- IP address: Enter the IPv4 or IPv6 address of the printer. For example, enter
10.0.0.1
. If you use host names to identify printers, you can get the IP address by pinging the printer in the Terminal app. Get the IP address and path (in this article) has more details. - Path: Enter the resource path of the printer. The path is typically
ipp/print
for printers on your network. Get the IP address and path (in this article) has more details. - TLS (iOS 11.0+, iPadOS 13.0+): Your options:
- No (default): Transport Layer Security (TLS) isn't enforced when connecting to AirPrint printers.
- Yes: Secures AirPrint connections with Transport Layer Security (TLS).
- Import a comma-separated file (.csv) that includes a list of AirPrint printers. Also, after you add AirPrint printers in Intune, you can Export this list.
Get the IP address and path
To add AirPrinter servers, you need the IP address of the printer, the resource path, and the port. The following steps show you how to get this information.
- On a Mac that's connected to the same local network (subnet) as the AirPrint printers, open Terminal (from /Applications/Utilities).
- In the Terminal app, type
ippfind
, and select enter.Note the printer information. For example, it may return something similar toipp://myprinter.local.:631/ipp/port1
. The first part is the name of the printer. The last part (ipp/port1
) is the resource path. - In the Terminal, type
ping myprinter.local
, and select enter.Note the IP address. For example, it may return something similar toPING myprinter.local (10.50.25.21)
. - Use the IP address and resource path values. In this example, the IP address is
10.50.25.21
, and the resource path is/ipp/port1
.
Associated domains
This Setting Is Enforced By An Extension For Macbook Air
In Intune, you can:
- Add many app-to-domain associations.
- Associate many domains with the same app.
This setting applies to:
- macOS 10.15 and newer
Settings apply to: User approved device enrollment, and Automated device enrollment
These settings use the AssociatedDomains.ConfigurationItem payload (opens Apple's web site).
- Associated domains: Add an association between your domain and an app. This feature shares sign on credentials between a Contoso app and a Contoso website. Also enter:
- App ID: Enter the app identifier of the app to associate with a website. The app identifier includes the team ID and a bundle ID:
TeamID.BundleID
.The team ID is a 10-character alphanumerical (letters and numbers) string generated by Apple for your app developers, such asABCDE12345
. Locate your Team ID (opens Apple's web site) has more information.The bundle ID uniquely identifies the app, and typically is formatted in reverse domain name notation. For example, the bundle ID of Finder iscom.apple.finder
. To find the bundle ID, use the AppleScript in Terminal:osascript -e 'id of app 'ExampleApp'
- Domains: Enter the website domain to associate with an app. The domain includes a service type and fully qualified hostname, such as
webcredentials:www.contoso.com
.You can match all subdomains of an associated domain by entering*.
(an asterisk wildcard and a period) before the beginning of the domain. The period is required. Exact domains have a higher priority than wildcard domains. So, patterns from parent domains are matched if a match isn't found at the fully qualified subdomain.The service type can be:- authsrv: Single sign-on app extension
- applink: Universal link
- webcredentials: Password autofill
- Enable direct download: Yes downloads the domain data directly from the device, instead of going through Apple's content delivery network (CDN). When set to Not configured, Intune doesn't change or update this setting. By default, the OS might download data through Apple's CDN dedicated to Associated Domains.This setting applies to:
- macOS 11 and newer
Tip
To troubleshoot, on your macOS device, open System Preferences > Profiles. Confirm the profile you created is in the device profiles list. If it's listed, be sure the Associated Domains Configuration is in the profile, and it includes the correct app ID and domains.
Content caching
Content caching saves a local copy of content. This information can be retrieved by other Apple devices without connecting to the Internet. This caching accelerates downloads by saving software updates, apps, photos, and other content the first time they're downloaded. Since apps are downloaded once and shared to other devices, schools and organization with many devices save bandwidth.
Note
Only use one profile for these settings. If you assign multiple profiles with these settings, an error occurs.
For more information on monitoring content caching, see View content caching logs and statistics (opens Apple's web site).
This setting applies to:
- macOS 10.13.4 and newer
Settings apply to: All enrollment types
For more information on these settings, see Content Caching payload settings (opens Apple's web site).
Enable content caching: Yes turns on content caching, and users can't disable it. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might turn it off.
- Type of content to cache: Your options:
- All content: Caches iCloud content and shared content.
- User content only: Caches user's iCloud content, including photos and documents.
- Shared content only: Caches apps and software updates.
- Maximum cache size: Enter the maximum amount of disk space (in bytes) that's used to cache content. When left blank (default), Intune doesn't change or update this setting. By default, the OS might set this value to zero (
0
) bytes, which gives unlimited disk space to the cache.Be sure you don't exceed the space available on the devices. For more information on device storage capacity, see How iOS and macOS report storage capacity (opens Apple's web site). - Cache location: Enter the path to store the cached content. The default location is
/Library/Application Support/Apple/AssetCache/Data
. It's recommended that you don't change this location.If you change this setting, your cached content isn't moved to the new location. To move it automatically, users need to change the location on the device (System Preferences > Sharing > Content Caching). - Port: Enter the TCP port number on devices for the cache to accept download and upload requests, from 0-65535. Enter zero (
0
) (default) to use whatever port is available. - Block internet connection and cache content sharing: Also known as tethered caching. Lost soundtrack youtube. Yes prevents Internet connection sharing, and prevents sharing cached content with iOS/iPadOS devices USB-connected to their Mac. Users can't enable this feature. When set to Not configured (default), Intune doesn't change or update this setting.
- Enable internet connection sharing: Also known as tethered caching. Yes allows Internet connection sharing, and allows sharing cached content with iOS/iPadOS devices USB-connected to their Mac. Users can't disable this feature. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might turn this off.This setting applies to:
- macOS 10.15.4 and newer
- Enable cache to log client details: Yes logs the IP address and port number of the devices that request content. If you're troubleshooting device issues, this log file may help. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not log this information. https://hwssgy.weebly.com/cluefinders-3rd-grade-download-mac.html.
- Always keep content from the cache, even when the system needs disk space for other apps: Yes keeps the cache content, and makes sure nothing is deleted, even when disk space is low. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might purge content from the cache automatically when it needs storage space for other apps.This setting applies to:
- macOS 10.15 and newer
- Show status alerts: Yes shows as alerts as system notifications. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not show these alerts as system notifications.This setting applies to:
- macOS 10.15 and newer
- Prevent the device from sleeping while caching is turned on: Yes prevents the computer from going to sleep when caching is on. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow the device to sleep.This setting applies to:
- macOS 10.15 and newer
- Devices to cache: Choose the devices that can cache content. Your options:
- Not configured (default): Intune doesn't change or update this setting.
- Devices using the same local network: The content cache offers content to devices on the same immediate local network. No content is offered to devices on other networks, including devices reachable by the content cache.
- Devices using the same public IP address: The content cache offers content to devices using the same public IP address. No content is offered to devices on other networks, including devices reachable by the content cache.
- Devices using custom local networks: The content cache provides content to devices in the IP ranges you enter.
- Client listen ranges: Enter the range of IP addresses that can receive the content cache.
- Devices using custom local networks with fallback: The content cache provides content to devices in the listen ranges, peer listen ranges, and parents IP addresses.
- Client listen ranges: Enter the range of IP addresses that can receive the content cache.
- Custom public IP addresses: Enter a range of public IP addresses. The cloud servers use this range to match client devices to caches.
- Share content with other caches: When your network has more than one content cache, the content caches on other devices automatically become peers. These devices can consult and share cached software.When a requested item isn’t available on one content cache, it checks its peers for the item. If the item is available, it’s downloaded from the content cache on the peer device. If it’s still not available, the content cache downloads the item from:
- A parent IP address, if any are configuredOR,
- From Apple through the Internet
When more than one content cache is available, devices automatically select the right content cache.Your options:- Not configured (default): Intune doesn't change or update this setting.
- Content caches using the same local networks: Content cache only peers with other content caches on the same immediate local network.
- Content caches using the same public IP address: Content cache only peers with other content caches on the same public IP address.
- Content caches using custom local networks: Content cache only peers with other content caches in the IP address listen range you enter:
- Peer listen ranges: Enter the IPv4 or IPv6 start and ending IP addresses for your range. The content cache responds only to peer cache requests from content caches in the IP address ranges you enter.
- Peer filter ranges: Enter the IPv4 or IPv6 start and ending IP addresses for your range. The content cache filters its list of peers using the IP address ranges you enter.
- Parent IP addresses: Enter the local IP address of another content cache to add as a parent cache. Your cache uploads and downloads content to these caches, instead of uploading/downloading directly with Apple. Only add a parent IP address once.
- Parent selection policy: When there are many parent caches, select how the parent IP address is chosen. Your options:
- Not configured (default): Intune doesn't change or update this setting.
- Round robin: Use the parent IP addresses in order. This option is good for load-balancing scenarios.
- First available: Always use the first available IP address in the list.
- Hash: Creates a hash value for the path portion of the requested URL. This option makes sure the same parent IP address is always used for the same URL.
- Random: Randomly use an IP address in the list. This option is good for load-balancing scenarios.
- Sticky available: Always use the first IP address in the list. If it's not available, then use the second IP address in the list. Continue to use the second IP address until it's not available, and so on.
Login items
Settings apply to: All enrollment types
- Add the files, folders, and custom apps that will launch at login: Add the path of a file, folder, custom app, or system app that opens when users sign in to their devices. Also enter:
- Path of item: Enter the path to the file, folder, or app. System apps, or apps built or customized for your organization are typically in the
Applications
folder, with a path similar to/Applications/AppName.app
.You can add many files, folders, and apps. For example, enter:/Applications/Calculator.app
/Applications
/Applications/Microsoft Office/root/Office16/winword.exe
/Users/UserName/music/itunes.app
When adding any app, folder, or file, be sure to enter the correct path. Not all items are in theApplications
folder. If users move an item from one location to another, then the path changes. This moved item won't be opened when the user signs in. - Hide: Choose to show or hide the app. Your options:
- Not configured (default): Intune doesn't change or update this setting. By default, the OS might show items in the Users & Groups login items list with the hide option unchecked.
- Yes: Hides the app in the Users & Groups login items list.
Login window
Settings apply to: All enrollment types
- Show additional information in the menu bar: When the time area on the menu bar is selected, Yes shows the host name and macOS version. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not show this information on the menu bar.
- Banner: Enter a message that's shown on the sign in screen on devices. For example, enter your organization information, a welcome message, lost and found information, and so on.
- Require username and password text fields: Choose how users sign in to devices. Yes requires users to enter a username and password. When set to Not configured, Intune doesn't change or update this setting. By default, the OS may require users to select their username from a list, and then type their password.Also enter:
- Hide local users: Yes hides the local user accounts in the user list, which may include the standard and admin accounts. Only the network and system user accounts are shown. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might show the local user accounts in the user list.
- Hide mobile accounts: Yes hides mobile accounts in the user list. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might show the mobile accounts in the user list. Some mobile accounts may show as network users.
- Show network users: Select Yes to list the network users in the user list. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not show the network user accounts in the user list.
- Hide computer's administrators: Yes hides the administrator user accounts in the user list. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might show the administrator user accounts in the user list.
- Show other users: Select Yes to list Other. users in the user list. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not show the other user accounts in the user list.
- Hide shut down button: Yes hides the shutdown button on the sign in screen. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might show the shutdown button.
- Hide restart button: Yes hides the restart button on the sign in screen. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might show the restart button.
- Hide sleep button: Yes hides the sleep button on the sign in screen. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might show the sleep button.
- Disable user login from Console: Yes hides the macOS command line used to sign in. For typical users, set this setting to Yes. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow advanced users to sign in using the macOS command line. To enter console mode, users enter
>console
in the Username field, and must authenticate in the console window. - Disable Shut Down while logged in: Yes prevents users from selecting the Shutdown option after they sign in. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow users to select the Shutdown menu item on devices.
- Disable Restart while logged in: Yes prevents users from selecting the Restart option after they sign in. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow users to select the Restart menu item on devices.
- Disable Power Off while logged in: Yes prevents users from selecting the Power off option after they sign in. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow users to select the Power off menu item on devices.
- Disable Log Out while logged in (macOS 10.13 and later): Yes prevents users from selecting the Log out option after they sign in. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow users to select the Log out menu item on devices.
- Disable Lock Screen while logged in (macOS 10.13 and later): Yes prevents users from selecting the Lock screen option after they sign in. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow users to select the Lock screen menu item on devices.
Single sign-on app extension
This setting applies to:
- macOS 10.15 and newer
Settings apply to: User approved device enrollment, and Automated device enrollment
- SSO app extension type: Choose the type of SSO app extension. Your options:
- Not configured: App extensions aren't used. To disable an app extension, switch the SSO app extension type to Not configured.
- Microsoft Azure AD: Uses the Microsoft Enterprise SSO plug-in, which is a redirect-type SSO app extension. This plug-in provides SSO for Active Directory accounts across all macOS applications that support Apple’s Enterprise Single Sign-On feature. Use this SSO app extension type to enable SSO on Microsoft apps, organization apps, and websites that authenticate using Azure AD.The SSO plug-in acts as an advanced authentication broker that offers security and user experience improvements.Important
- The Microsoft Azure AD SSO extension is in public preview. This preview version is provided without a service level agreement (SLA). It's not recommended to use in production. Certain features might not be supported, or might have restricted behavior. For more information, see Supplemental Terms of Use for Microsoft Azure Previews.
- There is a known issue with the macOS SSO app extension on already-enrolled macOS devices. We recommend that you wait to deploy the SSO app extension on already-enrolled macOS devices. If you configure these settings, and target already-enrolled devices, then users might need to unenroll, and reenroll to resolve the issue. The macOS SSO app extension works as expected on newly-enrolled devices.
- To achieve SSO with the Microsoft Azure AD SSO app extension type, install the macOS Company Portal app on devices. The Company Portal app delivers the Microsoft Enterprise SSO plug-in to devices. The MDM SSO app extension settings activate the plug-in. After the Company Portal app and the SSO app extension profile are installed on devices, users sign in with their credentials, and create a session on their devices. This session is used across different applications without requiring users to authenticate again.For more information about the Company Portal app, see What happens if you install the Company Portal app and enroll your macOS device in Intune.You can also download the Company Portal app.
- Redirect: Use a generic, customizable redirect app extension to use SSO with modern authentication flows. Be sure you know the extension and team ID for your organization's app extension.
- Credential: Use a generic, customizable credential app extension to use SSO with challenge-and-response authentication flows. Be sure you know the extension ID and team ID for your organization's SSO app extension.
- Kerberos: Use Apple's built-in Kerberos extension, which is included on macOS Catalina 10.15 and newer. This option is a Kerberos-specific version of the Credential app extension.
TipWith the Redirect and Credential types, you add your own configuration values to pass through the extension. If you're using Credential, consider using built-in configuration settings provided by Apple in the the Kerberos type. - Extension ID (Redirect, Credential): Enter the bundle identifier that identifies your SSO app extension, such as
com.apple.ssoexample
. - Team ID (Redirect, Credential): Enter the team identifier of your SSO app extension. A team identifier is a 10-character alphanumerical (numbers and letters) string generated by Apple, such as
ABCDE12345
.Locate your Team ID (opens Apple's website) has more information. - Realm (Credential, Kerberos): Enter the name of your authentication realm. The realm name should be capitalized, such as
CONTOSO.COM
. Typically, your realm name is the same as your DNS domain name, but in all uppercase. - Domains (Credential, Kerberos): Enter the domain or host names of the sites that can authenticate through SSO. For example, if your website is
mysite.contoso.com
, thenmysite
is the host name, and.contoso.com
is the domain name. When users connect to any of these sites, the app extension handles the authentication challenge. This authentication allows users to use Face ID, Touch ID, or Apple pincode/passcode to sign in.- All the domains in your single sign-on app extension Intune profiles must be unique. You can't repeat a domain in any sign-on app extension profile, even if you're using different types of SSO app extensions.
- These domains aren't case-sensitive.
- The domain must start with a period (
.
).
- URLs (Redirect only): Enter the URL prefixes of your identity providers on whose behalf the redirect app extension uses SSO. When users are redirected to these URLs, the SSO app extension intervenes, and prompts for SSO.
- All the URLs in your Intune single sign-on app extension profiles must be unique. You can't repeat a domain in any SSO app extension profile, even if you're using different types of SSO app extensions.
- The URLs must begin with
http://
orhttps://
.
- Additional configuration (Microsoft Azure AD, Redirect, Credential): Enter additional extension-specific data to pass to the SSO app extension:
- Key: Enter the name of the item you want to add, such as
user name
. - Type: Enter the type of data. Your options:
- String
- Boolean: In Configuration value, enter
True
orFalse
. - Integer: In Configuration value, enter a number.
- Value: Enter the data.
- Add: Select to add your configuration keys.
- Keychain usage (Kerberos only): Choose Block to prevent passwords from being saved and stored in the keychain. If blocked, users aren't prompted to save their password, and need to reenter the password when the Kerberos ticket expires. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow passwords to be saved and stored in the keychain. Users aren't prompted to reenter their password when the ticket expires.
- Face ID, Touch ID, or passcode (Kerberos only): Require forces users to enter their Face ID, Touch ID, or device passcode when the credential is needed to refresh the Kerberos ticket. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not require users to use biometrics or device passcode to refresh the Kerberos ticket. If Keychain usage is blocked, then this setting doesn't apply.
- Default realm (Kerberos only): Choose Enable to set the Realm value you entered as the default realm. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not set a default realm.Tip
- Enable this setting if you're configuring multiple Kerberos SSO app extensions in your organization.
- Enable this setting if you're using multiple realms. It sets the Realm value you entered as the default realm.
- If you only have one realm, leave it Not configured (default).
- Autodiscover (Kerberos only): When set to Block, the Kerberos extension doesn't automatically use LDAP and DNS to determine its Active Directory site name. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow the extension to automatically find the Active Directory site name.
- Password changes (Kerberos only): Block prevents users from changing the passwords they use to sign in to the domains you entered. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow password changes.
- Password sync (Kerberos only): Choose Enable to sync your users' local passwords to Azure AD. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might disable password sync to Azure AD. Use this setting as an alternative or backup to SSO. This setting doesn't work if users are signed in with an Apple mobile account.
- Windows Server Active Directory password complexity (Kerberos only): Choose Require to force user passwords to meet Active Directory's password complexity requirements. On devices, this setting shows a pop-up window with check boxes so users see they're completing the password requirements. It helps users know what they need to enter for the password. For more information, see Password must meet complexity requirements. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not require users to meet Active Directory's password requirement.
- Minimum password length (Kerberos only): Enter the minimum number of characters that can make up users passwords. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not enforce a minimum password length on the users.
- Password reuse limit (Kerberos only): Enter the number of new passwords, from 1-24, that are used until a previous password can be reused on the domain. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not enforce a password reuse limit.
- Minimum password age (Kerberos only): Enter the number of days that a password is used on the domain before users can change it. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might not enforce a minimum age of passwords before they can be changed.
- Password expiration notification (Kerberos only): Enter the number of days before a password expires that users get notified that their password will expire. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might use
15
days. - Password expiration (Kerberos only): Enter the number of days before the device password must change. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might never expire passwords.
- Password change URL (Kerberos only): Enter the URL that opens when users start a Kerberos password change.
- Principal name (Kerberos only): Enter the username of the Kerberos principal. You don't need to include the realm name. For example, in
[email protected]
,user
is the principal name, andcontoso.com
is the realm name.Tip- You can also use variables in the principal name by entering curly brackets
{{ }}
. For example, to show the username, enterUsername: {{username}}
. - However, be careful with variable substitution because variables aren't validated in the UI and they are case sensitive. Be sure to enter the correct information.
- You can also use variables in the principal name by entering curly brackets
- Active Directory site code (Kerberos only): Enter the name of the Active Directory site that the Kerberos extension should use. You may not need to change this value, as the Kerberos extension may automatically find the Active Directory site code.
- Cache name (Kerberos only): Enter the Generic Security Services (GSS) name of the Kerberos cache. You most likely don't need to set this value.
- Password requirements message (Kerberos only): Enter a text version of your organization's password requirements that's shown to users. The message shows if you don't require Active Directory's password complexity requirements, or don't enter a minimum password length.
- Enable shared device mode (Microsoft Azure AD only): Select Yes if you're deploying the Microsoft Enterprise SSO plug-in to macOS devices configured for Azure AD's shared device mode feature. Devices in shared mode allow many users to globally sign in and out of applications that support shared device mode. When set to Not configured, Intune doesn't change or update this setting.When set to Yes, all existing user accounts are wiped from the devices. To avoid data loss, or prevent a factory reset, make sure you understand how this setting changes your devices.For more information about shared device mode, see Overview of shared device mode.
- App bundle IDs (Microsoft Azure AD, Kerberos): Add the app bundle identifiers that should use single sign-on on your devices. These apps are granted access to the Kerberos Ticket Granting Ticket and the authentication ticket. The apps also authenticate users to services they're authorized to access.
- Domain realm mapping (Kerberos only): Add the domain DNS suffixes that should map to your realm. Use this setting when the DNS names of the hosts don't match the realm name. You most likely don't need to create this custom domain-to-realm mapping.
- PKINIT certificate (Kerberos only): Select the Public Key Cryptography for Initial Authentication (PKINIT) certificate that can be used for Kerberos authentication. You can choose from PKCS or SCEP certificates that you've added in Intune. For more information about certificates, see Use certificates for authentication in Microsoft Intune.
Next steps
Assign the profile and monitor its status.
You can also configure device features on iOS/iPadOS.
Increase the power of Visual Studio Code through Extensions
The features that Visual Studio Code includes out-of-the-box are just the start. VS Code extensions let you add languages, debuggers, and tools to your installation to support your development workflow. VS Code's rich extensibility model lets extension authors plug directly into the VS Code UI and contribute functionality through the same APIs used by VS Code. This topic explains how to find, install, and manage VS Code extensions from the Visual Studio Code MarketPlace.
Browse for extensions
You can browse and install extensions from within VS Code. Bring up the Extensions view by clicking on the Extensions icon in the Activity Bar on the side of VS Code or the View: Extensions command (⇧⌘X (Windows, Linux Ctrl+Shift+X)).
This will show you a list of the most popular VS Code extensions on the VS Code Marketplace.
Each extension in the list includes a brief description, the publisher, the download count, and a five star rating. You can click on the extension item to display the extension's details page where you can learn more.
Note: If your computer's Internet access goes through a proxy server, you will need to configure the proxy server. See Proxy server support for details.
Install an extension
![Setting Setting](/uploads/1/2/6/5/126562293/674630067.jpg)
To install an extension, click the Install button. Once the installation is complete, the Install button will change to the Manage gear button.
Extension details
On the extension details page, you can read the extension's README as well as review the extension's:
- Contributions - The extension's additions to VS Code such as settings, commands and keyboard shortcuts, language grammars, debugger, etc.
- Changelog - The extension repository CHANGELOG if available.
- Dependencies - Lists if the extension depends on any other extensions.
If an extension is an Extension Pack, the Extension Pack section will display which extensions will be installed when you install the pack. Join me download for desktop. Extension Packs bundle separate extensions together so they can be easily installed at one time.
Extensions view commands
You can run various Extensions view commands by clicking on the Extensions view's
.
More Actions button.There are commands to show:
- The list of currently installed extensions
- The list of outdated extensions that can be updated
- The list of currently enabled/disabled extensions
- The list of recommended extensions based on your workspace
- The list of globally popular extensions
You can sort the extension list by Install Count or Rating in either ascending or descending order. You can learn more about extension search filters below.
Search for an extension
You can clear the Search box at the top of the Extensions view and type in the name of the extension, tool, or programming language you're looking for.
For example, typing 'python' will bring up a list of Python language extensions:
If you know the exact identifier for an extension you're looking for, you can use the
@id:
prefix, for example @id:octref.vetur
. Additionally, to filter or sort results, you can use the filter and sort commands, detailed below.Manage extensions
VS Code makes it easy to manage your extensions. You can install, disable, update, and uninstall extensions through the Extensions view, the Command Palette (commands have the Extensions: prefix) or command-line switches.
List installed extensions
By default, the Extensions view will show the extensions you currently have enabled, all extensions that are recommended for you, and a collapsed view of all extensions you have disabled. You can use the Show Installed Extensions command, available in the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)) or the More Actions (
.
) drop-down menu, to clear any text in the search box and show the list of all installed extensions, which includes those that have been disabled.This Setting Is Enforced By An Extension For Mac Os
Uninstall an extension
To uninstall an extension, click the gear button at the right of an extension entry and then choose Uninstall from the drop-down menu. This will uninstall the extension and prompt you to reload VS Code.
Disable an extension
If you don't want to permanently remove an extension, you can instead temporarily disable the extension by clicking the gear button at the right of an extension entry. You can disable an extension globally or just for your current Workspace. You will be prompted to reload VS Code after you disable an extension.
If you want to quickly disable all installed extensions, there is a Disable All Installed Extensions command in the Command Palette and More Actions (
.
) drop-down menu.Extensions remain disabled for all VS Code sessions until you re-enable them.
Enable an extension
Similarly if you have disabled an extension (it will be in the Disabled section of the list and marked Disabled), you can re-enable it with the Enable or Enable (Workspace) commands in the drop-down menu.
There is also an Enable All Extensions command in the More Actions (
.
) drop-down menu.Extension auto-update
VS Code checks for extension updates and installs them automatically. After an update, you will be prompted to reload VS Code. If you'd rather update your extensions manually, you can disable auto-update with the Disable Auto Updating Extensions command that sets the
extensions.autoUpdate
setting to false
. If you don't want VS Code to even check for updates, you can set the extensions.autoCheckUpdates
setting to false.Update an extension manually
If you have extensions auto-update disabled, you can quickly look for extension updates by using the Show Outdated Extensions command that uses the
@outdated
filter. This will display any available updates for your currently installed extensions. Click the Update button for the outdated extension and the update will be installed and you'll be prompted to reload VS Code. You can also update all your outdated extensions at one time with the Update All Extensions command. If you also have automatic checking for updates disabled, you can use the Check for Extension Updates command to check which of your extensions can be updated.Recommended extensions
You can see a list of recommended extensions using Show Recommended Extensions, which sets the
@recommended
filter. Extension recommendations can either be:- Workspace Recommendations - Recommended by other users of your current workspace.
- Other Recommendations - Recommended based on recently opened files.
See the section below to learn how to contribute recommendations for other users in your project.
Ignoring recommendations
To dismiss a recommendation, click on the extension item to open the Details pane and then press the Ignore Recommendation button. Ignored recommendations will no longer be recommended to you.
Configuring extensions
VS Code extensions may have very different configurations and requirements. Some extensions contribute settings to VS Code, which can be modified in the Settings editor. Other extensions may have their own configuration files. Extensions may also require installation and setup of additional components like compilers, debuggers, and command-line tools. Consult the extension's README (visible in the Extensions view details page) or go to the extension page on the VS Code Marketplace (click on the extension name in the details page). Many extensions are open source and have a link to their repository on their Marketplace page.
Command line extension management
This Setting Is Enforced By An Extension For Mac Osx
To make it easier to automate and configure VS Code, it is possible to list, install, and uninstall extensions from the command line. When identifying an extension, provide the full name of the form
publisher.extension
, for example ms-python.python
.Example:
You can see the extension ID on the extension details page next to the extension name.
Extensions view filters
The Extensions view search box supports filters to help you find and manage extensions. You may have seen filters such as
@installed
and @recommended
if you used the commands Show Installed Extensions and Show Recommended Extensions. Also, there are filters available to let you sort by popularity or ratings and search by category (for example 'Linters') and tags (for example 'node'). You can see a complete listing of all filters and sort commands by typing @
in the extensions search box and navigating through the suggestions:Here are the Extensions view filters:
@builtin
- Show extensions that come with VS Code. Grouped by type (Programming Languages, Themes, etc.).@disabled
- Show disabled installed extensions.@installed
- Show installed extensions.@outdated
- Show outdated installed extensions. A newer version is available on the Marketplace.@enabled
- Show enabled installed extensions. Extensions can be individually enabled/disabled.@recommended
- Show recommended extensions. Grouped as Workspace specific or general use.@category
- Show extensions belonging to specified category. Below are a few of supported categories. For a complete list, type@category
and follow the options in the suggestion list:@category:themes
@category:formatters
@category:linters
@category:snippets
These filters can be combined as well. For example: Use
@installed @category:themes
to view all installed themes.If no filter is provided, the Extensions view displays the currently installed and recommended extensions.
Sorting
You can sort extensions with the
@sort
filter, which can take the following values:installs
- Sort by Marketplace installation count, in descending order.rating
- Sort by Marketplace rating (1-5 stars), in descending order.name
- Sort alphabetically by extension name.
Categories and tags
Extensions can set Categories and Tags describing their features.
You can filter on category and tag by using
category:
and tag:
.Supported categories are:
[Programming Languages, Snippets, Linters, Themes, Debuggers, Formatters, Keymaps, SCM Providers, Other, Extension Packs, Language Packs, Data Science, Machine Learning, Visualization, Notebooks]
. They can be accessed through IntelliSense in the extensions search box:Note that you must surround the category name in quotes if it is more than one word (for example,
category:'SCM Providers'
).Tags may contain any string and are not provided by IntelliSense, so review the Marketplace to find helpful tags.
Install from a VSIX
You can manually install a VS Code extension packaged in a
.vsix
file. Using the Install from VSIX command in the Extensions view command drop-down, or the Extensions: Install from VSIX command in the Command Palette, point to the .vsix
file.You can also install using the VS Code
--install-extension
command-line switch providing the path to the .vsix
file.You may provide the
--install-extension
multiple times on the command line to install multiple extensions at once.If you'd like to learn more about packaging and publishing extensions, see our Publishing Extensions topic in the Extension API.
Workspace recommended extensions
This Setting Is Enforced By An Extension For Macbook Pro
A good set of extensions can make working with a particular workspace or programming language more productive and you'd often like to share this list with your team or colleagues. You can create a recommended list of extensions for a workspace with the Extensions: Configure Recommended Extensions (Workspace Folder) command.
In a single folder workspace, the command creates an
extensions.json
file located in the workspace .vscode
folder where you can add a list of extensions identifiers ({publisherName}.{extensionName}).In a multi-root workspace, the command will open your
.code-workspace
file where you can list extensions under extensions.recommendations
. You can still add extension recommendations to individual folders in a multi-root workspace by using the Extensions: Configure Recommended Extensions (Workspace Folder) command.An example
extensions.json
could be:which recommends a linter extension, ESLint, and the Chrome debugger extension.
An extension is identified using its publisher name and extension identifier
publisher.extension
. You can see the name on the extension's detail page. VS Code will provide you with auto-completion for installed extensions inside these files..
VS Code prompts a user to install the recommended extensions when a workspace is opened for the first time. The user can also review the list with the Extensions: Show Recommended Extensions command.
Next steps
Here are a few topics you may find interesting.
- Extension API - Start learning about the VS Code extension API.
- Your First Extension - Try creating a simple Hello World extension.
- Publishing to the Marketplace - Publish your own extension to the VS Code Marketplace.
Common questions
Where are extensions installed?
Extensions are installed in a per user extensions folder. Depending on your platform, the location is in the following folder:
- Windows
%USERPROFILE%.vscodeextensions
- macOS
~/.vscode/extensions
- Linux
~/.vscode/extensions
You can change the location by launching VS Code with the
--extensions-dir <dir>
command-line option.Whenever I try to install any extension, I get a connect ETIMEDOUT error
You may see this error if your machine is going through a proxy server to access the Internet. See the Proxy server support section in the setup topic for details.
Can I download an extension directly from the Marketplace?
Some users prefer to download an extension once from the Marketplace and then install it multiple times from a local share. This is useful when there are connectivity concerns or if your development team wants to use a fixed set of extensions.
To download an extension, navigate to the details page for the specific extension within the Marketplace. On that page, there is a Download Extension link in the Resources section, which is located on the right-hand side of the page.
Once downloaded, you can then install the extension via the Install from VSIX command in the Extensions view command drop-down.
Can I stop VS Code from providing extension recommendations?
Yes, if you would prefer to not have VS Code display extension recommendations in the Extensions view or through notifications, you can modify the following settings:
extensions.showRecommendationsOnlyOnDemand
- Set to true to remove the RECOMMENDED section.extensions.ignoreRecommendations
- Set to true to silence extension recommendation notifications.
The Show Recommended Extensions command is always available if you wish to see recommendations.
Can I trust extensions from the Marketplace?
The Marketplace runs a virus scan on each extension package that's published to ensure its safety. The virus scan is run for each new extension and for each extension update. Until the scan is all clear, the extension won't be published in the Marketplace for public usage.
The Marketplace also prevents extension authors from name-squatting on official publishers such as Microsoft and RedHat.
This Setting Is Enforced By An Extension Mac
If a malicious extension is reported and verified, or a vulnerability is found in an extension dependency:
- The extension is removed from the Marketplace.
- The extension is added to a kill list so that if it has been installed, it will be automatically uninstalled by VS Code.
The Marketplace also provides you with resources to make an informed decision about the extensions you install:
- Ratings & Review - Read what others think about the extension.
- Q & A - Review existing questions and the level of the publisher's responsiveness. You can also engage with the extension's publisher(s) if you have concerns.
- Issues, Repository, and License - Check if the publisher has provided these and if they have the support you expect.
If you do see an extension that looks suspicious, you can report the extension to the Marketplace with the Report Abuse link at the bottom of the extension More Info https://teamatlantic.weebly.com/download-tableau-1013-macbook-pro.html. section.