Parallels For Mac Configuration
Home Forums > Parallels Desktop for Mac > Installation and Configuration. Share your experience about installing, configuring and fine-tuning Parallels Desktop. Parallels Mac Management fully integrates with the Configuration Manager console, so IT administrators can manage Mac and Windows computers using the same familiar graphical user interface. General Requirements for Parallels MAC management with SCCM 2012 R2. The Parallels Configuration Manager Proxy service account must have a registered. For administrations that are doing some basic Mac Management straight out of the System Center Configuration Manager built-in functionality, the graphic below provides a great comparison what you get out of the box from Microsoft, and what the Parallels Mac Management adds to base functionality. Click on the Parallels icon on Mac menu bar and choose Configure under your virtual machine section. Click on the cogwheel on top right corner of the virtual machine's window. When your virtual machine is running in Coherence mode.
In Part 1 of the series on Parallels Mac Management for SCCM, I talked about installing the Parallels Console Extensions into your environment. In Part 2, I will install our first ‘role’ the Parallels Configuration Manager Proxy.
Parallels Mac Management for SCCM requires the installation of the proxy on a server that resides in the defined ConfigMgr boundaries. It is recommended that the SMS Provider is installed on the server that hosts the Parallels Configuration Manager Proxy. If you need assistance on installing the SMS Provider on your remote device then take a look at my blog post on how to do this. The SMS Provider is not installed then you can point the proxy to a remote SMS Provider during configuration.
A proxy should be deployed to a Primary Site, if you have Secondary Sites in your environment then you should also deploy a proxy to each of those to reduced traffic over the link and to simplify Mac Client enrollment.
The Parallels Configuration Manager Proxy is a Windows Service application that acts as a proxy been the Mac client and ConfigMgr and can be installed on devices running Windows 2008R2 and later.
Pre-Requisites
The following pre-requisites need to be installed on the server that will host the proxy:
- .Net Framework 4
- .Net Framework 3.5
- Visual C++ 2010 Redist x86 available from https://www.microsoft.com/en-gb/download/details.aspx?id=5555
- Server patched with the latest updates. For Server 2012 – if not patched then install the following:
Permissions Needed to run the Installation
The account that will install the Parallels Configuration Manager Proxy requires the following rights:
- Local Administrator on the server
- DCOM Remote Activation permission
- Full Admin rights in ConfigMgr
- Permissions in AD
- Open ADSI Edit by clicking Start > Administrative Tools > ADSI Edit.
- Verify that the following container exists: DC= / DC= / CN=System / CN=ParallelsServices.
- If the container above doesn’t exist, grant the user the Create All Child Objects and Read permissions on the CN=System container. When granting these permissions to the user, apply it to This object and all descendant objects.
- If the container exists, do the following:
- Make sure the user have Read, Write, and Create All Child Objects permissions on it.
- Make sure the user has the Full Control permission on the CN=ParallelsServices / PmaConfigMgrProxy- container.
- Verify that the DC= / DC= / CN= Program Data / CN=Parallels container exists
- If the container above doesn’t exist, grant the user the Create All Child Objects and Read permissions on the CN=Program Data container. When granting these permissions to the user, apply it to This object and all descendant objects.
- If the CN=Parallels container exists, continue with the following steps
- Verify that the CN=Parallels / CN=Parallels Management Suite container exists. If it doesn’t, grant the user the Create All Child Objects and Read permissions on CN=Parallels container
- If the CN=Parallels / CN=Parallels Management Suite container exists, make sure that the user has Read, Write, and Create All Child Objects permissions on it.
- Permissions to read/write SPN
- SQL Server dbcreator role for the account on the ConfigMgr site database – a DB called PMM_ will be created.
- Administrative Rights in Authorization Manager – if Parallels has been previously installed and the Authorization Store exists, then the user configuring the Parallels Proxy must be assigned to the Administrator role in Authorization Manager
Installation
Note that for the series I am going to install all the Parallels roles on a separate site system server called Parallels.
Add the .Net Framework 3.5 and 4.5 features to your server and install the required Windows Updates.
Download the Visual C++ 2010 Redist x86 and run the install.
Accept the licence agreement and click Install.
Click Finish when complete.
Run the ‘Parallels Mac Management for SCCM.exe’ installation file and when the wizard appears deselect ‘MDM Server’ and choose ‘Configuration Manager Proxy’. Click Next.
Click Install to begin the installation.
Leave the checkbox for ‘Configure Parallels’ ticked and click Finish when complete.
At this stage the configuration of the proxy takes place. If you have installed a local SMS Provider then choose Local Server. I haven’t installed a provider and therefore I am pointing back the SMS Provider on my site server.
Next, an account needs to be assigned to run the Proxy as a Windows Service. The account must be:
- A domain user
- A local administrator
- Have the DCOM Remote Activation permission.
- Be a full ConfigMgr administrator
- If the CN=System / CN=ParallelsServices / CN=PmaConfigMgrProxy- container exists in Active Directory, the user must have Read, Write, and Create All Child Objects permissions on it
- If the container above doesn’t exist, grant the user the Create All Child Objects and Read permissions on the CN=System container. When granting these permissions to the user, apply it to This object and all descendant objects.
Specify an account and click Next.
Parallels For Mac Free
Address any pre-requisite issues that are encountered. Here for example I had to edit the permissions to the inboxesddm.box on the site server.
Once pre-requisites are addressed the check can be Rerun with ‘Rerun’ button and the Next option should become available.
As stated in Part 1 of the series, Parallels can run without the PKI requirements of native ConfigMgr Mac support, although the option to use HTTPS is there. I’ve selected HTTP and then clicked Next.
At this point it is possible to configure RBAC for Parallels. I have left this at default. The configuration wizard can be run again at anytime if changes are needed here. Click Next.
Now, the default ports required for communication with the ConfigMgr console and Mac clients can be altered. Click Next.
Decide whether to enroll into the Parallels CEIP program and click Next.
Click Finish on the summary screen.
Once complete you’ll be notified that the proxy settings have been updated and that you can run the wizard again at any time via the Start Menu.
If you take a look at your ConfigMgr DB you’ll notice that the PMM_ DB has been created.
In your System container in AD the ParallelsServices container…
,and in the ProgramData container, the Parallels container have been created.
That’s all for now. In Part 3 I’ll be delving deeper into the world of Parallels Mac Management for SCCM by installing the NetBoot Server & OS X Software Update Service roles.
Editor’s Note: This article was originally published at Computerworld.com.
Both Parallels Desktop and VMware Fusion deliver on the core goal of allowing Macintosh users to run Windows applications without needing to reboot their computers.
The biggest difference between them right now is that Parallels’ product is finished while VMware’s Fusion is still in beta testing. In fact, Parallels recently announced the availability of the third beta version of the next release of its software, which includes support for upgrading a virtual Windows XP system to Windows Vista, among other features.
The fact that Fusion is still in beta is rather evident. Several configuration dialogs include the sentence, “This device will be editable in a future release,” and there are some minor stability problems.
Performance is another major difference, and it is linked to the fact that Fusion is still in beta. Although the time it takes to install or boot Windows or to run most applications is similar between both Parallels and Fusion, some actions that involve redrawing the screen are slower in Fusion, sometimes resulting in a sluggish feel by comparison.
Running benchmark tests within similarly configured virtual machines under each application reveals dramatic differences in some processor and graphics functions. (Parallels’ scores for graphics performance are almost double those of Fusion.) The most likely cause for these differences is explained in a Fusion alert dialog that informs users that it is running in a debug mode that reduces performance and that can’t be disabled in the current release.
The finished version of Fusion will tell a fuller tale on the performance front.
Setup
Both Parallels Desktop and VMware Fusion are easy to install. Both offer setup assistants that guide users through creating a virtual machine and offer configuration suggestions based on the operating system being installed and the hardware specifications of the Mac.
Fusion takes advantage of the dual-core processors used in almost all Intel Macs by allowing you designate whether the virtual machine will be able to use one or both cores. This is a nice feature because you can opt to retain the processing power of one core exclusively for Mac OS X and Mac applications, or you can throw all the processing power to the virtual machine.
Parallels makes setup much easier than Fusion with its “Express Windows OS Installation Mode” that performs the entire install process of either Windows XP or Vista for you. All you need to do is enter your name and Windows activation key. This is both extremely user-friendly and a great-time saving convenience.
Both products offer a set of tools and specialized drivers for Windows to enhance its performance in a virtual environment. These tools offer things such as a shared folder that can be accessed from Windows and Mac OS X, the ability to respond to the cursor appropriately as you move into or out of the window containing the virtual machine, and enhanced hardware support. Both products also offer a tool for compressing the hard drive image file that serves as the virtual machine’s hard drive.
The boot process for virtual machines created with either Parallels or Fusion is essentially the same as the boot process for an actual PC. One difference is that Fusion provides you with a virtual BIOS configuration tool that can be used to change boot options such as the order in which the virtual machine searches for a bootable drive. For its part, Parallels manages these features through a virtual machine configuration dialog. Fusion also supports network boot from a Windows PXE server, which Parallels does not.
Although Parallels boots consistently, Fusion is prone to the occasional unexplained Windows boot failure (generally resolved by simply rebooting the virtual machine).
Ease of use
Most users will find both Fusion and Parallels easy to use and will probably never even need to adjust the configuration settings from their defaults. With their respective tool sets installed under Windows, users can easily move between the Windows and Mac OS X environments. The shared folders technique used in both applications is solid, though it took me a couple of reinstalls of the VMware Tools to get this to function properly in Fusion.
VMware delivers another option to accessing files between operating systems with its support for drag and drop of files and folders between virtual machines and Mac OS X. This is actually a much easier method than setting up shared folders, and it can be used without having to configure anything. But, as with the shared folders feature, I found that it did not always function properly. This is one of the few places where Fusion truly delivers something that every user will appreciate that Parallels does not, though this feature is slated for the next version of Parallels’ software, Desktop 2.
Parallels also offers a couple of features that make it more user-friendly than Fusion. One of those is clipboard support, allowing you to copy and paste between Mac and Windows applications. This makes working between the two operating systems much more seamless. /parallels-for-mac-restore.html.
Overall, both Parallels and Fusion rate well in the ease-of-use category — or will once some of the reliability issues are worked out during Fusion’s development.
Advanced configuration
Parallels offers a much broader set of options for advanced configuration. Fusion currently allows for configuration of shared folders, the use of a single hard drive image file, sound, CD-ROM access (read-only) and some basic network options.
In contrast, Parallels provides the ability to specify more granular virtual hardware information as well as the use of a disk image to mimic the functionality of a floppy drive. Parallels also offers the ability to clone or re-create with a different maximum size the hard drive image of a virtual machine. (Both applications use dynamically expanding hard drive images, but both also require a maximum size be set for the image when it is created.)
Parallels also supports the connection of multiple hard drive images and the use of multiple disk images or physical drives for use as CD/DVD-ROMs, as well as the creation of virtual serial and parallel ports. All of these features make it a more customizable than Fusion to a user or an application’s needs.
Both Parallels and Fusion offer limited choices for how virtual machines handle networking. Both products allow you to choose between using Network Address Translation to share your Mac’s network connection or choosing bridged access to a specific network adapter. Parallels also offers a host-only option that allows the virtual machine to connect to your Mac and any other virtual machines as though they were connected via a network. But it does not allow actual network access.
Neither product supports connection to multiple network cards or networks at this time, though Parallels Desktop 2 promises support for up to five network cards.
USB device access
Both Parallels and Fusion support access to USB devices connected to a computer, though Parallels currently only supports USB 1.1. Parallels gives you the option of having devices be automatically detected and used by the virtual machine or to manually choose the devices that will be used. It appears that this is the how Fusion will ultimately function, but that the capability has not yet been implemented.
Fusion offers access to built-in iSight cameras, Apple’s Bluetooth adapter (built-in or USB) and built-in IR ports, which are treated as USB 2.0 devices and are not supported by Parallels.
Overall impressions
Parallels For Mac Student Free
Both Parallels Desktop and VMware Fusion are good products. However, it is clear that Fusion still needs some work in terms of its performance and to fully implement its feature set. It also isn’t quite as stable and reliable as Parallels.
All of that is to be expected from a product currently in beta testing, but it does mean that Parallels remains the better option for the time being despite the fact that Fusion offers some features that the commercial release of Parallels doesn’t, such as drag and drop, control over how many processor cores virtual machines can access and full USB 2.0 support.
It is also worth noting that the next release of Parallels is slated to offer at least two of those features — drag and drop and USB 2.0. It is also slated for several more advances including the ability to use a Boot Camp partition as a Windows boot disk instead of a hard drive image file, greatly enhanced network options and full support for CD/DVD drives (including burn capabilities and access to copy-protected discs). There will also be a new mode called “coherence” that will allow Windows applications to run alongside Mac applications without the need for a separate Windows interface (i.e. Windows applications display right on the Mac desktop and appear in the Dock).
As a result, it seems that for the foreseeable future, VMware will remain a generation behind Parallels.
Explainer: Virtualization Vs. Boot Camp
Products that use virtualization are, of course, not the only option for running Windows on an Intel Mac. The other option is Apple’s dual-boot system called Boot Camp. The primary advantage to virtualization is that a user doesn’t have to leave the Mac OS X environment or restart the computer to run Windows because it is in a virtual environment within Mac OS X. Virtualization also offers support for a much wider range of Windows versions as well as other operating systems.
One major point in favor of Boot Camp is that the end-user license agreements for Windows Vista restrict its use in virtualized environments. This means that users wishing to run Vista with either Parallels or Fusion will need to purchase the more expensive Business or Ultimate editions of Vista. Even when using those, Microsoft forbids use of the digital rights management technologies that are built into Windows and recommends against the use of third-party DRM products as well.
This means that users should consider carefully whether or not to purchase Vista for use with virtualization products. The better option might be Boot Camp if Vista is being used for access to protected content from services not available for Mac OS X.
Under the hood, there are some serious differences between dual-booting and virtualized solutions. When a Mac boots into Windows using Boot Camp, it essentially is a Windows PC. When virtualization is used, Windows does not have direct access to most of the Mac’s hardware. Virtualization uses a feature of Intel processors to essentially partition the processor into virtual processors and then gives the primary operating system and each guest operating system access to these processors. It also relies on a mix of genuine and virtual hardware to complete the creation of a virtual machine onto which Windows and applications are installed and run.
Ryan Faas is a freelance writer and technology consultant specializing in Mac and multiplatform network issues. In addition to writing for Computerworld, he is a frequent contributor to InformIT.com. Ryan is also the co-author of Essential Mac OS X Panther Server Administration (O’Reilly Media, 2005). You can find more information about Ryan, his consulting services and recently published work at www.ryanfaas.com, and you can e-mail him at ryan@ryanfaas.com.
This story, 'Mac virtualization: VMware vs. Parallels' was originally published by Computerworld.
Anyone using parallels to for mac landfx. Jul 11, 2018 Parallels Desktop 13 for Mac will support the newer version of Mac Os once it is officially released. Please subscribe to this article to know about the. Browse to the LandFX folder on the Mac side. In most cases, Parallels will assign the letter Z to the drive associated with files and folders on the Mac side of your computer. In our example, the path to the LandFX folder is This PC Home on 'Mac' (Z:) Documents Landfx. You don’t have to give up your Mac to run Land F/X. Essential programs like AutoCAD, SketchUp, GIS, Rhino, and yes, Land F/X, all either require or work better with a Windows operating system. Fortunately, a program called Parallels allows you to do just that.