I guess this is more of an FYI than anything as I have already resolved the issue(s). We have 2 different SEPM environments. Yesterday, I upgraded both to 14.2.0 MP1. One did not encounter this issue. For one (the second environment I upgraded), I could no longer log onto the SEPM using an AD account after the upgrade. Luckily we have a local account we can log on with as a backup. For some reason after the upgrade, the check box to "Use Secure Connection" had become checked under the Directory Server General configuration tab. I was able to uncheck the option using a local account which resolved the issue for AD accounts. Prior to that the accounts would become locked out in trying to resolve.
Upgrades have become problematic for us since the version 14 releases. I have had 3 issues during upgrades, where I never used to have issues in the past (v11.x-v12.x). During our last upgrade, one of the tables had the user name appended to the front of all of the table names in the database, making the environment inacessible until I resolved that issue with our DBA's assistance. On our SEPM environment that did not have the AD issue yesterday, one of the servers in that environement (there are 2, the first went fine) wanted to repair or uninstall instead of upgrading. I had to do the repair twice, at which point it would fail when trying to connect to the DB as the other server had already been upgrades so it now saw a version difference. After running the repair a second time it followed through with the upgrade process. This was not the same environment that had the DB or AD issue. Never used to have to worry about this, but now I'll be on high alert awaiting issues during upgrades.