This is great information. There are other options, Kix32, testgrp.exe, ect., but they all have there share of problems! I currently am useing a product that work flawlessly except for one drawback. I have discovered that in a mutli-dc enviroment where a star, spoke, network design has been implimented the testgrp.exe will not verify that the login user is a member of the specified group if the circuit is broken. This is a problem due to the need to insure that the login user can still get to data, drive mappings, to the servers on his side of the wire "Local LAN" So my question about ifmember.exe is "Has anyone ever deployed this solution is an enterprise enviroment with muti remote locations? Each remote having a BDC for fault tolerence regarding attenication and to reduce the need to have addition traffic go accross the WAN ciruits. If you have tested this what happened in the event of a ciruit outage? Did the ifmember.exe arp out the request for athenication, hence the bdc answered the call or did the script through errors?
CodeCore --