Platform: Windows Server 2019, 2022 and 2025, with the version and hosting restrictions described below.
Establish why the default identity is insufficient
ApplicationPoolIdentity is a useful default because it separates a pool’s local security context without introducing a manually managed password. A dedicated domain identity is justified when the application genuinely needs its own identity at a backend service or another specific resource. Changing accounts merely because a page reports access denied can mask a different request identity or an unrelated ACL problem.
For a managed Netcloud24 application, the service team configures the runtime identity and resource permissions during preparation. Customers should not be asked to supply a personal administrator account to make the site work. This workflow is for the authorised administrator changing a reviewed pool and coordinating its application dependencies.
Map the identities involved in the failing operation
The pool account controls its worker process, but a request can use another context through Anonymous Authentication, Windows Authentication, impersonation or explicit virtual-directory credentials. Determine which identity accesses the exact file or backend before deciding on a custom process account. A new pool credential will not override every application-supplied connection secret.
For network access, a virtual application-pool identity generally presents the server’s machine account, while a dedicated domain process account can present its own identity. User impersonation and Kerberos delegation introduce further requirements and are separate designs. Do not enable unconstrained delegation or broad domain privileges as a shortcut for an ordinary service-account access requirement.
Inventory code reads, data writes, certificate-key access, registry settings and remote services. Identify whether a user profile is genuinely required. Profile loading changes storage and context behaviour; it does not itself grant permissions.
Provision an account with an operational owner
Use a dedicated account such as CORP\svc-servicedesk, with an approved owner, credential storage and rotation policy. Avoid employee accounts and privileged groups. Apply interactive-logon restrictions consistent with the organisation’s policy and verify that the required pool logon type remains permitted. An applicable deny right can override a local allow.
A gMSA can reduce conventional password handling in a supported deployment, but it needs its own AD key-distribution, host authorisation and IIS configuration prerequisites. Do not substitute a name ending in a dollar sign into a normal password dialog and assume the design is complete. This article uses a conventional dedicated account so those credential and lifecycle responsibilities remain explicit.
Before the change, confirm account state, the approved password handover and any backend grants. Coordinate rotation with the application owner; a password changed only in AD can leave IIS unable to start the next worker process.
Record pool scope without exporting secrets
Protect an IIS configuration backup and record the current identity type and username. Identify every application sharing the pool, because all will experience the identity and recycle change. Do not export plaintext passwords into an incident bundle.
Import-Module WebAdministration
Get-Item 'IIS:\AppPools\ServiceDesk-Worker' |
Select-Object Name,@{Name='IdentityType';Expression={$_.processModel.identityType}},
@{Name='Account';Expression={$_.processModel.userName}}
Get-WebApplication | Select-Object Path,ApplicationPool,PhysicalPath
Get-Website | Select-Object Name,ApplicationPool,PhysicalPathCheck the site’s anonymous identity and any impersonation setting alongside the pool. A shared pool may need to be split before one application receives a distinct backend identity. That is a separate configuration change with its own acceptance test, rather than an invisible side effect of credential replacement.
Prepare narrow permissions before switching accounts
Give the account read and execute on application code and only the necessary rights on approved data locations. Keep runtime-writable data separate from deployable code where supported. The example grants Modify to a specific data directory, which includes normal deletion and therefore needs business approval.
icacls 'E:\Web\ServiceDesk' /grant:r 'CORP\svc-servicedesk:(OI)(CI)RX'
icacls 'E:\ServiceData\ServiceDesk' /grant:r 'CORP\svc-servicedesk:(OI)(CI)M'
icacls 'E:\Web\ServiceDesk'
icacls 'E:\ServiceData\ServiceDesk'Review inheritance and retain system and administrator recovery access. For an SMB dependency, both share and NTFS permissions must allow the operation. For a database, grant the application role rather than server-wide administration. If a certificate private key is needed, grant access to that key through the supported provider mechanism, not an unrelated broad directory ACL.
Enter credentials through protected IIS management
In IIS Manager, select the intended pool, open Advanced Settings and edit Process Model Identity. Choose Custom account and enter the dedicated identity through Set. Verify the account and apply the change through the supported management tooling, which protects configured credentials. Do not manually paste an unencrypted password into ApplicationHost.config.
Check the configured logon type and its user-right policy, commonly batch logon for this scenario. Domain Group Policy can replace a local exception; correct the managed policy rather than repeatedly re-adding a right. Never change the account to LocalSystem or make it a local administrator merely to suppress a startup error.
Keep credential entry out of PowerShell transcription and screenshots. If secure automation is required, design its secret retrieval and configuration handling explicitly rather than turning the password into a literal command-line argument in a reusable script.
Recycle the selected pool and exercise the real dependency
Coordinate the recycle because in-memory state and active requests can be affected. Generate a request if the worker starts on demand, then confirm the pool remains healthy. Inspect worker processes and events without displaying credentials.
Restart-WebAppPool -Name 'ServiceDesk-Worker'
Get-WebAppPoolState -Name 'ServiceDesk-Worker'
$appcmd = Join-Path $env:windir 'System32\inetsrv\appcmd.exe'
& $appcmd list wp
Get-WinEvent -FilterHashtable @{LogName='System';StartTime=(Get-Date).AddMinutes(-20)} `
-MaxEvents 60Test page delivery and the operation that required the new account, such as writing an approved report or accessing a backend. Confirm code remains non-writable and unrelated resources remain denied. Pool startup establishes that activation worked, not that the complete permission model is correct. Account for an overlapped-recycle transition when old and new workers briefly coexist.
Diagnose failure and keep rotation recoverable
Immediate 503 or pool shutdown warrants WAS evidence for invalid credentials, account lockout, expiry, missing logon rights or rapid-fail protection. Repeated restarts can worsen lockout. A running pool with one failed operation needs effective-identity and resource-specific checks, including old user-store certificates or backend grants.
Rollback restores the recorded identity through protected tooling and recycles only the affected pool. Retain logs and the new account’s evidence before removing obsolete grants. After acceptance, remove old permissions only when no other service uses them. Document the account owner, dependencies, profile setting, logon policy and rotation test. A managed application needs a maintainable identity lifecycle, not one powerful credential that temporarily makes every error disappear.
Preparing IIS for the application rather than installing every feature
Prepare IIS from the application’s runtime and exposure requirements, inspect installed modules, verify controlled requests and logs, and…
Building an IIS site with its own worker-process boundary
Build a dedicated IIS site and pool with deliberate runtime and anonymous identity, read-only code access and a unique staging response,…
Publishing the correct HTTPS identity from IIS
Publish an IIS HTTPS hostname by identifying TLS termination, validating the exact certificate and key, checking SNI and HTTP.sys state,…
Delivering an IIS file-transfer endpoint with mandatory TLS
Deliver an explicit IIS FTPS endpoint with required TLS on both channels, narrow partner permissions and a matched passive network path,…
Using AppCmd as one part of an IIS recovery plan
Use named AppCmd backups for controlled IIS configuration rollback while protecting content, data, keys and runtimes separately, then…