-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Windows Server 2016 (1607) #211
Labels
Issue-Feature
This is a feature request for the Windows Package Manager client.
Milestone
Comments
xenadmin
added
the
Issue-Feature
This is a feature request for the Windows Package Manager client.
label
May 19, 2020
same problem here... |
We've updated the README.md with respect to Windows Server. Unfortunately, even Windows Server 2019 is not likely to be supported. |
nidietr-MSFT
added a commit
to nidietr-MSFT/winget-cli
that referenced
this issue
Dec 6, 2024
44d81dc8 Using early-return in UrlBuilder::GetQuery() 9e9b27e3 Fixing "Use of string after lifetime ends" 21bf6b98 Adding functional proxy tests 46388eaa Adding a ProxyServer implementation 7a0bfbec Exposing Path and Query via UrlBuilder b2014df3 Adding unit tests for proxy validation cdd840b0 Adding proxy input string support 216210ab Adding required permissions to enable uploading of CodeQL results (microsoft#214) fb953d6e Bump github/codeql-action from 2 to 3 (microsoft#215) 52af7124 Enabling CodeQL scanning (microsoft#211) e555d764 Bump clang-format from 18.1.5 to 19.1.1 (microsoft#210) ab8f0e72 Setup: improving build tools installation (microsoft#207) git-subtree-dir: src/SfsClient/sfs-client git-subtree-split: 44d81dc8e7614c0be8777db22431e5065aa7a6b8
nidietr-MSFT
added a commit
to nidietr-MSFT/winget-cli
that referenced
this issue
Dec 6, 2024
c639a506 Adding support for a custom proxy input (microsoft#218) 258d189b Improve logging when the content type is wrong (microsoft#221) 216210ab Adding required permissions to enable uploading of CodeQL results (microsoft#214) fb953d6e Bump github/codeql-action from 2 to 3 (microsoft#215) 52af7124 Enabling CodeQL scanning (microsoft#211) e555d764 Bump clang-format from 18.1.5 to 19.1.1 (microsoft#210) ab8f0e72 Setup: improving build tools installation (microsoft#207) git-subtree-dir: src/SfsClient/sfs-client git-subtree-split: c639a506e712dbd29ca7ca0c78d5216658e78748
nidietr-MSFT
added a commit
to nidietr-MSFT/winget-cli
that referenced
this issue
Dec 10, 2024
0e27525d Bumping version to 1.1.0 (microsoft#222) c639a506 Adding support for a custom proxy input (microsoft#218) 258d189b Improve logging when the content type is wrong (microsoft#221) 216210ab Adding required permissions to enable uploading of CodeQL results (microsoft#214) fb953d6e Bump github/codeql-action from 2 to 3 (microsoft#215) 52af7124 Enabling CodeQL scanning (microsoft#211) e555d764 Bump clang-format from 18.1.5 to 19.1.1 (microsoft#210) ab8f0e72 Setup: improving build tools installation (microsoft#207) git-subtree-dir: src/SfsClient/sfs-client git-subtree-split: 0e27525d597c730e71646fd0b15bdc8c8503f24d
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the new feature/enhancement
I work for a Citrix Service Provider. We design & host Citrix Virtual App (formerly XenApp) environments for several large companies, mainly from the transportation industry. I have to support hundreds of apps, many of them aren't even ready for Win2016, yet, and won't be ready for Win2019 in the next 1-3 years.
(Besides that Win2019 sadly has it's own flaws like Multi-User Search Roaming and per-user Font installation instead of per-machine.)
Until then I still have to create Golden Master Images with Microsoft Deployment Toolkit (MDT) automatically. It would be a great chance to ditch community projects like Evergreen (https://github.com/aaronparker/Evergreen) (no offense Aaron!) and use something official by Microsoft.
I would switch to Server 2019, but for the sake of compatibility in my industry, I just can't yet.
(Our) Reality is just not with Win2019, yet. I would switch, if I could.
Proposed technical implementation details (optional)
Support for Windows Server 2016 (1607)
The text was updated successfully, but these errors were encountered: