Will AD LDS be supported in Windows 7?
areis
usually shipped and deployed with our Application Server, which is .Net based
(C#) and runs on IIS.
Our Application Server is usually deployed on a server class operating
system, such as Windows 2003. and with our next minor release version,
Windows 2008. We made small changes to our ADAM implementation in order to
support AD LDS.
However, one of our deployment configurations is standalone, which means
that our server/ application server and client components are deployed in the
same box. This box will run on Windows 7. Here is where things get ugly.
In previous versions of our product, this was not a big deal as ADAM could
run on Windows XP. However, as of Windows 2008, Microsoft seems to have
dropped support of ADAM ( or AD LDS ) from its client based operating system
( Windows 7 ), this has caused us major headaches... to the point that for
the current release we are working on, we had to create a VMWare deployment
for the standalone deployment. We deploy our application server in a VMWare
session in the standalone system, where our App Server will be deployed in a
Windows 2008 VM Session.
I have seen one or two web sites saying that AD LDS will be supported in
Windows 7, but I have not seen anything from microsoft confirming this.
Can you clarify the support of AD LDS on Windows 7?
Joe Kaplan
there is something official that can be made available.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
"areis" <ar...@discussions.microsoft.com> wrote in message
news:44D6A882-ECC1-4967...@microsoft.com...
alexreis
thanks
alex
Joe Kaplan wrote:
I have heard the same things you have seen reported.
05-Nov-09
I have heard the same things you have seen reported. I will try to find out if
there is something official that can be made available.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
Previous Posts In This Thread:
EggHeadCafe - Software Developer Portal of Choice
Extract Icons from the Registry by their Extensions
http://www.eggheadcafe.com/tutorials/aspnet/c2689ba0-2aa5-44e8-83bb-3109969cd8e0/extract-icons-from-the-re.aspx
Ryan@discussions.microsoft.com Jim Ryan
My company is in the same boat. We developed our app around ADAM and it now
appears we must install an expensive server to get this functionality. This
lack of guidance from Microsoft has put us into a mode of evaluating open
source LDAP.
This is a yes or no question. Why is there no answer at this late date?
Thanks, Jim Ryan
"Alex Reis" wrote:
> .
>
Joe Kaplan
yet. No release date has been announced.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
"Jim Ryan" <Jim Ry...@discussions.microsoft.com> wrote in message
news:6D76534E-7E08-4E79...@microsoft.com...
Jim Ryan
Your reply leads me to believe that LDS will be supported on Windows 7
(reading between the lines). BTW - the product in question will be using
Windows Embedded Standard 2011
My company is a Micsoroft Embedded OEM. We are between a rock and a hard
place with this issue. We have a product that ships 10s of millions of
dollars a year and lack of a concrete answer to this question will probably
cause us to adopt an open source solution. I would think an OEM should be
able to get development code. We have beta tested many MS products in the
past.
Here is the latest note from my chief architect:
We need to figure out the Central Station / OS / LDAP issue. My plan has
been to use the embedded version of Windows 7, rather than Server 2008. If
we can’t have an LDAP instance on a Windows 7 box, I’ve got a big problem.
This is one of the risk items on the list I’ve been putting together.
---------------
· LDAP
The Pegasus implementation of settings stores application and global
settings in LDAP. Unfortunately, LDAP is a server component which is
unavailable on Windows 7, the OS planned for Central Station (LDAP client is
available, but not server – that is, we cannot create an LDAP instance on a
Windows 7 system). This might be acceptable in a networked implementation
where there is a LDAP server on the network, but is not acceptable for a
standalone system.
Alternatives:
· try to make Central run on Win Server 2008 (which may mean that we
have to develop some UI components such as on-screen keyboard that we get for
free with Win7)
· use a 3rd-party / open source LDAP library (not sure how much
difference there may be in the APIs / functionality from the Microsoft LDAP)
· hope Jim Ryan can find a “magic switch” that either enables the
LDAP services on Win7 or enables the Win7 UI on Server2008
· include a Server2008 system somehow, either as a separate box, or
as a VM running on the Central box (if that’s doable).
· rewrite settings to not use LDAP
Thanks, Jim Ryan
"Joe Kaplan" wrote:
> .
>
Joe Kaplan
great way to get the attention of someone there other than a support person.
It used to be the case that product team members would check newsgroups but
I haven't seen that for a while.
I can probably find the email address of the AD LDS program manager if you
contact me offline (joe @ joekaplan . net). I'm not sure he'll reply but he
should be able to give you something definitive.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
"Jim Ryan" <Jim...@discussions.microsoft.com> wrote in message
news:876C319C-1ACE-43B3...@microsoft.com...