Sort of. Trying to do this via just SMO and powershell was immensely frustrating when dealing with the remotelogin security. What I wanted the login to do was to use a sql login no matter the context (the bottom-most radio button in the screenshot below).

Alas, every time I set the remotelogin property and called the SetRemotePassword() method it would automatically add it to the Local server login to remote server login mappings list.

Not what I want. In order to determine the proper…properties to set I created a new linked server and scripted it out to have a gander at the properties.

Two properties stood out. The @locallogin and the @useself. Okay, cool. Easy enough, the smo linkedserverlogin has a properties collection in it, should be easy enough to set. Except, the bloody properties never get populated. Even after calling the Initialize($true) on the LinkedServerLogin smo object, said properties are not there.

Okay, let’s add them. Nope. There is no Add() method on the SqlPropertyCollection (or on the smo PropertyCollection inherited class). In the end, I ended up just having to execute a sql call in order to get this to work, as I’d already spent 4 stinking hours trying to get this to work correctly. I detest having to resort to doing this, but I HAVE to move on.

Here it is. If you have this figured, please please let me know what the poop is.