miércoles, 11 de enero de 2012 15:05
Greetings WSP developers,
At the moment WSP requires you to run Server component on every server you would like to manage. Running WSP Server component requires installation of IIS. So, let's say, if you have 2 DCs + DNS, 2 Mail, 2 Web, 2 FTP, 2 etc. server - every one of them should have IIS installed.
I have just installed a few Hyper-V servers for some other work and opened a wonderful world of WinRM for myself. You can manage servers remotely using MMC snap-ins and PowerShell and other interesting things. In most of the cases it uses WMI providers behind the scenes.
So the question came up: Is WMI providers the way to go to avoid installing WSP Server and efficiently manage servers remotely?
I know WSP uses WMI providers locally for some tasks (I'm do not know internals of WSP in details, so I might be wrong).
I have a feeling that MS DNS server and AD are good candidates for remote management using WMI providers for the start.
Is this something to look at? Any thoughts?
P.S. I'm not pro C# or VB developer though.
- Editado jegor miércoles, 11 de enero de 2012 15:06
Todas las respuestas
martes, 17 de enero de 2012 8:05Moderador
As far as I know, currently WSP uses classes in System.Management namespace to execute wmi queries for tasks like getting dns zones, records. I'm not familiar with wmi providers, a quick scan made me believe this coule be handy. You may consider contact firstname.lastname@example.org to receive direct response from wsp team.
Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact email@example.com. Microsoft One Code Framework
- Marcado como respuesta Lloyd ZhangMicrosoft Contingent Staff, Moderator jueves, 19 de enero de 2012 0:50