|
|
|||||||
Hi, I’m using Kix vey long with different OS Versions. Now it’s the first time to use it with Win10 The Win10 clients are in a Domain and I call the Script with the logonscript option of the AD User I have written a simple Kix script to map some drives and Printers. When I login after the computer was started /restarted it takes several minutes to run the script. When I logout and login again the script runs in seconds (like I would expect) I activated the GPO “wait for the network” and “Run scripts synchronously” I have done this with Win 7 in the same way for years in many different environments without any big Problems. DNS is working fine Is there anybody who knows something about this problem? Here is the script I’m using at the moment USE V: /delete USE T: /delete USE S: /delete USE U: /delete IF INGROUP("grp_1") USE V: "\\domain.local\Data\Share1" Use T: "\\domain.local\Data\Share2" ENDIF IF INGROUP("grp_2") USE S: "\\domain.local\Data\Share3" Use U: "\\domain.local\Data\Share4" ENDIF IF INSTR(@WKSTA,"room1-") ADDPRINTERCONNECTION ("\\DC1\HP-room1") SETDEFAULTPRINTER("\\DC1\HP-room1") ENDIF IF INSTR(@WKSTA,"room2-") ADDPRINTERCONNECTION ("\\DC1\Lexmark-room2") SETDEFAULTPRINTER("\\DC1\Lexmark-room2") ENDIF |
||||||||
|
|
|||||||
it's a windows 10 design issue. this is just one of the reasons to stay away from it. |
||||||||
|
|
|||||||
btw, after you did that GPO change, did you make sure it was in effect? sometimes it takes couple reboots or days of waiting before your GPOs actually are functioning. another nice design feature. |
||||||||
|
|
|||||||
I'm absolutely sure that the policies are applied to the PCs. I have seen the behavior of the policy while logging in and tested it with and without this policy. I don't like Win 10 but in future there won't be a choice. |
||||||||
|
|
|||||||
For drive mappings use GPP (Group Policy Preferences). You can select the option "Run in user context" so you don't run into the UAC crap Kix runs into. |