To add red to command line when logged in as root add
1. open
/root/.bashrc

2. add
PS1="\[\e[31m\]\u@\h:\w#\[\e[m\]“

To add green to command line when logged in as a normal user
1. open
~/.bashrc

2. Add
PS1="\[\e[32m\]\u@\h:\w\$\[\e[m\]“

There is a great ESX command reference card (aka a cheat sheet) at

http://www.vmreference.com/

There was a good article created last week, about how to create a stable windows 2003 print cluster. The write up is by Yong Rhee from Microsoft.

http://blogs.technet.com/askcore/archive/2008/06/13/how-to-optimize-your-windows-server-2003-print-failover-cluster.aspx

There is a great article how to join Linux systems to AD at

http://blog.scottlowe.org/2007/01/15/linux-ad-integration-version-4/

There are a fiew different ways to change the OEM information in Windows

For Vista (Registery):

Note: Logo Size must be 120×120 and .bmp

Data under System:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ OEMInformation

Data under performance information and tools:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winsat\WindowsExperienceIndexOemInfo

There is also a auto patch way:

http://keznews.com/2539_OEM_Logo_and_Information_for_Windows_Vista_-_Auto_Patch

and

http://stevejobs.blogs.keznews.com/oem-logo-and-information-for-windows-vista-auto-patch/

For other versions of windows

Note: Logo Size should be 120×120 and a .bmp

1. name your logo OEMLOGO.BMP
2. add it to %systemroot%\system (for 95/98/ME) or %systemroot%\system32 (for 2000, XP, 2K3)
3. Create a OEMINFO.INI
4. add it to %systemroot%\system (for 95/98/ME) or %systemroot%\system32 (for 2000, XP, 2K3)
5. You can create two sections [General] and [Support Information] in the INI file

For section [General]

Manufacturer=<text>
Model=<text>

For section [Support Information]

Line1=<some text>
Line2=<some text>
….. (and so on)

Example:

For MOSS 2007 and WSS 3.0 to install the Application Templates (20 pack or 40 pack), you can automate the process to install the files.

1. Right click on My Computer and choose Properties
2. Advanced tab, Environmental Variables
3. In the System variables section, scroll to Path, highlight it and choose Edit
4. In the Variable value box, go to the very end, put a semicolon, then paste in:
   C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\
   Note: There is no space between the semicolon and the path.
5. Click OK to close the windows
6. Save this as template1.bat:
   for %%f in (*.wsp) do stsadm.exe -o addsolution -filename %%f
   Note: Save this in the same folder as your WSP files
7. Save this as template2.bat:
   for %%f in (*.wsp) do stsadm.exe -o deploysolution -allowgacdeployment -immediate -name %%f
   Note: Save this in the same folder as your WSP files
8. You can either run this in the Windows GUI or via Command Prompt.

Note:  You can get the template from http://www.microsoft.com/downloads/details.aspx?FamilyID=5807b5ef-57a1-47cb-8666-78c1363f127d&displaylang=en

Backing up a sharepoint site (for the filename you can use .bak)

Stsadm –o backup –url <SiteURL> -filename <FileName>

Restore a sharepoint site from backup

Stsadm –o restore –url <restoretoURL> -filename <filetorestorefrom>

Note: location of stsadm is http://theregime.wordpress.com/2008/05/20/the-location-fo-stsadm-in-wss-30/

We have about 20 2.5.x ESX hosts in VIC 2.5 update 1 that have yet to get converted.

Problem 1: you cant make changes to VM running on the 2.5.x hosts from VIC

Fix 1: have to lanuch the MUI and make changes like power on, power off, and name changes from the MUI, Then you get Problem 2: once you update the MUI now VIC has the wrong information and it never updated, so you get FIX 2: Disconnect the 2.5.x host and reconnect the 2.5.x host and the information will be up-to-date in VIC.

WARINING: Changing the registry or deleting services could leave your system unusable know what it is before changing or deleting it.

Removing a service

1. You can run a command line

sc delete {service name}

2. Delete the key out of the registry

HKEY_LOCAL_MACHINE/system/CurrentControlSet/Services

Note: You can find the service name from the service properties and on the general tab.

If you plan on install templates in Windows Sharepoint Service (WSS) you will need the stsadm.exe, but it does not tell you the location of the tool. So the location is

c:\Program Files\common files\microsoft shared\web server extensions\12\bin

Along with other WSS tools