topic Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016 in Endpoint

Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

Matt_Parfitt — Thu, 17 Aug 2017 09:26:04 GMT

I am templating a Windows Server 2016 build and have installed the initial CheckPoint Endpoint Security Client.

I've deployed from the template and the status of the endpoint client is 'The Endpoint Agent is not available'.

Is there any steps I need to take in order to Sysprep the initial client in the my template?

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

Moti — Sun, 20 Aug 2017 17:36:00 GMT

Dameon Welch Abernathy

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

PhoneBoy — Mon, 21 Aug 2017 04:46:33 GMT

Some TAC tickets suggest the issue is occurring because the Windows image deployed contains an Endpoint client that has already registered with the server.

This deployment method can work, however the Endpoint registration process must occur after the workstation finishes its registration and acquires its SID.

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

Matt_Parfitt — Tue, 22 Aug 2017 15:04:20 GMT

Thanks for the reply Dameon.

Apologies if I'm being stupid - what does TAC mean?

Also, do you have any other information on what's required in order to make the Endpoint registration occur after the workstation?

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

PhoneBoy — Tue, 22 Aug 2017 16:50:24 GMT

TAC means Technical Assistance Center

Contact Support | Check Point Software

I will admit, I'm not familiar with the sysprep process.

I assume that means copying the MSI file to the image but not executing the MSI until post-install (i.e. machine boots for first time and gets a new SID).

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

Hugo_vd_Kooij — Wed, 23 Aug 2017 07:27:35 GMT

I happen to know from Trend Micro OfficeScan that the trick is usually that you install the client in the image then run a tool to delete the identifier on the client.

So if you deploy it it generates a new and unique identifier on each and every workstation. I guess something similar needs to be done for the endpoint client.

But I am a bit weak in my experience with endpoint software and troubleshooting. (it's on my to-do list somewhere.)

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

Matt_Parfitt — Thu, 24 Aug 2017 12:31:59 GMT

Thank you I will keep trying!

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

Matt_Parfitt — Thu, 24 Aug 2017 12:32:53 GMT

I see, that's helpful thank you. I'll go searching for a tool that can delete the identifier.

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

Jeroen_Demets — Tue, 16 Jan 2018 13:05:32 GMT

Hi,

did you find a way to delete the identifier?

We have the same question because we want to use Citrix Provisioning Services with Windows Server 2016. This means several servers will be booting off one image.

Thanks

Re: Sysprep CheckPoint Endpoint Security Client - Windows Server 2016

Miguel_Angulo — Tue, 16 Jan 2018 20:02:04 GMT

what deployment solution you use to deploy the sysprep'd image?