Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs

none
Linked deployment share - removed drivers on master not replicate to slave

 > 

    Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We are using MDT 2012 and use Linked Deployment Share between two servers. Now I am working to setup proper drivers on master MDT server. I found out that we have newest drivers for audio for specific hardware model and remove it (NOT using force option, cannot use this option, we have about 10 hardware models, some of them use newest audio driver) because does not work properly. The older one works ok. Then I try to replicate to slave server and after successfully replication removed drivers still appear in MDT on slave server

    Has anyone know this issue?  

    Thursday, August 01, 2013 1:39 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Are you saying the drivers you remove from the "master" server are not being removed from the linked share? That's pretty much how it works. If you want to remove drivers from the linked share, you will need to perform that function manually. (Linked shares are not mirrors of the "main/master" share.)

    -Nick O.

    Thursday, August 01, 2013 3:40 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hm... I did not realize it. So is it possible to make mirrors of two deploymentshares?
    Friday, August 02, 2013 7:07 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hm... I did not realize it. So is it possible to make mirrors of two deploymentshares?

    You could use something like DFS for replication, with exclusions for CustomSettings.ini and Bootstrap.ini (or whatever you want to be different between them.) 

    http://technet.microsoft.com/en-us/library/cc771058.aspx

    -Nick O.

    Friday, August 02, 2013 4:23 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote
    One of the accepted best solutions is robocopy with the /MIR switch.

    Blog: http://scriptimus.wordpress.com

    Friday, August 02, 2013 8:25 PM
    |