WIM you are referencing as the source. If you have patched your OS and you want to install a role or feature, it'll fail. WIM so you can match product versions. One caveat to the above is that this method still doesn't work for me. WIM as an install source. You'll need to decompress the MSU to get the. Again, this didn't work for me, but it may for you. Once I have the problem resolution from MS I'll update this thread for everyone. Were you able to resolve this? I'm having a similar issue trying to download the IIS feature using Ansible.
I had the same issue installing. NEt also, but if i try to install the Web Management Console it will find the feature package. I haven't removed any of the source files for the features.
It is a fresh install of server , apart from powershell there is nothing else on the server. Anyway, not to detract from the original topic i just wanted to know if you were able to find a resolution?
Same problems for me. I did not install any windows updates yet! It also fails with active Internet connection and not using -source parameter. So step 4. I was getting the typical "Add-Windows Feature : The request to add or remove features on the specified server failed. Searching led me to here:.
Which did not work, even when specifying the index. I noticed Dale's comment just as I was about to give up for now, and lo and behold I have success! I had copied the extracted source content to a local directory, and used essentially This time I got a success message with a prompt to restart after install. Maybe that will help others, even if it's not exactly the same issue. Sorry, Luis, no update. I gave up on it after my last post.
It's just not a feasible approach to remove the payloads and expect to be able to have all the roles and features available after. Some will work, but a lot don't and if you've patched the OS then it's a good bet that you won't be able to add much after. It's a real bummer because I would like to lessen to security footprint of the OS as much as possible. This is not something that is really supported, though. I know in your last post you said you gave up on this.
I just want to throw out a "Thank You" for posting this. I've been banging my head against the wall all morning trying to get this to work. After much research I came across this post which simply states that MS has some serious bugs with creating a legitimate SxS store. Considering it's been a year since you last worked with MS; I was hoping they would have resolved the issues by now. I can safely say that is not the case. I'm not sure why they try to sell this feature to experienced admins when it simply doesn't work for a great majority of the RFs including the most important ones.
Quick question regarding your attempts; are you using Server or ? Just curious if this is still present in I'm using Server fully up-to-date. I haven't played with Server and it's a good question whether these issues persist.
It appears they do as I found this thread by googling the error I am receiving when trying to install IIS on Server This looks like a mess and apparently its not fixed in In one of the call I had with MS, the tech had said that if we use a Features on Demand disk at the same rev level as the OS where the feature payload has been removed, we could reference that as the source to install the features. It didn't work for me on I was having same issue. Office Office Exchange Server.
Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. I did a CheckSUR to make sure that the component store is not corrupt.
Improve this question. MichelZ MichelZ Add a comment. Active Oldest Votes. Improve this answer. The important part here is the sxs subdirectory rather than just e.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Who is building clouds for the independent developer? Microsoft has confirmed it to be a problem in the packaging of volume licensed media for Windows Server R2.
This behavior isn't by design and has been corrected in the Volume Licensing build that was released on December 11, Use the new media for any Windows Server R2 installations. See the Resolution section to resolve this problem on servers on which you can't install features. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.
0コメント