Odeslat dotazOdeslat dotaz
 

DotazFolder Redirection in Windows XP SP3

  • 30. května 2008 9:52AcidIce Uživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaile
     
    Hi, Ever since I installed windows XP SP3 my folder redirection does not work.
    When I uninstall Windows XP SP3 the folder redirection works fine.

    I did find a temporary sollution where I copy the older "fdeploy.dll" of windows XP SP2 over the SP3 version.
    Is there another way to fix this without copying the older file over the newer file?

Všechny reakce

  • 4. června 2008 9:53Anonymous987654 Uživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaile
     

    Has anyone got a solution for this, please?

  • 4. června 2008 11:31firststknight Uživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaile
     

    Evening Anon

    Sof tware

    1a)In searching the net the thing I found was this from microsoft

    http://support.microsoft.com/kb/896427

    b)Another solution was to press the F5 refresh key, but doesnt seem to be a solution.

     

    c)What sort of firewall programs are you running? Zone-alarm? Windows Firewall? Assuming you have these set to allow connections to your other systems? <Have to ask> Turned off does it work?

    d)What about google/yahoo/microsoft/etc, etc. tool bar? uninstalled?

     

    2) Possible solution

    a)"Make sure the users' profiles' folder structure has a "Desktop", "My Documents", and any other folder that you use redirection with. The fdeploy.dll that comes with SP3 handles folder redirection differently and will error out if the profile does not have those folders"

     

      From the nice folks over in msfn.org.

     

    b) Other configuration

    Also instead of the name of the server systems. What about using the actual ip addresses? fixed some one elses problem here.

    c) To help prevent slow downs I would also consider turning off autocomplete in the internet explorer, internet options, advanced tab.

     

     d) And this fix for 30 delays doe not seem to be included in sp3. Might contact them about it if it helps your system out

     

    http://support.microsoft.com/kb/951624/  but this one is 941158.

     

     3) Other possibilitys to consider

      What are you using for your time source? One of the servers? Are your systems in in sync? Once or twice a week to your master server should be sufficient. And Where is your master server getting its time from NIST?

     

     4) You didnt mention which server you are using SBS? Server w2k3? Here is a kb for Server w2k3

    http://support.microsoft.com/kb/951851/

     

    Any way hopes this helps you out, Cheers Keith

  • 9. června 2008 11:26AcidIce Uživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaile
     

    Hi  1stknight - thank you for the response.

     

     

    numbers 1a and 1b isn't applicable and doesn't work - I have tried.

     

    1c) Windows Firewall is turned off and we have a ISA 2006 firewall running on the network. I do not think it is firewall related though, because it does work fine when I replace the "fdeploy.dll" with the older SP2 version.

     

    number 2a (Make sure the users' profiles' folder structure has a "Desktop"...) - the folder structures are as suggested above and does not work.

     

    2b)  Haven't tried this one yet - will try and see if it makes a difference.

     

    2c and d is not applicable

     

    3.) The time source is the one on the server and that updates from the internet using microsofts time server. I do not see where this may be part of the issue? The time is in sync on both the workstations and server - I checked.

     

    4) Using Windows Server 2003 R2 w. SP2 Standard Edition and all the updates to date.

  • 1. července 2008 13:12Lucifist Uživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaileUživatelské medaile
     

    There is a difference in the way Fdeploy.dll works in SP3. I am not too sure if this is a deliberate change to the functionality, however.

     

    If you have a client that is running Windows XP SP3 and their redirect is updated to a new location, you need to ensure that the source is reachable as well as the destination. If the source is not reachable for fdeploy.dll to verify that its moving content, the function will fail and the redirection path will not be updated to the new destination. This differs from SP2 in that if the source isn’t reachable, the process 'moves on' and updates the folder redirect location to the new destination.

     

    If you have replicated the content to the new area using Robocopy or similar utilities and intend to do so as a procedure, I recommend that you update your GPO and uncheck the "Move the contents of My Documents to the new location" option in the GPO (which is enabled by default on a new GPO). Once the GPO change has replicated to all sites, have the client logout and log back in and verify the results.