That happened over 8 months ago and my experience so far has been positive. ![]() I didn’t like having the machine sit unused, so I decided it was time to fix the situation by installing Windows 10 on a separate partition. Last summer I realized that I was primarily using Windows on a less-powerful Dell OptiPlex 9020 and only occasionally used the Mac Pro for my personal projects-and even when I did, I used the Mac Pro mostly via VSCode’s remote SSH extension. Except… I have slowly drifted away from macOS towards Windows and this has put the machine’s future at risk. I love the hardware looks, its small form factor and its quietness, plus it is still fast enough for my needs I have no good reasons to replace it. Equipped with a 6-core Intel Xeon E5-1650 v2 3.5GHz, 32GB of RAM, dual AMD FirePro D500 graphics cards, and a 512GB SSD, it’s not a fast machine by today’s standards-but it’s still pretty decent. inf file.The Mac Pro 2013 is the most powerful machine I have at home. Copied the exported drivers from step 3 back onto the MacBook I navigated the file structure to find any missing device drivers and manually installed them by right clicking on the.Installed Windows Server back on the MacBook.After confirming devices were available in the Windows Device Manager, I exported all third-party drivers with a few commands in Powershell.Once Windows 10 was installed and booted, I installed the Apple Bootcamp drivers package above.Installed a copy of Windows 10 on the MacBook Pro ( ISO available from Microsoft) following the same steps above to create a bootable USB Windows Installer.As a last resort, I installed a copy of Windows 10 on the MacBook Pro, exported the drivers, and manually installed them after re-installing Windows Server back on the MacBook. If you’re unlucky like me, critical drivers like the Wifi/Networking may still not be found. Here is a link to the Apple Bootcamp drivers () for Windows 10 that I installed: Last Resort: Export Windows 10 Drivers ![]() The Apple Bootcamp drivers make a great place to start. Windows Audio Service – reference link – can be started in the Windows Services manager.Wireless LAN Service – reference link – can be started by running Add-WindowsFeature -Name Wireless-Networking in Powershell.Without these services enabled, the respective driver installs may fail. Prior to attempting to install any drivers, I ensured that the Wireless LAN Service and Windows Audio Service were installed/started. Enable Wifi Networking and Audio Services Unfortunately Windows Server builds are not known for their driver compatibility. Once Windows Server was installed and booted, the next step was installing device drivers, and enabling things like networking, sound, and graphics. Once the USB drive was ready, it was as simple as inserting it into the MacBook, holding the Option key at boot, selecting the USB drive, and proceeding through the Windows Server installation. The USB drive contains 2 partitions: the first containing the Windows Server Installation Media, and the second required for Mac EFI boot ![]() Make sure to set the File System to “NTFS” – this will ensure that a separate EFI boot partition is created, which is required for the USB drive to be bootable by the Mac. Once I had the ISO, I used the a free utility called Rufus to “burn” the ISO to my USB thumb-drive. ![]() I ended up downloading a free evaluation copy directly from Microsoft 2. The first step was finding a Windows Server 2019 ISO that I could use to create the USB Installation Media. Booting the MacBook from a USB Windows Installer The steps I took to accomplish this are detailed below.ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |