Summary
If the WSUS Updates folder needs to be moved it is important to use the WsusUtil.exe tool to avoid issues.Symptoms
When the Updates folder is moved without using the WsusUtil.exe tool you will experience issues in publishing 3rd party patches from CSI and similar issues when creating 3rd party deployment packages in SCCM.Cause
The issue is not documented by Microsoft but it seems like the location of the actual updates can?t be located by the WSUS server.Steps To Reproduce
1) Use File Explore to move the content of C:\Updates or the entire folder C:\Updates.
2) Publish a package from CSI (Patching/Flexera Software Package System), you will get the error message Code: -2147467259 CreateDirectory failed. Resolution
The original location is C:\Updates and the folder contains 2 other folders 'C:\Updates\UpdateService Packages' and 'C:\Updates\WsusContent'.
The WsusUtil.exe will move the content of the Updates folder which includes the 2 subfolders, so if only one of the sub folders has been moved to a different location it is important to move it back to the original location before using the WsusUtil.exe to move both subfolders to the desired location.
To move the content of C:\Updates to D:\Updates, use the following command:
wsusutil movecontent D:\Updates D:\Updates\movelog.txt
In case the intension was to move the 2 sub folders from C:\Updates to D:\Updates and all the data has already been moved/copied to the new location on D:\Updates or if you wish not to move the content, the procedure would then be to use the following command:
wsusutil movecontent D:\Updates D:\Updates\movelog.txt ?skipcopy
This command will register the new location in the WSUS configuration, but it will not try to copy the data from the original location.
Workaround
If the content of C:\Updates was moved with File Explore, then use File Explore to move it back to the original location.Additional Information
Reference: https://technet.microsoft.com/en-us/library/cc720466(v=ws.10).aspxPlease also note that wsusutil take some time to the content and configure all the permission correctly. You may have to wait for couple of hours before you can use the WSUS and publish packages.