Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 0/410 docs · checked 21:27 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft 365 Apps Group Policy settings

2,420 settings · 5568.1000 · 10 Aug 2026

17 settingsCSV
Back to the list

Microsoft Project 2016 › Project Options › Schedule › Scheduling options for 'Project1'

Set default start date for new tasks

UserNeeds changes for IntuneL_SetDefaultStartDateForNewTasks

Supported on SUPPORTED_Windows7 (defined in the Windows templates)

What it does

This policy setting specifies the default start date for new tasks as they are entered in the current project. For projects scheduled from the start date, the options are "Start on Project Start Date" and "Start on Current Date." For projects scheduled from the finish date, the options are "Finish on Project Finish Date" and "Start on Current Date." If you enable or do not configure this policy setting, new tasks will start on the project start date. If you disable this policy setting, new tasks will not start on the project start date.

What it writes

Hive
HKEY_CURRENT_USER
Registry key
software\policies\microsoft\office\16.0\ms project\options\scheduling
Value name
new tasks start on current date
When enabled
DWORD 1
When disabled
DWORD 0
Why it needs changes for Intune
  • Policy references a Windows supportedOn definition.
  • ADMX-INTUNE-WINDOWS-SUPPORTEDON-REFERENCE

Configure and deploy

Choose a state; the output below is generated from the template for exactly that.

State

Enabled · User · template defaults

Registry file (.reg)

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\ms project\options\scheduling]
"new tasks start on current date"=dword:00000001


PowerShell

$ErrorActionPreference = 'Stop'

function Set-RegistryValue {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name,
        [Parameter(Mandatory = $true)][string] $PropertyType,
        [Parameter(Mandatory = $true)][object] $Value
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        New-Item -Path $Path -Force | Out-Null
    }

    New-ItemProperty -LiteralPath $Path -Name $Name -PropertyType $PropertyType -Value $Value -Force | Out-Null
}

function Remove-RegistryValue {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name
    )

    if (Test-Path -LiteralPath $Path) {
        Remove-ItemProperty -LiteralPath $Path -Name $Name -Force -ErrorAction SilentlyContinue
    }
}

function Clear-RegistryKeyValues {
    param(
        [Parameter(Mandatory = $true)][string] $Path
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        return
    }

    foreach ($propertyName in (Get-Item -LiteralPath $Path).Property) {
        Remove-ItemProperty -LiteralPath $Path -Name $propertyName -Force -ErrorAction SilentlyContinue
    }
}

# Policy: Set default start date for new tasks
# Name: L_SetDefaultStartDateForNewTasks
# Scope: User
# State: Enabled
# Source: proj16.admx

Set-RegistryValue -Path 'Registry::HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\ms project\options\scheduling' -Name 'new tasks start on current date' -PropertyType 'DWord' -Value 1
  • The OMA-URI is an inferred ADMX-backed Policy CSP candidate derived from the source ADMX file name and policy name.
  • Some Microsoft policies use built-in Policy CSP pages whose area names don't match the ADMX file name, so verify the candidate against Microsoft Learn before deployment.

ADMX profile candidate (OMA-URI)

./User/Vendor/MSFT/Policy/Config/ADMX_proj16/L_SetDefaultStartDateForNewTasks

ADMX SyncML candidate

<SyncML xmlns="SYNCML:SYNCML1.2">
  <SyncBody>
    <Replace>
      <CmdID>1</CmdID>
      <Item>
        <Meta>
          <Format>chr</Format>
          <Type>text/plain</Type>
        </Meta>
        <Target>
          <LocURI>./User/Vendor/MSFT/Policy/Config/ADMX_proj16/L_SetDefaultStartDateForNewTasks</LocURI>
        </Target>
        <Data>&lt;enabled/&gt;</Data>
      </Item>
    </Replace>
    <Final/>
  </SyncBody>
</SyncML>
Intune remediation scripts

Detection

$ErrorActionPreference = 'Stop'
$reasons = [System.Collections.Generic.List[string]]::new()

function Test-RegistryValueExists {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        return $false
    }

    return $null -ne (Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction SilentlyContinue)
}

function Test-RegistryValueEquals {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name,
        [Parameter(Mandatory = $true)][string] $Kind,
        [Parameter(Mandatory = $true)][object] $Expected
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        return $false
    }

    $valueObject = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction SilentlyContinue
    if ($null -eq $valueObject) {
        return $false
    }

    $actual = $valueObject.$Name
    switch ($Kind) {
        'String' { return [string]$actual -ceq [string]$Expected }
        'ExpandString' { return [string]$actual -ceq [string]$Expected }
        'DWord' { return [uint32]$actual -eq [uint32]$Expected }
        'QWord' { return [uint64]$actual -eq [uint64]$Expected }
        'MultiString' {
            $actualArray = @($actual)
            $expectedArray = @($Expected)
            if ($actualArray.Count -ne $expectedArray.Count) { return $false }
            for ($index = 0; $index -lt $actualArray.Count; $index++) {
                if ([string]$actualArray[$index] -cne [string]$expectedArray[$index]) { return $false }
            }
            return $true
        }
        'Binary' {
            $actualArray = [byte[]]$actual
            $expectedArray = [byte[]]$Expected
            if ($actualArray.Length -ne $expectedArray.Length) { return $false }
            for ($index = 0; $index -lt $actualArray.Length; $index++) {
                if ($actualArray[$index] -ne $expectedArray[$index]) { return $false }
            }
            return $true
        }
        default { return [string]$actual -ceq [string]$Expected }
    }
}

# Policy: Set default start date for new tasks
# Name: L_SetDefaultStartDateForNewTasks
# Scope: User
# State: Enabled
# Source: proj16.admx

$isMatch = Test-RegistryValueEquals -Path 'Registry::HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\ms project\options\scheduling' -Name 'new tasks start on current date' -Kind 'DWord' -Expected 1
if (-not $isMatch) {
    $reasons.Add('Value mismatch: HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\ms project\options\scheduling\new tasks start on current date') | Out-Null
}

if ($reasons.Count -eq 0) {
    Write-Output 'Compliant'
    exit 0
}

$reasons | ForEach-Object { Write-Output $_ }
exit 1

Remediation

$ErrorActionPreference = 'Stop'

function Set-RegistryValue {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name,
        [Parameter(Mandatory = $true)][string] $PropertyType,
        [Parameter(Mandatory = $true)][object] $Value
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        New-Item -Path $Path -Force | Out-Null
    }

    New-ItemProperty -LiteralPath $Path -Name $Name -PropertyType $PropertyType -Value $Value -Force | Out-Null
}

function Remove-RegistryValue {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name
    )

    if (Test-Path -LiteralPath $Path) {
        Remove-ItemProperty -LiteralPath $Path -Name $Name -Force -ErrorAction SilentlyContinue
    }
}

function Clear-RegistryKeyValues {
    param(
        [Parameter(Mandatory = $true)][string] $Path
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        return
    }

    foreach ($propertyName in (Get-Item -LiteralPath $Path).Property) {
        Remove-ItemProperty -LiteralPath $Path -Name $propertyName -Force -ErrorAction SilentlyContinue
    }
}

# Policy: Set default start date for new tasks
# Name: L_SetDefaultStartDateForNewTasks
# Scope: User
# State: Enabled
# Source: proj16.admx

Set-RegistryValue -Path 'Registry::HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\ms project\options\scheduling' -Name 'new tasks start on current date' -PropertyType 'DWord' -Value 1

History 1 retained release

  1. 5568.100010 Aug 2026
    • Already present in the first release ChangeIntel keeps.

Template

Internal name
L_SetDefaultStartDateForNewTasks
Namespace
proj16.Office.Microsoft.Policies.Windows
Template file
proj16.admx
Release
Microsoft 365 Apps 5568.1000 · file set 8be05d876aae137d…
Definition, editor controls and support

Definition

<policy class="User" displayName="$(string.L_SetDefaultStartDateForNewTasks)" explainText="$(string.L_SetDefaultStartDateForNewTasksExplain)" key="software\policies\microsoft\office\16.0\ms project\options\scheduling" name="L_SetDefaultStartDateForNewTasks" valueName="new tasks start on current date" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="proj16.Office.Microsoft.Policies.Windows:L_PjSchedDoc" />
      <supportedOn ref="Microsoft.Policies.Windows:SUPPORTED_Windows7" />
      <enabledValue>
        <decimal value="1" />
      </enabledValue>
      <disabledValue>
        <decimal value="0" />
      </disabledValue>
    </policy>

Editor controls

Supported platforms and category

proj16.Office.Microsoft.Policies.Windows:category:L_PjSchedDoc
<category displayName="$(string.L_PjSchedDoc)" name="L_PjSchedDoc" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="proj16.Office.Microsoft.Policies.Windows:L_PjSchedule" />
    </category>
proj16.Office.Microsoft.Policies.Windows:category:L_PjSchedule
<category displayName="$(string.L_PjSchedule)" name="L_PjSchedule" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="proj16.Office.Microsoft.Policies.Windows:L_ProjectOptions" />
    </category>
proj16.Office.Microsoft.Policies.Windows:category:L_Proj
<category displayName="$(string.L_Proj)" name="L_Proj" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions" />
proj16.Office.Microsoft.Policies.Windows:category:L_ProjectOptions
<category displayName="$(string.L_ProjectOptions)" name="L_ProjectOptions" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="proj16.Office.Microsoft.Policies.Windows:L_Proj" />
    </category>
proj16.Office.Microsoft.Policies.Windows:unresolved:Microsoft.Policies.Windows:SUPPORTED_Windows7
<unresolved reference="Microsoft.Policies.Windows:SUPPORTED_Windows7" />
proj16.Office.Microsoft.Policies.Windows:category:L_PjSchedDoc
<category displayName="$(string.L_PjSchedDoc)" name="L_PjSchedDoc" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="proj16.Office.Microsoft.Policies.Windows:L_PjSchedule" />
    </category>
<strings><string id="proj16.Office.Microsoft.Policies.Windows:L_PjSchedDoc">Scheduling options for 'Project1'</string></strings>
proj16.Office.Microsoft.Policies.Windows:category:L_PjSchedule
<category displayName="$(string.L_PjSchedule)" name="L_PjSchedule" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="proj16.Office.Microsoft.Policies.Windows:L_ProjectOptions" />
    </category>
<strings><string id="proj16.Office.Microsoft.Policies.Windows:L_PjSchedule">Schedule</string></strings>
proj16.Office.Microsoft.Policies.Windows:category:L_Proj
<category displayName="$(string.L_Proj)" name="L_Proj" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions" />
<strings><string id="proj16.Office.Microsoft.Policies.Windows:L_Proj">Microsoft Project 2016</string></strings>
proj16.Office.Microsoft.Policies.Windows:category:L_ProjectOptions
<category displayName="$(string.L_ProjectOptions)" name="L_ProjectOptions" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="proj16.Office.Microsoft.Policies.Windows:L_Proj" />
    </category>
<strings><string id="proj16.Office.Microsoft.Policies.Windows:L_ProjectOptions">Project Options</string></strings>
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Oct 21:27 UTC · 253 of 255 readable · 252 fully read · documentation 0/410 current