Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Duplicate
-
None
-
None
-
Windows Server 2016 Desktop Experience
Description
When setting an application pool to run as 'No Managed Code', the Puppet Forge documentation (v. 4.3.2) suggests setting managed_runtime_version => '""',. This should result in the application pool running as 'No Managed Code'
While this seems to function as intended, the node will continually loop through an intentional change:
2018-08-06 14:53 Z |
notice | managed_runtime_version changed '' to '""' * Source:/Stage[main]/REDACTED_web_services::REDACTED/Iis_application_pool[REDACTED]/managed_runtime_version
|
Example Code causing this behavior:
# Sets managed runtime version to no managed code |
iis_application_pool { 'REDACTED': |
ensure => 'present', |
managed_pipeline_mode => 'Integrated', |
managed_runtime_version => '""', |
state => 'Started', |
auto_start => true, |
identity_type => 'SpecificUser', |
user_name => $iis_user, |
password => $iis_password, |
}
|
|
|
Attachments
Issue Links
- is duplicated by
-
MODULES-9236 IIS : Setting Application pool .NET CLR Version to No Managed Code in 2008 R2 does not work
-
- Closed
-
- relates to
-
MODULES-7820 IIS: Trying to set 'No Managed Code' not working
-
- Resolved
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...