I don't want to start the whole 'VBScript vs. CMD file vs. Kix' debate again, but I will just say that VBScript is way faster than using IFMEMBER and REG. I rewrote a customer's 1700 line CMD login script in VBScript and it went from minutes to seconds. I do agree that it's more complicated to write VBScript, but the payoff for a little learning is tremendous. Jeff Durbin -----Original Message----- From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx] Sent: Wednesday, September 03, 2003 9:51 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Hidedrives You don't even need vbscript - you could do it with cmd files and resource kit utilities (IFMEMBER.EXE and REG.EXE). And whilst I do quite a bit of vbscript / WSH / ADSI stuff, this would be more complex via vbscript than it needs to be. You would have to use WSH (either that, or WMI) to access the registry, and rather convoluted stuff in ADSI to establish group membership. Whereas using command files, or say something like Kix it's all very direct - one-liners for both the group membership check, and the registry writes. Neil > -----Original Message----- > From: Durbin, Jeff [mailto:jdurbin@xxxxxxxxxxxxxxxxxxx] > Sent: 03 September 2003 17:45 > To: thin@xxxxxxxxxxxxx > Subject: [THIN] Re: Hidedrives > > > No, but as a workaround, you could use a VBScript to set the > reg key based on group membership during logins. Just be sure > to call it before Explorer loads. If I remember correctly, if > you call it from USRLOGON.CMD, that runs before Explorer. If > not, call it from AppSetup in WinLogon. > > Jeff Durbin > > -----Original Message----- > From: Chris Fraser [mailto:chrisfraser@xxxxxxxxxx] > Sent: Tuesday, September 02, 2003 2:16 PM > To: thin@xxxxxxxxxxxxx > Subject: [THIN] Hidedrives > > > Hello all, > > I've implemented system policies (nt4 style, not GPOs) on a > newly built win2k sp3 server in an NT4 domain. > > I have an issue where the policy for hiding drives does not > stick. If I set the policy, save the file, close poledit and > then open it up again, the setting has been greyed out. > Drives are still visible to users on the system. > > I have created a separate template (hidedrives.adm) for > hiding drives so that I do not need to edit the standard > ADMs. I have insured that there is no other place in the > policy that I have configured the drive visibility. > > Has anyone else seen this issue? *********************************************** This e-mail and its attachments are confidential and are intended for the above named recipient only. If this has come to you in error, please notify the sender immediately and delete this e-mail from your system. You must take no action based on this, nor must you copy or disclose it or any part of its contents to any person or organisation. Statements and opinions contained in this email may not necessarily represent those of Littlewoods. Please note that e-mail communications may be monitored. The registered office of Littlewoods Limited and its subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB. Registered number of Littlewoods Limited is 262152. ************************************************ ******************************************************** This Week's Sponsor: ThinPrint http://www.thinprint.com ********************************************************** Useful Thin Client Computing Links are available at: http://thethin.net/links.cfm For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm ******************************************************** This Week's Sponsor: ThinPrint http://www.thinprint.com ********************************************************** Useful Thin Client Computing Links are available at: http://thethin.net/links.cfm For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm