Under this folder, create a folder for each operating system version that we will be adding. Mine is \\fileserver\software$\Microsoft\.NET Framework 3.5 SP1. On your application staging file share (wherever you put application source files for Configuration Manager to find), locate the folder structure for. In this case, we’ll just add to what we built before. We will have to locate all of the needed files and copy them to a file share for access by Configuration Manager. Remember, nearly every Windows version has a different payload for NetFx3. Below, I will add to that Configuration Manager application. NET 3.5 SP1 if you need to start from scratch. Please refer to my January 2016 entry on building the Configuration Manager application for. NET 3.5 on both operating systems indeed, investigation shows that the Microsoft-Windows-NetFx3-OnDemand-Package.cab files found under sources\sxs on the installation media for Windows 10 v1607 64-bit and Windows Server 2016 are identical. This is excellent news because it suggests that we may be able to use the same files for installing. Although Windows Server 2016 was released two months after its corresponding Windows 10 release, both have the same year-month version number of “1607”, and their build numbers are also identical: 14393. With the August 2016 release of Windows 10 version 1607 (“Anniversary Update”) and the initial release of Windows Server 2016 in October 2016, it is well past time to revisit last year’s entry on deploying the.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |