Removes all known adware from your Mac. It is very simple to use, and should clean up your system in less than a minute, from start to finish. Just open the app, click the Scan for Adware button, and remove anything that is detected. That’s it!

If AdwareMedic doesn’t solve your problem, it includes the ability to take a system snapshot that can help find possible sources for the problem. This both helps you get rid of the adware and helps others by improving the app!

AdwareMedic will not install anything on your system. When it is opened, it will connect to adwaremedic.com to check for and/or download the latest adware “signatures” (a small text file that tells AdwareMedic how to identify adware components).

Although AdwareMedic functions somewhat like anti-virus software, it’s important to understand that it is not anti-virus software! It does not remove any real malware – only adware. If you think you may be infected with actual malware, be aware that there is nothing that can reliably remove all malware. For more information, see The Safe Mac’s Mac Malware Guide and the article How to remove infected files.

It is also important to understand that AdwareMedic does not protect you against adware. AdwareMedic simply removes adware. Using AdwareMedic will not prevent you from being “infected” with adware again in the future. For that matter, neither will using anti-virus software; only a change in your online habits can keep you safe.

If you are leery of using unfamiliar software to remove a problem caused by downloading some other unfamiliar software – which is a perfectly reasonable thing, and is a precaution people should take more often – then you can follow the manual removal instructions in my Adware Removal Guide instead. This guide is kept in sync with everything AdwareMedic removes.

What is adware?

Adware is unwanted software that uses sneaky and dishonest methods to get installed on your computer, and then changes the behavior of your web browser. Once installed, it does things like injecting advertisements into web pages, causing pop-up windows or tabs to open to advertising sites, and changing your home page and/or search engine.

Although adware sounds like malware, there is a crucial difference: adware on the Mac has never been documented to involve keylogging, back doors or any other such malicious activities… just unwanted advertising. As such, most anti-virus software doesn’t bother to detect most adware, and if it does, it doesn’t do a very comprehensive job of detecting it. This is where AdwareMedic comes in – it detects the adware that anti-virus software doesn’t.

Where did it come from?

The short answer: from an installer for some app you were tricked into downloading from an unsavory site. This may be a site like Download.com or Softonic, or a site offering streaming of “free” videos, or from a piracy site or torrent, or something else similar.

When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
“Unable to connect to the server by using Windows PowerShell remoting”.

Figure 1: Unable to connect to the server by using Windows PowerShell remoting
First of all, we need to verify the configurations as it suggested:
1. The server must be available by using Windows PowerShell remotely.
2. The server must be joined to a domain.
3. The server must be running at least Windows Server 2012 R2.
4. The currently logged on user must be a member of the local Administrators group on the server.
5. Remote Desktop Services connections must be enabled by using Group Policy.
In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
Enable-PSRemoting -Force

Figure 2: Enable PowerShell Remoting
However, if issue persists, we need to check whether it has enough memory to work.
By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase the memory via the PowerShell command below:
Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000
Then, you need to restart the server and the issue should be resolved.

In this tech tip, we’re going to cover how to deal with the “Unlicensed Product” error / red title bar that you might occasionally see in Office 2010 or Office 2013 when you are licensing against an Office 365 subscription.

One of the things to remember is that when you leverage an Office 365 software-eligible subscription, it does not license your local copy of Office with a product key. It uses a software liaison that will frequently reach out to Microsoft’s servers to validate that your copy of Office is legitimate for use. Often times, this piece of software gets confused and “breaks” Office, leaving you with a program that’s stuck in reduced functionality mode – indicated by a red bar across the top of the app.

The easiest way to fix this is to simply “remind” Office which user is licensed to use it.

For Office 2010:
.: Open a Command Prompt as an administrator, and then copy/paste or type in one of the following commands below – quotations included – for whatever your corresponding versions of Windows and Office are, and then press enter.32-bit Office and 32-bit Windows

This will bring up the Office Sign-In Assistant dialog box; you’ll want to type in the credentials for the user that you’re trying to license Office for. (These are the creds that you would log into Office 365 with.)

For Office 2013:
.: Open a Command Prompt as an administrator, and then navigate to one of the paths below by copy/pasting the first area of code – quotations included – for whatever your corresponding versions of Windows and Office are and press enter. Once you’re in the appropriate folder, you can then copy/paste or type in: cscript ospp.vbs /act and press enter.32-bit Office and 32-bit Windows

Today am discussing about uploading thumbnail photos to active directory which will help for Office 365 mail system SSO and Lync users can see the colleague photos

For doing this you should have at least one of the domain controller run on Windows server 2012 R2.

Here is the procedure for doing this

First you have alias name of all the active directory users and save this file as csv format. Another thing you have passport size photograph for all the users , the size should be less than 10 KB otherwise photo’s won’t appear in the search directory and save these photos by using the alias name and put the photos and csv files in the Windows server 2012 R2 domain controller.

Here is the option for the mac users to reduce the photo size to less than 10 KB

Use the software called Shrink-o-Matic, by using u can reduce the photos by batch as well as single size also.