Create an Integration Services package and schedule it to run daily/weekly, depending how often you add/remove logins. There is a "Transfer Logins Task" where you can select the logins that would have to be transferred along with some conditions; it's important to set "copySids" to True.Good luck

We tend to use the method specified in the Microsoft KB article. We also script out the logins and store it in a location that gets backed up to tape (which is then stored off-site) for disaster recovery situations.

Preet (6/16/2008)Deepak's link will give you what you want. Its been improved since I last needed it. Default databases etc. The key thing is the copying of the SIDs.

This is a good point. The Microsoft scripts do ensure the SID is carried over. This is important because that's how the login maps into the database as a user. Without using the Microsoft scripts, you'd have to run sp_change_users_login to reconcile whenever you had to switch-over to the standby system.