MichelZ's questions

I am trying to install the Media Foundation feature onto a Windows 2012 R2 box in preparation for it to be used as an RDS Session Host.

However, all attempts to install fail with:
Installation of one or more roles, role services, or features failed. The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077. Error: 0x800f081f

Please find the dism and cbs logs -->here<--

The Windows box is fully up2date as of today with all Windows Updates. I have specified the file location as WIM:F:\sources\install.wim:4, where F:\ is the mounted Windows DVD (tried RTM + Update1 DVD's). There is a WSUS on the Network, and the Policy is set to:

Never attempt to download payload from Windows Update: Disabled

Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS): Enabled

I have installed other features successfully using this method before.

I also tried with and without specifying a source with the same result.

I did a CheckSUR to make sure that the component store is not corrupt.

The Windows Installation is one which had the local file store removed (Features on Demand) to keep the footprint small. (i.e. Get-WindowsFeature | Where-Object {$_.Installed –eq $False} | Uninstall-WindowsFeature -Remove)

Unfortunately, I don't really know what to do from the errors in the log file.

I can see instances of:

2014-07-23 16:28:22, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

2014-07-23 16:28:22, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]

I can see that it downloads some packages but has some troubles there:

2014-07-23 16:27:03, Info CBS DWLD: Bundled index = 1

2014-07-23 16:27:03, Info CBS DWLD: Windows update server URL: http://download.windowsupdate.com/d/msdownload/update/software/updt/2014/05/windows8.1-kb2965500-x64_df916a7e348b2d53dbdc8e7f1828d0d1f7b5c3ca.cab

2014-07-23 16:27:03, Info CBS DWLD:Content is Full-Cab package.

2014-07-23 16:27:03, Info CBS
Failed to copy to path on bundle: 1 [HRESULT = 0x80246013 - Unknown Error]

2014-07-23 16:27:03, Info CBS WU: WSUS service is the default, URL: (null), Name: Windows Server Update Service

as well as:

2014-07-23 16:28:24, Info CBS Exec: Processing complete. Session: 30385793_3994419723, Package: Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

2014-07-23 16:28:24, Error CBS Failed to perform operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

2014-07-23 16:28:24, Info
CBS Session: 30385793_3994419723 finalized. Download error: 0x800f094b [CBS_E_SOURCE_MISSING_FROM_WUSUS_BYPASS_EXPRESS], Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

Windows Server 2003 is a very good operating system from Microsoft, and we're relying on it on a daily basis.
I have heard that I should replace it by something "newer" and more "modern".

Why should I do this?
What are the implications if I don't upgrade?

Got some servers with RAID Controllers and SSD.

Raid Controller: LSI MegaRaid 9271-4i
SSD: Intel 520

The MegaRaid controllers have the ability to update drive firmware using MegaCLI.

Intel for example only offers a Firmware Update Tool, and not direct .bin Firmware files.

Is there a possibility to update these drives without pulling them out and attaching them to a normal SATA controller and using the FUT? Any other ways you can think of for doing this? Or do people using RAID Controllers + SSD not update their SSD Firmware's at all?

I've updated some of my test hosts to Update 1 (KB2919355).

Now, they cannot scan against WSUS anymore (0x80072F8F)

OK, easy you say! Microsoft patched that issue, and warned about it.

Now to the harder part. My WSUS Server is running on 2012 R2, and has TLS 1.2 enabled - I should not be affected.

Even weirder, I've installed the corrected update which is supposed to have fixed the issue. To be safe, I tried installing the Update KB2959977 mentioned in above KB Article. Result: This update is already installed.

So, I'm at a loss here :) Does anyone else have the same problem? Any suggestions? Did Microsoft screw this really up?

I'm trying to modify the web.config using PowerShell.

So far, I'm able to replace the Connection String using:

Set-WebConfigurationProperty -pspath "IIS:\Sites\$Name\WS" -filter "connectionStrings/add[@name='Product.Core.WebServices.Properties.Settings.DirectoryConnectionString']" -name "connectionString" -value "Server=SERVERNAME\INSTANCE1;Database=ProductDirectory.$Name;Trusted_Connection=True;"

this works OK.

Now, I want to change something in the applicationSettings part of the web.config. The Part looks like:

<applicationSettings>
    <Product.Core.WebServices.Properties.Settings>
      <setting name="LogLevel" serializeAs="String">
        <value>Info</value>
      </setting>
      <setting name="LogDirectory" serializeAs="String">
        <value>D:\temp</value>
      </setting>
      <setting name="LogSpecialTroubleshoot" serializeAs="String">
        <value>False</value>
      </setting>
      <setting name="LogSqlQueries" serializeAs="String">
        <value>False</value>
      </setting>
      <setting name="LogPerformance" serializeAs="String">
        <value>False</value>
      </setting>
      <setting name="LogXmlInput" serializeAs="String">
        <value>False</value>
      </setting>
      <setting name="LogXmlInputSeperate" serializeAs="String">
        <value>False</value>
      </setting>
      <setting name="EnableCatchAllLogging" serializeAs="String">
        <value>True</value>
      </setting>
      <setting name="DirectoryDatabaseName" serializeAs="String">
        <value>ProductDirectory</value>
      </setting>
    </Product.Core.WebServices.Properties.Settings>   
</applicationSettings>

I would like to change the "DirectoryDatabaseName" node.

Using:

Set-WebConfigurationProperty -pspath "IIS:\Sites\$Name\WS" -filter "applicationSettings" -name "test" -value "ProductDirectory.$Name"

I can change the "root" node (applicationSettings) and add an attribute with name "test" to it. However, if I'm trying to go "deeper" into the structure, I get the following Error:

WARNING: Target configuration object 'applicationSettings/Product.Core.WebServices.Properties.Settings/setting[@name='DirectoryDatabaseName'] is not found a
t path 'MACHINE/WEBROOT/APPHOST/TestM/WS'.

I'm using the following PS for that:

Set-WebConfigurationProperty -pspath "IIS:\Sites\$Name\WS" -filter "applicationSettings/Product.Core.WebServices.Properties.Settings/setting[@name='DirectoryDatabaseName']" -name "test" -value "ProductDirectory.$Name"

Not even this works (same error):

Set-WebConfigurationProperty -pspath "IIS:\Sites\$Name\WS" -filter "applicationSettings/Product.Core.WebServices.Properties.Settings" -name "test" -value "ProductDirectory.$Name"

So somehow it stops working "one level below" applicationSettings

Also, how would the syntax be to change the text between <value> and </value>?