Pop this into the run dialog: control ncpa.cpl This will also work for the following: control printers = Printers control sysdm.cpl = System Properties control appwiz.cpl = Programs & Features (Add & Remove) This can also be coupled with ‘Runas’: runas /user:computername\Administrator rundll32.exe shell32.dll,Control_RunDLL ncpa.cpl

Ldifde -d DC=domain,DC=co,DC=uk -r (&(mailnickname=*)) -l proxyAddresses -f Report.txt

Using a Nexenta VM it is possible to create a 500 TB thin provisioned iSCSI target in three lines: zpool create zfspool01 raidz c2t0d0 c2t1d0 c2t2d0 zfs create -s -V 500TB zfspool01/share01 zfs set shareiscsi=on zfspool01/share01 In this case the disks c2t0d0, c2t1d0 and c2t2d0 are all dynamic 10 GB virtual disks. This can easily be mounted with the Microsoft iSCSI Initiator for testing; it will be interesting to see how well this plays with ESX…

You can use the following web service to see if your DNS servers or resolvers need attention. For Windows: nslookup -querytype=TXT -timeout=10 porttest.dns-oarc.net. nslookup -querytype=TXT -timeout=10 porttest.dns-oarc.net. DnsServerName For *nix: dig +short porttest.dns-oarc.net TXT dig @DnsServerName +short porttest.dns-oarc.net TXT Where DnsServerName is the name of the DNS server you want to check. You are looking for GREAT, GOOD or POOR in the results. Original Reference

If you haven’t got hwinfo installed then: sudo aptitude install hwinfo Then put this in: sudo hwinfo –framebuffer Returns : 02: None 00.0: 11001 VESA Framebuffer [Created at bios.447] Unique ID: rdCR.il6towt04X5 Hardware Class: framebufferModel: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS Intel(r) 82945GM Chipset Family Graphics ControllerVendor: Intel CorporationDevice: Intel(r) 82945GM Chipset Family Graphics ControllerSubVendor: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOSSubDevice:Revision: Hardware Version 0.0Memory Size: 7 MB + 704 kBMemory Range: 0xd0000000-0xd07affff (rw)Mode 0x0312: 640x480 (+2560), 24 bitsMode 0x0314: 800x600 (+1600), 16 bitsMode 0x0315: 800x600 (+3200), 24 bitsMode 0x0301: 640x480 (+640), 8 bitsMode 0x0303: 800x600 (+832), 8 bitsMode 0x0311: 640x480 (+1280), 16 bitsConfig Status: cfg=new, avail=yes, need=no, active=unknown``` Which seems to suggest the highest framebuffer resolution the 901 supports is 800x600, 24 bits.

You can get some interesting information out of these if you pop then into Google Chrome: about:crash about:memory about:stats about:histograms about:dns about:version about:network about:internets about:cache

Log in over SSH and run: vmkfstools -c 50G -d thick /vmfs/volumes/san/vm/thick.vmdk vmkfstools -c 50G -d thin /vmfs/volumes/san/vm/thin.vmdk A ls will show: 50G thick-flat.vmdk 373 thick.vmdk 50G thin-flat.vmdk 398 thin.vmdk However a du will show: 50G thick-flat.vmdk 64K thick.vmdk 1.0M thin-flat.vmdk 64K thin.vmdk Which is, I think, rather neat…

If you want to enable promiscuous network sniffing within a vSwitch the safest way to do it is to create a second port group. Promiscuous mode can be enabled on an existing port group but once this has been done, any device connected to that port group has that ability. Once you have your second port group correctly configured you can attach a monitoring appliance. To do my monitoring I tend to use OpenBSD with tcpdump and then use Wireshark to analyse the data.

Sysinternals Live is a service that enables you to execute Sysinternals tools directly from the Web without hunting for and manually downloading them. dir \live.sysinternals.com\tools\ | fw -Column 4

ans,unans=traceroute(['www.google.co.uk','www.yahoo.com','www.microsoft.com']) ans ans.graph(target="> /tmp/graph.svg")