I promise...I have read every post involving this topic and cannot get anything to work. I've been using Kixtart for years with no issue...I have depended heavily on the INGROUP function to do various things.
2008 R2 Active Directory KIX 4.62 XP clients work just fine as they always have Win7 SP1 clients do not. Win7 32 bit and 64 bit exhibit same behaviour
if ingroup("XYZ") = 1 ? "Member of group!" endif
The above script does not display anything The user in question belongs to the group User has logged off and back on I have flushed the cache both with /f and by deleting the registry key "TokenCache" I have tried to apply the hotfix 976494 but I get a message saying it does not apply (I assume because I am on SP1) I do NOT get the 1789 error in event log
I have run out of things to try...has anybody successfully gotten this to work *in today's environment*? (Meaning a fully patched and up to date Win7 SP1 client on 2008 AD.)
Glenn BarnasGlenn Barnas KiX Supporter
Registered: 2003-01-28
Posts: 4401
Loc: New Jersey
Welcome to KORG!
This works for me (after changing the group name)
Try
Code:
'Result: ' ingroup("XYZ") ?
@SERROR
and see what it returns. Testing for "1" isn't always the best, even though it should work in this case. Can you try a different group?
FYI - Our AD Forest/Domain is Windows 2008, servers are fully patched as of July's releases, and my workstation is W7-x64, again - fully patched. Kix version is 4.62. All servers are 2K8r2, all workstations are W7, mostly x64. There is one 2K3 test server and one XP test workstation still in the network.
Glenn
_________________________ Actually I am a Rocket Scientist!
If this is a new group, remember that you have to logoff and back on for the user to receive the new security token. And yes I have am using this with Windows 7 X64 SP1 clients, with a mix of servers and ADs all the way up to 2008 R2.
and see what it returns. Testing for "1" isn't always the best, even though it should work in this case. Can you try a different group?
Glenn
I'm probably missing something very obvious, but that code seems to be a single "active" element..."@SERROR". The other line is fully commented out, is it not? Is that really what you meant to post?
Registered: 2006-08-16
Posts: 687
Loc: Maryland, USA
Kixtart by default displays. So, Glenn's first line is text in single quotes. Kixtart would see that and just display it. By adding the function on the same line, Kixtart will evaluate that function and display the results. This is followed by the "?" which just says to display a carriage return and line feed. The next line is a macro which Kixtart will evaluate and display the results.
OK...my bad! I'm crossing languages & comment references.
Anyway...solved my problem. What has worked for years with XP in doing a conditional check using IF @WKSTA was no longer working and I was skipping past the majority of my script.
A VERY liberal use of print statements placed at strategic points finally brought me to the offending section. I was assuming.... (I know!)
Glenn BarnasGlenn Barnas KiX Supporter
Registered: 2003-01-28
Posts: 4401
Loc: New Jersey
Unike VB, Kix essentially treats pairs of single and double quotes the same. I have gotten into the habit long ago to use single quotes in Kix so I can pass double quotes to other apps that are more picky.. like VBscript!
Glenn
PS - Thanks for the explaination, Brad!
_________________________ Actually I am a Rocket Scientist!
