# data[].attributes.body
Except some small hiccups

# data[].attributes.body
Need Less Resources in office on Release day

# data[].attributes.headline
Dry run environment DB set up was not proper

# data[].attributes.subject
Dry run environment DB set up was not proper

# data[].attributes.body
Dry run failed first time as Ethil dry run environment DB set up was not proper.TOWER\domain users not removed.

# data[].attributes.body
Second time for Dry run fail, as ETHIL_Archive DB not refreshed

# data[].attributes.body
Quick solution for Dry run , when it fail second time

# data[].attributes.headline
Initial thoughts it will take 2 days to setup the dry run was not correct 

# data[].attributes.subject
Initial thoughts it will take 2 days to setup the dry run was not correct 

# data[].attributes.body
Lavan initial thoughts it will take 2 days to setup the dry run for the ETHIL system. But as per Anshuman Actually Dinesh was doing the set up previously.  Why there is confusion ?

# data[].attributes.body
Anshuman found command prompt and several other folders open in Prod copy environment.

Hence He restarted Ethil prod copy server and clicked on Try Again button in Octopus, this time deployment on Ethil Prod copy was successful.

# data[].attributes.body
Links in EmailInfopack and quotepacks   for COP  is not working. why we have to do this and how can we avoid this in future

# data[].attributes.body
When turning replication back on the “read committed snapshot” is True, this needs to be followed up by Dinesh

# data[].attributes.body
Communication – Went out in a timely manner but instructed users to re-install Ethil when it shouldn’t be necessary. Similar to last release there were a number of incidents logged for “Ethil error: CacheManager” which was thought to be due to systems not being closed down prior to release.

Future comms will advise users to turn off their machines prior to leaving work on Friday/Saturday and that following the release Ethil & Ilsa should be immediately available. However if users do have difficult accessing the system it is available to be installed in InstallIT. Jill to follow up with Service Desk

Specific details of changes being implemented are provided to the business in the scope confirmation provided by Anil. They are not needed to be included in the release comms.

# data[].attributes.body
Many of the specifications were incomplete, eg All packs with underwriting did not mean all packs with underwriting, all letters did not mean all letters

# data[].attributes.body
This XML contains the underwriting even though letter does not use it. This was therefore out-of-scope to avoid testing, but we had to test that it did not change.

# data[].attributes.body
Was nice to see that both the release on Sat and the Tax letters on Sun went without any errors, thumbs up to whoever worked both days.

# data[].attributes.body
What happens if Anshuman is not available?

# data[].attributes.body
Upgrade of the applications in the Citrix environment went well for 175+ user desktops (Manila + Cape Town + India users) and also for Melbourne Citrix application users.

# data[].attributes.body
ILSA's replication to reporting is not very good, and in cases like this release (where new data was inserted to non-replicated tables) there should be a separate step to create a reporting environment release (maybe).

# data[].attributes.body
This was not communicated well.

# data[].attributes.body
Create new KT for Dry run Database - DN

# data[].attributes.body
Add the EthIL_Archive database to the list of DBs to be restored
- DN

# data[].attributes.body
Prod Copy server had folders and command prompt open and caused the Prod copy deployment to fail. Update team to use server and then log off - AS

# data[].attributes.headline
What percentage of hosts were not able to have the client pushed?

# data[].attributes.subject
What percentage of hosts were not able to have the client pushed?

# data[].attributes.body
Need to confirm the desktop process – What percentage of hosts were not able to have the client pushed? What is causing the update to be unsuccessful for some?

Is the old version of Ethil/Ilsa being turned off before the new version is being turned on in each environment? NagaRaju & Abhijit

# data[].attributes.body
Investigate what scripts are run to set the read committed value on the databases - DN and TH

# data[].attributes.body
Anshuman is the only one who can do the release. This is too risky. Handover to more resources.
- AS and TH

# data[].attributes.body
Determine what tables need replication and update the PK to enable it. - DN and AS (and PJ)