Subcategories

• General

  General FOG related questions.
  2.1k
  Topics
  15.6k
  Posts

  J

  I am in the process of migrating my old fog master server to a new master server.

  Old fog server version 1.5.10.1660
  new fog server version 1.5.10.1667

  This server is the master server for 25 remote sites each having their own storage node. We installed the fog client on the remote hosts to use the DNS name for the server dc-fog-el. Currently it is in use for the old server but I would like to repurpose it for the new one that has a different IP address. Reading the wiki page for Migrating fog and for Maintain Control Of Hosts When Building New Server I have a question about this process. When migrating the SSL folder from /opt/fog/snapins, it contains files that have the old servers IP address. The wiki says to transfer the SSL folder to the new server and re-install fog. Even though the two servers have different IPs and the fog client is using the domain name for the old server, will the new server maintain control of the existing hosts during this process if I migrate the domain name to the new server?

  My goal in all of this is to prevent a lot of headache and work for our tech support team to have to reinstall the fog client on over hundreds of computers. I am working on migrating the database over to the new server. I know there were some config files for mysql/mariadb and php I needed to change and increase the memory and connection limit sizes.

  Any help with understanding this migration would be much appreciated!

• Tutorials

  Share your knowledge
  340
  Topics
  2.9k
  Posts

  D

  @george1421 Thanks for your help.

  I solve the problem with this AutoUnatted.xml

  <?xml version=“1.0” encoding=“utf-8”?>
  <unattend xmlns=“urn:schemas-microsoft-com:unattend”>
  <!-- Bypass OOBE -->
  <settings pass=“oobeSystem”>
  <component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
  <OOBE>
  <HideEULAPage>true</HideEULAPage>
  <HideLocalAccountScreen>true</HideLocalAccountScreen>
  <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
  <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
  <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
  <ProtectYourPC>3</ProtectYourPC>
  <SkipUserOOBE>true</SkipUserOOBE>
  <SkipMachineOOBE>true</SkipMachineOOBE>
  <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
  <NetworkLocation>Other</NetworkLocation>
  </OOBE>
  </component>
  <component name=“Microsoft-Windows-International-Core” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
  <SystemLocale>pt-PT</SystemLocale>
  <UILanguage>pt-PT</UILanguage>
  <UserLocale>pt-PT</UserLocale>
  <InputLocale>0816:00000816</InputLocale>
  </component>
  </settings>

  <!-- Run SetupComplete.cmd via PostOOBE --> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>reg add "HKEY_LOCAL_MACHINE\SYSTEM\Setup\FirstBoot\PostOobe" /v "00" /t REG_SZ /d "cmd /c C:\Windows\Setup\Scripts\SetupComplete.cmd &amp; exit /b 0" /f</Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings>

  </unattend>

  The AutoUnatted.xml will call the the script C:\Windows\Setup\Scripts\SetupComplete.cmd

  I make the sysprep with AutoUnatted.xml