Re: LSA vs LSP GUI on Vista/2008?
- From: Gerry Hickman <gerry666uk2@xxxxxxxxxxxxxxxx>
- Date: Tue, 17 Feb 2009 23:17:52 +0000
Hi Jialiang, Joe,
I really wish I hadn't mentioned the dreaded .NET word. I have no
interest in calling anything from .NET or writing any wrapper in .NET or
wrapping a COM class in .NET or calling native code from .NET using
P/Invoke or any other combination of convoluted .NET interop.
What I was originally trying to ask, is if there already exists a
managed class in .NET that can enumerate the LSA - I think the answer to
that was "No". Sorry for not being clear enough earlier.
Now the interesting stuff:
Regarding writing COM classes, ATL/COM Servers, WMI providers etc., I'm
very interested in this, but I have some major concerns listed below,
I'd very much appreciate any comments:
1. Where is the roadmap on Microsoft's website showing the future of
ATL/COM?
2. How quickly can we expect bugs in ATL to be fixed over the next two
years 2009/2011 compared to .NET?
3. My native code in C/C++ is able to work with LSA on thousands of
remote machines without any installation. My understanding is that in
order to use COM clients and servers, I'd need information added to the
registry of EVERY remote machine?
4. Regarding writing a WMI provider, and assuming this provider would be
installed to the target machine, is there any way to install a WMI
provider to a remote machine at run time and then uninstall it when the
calling program finishes? What about enabling a WMI provider that's shipped with Windows but not installed, such as the MSI provider on Windows Server 2003 or the SNMP provider on Windows Server 2008, is it possible to enable them on thousands of machines without logging in to each one with an interactive shell?
5. Using .NET remoting, my understanding is that it will only work if
the class exists in the library of the remote machine, so it's the same
problem of having to install it to thousands of machines? Can it work
without Admin rights, like what you can do with DCOM?
5a. Seems like the same weakness in PowerShell?
6. Using WinRM, my understanding is that it's disabled by default and it
only works with Admin rights - unlike DCOM that can work without Admin
rights.
I like the examples on codeplex, but I did not see much information about perfecting the installation process for remote machines; these things sometimes need keys written to HKLM\Software\Classes, AppID, CLSID, then x-ref GUIDs pointing all over the place, then launch/activation ACLs. It's easy on a local machine with Admin rights and Visual Studio, but I have not found a good way to do this on thousands of machines at run time, and then clean them up after.
Cheers.
Jialiang Ge [MSFT] wrote:
I agree with Joe. Many functions provided by .NET class library eventually calls into Windows API using something similar to P/Invoke. Using P/Invoke is safe as long as the signature is written rightly and the parameters do not require pointers. The unsafe programming in .NET generally refers to the direct operations on memory using pointers, for example, http://www.codeproject.com/KB/cs/unsafe_prog.aspx.
Regarding how to write a COM component in .NET, my HelloWorld project has a sample for it: CSDllCOMServer
http://www.codeplex.com/HelloWorld
You can find the detailed steps of building such a component in the sample's ReadMe.txt file. Inside the component, you can expose a method that P/Invokes the native API LsaEnumerateAccountsWithUserRight.
Regards, Jialiang Ge (jialge@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support
=================================================
Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================
--
Gerry Hickman (London UK)
.
- Follow-Ups:
- Re: LSA vs LSP GUI on Vista/2008?
- From: "Jialiang Ge [MSFT]"
- Re: LSA vs LSP GUI on Vista/2008?
- References:
- LSA vs LSP GUI on Vista/2008?
- From: Gerry Hickman
- RE: LSA vs LSP GUI on Vista/2008?
- From: "Jialiang Ge [MSFT]"
- Re: LSA vs LSP GUI on Vista/2008?
- From: Gerry Hickman
- Re: LSA vs LSP GUI on Vista/2008?
- From: "Jialiang Ge [MSFT]"
- Re: LSA vs LSP GUI on Vista/2008?
- From: Gerry Hickman
- Re: LSA vs LSP GUI on Vista/2008?
- From: Joe Kaplan
- Re: LSA vs LSP GUI on Vista/2008?
- From: Gerry Hickman
- Re: LSA vs LSP GUI on Vista/2008?
- From: Joe Kaplan
- Re: LSA vs LSP GUI on Vista/2008?
- From: "Jialiang Ge [MSFT]"
- LSA vs LSP GUI on Vista/2008?
- Prev by Date: Re: Vista/2008 cmdline Security Tools?
- Next by Date: Can exchange key pair be exported and used on another machine?
- Previous by thread: Re: LSA vs LSP GUI on Vista/2008?
- Next by thread: Re: LSA vs LSP GUI on Vista/2008?
- Index(es):
Relevant Pages
|