What problems is this going to cause?
Without knowing your environment, it's going to be hard to tell you with full certainty (I don't know how you use the software. Is it only for authentication? How many users? How many servers? Are there any filers? Do you have a sense of how large the new environment is? Note that if it's an acquiring company there is a new namespace and possibly a new naming convention (joedoe vs. joe.doe) . Are the constraints of this freemium product the right thing for you? Are you subject to any regulation (e.g. SOx, PCI, HIPAA, etc)?
See what I mean?
The main problem you're going to have was outlined in my original response - your namespace is going to change and your UID/GID numbers will change. This can be from an ' annoying users/chown fest' exercise to an 'application down/ceo is breathing over my shoulder' exercise (this depends on how many critical servers use the software and the different ways to use it. E.g. you could have a Kerberos key table that is key for a Java app to run that is critical for your business).
I assume they will have different id and not have permission on their files/directories. But once they login and I see what they new ids are then I can change the files/directories to their new accounts.
Yes you can. The most common issue is that you are able to log in, but not change directories to your home folder.
However, it's also possible that you have an NFS server with multi-terabyte files belonging to key project owners.
I've downloaded the new version as suggested. When I run it will it overwrite the old settings or will it just give me the option to add the additional domain?
Depending on how old the version of the software is, you may or may not be able to upgrade in place. Reasoning:
- 32-bit operating systems are no longer supported
- as part of the normal lifecycle, your operating system may no longer be supported by the express version you downloaded (e.g. AIX 6.x)
- In the winter of 2016 with the 2017 release, the packaging of the software changed significantly. We split cURL, OpenSSL and OpenLDAP from the main installer.
The answer to the behavior depends on the bullet points above. If you kept your software up to date, this will be as simple as 'yum update CentrifyDC' or as painful as a uninstall/reinstall * n servers.