IIS 6 and Application Pools

Here is a nice explanation regarding IIS 6 application pools...

The 2nd one explains how to configure a new Application pool identity account.

Reference: http://www.developer.com/net/asp/article.php/2245511/IIS-and-ASPNET-The-Application-Pool.htm
http://support.microsoft.com/kb/832770

WBCOOP

I have registered to play in the PokerStars World Blogger Championship of Online Poker! The WBCOOP is a free online Poker tournament open to all Bloggers, so register on WBCOOP to play.

Registration code: 994146

How to Install NetBackup 6.5 Client and/or patches on a Cluster without the PBX Cluster Resource Groups

Otherwise, assuming Netbackup was not installed cluster-aware, from Cluster Adminstrator, take the PBX stuff offline and delete.

Reference: http://seer.entsupport.symantec.com/docs/304228.htm

8925 Tilt Mac Address

With the wireless adapter on, if you go into Settings - Connections (tab) - Wireless LAN - Advanced (tab). You should see a line for the MAC.

Unpublish network printers

To uncheck the "List in the directory" for all print queues on \\printserver use this command:

• C:\Program Files\Windows Resource Kits\Tools>setprinter \\printserver 7 "dwAction=unpublish"

Adding new MSCS node with Snapdrive and iSCSI

I was having problems replacing a failed node in a Windows 2003 MSCS cluster. With Netapp storage, I had the LUNs mapped to both nodes, but I could not add the shared disks to the new node unless I added it the cluster first.

Use Cluster Administrator to add a new node and specify "Advanced", then click "Advanced (minimum) configuration". This will add the node without shared disks. Once complete, I was able to open SnapDrive and the shared LUNs showed up.

For some strange reason, the only weird think in the System event logs was this warning, Event ID 20:

"A Path Verification request to a device on \Device\MPIODisk2 that is controlled by Microsoft iSCSI DSM has failed. This may indicate a Path Failure."

When I booted the new node alone (with other cluster node off), the LUNs showed up, but as "dedicated" LUNs in SnapDrive.

This led me to try and see if I could add the node to the cluster without shared disk, then to try and access the LUNs after that to see if they showed up as "clustered", which they did!

Reference: http://support.microsoft.com/kb/331801/en-us

Connecting ESX host to iSCSI LUN on Netapp v3140

Reference: http://blog.scottlowe.org/2006/12/15/iscsi-from-netapp-to-esx-server/