topic Re: Is it possible deploy sandblast agent in environment with unmanage endpoint/no active directory in Endpoint

Is it possible deploy sandblast agent in environment with unmanage endpoint/no active directory

Daka — Tue, 05 May 2020 12:52:03 GMT

Hi Folks,

i have a question, Is it possible deploy sandblast agent in environment with unmanage endpoint/no active directory? because on endoint managaement server i see, there are a configuration that let we register active directory to the endpoint managament sever via organization scanner. is it mandatory requirement or have another workaround?

Thankyou,

Re: Is it possible deploy sandblast agent in environment with unmanage endpoint/no active directory

Kobie_Bendalak — Sat, 09 May 2020 11:34:13 GMT

SBA can be deployed on Workgroup computers, see following SKs sk164957 OR sk92329 for example.

With that said, know there are a few limitations around it.

For instance, customers who install the Endpoint Security Client before joining the domain to their environment, will result in a lot of duplicate machines in the "Other users/computers" folder in their SmartEndpoint.

Re: Is it possible deploy sandblast agent in environment with unmanage endpoint/no active directory

Daka — Sat, 09 May 2020 14:40:02 GMT

Hi kobie,

thanks for information. I try to access sk92329 but it seems the sk is not available. Can you check again the above sk did you mean?

Re: Is it possible deploy sandblast agent in environment with unmanage endpoint/no active directory

Kobie_Bendalak — Sat, 09 May 2020 14:47:03 GMT

My apologies, it's classified as internal and is available only for Check Point employees. sk164957 Shows that we do support workgroups.

Re: Is it possible deploy sandblast agent in environment with unmanage endpoint/no active directory

Daka — Sun, 17 May 2020 08:15:27 GMT

Hi Koby,

on this SK i read. if we deply sba on workgroup/un managaed devices, we maybe facing issue duplicate machine name appear on smart endpoint (please correct if iam wrong). if it correct, so any advice regarding what we can do/take attention to avoid this issue during deployment on unmanaged devices environemtn? any sk or workaround? Thanks for your attentions.