{"id":281,"date":"2009-01-14T10:18:38","date_gmt":"2009-01-14T10:18:38","guid":{"rendered":"https:\/\/www.wapshere.com\/missmiis\/?p=281"},"modified":"2009-11-18T08:35:35","modified_gmt":"2009-11-18T08:35:35","slug":"ilm-2-rc0-part-1-installation","status":"publish","type":"post","link":"https:\/\/www.wapshere.com\/missmiis\/ilm-2-rc0-part-1-installation","title":{"rendered":"ILM “2” RC0 Part 1 – Installation"},"content":{"rendered":"

So,\u00c2\u00a0 I have a bit of time this week while the year gets started, and thought I would spend it playing with the\u00c2\u00a0latest evaluation\u00c2\u00a0version of ILM “2”<\/a>. I hope to upgrade my company’s system at some point, so my first plan is to see if I can import the existing ILM 2007\u00c2\u00a0database into it – but before I can get there, I obviously need to install the thing.<\/p>\n

<\/p>\n

First I had to decide where to install it<\/strong><\/p>\n

The office ESX farm is awaiting a capacity upgrade so I figured I’d use my demo laptop which is, for the spec nuts, a Lenovo T61 Thinkpad with 4GB of RAM, a dual-core 2.20GHz proc, and 150GB of disk.<\/p>\n

I\u00c2\u00a0wasted a whole day installing Windows Server 2008 into a VM, using VMWare Workstation running on Vista, but the performance was appalling. I then decided to jump in, boots and all, and\u00c2\u00a0rebuild the laptop with\u00c2\u00a0Windows 2008 Server. And I must say, I was pleasantly surprised by how effortless this was – the performance bears no comparison as well!<\/p>\n

One\u00c2\u00a0thought was to skip all the hard stuff and just download the ready-made VM<\/a>, which should run using Hyper-V on my newly built server\/laptop. I may still try this, but the resource requirements are pretty steep – 4GB recommended for the VM, and I only have 4GB available to the whole machine!<\/p>\n

So I went ahead with the manual installation, starting by installing SQL 2008, Sharepoint Services 3.0 and all the IIS components, as per this ILM “2” installation doc<\/a>, directly onto the laptop’s core OS.<\/p>\n

Creating the Service Account<\/strong><\/p>\n

The document stresses the need for a mail-enabled domain account to run the ILM service. This must be a dedicated account – which I think just means the mailbox shouldn’t be used by anything else. Presumably this mailbox will become important in the Workflows.<\/p>\n

I created a regular Domain Users account, then added it to local Administrators. In SQL 2008, I created it as a Login and gave it the sysadmin<\/em> right.<\/p>\n

Installing the Sychronization Service<\/strong><\/p>\n

The “MIIS bit” is now called the Synchronization Service. I installed it and, guess what? It looks exactly the same as it always has.<\/p>\n

Along the way I encountered this error: “Identity Lifecycle Manager Evaluation Release Candidate requires a running instance of Microsoft SQL Server…”\u00c2\u00a0\u00c2\u00a0 I was running the installation\u00c2\u00a0as an account which belonged to the local Admins, but which I had not yet added as a login in SQL Server – and in fact the installation doc convered this. The installing\u00c2\u00a0account must be a SQL Login and<\/em> it must have the sysadmin right.<\/p>\n

Whenever asked for a service account I gave it the domain account I created above. I was unsure whether this was the right thing to do, but so far so good.<\/p>\n

Installing the ILM Server<\/strong><\/p>\n

Supposedly this bit will do all the Sharepoint Portal stuff, and the seperate “Object Store” database (are they still calling it that?)<\/p>\n

I was again\u00c2\u00a0confused by the different accounts requested – you are asked for two during the installation,\u00c2\u00a0though it doesn’t ask for a password for the second account (so why ask for the account?).<\/p>\n

I attempted to\u00c2\u00a0create and use\u00c2\u00a0different accounts – during which I got this delightful error from the installation program: “Error -2147217900: failed to execute SQL string, error detail: Specified collection: ‘ReferenceSchemaCollection’ cannot be dropped because it is in use by object ‘dbo.GetMembersNotInSet’.”<\/p>\n

In the end I used the same domain account as I had in the Sync Service installation above, and this time it\u00c2\u00a0completed.<\/p>\n

Post-Install Steps<\/strong><\/p>\n

When I say “completed” I don’t mean “working”. The ILM Portal attempts to open at the end of the installation, and the message was “Error: Access denied”. Nice. I hoped that the post-installation steps from the doc would sort this out.<\/p>\n

Firstly, the doc says you may have to manually start the “Microsoft ILM Common Services” – I don’t have this service. Instead I have “Microsoft Identity Manager Lifecycle Services ” (in addition to the familar “Microsoft Identity Integration Server”) so I’m guessing they mean that? It was already started.<\/p>\n

The doc also said you might have to manually add the ILM service account into the MIISAdmins group if installing on a different server to the Sync Engine<\/em>. I installed it all on the same server – but I still had to make the manual group addition.<\/p>\n

Next I followed the instructions in the doc to run the stsadm command and give access to the Sharepoint page – however the stsadm command itself refused to run with\u00c2\u00a0“Access denied”. In troubleshooting stsadm:<\/p>\n