{"id":208376,"date":"2024-01-03T11:21:33","date_gmt":"2024-01-03T11:21:33","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/automatiser-gestion-outils-d-administration-windows-powershell\/"},"modified":"2024-03-14T15:27:01","modified_gmt":"2024-03-14T15:27:01","slug":"automatiser-gestion-outils-d-administration-windows-powershell","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/fr\/script-hub\/automatiser-gestion-outils-d-administration-windows-powershell\/","title":{"rendered":"Automatiser la gestion des outils d&rsquo;administration Windows avec ce script PowerShell indispensable"},"content":{"rendered":"<p>Si vous \u00eates un professionnel de l&rsquo;informatique ou un fournisseur de services g\u00e9r\u00e9s (MSP), vous savez qu&rsquo;assurer la s\u00e9curit\u00e9 du syst\u00e8me tout en maintenant la facilit\u00e9 d&rsquo;acc\u00e8s aux diff\u00e9rents outils d&rsquo;administration Windows est une t\u00e2che d\u00e9licate. C&rsquo;est l\u00e0 que les scripts PowerShell, comme celui d\u00e9crit ci-dessous, entrent en jeu.<\/p>\n<h2>Que fait le script ?<\/h2>\n<p>Le script vous permet d&rsquo;activer ou de d\u00e9sactiver les outils d&rsquo;administration Windows de votre choix sur une machine Windows. Les outils que vous pouvez manipuler comprennent l&rsquo;Invite de commande, le Panneau de configuration, la Console de gestion Microsoft (MMC), l&rsquo;\u00c9diteur de registre, la Fen\u00eatre d&rsquo;ex\u00e9cution des commandes et le Gestionnaire des t\u00e2ches. Le plus int\u00e9ressant, c&rsquo;est que vous pouvez ex\u00e9cuter ce script pour tous les profils utilisateur sur une machine, ou l&rsquo;appliquer de mani\u00e8re s\u00e9lective en fonction de profils utilisateur sp\u00e9cifiques.<\/p>\n<h2>Caract\u00e9ristiques cl\u00e9s<\/h2>\n<ul>\n<li><strong>Exclusion d&rsquo;utilisateurs<\/strong>: Le script permet d&rsquo;exclure des utilisateurs sp\u00e9cifiques, ce qui permet d&rsquo;adapter l&rsquo;acc\u00e8s de chaque utilisateur.<\/li>\n<li><strong>Contr\u00f4le des privil\u00e8ges \u00e9lev\u00e9s<\/strong>: Le script v\u00e9rifie qu&rsquo;il est ex\u00e9cut\u00e9 avec des privil\u00e8ges administrateur avant de s&rsquo;ex\u00e9cuter.<\/li>\n<li><strong>Manipulation des cl\u00e9s du registre<\/strong>: Il utilise PowerShell pour manipuler les cl\u00e9s de registre, garantissant ainsi que les modifications sont appliqu\u00e9es \u00e0 l&rsquo;ensemble du syst\u00e8me.<\/li>\n<\/ul>\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    This will enable the selected administrator tools depending on your selection (Defaults to all). Can be given a comma seperated list\/string of tools to be enabled.\r\n    Can also be given a comma seperated list of users to exclude from this action. Full Options: \"All\", \"Cmd\", \"ControlPanel\", \"MMC\", \"RegistryEditor\", \"Run\", \"TaskMgr\"\r\n.DESCRIPTION\r\n    This will enable the selected administrator tools. The options are \"All\", the command prompt, the control panel, the microsoft management console,\r\n    the registry editor, the run command window and task manager. You can give it a comma seperated list of items if you want to enable some but not all.\r\n    Exit 1 is usually an indicator of bad input but can also mean editing the registry is blocked.\r\n.EXAMPLE\r\n    PS C:&gt; .Enable-LocalAdminTools.ps1 -Tools \"MMC,Cmd,TaskMgr,RegistryEditor\"\r\n    Enabling MMC...\r\n    Set Registry::HKEY_USERSDefaultProfileSoftwarePoliciesMicrosoftMMCRestrictToPermittedSnapins to...\r\n    Enabling Cmd...\r\n    Set Registry::HKEY_USERSDefaultProfileSoftwarePoliciesMicrosoftWindowsDisableCMD to...\r\n    Enabling TaskMgr...\r\n    Set Registry::HKEY_USERSDefaultProfileSoftwareMicrosoftWindowsCurrentVersionPoliciesSystemDisableTaskMgr to...\r\n    Enabling RegistryEditor...\r\n    Set Registry::HKEY_USERSDefaultProfileSoftwareMicrosoftWindowsCurrentVersionPoliciesSystemDisableRegistryTools to...\r\n.OUTPUTS\r\n    None\r\n.NOTES\r\n    General notes: Will set the regkeys for users created after this script is ran.\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]$Tools = \"All\",\r\n    [Parameter()]\r\n    [String]$ExcludedUsers\r\n)\r\n\r\nbegin {\r\n    # Lets double check that this script is being run appropriately\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 \"[Error] 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\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)\"\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)\"\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\r\n                # It was easier to write-output twice than combine the two objects.\r\n                $DefaultProfile | Where-Object { $ExcludedUsers -notcontains $_.UserName } | Write-Output\r\n            }\r\n        }\r\n\r\n        $UserProfiles | Where-Object { $ExcludedUsers -notcontains $_.UserName } | Write-Output\r\n    }\r\n\r\n    function Set-Tool {\r\n        [CmdletBinding()]\r\n        param(\r\n            [Parameter()]\r\n            [ValidateSet(\"All\", \"Cmd\", \"ControlPanel\", \"MMC\", \"RegistryEditor\", \"Run\", \"TaskMgr\")]\r\n            [string]$Tool,\r\n            [string]$key\r\n        )\r\n        process {\r\n            # Each option has a different registry key to change. Since this function only supports 1 item at a time I can check which option and set the regkey individually.\r\n            Write-Host \"Enabling $Tool...\"\r\n            switch ($Tool) {\r\n                \"Cmd\" { Set-HKProperty -Path $keySoftwarePoliciesMicrosoftWindowsSystem -Name DisableCMD -Value 0 }\r\n                \"ControlPanel\" { Set-HKProperty -Path $keySoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer -Name NoControlPanel -Value 0 }\r\n                \"MMC\" { Set-HKProperty -Path $keySoftwarePoliciesMicrosoftMMC -Name RestrictToPermittedSnapins -Value 0 }\r\n                \"RegistryEditor\" { Set-HKProperty -Path $keySoftwareMicrosoftWindowsCurrentVersionPoliciesSystem -Name DisableRegistryTools -Value 0 }\r\n                \"Run\" { Set-HKProperty -Path $keySoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer -Name NoRun -Value 0 }\r\n                \"TaskMgr\" { Set-HKProperty -Path $keySoftwareMicrosoftWindowsCurrentVersionPoliciesSystem -Name DisableTaskMgr -Value 0 }\r\n                \"All\" {\r\n                    Set-HKProperty -Path $keySoftwarePoliciesMicrosoftWindowsSystem -Name DisableCMD -Value 0\r\n                    Set-HKProperty -Path $keySoftwareMicrosoftWindowsCurrentVersionPoliciesSystem -Name NoDispCPL -Value 0\r\n                    Set-HKProperty -Path $keySoftwarePoliciesMicrosoftMMC -Name RestrictToPermittedSnapins -Value 0\r\n                    Set-HKProperty -Path $keySoftwareMicrosoftWindowsCurrentVersionPoliciesSystem -Name DisableRegistryTools -Value 0\r\n                    Set-HKProperty -Path $keySoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer -Name NoRun -Value 0\r\n                    Set-HKProperty -Path $keySoftwareMicrosoftWindowsCurrentVersionPoliciesSystem -Name DisableTaskMgr -Value 0\r\n                }\r\n            }\r\n        }\r\n    }\r\n}\r\nprocess {\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 ($ExcludedUsers -or $env:ExcludedUsers) {\r\n        if ($env:ExcludedUsers) {\r\n            $ToBeExcluded = @()\r\n            $ToBeExcluded += $env:ExcludedUsers.split(\",\").trim()\r\n            Write-Warning \"The Following Users will not have your selected tools disabled. $ToBeExcluded\"\r\n        }\r\n        else {\r\n            $ToBeExcluded = @()\r\n            $ToBeExcluded += $ExcludedUsers.split(\",\").trim()\r\n            Write-Warning \"The Following Users will not have your selected tools disabled. $ToBeExcluded\"\r\n        }\r\n        $UserProfiles = Get-UserHives -IncludeDefault -ExcludedUsers $ToBeExcluded\r\n    }\r\n    else {\r\n        $UserProfiles = Get-UserHives -IncludeDefault\r\n    }\r\n\r\n    # Loop through each profile on the machine\r\n    Foreach ($UserProfile in $UserProfiles) {\r\n        # Load each user's registry hive if not already loaded. Backticked \"UserProfile.UserHive\" so that it accounts for spaces in the username.\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        # The path is different for each individual user. This is the base path.\r\n        $key = \"Registry::HKEY_USERS$($UserProfile.SID)\"\r\n\r\n        # List of checkbox items\r\n        $CheckboxItems = \"Cmd\", \"ControlPanel\", \"MMC\", \"RegistryEditor\", \"Run\", \"TaskMgr\"\r\n        # Checkboxes come in as environmental variables. This'll grab the ones that were selected (if any)\r\n        $EnvItems = Get-ChildItem env:* | Where-Object { $CheckboxItems -contains $_.Name }\r\n\r\n        # This will grab the tool selections from the parameter field. Since it comes in as a string we'll have to split it up.\r\n        $Tool = $Tools.split(\",\").trim()\r\n\r\n        # If the checkbox for all was selected I can just run the function once instead of running it repeatedly for the same thing.\r\n        if ($env:All) {\r\n            Set-Tool -Tool \"All\" -Key $key\r\n        }\r\n        elseif ($EnvItems) {\r\n            # If checkboxes were used we should just use those.\r\n            $EnvItems | ForEach-Object { Set-Tool -Tool $_.Name -Key $key }\r\n        }\r\n        else {\r\n            $Tool | ForEach-Object { Set-Tool -Tool $_ -Key $key }\r\n        }\r\n\r\n        # Unload NTuser.dat for user's we loaded previously.\r\n        If ($ProfileWasLoaded -eq $false) {\r\n            [gc]::Collect()\r\n            Start-Sleep -Seconds 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}\r\nend {\r\n    $ScriptVariables = @(\r\n        [PSCustomObject]@{\r\n            name           = \"All\"\r\n            calculatedName = \"all\"\r\n            required       = $false\r\n            defaultValue   = [PSCustomObject]@{\r\n                type  = \"TEXT\"\r\n                value = $true\r\n            }\r\n            valueType      = \"CHECKBOX\"\r\n            valueList      = $null\r\n            description    = \"All Admin Tools\"\r\n        }\r\n        [PSCustomObject]@{\r\n            name           = \"Cmd\"\r\n            calculatedName = \"cmd\"\r\n            required       = $false\r\n            defaultValue   = $null\r\n            valueType      = \"CHECKBOX\"\r\n            valueList      = $null\r\n            description    = \"Command Prompt\"\r\n        }\r\n        [PSCustomObject]@{\r\n            name           = \"ControlPanel\"\r\n            calculatedName = \"controlpanel\"\r\n            required       = $false\r\n            defaultValue   = $null\r\n            valueType      = \"CHECKBOX\"\r\n            valueList      = $null\r\n            description    = \"Control Panel\"\r\n        }\r\n        [PSCustomObject]@{\r\n            name           = \"MMC\"\r\n            calculatedName = \"mmc\"\r\n            required       = $false\r\n            defaultValue   = $null\r\n            valueType      = \"CHECKBOX\"\r\n            valueList      = $null\r\n            description    = \"Microsoft Management Console\"\r\n        }\r\n        [PSCustomObject]@{\r\n            name           = \"RegistryEditor\"\r\n            calculatedName = \"registryeditor\"\r\n            required       = $false\r\n            defaultValue   = $null\r\n            valueType      = \"CHECKBOX\"\r\n            valueList      = $null\r\n            description    = \"The Registry Editor\"\r\n        }\r\n        [PSCustomObject]@{\r\n            name           = \"Run\"\r\n            calculatedName = \"run\"\r\n            required       = $false\r\n            defaultValue   = $null\r\n            valueType      = \"CHECKBOX\"\r\n            valueList      = $null\r\n            description    = \"Run Command Window\"\r\n        }\r\n        [PSCustomObject]@{\r\n            name           = \"TaskMgr\"\r\n            calculatedName = \"taskmgr\"\r\n            required       = $false\r\n            defaultValue   = $null\r\n            valueType      = \"CHECKBOX\"\r\n            valueList      = $null\r\n            description    = \"Task Manager\"\r\n        }\r\n        [PSCustomObject]@{\r\n            name           = \"ExcludedUsers\"\r\n            calculatedName = \"excludedusers\"\r\n            required       = $false\r\n            defaultValue   = $null\r\n            valueType      = \"TEXT\"\r\n            valueList      = $null\r\n            description    = \"Comma separated list of users you would like to exclude.\"\r\n        }\r\n    )\r\n}<\/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\/fr\/phase-de-test-gratuit\/\">Obtenez l&rsquo;acc\u00e8s<\/a><\/p>\n<\/div>\n<h2>Pourquoi ce script est-il utile aux professionnels de l&rsquo;informatique et aux entreprises MSP ?<\/h2>\n<ol>\n<li><strong>Contr\u00f4le centralis\u00e9<\/strong>: Ce script vous permet de contr\u00f4ler plusieurs profils d&rsquo;utilisateurs de mani\u00e8re centralis\u00e9e, ce qui permet de gagner du temps et de r\u00e9duire les erreurs humaines.<\/li>\n<li><strong>S\u00e9curit\u00e9<\/strong>: En d\u00e9sactivant certains outils d&rsquo;administration Windows, vous pouvez vous assurer que votre syst\u00e8me est prot\u00e9g\u00e9 contre les menaces internes et externes.<\/li>\n<li><strong>Facilit\u00e9 d&rsquo;utilisation<\/strong>: Le script est explicite et comporte une multitude d&rsquo;options permettant de personnaliser vos param\u00e8tres.<\/li>\n<li><strong>Automatisation<\/strong>: Il peut \u00eatre int\u00e9gr\u00e9 dans un grand processus d&rsquo;automatisation, ce qui permet de simplifier les t\u00e2ches de configuration du syst\u00e8me.<\/li>\n<li><strong>Option de retour en arri\u00e8re<\/strong>: Comme le script manipule des cl\u00e9s de registre, les modifications peuvent \u00eatre facilement annul\u00e9es si n\u00e9cessaire.<\/li>\n<\/ol>\n<h2>Comment utiliser le script<\/h2>\n<ol>\n<li><strong>T\u00e9l\u00e9charger et ouvrir<\/strong>: T\u00e9l\u00e9chargez le script et ouvrez PowerShell en tant qu&rsquo;administrateur.<\/li>\n<li><strong>Ex\u00e9cuter<\/strong>: Ex\u00e9cutez le script en sp\u00e9cifiant les outils que vous souhaitez activer ou d\u00e9sactiver. Par exemple, pour activer uniquement le Gestionnaire des t\u00e2ches et l&rsquo;Invite de commande, vous devez ex\u00e9cuter la commande suivante :<br \/>\n<\/li>\n<li><strong>V\u00e9rifier<\/strong>: Une fois l&rsquo;ex\u00e9cution termin\u00e9e, v\u00e9rifiez que les modifications ont \u00e9t\u00e9 appliqu\u00e9es en vous connectant aux comptes d&rsquo;utilisateurs respectifs.<\/li>\n<\/ol>\n<h2>Conclusions<\/h2>\n<p>Dans le monde technologique actuel, qui \u00e9volue rapidement, l&rsquo;importance de solutions de gestion de syst\u00e8mes performantes, \u00e9volutives et flexibles est incontestable. Ce script PowerShell offre aux professionnels de l&rsquo;informatique et aux MSP un outil puissant pour personnaliser la gestion des outils d&rsquo;administration Windows. Lorsqu&rsquo;il est utilis\u00e9 avec une <a href=\"https:\/\/www.ninjaone.com\/fr\/\">plateforme de gestion informatique<\/a> compl\u00e8te comme NinjaOne, vous pouvez non seulement simplifier mais aussi amplifier vos capacit\u00e9s d&rsquo;administration de syst\u00e8me.<\/p>\n<p>Alors allez-y, d\u00e9ployez le script, <a href=\"https:\/\/www.ninjaone.com\/fr\/phase-de-test-gratuit\">essayez NinjaOne<\/a> et d\u00e9couvrez par vous-m\u00eame le futur de la gestion informatique efficace, s\u00e9curis\u00e9e et performante.<\/p>\n","protected":false},"author":35,"featured_media":206993,"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":[4287],"class_list":["post-208376","script_hub","type-script_hub","status-publish","has-post-thumbnail","hentry","script_hub_category-windows","use_cases-configuration-de-systeme"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/script_hub\/208376","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=208376"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/media\/206993"}],"wp:attachment":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/media?parent=208376"}],"wp:term":[{"taxonomy":"script_hub_category","embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/operating_system?post=208376"},{"taxonomy":"use_cases","embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/use_cases?post=208376"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}