none
Features on Demand in Server 2012 - Integrate payloads into image file?

    Question

  • I recently ran into an issue with Features on Demand in Server 2012. I deployed our 2012 image to one of our developers and he wound up needing to enable some features after the deployment. It gave him an error and asked him for an install source. I did some digging and came across this article:

    http://technet.microsoft.com/en-us/library/jj127275.aspx

    It talks about building a network store for the SXS folder, but (honestly) I'd prefer to just integrate the feature files into my image. Does anyone know how to do that in MDT?
    Tuesday, September 10, 2013 10:04 PM

Answers

  • OK, when adding the roles afterwards, simply point to where the SxS folder is. You can have the task sequence copy it to each computer, so it's always available locally. When adding features via server manager, dism or PowerShell, there is an option to specify an alternate location if the machine doesn't have Internet Access.

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    • Marked as answer by ZeusABJ Tuesday, September 17, 2013 2:19 AM
    Thursday, September 12, 2013 6:15 PM
  • Yes its possible with a gpo: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair
    • Marked as answer by ZeusABJ Tuesday, September 17, 2013 2:19 AM
    Saturday, September 14, 2013 9:25 AM

All replies

  • yes, when building the reference image, add full source files, add the install roles and feature action to state restore phase in the TS (somewhere before the Windows Update action), and then select the features you need.

    MDT knows how to deal with the SxS folder issues.

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Wednesday, September 11, 2013 5:57 AM
  • yes, when building the reference image, add full source files, add the install roles and feature action to state restore phase in the TS (somewhere before the Windows Update action), and then select the features you need.

    MDT knows how to deal with the SxS folder issues.

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Hey Johan, thanks for responding. No I understand that part and I have it working. My question is how to stage the SxS folder so that my developers can install roles and features AFTER an image has been deployed. I've already deployed some Windows 2012 images and when they try to install .NET Framework features it prompts them for source media. I want to "fix" my image so all the roles and features payloads are already in the OS AFTER a deployment. Is that possible?

    BTW - I sat with you and Kent in a couple of sessions at TechEd 2013. Nice to hear from you again. Also really enjoyed your SCCM Pre-Con talk. learned a lot.

    Thursday, September 12, 2013 5:53 PM
  • OK, when adding the roles afterwards, simply point to where the SxS folder is. You can have the task sequence copy it to each computer, so it's always available locally. When adding features via server manager, dism or PowerShell, there is an option to specify an alternate location if the machine doesn't have Internet Access.

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    • Marked as answer by ZeusABJ Tuesday, September 17, 2013 2:19 AM
    Thursday, September 12, 2013 6:15 PM
  • OK, when adding the roles afterwards, simply point to where the SxS folder is. You can have the task sequence copy it to each computer, so it's always available locally. When adding features via server manager, dism or PowerShell, there is an option to specify an alternate location if the machine doesn't have Internet Access.

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Okay I think I've got you here, let me just verify. So I should just copy that SxS folder locally (maybe set up an XCOPY script to drop it on the root of OSDisk during my task sequence) and then instruct my devs to just point to it as needed in DISM. Okay so (just to verify) *all* I need is the SxS folder then? I had copied the entire set of 2012 Server source files to one 2012 Server for a dev (I think it was around 4GB) at one point. SxS is much smaller, if thats all I need then that's fantastic. If thats the case I'll just drop that in my image file when I build it out. Can you just confirm that for me?
    Thursday, September 12, 2013 11:58 PM
  • Yes the SxS folder is all you need to enable any feature.
    Friday, September 13, 2013 7:35 AM
  • Yes the SxS folder is all you need to enable any feature.

    Okay thats great, last question. Is there any way I can configure Server 2012 to always look for the SxS folder at the following path:

    C:\SXS

    Maybe a setting somewhere in the registry? Anyone know if thats possible?

    Friday, September 13, 2013 11:07 PM
  • Yes its possible with a gpo: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair
    • Marked as answer by ZeusABJ Tuesday, September 17, 2013 2:19 AM
    Saturday, September 14, 2013 9:25 AM
  • Thanks guys.
    Tuesday, September 17, 2013 2:19 AM