Translations of this page: not yet ported. Translators, see Discussion page.

Over time, there have been a variety of Third Party Applications that have attempted to make Wine more useful or easier to use.It is important to understand that although these third party applications may make Wine more usable, they are not supported by the Wine project. If you have questions regarding the use of a third party application, please use the support mediums provided by that third party rather than Wine HQ.

AD administration tools for windows on Ubuntu. I've recently moved into using Ubuntu as a work platform to get some exposure to the Linux side of things. As you might have guessed I'm relatively new to the OS. You might be able to run RSAT well under wine, too; I've never tried but it seems like it should be easy enough. Wine (originally an acronym for 'Wine Is Not an Emulator') is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, such as Linux, macOS, & BSD.

Why Third Party Applications Exist

Users want to run applications and sometimes a change to Wine can cause an application to work, but this change cannot be incorporated into Wine for some reason. For example, the change may break Wine for other applications and/or platforms. As such changes to Wine must meet some level of QA. If the change is a dirty hack to Wine's source code that allows an application to run, then the change may end up within Wine's source code only after it has been properly fixed.

In theory, any third party application here is essentially a temporary workaround until underlying bugs in Wine can be fixed properly. As wine improves, parts or all of these third party applications may become obsolete or incompatible with Wine (at least until the third party provides a suitable update).

Current Third Party Applications

The applications below should work with the latest Wine and are still being maintained.

The Crossover series of products are a repackaging with added patches to support more applications and added interfaces on top of WineHQ.

DOSBox is an emulator for legacy x86 PCs, which is particularly useful for old MS-DOS programs since they often used hardware in rigid ways (e.g. using CPU clock cycles directly for timing). Wine uses DOSBox for its virtual 8086 mode (for more details, see Wine Wiki's DOSBox page).

This module allows unix windows managers to generate crisp desktop icons from the icons embedded in Windows executables.

A Python-based GUI tool that provides managing of registry keys for Wine.

Lutris is an open gaming platform for Linux. It helps you install and manage your games in a unified interface. This support includes managing Windows games (run via Wine).

A tool which is aiming on making it easy for the user to install Windows software, like World of Warcraft, Adobe Photoshop, Guild Wars and much more.

A tool made by the same team as PlayOnLinux but for Mac user.

A tool for installing games, applications, and various redistributable runtimes, e.g. mono, dcom98, fonts. Workarounds to Wine bugs are run automatically. (See also the Winetricks page on this wiki.

A tool to install and run pre- or custom configured apps. It comes with precompiled wine and allows to create fully self-contained .app bundles.

Create wrappers used to make ports that work like Native macOS applications. Uses Winehq portable releases, bundles all needed dylibs and binarys for use with winetricks, always downloads the current version of winetricks.

Using Wineskin technology, Porting Kit can install games and apps compiled for Microsoft Windows® in macOS. It's free, it's simple, it's the Porting Kit.

A Qt GUI for Wine. It will help you manage wine prefixes and installed applications.

A DirectX 1-11 to OpenGL wrapper based on WineD3D.

Obsolete Third Party Applications

These applications are no longer useful, unmaintained, and do not work with current Wine releases. You should not use these.

• osxwinebuilder (for Mac OS X)

A command line script to compile and install Wine and a number of prerequisite packages from source on Mac OS X.

Make wrappers or ports of Windows software to Macs. Wine and custom Xquartz X11 all built in. Pre-built packages, or you can custom compile your own Wine source to use too. Finished products look and work like native Mac apps. File associations, fullscreen, multi-monitors, resolution switching.. great for games. LGPL licensed open source.

GUI bottle manager to import, create and clone bottles. Edit registers of the bottles. Set colors according to your GTK theme.

provide an OpenGL-based free replacement for Microsoft Direct3D (useful for things like VirtualBox)

A graphical frontend for Wine that offers prefix management, winetricks integration and access to most of the Wine command-line utilities in one GUI.

• WineXS

A GUI for Wine.

• Pipelight

A tool to use windows only plugins inside Linux browsers.

• Bordeaux

A tool for installing a lot of Windows applications on Linux, Free'BSD, PC-BSD, Open'Solaris & Mac like Microsoft Office, Microsoft Project, Adobe Photoshop, and more.

A menu driven installer for around 90 windows applications. No longer being maintained.

• WineDoors

A tool to install and configure Wine, as well as many Windows programs.

• Winesetuptk

A Wine setup tool formerly provided by CodeWeavers, Inc. Wine can now setup its own environment automatically, and Winecfg has now replaced the other limited configuration that winesetuptk allowed.

A graphical user interface for the WINE emulator. It provided an interface for configuring and running MS-Windows applications. It is no longer useful now.

• WineBot

A tool to automate Windows program installation under Wine

A python-based, command-line replacement for Winecfg. Has not been updated since 2009.

• wisotool

A tool for automated installs of various Windows programs (downloadable demos and from disk images), including workarounds. It was merged into winetricks.

A malware-analyzer that sandboxes Wine on Debian in a QEMU image (remember Wine provides no sandboxing). Windows executables are then loaded into the sandbox, and Wine's function-tracing system is used to detect suspicious behavior.

While delivering IT Virtualization Boot Camps across the country, we often get asked about how to administer Windows Server 2008 R2 computers running Hyper-V or other services remotely. This is especially true if you want to administer computers running Hyper-V Server or Windows Server 2008 R2 Server Core install. Mitch put together information on how to do this, so here it is.

In this day and age of virtualization it is not that it is getting harder to sit down at a server to administer it… it is just getting easier to administer it remotely. Where it does get easier is when you have several servers – often a mix of physical and virtual – that you need to manage. Sure, you can still sit down at the physical servers… you could even open an RDP (Remote Desktop Protocol) session to administer them individually from your desktop. However with each of those you are going to have to manage them all individually.

Enter the Remote Server Administration Toolkit (RSAT). Mac os x el capitan dmg download.

Unless you are using System Center to administer your servers, chances are you are either using PowerShell or, more likely at this point, MMC (Microsoft Management Console) consoles. As we learned in Microsoft Windows 2000 Server, MMC consoles can connect to remote servers (or desktops) as long as Windows Remote Management (WinRM) is enabled (Actually WinRM and the Windows Firewall were only introduced in Windows Server 2003 R2 if memory serves, but MMC consoles were remoteable ).

You can enable WinRM in Windows Server 2008 R2 from the Server Manager main screen (as shown):

(Note: For those of you running Server Core installations… good for you! you can do all of this with a simple command line: WinRM /quickconfig)

Now that we can remotely manage our servers, we can do so from any Windows Server 2008 R2 box by adding the appropriate feature from the Add Feature Wizard:

I should mention that you will not be able to manage systems on which you do not have credentials, and although the RSAT tools can work in a workgroup, they are much more fluid and trouble-free in a domain environment. Also remember that adding the role or feature under RSAT does not install the actual role or feature, only the consoles required to manage them.

This is great for administrators who want to manage their servers remotely from another server… but what about managing them from your desktop? There’s a simple solution for that. Simply download the Remote Server Administration Tools (RSAT) for Windows 7 (http://www.microsoft.com/download/en/details.aspx?id=7887) from the Microsoft Download Center. Using another version of Windows? There is an RSAT download available for WIndows Vista, but if you are still running Windows XP then I am afraid you are out of luck (…and have 777 days until #EndOfDaysXP!).

Once you have downloaded and installed RSAT into your Windows 7 machine you will see no difference. However if you go to Turn Windows features on or off, things start to change. To get there, open Windows Explorer and navigate to Computer. If you do not see the option to Uninstall or change a program chances are you have not clicked on Computer.

You should see a list of your installed programs on the right, but to the left there should see an option ‘Turn Windows features on or off (shown). Click there.

It will take a couple of minutes, but when it is done you are ready to start administering your servers from Windows 7… just click on the Start pearl, expand Administrative Tools, and the new consoles should be there.

You can load any of them up (for this example we will use Hyper-V Manager) and you have… nothing. However you can right-click on Hyper-V Manager in the Navigation pane, and click Connect to Server…

You can add multiple remote servers to the same MMC console (seen below), including full installations of Windows Server, as well as Server Core installations and (in the case of Hyper-V hosts) Windows Hyper-V Server, which have to be managed remotely as they have no graphical user interface (GUI).

So go ahead… manage your servers from your desktop without ever having to leave your office/cubical/desk/cafeteria. Wherever you like to work from!