[THIN] Re: ifmember.exe question
- From: "Pavlo Ignatusha" <pignatusha@xxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Thu, 30 Sep 2004 12:12:53 -0400
Neil,
This is strange cause I sent you the whole listing of the final script after
I was done. Yes I fixed error by installing manually WSH 5.6. on the DC.
I can re-send the listing if you interested.
Thanks,
Pavlo Ignatusha
Systems Network Coordinator
Pembroke General Hospital
Tel. (613) 732-3675 ext.6150
Fax. (613) 732-9986
www.pemgenhos.org
"All that matters is love and work" - Sigmund Freud.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf
Of Braebaum, Neil
Sent: Thursday, September 30, 2004 11:52 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: ifmember.exe question
I've always been OK with Kix being in NETLOGON - but if your network
isn't the quickest, you could always cache it locally at login, if it
isn't already there (ie have a wrapper cmd file, and copy Kix locally if
it doesn't already exist).
Neil
PS: I didn't get your messages to my private email when I was at home,
so that's why there was a delay, did you get getname() to be happy with
non-existent users?
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Pavlo Ignatusha
> Sent: 30 September 2004 16:38
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: ifmember.exe question
>
> Thanks Neil,
>
> I actually found a reference on the Technet that ifmember is
> only good for NT (and above I guess). So if I want to support
> W95 I have to use Kixstart. Well 1 more thing to learn :))
> http://www.microsoft.com/technet/prodtechnol/winntas/tips/winn
> tmag/grlogon.m
> spx
>
> Can I execute kix script having kix.exe only in NETLOGON
> folder or I better off copying it to local drives?
>
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Braebaum, Neil
> Sent: Thursday, September 30, 2004 10:44 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: ifmember.exe question
>
> Kix will work on 95 onwards, and is very similar (ingroup
> rather than ifmember).
>
> It's ideally suited to the login script environment, too,
> because Kix caches group membership information.
>
> Doing this via Kix (ie drive mappings based on group
> membership) is only very marginally different from doing it
> in cmd / bat files.
>
> eg:-
>
> if ingroup("Group1")
> use j: \\server1\fileshare1
> endif
>
> Plus you can easily do things like:-
>
> select
> case ingroup("Group1")
> use j: \\server1\fileshare1
> case ingroup("Group2")
> use j: \\server1\fileshare2
> case 1
> ; ie default - everybody gets this
> use k: \\server2\fileshare
> endselect
>
> Neil
>
> > -----Original Message-----
> > From: thin-bounce@xxxxxxxxxxxxx
> > [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Pavlo Ignatusha
> > Sent: 30 September 2004 15:33
> > To: Org Thin (E-mail)
> > Subject: [THIN] ifmember.exe question
> >
> >
> > Hi everybody.
> >
> > I've searched the archives but did not find the answer to my
> > problem. I'm trying to consolidate my logon scripts. We are
> > still using some Windows 95 PCs along with w98, w2k and xp.
> > Eventually (once we decomission w95/98) I will migrate
> > everything to vbs but for now I need compatibility. I would
> > like to write a *.bat file and use ifmember to map drives.
> >
> > The thing is the ifmember from w2k resource kit I have is not
> > running on w95. It returns an error 120. Should I find
> > ifmember from NT resource kit? Is there ifmember that will
> > work on all OSs from W95 up? Or should I include OS detection
> > logic in the script and branch it accordingly?
***********************************************
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 Weeks Sponsor RTO Software
Do you know which applications are abusing your CPU and memory?
Would you like to learn? -- Free for a limited time!
Get the RTO Performance Analyzer to quickly learn the applications, users,
and time of day possible problems exist.
http://www.rtosoft.com/enter.asp?id=320
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
