My HyperV-Host should connect to the shares provided by a virtual file server. Whenever I login to "early", the drives are not mapped, because the file-server-vm has not yet started.
The command I'm using in the logon script looks simple like this:
net use s: \\file1.mydomain.local\share1 /PERSISTENT:NO
In this scenario, the share is not available on the network, so it is not mapped. Can I "force" a network drive mapping, even if the share is not (yet) available?
I could go with a persistent mapping ofc, but the shares change over time and I dont want to reconfigure each and every server, whenever a share becomes available.
is there something like a "force" option, or is it possible to distribute persistent network-drive-mappings via GPO?