Anaqua

WiseTime is part of Anaqua Inc., IP Management Solutions & Services.

About Anaqua
WiseTime

Enterprise Desktop App Auto-Update Policy Configuration

7 months ago · Updated

WiseTime Desktop App supports enterprise deployment with centralized control over auto-update functionality. IT administrators can disable auto-updates via Windows registry policy, allowing them to manage updates through their preferred deployment mechanisms (MSI, SCCM, etc.).

The article covers:

  1. Windows Registry Configuration
  2. Behavior When Auto-Update is Disabled
  3. Verification
  4. Deployment Scenarios
  5. Best Practices
  6. Troubleshooting
  7. Security Considerations
  8. Compatibility
  9. Support

Windows Registry Configuration

Registry Location

  • Registry HiveHKEY_LOCAL_MACHINE
  • Key PathSOFTWARE\PracticeInsight\WiseTime
  • Value NameDisableAutoUpdate
  • Value TypeDWORD (32-bit)
  • Value Data:
    • 1 = Disable auto-updates (enterprise managed)
    • 0 or absent = Enable auto-updates (default behavior)

Configuration Methods

# Run as Administrator
New-Item -Path "HKLM:\SOFTWARE\PracticeInsight" -Name "WiseTime" -Force
Set-ItemProperty -Path "HKLM:\SOFTWARE\PracticeInsight\WiseTime" -Name "DisableAutoUpdate" -Value 1 -Type DWORD

# To re-enable auto-updates
Set-ItemProperty -Path "HKLM:\SOFTWARE\PracticeInsight\WiseTime" -Name "DisableAutoUpdate" -Value 0 -Type DWORD

# To remove the policy (reverts to default behavior)
Remove-ItemProperty -Path "HKLM:\SOFTWARE\PracticeInsight\WiseTime" -Name "DisableAutoUpdate" -ErrorAction SilentlyContinue

Method 2: Registry Editor (regedit)

  1. Open Registry Editor as Administrator
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE
  3. Create key structure: PracticeInsight\WiseTime (if not exists)
  4. Right-click in the right pane → New → DWORD (32-bit) Value
  5. Name: DisableAutoUpdate
  6. Value: 1 to disable, 0 to enable

Method 3: Registry File (.reg)

Create a .reg file and deploy via Group Policy or run manually:

To disable auto-updates:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\PracticeInsight\WiseTime]
"DisableAutoUpdate"=dword:00000001

To enable auto-updates:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\PracticeInsight\WiseTime]
"DisableAutoUpdate"=dword:00000000

Method 4: Group Policy Deployment

  1. Create custom ADM/ADMX template or use registry preferences
  2. Deploy to target computers via Group Policy
  3. Registry setting will be applied on next policy refresh

Behavior When Auto-Update is Disabled

When the DisableAutoUpdate registry key is set to 1:

Automatic Updates

  • Periodic background update checks are disabled
  • Automatic download and installation is disabled
  • Update notifications are not shown

User Interface Changes

  • “Check for Updates” menu items are hidden from:
    • Application main menu (WiseTime → Check for Updates)
    • System tray context menu
  • Updates tab is hidden from Preferences dialog
  • Manual update checks via UI are disabled

Manual Update Attempts

  • If user somehow triggers update check, they will see an error state
  • No update-related network requests are made

Verification

Check Current Policy Status

# Check if auto-update is disabled by policy
$regPath = "HKLM:\SOFTWARE\PracticeInsight\WiseTime"
$regName = "DisableAutoUpdate"

if (Test-Path $regPath) {
    $value = Get-ItemProperty -Path $regPath -Name $regName -ErrorAction SilentlyContinue
    if ($value.$regName -eq 1) {
        Write-Host "Auto-update is DISABLED by enterprise policy"
    } elseif ($value.$regName -eq 0) {
        Write-Host "Auto-update is ENABLED by enterprise policy"
    } else {
        Write-Host "Auto-update policy not set (default: ENABLED)"
    }
} else {
    Write-Host "Auto-update policy not set (default: ENABLED)"
}

Application Logs

The application logs will show:

AppUpdater: Registry key SOFTWARE\PracticeInsight\WiseTime/DisableAutoUpdate = 1, auto-update disabled: true
AppUpdater: Auto-update is disabled by enterprise policy, skipping periodic checking

Deployment Scenarios

Scenario 1: Fresh Installation with Policy

  1. Deploy MSI with auto-update policy pre-configured
  2. Application will start without auto-update functionality
  3. IT can manage updates centrally via MSI upgrades

Scenario 2: Existing Installation - Disable Updates

  1. Deploy registry policy to existing installations
  2. Restart application (or wait for next launch)
  3. Auto-update functionality will be disabled

Scenario 3: Mixed Environment

  1. Some machines with policy (managed updates)
  2. Some machines without policy (auto-updates enabled)
  3. Both configurations can coexist

Best Practices

For IT Administrators

  • Test policy in development environment first
  • Use Group Policy for centralized deployment
  • Document update management procedures
  • Plan regular update cycles for managed machines
  • Monitor application logs for policy verification

For Deployment

  • Set policy before first application launch if possible
  • Include registry configuration in MSI deployment scripts
  • Verify policy deployment across target machines
  • Provide fallback procedure if policy needs to be reverted

Troubleshooting

Policy Not Working

  1. Verify registry path and value name are correct
  2. Check registry permissions (should be readable by all users)
  3. Restart the application
  4. Check application logs for policy detection

Policy Deployment Issues

  1. Verify Group Policy is applied (gpupdate /force)
  2. Check registry on target machines manually
  3. Ensure PowerShell scripts run with Administrator privileges
  4. Validate .reg file syntax if using registry files

Reverting Policy

# Remove the registry value entirely
Remove-ItemProperty -Path "HKLM:\SOFTWARE\PracticeInsight\WiseTime" -Name "DisableAutoUpdate" -ErrorAction SilentlyContinue

# Or set to 0 to explicitly enable
Set-ItemProperty -Path "HKLM:\SOFTWARE\PracticeInsight\WiseTime" -Name "DisableAutoUpdate" -Value 0 -Type DWORD

Security Considerations

  • Registry key is in HKLM (requires administrator access to modify)
  • User-level registry (HKCU) is not checked to prevent user override
  • Policy affects all users on the machine
  • No sensitive data is stored in the registry key

Compatibility

  • Supported Platforms: Windows only
  • Registry Location: Machine-wide (HKLM)
  • Application Versions: v4.0+ (with enterprise policy support)
  • Windows Versions: Windows 10, Windows 11, Windows Server 2016+

Support

For enterprise deployment support:

  • Contact: support@wisetime.com
  • Include application version and deployment method in support requests.

Was this article helpful?

Have more questions? Contact Support

Need some help? We’re here for you.

Submit your details and we’ll be in touch.


Psssst! Have you tried our Help section?