Windows 10 Forgetting Mapped Drives after Reboot












0















We have a script that runs at logon and provides users with the relevant mapped network drives depending on certain variables. No issues with this on XP or 7.



On 8 and 10, after a reboot the mapped drives will be gone.



Even if I manually map these drives (ensuring reconnect at logon is ticked) they disappear after a reboot.



We need to look into mapping these with group policy but this might be further in the future than I would like to understand why our existing method isn't working.



Can anyone provide some insight into why this might be the case?










share|improve this question

























  • But if the script runs at logon why is this a problem? It would just remap the drives? Without information on how you do the mapping it could be kind of hard to answer, though it seems odd that even the manual mappings would disappear.

    – Seth
    Jan 27 '17 at 8:25
















0















We have a script that runs at logon and provides users with the relevant mapped network drives depending on certain variables. No issues with this on XP or 7.



On 8 and 10, after a reboot the mapped drives will be gone.



Even if I manually map these drives (ensuring reconnect at logon is ticked) they disappear after a reboot.



We need to look into mapping these with group policy but this might be further in the future than I would like to understand why our existing method isn't working.



Can anyone provide some insight into why this might be the case?










share|improve this question

























  • But if the script runs at logon why is this a problem? It would just remap the drives? Without information on how you do the mapping it could be kind of hard to answer, though it seems odd that even the manual mappings would disappear.

    – Seth
    Jan 27 '17 at 8:25














0












0








0








We have a script that runs at logon and provides users with the relevant mapped network drives depending on certain variables. No issues with this on XP or 7.



On 8 and 10, after a reboot the mapped drives will be gone.



Even if I manually map these drives (ensuring reconnect at logon is ticked) they disappear after a reboot.



We need to look into mapping these with group policy but this might be further in the future than I would like to understand why our existing method isn't working.



Can anyone provide some insight into why this might be the case?










share|improve this question
















We have a script that runs at logon and provides users with the relevant mapped network drives depending on certain variables. No issues with this on XP or 7.



On 8 and 10, after a reboot the mapped drives will be gone.



Even if I manually map these drives (ensuring reconnect at logon is ticked) they disappear after a reboot.



We need to look into mapping these with group policy but this might be further in the future than I would like to understand why our existing method isn't working.



Can anyone provide some insight into why this might be the case?







networking windows-10 windows-8






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 27 '17 at 9:52







user477799

















asked Jan 27 '17 at 8:23









RASBRASB

107515




107515













  • But if the script runs at logon why is this a problem? It would just remap the drives? Without information on how you do the mapping it could be kind of hard to answer, though it seems odd that even the manual mappings would disappear.

    – Seth
    Jan 27 '17 at 8:25



















  • But if the script runs at logon why is this a problem? It would just remap the drives? Without information on how you do the mapping it could be kind of hard to answer, though it seems odd that even the manual mappings would disappear.

    – Seth
    Jan 27 '17 at 8:25

















But if the script runs at logon why is this a problem? It would just remap the drives? Without information on how you do the mapping it could be kind of hard to answer, though it seems odd that even the manual mappings would disappear.

– Seth
Jan 27 '17 at 8:25





But if the script runs at logon why is this a problem? It would just remap the drives? Without information on how you do the mapping it could be kind of hard to answer, though it seems odd that even the manual mappings would disappear.

– Seth
Jan 27 '17 at 8:25










1 Answer
1






active

oldest

votes


















0














Firstly, if you have no network available at logon, this can cause issues with drive mappings (as the logon process does not always wait for the network). There is a group policy setting to wait for network before logon (check https://technet.microsoft.com/en-us/library/gg486839.aspx and https://support.microsoft.com/en-us/help/2421599/ )



Secondly; if the script being called is running the 'net use' command without the persist command, the mapped drive will be removed on log off:



NET USE [/PERSISTENT:{YES | NO}]



Why not use GPO to map drives as you have a greater array of options.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1172121%2fwindows-10-forgetting-mapped-drives-after-reboot%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Firstly, if you have no network available at logon, this can cause issues with drive mappings (as the logon process does not always wait for the network). There is a group policy setting to wait for network before logon (check https://technet.microsoft.com/en-us/library/gg486839.aspx and https://support.microsoft.com/en-us/help/2421599/ )



    Secondly; if the script being called is running the 'net use' command without the persist command, the mapped drive will be removed on log off:



    NET USE [/PERSISTENT:{YES | NO}]



    Why not use GPO to map drives as you have a greater array of options.






    share|improve this answer




























      0














      Firstly, if you have no network available at logon, this can cause issues with drive mappings (as the logon process does not always wait for the network). There is a group policy setting to wait for network before logon (check https://technet.microsoft.com/en-us/library/gg486839.aspx and https://support.microsoft.com/en-us/help/2421599/ )



      Secondly; if the script being called is running the 'net use' command without the persist command, the mapped drive will be removed on log off:



      NET USE [/PERSISTENT:{YES | NO}]



      Why not use GPO to map drives as you have a greater array of options.






      share|improve this answer


























        0












        0








        0







        Firstly, if you have no network available at logon, this can cause issues with drive mappings (as the logon process does not always wait for the network). There is a group policy setting to wait for network before logon (check https://technet.microsoft.com/en-us/library/gg486839.aspx and https://support.microsoft.com/en-us/help/2421599/ )



        Secondly; if the script being called is running the 'net use' command without the persist command, the mapped drive will be removed on log off:



        NET USE [/PERSISTENT:{YES | NO}]



        Why not use GPO to map drives as you have a greater array of options.






        share|improve this answer













        Firstly, if you have no network available at logon, this can cause issues with drive mappings (as the logon process does not always wait for the network). There is a group policy setting to wait for network before logon (check https://technet.microsoft.com/en-us/library/gg486839.aspx and https://support.microsoft.com/en-us/help/2421599/ )



        Secondly; if the script being called is running the 'net use' command without the persist command, the mapped drive will be removed on log off:



        NET USE [/PERSISTENT:{YES | NO}]



        Why not use GPO to map drives as you have a greater array of options.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 27 '17 at 9:33









        MikeCMikeC

        523




        523






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1172121%2fwindows-10-forgetting-mapped-drives-after-reboot%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?