tag:blogger.com,1999:blog-62687483129304921.post12155855356491354..comments2024-03-28T13:13:53.318+01:00Comments on ADdict: FIM: Calling FIM Automation cmdlets from within a PowerShell ActivityThomashttp://www.blogger.com/profile/12651864373303201993noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-62687483129304921.post-70926627274036790462013-03-24T10:19:59.496+01:002013-03-24T10:19:59.496+01:00Yup, in order for this to work you need to make su...Yup, in order for this to work you need to make sure the FIM Service account is a valid portal user account. It has to be known with it's domain, SID and username in the Portal. You can either do this by flowing the information from Active Directory, or by just creating it in the Portal your self. As far as the SID part is concerned there are some powershell scripts which can take care of this for you. The FIM ScriptBox definately has these.Thomashttps://www.blogger.com/profile/12651864373303201993noreply@blogger.comtag:blogger.com,1999:blog-62687483129304921.post-8798753981274637412013-03-15T07:43:53.444+01:002013-03-15T07:43:53.444+01:00Hi, I have the same setup as you, and am getting t...Hi, I have the same setup as you, and am getting the error: GetCurrentUserFromSecurityIdentifier: No such user DEMO\s_fim_service, S-1-5-21-527237240-xxxxxxxxxx-839522115-10842<br /><br />But I do not understand your fix for it...do you mean to say that for this to work, we have to export the FIMService account to the FIM Portal?<br /><br />thank youAnonymousnoreply@blogger.com