Month: August 2009

Proxy authentication in a VBScript

While experimenting with Twitter API using VBScript, I was unable to access as the script was not authenticating to the proxy server inside the corporate network. I was using XMLHTTPRequest object initially and found out that there is no way I could authenticate to a proxy when using this object. I quickly looked at WinHttpRequest object and it provides a mechanism to set the proxy credentials. I thought it is worth sharing that here.

The overall output of this script will be 20 recent replies to your Tweeter account in XML format. That may not be really useful to you but I just wanted to describe how the proxy server authentication can be done using VBScript. Technorati Tags: Twitter,Twitter API,Scripting,VBScripts

Windows 7 CHKDSK memory consumption – Update

I did check this after installing RTM on my home PC. Looks like the magnitude of the issue increases with the size of the volume and number /size of files on it. For example, when I first verified this with RC, I ran CHKDSK against a 500GB volume with lot of personal data, ISO images, WIM files and VHDs. The result can be seen here. However, after installing RTM build, I ran it once again against an empty partition of 500GB and the memory consumption by CHKDSK for ~35MB. To me, this issue certainly looks like a design bug. I have not seen a BSOD anytime. So, this is not as critical as others might claim. Anyway, as more and more people start talking about it, I am sure MS will release a fix soon. Technorati Tags: Windows 7,Windows Server 2008 R2,CHKDSK

Windows 7 CHKDSK memory consumption

Okay..there is already a lot written about this bug on the Internet. To summarize, many people have reported a memory leak behavior with Windows 7 CHKDSK utility when the /R switch is used. /R switch is used to locate bad sectors and recover readable information. Many of the blog posts also report that it is a RTM bug. So, first thing was to verify if it happens on the RC build. I am still running RC (x64) on my Studio 540S system with 4GB of RAM. I ran chkdsk against D: (500GB SATA disk) and started monitoring memory utilization. Here is what happened after a few seconds – as chkdsk entered stage 4 of it’s process. As you can see, my system is still running Windows 7 RC and I am using all inbox drivers on this. So, this is not something got introduced in RTM build. Now, I killed the chkdsk process to see if it releases the memory or not. It does, unlike others reported at various other places. Next thing was to …

R2: Hyper-V host compatibility checks – A few thoughts

Yesterday, I released a script to find out if a given VM or VMs on a source host can be migrated successfully to another physical host with Hyper-V role. When you use this script to verify if a running VM can be moved from HOST A with most recent Intel processor to HOST B with an older Intel processor, you may find that the migration is not possible. This is because HOST A has a processor feature set that is the superset of HOST B and hence when a running VM is migrated from A to B, it will fail to run. Now, in Windows Server 2008 R2, there is a feature called processor compatibility mode. This can be found in the VM properties window. This feature is disabled by default. When you enable this feature, the overall guest visible processor feature set will be limited. So, this enables a virtual machine to be moved from a host with most recent version of the processor to a host with older version of processor. However, make …

R2: Script release for Hyper-V host compatibility checks for VM quick / live migrations

In my previous post, I talked about how we can use CheckSystemCompatibilityInfo() and GetSystemCompatibilityInfo() methods to check host compatibility checks before performing quick or live migrations. I had mentioned that I will post a script around these methods. In this post, I will release – download at the end of post — the script and talk a bit about how the above mentioned methods are used. Here is the usage of this script cscript getcompatibility.vbs /SRCHOST:[HOSTNAME] /DESTHOST:[HOSTNAME] /VMNAME:[VM_NAME] In the above command-line, SRCHOST is the name of the Hyper-V host from which you want to migrate the virtual machines DESTHOST is the name of the Hyper-V host to which you want to migrate the virtual machines VMNAME is the name of the virtual machine — running on SRCHOST – you want to migrate In this parameters, SRCHOST and DESTHOST parameters are mandatory and VMNAME is optional. If you refer to the GetSystemCompatibilityInfo(), the ComputerSystem input parameter can either be a Hyper-V host name or a virtual Machine element name. If the input is a Hyper-V …