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. 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. I have had 3 issues during upgrades, where I never used to have issues in the past (). Upgrades have become problematic for us since the version 14 releases. Prior to that the accounts would become locked out in trying to resolve. I was able to uncheck the option using a local account which resolved the issue for AD accounts. For some reason after the upgrade, the check box to "Use Secure Connection" had become checked under the Directory Server General configuration tab. Luckily we have a local account we can log on with as a backup. For one (the second environment I upgraded), I could no longer log onto the SEPM using an AD account after the upgrade. Yesterday, I upgraded both to 14.2.0 MP1. I guess this is more of an FYI than anything as I have already resolved the issue(s). I do not need a solution (just sharing information)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |