- 2 minutes to read
Step 14: Post Migration Tasks
🏁 Your Nodinite environment now runs v7. Use this page to confirm the migration, then follow the standard post-installation steps to secure and maintain the environment.
Prerequisites
- Step 13 completed – Old files and folders cleaned up
- All v7 services running and tested
Migration Completion Checklist
- Test thoroughly – the Logging Service, the Monitoring Service, and alerting through the Alarm Plugins work end to end
- Review the Log Databases – open Log Databases and run the Update Log Database wizard if a schema update is available (step 15 of the Migration Guide)
- Update documentation – record the new URLs, per-service ports, and configuration details
- Train users – share the new Web Client URL and relevant UI changes
- Monitor – review AI Diagnostics and the Log Audits for errors and warnings
Post-Installation Steps
The standard Post-Installation Steps guide keeps your environment healthy:
- Configure antivirus exclusions for IIS and Nodinite folders
- Monitor disk usage to prevent downtime
- Back up the SQL Server databases
- Tune SQL Server performance for your workload
- Harden the environment: TLS, SQL encryption, and authentication
- Review Service Principal Names (SPN) for any IIS or SQL service-account changes made during the migration
- Follow the monthly update cadence with Update Nodinite v7
Tip
Many of these may already be in place from v6. Review them for the v7 IIS-based architecture; for example, the IIS application pool identities may now need antivirus exclusions.
Future Enhancements
- Group Managed Service Accounts (gMSA) – automated password management for service identities, including the IIS application pools. If you change identities, check SPN again before users return to Windows authentication.
- OAuth 2.0 / OpenID Connect – modern single sign-on. Requires HTTPS (Step 10); switch with Migrate Authentication Method.
Contact your Partner or read the Support page for guidance on these features.