locked
Windows Server 2003 patching after EOL - WSUS Issue RRS feed

  • Question

  • Hi,

    I am asking WSUS question here hoping someone might have tried it before and had same experience. We are SCCM 2012 R2 SP1 shop and trying to patch Windows servers 2003 with Microsoft Connect program. I have downloaded the CAB and SUs but when I run CSAIMPORT command then I always get following error no matter what I do

     "Directory not found: %1. Please check if you specified the full path".

    I have tried following commands with no luck

    WSUSUtil CSAIMPORT "%location_of_cab_file%" "%location_of_payload_folder%" "%location_of_working_dir%"

    I have moved around cab and payload to different locations, ran command with and without working dir but no luck. I have also noticed following in SoftwareDistribution.log after it spits out above error on screen.

    "WsusTestKeys.PreformCheckAuest.cab signature is invalid

    WsusUtil.1WsusTestKeys.AreTestKeysAllowedServer Test key check: test keys are NOT allowed"

    Anyone like to shed some lights on? BTW, SCCM is synching with MS without any problem on the same server but it wouldn't do when manually imported.

    Thanks


    • Edited by IHunzai Sunday, August 16, 2015 2:24 PM
    Sunday, August 16, 2015 2:23 PM

Answers

  • ** RESOLVED **

    After working few days of troubleshooting, it turns out to be a small thing. The sub folder "WSUSContent" under WSUS was missing and by creating manually and re-running the tool (wsusutil csaimport) it worked like a charm...

    Step 1:

    Get the WSUS Content Path from following query (must run on WSUS server)

    Select LocalContentCacheLocation From vwConfiguration

    In my case, it spitted out S:\WSUS\WsusContent as location but when I checked the path, the sub-folder "WsusContent" was missing probably someone accidently deleted it.

    Step 2:

    Created new folder under S:\WSUS and renamed it to WsusContent

    Step 3:

    Run the tool again as shown in my original email and it worked this time!!

    I am posting resolution so you don't waste 3 days banging your head against the wall on troubleshooting that turned out to be an easy fix.


    Monday, August 17, 2015 9:52 PM

All replies

  •  We are SCCM 2012 R2 SP1 shop and trying to patch Windows servers 2003 with Microsoft Connect program. 

    Does this help?

    Import Microsoft Custom Support Agreement updates into WSUS


    Rolf Lidvall, Swedish Radio (Ltd)

    Monday, August 17, 2015 7:29 AM
  • I have already used the solution in that blog with no luck. I am not sure if there are any known issues importing W2K3 updates (beyond Jul 14) on WSUS running on Server 2012 R2.

    • Edited by IHunzai Monday, August 17, 2015 3:48 PM
    Monday, August 17, 2015 2:11 PM
  • ** RESOLVED **

    After working few days of troubleshooting, it turns out to be a small thing. The sub folder "WSUSContent" under WSUS was missing and by creating manually and re-running the tool (wsusutil csaimport) it worked like a charm...

    Step 1:

    Get the WSUS Content Path from following query (must run on WSUS server)

    Select LocalContentCacheLocation From vwConfiguration

    In my case, it spitted out S:\WSUS\WsusContent as location but when I checked the path, the sub-folder "WsusContent" was missing probably someone accidently deleted it.

    Step 2:

    Created new folder under S:\WSUS and renamed it to WsusContent

    Step 3:

    Run the tool again as shown in my original email and it worked this time!!

    I am posting resolution so you don't waste 3 days banging your head against the wall on troubleshooting that turned out to be an easy fix.


    Monday, August 17, 2015 9:52 PM
  • Hi,

    Glad to hear that and thanks for your feedback.

    Have a nice day.


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

    Wednesday, August 26, 2015 3:05 AM
  • Had similar issue, but WsusContent was there.

    Running the following command solved the issue for me.

    wsusUtil.exe postinstall content_dir=c:\wsus sql_instance_name=%computername%

    Found info in this blog

    https://blogs.technet.microsoft.com/reshard_sharps_blog/2013/08/18/wsus-post-deployment-configuration-fails-on-windows-server-2012/

    Tuesday, August 23, 2016 4:28 PM