Tried adding the registry entry 'EnableLinkedConnections' (per (v=ws.10). Notepad is the stock text editor on Windows 10 and it is basic. Regardless, the script file must nevertheless be created on the system it will run on and we always recommend using Notepad to do the job. Here are the first steps, more steps may be needed, after I see the result of these logs. Disabled the 'logon script delay' policy locally (I didn't want to change organization wide GP until I knew it would work) Some of these scripts can be used as they are while others need to be modified for individual use cases. It looks like something that piggybacked on some software you installed. Verified that the logon script works as intended when the same users log into a Windows 7 machine I have also confirmed that just running the commands in the logon script directly on the machine works without issue (in fact, I placed the script on the users desktop to run as a temporary workaround when they log Verified through 'gpresult /R' that the policy containing the logon script is indeed applying Here are some steps that I have already tried/investigated: The script is very simple (identifying info redacted):Ĭopy "\\folderpath.lnk" "%userprofile%\desktop" /y I am looking for answers as to why my client's Windows 10 machine does not run it's logon script (distributed through Group Policy).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |