"IFMEMBER.EXE" error

  • Thread starter Thread starter Brad
  • Start date Start date
B

Brad

I use the ifmember.exe utility in our corp logon scripts. Some recent
changes have put some clients in more than 100 groups, and therefore
causes the Error 122 to occur.(KB article 290794).
I have started testing with the new and improved ifmember.exe, but to
complete successful logon, it takes about 4 minutes. My clients won't
be real thrilled about that :-)
Has anyone encountered this and resolved the problem? Thanks!
 
Brad said:
I use the ifmember.exe utility in our corp logon scripts. Some recent
changes have put some clients in more than 100 groups, and therefore
causes the Error 122 to occur.(KB article 290794).
I have started testing with the new and improved ifmember.exe, but to
complete successful logon, it takes about 4 minutes. My clients won't
be real thrilled about that :-)
Has anyone encountered this and resolved the problem? Thanks!
Click to expand...

Are you runninf ifmember every time to evaluate group membership?
Someone showed me nifty tip that runs ifmember once, dumping the results
into environment variables, and then referencing those in the rest of
the script, as opposed to enumerating the list w/ ifmember every time.

If you're interested, let me know, and I'll post the relevant parts of
our script.

hth
 
Are you runninf ifmember every time to evaluate group membership?
Someone showed me nifty tip that runs ifmember once, dumping the results
into environment variables, and then referencing those in the rest of
the script, as opposed to enumerating the list w/ ifmember every time.

If you're interested, let me know, and I'll post the relevant parts of
our script.

hth
Click to expand...
I am running it everytime the users login in to determine which of
three primary groups they belong to. In the cases that are causing the
problems, they actually belong to the group in the third statement, so
ifmember looks to be parsing three times to get to where it confirms
membership.
I think that even to run once, it will take over a minute, which is
not acceptable. The current version of ifmember we use runs in about 3
seconds (assuming the user is in less than 100 groups), so I need to
get close to that. I have a couple of othe options, like separate
scripts for the three primary groups, but I have about 20 regional
scripta that each contain the ifmember call, so I'd have to create 60
separate scripts instead of the 20 we have now. Another option is to
modify the groups they belong to, but that is more a management call
than technical :-)
 
Not quite the same problem but hoping you can help. I have 'inherited' ifmember.exe from a previous administrator so not sure which version I've got, though it's on a 2003 server.
My problem is that I am getting incorrect results from ifmember.exe. If I run the util with the /l switch the listed memberships do NOT match those I can see in the 'Properties/Member Of' tab for the user. Any ideas?
 
Back
Top