# Deployment

When you are ready to deploy your AutopilotOOBE Configuration Json, there are three methods to do this

## Command Line

I'd advise against this as this is quite a bit to type in, but it is absolutely possible. Good Luck!

```
$Params = @{
    Title = 'OSDeploy Autopilot Registration'
    GroupTag = 'Enterprise'
    GroupTagOptions = 'Development','Enterprise'
    Hidden = 'AddToGroup','AssignedComputerName','AssignedUser','PostAction'
    Assign = $true
    Run = 'NetworkingWireless'
    Docs = 'https://autopilotoobe.osdeploy.com/'
}
AutopilotOOBE @Params
```

## CustomProfile

You can easily send me your Configuration Json and I can add it to the AutopilotOOBE PowerShell Module.  Once it is published, you will be able to use it right away as long as you install the latest AutopilotOOBE PowerShell Module

![](https://2658300904-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbqMV0UfDLtVGCCM8EV%2F-MfvFzdHwVsq4vcP_MdR%2F-MfvPBFlr_OIm3TlF21_%2Fimage.png?alt=media\&token=04dbd63f-7896-4be7-a70f-222d3f0f6321)

In OOBE, you simply add your CustomProfile name as an AutopilotOOBE parameter and it will import the CustomProfile to your ProgramData.  This will ensure that any subsequent execution of AutopilotOOBE is customized for your Organization

![](https://2658300904-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbqMV0UfDLtVGCCM8EV%2F-MfvFzdHwVsq4vcP_MdR%2F-MfvPSBPzLML0d8pTHye%2Fimage.png?alt=media\&token=919d62aa-f4b3-4f14-829a-d4a7a7ed3aba)

![](https://2658300904-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbqMV0UfDLtVGCCM8EV%2F-MfvFzdHwVsq4vcP_MdR%2F-MfvPiiTieXO-TDK5G12%2Fimage.png?alt=media\&token=95c69b4d-eab9-4e66-bb76-4382bb757e91)

## Configuration Json Staging

If you are going to image the Device , then you can also save the Configuration Json in WinPE after your Operating System has been expanded to the Hard Disk.  This will ensure that AutopilotOOBE will always be executed with your configuration

### OSDHelp AutopilotOOBE

An example on how to do this is in OSDHelp which is part of the OSD PowerShell Module

```
Install-Module OSD -Force
Import-Module OSD -Force
OSDHelp AutopilotOOBE
```

![](https://2658300904-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbqMV0UfDLtVGCCM8EV%2F-MhRmK1UfZcRViUCNRhd%2F-MhRqC-uc1JexXGl6698%2Fimage.png?alt=media\&token=156a8127-d485-4c08-b8ff-6ec2f49c79a1)

### OSDCloud

If you are using OSDCloud, you can apply the Configuration Json in a method similar to the script below, after Start-OSDCloud has completed

```
#=======================================================================
#   OS: Params and Start-OSDCloud
#=======================================================================
$Params = @{
    OSBuild = "21H1"
    OSEdition = "Pro"
    OSLanguage = "en-us"
    OSLicense = "Retail"
    SkipAutopilot = $true
    SkipODT = $true
}
Start-OSDCloud @Params

#=======================================================================
#   PostOS: AutopilotOOBE Staging
#=======================================================================
$AutopilotOOBEJson = @'
{
    "Assign":  {
                   "IsPresent":  true
               },
    "GroupTag":  "Enterprise",
    "GroupTagOptions":  [
                            "Development",
                            "Enterprise"
                        ],
    "Hidden":  [
                   "AddToGroup",
                   "AssignedComputerName",
                   "AssignedUser",
                   "PostAction"
               ],
    "PostAction":  "Quit",
    "Run":  "NetworkingWireless",
    "Docs":  "https://autopilotoobe.osdeploy.com/",
    "Title":  "OSDeploy Autopilot Registration"
}
'@
$AutopilotOOBEJson | Out-File -FilePath "C:\ProgramData\OSDeploy\OSDeploy.AutopilotOOBE.
```

## Sponsors

{% embed url="<https://www.recastsoftware.com/?utm_source=osdeploy&utm_medium=ad&utm_campaign=web>" %}
OSDeploy is sponsored by Recast Software
{% endembed %}