<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Identity Collector server change from Windows 2022 to Windows 2025 in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280780#M46664</link>
    <description>&lt;P&gt;The gateways connect on IP basis with certificate. I would spin up new 2025 server, install latest IDC software. Export config from old system and import it:&amp;nbsp;&lt;A href="https://sc1.checkpoint.com/documents/Identity_Awareness_Clients_Admin_Guide/Content/Topics-IA-Clients-AG/Identity-Collector-Updating.htm?Highlight=export" target="_blank"&gt;https://sc1.checkpoint.com/documents/Identity_Awareness_Clients_Admin_Guide/Content/Topics-IA-Clients-AG/Identity-Collector-Updating.htm?Highlight=export&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Then add the new server to the gateway object in Smart Console.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Alternative you can install new 2025 with same IP, import config and turn off old server. But this is more risky because you lose the old server. With the first plan you can build the new one and take all the time you need. Would recommend to build 2 IDC servers on 2025 if one breaks down or you need to run windows update there is one left.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Server name is not relevant.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Aug 2026 13:32:41 GMT</pubDate>
    <dc:creator>Lesley</dc:creator>
    <dc:date>2026-08-05T13:32:41Z</dc:date>
    <item>
      <title>Identity Collector server change from Windows 2022 to Windows 2025</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280766#M46663</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need to upgrade a Windows server from 2022 to 2025. This server is Identity Collector.&lt;/P&gt;&lt;P&gt;Is it possible to backup the Config file and reimport it on the new server?&lt;/P&gt;&lt;P&gt;Are there some requirements regarding server name? does it require to have the same name as the former?&lt;/P&gt;&lt;P&gt;Or do we need to start from scratch ?&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2026 09:35:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280766#M46663</guid>
      <dc:creator>DR_74</dc:creator>
      <dc:date>2026-08-05T09:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Collector server change from Windows 2022 to Windows 2025</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280780#M46664</link>
      <description>&lt;P&gt;The gateways connect on IP basis with certificate. I would spin up new 2025 server, install latest IDC software. Export config from old system and import it:&amp;nbsp;&lt;A href="https://sc1.checkpoint.com/documents/Identity_Awareness_Clients_Admin_Guide/Content/Topics-IA-Clients-AG/Identity-Collector-Updating.htm?Highlight=export" target="_blank"&gt;https://sc1.checkpoint.com/documents/Identity_Awareness_Clients_Admin_Guide/Content/Topics-IA-Clients-AG/Identity-Collector-Updating.htm?Highlight=export&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Then add the new server to the gateway object in Smart Console.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Alternative you can install new 2025 with same IP, import config and turn off old server. But this is more risky because you lose the old server. With the first plan you can build the new one and take all the time you need. Would recommend to build 2 IDC servers on 2025 if one breaks down or you need to run windows update there is one left.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Server name is not relevant.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2026 13:32:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280780#M46664</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2026-08-05T13:32:41Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Collector server change from Windows 2022 to Windows 2025</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280781#M46665</link>
      <description>&lt;P&gt;Ultimately, it's as if I'm adding another server as a backup for the first one.&lt;/P&gt;&lt;P&gt;However, even if I import the configuration, do I still need to set up the certificate and trust relationship with the gateway for this new IdC?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2026 13:41:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280781#M46665</guid>
      <dc:creator>DR_74</dc:creator>
      <dc:date>2026-08-05T13:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Collector server change from Windows 2022 to Windows 2025</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280784#M46666</link>
      <description>&lt;P&gt;I am not sure about this part if the config export file takes the key and will trust the certificate.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2026 13:49:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Identity-Collector-server-change-from-Windows-2022-to-Windows/m-p/280784#M46666</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2026-08-05T13:49:45Z</dc:date>
    </item>
  </channel>
</rss>

