Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure TOTAL
F-Secure SAFE / Internet Security / Anti-Virus
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Common topics
User Guides
Support
Login
|
Register
New Active Directory default profile assignments feature - availability starting 23.1.2020 - F-Secure Community
<main> <article class="userContent"> <p>Hi,</p><p>we are now enabling a new feature that allows you to assign different default profiles based on a devices Active Directory organization path. So what does this feature do:</p><ol><li>It supports currently Computer Protection and Server Protection installations.</li><li>When you install a new Computer or Server Protection client, you can assign a profile based on Active Directory organization path instead of the company default profile.</li></ol><p>As this is the very first release for new service, it still has the following limitations that we are going to address in the coming months:</p><ul><li>Active Directory organization tree is built based on our software seeing AD paths reported by existing Computer or Server Protection devices. This means you cannot create rules for totally new deployments that don't have clients installed and reporting the AD paths. As very next step we are adding a feature to manually list your AD organization and then import it to PSB portal to be used.</li><li>If your device changes location in your AD organization tree, we currently do not automatically update the assigned profile.</li><li>We are already working on a feature that will allow you to make a computer follow changes to its AD path and use that for figuring out its current profile. This can be configured to be enabled on a per company basis.</li></ul><p>This new service also changes the process for how profiles are assigned to devices: instead of the assignment happening when a device registers to the system, it now happens when a device first starts sending upstream data to the backend. This allows us to add much more complex logic in the future for determining which profile will be assigned to the device.</p><p>The upcoming Computer / Server Protection 20.1 release will also bring a new way of assigning profiles to new installations. You will be able to give the profile id as a command line parameter to the installer when starting the client installation and the device will use the given profile instead of using the company default.</p><p>We will also soon roll out the frequently requested ability of filtering devices based on the profile that is assigned to them.</p><p>I've attached a couple of pictures that show what the feature looks like in the portal.</p><p> </p><div class="embedExternal embedImage"> <div class="embedExternal-content"> <a class="embedImage-link" href="https://us.v-cdn.net/6032052/uploads/0VJTC4ZR2JZF/8279i8e7fe96ade5ff48f.jpg" rel="nofollow noreferrer noopener ugc" target="_blank"> <img class="embedImage-img" src="https://us.v-cdn.net/6032052/uploads/0VJTC4ZR2JZF/8279i8e7fe96ade5ff48f.jpg" alt="8279i8E7FE96ADE5FF48F.jpg" /> </a> </div> </div> <p><br></p><p>Br,</p><p> PSB Team.</p> </article> </main>