Since then, it is suggested that you can use the logon script to help you resolve the issue. And the problem still exists on windows 10 1709. Thanks for the link, for this bat, is it better to first disconnect the drive then re-connect it on start? This case, a GPO can solve the issue? Is there anyway to test this locally without using the GPO? Like Local Security Policy? Mapping on that form works, but after restart the problem persists.Ĥ. On other mapped drives their own windows domain account has permission, so that doesn't happen.ģ. Not every machine because we haven't tested on all of them, but every that does use this mapped drive happens this. Double clicking to reactivate it doesn't works, to reach it out again user must type the address on Windows Explorer then authenticate. When user starts the machine, that specific mapped drive (and only it) appears with a X. If you have feedback for TechNet Subscriber Support, vivian_zhou,ġ. If you have feedback for TechNet Subscriber Support, you double click the drive with red x, will it be auto mapped again? Please remember to mark the replies as answers if they help. Note: this is a 3rd party link, we don't have any warranties on this website. If nothing helps, there is a work around for you:Ĭreate a logon script to help you map the drive, below is the reference: Templates\System\Logon \ Always wait for the network at computer startup and logon So it is suggested that you can update your network card driver and enable the policy This is expected when the machine doesn't have connectivity to the shares during logon. Open cmd as administrator and type net use What if use the command line to map the drive? If you double click the drive with red x, will it be auto mapped again?ĭid the problem happen on every domain users, on every domain joined machine?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |