{"id":208385,"date":"2024-01-04T09:34:17","date_gmt":"2024-01-04T09:34:17","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/comment-desactiver-le-microsoft-store-sur-votre-reseau\/"},"modified":"2024-03-04T18:00:45","modified_gmt":"2024-03-04T18:00:45","slug":"comment-desactiver-le-microsoft-store-sur-votre-reseau","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/fr\/script-hub\/comment-desactiver-le-microsoft-store-sur-votre-reseau\/","title":{"rendered":"Automatisation informatique : Un script pour d\u00e9sactiver le Microsoft Store sur votre r\u00e9seau"},"content":{"rendered":"<p>Aujourd&rsquo;hui, nous nous concentrons sur un <strong>script PowerShell con\u00e7u pour d\u00e9sactiver le Microsoft Store<\/strong> pour tous les utilisateurs et les utilisateurs nouvellement cr\u00e9\u00e9s \u00e0 l&rsquo;aide <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows\/security\/application-security\/application-control\/windows-defender-application-control\/applocker\/applocker-overview\" target=\"_blank\" rel=\"noopener\">d&rsquo;AppLocker<\/a>. La gestion des autorisations des utilisateurs et de l&rsquo;acc\u00e8s aux applications au sein d&rsquo;un r\u00e9seau d&rsquo;entreprise peut s&rsquo;av\u00e9rer une t\u00e2che difficile et fastidieuse. Cependant, les scripts qui g\u00e8rent automatiquement ces t\u00e2ches sont d&rsquo;une grande utilit\u00e9 pour les professionnels de l&rsquo;informatique et les fournisseurs de services g\u00e9r\u00e9s (MSP).\u00a0Ce script est adapt\u00e9 aux syst\u00e8mes Windows 10 et Server 2016, offrant plusieurs options configurables, telles que l&rsquo;exclusion d&rsquo;utilisateurs sp\u00e9cifiques et le ciblage des seuls utilisateurs existants.<\/p>\n<p>Dans cet article, nous allons explorer les diff\u00e9rents aspects du script et les raisons pour lesquelles il pourrait constituer un ajout inestimable \u00e0 votre bo\u00eete \u00e0 outils informatique.<\/p>\n<h2>Le script<\/h2>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"powershell\">#Requires -Version 5.1\r\n\r\n&lt;#\r\n.SYNOPSIS\r\n    Disables the Windows Store for all users and newly created users using AppLocker. Can be given a comma separated list\r\n    of users to exclude.\r\n.DESCRIPTION\r\n    Disables the Windows Store for all users and newly created users using AppLocker. Can be given a comma separated list\r\n    of users to exclude.\r\n.EXAMPLE\r\n    (No Parameters)\r\n    \r\n    WARNING: Creating AppLocker rule for user or group \"Interactive\"...\r\n    Registry::HKEY_USERSDefaultProfileSoftwarePoliciesMicrosoftWindowsStoreRemoveWindowsStore changed from 0 to 1\r\n    Registry::HKEY_USERSS-1-5-21-3870645062-3653562310-3850680542-1001SoftwarePoliciesMicrosoftWindowsStoreRemoveWindowsStore changed from 0 to 1\r\n    Registry::HKEY_USERSS-1-5-21-3870645062-3653562310-3850680542-1002SoftwarePoliciesMicrosoftWindowsStoreRemoveWindowsStore changed from 0 to 1\r\n\r\nPARAMETER: -ExcludeUsers \"Test1,Test2\"\r\n    A comma seperated list of users to exclude. Please note newly created users will not have the windows store disabled.\r\n.EXAMPLE\r\n    -ExcludeUsers \"Test1,Test2\"\r\n\r\n    WARNING: The Following Users and newly created users will not have the windows store disabled. Test1 Test2\r\n    Registry::HKEY_USERSS-1-5-21-3870645062-3653562310-3850680542-1002SoftwarePoliciesMicrosoftWindowsStoreRemoveWindowsStore changed from 0 to 1\r\n    WARNING: Creating AppLocker rule for user or group \"tuser\"...\r\n\r\nPARAMETER: -ExistingUsersOnly\r\n    This will disable the Windows store for existing users only.\r\n.EXAMPLE\r\n    -ExistingUsersOnly\r\n\r\n    WARNING: Only existing users will have the windows store disabled!\r\n    Set Registry::HKEY_USERSS-1-5-21-3870645062-3653562310-3850680542-1001SoftwarePoliciesMicrosoftWindowsStoreRemoveWindowsStore to 1\r\n    WARNING: Creating AppLocker rule for user or group \"kbohlander\"...\r\n    Set Registry::HKEY_USERSS-1-5-21-3870645062-3653562310-3850680542-1002SoftwarePoliciesMicrosoftWindowsStoreRemoveWindowsStore to 1\r\n    WARNING: Creating AppLocker rule for user or group \"tuser\"...\r\n.OUTPUTS\r\n    None\r\n.NOTES\r\n    Minimum OS Architecture Supported: Windows 10, Server 2016\r\n    Release Notes:\r\n    Initial Release\r\nBy using this script, you indicate your acceptance of the following legal terms as well as our Terms of Use at https:\/\/www.ninjaone.com\/terms-of-use.\r\n    Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms. \r\n    Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party. \r\n    Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library or website belonging to or under the control of any other software provider. \r\n    Warranty Disclaimer: The script is provided \u201cas is\u201d and \u201cas available\u201d, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations. \r\n    Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks. \r\n    Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script. \r\n    EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).\r\n#&gt;\r\n\r\n[CmdletBinding()]\r\nparam (\r\n    [Parameter()]\r\n    [String[]]$ExcludeUsers,\r\n    [Parameter()]\r\n    [Switch]$ExistingUsersOnly\r\n)\r\n\r\nbegin {\r\n    function Test-IsElevated {\r\n        $id = [System.Security.Principal.WindowsIdentity]::GetCurrent()\r\n        $p = New-Object System.Security.Principal.WindowsPrincipal($id)\r\n        $p.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator)\r\n    }\r\n\r\n    function Test-IsSystem {\r\n        $id = [System.Security.Principal.WindowsIdentity]::GetCurrent()\r\n        return $id.Name -like \"NT AUTHORITY*\" -or $id.IsSystem\r\n    }\r\n\r\n    if (!(Test-IsElevated) -and !(Test-IsSystem)) {\r\n        Write-Error -Message \"Access Denied. Please run with Administrator privileges.\"\r\n        exit 1\r\n    }\r\n    \r\n    # Setting up some functions to be used later.\r\n    function Set-HKProperty {\r\n        param (\r\n            $Path,\r\n            $Name,\r\n            $Value,\r\n            [ValidateSet('DWord', 'QWord', 'String', 'ExpandedString', 'Binary', 'MultiString', 'Unknown')]\r\n            $PropertyType = 'DWord'\r\n        )\r\n        if (-not $(Test-Path -Path $Path)) {\r\n            # Check if path does not exist and create the path\r\n            New-Item -Path $Path -Force | Out-Null\r\n        }\r\n        if ((Get-ItemProperty -Path $Path -Name $Name -ErrorAction Ignore)) {\r\n            # Update property and print out what it was changed from and changed to\r\n            $CurrentValue = (Get-ItemProperty -Path $Path -Name $Name -ErrorAction Ignore).$Name\r\n            try {\r\n                Set-ItemProperty -Path $Path -Name $Name -Value $Value -Force -Confirm:$false -ErrorAction Stop | Out-Null\r\n            }\r\n            catch {\r\n                Write-Error \"[Error] Unable to Set registry key for $Name please see below error!\"\r\n                Write-Error $_\r\n                exit 1\r\n            }\r\n            Write-Host \"$Path$Name changed from $CurrentValue to $($(Get-ItemProperty -Path $Path -Name $Name -ErrorAction Ignore).$Name)\"\r\n        }\r\n        else {\r\n            # Create property with value\r\n            try {\r\n                New-ItemProperty -Path $Path -Name $Name -Value $Value -PropertyType $PropertyType -Force -Confirm:$false -ErrorAction Stop | Out-Null\r\n            }\r\n            catch {\r\n                Write-Error \"[Error] Unable to Set registry key for $Name please see below error!\"\r\n                Write-Error $_\r\n                exit 1\r\n            }\r\n            Write-Host \"Set $Path$Name to $($(Get-ItemProperty -Path $Path -Name $Name -ErrorAction Ignore).$Name)\"\r\n        }\r\n    }\r\n\r\n    # This will get all the registry path's for all actual users (not system or network service account but actual users.)\r\n    function Get-UserHives {\r\n        param (\r\n            [Parameter()]\r\n            [ValidateSet('AzureAD', 'DomainAndLocal', 'All')]\r\n            [String]$Type = \"All\",\r\n            [Parameter()]\r\n            [String[]]$ExcludedUsers,\r\n            [Parameter()]\r\n            [switch]$IncludeDefault\r\n        )\r\n\r\n        # User account SID's follow a particular patter depending on if they're azure AD or a Domain account or a local \"workgroup\" account.\r\n        $Patterns = switch ($Type) {\r\n            \"AzureAD\" { \"S-1-12-1-(d+-?){4}$\" }\r\n            \"DomainAndLocal\" { \"S-1-5-21-(d+-?){4}$\" }\r\n            \"All\" { \"S-1-12-1-(d+-?){4}$\" ; \"S-1-5-21-(d+-?){4}$\" } \r\n        }\r\n\r\n        # We'll need the NTuser.dat file to load each users registry hive. So we grab it if their account sid matches the above pattern. \r\n        $UserProfiles = Foreach ($Pattern in $Patterns) { \r\n            Get-ItemProperty \"HKLM:SOFTWAREMicrosoftWindows NTCurrentVersionProfileList*\" |\r\n                Where-Object { $_.PSChildName -match $Pattern } | \r\n                Select-Object @{Name = \"SID\"; Expression = { $_.PSChildName } }, \r\n                @{Name = \"UserHive\"; Expression = { \"$($_.ProfileImagePath)NTuser.dat\" } }, \r\n                @{Name = \"UserName\"; Expression = { \"$($_.ProfileImagePath | Split-Path -Leaf)\" } }\r\n        }\r\n\r\n        # There are some situations where grabbing the .Default user's info is needed.\r\n        switch ($IncludeDefault) {\r\n            $True {\r\n                $DefaultProfile = \"\" | Select-Object UserName, SID, UserHive\r\n                $DefaultProfile.UserName = \"Default\"\r\n                $DefaultProfile.SID = \"DefaultProfile\"\r\n                $DefaultProfile.Userhive = \"$env:SystemDriveUsersDefaultNTUSER.DAT\"\r\n                $DefaultProfile | Where-Object { $ExcludedUsers -notcontains $_.UserName }\r\n            }\r\n        }\r\n\r\n        $UserProfiles | Where-Object { $ExcludedUsers -notcontains $_.UserName }\r\n    }\r\n\r\n    function New-WindowStoreBlock {\r\n        param(\r\n            [Parameter()]\r\n            [String]$User\r\n        )\r\n\r\n        Write-Warning \"Creating AppLocker rule for user or group `\"$User`\"...\"\r\n        [xml]$AppLockerTemplate = Get-AppXPackage -AllUsers -Name \"Microsoft.WindowsStore\" | Get-AppLockerFileInformation | New-AppLockerPolicy -User \"$User\" -Optimize -Xml\r\n        $AppLockerTemplate.AppLockerPolicy.RuleCollection.EnforcementMode = \"Enabled\"\r\n        $AppLockerTemplate.AppLockerPolicy.RuleCollection.FilePublisherRule.Action = \"Deny\"\r\n        $AppLockerTemplate.AppLockerPolicy.RuleCollection.FilePublisherRule.Conditions.FilePublisherCondition.BinaryVersionRange.LowSection = \"*\"\r\n        $AppLockerTemplate.Save(\"$env:TEMPapplocker.xml\")\r\n        Set-AppLockerPolicy -XmlPolicy \"$env:TEMPapplocker.xml\" -Merge\r\n        Remove-Item \"$env:TEMPapplocker.xml\"\r\n    }\r\n}\r\nprocess {\r\n    if ($env:ExistingUsersOnly) { $ExistingUsersOnly = $env:ExistingUsersOnly }\r\n    # This registry key only works sometimes. It's worth setting if its an older windows build or has an older version of the store installed.\r\n    $Path = \"SoftwarePoliciesMicrosoftWindowsStore\"\r\n    $Name = \"RemoveWindowsStore\"\r\n    $Value = 1\r\n    \r\n    # Get each user profile SID and Path to the profile. If there are any exclusions we'll have to take them into account.\r\n    if ($ExcludeUsers -or $env:ExcludeUsers -or $ExistingUsersOnly) {\r\n        if ($env:ExcludeUsers) {\r\n            $ToBeExcluded = @()\r\n            $ToBeExcluded += $env:ExcludeUsers.split(\",\").trim()\r\n        }\r\n\r\n        if ($ExcludeUsers) {\r\n            $ToBeExcluded = @()\r\n            $ToBeExcluded += $ExcludeUsers.split(\",\").trim()\r\n        }\r\n\r\n        if ($ToBeExcluded) { \r\n            Write-Warning \"The Following Users and newly created users will not have the windows store disabled. $ToBeExcluded\"\r\n            $UserProfiles = Get-UserHives -ExcludedUsers $ToBeExcluded \r\n        }\r\n        elseif ($ExistingUsersOnly) { \r\n            Write-Warning \"Only existing users will have the windows store disabled!\"\r\n            $UserProfiles = Get-UserHives \r\n        }\r\n    }\r\n    else {\r\n        $UserProfiles = Get-UserHives -IncludeDefault\r\n    }\r\n\r\n    [xml]$AppLockerXML = '&lt;AppLockerPolicy Version=\"1\"&gt;&lt;RuleCollection Type=\"Appx\" EnforcementMode=\"Enabled\"&gt;&lt;FilePublisherRule Id=\"a9e18c21-ff8f-43cf-b9fc-db40eed693ba\" Name=\"(Default Rule) All signed packaged apps\" Description=\"Allows members of the Everyone group to run packaged apps that are signed.\" UserOrGroupSid=\"S-1-1-0\" Action=\"Allow\"&gt;&lt;Conditions&gt;&lt;FilePublisherCondition PublisherName=\"*\" ProductName=\"*\" BinaryName=\"*\"&gt;&lt;BinaryVersionRange LowSection=\"0.0.0.0\" HighSection=\"*\" \/&gt;&lt;\/FilePublisherCondition&gt;&lt;\/Conditions&gt;&lt;\/FilePublisherRule&gt;&lt;\/RuleCollection&gt;&lt;\/AppLockerPolicy&gt;'\r\n    $AppLockerXML.Save(\"$env:TEMPapplocker.xml\")\r\n    Set-AppLockerPolicy -XmlPolicy \"$env:TEMPapplocker.xml\" -Merge\r\n    Remove-Item \"$env:TEMPapplocker.xml\"\r\n\r\n    if (!$ToBeExcluded -and !$ExistingUsersOnly) {\r\n        New-WindowStoreBlock -User \"Interactive\"\r\n    }\r\n\r\n    $script:DisabledWinRun = $true\r\n    $failedUsers = @()\r\n    # Loop through each profile on the machine\r\n    Foreach ($UserProfile in $UserProfiles) {\r\n        # Load User ntuser.dat if it's not already loaded\r\n        If (($ProfileWasLoaded = Test-Path Registry::HKEY_USERS$($UserProfile.SID)) -eq $false) {\r\n            Start-Process -FilePath \"cmd.exe\" -ArgumentList \"\/C reg.exe LOAD HKU$($UserProfile.SID) `\"$($UserProfile.UserHive)`\"\" -Wait -WindowStyle Hidden\r\n        }\r\n\r\n        # Manipulate the registry\r\n        $key = \"Registry::HKEY_USERS$($UserProfile.SID)$($Path)\"\r\n        Set-HKProperty -Path $key -Name $Name -Value $Value -PropertyType DWord\r\n\r\n        # This will be our applocker policy we'll need to tweak it prior to running it\r\n        if ($UserProfile.SID -notlike \"DefaultProfile\") {\r\n            if ($ToBeExcluded -or $ExistingUsersOnly) {\r\n                New-WindowStoreBlock -User \"$($UserProfile.UserName)\"\r\n            }\r\n        }\r\n\r\n        if ($(Get-ItemProperty -Path $key -Name $Name -ErrorAction Ignore).$Name -ne $Value) {\r\n            $script:DisabledWinRun = $false\r\n            $failedUsers += $UserProfile.UserName\r\n        }\r\n        \r\n        # Unload NTuser.dat\r\n        If ($ProfileWasLoaded -eq $false) {\r\n            [gc]::Collect()\r\n            Start-Sleep 1\r\n            Start-Process -FilePath \"cmd.exe\" -ArgumentList \"\/C reg.exe UNLOAD HKU$($UserProfile.SID)\" -Wait -WindowStyle Hidden | Out-Null\r\n        }\r\n    }\r\n    \r\n    Start-Process -FilePath \"cmd.exe\" -ArgumentList \"\/C sc config `\"AppIDSvc`\" start=auto &amp; net start `\"AppIDSvc`\"\" -WindowStyle Hidden | Out-Null\r\n    Start-Sleep -Seconds 30\r\n    if ($script:DisabledWinRun) {\r\n        # All $UserProfiles updated\r\n        exit 0\r\n    }\r\n    else {\r\n        $failedUsers | ForEach-Object { Write-Error \"Failed to update user `\"$_`\"\" }\r\n        Write-Error \"One or more user profiles failed to update\"\r\n        exit 1\r\n    }\r\n}\r\nend {}<\/pre>\n<p>&nbsp;<\/p>\n\n<div class=\"in-context-cta\"><p>Acc\u00e9dez \u00e0 plus de 700 scripts dans le Dojo NinjaOne<\/p>\n<p><a href=\"https:\/\/www.ninjaone.com\/freetrialform\/\">Obtenez l&rsquo;acc\u00e8s<\/a><\/p>\n<\/div>\n<h2>Principales caract\u00e9ristiques du script<\/h2>\n<h3>V\u00e9rification des permissions \u00e9lev\u00e9es<\/h3>\n<p>Avant que le script ne puisse effectuer des modifications, il v\u00e9rifie s&rsquo;il est ex\u00e9cut\u00e9 avec des droits d&rsquo;administrateur. Cette fonction est essentielle pour appliquer les modifications aux param\u00e8tres du syst\u00e8me et aux comptes d&rsquo;utilisateurs.<\/p>\n<h3>Flexibilit\u00e9 des exclusions d&rsquo;utilisateurs<\/h3>\n<p>Si vous ne souhaitez pas appliquer les param\u00e8tres \u00e0 tous les utilisateurs, vous avez la possibilit\u00e9 de sp\u00e9cifier une liste d&rsquo;utilisateurs \u00e0 exclure, s\u00e9par\u00e9s par des virgules.<\/p>\n<h3>Option uniquement pour les utilisateurs existants<\/h3>\n<p>Si vous pr\u00e9f\u00e9rez ne pas affecter les comptes nouvellement cr\u00e9\u00e9s, il existe \u00e9galement un param\u00e8tre pour cela.<\/p>\n<h3>Manipulation du registre<\/h3>\n<p>Le script utilise le registre Windows pour appliquer les changements de strat\u00e9gie, en veillant \u00e0 ce qu&rsquo;elles soient profond\u00e9ment ancr\u00e9es et qu&rsquo;elles perdurent apr\u00e8s le red\u00e9marrage du syst\u00e8me.<\/p>\n<h3>Int\u00e9gration d&rsquo;AppLocker<\/h3>\n<p>Le script va au-del\u00e0 des simples modifications de registre en cr\u00e9ant \u00e9galement une r\u00e8gle AppLocker pour bloquer le Windows Store, ajoutant ainsi une couche de s\u00e9curit\u00e9 suppl\u00e9mentaire.<\/p>\n<h2>Comment les MSP peuvent en tirer parti<\/h2>\n<h3>Personnalisation en fonction du client<\/h3>\n<p>Gr\u00e2ce \u00e0 la possibilit\u00e9 d&rsquo;exclure des utilisateurs sp\u00e9cifiques, les MSP peuvent adapter le comportement du script aux besoins particuliers de chaque client.<\/p>\n<h3>\u00c9volutivit\u00e9<\/h3>\n<p>Que vous g\u00e9riez le r\u00e9seau d&rsquo;une petite entreprise ou d&rsquo;une multinationale, ce script s&rsquo;adapte sans effort, gr\u00e2ce \u00e0 ses capacit\u00e9s d&rsquo;automatisation.<\/p>\n<h3>Conformit\u00e9<\/h3>\n<p>De nombreux secteurs d&rsquo;activit\u00e9 imposent des r\u00e8gles de conformit\u00e9 strictes qui limitent l&rsquo;utilisation des applications. Ce script permet d&rsquo;assurer cette conformit\u00e9 en bloquant l&rsquo;acc\u00e8s aux applications non autoris\u00e9es du Windows Store.<\/p>\n<h3>Service \u00e0 valeur ajout\u00e9e<\/h3>\n<p>Les fournisseurs de services de gestion peuvent proposer ce service dans le cadre de leur offre de s\u00e9curit\u00e9, ce qui rend leurs services plus attrayants pour les clients potentiels.<\/p>\n<h2>Conclusion<\/h2>\n<p>La s\u00e9curit\u00e9 et la conformit\u00e9 sont les deux facettes de la <a href=\"https:\/\/www.ninjaone.com\/fr\/gestion-informatique-grande-entreprise\/\">gestion informatique<\/a>. Ce script PowerShell facilite la r\u00e9alisation de ces deux objectifs en automatisant le processus permettant de d\u00e9sactiver le Microsoft Store pour plusieurs comptes d&rsquo;utilisateurs, avec des options personnalisables pour diff\u00e9rents cas d&rsquo;utilisation. Les <a href=\"https:\/\/www.ninjaone.com\/fr\/efficacite\/\">professionnels de l&rsquo;informatique et les MSP peuvent gagner beaucoup de temps<\/a>, renforcer la s\u00e9curit\u00e9 et simplifier la gestion en int\u00e9grant ce script dans leurs flux de travail habituels.<\/p>\n","protected":false},"author":35,"featured_media":206954,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_relevanssi_hide_post":"","_relevanssi_hide_content":"","_relevanssi_pin_for_all":"","_relevanssi_pin_keywords":"","_relevanssi_unpin_keywords":"","_relevanssi_related_keywords":"","_relevanssi_related_include_ids":"","_relevanssi_related_exclude_ids":"","_relevanssi_related_no_append":"","_relevanssi_related_not_related":"","_relevanssi_related_posts":"","_relevanssi_noindex_reason":"","_lmt_disableupdate":"no","_lmt_disable":""},"operating_system":[4212],"use_cases":[4289],"class_list":["post-208385","script_hub","type-script_hub","status-publish","has-post-thumbnail","hentry","script_hub_category-windows"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/script_hub\/208385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/script_hub"}],"about":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/types\/script_hub"}],"author":[{"embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/users\/35"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/comments?post=208385"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/media\/206954"}],"wp:attachment":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/media?parent=208385"}],"wp:term":[{"taxonomy":"script_hub_category","embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/operating_system?post=208385"},{"taxonomy":"use_cases","embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/use_cases?post=208385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}