How to find the processes running on a remote server AND how to find the services associated with svchost.exe.

We had a server which was running at 100% cpu utilization.  Unfortunately,

we were unable to RDP into the server to identiify the offending process.

To get the process details of a remote server, I used PsList.exe.  PSList is a part of a suite of tools which can be downloaded here:

http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx

In this case, it was svchost.exe.   Since there can be multiple svchost processes running, take note of the Process ID (Pid).   svchost.exe can contain other individual services.  To find out what they are, use tasklist and match up the PID to the offending service.  (In this case 924)

tasklist /s myserver /svc /fi "imagename eq svchost.exe"

Quick Tip: Faster way of logging into a server using a local account

I was working with a co-worker and noticed he was logging into a w2k8r2 server using a local account and typing in the entire server name and user account.

Instead of typing in the local server name just use the following:
.\

Faster, simpler and more accurate!

Powershell fix: The trust relationship between this workstation and the primary domain failed

We're a heavily virtualized shop.  To save on host resources, we often shutdown Test/Dev/Staging/template servers that are not in use.

One of the drawbacks of this is I would often receive the following error when powering on a server that has been off the network for a while:

The error is often due to the computer password no longer matching the one in Active Directory.   This is caused by the computer being offline for a while, or when reverting to an old snapshot or backup.

In the past, I've been removing the server from AD and rejoining the domain.  As the number of these occurances have increased, I've been leveraging powershell to fix this issue as quickly and efficiently as possible. 

To resolve this issue, log into the offending server using the local admin account.  Launch Powershell as an administrator and run the following cmdlet:

Reset-ComputerMachinePassword [-Credential <PSCredential> ] [-Server <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]

For -server, enter your the domain controller.

Enter the password when prompted and reboot.  You will now be able to log into the server using domain credentials.

**Update**  
If you're using a version of powershell below 3, you'll receive the following error:

Reset-ComputerMachinePassword : A parameter cannot be found that matches parameter name 'credential'.

In that case, I typically fall back to the old Netdom command:

netdom resetpwd /s:server /ud:domain\User /pd:*
or 
netdom resetpwd /server:server /userD:domain\User /PasswordD *

Security Warning - Run only scripts that you trust.

Ok, I'm embarrassed about this one...  I was receiving the following prompt and it took me a sec to sort this one out.

To disable the above warning, perform one of the following:
1. Unblock the file through the GUI:

 

2.  Use the Powershell unblock-file cmdlet

Done!

How to schedule PowerShell Scripts with Parameters

The global VMware admins at the company I work at needed a mechanism to monitor the membership of AD groups associated with the virtual environment.

The following script by Francois-Xavier Cat fit the bill perfectly!  (Thanks again!)
http://www.lazywinadmin.com/2013/10/powershell-monitor-and-report-active.html

Setup was simple and it ran perfectly in the Powershell ISE.  However, when it came time to scheduling it in Windows Task Scheduler, I had a bit of trouble.  It turn out, escape characters (ex. \) are needed for it to run properly.

In the Program/script field enter the following:
C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe

In the Add arguments field, the following was entered:

-command "D:\MyFolder\TOOL-MONITOR-AD_Group_20131127.ps1 -group \"group01\",\"group02\",\"group03\" -EmailFrom test@MyDomain.com -Emailto \"user01@MyDomain.com\",\"user02@MyDomain.com\",\"user03@MyDomain.com\" -emailserver smtprelay.MyDomain.com

Powershell: Verifying the vCenter Services are running

This past weekend, I was unable to log into our vCenter server.   To quickly get the status of vCenter Services, I ran the following commands.

get-service -cn YourvCenterServer -DisplayName VMware*

 Unfortunately, the vCenter SSO service has a different service naming convention (gsv is an alias for get-service):

gsv -cn YourvCenterServer -DisplayName vCenter*

It turns out, the volumes associated with the sql server housing the vCenter DB were being moved from the Equallogic to the Compellent array....

Graphics Card Fix: How to Revive a Misbehaving Card

AKA Oven fix, Oven mod, Oven trick, "Baking your Video Card"

I recently had issues with an EVGA 8800 GTX Graphics card.  There was absolutely no video output, just a black screen upon power on.

I replaced the power supply with a new 700 Watt unit, updated the BIOs, and confirmed the problem followed different know good computers. 

A Google search showed a few cards (and XBOX 360s) that were repaired by cooking it in an OVEN!

Well, I had nothing to loose, so I gave it a go.  I was surprised that IT WORKED! 

My "Non-Scientific" explanation - Apparently, over time, the tiny electrical connections/solder begins to crack and no longer makes contact to the components on the board. Baking the card melts the solder and "reforms" the contact.  Below are the steps I performed.  

***Perform the following fix at your own risk.  I am not responsible for any damage or injury while performing the steps below***

1. Remove the fan and heat sink from the card.  On the EVGA 8800 GTX there were 

11 x large screws

2 x black screws near the exhaust port.

1 x power wires to the GPU fan

2.  Clean off the old thermal paste using isopropyl alcohol.

3. Place aluminum foil on a cooking sheet.  I rolled up 4 aluminum foil "balls" to prop the card off the cooking sheet.  Keep GPU side up.  (Ball placement didn't seem to matter.  Just as long as the card was horizontal and not sitting directly on the cooking sheet)

4.  Preheat oven to 385 degrees.  Place the card into the oven for 8 minutes.  Use fans to ventilate the area.  I used a fan and channeled the air out an open window. 

5. After 8 minutes, crack open the door and let stand for 20 minutes to allow the card to slowly cool down in the oven. 

6. After 20 minutes, removed the card from the oven and allow it to cool completely.

7. Clean the gpu and fan mating surface one last time.

8. Place a small amount of thermal paste on the GPU.  I typically spread the paste using a sandwich bag.

9.  Reinstall the fan/heatsink back onto the card.

10.  Reinstall the graphics card back into the computer and test functionality. 

Thanks it! Good luck, the procedure above worked for me.  As vendors always say "Your mileage may very"