Remove BlueTooth Add-In from all Office365 applications via Group Policy

Can someone explain or provide me with (or provide a link to) an easy to follow way on how to remove the Bluetooth add-in from all Office365 installed applications via Group Policy?

We have a client whose staff use Office365.  Office365 applications are installed on the local workstations (Desktops and Laptops).  All the workstations are connected to the domain.

They also use the Exclaimer software to manage their signatures.  Whenever a change is made to the signature blocks in Exclaimer they get the issue of either in Word or Outlook (or both) asking to continually save changes to their respective dotm templates (i.e. every time they close a document or send an e-mail).  Removing the Bluetooth Add-In for Word and Outlook temporarily fixes the issue (and yes, I do that as the Administrator account), but somewhere along the line it re-installs and re-enables itself and the issue occurs again.  This is happening to a number of staff.

They have a mix of Windows 7 Professional and Windows 8.1 machines (all 64 bit).

What I'd like to do is have the Bluetooth add-in removed from all installed Office365 application via Group Policy.  I've searched Google but a lot of the solutions are doing my head in.  

Note: I don't want to just disable the plugin.  We want it gone completely.

Any and all help is appreciated.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jackie ManIT ManagerCommented:
You got a tough question.

What I could think of is to push the fix to the client machine via logon script.
KenostiAuthor Commented:
Yeah, that just disables it.  I want it removed completely.
If the installation was from the Office 365 portal the updates will always put the original installation back to what was chosen at the start - this behaviour is not open to fixing with GP.

If you copy the installation to a server and have on-premise installs you can prevent it being installed.

From your description you have taken the former path in which case the logon script disabling is probably the least worst way forward.

You probably already found this but it's explicit about the lack of control over Portal installations
Office 365 deployment planning

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
KenostiAuthor Commented:
So, that's what's happening.  Damnit.

I inherited the current methodology (only started six weeks ago).

Thanks for the link.  It isn't one I found and is the kind of information I was looking for. Will take an in-depth look at it later.

Keeping this open for a bit in case I need additional assistance.
KenostiAuthor Commented:
We went with another solution.  Moved the client to Exclaimer Cloud and removed the local Exclaimer agent form their machines.  Problem solved.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.