none
How do I install updates/patches/hotfixes to the WSUS server that is connected to a DFS share?

    Frage

  • Hey everyone,

    I've been trying to install updates for the WSUS 3.0 SP2 and I keep getting an error saying that the installer could not access the network location of the UpdateServicesPackages folder. The updates are locally stored on the server and are being run with administrator privileges. 

    One thing that I have noticed is that the location being shown in the error message has two back-slashes before the folder name. ie. \\share\WSUS\\UpdateServicesPackages.

    Any help would be greatly appreciated. :)

    Thanks in advance.

    Freitag, 26. Juli 2013 15:13

Antworten

  • Thank you Lawerence for your comments. However, I decided to uninstall WSUS and reinstall it. That fixed all the problems. The person who had been previously working on the project had configured it incorrectly and messed everything up pretty bad.

    Mittwoch, 31. Juli 2013 18:26

Alle Antworten

  • The share name you have listed is syntactically incorrect.

    It should be \\server\UpdateServicesPackages, and the 'WSUS' portion of the name should not be present at all.

    But your message is inconsistent with your thread subject line, so can we get some clarification as to what the situation really is. You state in your post that the updates are locally stored on the server, and you don't mention an NLB cluster or additional nodes, so I'm curious as to what the point of "...that is connected to a DFS share" is in the subject line? I don't see any evidence that a DFS share is involved, and it wouldn't be a supported configuration on a standalone (single-node/non-NLB) WSUS server anyway.

    Perhaps equally as significant is identifying what update(s) you are attempting to install that would even care about the \\server\UpdateServicesPackages share. That share is used to push binary content onto the server during the process of local publishing; there's absolutely no reason for any installer to need to access that share, and the appearance that something is strongly suggests that package is severely flawed. The fact that it has an invalid share name complicates it a bit more.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Freitag, 26. Juli 2013 22:23
    Moderator
  • Thank you Lawerence for your comments. However, I decided to uninstall WSUS and reinstall it. That fixed all the problems. The person who had been previously working on the project had configured it incorrectly and messed everything up pretty bad.

    Mittwoch, 31. Juli 2013 18:26
  • The person who had been previously working on the project had configured it incorrectly and messed everything up pretty bad.

    I see this a lot.

    It's why my mantra on "inherited systems" is gut-it-and-rebuild if it isn't working perfectly. :)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Mittwoch, 31. Juli 2013 21:56
    Moderator