microsoft / update-client-server-sync

Provide a C# implementation (.NET Core) of the Microsoft Update Client-Server sync protocol.

Windows Update Services ClientServer Sync Protocol

Provides a sample C# implementation (.NET Core) for the Microsoft Update Client-Server protocol, server side. This server implementation can be run on-premises or as a ASP.NET Web App in the cloud.

Use this library to build solutions for deploying Microsoft updates to Windows PCs.

This library assumes update metadata and content was acquired and indexed using the Server-Server Sync library.

Reference the library in your project

In your .NET Core project, add a reference to the UpdateServices.ClientServerSync NuGet package.

Alternatively, you can compile the code yourself. Visual Studio 2017 with .Net Core development tools is required to build the solution provided at build\client-server-sync.sln

Using the library

Please refer to the API documentation for help on using the library.

Using UpdateServerStartup to start a ASP.NET web app

Creating a custom ASP.NET web app

Use the downsync utility

The downsync utility is provided as a sample for using the library. Downsync can be used to deploy updates to Windows PC.

You can build downsync in Visual Studio; it builds from the same solution as the library. Or download and unzip downsync from https://github.com/microsoft/update-client-server-sync/releases

See Using the DownSync utility

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

update-client-server-sync's Issues

What version of WUSP spec does this follow?

For example, where did deviceAttributes from GetExtendedUpdateInfo2 come from?

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Matched drivers without ComputerHWIds are better than Installed ones with ComputerHWID?

Or at least the comment on this line contradicts the result.
The code returns false, but the comment states "installed is better". I expected it to return true at this point.

update-client-server-sync/src/client-server-sync-lib/Server/ClientSync_Drivers.cs

Line 129 in 85575d2

// The installed driver matched a computer HW ID while the match result did not; the installed driver is better

Same twist on line 165

update-client-server-sync/src/client-server-sync-lib/Server/ClientSync_Drivers.cs

Line 165 in 85575d2

// The installed driver did not match a computer hardware id but the match result did match