New
#1
Mapping network shares on boot
Hello,
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???
Thanks
BR
Kosta