User Powershell to test a password

Sometimes you need to test to make sure you’re entering the correct the right password. Be it a service account while installing a app or testing a password reset.

The start-process cmdlet is used to start one or more processes on a local computer. Get-Credential gets an object based on username and password. Use it to open an application and test the credentials.

Open a Powershell prompt:

start-process notepad.exe -credential (Get-Credential acme\johnquser)

start-process

Enter the credentials you’re trying to test. If you’re correct, notepad will open.

enterpassword

notepad

If not, a password reset is in order.

 

 

When .NET wants to be 4.5.2

Someone in the application group said that they wanted .NET downgraded from 4.5.2 to 4.51. I did as I was asked and then in the next few days, I got another call telling me that 4.5.2 was back.  The application they are running is not supported in 4.5.2.

This system isn’t managed by WSUS so Windows update did what it was designed to do.

Here is a link to block the update of .NET to 4.5.2:

How to temporarily block the installation of the .NET Framework 4.5.2

Be sure to backup the registry before you begin.

Browse to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\

Add a new Key called WU, then add a new DWORD value named BlockNetFramework452
Modify it and set it to 1.
Exit the registry.

 

 

Powershell Script with Spaces in the Path

I’ve been trying to write this script that has a path to a .dll with a space in it. Every example I came upon either used single quotes, double quotes or nothing at all.

I tried

Import-Module -name 'c:\program files\EqualLogic\bin\EqlPSTools.dll'

and

Import-Module -name "c:\program files\EqualLogic\bin\EqlPSTools.dll"

There are 2 ways that worked:

