Even Macs can pick up annoying adware programs from the Internet. Our tool is a free app that quickly eliminates adware from your Mac. The current version detects and removes Genieo and Vsearch. Mac support tool No. 3: Thursby's ADmitMac. ADmit Mac provides another alternative to Apple's Active Directory plug-in. It offers a number of advanced features, including smartcard support for. Integrate Active Directory using Directory Utility on Mac. You can use the Active Directory connector (in the Services pane of Directory Utility) to configure your Mac to access basic user account information in an Active Directory domain of a Windows 2000 or later server. Google Ads Editor Make changes across your campaigns with ease Google Ads Editor is a no-cost, downloadable application that lets you work offline and make bulk changes quickly, and easily. Download Google Ads Editor. Download Google Ads Editor on a computer running Windows or Mac OS. Adware Removal Tool is a self-explanatory Mac OS X application that enables you to free your Mac from disrupting adware (Genieo) with just a few mouse clicks. Quickly and effortlessly remove Genieo from your Mac. Genieo is an annoying malware classified as a browser hijacker that changes your Internet.
To read this blog post in Spanish, please click here.
Apple® Mac devices are growing in corporate popularity by the day. It’s up to IT departments to make sure that these devices utilize all resources in the environment, as well as ensure they’re visible and managed.
This can be a challenge, as Mac and Windows are very different, and Mac devices remain a minority in Windows-dominant environments. Determining how to incorporate Mac into a Windows infrastructure includes a number of factors, such as: the number of devices that need support; what type of access they require; and what tools and systems an organization already has. IT departments also need to figure out how to integrate Mac with existing Windows and Active Directory domains.
In Windows-centric organizations, managing Mac is not the highest priority on the IT project list for a variety of reasons. Few IT teams have expertise in managing Mac. Familiar techniques for managing PCs don’t help, and the best practices for dealing with Mac in a complex enterprise infrastructure can be convoluted and are not widely known.
IT teams take four main approaches when trying to accommodate Mac devices:
- Incorporate Mac devices into the Active Directory (AD) domain using existing tools meant for Windows computers.
- Use special third-party tools to manage Mac devices in the AD domain.
- Manage Mac like mobile devices.
- Manage both Mac and PC computers in Microsoft SCCM.
Some teams decide to have unmanaged macOS® devices in the environment, but this is a big security risk. You won’t necessarily lose a job if a Mac gets hacked and your infrastructure becomes vulnerable, but this can be destructive in many other ways.
Let’s take an in-depth look at these four approaches to managing Mac devices in a Windows environment.
1.Incorporate Mac devices into the Active Directory domain using existing tools.
This is the preference of many IT administrators. It’s possible to a certain degree; Mac desktops and laptops include the client component necessary to join AD and other standards-based directory services. Binding a Mac to the domain is relatively simple. Windows Server automatically creates the computer object in AD (unless it already exists), just like it would with a Windows desktop.
Recent macOS releases make it even easier to integrate Apple products, as the OS can work with Microsoft System Center Configuration Manager (SCCM) and Microsoft Exchange ActiveSync.
The fact remains, however, that Mac computers are not Windows desktops, and most management products are built for Windows. Native SCCM capabilities for Mac devices are limited and insufficient for full macOS lifecycle management. Compatibility issues inevitably come up. One way to smooth these issues is to extend the AD schema to better accommodate Mac computers. However, that requires development resources and technical expertise beyond what many companies can commit, especially if Mac devices are in the minority.
2. Use special third-party tools to manage Mac devices in the AD domain.
AD and command support in macOS make integrating Mac devices easier, but many administrators still like to use other tools to help with management. For example, IT admins can join Mac devices to AD domains and then use Apple Remote Desktop™ to push commands out to Mac clients.
An alternative is to implement Mac OS X® Server on its own system; Apple Profile Manager can then be used to set Mac policies based on AD groups. This entails setting up an Apple Open Directory domain alongside the AD service, which can make management easier in the long term. The Mac devices are still bound to AD, so there is seamless communication between the two environments, as well as shared file and printer services.
If this sounds too complicated, there is Centrify User Suite (Mac Edition), which can administer Mac devices and centrally manage authentication, policy enforcement, and single sign-on. Another option is Jamf Pro, a comprehensive endpoint management product.
3. Manage Mac like mobile devices.
Apple is moving toward a mobile device management (MDM) model, rather than a traditional directory services model. This means that IT admins can use the same management tools on Mac computers, iOS, and Android devices.
The new Apple MDM framework allows administrators to initiate AirPlay® sessions on managed devices and push enterprise applications to Mac computers. Improved OS X Server and platform capabilities also make it more MDM-friendly. Users can register Mac devices, and vendors can make use of a greater number of application programming interfaces available to third-party security and management solutions.
Many MDM vendors have quickly embraced new Mac features, such as VMware AirWatch. AirWatch allows admins to manage Mac computers alongside smartphones and tablets and perform a wide variety of tasks.
Organizations can also implement a separate tool, such as MobileIron or an Apple server not bound to AD. This allows IT admins to implement user access through virtual private networks without having to join the devices to the domain. This is useful when incorporating users’ personal Mac laptops.
4. Manage both Mac and PC computers in Microsoft SCCM.
This approach works best for organizations that already use Microsoft SCCM to manage PC. However, Microsoft SCCM alone has only a few features for managing Mac devices—not enough for managing Mac in enterprise. SCCM allows for the following:
- Setting up support and enrolling macOS clients.
- Deploying settings to macOS clients.
- Performing hardware inventory of macOS clients.
- Deploying applications to macOS clients.
While SCCM is capable of managing these devices, additional items need to be installed and configured to support Mac. You’ll need to implement a public key infrastructure for Active Directory Certificate Services. These certificates are used to communicate with SCCM through SSL communications. Each Mac with a SCCM client installed acts like an Internet-based client.
Since the Mac devices are acting like Internet-based clients, you’ll need to have a Configuration Manager Site server with a fully qualified domain name, as well as a minimum of one HTTPS-enabled management point and one HTTPS-enabled distribution point.
You’ll also need to configure the enrollment point and enrollment proxy point features in SCCM. This will allow your macOS clients to be enrolled in the SCCM environment after the client is installed. In order to enable the management of these macOS clients, you’ll need to configure custom client settings.
SCCM’s built-in support for Mac OS does work great, but there are certain limitations to the features and functionality of this support. To manage Max OS X clients, you must have PKI infrastructure and additional SCCM site systems. If you’re not planning on enabling HTTPS communications for your entire corporate environment, you’ll need to have multiple management points and distribution points. One management point will be configured for HTTP communications, and one will be configured for HTTPS communications, as is the same for the multiple distribution points.
Extend SCCM for Enterprise-Level Mac Management
What if you could add the same right-click management that Windows devices receive in SCCM to Mac devices? What if you could do it with a short learning curve, no silos, and the same system administrators?
There is a solution that can do all of this and more: Parallels® Mac Management for Microsoft® SCCM. Parallels Mac Management gives SCCM all the missing tools for Mac management, including FileVault® 2 encryption, macOS deployment, application delivery, Apple Device Enrollment Program, and compliance via SCCM configuration items and baselines.
With Parallels Mac Management, you simply add full macOS lifecycle management to Microsoft SCCM and manage PC and Mac computers in a single pane of glass. There’s a minimum learning curve and no additional infrastructure required. The solution leverages your Microsoft SCCM investments and enables Windows admins to manage Mac computers.
For further information on Parallels Mac Management, please feel free to contact our sales team to request a free trial.
-->This article describes the tools that are available in Remote Server Administration Tools (RSAT) for Windows.
Original product version: Windows 10, version 1909, Windows 10, version 1903, Windows 10, version 1809. Windows 7 Service Pack 1. Windows Server 2019. Windows Server 2012 R2
Original KB number: 2693643
Introduction
RSAT enables IT administrators to remotely manage roles and features in Windows Server from a computer that is running Windows 10 and Windows 7 Service Pack 1.
You cannot install RSAT on computers that are running Home or Standard editions of Windows. You can install RSAT only on Professional or Enterprise editions of the Windows client operating system. Unless the download page specifically states that RSAT applies to a beta, preview, or other prerelease version of Windows, you must be running a full (RTM) release of the Windows operating system to install and use RSAT. Although some users have found ways of manually cracking or hacking the RSAT MSU to install RSAT on unsupported releases or editions of Windows, this is a violation of the Windows end-user license agreement.
Installing RSAT is similar to installing Adminpak.msi in Windows 2000-based or Windows XP-based client computers. However, there's one major difference: in Windows 7, the tools aren't automatically available after you download and install RSAT. You must enable the tools that you want to use by using Control Panel. To do this, click Start, click Control Panel, click Programs and Features, and then click Turn Windows features on or off.
In the RSAT releases for Windows 10, tools are again all enabled by default. You can open Turn Windows features on or off to disable tools that you don't want to use for Windows 7.
For RSAT in Windows 7, you must enable the tools for the roles and features that you want to manage after you run the downloaded installation package.
Note
You cannot do the following changes for RSAT in Windows 8 or later versions.
If you have to install management tools in Windows Server 2012 R2 for specific roles or features that are running on remote servers, you don't have to install additional software. Start the Add Roles and Features Wizard in Windows Server 2012 R2 and later versions. Then, on the Select Features page, expand Remote Server Administration Tools, and then select the tools that you want to install. Complete the wizard to install your management tools.
Download locations for RSAT
Add Mac To Active Directory
RSAT for Windows 10 platform and tools support matrix
| Remote Server Administration Tools Technology | Description | Manages technology in Windows Server 2012 R2 | Manages technology in Windows Server 2016 Technical Preview and Windows Server 2012 R2 |
|---|---|---|---|
| Active Directory Certificate Services (AD CS) tools | AD CS tools include the Certification Authority, Certificate Templates, Enterprise PKI, and Online Responder Management snap-ins. | √ | √ |
| Active Directory Domain Services (AD DS) tools and Active Directory Lightweight Directory Services (AD LDS) tools | AD DS and Active Directory Lightweight Directory Services (AD LDS) tools include Active Directory Administrative Center, Active Directory Domains and Trusts, Active Directory Sites and Services, Active Directory Users and Computers, ADSI Edit, Active Directory module for Windows PowerShell; plus tools such as DCPromo.exe, LDP.exe, NetDom.exe, NTDSUtil.exe, RepAdmin.exe, DCDiag.exe, DSACLs.exe, DSAdd.exe, DSDBUtil.exe, DSMgmt.exe, DSMod.exe, DSMove.exe, DSQuery.exe, DSRm.exe, GPFixup.exe, KSetup.exe, NlTest.exe, NSLookup.exe, W32tm.exe. | √ | |
| Best Practices Analyzer | Best Practices Analyzer cmdlets for Windows PowerShell | √ | √ |
| BitLocker Drive Encryption Administration Utilities | Manage-bde, Windows PowerShell cmdlets for BitLocker, BitLocker Recovery Password Viewer for Active Directory | √ | √ |
| DHCP Server tools | DHCP Server tools include the DHCP Management Console, the DHCP Server cmdlet module for Windows PowerShell, and the Netsh command-line tool. | √ | √ |
| DirectAccess, Routing and Remote Access | Routing and Remote Access management console, Connection Manager Administration Kit console, Remote Access provider for Windows PowerShell, Web Application Proxy | √ | √ |
| DNS Server tools | DNS Server tools include the DNS Manager snap-in, the DNS module for Windows PowerShell, and the Ddnscmd.exe command-line tool. | √ | √ |
| Failover Clustering tools | Failover Clustering tools include Failover Cluster Manager, Failover Clusters (Windows PowerShell cmdlets), MSClus, Cluster.exe, Cluster-Aware Updating management console, Cluster-Aware Updating cmdlets for Windows PowerShell | √ | √ GUI tools support Windows Server 2016 Technical Preview and Windows Server 2012 R2. Only PowerShell tools work in Windows Server 2012. |
| File Services tools | File Services tools include the following: Share and Storage Management tools, Distributed File System tools, File Server Resource Manager tools, Services for NFS Administration tools, iSCSI management cmdlets for Windows PowerShell; Work Folders Management Tools - Distributed File System Tools include the DFS Management snap-in, and the Dfsradmin.exe, Dfsrdiag.exe, Dfscmd.exe, Dfsdiag.exe, and Dfsutil.exe command-line tools and PowerShell modules for DFSN and DFSR - File Server Resource Manager Tools include the File Server Resource Manager snap-in, and the Dirquota.exe, Filescrn.exe, and Storrept.exe command-line tools. | √ | √ The Share and Storage Management snap-in is deprecated after the release of Windows Server 2016.Storage Replica is new in Windows Server 2016 Technical Preview, and won't work in Windows Server 2012 R2. |
| Group Policy Management tools | Group Policy Management tools include Group Policy Management Console, Group Policy Management Editor, and Group Policy Starter GPO Editor. | √ | √ Group Policy has some new features in Windows Server 2016 Technical Preview that are not available on older operating systems. |
| Hyper-V tools | Hyper-V tools include the Hyper-V Manager snap-in and the Virtual Machine Connection remote access tool. | Hyper-V tools are not part of Remote Server Administration Tools for Windows 10. These tools are available as part of Windows 10. You do not have to install RSAT to use the tools. The Hyper-V Manager console for Windows Server 2016 Technical Preview doesn't support managing Hyper-V servers running Server 2008 or Server 2008 R2. | Hyper-V in Windows 10 can manage Hyper-V in Windows Server 2012 R2. |
| IP Address Management (IPAM) Management tools | IP Address Management client console | √ IPAM tools in Remote Server Administration Tools for Windows 10 cannot be used to manage IPAM running in Windows Server 2012 R2. | √ IPAM tools in Remote Server Administration Tools for Windows 10 cannot be used to manage IPAM running in Windows Server 2012 R2. |
| Network Adapter Teaming, or NIC Teaming | NIC Teaming management console | √ | √ |
| Network Controller | Network Controller PowerShell module | Not available | √ |
| Network Load Balancing tools | Network Load Balancing tools include the Network Load Balancing Manager, Network Load Balancing Windows PowerShell cmdlets, and the NLB.exe and WLBS.exe command-line tools. | √ | √ |
| Remote Desktop Services tools | Remote Desktop Services tools include the Remote Desktop snap-ins, RD Gateway Manager, tsgateway.msc, RD Licensing Manager, licmgr.exe, RD Licensing Diagnoser, lsdiag.msc. Use Server Manager to administer all other RDS role services except RD Gateway and RD Licensing. | √ | √ |
| Server for NIS tools | Server for NIS tools include an extension to the Active Directory Users and Computers snap-in, and the Ypclear.exe command-line tool | These tools are not available in RSAT for Windows 10 and later releases. | |
| Server Manager | Server Manager includes the Server Manager console. Remote management with Server Manager is available in Windows Server 2016 Technical Preview, Windows Server 2012 R2, and Windows Server 2012. | √ | √ |
| SMTP Server tools | SMTP Server tools include the Simple Mail Transfer Protocol (SMTP) snap-in. | These tools are not available in RSAT for Windows 8 and later releases. | |
| Storage Explorer tools | Storage Explorer tools include the Storage Explorer snap-in. | These tools are not available in RSAT for Windows 8 and later releases. | |
| Storage Manager for Storage Area Networks (SANs) tools | Storage Manager for SANs tools include the Storage Manager for SANs snap-in and the Provisionstorage.exe command-line tool. | These tools are not available in RSAT for Windows 8 and later releases. | |
| Volume Activation | Manage Volume Activation, vmw.exe | √ | √ |
| Windows System Resource Manager tools | Windows System Resource Manager tools include the Windows System Resource Manager snap-in and the Wsrmc.exe command-line tool. | √ WSRM has been deprecated in Windows Server 2012 R2, and tools for managing WSRM are not available in Remote Server Administration Tools for Windows 8.1 and later releases of RSAT. | |
| Windows Server Update Services tools | Windows Server Update Services tools include the Windows Server Update Services snap-in, WSUS.msc, and PowerShell cmdlets. | √ | √ |