![]() ![]() Or you can mount the Windows Server 2012 (non-Core) install image from WIM file in the installation DVD and point –Source to that. If you have another Windows Server 2012 (non-Core) you can share its c:Windows folder and point –Source to that. ![]() This must point to the c:Windows folder and that’s where the binaries are copied over from. The Add-WindowsFeature cmdlet has a –Source switch which lets you specify a path from where it can pick up the binaries. ![]() (However: if it were a non-GUI feature whose binaries were removed via the Uninstall-WindowsFeature cmdlet with the –Remove switch, then we would have had to point Add-WindowsFeature to a source if we wanted to install these features later). Had it been a non-GUI feature such as DNS or DHCP, the binaries would already be installed as part of Server 2012 Core – but not enabled – and so all the cmdlet needed to do would be to enable the feature. It happens because (obviously) the binaries for the Server Manager GUI bits are not present in the installed system and so one must point the Add-WindowsFeature cmdlet to a source where it can get these from.
0 Comments
Leave a Reply. |