Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migraging NCPA Configs When Upgrading from NCPA 2.X to 3.X on WIndows #1097

Closed
shoreypu opened this issue Jan 24, 2024 · 11 comments
Closed

Migraging NCPA Configs When Upgrading from NCPA 2.X to 3.X on WIndows #1097

shoreypu opened this issue Jan 24, 2024 · 11 comments
Labels
3.X.X close pending Enhancement

Comments

@shoreypu
Copy link

When attempting to upgrade from NCPA 2.4 to 3.0.1 in Windows, the new agent no longer has any of the config files from the old agent. NCPA 2.X is 32-bit and installs to C:\Program Files (x86)... and 3.x is 64-bit and installs to C:\Program Files... The config from C:\Program Files (x86)... is not copied over to C:\Program Files....

Is there a way to copy over the config files as part of the upgrade?

Thanks
@bramassendorp
Copy link

bramassendorp commented Jan 24, 2024 via email

@shoreypu
Copy link
Author

I kind of implied that with config files, but probably should have spelled that out as well. Basically, this is a new, un-configured, agent.

@MrPippin66
Copy link

I would agree this is a pretty serious problem. We've yet to deploy/upgrade from V2 to V3 for Windows and this will cause a lot of headaches.

@shoreypu
Copy link
Author

shoreypu commented Feb 2, 2024

I would agree this is a pretty serious problem. We've yet to deploy/upgrade from V2 to V3 for Windows and this will cause a lot of headaches.

I've run some tests and it looks like you can copy over the files prior to upgrading, which will not be overwritten. However, I also noticed some differences in the ncpa.cfg files, that I am still reviewing. The standard set of NCPA checks we run work, but I'm not sure if there are any caveats to running with the old config. Guidance would definitely be helpful.

@MrPippin66
Copy link

Regardless, there should be an "upgrade" part of the installation that detects a 32-bit previous installation which does all the requisite migration steps.

@ne-bbahn
Copy link
Contributor

I need to verify that there are no differences in configuration that would cause things to break if someone upgrades, but as long as that's not an issue, I'll have the NSIS script copy over the old configs to the new location.

@MrPippin66
Copy link

Okay, but just to be clear, that really should be the entire current contents of the existing 32bit location (minus the files the upgrade would installing)

@ne-bbahn
Copy link
Contributor

Okay, but just to be clear, that really should be the entire current contents of the existing 32bit location (minus the files the upgrade would installing)

I believe it should copy the contents of the etc, plugins and var folders. If you think anything else should be copied over, let me know.

@MrPippin66
Copy link

MrPippin66 commented Feb 28, 2024 via email

@ne-bbahn
Copy link
Contributor

ne-bbahn commented Apr 2, 2024

This will be included in NCPA 3.1.0

@MrPippin66
Copy link

And tentative schedule for this release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.X.X close pending Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@shoreypu @bramassendorp @MrPippin66 @ne-bbahn