http://bugzilla.wpkg.org/show_bug.cgi?id=208 edv at platzer-statik.at changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |edv at platzer-statik.at Resolution|FIXED | --- Comment #7 from edv at platzer-statik.at --- As a matter of fact the domain groups may not be correctly retrieved under certain circumstances. In my environment, the code down below (copied from wpkg.js) does not get group membership for hosts running XP Pro SP3 x86 but works for hosts running XP Pro x64. The domain is a 2003 AD with a (german) 2003 R2 Domain Controller, tested with 1.2 and 1.2.1RC45. Based on my experience with AD, "Computer"-accounts and groups it may be better to check if the computer-account is a member of a specific group and not do it like in the current implementation. -- Output: # cscript /nologo list-group.js * Groups of Computer: XPPRO-2 Domänencomputer * Computers in group: software-basis SWTEST01$ SWTEST02$ XPPRO-2$ -- Code: var HostName='XPPRO-2'; var GroupName='software-basis' var DomainName='testdom.local'; var comp = GetObject("WinNT://" + DomainName + "/" + HostName + "$,user") ; var grp = GetObject("WinNT://" + DomainName + "/" + GroupName + ",group") ; var Members = grp.Members(); var Groups = comp.Groups(); var compList = new Enumerator(Groups); var grpList = new Enumerator(Members) WScript.Echo("* Groups of Computer: " + HostName); for (; !compList.atEnd(); compList.moveNext() ) { var group = compList.item(); WScript.Echo(group.Name); } WScript.Echo("* Computers in group: " + GroupName); for (; !grpList.atEnd(); grpList.moveNext() ) { var member = grpList.item(); WScript.Echo(member.Name); } -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |