WindowsAdminGuru BLOG

The original name of this post was "a poor developer's guide to windows azure" but then I found the Bart Simpson's Chalkboard Generator : My Azure story begins back in PDC08 where Microsoft announced a community preview of Windows Azure which includes a free subscription for a limited period. I took advantage of this to develop the Wcf binding box (which btw got some good reviews ). A few months after, the preview has ended and my account became read only. I was not too bothered by it as I had other things in mind . A few weeks ago I had a crazy idea to build a wsdl2-->wsdl1 converter. The most natural way to do it was to create an online service. But my azure trial is already in freeze, and I did not want to pay a hosting service just to host a free contribution I make for the community. What could I do? I then remembered that I (and my contest winners ) have a special MSDN premium Azure offer . And this is how wsdl2wsdl came to life. Veni, vidi, v

If your server has two HBA cards connected to EMC SAN storage device, you can implement load-balancing, and fail-over on the HBA cards using the EMC PowerPath software. Powermt management utility helps you manage I/O paths from the server to the EMC storage device. In this article, let us discuss how to use powermt command with practical examples. 1. powermt display – Display High Level HBA I/O Paths powermt display command (without any arguments), displays the available HBAs and their current status. The following examples, shows that there are 2 HBAs connected to the server, both the HBAs are in active condition with 2 I/O path’s each. qla2xxx indicates that it is using the Q-Logic HBA card. This also indicates that the connected EMC device is CLARiiON, as it displays a value for “CLARiiON logical device count” as 1. C:\Program Files\EMC\PowerPath> powermt display Symmetrix logical device count=0 CLARiiON logical device count=1 Hitachi logical device count=0 Invista

In my daily life, I couldn’t imagine not having VMware Workstation to create labs or test case scenarios. On many occasions, I clone a vm in minutes to test something, but I often find that the SID remains the same. A simple utility exists that enables you to quickly change the SID and the computer name of a cloned virtual machine. The utility is called NewSID v4.10 and is available for download free of charge. After you download the application, extract the file to a drive and open a command prompt. Next, browse to the applicable directory. Next, run the auto option to create a new SID and rename the computer. It takes a few minutes for the process to complete and the computer to reboot. When you log in to the computer again, the SID is brand new and the computer (Figure D) is automatically renamed. newsid.exe /a [newcomputername]

How to add a datastore in VMware Farm. Let me share on how to add a new datastore. Please follow the below steps. 1. Choose the ESX Server. 2. Click on “Configurations”. 3. Select “Storage”. 4. Click on “Add Storage”. 5. Choose storage type “LUN/Disk”. 6. Select the LUN and click Next. 7. Type the name for the LUN. 8. Select the maximum file size. 9. Click on “Finish”. 10. Wait for “Create VMFS Datastore” task to be completed. Now you will be able to view the datastore or else click on rescan to view the recently created datastore.

I was supposed to register EMC powerpath in one of the servers and I did not have an proper idea to do so. I did not have the key with myself. Then after a lots of googling I found the command to check the EMC powerpath registration status. C:\Users\administrator>powermt check_registration There are no license keys now registered. Then I logged into another server, executed the same command and got the key. C:\Users\administrator>powermt check_registration Key XXXX-XXXX-XXXX-XXXX-XXXX-XXXX Product: PowerPath Capabilities: All I then used the same key for the server using the command. C:\Users\administrator>emcpreg -add XXXX-XXXX-XXXX-XXXX-XXXX-XXXX Success: License added I succeeded in registration.

Recently I had an issue where we recently built up new blade servers in a very new enclosure. The problem was that I was unable to ping among any server available in the same enclosure. After a long struggle I found that the issue was due to the enclosure configuration and settings. This was because the “Private Network” option was enabled. Private Network option provides an extra networking security. Once I unchecked the Private Network I was able ping all the server from each other. To enable Private Network, 1. Login to the HP Virtual Connect Manager. 2. Choose Ethernet networks” and choose the network. 3. You will now find an option “Private Network”. 4. Uncheck the option to resolve the issue.

The McAfee fails to update automatically There are different possibilities of issue. However, few of the troubleshoot steps were previously discussed in our portal. This time I have got one more possibilities. This issue could occur if it could not connect to the repository. Therefore, please check whether the Autoupdate repository list is updated properly. Please follow the below steps to confirm the same: 1. Open “McAfee Virus Console”. 2. Click on “Tools” and select “Edit Autoupdate Repository list”. 3. Select the desired server list and click “Ok”. Now try Autoupdate, this should work fine. Came to know about one more fix. However am not sure whether it works. Its didnt work for me but might work for you, so try and share your experience. Try to copy the file “sitelist.xml” (from same location as mentioned below) from any working server to the required server in the location C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework

This can be achieved using the free utility available from Dell. Its very simple and easy to use. This works fine on Basic disk and I have tried with Windows 2003 Standard Edition 64 Bit. Download the utility ExtPart Open the command utility and browse to the location where the Extpart is located. Then execute the command extpart Syntax: extpart [volume size ]   volum e – the volume to extend. e.g. f:, g:, etc (only basic volumes)   size – the size in megabytes by which to extend the volume. Example: To extend the C: volume by 10 GB (10240 MB) use the following command: extpart g: 1024 Updated: 23/03/2011: I tried in both physical and virtual machine. It works fine without any down time!!!!! Good news for Windows Administrators

Here goes the command line command to check Veritas Storage Foundation (VSF) - Goto Command Prompt type vxassist version output would be like this -