LitwareHR May 2008 on Vista

Topics: Business model, Setup, Troubleshooting
Jun 5, 2008 at 7:00 PM
I guess this latest version will not run on Vista because it requires Active Directory Lightweight Directory Services, and that is not available on Vista?
Coordinator
Jun 12, 2008 at 4:05 PM


leftyfarrell wrote:
I guess this latest version will not run on Vista because it requires Active Directory Lightweight Directory Services, and that is not available on Vista?



We simply haven't tested LW on Vista. We did post some time ago how to run on XP, so it should be possible. ADLS is just ADAM with a minor tweaks. The main dependency of the last drop is IIS7 which I believ you can install in Vista. 
Jun 12, 2008 at 9:21 PM
I found this post which indicates a way to "hack" an install of ADAM on Vista.  The default installer "chokes" as he puts it, and apparently, MS has no intention of updating the installer to be Vista friendly.

http://geekswithblogs.net/cicorias/archive/2007/10/10/Installing-ADAM-on-Vista.aspx

I have not yet tried this myself.
Coordinator
Jun 13, 2008 at 3:50 AM


Lefty wrote:
I found this post which indicates a way to "hack" an install of ADAM on Vista.  The default installer "chokes" as he puts it, and apparently, MS has no intention of updating the installer to be Vista friendly.

http://geekswithblogs.net/cicorias/archive/2007/10/10/Installing-ADAM-on-Vista.aspx

I have not yet tried this myself.



If you look at the workshop's security lab you can see where we use ADAM and mock it out if that dependency bothers you. The workshop doesn't use ADAM (or ADLS), but still calls "login", etc

The workshop:
http://www.codeplex.com/LitwareHR/Wiki/View.aspx?title=SaaS%20Architecture%20Workshop%20070402&referringTitle=Home 

The security lab:
http://files.skyscrapr.net/users/saas/sampleApp/Videos/SW/Lab03-Security.zip
Jun 13, 2008 at 1:06 PM
A note to others about the ADAM on Vista "hack".  The method provided apparently works on Vista pre-SP1, however, I ran into problems attempting it on SP1.  The adaminstall.exe fails because of a dependency on another windows DLL, that seems to have been updated by SP1.