On a Windows 8.1 installation, for example, the command and its output will be:Ĭ:\>Dism /Online /Get-FeatureInfo /FeatureName:NetFx3ĭeployment Image Servicing and Management toolĭisplay Name. You can see this for yourself by running the following command from an administrative command prompt in Windows 8/Server 2012 or higher. It is still an operating system component, but its installation status is “Disabled with Payload Removed”. It was a built-in operating system component in Windows 7, but in Windows 8 and higher, it is a Feature on Demand and is not included by default. NET Framework 3.5 is a prerequisite for Microsoft Office 20 as well as many other commercial and internal applications.
There are some excellent answers with links to better documentation on Super User. Run robocopy /? at a command prompt to get the usage information for your version of Windows. The documentation on TechNet is out of date for the most recent Windows versions, and it is incomplete. I will also be using Robocopy in this post. I assume familiarity with the basics of building ConfigMgr Applications here, so if you need some remedial reading, please review the Deploy and manage applications with System Center Configuration Manager topic on TechNet. Today’s topic demonstrates building a Configuration Manager Application package with multiple deployment types.
0 kommentar(er)
