tag:blogger.com,1999:blog-62687483129304921.post9026689494538498324..comments2024-03-28T13:13:53.318+01:00Comments on ADdict: Recovering or Installing an additional FIM Service instance when using Update 1Thomashttp://www.blogger.com/profile/12651864373303201993noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-62687483129304921.post-41426030434959334222012-01-17T06:11:00.847+01:002012-01-17T06:11:00.847+01:00Thomas,
Good article. I love the graphical approac...Thomas,<br />Good article. I love the graphical approach to showing the problem. The article raises the problem that some have not encountered (restoring a service instance after updates are applied) and one of the pitfalls (the Agent jobs). I do want to caution you against the use of the term TEMP DB as in "continue updating the TEMP DB" as some might get confused with the actual tempdb (one of the system databases). In my opinion it is easier to install the FIM Server with it pointing at an entirely separate SQL Server, do the patching, and then edit the registry. Then you do need to drop the database on the separate SQL Server and the jobs.David Lundellhttps://www.blogger.com/profile/17202883653808140101noreply@blogger.com