Skip to content
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

netfx3 is not supported on server 2016 #89

Open
axelrtgs opened this issue Jun 8, 2018 · 3 comments
Open

netfx3 is not supported on server 2016 #89

axelrtgs opened this issue Jun 8, 2018 · 3 comments

Comments

@axelrtgs
Copy link

axelrtgs commented Jun 8, 2018

netfx3 is not supported on server 2016 causing the chef run to fail when using the defaults since 10 is listed in the versions supported for the feature

@Annih
Copy link
Contributor

Annih commented Jun 9, 2018

Hello @axelrtgs thanks for your report, could you please precise some points, to let me help you resolve your error.

  1. What is the error you get?
  2. What do you mean by "the defaults"? the recipe for ms_dotnet3 is not included by default
  3. Which version of this cookbook and Windows Server 2016 you have?

FYI netfx3 is supported on Windows Server 2016, you just need to provide the source URL/path.

@Annih
Copy link
Contributor

Annih commented Oct 7, 2018

@axelrtgs could you provide more info, otherwise I'll close this issue

@axelrtgs
Copy link
Author

axelrtgs commented Oct 9, 2018

I am using the latest version of the cookbook and server 2016 standard
By defaults i mean including the recipe without any modification or using the resources with special parameters.
For more information on the issue with netfx3 and server 2016 see the following link which describes much more in detail than i could ever summarize here: http://woshub.com/how-to-install-net-framework-3-5-on-windows-server-2016/

i guess saying unsupported is a bit of a stretch its more of its not included by default so cannot be activated by just installing the feature, you need to provide a source for it to work on 2016 and if the recipe is run on 2016 it throws an error.

For those of us in mixed environments it makes it hard to start wrapping every single little thing in if/else cases so i think we should find a way to include a check (or link to source) within the cookbook so it will either install and work or allow us to specify the source location and if not specified give a friendly warning instead of crashing the run (similar to the unsupported or superseded warnings)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants