Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
PUP 4.10.10, PUP 5.3.4
-
None
-
Any version of Windows including 2008R2 and above (virtual accounts were introduced in 2008R2 / 7)
-
-
Windows
-
Windows Kanban
-
Customer Feedback
-
Normal
-
3 - 25-50% of Customers
-
3 - Serious
-
5 - $$$$$$
-
-
Bug Fix
-
-
Needs Assessment
Description
Steps to reproduce
1. Create Group "TestGroup" with "IIS AppPool\DefaultAppPool" as a member
group { 'TestGroup':
|
name => 'TestGroup',
|
ensure => present,
|
members => ['IIS AppPool\DefaultAppPool'],
|
auth_membership => false,
|
}
|
2. Re-run the same manifest
group { 'TestGroup':
|
name => 'TestGroup',
|
ensure => present,
|
members => ['IIS AppPool\DefaultAppPool'],
|
auth_membership => false,
|
}
|
3. Once the group exists on the system, Puppet fails to resolve the virtual account properly and generates an error like:
"Could not resolve name: DefaultAppPool"
|
Attachments
Issue Links
- duplicates
-
PUP-8295 Group resource cannot resolve virtual account "NT Service\Servicename"
-
- Closed
-
- is duplicated by
-
PUP-4208 Name Collision When Managing Users or Groups in Trusted Domains
-
- Closed
-
- relates to
-
PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
-
- Closed
-