Uninstalling clients hosted on NEOSYS Server: Difference between revisions
m (Added instructions to include admin when sending the FYI emails regarding disabling or deletion.) |
|||
| Line 1: | Line 1: | ||
This must be done in the following circumstances: | This must be done in the following circumstances: | ||
# Reinstallation on other servers | #Reinstallation on other servers | ||
# Reinstallation on clients own server | #Reinstallation on clients own server | ||
# Termination of contract | #Termination of contract | ||
# Any other reason | #Any other reason | ||
NEOSYS needs to: | NEOSYS needs to: | ||
# Ensure that the installations can no longer be used by accident or design | #Ensure that the installations can no longer be used by accident or design. | ||
# Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances | #Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances. | ||
==== Stage 1. Disabling ==== | Include admin@neosys.com when sending emails regarding this subject. | ||
====Stage 1. Disabling==== | |||
1. Ensure that the NEOSYS processes, for the installation that is being moved, have been shut down. This includes checking that no ntvdm process is running for the installation being moved, in procexp.exe (Find, Handle, D:) | 1. Ensure that the NEOSYS processes, for the installation that is being moved, have been shut down. This includes checking that no ntvdm process is running for the installation being moved, in procexp.exe (Find, Handle, D:) | ||
2. Stop the associated web in IIS | 2. Stop the associated web in IIS. | ||
3. Edit the process startup cmd file, which is scheduled to run daily in the task scheduler and comment out the stopped installation from it | 3. Edit the process startup cmd file, which is scheduled to run daily in the task scheduler and comment out the stopped installation from it. | ||
4. Do not amend the client folder name or location, leave the client folder name as it is. | 4. Do not amend the client folder name or location, leave the client folder name as it is. | ||
| Line 25: | Line 27: | ||
5. Retain a copy of the latest backup.zip file as mentioned in [[Backup_and_Restore#Historical.2FLapsed_Clients.3F| Handling backup for historical clients]] | 5. Retain a copy of the latest backup.zip file as mentioned in [[Backup_and_Restore#Historical.2FLapsed_Clients.3F| Handling backup for historical clients]] | ||
6. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it (edit: genclients.sh) | 6. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it. (edit: genclients.sh) | ||
7. Strike-through the terminated client's link on support home page (support.htm). | 7. Strike-through the terminated client's link on support home page (support.htm). | ||
==== Stage 2. Permanent Deletion ==== | ====Stage 2. Permanent Deletion==== | ||
Any installation found in the hosts\OLD folder which is older than one year may be deleted to free up storage and backup resources as follows: | Any installation found in the hosts\OLD folder which is older than one year may be deleted to free up storage and backup resources as follows: | ||
1. Delete the associated web in IIS | 1. Delete the associated web in IIS. | ||
2. Delete the associated folders in hosts folder | 2. Delete the associated folders in hosts folder. | ||
3. Remove the terminated client's link from support home page (support.htm). | 3. Remove the terminated client's link from support home page (support.htm). | ||
4. Delete the associated entry from Zone Edit. | 4. Delete the associated entry from Zone Edit. | ||
Revision as of 10:12, 12 January 2020
This must be done in the following circumstances:
- Reinstallation on other servers
- Reinstallation on clients own server
- Termination of contract
- Any other reason
NEOSYS needs to:
- Ensure that the installations can no longer be used by accident or design.
- Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances.
Include admin@neosys.com when sending emails regarding this subject.
Stage 1. Disabling
1. Ensure that the NEOSYS processes, for the installation that is being moved, have been shut down. This includes checking that no ntvdm process is running for the installation being moved, in procexp.exe (Find, Handle, D:)
2. Stop the associated web in IIS.
3. Edit the process startup cmd file, which is scheduled to run daily in the task scheduler and comment out the stopped installation from it.
4. Do not amend the client folder name or location, leave the client folder name as it is.
The old procedure to Capitalise the client folder name or MOVING this folder to the "OLD" folder leads to backups doubling up on capacity on the backup server as the historical snapshots retain the old folders on the backup server. Hence, these procedures must be stopped.
5. Retain a copy of the latest backup.zip file as mentioned in Handling backup for historical clients
6. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it. (edit: genclients.sh)
7. Strike-through the terminated client's link on support home page (support.htm).
Stage 2. Permanent Deletion
Any installation found in the hosts\OLD folder which is older than one year may be deleted to free up storage and backup resources as follows:
1. Delete the associated web in IIS.
2. Delete the associated folders in hosts folder.
3. Remove the terminated client's link from support home page (support.htm).
4. Delete the associated entry from Zone Edit.
