[wpkg-users] [Bug 273] Per user install support
bugzilla-daemon at bugzilla.wpkg.org
bugzilla-daemon at bugzilla.wpkg.org
Mon May 21 23:07:38 CEST 2012
http://bugzilla.wpkg.org/show_bug.cgi?id=273
--- Comment #15 from Stefan Pendl <pendl2megabit at yahoo.de> ---
(In reply to comment #14)
>
> Could "usergroup" match against a more fully qualified group name?ie
> "domain\usergroup" or "usergroup at domain.tld". Could it also be supported by a
> "user" attribute that supplies the same for a user account? What I'm thinking
> is that both your and Stephan's solutions work brilliantly but they're limited
> to using the value of %USERNAME%. That leaves a big grey area where people
> might want to discriminate between local or domain users/groups. I could extend
> your option by using /host:"%DOMAIN%\%USERNAME%" but you can't do that easily
> with Stephan's offer as it involves working out how two environment variable
> comparisons work (I'm not sure how WPKG deals with multiple attributes as
> filters yet).
>
<host profile-id="OfficeSimple">
<condition>
<check type="host" condition="environment" value="USERNAME=^Georg$"/>
<check type="host" condition="environment" value="USERDOMAIN=^Company$"/>
</condition>
</host>
<host profile-id="OfficeSimple">
<condition>
<check type="host" condition="environment" value="USERNAME=^Georg$"/>
<check type="host" condition="environment"
value="USERDNSDOMAIN=^Company.com$"/>
</condition>
</host>
One could now build a command script to execute NET GROUP /DOMAIN or NET
LOCALGROUP and parse the output for the user name.
This could be added as an execute file check.
--
Stefan
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the wpkg-users
mailing list