Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
"File Conflict" warnings incorrectly displayed for files within a mounted folder. Is is possible to disable these incorrect warnings on WHS V1? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm developing an add-in which supports WHS V1.  The add-in will create a mounted folder.  The problem is that after some amount of time sitting idle the WHS Console will add a "file conflict" warning to the Console's Home Network Health for every file within the mounted folder.

    Note, this issue occurs outside of my add-in (I can reproduce this issue by simple creating a mounted folder on WHS V1 using the MS Disk Manager from within Computer Manager) but I need some method to disable these warnings so I can complete development of my add-in.  Yes, I want to support both WHS V1 and WHS 2011.

    My question is: does anyone know how I can disable "file conflict" warnings in a specific folder?  Or, better yet, a method to fix these incorrect warnings?

    Thanks!

    Joe

    Friday, September 30, 2011 12:03 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    The warnings occur because Drive Extender is unable to duplicate files and/or folders within a managed share. The only way to disable this is to disable Drive Extender itself.

    If by "mounted folder" you mean a file system mounted to a folder (a "volume mount point"), with that folder in a Windows Home Server share, I don't think you're ever going to be able to get that to work with V1. Drive Extender knows nothing about your mount point; at best it will treat it as any other folder in a share and duplicate it's contents into the storage pool.

    I'm not on the WHS team, I just post a lot. :)
    Friday, September 30, 2011 1:19 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Ken.  I was affraid I'd hear this was built into the DE.  I apprecaite your kind and quick response.
    Friday, September 30, 2011 6:46 PM