Wednesday, November 23, 2005


Recently, one of my colleagues ran into this issue when he was trying to install IIS components on Windows Server 2003. Since, I was aware of this issue, I thought of posting it for my own documentation. Whenever Service Pack is slipstreamed into the original installation source (i386), an additional file WIN51IS.SP1 is automatically created in the same directory where i386 folder resides. This file - WIN51IS.SP1 is essentially a service pack identifier file and its exact name depends on the OS version and the service pack slipstreamed into it. Few examples: WIN51IA.SP1 for Windows 2003 Advanced/Enterprise Server WIN51IS.SP1 for Windows 2003 Standard Server WIN51IB.SP1 for Windows 2003 Web Server The availability of this file is necessary for a successful installation if the source \i386 folder has service pack integrated into it. So, next time when you stage i386 folder on the hard disk, ensure that you also copy-paste WIN51IS.SP1 file in the same folder where i386 resides (not inside i386) to avoid any installation issues.

Thursday, September 22, 2005

Enterprise Security

One of my friends - Arvind got inspired and jumped into the blogging world. He recently got promoted as Information Security Lead on his project in one the major IT Consultancy firms.

Nice to have him share his thoughts on the stuffs that he works on - Active Directory, Group Policy, Information Security, Change Management, et al.

Thursday, September 15, 2005

NETSH / How to reinstall TCP/IP in XP/2003

Admins who manage HP/Compaq Proliant servers would probably agree with me that remotely administering these server using RIB/iLO is a real pain. Few weeks ago, I had to re-do network teaming on one of the remote servers located in different geography using the RIB interface. It was a real pain trying to keep mouse cursor in sync to be able to go through many clicks to make network configuration and re-assign IP/gateway/DNS/WINS addresses. That was when I realized the true potential of NETSH command-line interface and the scripting capabilities it offers on Windows platform.

For the same scenario, I could’ve exported the network configuration using c:\>netsh -c interface dump > c:\netsetting.txt and after re-doing the teaming could’ve imported the same setting from the text file using C:\>netsh -f c:\netsetting.txt

Though we need to be careful not to change the name of any of the network interfaces – HP Network Team #1 should not become HP Network Team #2 after redoing the teaming.

Netsh comes handy not only for exporting/importing network configurations, but it is also capable of making different network settings like assigning IP/mask/gateway/DNS/WINS. Netsh command is also used for resetting TCP/IP stack in Windows XP and 2003 platforms. Unlike Window 2000, TCP/IP is a core component of Windows XP/2003 and cannot be uninstalled/reinstalled; it can only be reset to the state when the operating system was installed, which the following command does

c:\>netsh int ip reset resetlog.txt

Find more details at:

Sunday, September 11, 2005

It had to happen sooner or later

The Blogger plug-in for MS Word work is a great opportunity for me start putting up my thoughts/comments/stories centered mostly around techi/geeky/random stuff... stay tuned.