working with objects

Retrieving the account IIS is using as the anonymous user account with VBScript

I recently posted a script that retrieved the anonymous user password for a server in IIS. This script I posted, Using the IIS ADSI object to retrieve the anonymous user password for a server via VBScript, came in quite handy in a pinch, but not knowing the anonymous user account the password goes with can also be a pain.Luckily I had that piece of information in the script as well!

So, I’ve wrapped that part of the script into a function for your use as well. Below is a snippet from the script to display the user account.

Function Get_IUSR_Username(ServerName)
Dim IIsObject

Set IIsObject = GetObject (”IIS://” & ServerName & “/w3svc”)
on Error resume Next
Get_IUSR_Username = IIsObject.Get(”AnonymousUserName”)
On Error GoTo 0
End Function

Enjoy!

Using the IIS ADSI object to retrieve the anonymous user password for a server via VBScript

I recently had to change the anonymous user account for a change request for a site in IIS, but unfortunately the change did not work and we had to roll it back. However, I didn’t have and wouldn’t have known the account’s password since IIS and windows changes it periodically.

So, out came the scripting tool belt and I found that I had a script written previously that let me get the anonymous user account and password through the IIS ADSI object.

Below is a snippet from the script to display the password.

Function Get_IUSR_Password(ServerName)
   Dim IIsObject
   
   Set IIsObject = GetObject (”IIS://” & ServerName & “/w3svc”)
   on Error resume Next
   Get_IUSR_Password = IIsObject.Get(”AnonymousUserPass”)
   On Error GoTo 0
End Function

Enjoy!

Clean up your toys when your done: Fighting memory leaks in your scripts

One on the things you always want to do when you create objects in your scripts, especially objects from third party companies is, is to always remember to destroy the objects when you are done with them. At the very least, before you exit the script.

Object creation and not destroy the objects can be one source of memory leaks. In order to destroy an object should use the object’s .dispose method. If it does not have a dispose method, you set simply it to a special value of nothing. This will destroy the object and free up it’s memory. An example of using nothing is shown below:

Dim ObjTest
Set ObjTest = GetObject(”winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2″)
ObjTest = nothing

VBScript Statements: Explanation of the Set Statement

The set statement is used to assign any value to any type of variable. For the most part this command is optional. However, it needs to be used when you are assigning an object reference to a variable, such as when you use a variable to hold the return of a CreateObject function for later reference in your code.

An example of the set command would look like:

Option explicit
Dim objDictionary
Set objDictionary = CreateObject(”Scripting.Dictionary”)

VBScript Statements: Explanation of the With … End With Statement

The With … End With statement allows you to execute a section of code on a specific object or class that calls methods or set properties on the object from within VBScript without referencing the object directly in the code written.

It is a way of simplifying your code, and very useful in large scripts.
For example:

(please note, these examples are snippets of code and will not work by themselves in an editor)

with objSomething
     .FirstName = “Jerry”
     .LastName = “Lees”
     .URL = “http://www.gamersigs.net“
     .XBoxLiveTag = “CrashSerious”
     .Email = “Not-a-chance-spammers”
End with

This would be equivalent to the following standard code:

     objSomething.FirstName = “Jerry”
     objSomething.LastName = “Lees”
     objSomething.URL = “http://www.gamersigs.net“
     objSomething.XBoxLiveTag = “JLees”
     objSomething.Email = “Not-a-chance-spammers”