locked
WSUS Metadata/content mismatch bw Upstream and replica server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Find WSUS Replica server's metadata is not equal to Upstream Server's metadata and Content folder.

    As we have 2 WSUS Upstream servers in our environment (Server names: USS-WSUS-01 and USS-WSUS-02)

    As we migrated replica server DSS-WSUS-10 to USS-WSUS-01 from USS-WSUS-02. After Migration metadata sync process was completed successfully.

    But we see the some Discrepancies bw replica server (DSS-WSUS-10) and Upstream WSUS Server (USS-WSUS-01) , the patch counts (Unapproved Updates and Declined Updates) are not equals to Upstream Server. Only approved updates counts is matching with USS.

    Anyone please suggest how to resolve this issue. 



    • Edited by Ramesh-N Monday, May 22, 2017 8:30 AM
    Monday, May 22, 2017 8:21 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Run my script on all servers - use -FirstRun and then in your case, after that successfully completes, run -QuarterlyRun, and then run -InstallTask

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.

    Adam Marshall, MCSE: Security
    http://www.adamj.org


    • Edited by AJTek.caMVP Thursday, May 25, 2017 12:16 PM
    • Marked as answer by Ramesh-N Monday, June 12, 2017 7:41 AM
    Thursday, May 25, 2017 12:16 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
    Please check the count of Unapproved Updates and Declined Updates on the downstream server is more or less than upstream server.
    If the count is more than upstream server, in my opinion, it may be that there is some Unapproved Updates and Declined Updates which are synced from old replica server USS-WSUS-02 before.
    Best regards, 
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. 

    • Proposed as answer by Wendy Jiang Monday, May 29, 2017 11:51 AM
    Tuesday, May 23, 2017 5:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Wendy,

    Yes that's correct, both the values are more than the current Upstream Server and its taken from old USS Server.

    Do you know how to correct/clear that entries, which are synced from old USS. Now the Replica DSS's metadata/content should be matched with our New USS.

     Thanks&Regards,

     Ramesh

    Tuesday, May 23, 2017 6:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Ramesh,
    As far as I know, there are no built-in methods to do that, but in my experience, you could have a try reinstalling WSUS role and re-syncing with the new upstream server.
    Best regards, 
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. 

    • Proposed as answer by Wendy Jiang Monday, May 29, 2017 11:51 AM
    Thursday, May 25, 2017 9:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Run my script on all servers - use -FirstRun and then in your case, after that successfully completes, run -QuarterlyRun, and then run -InstallTask

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.

    Adam Marshall, MCSE: Security
    http://www.adamj.org


    • Edited by AJTek.caMVP Thursday, May 25, 2017 12:16 PM
    • Marked as answer by Ramesh-N Monday, June 12, 2017 7:41 AM
    Thursday, May 25, 2017 12:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Was your issue resolved? If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions. If no, please reply and tell us the current situation in order to provide further help.
    Best Regards,

    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. 

    Monday, May 29, 2017 11:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Run my script on all servers - use -FirstRun and then in your case, after that successfully completes, run -QuarterlyRun, and then run -InstallTask

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.

    Adam Marshall, MCSE: Security
    http://www.adamj.org


    Hello Adamj,

    im getting below error message while im clicking on the Lin: http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    Error Message:

    Oops! A Server Error Has Occurred.

    Sorry! We've encountered a server application error in the Spiceworks Community.

    If you'd like, contact us at support@spiceworks.com and tell us about what you were doing when this error occurred so we can take a look.

    Once again, sorry about the problem, and thank you for your patience.

    For more information please visit Spiceworks Support.

    Monday, June 5, 2017 12:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Was your issue resolved? If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions. If no, please reply and tell us the current situation in order to provide further help.
    Best Regards,

    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. 

    Hello Wendy, I will do that once it getting resolved, Thanks.

    Monday, June 5, 2017 12:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have alerted Spiceworks support about this issue. It seems to be for every script on the scripts pages.

    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Monday, June 5, 2017 12:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It's back now.

    Message I got from SW Support was:

    Hi!

    Thanks for reporting the broken links. Overnight, it looks like all of our how-tos and scripts started erroring. We've restarted our servers, and they seem to be back up and working again, but we'll continuing monitoring and investigating today to figure out what went wrong and how to prevent it from happening again.

    If you see any more issues, please let us know!

    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Monday, June 5, 2017 3:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
    Since there is no feedback about this case for days, we would think that the problem might be fixed by the replies as above, if that is the case, please help to mark the replies as answers, it will help others find the answers easily who have the similar question.
    Best Regards,
    Wendy Jiang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. 

    Friday, June 9, 2017 12:53 PM