We have repeated the knowledge base article here just in case it is not available on Microsoft’s site.  The original article can be found here

Microsoft’s Article is shown here:

This step-by-step article describes how to use Netdom.exe to reset machine account passwords of a domain controller in Windows Server 2008 R2, in Windows Server 2008, or in Windows Server 2003.

Each Windows-based computer maintains a machine account password history that contains the current and previous passwords that are used for the account. When two computers try to authenticate with each other and a change to the current password is not yet received, Windows relies on the previous password. If the sequence of password changes exceeds two changes, the computers involved may not be able to communicate, and you may receive error messages. For example, you may receive “Access Denied” error messages when Active Directory replication occurs.

This behavior also applies to replication between domain controllers of the same domain. If the domain controllers that are not replicating reside in two different domains, look at the trust relationship more closely.

You cannot change the machine account password by using the Active Directory Users and Computers snap-in, but you can reset the password by using the Netdom.exe tool. The Netdom.exe tool is included in the Windows Support Tools for Windows Server 2003. The Netdom.exe tool is also included in Windows Server 2008 R2 and in Windows Server 2008.

The Netdom.exe tool resets the account password on the computer locally (known as a “local secret”) and writes this change to the computer’s computer account object on a Windows domain controller that resides in the same domain. Simultaneously writing the new password to both places ensures that at least the two computers involved in the operation are synchronized, and starts Active Directory replication so that other domain controllers receive the change.

The following procedure describes how to use the netdom command to reset a machine account password. This procedure is most frequently used on domain controllers, but also applies to any Windows machine account.

You must run the tool locally, from the Windows-based computer whose password you want to change. Additionally, you must have administrative permissions locally and on the computer account’s object in Active Directory to run Netdom.exe.

Use Netdom.exe to Reset a Machine Account Password

//

1. Install the Windows Server 2003 Support Tools on the domain controller whose password you want to reset. These tools are located in the Support\Tools folder on the Windows Server 2003 CD-ROM. To install these tools, right-click the Suptools.msi file in the Support\Tools folder, and then click Install.
   Note This step is not necessary in Windows Server 2008 R2 and in Windows Server 2008 because the Netdom.exe tool is included in these Windows editions.
2. If you want to reset the password for a Windows domain controller, you must stop the Kerberos Key Distribution Center service and set its startup type to Manual.Notes
   • After you restart and verify that the password has been successfully reset, you can restart the Kerberos Key Distribution Center (KDC) service and set its startup type back to Automatic. This forces the domain controller that has the incorrect computer account password to contact another domain controller for a Kerberos ticket.
   • You may have to disable the Kerberos Key Distribution Center service on all domain controllers except one. If you can, do not disable the domain controller that has the global catalog, unless it is experiencing problems.
3. Remove the Kerberos ticket cache on the domain controller where you receive the errors. You can do this by restarting the computer or by using the KLIST, Kerbtest, or KerbTray tools. KLIST is included in Windows Server 2008 R2 and in Windows Server 2008. For Windows Server 2003, KLIST is available as a free download in the Windows Server 2003 Resource Kit Tools. To obtain the tools, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en
4. At a command prompt, type the following command:
   netdom resetpwd /s:server /ud:domain\User /pd:*

   A description of this command is:

   • /s:server is the name of the domain controller to use for setting the machine account password. This is the server where the KDC is running.
   • /ud:domain\User is the user account that makes the connection with the domain you specified in the /s parameter. This must be in domain\User format. If this parameter is omitted, the current user account is used.
   • /pd:* specifies the password of the user account that is specified in the /ud parameter. Use an asterisk (*) to be prompted for the password.

   For example, the local domain controller computer is Server1 and the peer Windows domain controller is Server2. If you run Netdom.exe on Server1 with the following parameters, the password is changed locally and is simultaneously written on Server2, and replication propagates the change to other domain controllers:

   netdom resetpwd /s:server2 /ud:mydomain\administrator /pd:*
5. Restart the server whose password was changed. In this example, this is Server1.

http://support.microsoft.com/kb/911829

GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}

Once that is done, the folder’s icon will change to resemble a control panel and will contain dozens of control options.

I think most of these options are available elsewhere, but this provides a simple, easy-to-use method to access all of them.

On of the most interesting sections of Google Analytics is in the Visitors section and it is called User Defined.  This is an area that allows you to create some customized “tags” or “labels” for any of your visitors.

I could go on and explain all the nitty-gritty details, but guys over at Google Analytics have already posted a very detailed explanation on how to implement this capability and shows how it can provide additional value to the tremendous value that GA already provides.

To review all the User Defined details you just use the links already created in this post.

One of the most useful features of the LogMeIn offering is the ability to setup a secondary user to allow access to one or more computers in your account.  It is pretty easy to setup this feature.

By creating Secondary Users in your LogMeIn account, you can allow remote access to one or more of your computers.   Secondary Users have access only to the computers that you authorize, and you can disable their access at any time.  Secondary Users can not see any details of your LogMeIn account.

To create a Secondary User, follow these steps:

1. Log in to LogMeIn.com using your registered email and password.
2. On the My Computers page, click the Users link on the left side of the screen.  If you do not see the Users link you probably have to change your view to be “Advanced View”.
3. Click the Secondary Users link at the top of the screen
4. Click Add New Secondary User.
5. Enter the email address for the Secondary User that you are adding to you account.
6. If you don’t specifically change the permissions, the secondary user will have access to all computers in your account.  However, you can select specific computers using the Specify Computers option
7. Once done, click Send Invitation.

Note: Secondary Users are required to define their own password when accepting the invitation, and can change it at any time.   The Secondary User will need to know the Windows Username and Password for the computer’s they have received access to.  If the computers are on a domain they can probably login with their own domain logins.

Note: you might need to register at SQLServerCentral.com to gain access to the site to read the above linked article.

Turns out that it is super simple to remove that email address.  Just compose and email and start typing the address.  When you see it appear, just use the arrows to select the one that is incorrect and press the Delete key.  It will be gone forever.  Quick and easy.

If you want to clear the entire email history, you can do the following:

• Exit Outlook
• Run Windows Explorer
• Navigate to the C:\Documents and Settings\username\Application Data\Microsoft\Outlook folder (substitute username with your username)
• Find the file with the NK2 extension and rename or delete it.

If you have two (or more) monitors that are the same height, you could issue the following command:

mstsc /span

When the Remote Desktop application starts up it will ask you what Computer you want to connect to.  Just enter the name or IP address of the computer and you will be connected in full screen mode across your two (or more) monitors.

Some notes from the Microsoft Help about what the /span option does and its limitations:

Matches the remote desktop width and height with the local virtual desktop, spanning across multiple monitors if necessary. To span across monitors, the monitors must all have the same height and be aligned side by side.

In order to save the /span option into the .rdp file you will need to manually edit it:

• Open Windows Explorer, and browse to the folder containing the .rdp file you want to edit.
• Right-click the file > Open With > Choose Program > Notepad (or any other text editing program you have installed on your computer)
• Once the file is open in Notepad go to the bottom of the file and add the following command: span monitors:i:1
• Save the file.

Now your rdp file will automatically span monitors when executed.

If you have any questions about them, drop me a comment here.