To send a syslog message from Linux:

echo "<154>Hi Team Unicorn! Rome is up!" | nc -w1 -u 192.168.112.63 514

Install a KMS Server

Tired of being warned that your Win7 is counterfeit? Instead of typing in product keys, use Windows Key Management Service aka KMS. Works well for any Windows 2008/7 network with more than 25 seats (or 6 servers if you're doing only Windows 2008 R2 servers). If you don't hit 25, no one can activate.

To install the KMS service:

1. Install Windows 2008 R2. For me, I've found that using a domain controller to host the KMS avoids any DNS issues. KMS is advertised via DNS.
2. Install the key: slmgr.vbs /ipk
3. Activate the first KMS license: slmgr.vbs DNS name of client username password /ato
4. Verify that your clients can see the KMS server via DNS. From a Windows installation that you want to activate, run: nslookup -type=srv _vlmcs._tcp.
   You should get the KMS server IP and DNS name back.
5. Once that first one is up, boot up at least 24 other Windows machines. Windows clients should automatically register with the KMS server.
6. Check how many Windows clients have registered by running: slmgr.vbs /dlv on your KMS server and Look for the Current Count
7. Once you hit 25, after you try to activate windows, you should get an Activation Successful message. If you don't, Google the error code. Some common errors and solutions are below:

Troubleshooting:

• 0xC004F074 "The Key Management Server (KMS) is unavailable" - you'll get this error if your client's time is more than 4 hours different than the KMS host's time. Change your client's time. Better yet, use an NTP server.  Also ensure that the time zones match (e.g. a client on 10am GMT will error when connecting to a KMS server on 10am PDT).
• 0xc004f038 is good. It means that you can see your KMS server, but you haven't reached your threshold yet. Keep on activating more clients or convert some clients from MAK to KMS.
• To convert existing MAK clients to KMS, run: slmgr.vbs /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 . Don't worry, this key is Microsoft's public KMS client setup key for Windows 7 Pro. For this key and other Windows flavours, check out http://technet.microsoft.com/en-us/library/ff793406.aspx

All KMS commands use slmgr.vbs and they can be run remotely. You don't even need to log in to the client desktops! Useful commands include:

• Activate windows:

  slmgr.vbs [DNS client name] /ato

• Display license info:

  slmgr.vbs [DNS client name] /dli

• Install the Win7 Pro KMS client setup key:

  slmgr.vbs [DNS client name] /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

To run these commands locally (i.e. if you're already on the client desktop), you can omit your credientials and add only the command switch (ex. slmgr.vbs /dli ).

Note that the Windows Server 2008 R2 KMS key will activate W2K8R2 server AND Windows 7 clients. For more details on the licensing scope of KMS keys, check out http://technet.microsoft.com/en-us/library/ee939271.aspx

Advanced Port Scanner v1.3
A small useful port scanner:
http://www.radmin.com/products/utilities/portscanner.php

Uncover Hidden Hardware in Device Manager
When upgrading from VMWare ESX 3.5 -> 4.1, VM hardware versions changed from 4 to 7 which ended up orphaning Version 4 NICs. To get rid of these hiding NICs, run the following from a command prompt:
set devmgr_show_nonpresent_devices=1
devmgmt.msc

Refer to http://oreilly.com/pub/h/3105 for more info.

How to set the time service for your W2K3 Server Domain Controller

To configure your time server, run
w32tm /config /manualpeerlist: /syncfromflags:MANUAL
To update the time, run w32tm /config /update
To verify the time, run w32tm /monitor

Example:
w32tm /config /manualpeerlist:ntp.ubc.ca /syncfromflags:MANUAL

w32tm /config /update

w32tm /monitor

If the right time server is still not being used, check the Default Domain Controllers group policies' Computer configuration/Administrative Templates /System/Windows Time service/Time Providers . Ensure that all three settings listed are set to “not configured”.

User may experience an error message, "the process hppostprocessing stopped unexpectedly with status 13 " in MAC 10.4.x when trying to print.

A couple of people I know have tried to install HP print drivers on their Macs which end up preventing them from printing on our TCP/IP network. One fix is to run the following commands from Terminal:

cd /Library/Printers/hp/filter

sudo chmod 775 hppostprocessing

For more details, refer to:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=412144&prodTypeId=18972&prodSeriesId=412144&objectID=c00736758

Restart the VMWare Management Service

Sometimes VMWare Virtual Infrastructure Client reports that VMs are disconnected. The solution is usually to restart the service that the VI client is connecting to by SSHing into the host machine and restarting the management service by running "service mgmt-service restart".

For more info, check out:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1003631&sliceId=1&docTypeID=DT_KB_1_1&dialogID=24868783&stateId=1%200%2024872576