Below you will find out how to install the Bitdefender clients – including building the packages. This includes Windows, and Mac.
Bear in mind that you should have your OS patched to current, and if you have firewall or other security products installed check this article out. What a long amazing list of anti-malware software that BD can uninstall.
Here is an article that will help you build an MSI for mass delivery of the Windows client.
Installation – Windows desktop
We will install the first client on my Windows desktop. We will do this by creating a package that we execute on my desktop manually. It uses the policy settings and I can customize a little. So lets get started.
- Change to the Networks \ Packages view.
- Use the Add button to add a new endpoint package. Give it a name and description.
- I have also deselected the Firewall but made no other choices. Firewalls are hard enough to manage and AD is already doing that for me in the lab. When you are done use the Save button.
- We see we have a new package now.
- I am going to select it and download it. I get a lot of choices of what to download.
- I like how this one package – currently with a default policy and simple configuration can be applied in a variety of different operating systems. Very nice. I suspect some of the ones that are not available are due to them not being on my appliance, or not licensed. I should mention an hour later the Mac kit could be downloaded. So maybe it was just time and once a package was created things were downloaded to match.
- I will now execute the kit on my desktop manually. It extracts to just two files.
- I double-click on the .exe and I am prompted to extract the files and it suggests that is the best thing to do.
- Once it is done, and it doesn’t take long I see the main install file.
- And of course I double+click on it.
- UAC says are you sure. In two places it asks.
- Now I see this.
- Next I see that it needs a restart and will continue automatically after the restart. Likely due to removing MSE.
- So removing MSE – good. But this does show this is not a silent process so not yet suited for a login script or GPO distribution. Due to removing MSE there was a restart required and it said it would continue after the restart. There is a way it seems to push out from the appliance an install and that may be more flexible. The package I created and downloaded is designed for remote computers with no or very slow internet.
- In fact the install process does restart after the restart and almost the first thing it does is scan.
- Even with the restart, and scan, the install is finished pretty fast.
- We can see it running in the tray.
- When we start it up we see a minimalist UI which I like.
- My 2 risks go away after a very quick update and a not so quick scan. The scan doesn’t show much detail but if you use View Details you can see more about what is happening.
I can build a package and enable Exchange support in it very easily and protect both the OS and Exchange itself including the email traffic. Handy.
Installation – Mac
I use the same Power User package but download the Mac Kit for it. It downloaded a .dmg file and that needs to be copied to my local Mac hard drive before I can execute it.
It is a simple install – confirms which disk, asks for authentication and installs. Once it finishes the install you see the main screen. But there is also clue it is working – up in the top right corner of the screen.
From it (click on it) I can Open Main Window which is seen below.
So pretty easy! Very nice UI and well done by Mac standards. Uses the OS X notifications nicely too. BTW, my issue was that I needed to allow Bitdefender access to my extensions in the security area. Which was two clicks.
- 9/25/18 – I learned something quite important today about Bitdefender and updates. The default policy, or one that you do if it has update enabled, means that clients will be discretely updated. Even if you do a package with old bits in it that once installed, you will have it updated to current. This is why when I upgraded my Mac to the new OS the AV client actually worked without me having to uninstall and install like I had to on other machines with different AV.
- 9/24/18 – added the link for help with creating an MSI.
- 9/9/18 – published
=== END ===