Migrating to 0.4.0

In general it is not recommended for most people. This is because the automated migration tools could have bugs and thus you end up with a badly migrate solution. The recommended approach is to keep the old config for now unless you want to verify your migration manually.

Migrating to ini

Migrating is very simple all you need to do is:

nscp settings --migrate-to ini

What this will do is:

1. Read the "old" configuration (and convert it in-line)
2. Write the new configuration (ini)
3. Switch your context to the new configuration (modify boot.ini).

Migrating to registry

Migrating is very simple all you need to do is:

nscp settings --migrate-to registry

What this will do is:

1. Read the "old" configuration (and convert it in-line)
2. Write the new configuration (regitry)
3. Switch your context to the new configuration (modify boot.ini).

Reverting to old

If you which to revert your configuration you can easily do:

nscp settings --switch old

What this will do is:

1. Switch your context to the old configuration (modify boot.ini).

Verifying your configuration

After migrating (to ini) you can easily verify your configuration by opening nsclient.ini and verify that all key you need are there. Note that some things have shifted around so for instance what was previously NSCAAgent.dll will no be both Scheduler as well as NSCAClient as both modules are required. There might also be some keys which are no longer supported as well as some keys which are not working and/or is not migrated properly. After migrating and verifying the config please report any issues so I can add them.

After verifying the config start the agent and verify that everything works (again some keys might migrate properly but there could be bugs and other issues in the actual program as well.) Again it is important to report all these to me so I can add support for them.