Synergetic Deployment Tool (SDT)
SDT can be used by clients in all Test and Production environments where a hand over has occurred.
We can provide priority phone support where there has no booking between the hours of 9am-5pm AEST. Please ask to speak with one of our Systems Specialists.
We are happy to conduct the upgrade for you, so if required please book here.
If you have not yet had a hand over please include this in the notes section when you next book.
Pre-requisites
Have SDT installed in an environment
If running SDT from a Jump Server that has not previously been used for this purpose, you will need to install the Database Patcher runtimes: V68_20170505DBPatcherRuntimesInstaller-SQL2016.exe Request this from Education Horizons via a support case
Have a login to the SDT application
Request this from Education Horizons via a support caseBe user in the Synergetic Upgrades AD group with the account used to sign into the computer
Your school-based IT team can do thisRead this document!
We recommend setting a System Message to avoid users being in the application during an upgrade.
Please refer to How to set a system message
Legacy Location (Deprecated)
Where do I find the Synergetic SDT?
Go to the server wherever the SDT tool was configured (usually SQL server)
C: Drive > SDT > Synergetic.Application.SDT.exe
You will not be able to log into the SDT from this location anymore
Please follow the link to find more information and download the latest version of SDT ( Under files on top right) Self Deployment Tool - Requirements (synergetic.net.au)
New Location
Go to the server wherever the SDT tool was configured (usually SQL server)
There should a desktop icon. If not you can find the application here: C: Drive > Program Files > SDT > Synergetic.Application.SDT
How to update the SDT tool whenever the new build of SDT released
Run the SDT tool whenever we release a new build of SDT tool it automatically comes with the pop up when we run the tool.
Click Yes > Next > select Everyone instead of only me > Next
Done installation completed
Login
Go to desktop open SDT ( no need to run as admin as moving forward)
Enter your Username and Password provided.
If you do not have credentials, or there is staff movement, please contact us for additional credentials to log into the tool.
Commence Upgrade
On the left hand there are Environments which are usually ‘Test’, ‘Dev’ and ‘Production’, though you may also have other environments in use at your organization.
Select which environment that you want to do the upgrade on.
Make sure you select the correct environment that you want to upgrade
Click Check Health in the middle. It will check all the files locations and permissions on those.
Wait until Jobs in progress reduces to 0 confirming that all products are ready to be upgraded.
If there are any issues here please raise a case in the help portal.Click on View releases on the right hand side.
During check health the Command Prompt pop up you can minimize this don’t close it
You will be offered a list of available versions.
Simply highlight the version you would like to install, tick the check box ‘I have verified…’ then click Apply.
The SDT will download the product packages.
Once complete these will begin deploying.
When all packages have installed with no error the upgrade is complete.
Make sure your Service suite is stopped during the upgrade process (you will be prompted for this before the upgrade will commence).
You will have to start and stop manually before and after the upgrade process.
The Database Patcher will commence installation first.
Progress bar
Once the upgrade has completed, the Release and Last Updated information will automatically update to reflect this, and concludes the upgrade process.
Troubleshooting Q&A
Q. Sometimes the check health fails on certain products
A. If the check health still comes failed it means it missing some value of the products or it haven’t been configured in that case you can call support where we can join you and help you in the process, or log a case.
Q. The process stalls at the Database Patcher
A. You can check the database patcher is working by going to the working path and see if the PatchLog folder has been created. PatchLog is the folder where all the logs files are stored.
If it created and there is still an issue, contact us for assistance.
Q. Windows Application update failure
All the products have successfully updated other than the Windows client. This usually fails when somebody has the executable open during the upgrade process.
A. Make sure everybody out from the systems during the upgrade.
One way to do is go to your Windows right click > go to computer management > Shared folder > open files and close any Synergetic files that are in use.
Following this, untick all the other products in the SDT other than the Windows client.
Q. I get a error pop up at the end of the upgrade “Object reference not set to an instance of an object”
A. We have a minor bug in the tool which comes at end of the upgrade process or when it finish with the upgrade it just a pop with a dialog which says object reference when you came across this issue don’t worry about it.
It's just trying to start the service suite automatically which you will need to do manually.
Q. When I run the SDT application getting this error “Synergetic. Updater. Application. SDT has stopped working”
This may be happens sometime when you run the SDT application exe but, it giving you the error something like Windows cannot access the specified device, path or A problem caused the program to stopped working correctly.
Reason: It happens when there is a some kind of protection or antivirus running in the server or in the background which blocking the SDT for execution.
Resolutions:
Antivirus can be turned off during the upgrade process then turning back on after the upgrade process is finish which seems to be one of the resolution for this kind of errors.
SDT tool can be run from different server but same thing applicable needed the antivirus need to be turnoff. If there is no antivirus in the other server there will no issue you will encounter, but the condition is that the SDT file application should be in that server.