Quote:

That one weird nick based on Björn

I ponder if a gpupdate would suffice *_* (prolly not)



Yeah, it's my nickname, given by some damn consultant some 11 years ago, it has stuck

I'll try that.

Quote:

What methodology was used in the vb script to check group membership?

How was the user forced to logoff using the vb script?

From what you wrote, it appears that the old process required a logoff and logon to work. Is this correct?

Define what happens when you say "run on the fly".



The vb-script used NTFS-permissions, i.ex tried to "copy" _everything_ to the client. This did not require any logoff for some reason, but the process was really, really slow on remote sites. Hence, they did not require to logon/logoff. The KIX-script was built using InGroup() and a configfile, to just copy the files necessary, however, this is not updated and re-running the script would not gain access to the new icons/files after adding the user to a domaingroup. Hope this clears things up abit regarding my silly "on-the-fly" wording.

Quote:

to reload the auth stuff, you would need to totally disconnect from the server and reconnect again.
if the credentials are part of the logon credentials, there is no way to refresh the rights than via re-logon.



Ok, my guess is that InGroup() is using the kerberos ticket gained at logon, hence I'd guess there's no way to force a re-creation of this in a easy way.

Thanks for the input, guys!

/Weird UNIX-guy trying to do things in the MS-world.