DiIWM (Di IIs Web Manager) is a web application written in VB.NET to manage IIS6.0. Both WMI and ADSI is used. DiIWM can connect and manage local and remote IIS. DiIWM also provides an assembly (Di) written in C# to manage IIS6.0.
Be the first to post a text review of Di IIS Web Manager. Rate and review a project by clicking thumbs up or thumbs down in the right column.
Thanks to Anton for this mail : "I finally tracked it down. Turns out that each namespace in the CIM repository has a security descriptor to control access. I was able to access root\cimv2 just fine from ASP.NET and VBScript, but was getting Access Denied when trying to access the root\MicrosoftIISv2 namespace. Luckily, an error was generated in the EventViewer: "Access to the root\MicrosoftIISv2 namespace was denied. The namespace is marked with RequiresEncryption but the client connection was attempted with an authentication level below Pkt_Privacy. Re try the connection using Pkt_Privacy authentication level." Before Windows Server 2003 SP1, providers could not set namespace security to require encryption before returning data. It looks like with SP1, the RequiresEncryption is configurable and is also the default. You can change this through the WMI control (globally) or programmatically per connection. In VB, it would look like this: set locatorObj = CreateObject("WbemScripting.SWbemLocator") locatorObj.Security_.authenticationLevel = WbemAuthenticationLevelPktPrivacy In C#, it would look like this: ConnectionOptionsObject = new ConnectionOptions(); ConnectionOptionsObject.Username = UserName; ConnectionOptionsObject.Password = Password; ConnectionOptionsObject.Authentication = AuthenticationLevel.PacketPrivacy; I have not tested this on other platforms outside of W2K3, SP1, as it presumably wasn't needed. Not sure if you're planning on publishing a newer version of your libraries any time soon, but just adding the line above to each ConnectionOptions object will fix this if anyone else experiences the issue."
Be the first person to add a text review.
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: