This is potentially a complicted issue that may be hard to fix. You rightfully worry about the potential damage to your deployment eventhough it is not obvious at the moment. It may bite you at some point in the future. Murphy knows no mercy. Best approach in terms of risk management is to start over.
If yu want a more surgical approach then a good place to start your assesment is by inspecting the log files of the deployment wizard and the installation logs themselves. The first are in your personal C:\Users\<username>\AppData\Local\SAS\SASDeploymentWizard directory. The latter are in <SASHome>\InstallMisc\InstallLogs.
The deployment process is divided in two phases: install and configure. As the install was completed a reconfigure would be sufficient. From what you describe I would personally not take the chance and do at least that in any case. Erase the existing config using the deployment wizard. If that fails you know enough: redo the whole damn process.
Also a question to be answered: why did the server shutdown in the first place? You do not want that to happen again.
Hope this helps,
- Jan.