Let's try to avoid one...

Copy and Paste is not working on my Remote Desktop Connection

Download PDF

Have you ever had copy and paste give out on you during the day in one or all of your rdp windows? If so there is an easy solutions to get it working again. Basically the copy/paste over rdp process has crashed on you.

Just bring up task manager on the target (the one you are remoted into) system and look for the process rdclip and end task on it– they system will then auto-restart the process in that background the next time you try to cut/paste and the feature will function again.

WSUS patches will not install – Large CBS log file

Download PDF

There are several instances and variations but your automatic updates will indicate “files in use/locked” information or “corrupt patch” information. This is almost always accompanied by a very large CBS log file. (%windir%\logs\cbs\cbs.log)

Windowsupdate.log file may indicate something similar to this:

2014-11-07 15:42:17:069 328 e9c Setup WARNING: CBS EvaluateApplicability returned error, error = 0x80070BC9
2014-11-07 15:42:17:069 328 e9c Setup FATAL: Applicability evaluation for setup package “WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226″ failed, error = 0x80070BC9
2014-11-07 15:42:17:069 328 e9c Setup FATAL: SelfUpdate check failed, err = 0x80070BC9
2014-11-07 15:42:17:069 328 e9c Agent * WARNING: Skipping scan, self-update check returned 0x80070BC9
2014-11-07 15:42:17:069 328 e9c Agent * WARNING: Exit code = 0x80070BC9
2014-11-07 15:42:17:069 328 e9c Agent *********
2014-11-07 15:42:17:069 328 e9c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]

All of these things usually indicate a corrupt or pending installation that is now preventing further updates from applying– a very reliable solution to these problems has been to run the following command.

C:\Windows\system32 sfc /scannow

It may take a few minutes for the utility to run. Once complete reboot the system and rerun auto updates. If the error messages continue to repeat the above steps

Depending on how extensive the roll back is it can take many (6+) sfc /scannow and reboots for your update log to successfully replay and fix the problem.

vSphere HA Waiting for cluster election to complete Operation timed out

Download PDF

Sometimes when adding a new ESXi host to to a 5.x cluster you may get the following error. The solution that has been consistently proven relaible is to disable HA at the cluster level and then re-enable it. When it comes back on line HA is available on all hosts including the one that was giving you trouble

Converting external drive from FAT32 to NTFS

Download PDF

The process is usually straight forward {convert driveletter:FS/NTFS} but not so when using an external USB attached drive. Usually during the conversion initialization you will receive the following error:

$ Convert cannot run because the volume is in use by another
process. Convert may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.

After you dismount the drive you get:

$ Convert cannot gain exclusive access to the K: drive,
so it cannot convert it now. Would you like to
schedule it to be converted the next time the
system restarts (Y/N)?

This is where it gets fun–if you choose to restart the conversion will fail, as it will try to run before the USB external drive has had time to initialize–thus the process fails.

So lets try a different approach:

C:\ convert k:/fs:ntfs /NoSecurity /X
The type of the file system is FAT32.
Enter current volume label for drive K: MyDrive
Volume Steve_Media created 1/20/2010 11:32 AM
Volume Serial Number is 014D-A8B6
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
117,161,008 KB total disk space.
272 KB in 7 hidden files.
848 KB in 43 folders.
49,333,936 KB in 2,295 files.
67,825,936 KB are available.
16,384 bytes in each allocation unit.
7,322,563 total allocation units on disk.
4,239,121 allocation units available on disk.

At this point you will receive an error about a dirty file system

$ This drive is dirty and cannot be converted. You will need to
clear the dirty bit on this drive by running CHKDSK /F or allowing
AUTOCHK to run on it the next time you reboot.
The conversion failed.
K: was not converted to NTFS

This is fine–we will just flip the dirty bit “off” by running the following:

C:\ chkdsk k: /F
The type of the file system is FAT32.
Volume Steve_Media created 1/20/2010 11:32 AM
Volume Serial Number is 014D-A8B6
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
117,161,008 KB total disk space.
272 KB in 7 hidden files.
848 KB in 43 folders.
49,333,936 KB in 2,295 files.
67,825,936 KB are available.
16,384 bytes in each allocation unit.
7,322,563 total allocation units on disk.
4,239,121 allocation units available on disk.

So now lets rerun the original convert command:

C:\ convert k:/fs:ntfs /NoSecurity /X
The type of the file system is FAT32.
Enter current volume label for drive K: MyDrive
Volume Steve_Media created 1/20/2010 11:32 AM
Volume Serial Number is 014D-A8B6
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
117,161,008 KB total disk space.
272 KB in 7 hidden files.
848 KB in 43 folders.
49,333,936 KB in 2,295 files.
67,825,936 KB are available.
16,384 bytes in each allocation unit.
7,322,563 total allocation units on disk.
4,239,121 allocation units available on disk.
Determining disk space required for file system conversion...
Total disk space: 117218241 KB
Free space on volume: 67825936 KB
Space required for conversion: 214495 KB
Converting file system
Conversion complete

Congratulations on converting to NTFS and external drive.

Windows time server setup

Download PDF

Setting up a reliable time source is must in any environment. In the MS Windows Active Directory world this actually can not be found in the GUI or via a wizard. We gotta go to the dreaded command line. :)

It’s actually fairly straight forward. Please note that it must be run to the BDC FISMO role holder.
If you don’t happen to know where the BDC role resides use the following command

C:\ netdom /query fsmo

Okay now onto the time-server setup.

Lets stop the time service:

C:\ net stop w32time

Next we will specify some items with some switch options–basically we are telling it we have a manual peer list (you can always see the full definition by doing a

C:\ w32tm ?

Let us specify our peer list.

C:\ w32tm w32tm /config /syncfromflags:manual /manualpeerlist:”timeserver1.org, timeserver2.org”

Next we have to advertise out that we are reliable time source to our client workstations

C:\ w32tm /config /reliable:yes

Restart the time service on the BDC

C:\ net start w32time

If everything went well you should see valid time synchronization information from your peer target by running the following command.

C:\ w32tm /query /configuration

See that wasn’t too hard…

Windows box fails to dynamically register its DNS with no errors recorded in Event Viewer

Download PDF

Sometimes it is the simplest things that get you.  I was asked to troubleshoot a system that would not register into DNS after a domain migration. The system could ping its new gateway and the new DNS servers–telnet showed access to the new DNS boxes on port 53 and name resolution was functioning correctly other than the fact that the system would not register itself in DNS.

Trying to force registration from the command line with

C:\ ipconfig /registerdns

yielded no positive results.  Matter of fact it yielded no results at all in Event Viewer.  Strange at the very least it should show errors. Okay lets break-out wireshark and see what happening…

Setup wireshark, issued ipconfig /registerdns and capture indicated that we were not sending any DNS queries out from our server.  Very strange, so lets take a closer looks at our NIC and see if we missed something.

Drilling down to Advanced TCP/IP Settings and in the DNS settings tab we found our culprit. Someone had unchecked the “Register this connection’s address in DNS” check-box.  So even if we issued the command manually to force DNS registration

C:\ ipconfig /registerdns

the NIC was ignoring it.  Appears that in this instance the GUI setting overrides our command line process.