'Getting' Application Pools is Very Slow

hi,

so, i've been experiencing rather strange issue powershell , iis time now. after searching web answers , finding none, came work-around resolved issue time being. however, we're beginning powershell dsc, , we're running same issue previously. please keep in mind, while issue impeding our test dsc, issue appears powershell , our windows 2012 r2 servers, not dsc.

situation:

we have automated process (a bunch of powershell, basically) configures our applications , deploys them - including web applications hosted in iis. 1 servers (consistently same ones, though), following command can take anywhere 2 8 minutes execute:

get-childitem iis:\apppools | ? {$_.name -eq "some-application-pool-name"}

more recently, i've found powershell dsc using xwebadministration module takes 120-125 seconds configure application pool. appears stuck here:

    # xpath -filter case-sensitive. use where-object target application pool name.
    $apppool = get-webconfiguration -filter '/system.applicationhost/applicationpools/add' |
        where-object -filterscript {$_.name -eq $name}

i don't see problem on of our servers, in particular case testing powershell dsc, 2 servers i'm comparing identical (literally same vm template). difference 1 acting our pull server while other acting node configured. yet, 1 shows behavior while other not. i've tried multiple methods 'get' application pools or specific one, take 2 minutes or more execute. 'get' first few default application pools, gets stuck when 'getting' ones made.

i monitored situation using procmon once. difference noticed powershell sessions on servers showing behavior reach registry twice, while other powershell sessions on servers not showing behavior once. have no explanation why, , didn't seem take significant amount of time.

i've seen issue disappear once , once only. after running dsc configuration, manually changed security settings of application pool:

1) changed application pool identity default ("applicationpoolidentity").

2) applied change.

3) went , changed application pool identity 'custom account'.

4) entered service account credentials in manually.

once noticed this, removed website , corresponding application pool , attempted run dsc configuration once more. , once more, took 120-125 seconds execute. has noticed issue before? has created serious obstacle our attempts further automate our server , application configurations.

this issue should posted here: http://forums.iis.net since not scripting question yu have proven.

---

\_(ツ)_/

Windows Server  >  Windows PowerShell