One of the major problems I’ve encountered when using an imaging process is that when I need to install additional modules sometimes they don’t install as easily as if I had just manually installed Windows from the start.<\/p>\n\n\n\n
After deploying 20+ of my new GM image laptop, I had a user report that they needed to have MapPoint 2010 installed. Since it’s near the end of 2020, and MapPoint hasn’t received an update since version 2013 came out (8 years ago at the time of this writing) – AND you cannot buy MapPoint from Microsoft any longer – I didn’t quite know what to expect.<\/p>\n\n\n\n
Apparently a specialized group of customer care employees utilize MapPoint to “pin” where technicians are supposed to be and keep track of all customer-care-related scheduling. Who knew?<\/p>\n\n\n\n
One of the pre-requisites for installation is .NET 3.5 libraries (and their subsequent backwards-compatible 2.0 and 2.5 files). The usual auto install will successfully install this Windows Add-on, but my image doesn’t include all of the necessary source files. Running it through add-remove programs\/features also fails.<\/p>\n\n\n\n
Easiest way for me was to simply double-click on the Windows 10 ISO to mount it, then run the following command in an Administrative command prompt:<\/p>\n\n\n\n
dism \/online \/enable-feature \/featurename:NetFX3 \/All \/Source:D:\\sources\\sxs \/LimitAccess<\/code><\/li>- Obviously change the Source to reflect the drive letter of your mounted ISO<\/li><\/ul>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
One of the major problems I’ve encountered when using an imaging process is that when I need to install additional modules sometimes they don’t install as easily as if I had just manually installed Windows from the start. After deploying 20+ of my new GM image laptop, I had a user report that they needed … Continue reading .NET Framework 3.5 Windows 10<\/span>