Migrating tool from SG to XG

Be warry of doing this:

Doing an 9.5 SG as a trail (quicker to deply) and installed an XG (converting the SG).  Then converting it in the SG to XG converter deloys some unexpected things.  The Default certificate, which is bank on the XG and needs to be filled out in order to log into the client portal is prefilled (from the trial) and has Sophos Head Office address default details.  Once installed onsite no one can VPN to the Converted SG to XG site as these details are wrong.  You have to filled the defualt cetetificate properly -- then regenerate it.  (I think the regeneration here is thing really needed). Then regenerate your VPN client configuration.  Then the SG to XG issues resolve them selves.

In other words check the default Certificate and fill it out right before configuring anything else.  then regenerate it and add to the clients.

Fixed the cloning issue we had.  Thus far we converted UTM9.5 to XG17.1Mr2.  This might need to become another string but this is how this was fixed.  The client firewalls were 135W.  We used a XG135W in our lab to build the client's firewall from the Convert file from the UTM 9.5--> 17.   What I did not do was clear the Synchronized Security tic from the previous build on the First Test XG 135W Build.  So my test router had Syncronized Securty when I restored the client build to it from the converter.  Every 125W and 135W there after we could not get Synchronized Security to work (once deployed).  Raised a ticket with Sophos.  They advised rebooting to fix, which did not fix.  They peered into one machine on SSH and found the cloned device, running in the clients site, stated it was registered.  In the Gui it was not. 

I restored the Source XG135W to the time when it was Registered for Syncronized Security.  Made sure it was on the Internet and could be seen from Sophos Central. 

• I purged the registration.
• Deleted that Firewall from Sophos Central (where it was registered).
• Rebooted it. 
• I restored every configuration from each client site Firewall which had the "failure to regiester Syncronized Security" error to the orginal test XG Firewall Device. 
• Exposed it to the Internet in RAW form when booted (rebooted to get a green tick). 
• After about 10 minutes I turned the Test XG Firewall Off. 
• Went to the client's firewall and was able to register the device with Sychronized Security.
• Repeated with each client with issue with success.

Lesson:  Dont clone a XG Firewall without clearing the registration. 

Fixed the cloning issue we had.  Thus far we converted UTM9.5 to XG17.1Mr2.  This might need to become another string but this is how this was fixed.  The client firewalls were 135W.  We used a XG135W in our lab to build the client's firewall from the Convert file from the UTM 9.5--> 17.   What I did not do was clear the Synchronized Security tic from the previous build on the First Test XG 135W Build.  So my test router had Syncronized Securty when I restored the client build to it from the converter.  Every 125W and 135W there after we could not get Synchronized Security to work (once deployed).  Raised a ticket with Sophos.  They advised rebooting to fix, which did not fix.  They peered into one machine on SSH and found the cloned device, running in the clients site, stated it was registered.  In the Gui it was not. 

I restored the Source XG135W to the time when it was Registered for Syncronized Security.  Made sure it was on the Internet and could be seen from Sophos Central. 

• I purged the registration.
• Deleted that Firewall from Sophos Central (where it was registered).
• Rebooted it. 
• I restored every configuration from each client site Firewall which had the "failure to regiester Syncronized Security" error to the orginal test XG Firewall Device. 
• Exposed it to the Internet in RAW form when booted (rebooted to get a green tick). 
• After about 10 minutes I turned the Test XG Firewall Off. 
• Went to the client's firewall and was able to register the device with Sychronized Security.
• Repeated with each client with issue with success.

Lesson:  Dont clone a XG Firewall without clearing the registration.