Import-Module -name c:\program` files\EqualLogic\bin\EqlPSTools.dll

Using the back tick character, below the tilde on a Windows keyboard. Not to be confused with the opening single quote.

keyboard

and

Import-Module -name ("c:\program files\EqualLogic\bin\EqlPSTools.dll")

For more on commonly confused characters, check out this page.

VDP backup fails due to error consolidating disks on VM

We are running VDP 5.8 on vSphere 5.5. One of the appliances failed to backup a VM last night. Checking the VM in the client, there is a message to consolidate the disks. I attempt to consolidate by right-clicking on the VM > Snapshot > Consolidate and it failed with this error:
locked

I checked the vmware.log file for the VM and saw this error:
2015-09-15T03:00:29.146Z| vcpu-0| I120: DISK: Failed to open disk for consolidate '/vmfs/volumes/5490a09a-eb6682ee-affb-bc305bef5520/mobxxxxxx/mobxxxxxx-000002.vmdk' : Failed to lock the file (16392) 8162

I check the settings on the VDP appliance and notice that the VMDK that belongs to the vm is attached.

extra-vdp-disk

Shut down the VDP appliance and remove the disk. Making sure to only remove from virtual machine and NOT remove from virtual machine and delete files from disk.

remove-extra-vdp-disk

Run the consolidation and if it succeeds, re-run the VDP backup on out of date sources to remediate your failed backup.

VMworld 2015 in the books

I’m coming off another vmworld and this one was pretty good. This year, we were back in San Fransisco at the Moscone Center. There were plenty great sessions, engaging speakers, opportunities to meet up with folks from past vmworld’s, networking, vendor parties and the party in AT&T park was the icing on the cake. The VWoman session was really enlightening as usual, but it was the same time as the hall crawl and it was not easy to blow that off. I really don’t like that they put both up against each other. It’s like they wanted the men to have the hall crawl all to themselves. #fail

One key highlight was seeing a woman I met at VMworld 2 years ago present a session this year. Sonya Ryherd from Cox Automotive did a session with her colleague, Chris Nakagaki, called, Introduction to Monitoring the Public Cloud with vRealize Operations Manager. They did a great job. It was one of those sessions where you walked away knowing something you didn’t know before. I was very intrigued and learned even more about what vRealize Operations could do. I’m installing it ASAP!

It’s very invigorating to walk away from the conferences with a renewed sense of direction and passion in what I do. Along with finding out about the new technologies and direction they’re headed, you discover features, flings, tips and tools that you’ve never knew existed. That’s like finding the prize in the cracker jack box. You knew it was there, but you didn’t know what that little gem would be.

The 1st things I’ll do when I get back to the office.

  • Plan for the upgrade to vSphere 6.0.
  • Upgrade tools to v10 before the sphere upgrade.
  • Deploy my ESXi lab in the cloud using Ravello & get ready for the VCP6 exam in 2016.
  • Install our newly purchased vRealize Operations

All in all,  a really good time this year, dare I say the best VMworld yet for me.  I ate at a number of wonderful restaurants:

  • The Cavalier
  • Flour + Water
  • Shalimar
  • Brenda’s Soul Food
  • Green Papaya (not wonderful, but I got my sushi fix)
  • Chipotle (like, who doesn’t eat here when at VMworld?)
  • Scoma’s
  • Ghirardelli’s

I won some cool swag:

  • Signed Tour de France jersey
  • $40 VMworld store gift card
  • 2 Starbuck’s gift cards
  • FitBit HR

And got plenty of t-shirts and swag to drag back to the east coast.

I have a ton of photos, but I’ll post just one.

A great way to end a day at VMworld

One sad note about the conference….I’m sad that It’ll be in Las Vegas next year, but I’ll try to be there. I’m not a woman that likes Hades very much.

See you next year (maybe)!

BSOD on a Windows VM bugcheck code 24

A VM that is running Windows 2008 R2 has experienced a BSOD. The application owner notified me and sent me some useful information.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.400.8
Locale ID: 1033
Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF88006C34E28
BCP3: FFFFF88006C34680
BCP4: FFFFF880014E81B2
OS Version: 6_1_7601
Service Pack: 1_0
Product: 400_3
Files that help describe the problem:
C:\Windows\Minidump50415-20202-01.dmp
C:\Users\servername\AppData\Local\Temp\WER-42663418-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 Good info here, but with all BSODs, you should look at the dump file for more definitive information.

I grabbed the dump file, and downloaded Windows SDK. During the install, I unchecked all the boxes except the Debugging Tools for Windows and installed.

Features to Install

Launch WinDGB (x64) as administrator. The first step is to configure the symbol file path. It can be any folder on your server, just create an empty one and go to File > Symbol File Path.

In the symbol search path, I entered the following and clicked OK.

SRV*c:\tmp\symbols*http://msdl.microsoft.com/download/symbols

Symbol Search Path

Save the workspace. File > Save Workspace

Opened the dump file. File > Open Crash Dump.

Open Dump File

Before you proceed, read the info under the bugcheck analysis. It tells you what probably caused the error.

NTFS.sys

Click the link in the Bugcheck Analysis section, !analyze -y to get more information.

Read through the info. Note the following:

  • Process Name
  • Bugcheck_str
  • Image Name
  • Area right above the debugging details

At the very top you’ll see a message and some arguments.

Analyze

At the kd> prompt at the bottom of the debugger, enter

.bugcheck

Bugcheck command

In the analysis you see the Arguments. Do a .cxr on the 3rd argument as it suggests.

arguments

.cxr fffff88004523680

CXR command

CXR output

Next,

Run the kb command for a more informative stack trace.

Run KB command

There are now a few pieces of information to hone in on.

  1. The bug check code
  2. The stack track text

Look up the bugcheck code here on the msdn bug check code reference page.

https://msdn.microsoft.com/en-us/library/windows/hardware/hh994433%28v=vs.85%29.aspx

Google the stack trace text and this vmware KB article # 2115997 comes up.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2115997

This appears to be a known issue with a few versions of vmware tools:

I looked in the vmware.log file for the entries mentioned and they matched.

vmware-logs

The image name on the dump file referenced vds.exe and this VM is running tools version 9.4.11. This issue only appeared since the tools upgrade when we upgraded to 5.5 Patch 4

To confirm what version of tools you’re running, go to the VM and in the notifications bar, right click on the icon and select About  VMware Tools

VMware Tools version

Time to downgrade tools.

Find the tools ISO that will have a version that is not listed in the KB, but one that is compatible with your version of vsphere.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1036810

https://packages.vmware.com/tools/versions

Search for your current version and find the one closest to it that is not affected with this issue.

Version of tools to downgrade to

You’ll have to uninstall the current version of tools before installing older version. It will require a reboot.

The hardware version will not be an issue with this versions of tools, but confirm that for your specific environment.