Windows 10: 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


:)

 

Network drives don't reconnect on Windows 10 boot up

I have two NAS drives mapped as X: and Y: drives on my Win 10 laptop. These always re-connected on boot up.

I recently replaced the hard drive with an SSD and did a fresh install of Win 10.

Now when I boot, the network drives do not reconnect. I get the pop up (bottom right corner of the screen on boot with the yellow warning triangle) with the message "Could not reconnect all network drives. Click here to check the status of your network
drives. Windows Explorer"

The drives appear mapped, but with a red cross on their icon. Attempting to access them gives the message: "Restoring network connections. An error occurred while reconnecting X: to \\192.168.0.3\Shared-files. Microsoft Windows Network: A specified logon
session does not exist. It may already have been terminated. This connection has not been restored."

At the moment, I have written a small command file to drop and re-create the network drive mappings

net use x: /d

net use x: \\192.168.0.3\Shared-files /user:***** ******

net use y: /d

net use y: \\192.168.0.2\share /user:***** ******

exit

Surely there must be a proper fix for this issue?

 

windows 10 pro ver 1511 build 10586.3 lost all local network pc's

share between homegroup not working

have to reset to read/write

computers and NAS not showing in network

but do show when map drive

confirmed able to map share and share

confirmed had to go thru all homegroup share and reset to read/write

still only 2 of 4 computers showing in network

hmmm was not getting Authenticated when mapped share????

smoke break

 

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

 

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?

 

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.