Salvador Manzo <[EMAIL PROTECTED]> wrote on 04/17/2008 04:55:56 PM: > I see no one has responded yet. > Look up sp_help_revlogin on the MS site > It?s a stored procedure you install on the Source server that > extracts usernames, encrypted passwords and SID information, which > you then run against the destination sever.
Thanks so much; I'll look into it. Turns out, you can have LANDesk tell you what the database username and password is, that it is using: https://coreserver/landesk/managementsuite/core/ssl/information/DatabaseInformation.asmx?op=GetConnectionString You have to run that on the Core server. I did find the sp you mentioned above, but luckily did not need it. Thanks > > > On 4/17/08 7:33 AM, "[EMAIL PROTECTED]" <Michael. > [EMAIL PROTECTED]> wrote: > > So we use LANDesk here, configured so that we have a core server, > and a separate (SQL2000) database server. Now, I need to upgrade > *just* the database server to SQL2005. I have a forum post that > tells me how to do that (surprisingly easy, if it works ...). > However, what I need to do is have the same SQL user defined on the > new database server. The user is just a SQL user (i.e., the "Logins" > list it just as "LD", not "domain\LD". > > And, of course, no one can find the documentation for what that > password is. <SIGH> > > So what I need is some way to find that password, if I can, and it > when creating the new user on the new SQL2005 server, so that when > LANDesk goes to access it using it's current credentials, it should > Just Work. I realize I could change the current password in SQL (and > in LANDesk svccfg), but I don't want to take a chance on breaking > the currently working system. If it doesn't work after I point > LANDesk at it's new db server, I can just re-point back at the old > server, without having to mess with any other settings. > > SO ... has anybody done something similar (i.e., upgrade *just* a > LANDesk database server to a new version)? Or know of some way to > either recover the SQL user's password, or - failing that - perhaps > port all the current SQL2000 users and passwords to the new SQL2005 server? > > (as you can tell, I know very little about SQL. Outside of backing > up/restoring databases, and creating users, I start to get confused ....) > > Thanks > > ----- > Salvador Manzo [ 620 W. 35th St - Los Angeles, CA 90089 e. [EMAIL PROTECTED] ] > Auxiliary Services IT, Datacenter > University of Southern California > 818-612-5112 > An avidity to punish is always dangerous to liberty. It leads men to > stretch, to misinterpret, and to misapply even the best of laws. He > that would make his own liberty secure must guard even his enemy > from oppression; for if he violates this duty he establishes a > precedent that will reach to himself. > Thomas Paine, "Dissertation on First Principles of Government" > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
