Choose from several options for complete web, email and data security.
Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Come work for the global leader in unified information security.
Anyone have stats, info, feelings about the DirSync Client in regards to:
Have 8k to 10k users in an AD that will be using. Unclear yet how many different groups in the AD the web policy(s) will be using but was looking to get feedback from those that use it now.What sort of systems it you have it running on and do you see performance hits when it is running?
Will be configuring it to look for two ldap stores (primary and secondary location) I believe it will use either (or both if they are available, correct?)
I run it once an hour. I have to run it fairly frequently because ours is a large enterprise and there are many IT folks that can be adding users into the active directory groups that have the GPO linked to them that configures browsers to utilize the service. Once the GPO applies, the users' internet is broken until the dir sync job completes.
We have about 80K users on AD that are synced via our dir sync client. The biggest impact on the time to complete the synchronization is really the AD servers resources. Prior to upgrading them to Win Server 2008, it would easily take 45 min for the dir sync process to complete. Now, with all domain controllers on Win Server 2008, it takes 5 min or less for dir sync process to complete.
As far as resources on the server that hosts the dir sync client itself, we just followed what was in the documentation and have not had any issues.
The one thing you do need to be careful about is if not all of your users have email addresses in AD. If they don't you will need to change the default behavior of what dir sync client (e.g., pulling user principal name vice email address)