Windows Identity Foundation and Windows Azure passive federation

Home

Downloads

Discussions

People

License

RSS

All Resource Updates

Discussions

Releases

Wiki

RSS Feed

RSS

Comments \| Print \| Page Info \| Change History (all pages)	Search Wiki:
Home
This Hands-on Lab Has Been Superseded Thank you for your interest in Windows Azure and Windows Identity Foundation! This lab was originally conceived as an early preview. Since then, both Windows Azure and WIF have been released and the guidance on how to use them together has been migrated in the Windows Azure Platform Training Kit and the Windows Identity Developer Training Kit. You can find an online version of this lab in the msdn training courses. We welcome your feedback! You can find more information here and here.
Last edited Jun 23 2011 at 12:13 AM by Vittorio, version 7
Comments jkrishnaswamy wrote Feb 13 2010 at 8:04 PM This is supposed to work in Windows 7 and it does not. Who says? The Configuration Wizard. I would add a screen shot in evidence but there is no such provision here. Why don't you place it on a publicaly accessible folder on the skydrive. Vittorio wrote Mar 8 2010 at 2:02 AM Hi , the lab works on Windows 7 and has been thoroughly tested both on x86 and x64 versions. One common issue you can stumble upon is described in http://blogs.msdn.com/vbertocci/archive/2010/03/07/using-the-windows-identity-foundation-and-windows-azure-passive-federation-lab-with-the-february2010-windows-azure-tools.aspx, can you check if that's what is happening to you? pattmania wrote Sep 17 2010 at 10:15 AM Hi Vittorio, This also doesn't work for me - and not as a consequence of the link specified as it is failing on otehr requirements. I'm using Windows 7 Ultimate. The Configuration Wizard is failing, claiming I don't have Microsoft SQL Express 2005 or Later. I do have it, and can connect to it using the MS SQL 2008 Management tools as I also have those installed. I can also run the Azure 1.2 SDK development storage server - which I believe requires SQL Express. The configuration manager also claims I don't have the Windows Identity Foundation SDK installed - despite me following the download link and installing the requested Windows6.1-KB974405-x86.msu. Could the required software wizard be looking for specific versions of applications rather than minimum versions? Any advice you can give would me apprecaited. Thanks, Nick pattmania wrote Sep 17 2010 at 11:18 AM Ok, I've made progress on this and thought I'd post what I did to coax this into life here for benefit of anyone else struggling with it. All of the below changes refer to teh dependny checks that sit in dependencyChecker\scripts\dependencies\check of the setup (which can be extracted with WinRAR) The SQL install check is assuming that the user has 32bit SQL 2005 or 64 bit 2008 - but isn't catering for 32bit 2008, so I corrected that check by changing adding in both $res3 bits, so I needed to change CheckSqlServer.ps1 from : $res1 = SearchUninstall -SearchFor 'Microsoft SQL Server 2008' -UninstallKey 'HKLM:SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\'; $res2 = SearchUninstall -SearchFor 'Microsoft SQL Server 2005' -UninstallKey 'HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\'; ($res1 -or $res2) to $res1 = SearchUninstall -SearchFor 'Microsoft SQL Server 2008' -UninstallKey 'HKLM:SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\'; $res2 = SearchUninstall -SearchFor 'Microsoft SQL Server 2005' -UninstallKey 'HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\'; $res3 = SearchUninstall -SearchFor 'Microsoft SQL Server 2008' -UninstallKey 'HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\'; ($res1 -or $res2 -or $res3) The next problem was that the Windows Identity Runtime registry key has changed, so I changed CheckWifRuntime.ps1 from $res1 = SearchInstall -SearchVersion '6.1.7600.0' -PathKey 'HKLM:SOFTWARE\Wow6432Node\Microsoft\Windows Identity Foundation\Setup\'; $res2 = SearchInstall -SearchVersion '6.1.7600.0' -PathKey 'HKLM:SOFTWARE\Microsoft\Windows Identity Foundation\Setup\'; ($res1 -or $res2) to $res1 = SearchInstall -SearchVersion '6.1.7600.0' -PathKey 'HKLM:SOFTWARE\Wow6432Node\Microsoft\Windows Identity Foundation\Setup\'; $res2 = SearchInstall -SearchVersion '6.1.7600.0' -PathKey 'HKLM:SOFTWARE\Microsoft\Windows Identity Foundation\Setup\'; $res3 = SearchInstall -SearchVersion '6.1.7600.0' -PathKey 'HKLM:SOFTWARE\Microsoft\Windows Identity Foundation\Setup\v3.5\'; ($res1 -or $res2 -or $res3) The next problem is that the WIF link goes to the component not the WIF SDK, so I downloaded the SDK from here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c148b2df-c7af-46bb-9162-2c9422208504&displaylang=en I then re-ran it and the CheckWifSdk.ps1 check still failed, because it is looking for a display name that has changed, so changed: $res1 = SearchUninstall -SearchFor 'Windows Identity Foundation SDK' -SearchVersion '6.1.7600.76' -UninstallKey 'HKLM:SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\'; $res2 = SearchUninstall -SearchFor 'Windows Identity Foundation SDK' -SearchVersion '6.1.7600.76' -UninstallKey 'HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\'; (($res1 -eq $TRUE) -or ($res2 -eq $TRUE)) to $res1 = SearchUninstall -SearchFor 'Windows Identity Foundation SDK' -SearchVersion '6.1.7600.76' -UninstallKey 'HKLM:SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\'; $res2 = SearchUninstall -SearchFor 'Windows Identity Foundation SDK' -SearchVersion '6.1.7600.76' -UninstallKey 'HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\'; $res3 = SearchUninstall -SearchFor 'Windows Identity Foundation SDK' -SearchVersion '6.1.7600.16436' -UninstallKey 'HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\'; (($res1 -eq $TRUE) -or ($res2 -eq $TRUE) -or ($res3 -eq $TRUE)) then corrected the Azure 1.2 SDK check as detailed here: http://blogs.msdn.com/vbertocci/archive/2010/03/07/using-the-windows-identity-foundation-and-windows-azure-passive-federation-lab-with-the-february2010-windows-azure-tools.aspx - NOTE: I neede to apply this fix needs applying to CheckAzureTools.ps1 as well as CheckAzureToolsForVS.ps1 After all that, it decided it was happy with life and installed. If the lab install was thorughly tested, then perhaps it's worth looking into the test scripts to see if something can be done to add more consideration to future versions? It's a shame that so much work has gone into the lab and that people can't easily consume it due to such a fragile install. The fact that the WIF link goes to the component rather than the SDK is also an unfortunate miss. Hope the above helps other people get it installed, Nick Sign in to add a comment

Updating...