Install Net Framework 4.5
Gaetane Eary
You may see the following configuration dialog if you try to run an app that requires .NET Framework 3.5. Choose Install this feature to enable .NET Framework 3.5. This option requires an Internet connection.
The .NET Framework is created by Microsoft and provides an environment for running applications. There are different versions available. Many companies develop their apps to run using the .NET Framework, and these apps target a specific version. If you see this pop-up, you're trying to run an application that requires .NET Framework version 3.5, but that version is not installed on your system.
You don't need to select the child items for Windows Communication Foundation (WCF) HTTP Activation and Windows Communication Foundation (WCF) Non-HTTP Activation unless you're a developer or server administrator who requires this functionality.
If you still can't resolve your installation issue or you don't have an Internet connection, you can try installing it using your Windows installation media. For more information, see Deploy .NET Framework 3.5 by using Deployment Image Servicing and Management (DISM). If you're using Windows 7, Windows 8.1, the latest release Windows 10, or Windows 11, but you don't have the installation media, create an up-to-date installation media here: Create installation media for Windows. Additional information about Windows 11 and Windows 10 Features on Demand: Features on Demand.
If you're not relying on Windows Update as the source for installing .NET Framework 3.5, you must ensure to strictly use sources from the same corresponding Windows operating system version. Using sources from a different Windows operating system version will either install a mismatched version of .NET Framework 3.5 or cause the installation to fail, leaving the system in an unsupported and unserviceable state.
The feature still does not install even when I direct it to the SXS folder. I have program that use the 4.8 and the 3.51 together. I need to test this to get my companies programs to be certified. Anyone have any ideas. And Yes I have tried the DISM command line entry. Still no good.
.NET Framework 3 is still available, but it is not present on the sources of the installed OS. For standard Windows 10, it is download upon request by Windows. On Windows Server 2022, you need to get it from the installation iso/DVD.
2. In there, select the .NET Framework 3.5 and 4.8 (4.8 can be skipped, but recommanded) and enable all the feature and the subfeatures. (For advanced users, some subfeatures can be skipped, if truly unneccesary) It is pretty recommended to check on the features page DirectPlay, (it contains legacy Direct X, from before Windows 10, in a way, it is required by some components of .NET Framework. Also, there is Windows 10 Identity Foundation 3.5, since it is also a part of .NET Framework 3. You will get to a page with several components (I do not remember it what it says exactly, I rarely use it), there you shall a group of options labeled Application Developement. I suggest you check all things in there, since they are all related to .NET Framework. Of course, if you are an advanced user and know exactly what each one does and some are unneccesary, some of those can be skipped.
3. When you get to Confirm Installation Selection you need to check Specify Alternate Source Path. You need to acces the WS 2022 installation DVD or mounted or unzipped iso installation USB drive and go to the Sources and then Sxs in Sources. Get the adress in Windows Explorer and add it to Specify Alternate Source Path. This is the most important step.
If you have tried these steps precisely and installation fails, please be more specific about your experience. Tell us what exactly you did (i.e. where you obtained the sources and how exactly you specified the path) and what was the outcome. If there was an error message, please copy it as is, preferably via text. (But a screenshot would also do.) Thank you for providing the feedback!
I was trying to test our products to make sure that they are compatible with Windows Server 2016. And during some testing, I mistakenly thought that I can simply "downgrade" .NET framework from 4.6 to 4. So I removed .NET 4.6 from Roles and from IIS.
Now, I can't install it back using installer (because its part of OS so it is asking me to enable it from role & features). And I can't start server manager (to install role & features) because it needs .Net 4 at minimum.
My problem:On Windows Server 2016, the .NET Framework 4.6 had been inadvertently uninstalled from my system while trying to fix some issues with IIS. It was removed using the Server Manager > Remove Roles and Features.
As a result, the Power Shell, Server Manager, and Event Viewer were no longer working. So I downloaded and installed the latest offline version of the .NET Framework 4.7 from Microsoft using the installer. However, it did not fix the problem when installed by clicking on the installer.
SolutionTo fix the problem, I had to install it from the command line using the "/all" switch. I unzipped the installer to a folder and here is the command that I used to install it. In the last argument in quotes is the path to the installer, which will need to be modified based on where you have the installer unzipped:
Before installing Windows 11 Home or Pro on your Framework Laptop DIY Edition, make sure you've installed memory, storage, and WiFi. Here is a link to the Framework Laptop DIY Edition Quick Start Guide where we go over all the steps to get started.
Don't forget to install the Driver Bundle (Download here) after you complete Windows 11 installation. Because the hardware in the Framework Laptop is so new, a fresh Windows install doesn't have the needed drivers for full hardware support.
Now I would like to do a fresh install of Windows 11. The EFI USB was created following the instructions here. I do see the EFI USB when booting in the BIOS boot menu. However, when selecting the USB I get the following message: "Framework Laptop EFI USB Device Boot failed"
I am having a devil of a time installing Windows 11 on a brand new 12th gen Intel Framework (i7-1260p). I'm trying to install again and wipe everything away but when I try and boot into BIOS it just keeps looping the framework logo screen and then seemingly cycling off and on again. The first install that was successful continuously crashed or froze up (over the course of 3 working hours), especially with Zoom. I've been hunting for a solution and so far I've updated the firmware on the WD SN850 SSD and if I can get it to start again I'll install the BIOS update. This is nuts because I have an i5 12th gen running Manjaro and install and operation were super easy. Been using it for a few months and aside from a few hiccups it's been totally reliable. Windows never does anything that makes it seem like a decent OS to me. I'd never use it if it wasn't for work.
This, and the workaround, aren't working around for me. Even after copying the wifi drivers I am getting a Windows Setup screen and a Load driver dialog saying "A media driver your computer needs is missing." Any ideas?
I guess all admins face this issue where machines just stop connecting to the Jamf Cloud service.
Could be that something just broke or the user broke it just because he/she can.
This blog post seems to offer a solution
-to-reinstall-the-jamf-framework-through-the-api-with-webhooks-and-micr...
How can a machine that is not contacting Jamf anymore be instructed to re-deploy the framework?
The blog starts promising: "This blog shows how to automatically re-deploy the Jamf Framework to macOS clients who did not check in for the last X amount of days"
When reading through the blog post it is unlclear to me how the re-deploy action is pushed to the machine.
In the video that is attached to the blog post, an email is send to the potential end-user.
Anyone reads if different then me or actually got this implemented?
Think of the Jamf agent being in two parts, the binary (Jamf) and MDM profile (Apple)
Its possible for any admin enabled user and bit of tech knowledge to look up the terminal command to remove the all JAMF Framework.
The above blog assumes you have wisely ensured all your mac's were enrolled via ADE (DEP) and you have marked the MDM profile to be non-removable.
Even if a user manually removes jamf or runs the command to remove all framework; because the MDM profile is non-removable, it will still receive MDM commands by APNs, so by using the information in the blog you can send a MDM command to reinstall the Jamf framework and restore the Jamf binary functionality (it uses the same MDM command that adds the Jamf binary on enrolment)
The blog tells you how to automate this, so you will need to set up a web hook server of some description (something like JAWA or in the above example PowerAutomate) to handle the trigger mechanism its needs (normally done by the Jamf binary) for the Jamf Pro API to send a "InstallEnterpriseApplication" MDM command via APNs asking the client to get the QuickAdd package installed again to restore the Jamf binary framework to the device.
This is really for the scenario where the management framework has been broken or removed, but the device still has internet access so that APNs can still be used (as long as the device can reach Apple and your Jamf/Jamf Cloud instance it can give you access back to your device).
If they don't have any internet, then it cant fix that scenario
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
c80f0f1006