|
|
|||||||
I have created a logical drive known as "M:\Marketing". On the drive I have created two shares known as: NW_Evnt_Dept and NW_Mktg_Dept I am using kixscripsts to map to the drives from W9x client machines. The two shares exist for two different departments. The first share I created was NW_Mktg_Dept, and I mapped the drive as shown below: If INGROUP (nw2_mktg_dept) Mapdrive ("M:","\\nw-data-store1\nw_mktg_dept) endif I then created the second share and mapped the drive as follows: If INGROUP (nw2_evnt_dept) Mapdrive ("H:","\\nw-data-store1\nw_evnt_dept) endif When I assign users to this group the mapping does not work? Any ideas why? |
||||||||
|
|
|||||||
Is the mapping failing or the InGroup() not firing?
|
||||||||
|
|
|||||||
Please excuse my ignorance. Where abouts, when using W9x clients, should I place the -d %0\..\kix32 %0\..\livscript.kix I have tried after kix32 and after livscript.kix but the script will not run in debug mode? |
||||||||
|
|
|||||||
it looks so obvious: Quote: where is that missing quote? |
||||||||
|
|
|||||||
S orry that was a typing error the quotes are at the end. Problem still persists? |
||||||||
|
|
|||||||
Eh? What "-d"? Use /f (or -f) to flush the group membership cache. The debug message does not need debug mode - you just want to insert a temporary message so that you can determine whether the InGroup() is processing or not. If your MapDrive UDF outputs messages then this will suffice. |
||||||||
|
|
|||||||
Hi Rich, Were do you place the /f to flush the membership? I have monitored the script and it does not even attempt to map the drive? |
||||||||
|
|
|||||||
Code: %0\..\kix32 /f %0\..\livscript.kix Should do it. |
||||||||
|
|
|||||||
Thanks for that Rich. I tried it but still no success? Can kix map to multiple shares on the one logical drive? It looks as though everything is right on the server with regards to permissions, group namings, etc? |
||||||||
|
|
|||||||
You need to determine what the error is first. If the InGroup() is not working, then the issue is not with the mapping, but rather with the group membership check, and you will need to fix that first. Just run a simple script with the failing user: Code: If InGroup("....whatever group") Once the group check is working you can worry about the drive mapping. Check that your old and new groups are the same type i.e. Local vs Global. |
||||||||
|
|
|||||||
Quote: As I read it, it should be: %0\..\kix32 %0\..\livscript.kix /f But I'm sure either way works just fine. Thanks for making KiXtart so easy Ruud. |
||||||||
|
|
|||||||
What Doc references is talked about in a Microsoft Knowledgebase article too - A Logon Script Does Not Work If %0 or %0\..\ Calls Multiple Commands Kent |