Mapping network shares on boot

  1. Posts : 40
    Windows 10 Pro

    Mapping network shares on boot


    Is it only me, or is Win10 extremely buggy when it comes to startup scripts?

    In Win7 this worked flawlessly, but since I upgraded (and now installed fresh), when I give an user a logon script (and put it in the corresponding folder of course, incl. turn off the 5min delay), nothing happens. Like, never.

    If I then try doing things manually, things get even worse:
    - using net use under non-administrative CMD, sometimes is OK, and mostly the mapped drive does not show in This PC (but I can find it in CMD via "x:")
    - placing a script with net use x: \\server\share on the desktop brings similar results - sometimes OK, sometimes not

    I am simply unable to pinpoint where the problem really is. First I though it was something with non being "Administrator", but don't think so...

    It will be less problem with gpedit.msc but rather the problematic script execution.

    More-over, not even using map network drive via Windows Explorer is reliable. It may appear in This PC, or it may not (and only be accessible via CMD).

    Any ideas what's going on here???

      My Computer

  2. Posts : 8,126
    windows 10

    If you run it as admin it won't show in explorer as that's not running as admin if it's a mapping you use all the time add persistent to the car so it's mapped all the time. Running via a script can depending on how it's run can mean it runs as system not the user running via at cmd has always done that
      My Computer

  3. Posts : 40
    Windows 10 Pro
    Thread Starter

    Does the running of script as a User which is part of the Administrators group make the script run as Administrator? I don't think so.

    I'll try adding persistent:yes.

    I can assign the script to a computer policy, but that doesn't run anything, funny enough. Usually it should... especially after gpupdate and reboot.

    So what should I do really?
      My Computer

  4. Posts : 40
    Windows 10 Pro
    Thread Starter

    Well, funny enough I managed to solve this.

    From what I read, MS is going away from GPO scripts. There is an article out there about that.
    So, as suggested I tried with Scheduler, and low and behold, it is mapped, BUT: only with persistent:yes. Weird.

    And additionally, the logoff script which does couple of cleaning tasks, is running fine from GPO.
      My Computer


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 23:16.
Find Us

Windows 10 Forums