Office Admin Explorer

New tasks

Registry value
new tasks start on current date
Group PolicyNew tasks
German versionNeue Vorgänge
Intune settings catalogNew tasks (User)
ScopeUser · HKCU
ADMXproj16.admx · L_PjNewTasks
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Project 2016\Project Options\Schedule\Scheduling options for 'Project1'
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Project 2016\Projektoptionen\Zeitplan\Terminplanoptionen für 'Projekt1'

Registry

ValueData
HKCU\Software\policies\microsoft\office\16.0\ms project\options\scheduling
new tasks start on current date0 = Start on Project Start Date · 1 = Start on Current Date

Not configured = the value does not exist – the application default applies and users may change the setting.

PowerShell

Check the current value (read-only)

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\scheduling"
foreach ($name in @('new tasks start on current date')) {
    try   { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
    catch { '{0}: not configured' -f $name }
}

Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.

Enable

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

try {
    $key = "$root\Software\policies\microsoft\office\16.0\ms project\options\scheduling"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'new tasks start on current date' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # options: 0 = Start on Project Start Date, 1 = Start on Current Date
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Reset to Not configured
# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\scheduling"
Remove-ItemProperty -Path $key -Name 'new tasks start on current date' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

New tasks (User)

Settings catalog → Add settings → search for the name above.

Intune Settings Catalog Viewer ↗

Alternative: custom profile (OMA-URI)
OMA-URI
./User/Vendor/MSFT/Policy/Config/proj16v2~Policy~L_Proj~L_ProjectOptions~L_PjSchedule~L_PjSchedDoc/L_PjNewTasks
Data typeString
Value<enabled/> · <disabled/>

This policy has options: add one <data id="…" value="…"/> per element after <enabled/>. The element IDs are in the ADMX file.

Cloud Policy

Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for New tasks. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

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 this setting, new tasks will start on the date you specified.

If you disable or do not configure this setting, the user's default setting is used.

Same category: Microsoft Project 2016 › Project Options › Schedule › Scheduling options for 'Project1'

All policies in this category · All 140 policies of proj16.admx