Category: Windows

WIDI/Miracast/Screenbeam stopped working (Resolved)

I have only run into this on Dell systems, but the fix should be the same for others minus Dell Command update.

  1. Run all Windows updates
  2. If it’s a Dell pc, run dell command update and continue running command update until all hardware updates are complete (may take several reboots)
  3. Download and run Intel Driver and support assistant (Dell systems may complain on display driver, that’s is OK to skip if it complains)
  4. When all drivers have been updated, make a note of you display driver
  5. In device manager, goto Display adapters, right click on your display adapter and select uninstall device. MAKE SURE YOU ALSO SELECT DELETE THE DEVICE DRIVER FROM THE SYSTEM.
  6. Reboot and everything should work

I didn’t have to reinstall the display adapter driver on a Dell Latitude 7480

On Windows 10, to connect to wireless display, select the windows key + P, then click connect to wireless display.

STOP 0x0000007B Resolved on P2V’d Windows SBS 2011

***The following was on a Hyper-V vm, but this also applies to VMware.***

****This should work on most versions of Windows (doesn’t have to be SBS)****

The other week we picked up a new client with an emergency issue. They had an SBS 2011 Server on failing hardware. The hardware was so bad that we didn’t think it would last until the replacement server would arrive. We had an older Server that had enough power to handle their server virtualized until their new hardware arrived. So I started the virtualization process. This is where the fun began. (There were several issues minor issues, but I’ll stick to the major problem here.)

After creating the vm without any disk drives, I attached the newly created drives and powered up the vm and was greeted by the BSOD: STOP 0x0000007B.

Luckily there is an easy fix for this and  you don’t need restart the p2v.

  • Boot the vm off any Windows CD/DVD (Windows 7 & up. Doesn’t have to be the same OS as vm. You could also mount the drive on the host or another vm. If you mount the drive, just run regedit)
  • After booting off OS cd, when you encounter the language selection, hit Shift-F10 for a command prompt
  • At the command prompt, run regedit
  •  In regedit, highlight Hkey_Local_Machine
  • With Hkey_Local_Machine highlighted, goto File, and Load Hive
  • In Load Hive, select the drive letter where Windows OS was installed (C: in this case), then go to: Windows\System32\config\system
  • Name the Hive whatever you want (IE: recovery)
  • Expand HKEY_LOCAL_MACHINE\recovery\ControlSet1\Services\intelide
  • Change the data for value “Start” from “3” to “0”
  • Now goto File and “Unload Hive” (If you run into issues make sure Hkey_Local_Machine is highlighted)
  • Exit regedit and reboot the machine and you’re good to go

If you still have issues after reboot, check the following keys and set them to:

Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3

Resolving issues after migrating Windows 7 to new hardware (BSOD Stop 7B 0x0000007B)

Awhile ago, I had a client that had purchased several of the same laptops for training purposes.  Since all of the laptops were the same make and model, I setup 1 of the 10 as a master image that I had locked down so the trainees had limited access to the pc. Any changes made are automatically wiped after logout/reboot. For faster deployment of the laptops, I had created an image of the first laptop via Clonezilla (I am a big fan of Open Source).

A few years had gone by and there was an issue with one of the laptops. We checked the warranty status and found it was out of warranty. Rather than pay for repairs, it was cheaper to find a replacement on Amazon. Unfortunately, the one on Amazon had a different processor (not that big of a deal).

The new laptop arrived and I pushed out the image to the replacement laptop and when it booted we were greeted with the BSOD Stop 7B 0x0000007B. Rather than reload and reconfigure Windows from scratch I used a tool I had used in the past to help with this exact issue: fix_7hdc.vbs. To resolve this:

  1. Download fix_7hdc.vbs and copy the .vbs to a USB drive
  2. restart the pc.
  3. When the pc is restarting keep tapping the F8 key.
  4. When the Advanced Startup Options Menu appears, Select “Repair My Computer”
  5. In that window, select “Command Prompt”
  1. Insert your USB drive
  2. To find the drive letter of your USB drive via DOS prompt type: wmic logicaldisk get name,description
  3. Once you have the drive letter, goto that drive: e:
  4. Run the script via: cscript fix_7hdc.vbs /enable /search
  5. When the script is done, you are safe to reboot.
  6. Windows made it quite a bit further after reboot, but it still had issues so I rebooted into safe mode and logged in as the administrator and let Windows Find and install the drivers it was able to on its own. When completed I rebooted to Windows and downloaded the rest of the needed drivers and installed the latest Windows updates.

Unable to activate BitLocker after imaging Surface Pro or Surface Book

I ran into the following error after pushing an image to a Microsoft Surface Book and configuring the imaged device for a new user. I tried to Turn on BitLocker and immediately saw:

This device cannot use a Trusted Platform Module.  Your administrator must set the “Allow Bitlocker without a compatible TPM” option in the  “Required additional authentication at startup” policy for OS volumes

During the imaging process I had turned off TPM via BIOS, so I rebooted into BIOS ad made sure TPM was enabled. Next I saved and exited BIOS and restarted. WIth TPM enabled in BIOS I did the following:

  1. Entered Device manager: (Type device  Manager in Start Menu)
  2.  In Device Manager, look for “Security Devices” (If you don’t see “Security Devices”, click on “View” and “Show hidden devices”.
  3. Under Security Devices you should See “Trusted Platform Module 2.0” or similar
  4. Right Click on that and select Properties
  5. Mine showed the device was not detected
  6. I then clicked on cancel (In the TPM Properties screen)
  7. I then Right Clicked on TPM module and selected “Uninstall device”
  8. This required a reboot which I did.
  9. After reboot I checked the device manager and TPM was shown as working properly. I was then able to turn on and configure BitLocker

VMWare: How to add RDP rule to esxi firewall via cli

Sometimes I need to ssh jump to esxi host and tunnel RDP to an internal host across the ssh session

Backup:
cp /etc/vmware/firewall/service.xml /etc/vmware/firewall/service.xml.bak

chmod 644 /etc/vmware/firewall/service.xml

chmod +t /etc/vmware/firewall/service.xml

vi & enter towards the bottom of service.xml (below 0037):

<!– MY RDP –>
<service id=’0038′>
<id>myrdp</id>
<rule>
<direction>outbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>3389</port>
</rule>
<enabled>false</enabled>
<required>false</required>
</service>

chmod 444 /etc/vmware/firewall/service.xml

esxcli network firewall refresh

esxcli network firewall ruleset list

esxcli network firewall ruleset set -e true -r myrdp

Now feel free to RDP via ssh tunnel. I usually disable the rule after via:

esxcli network firewall ruleset set -e false -r myrdp

Shadow an RDP session

I was working on migrating VM’s via Hyper V cluster failover remotely, and a college asked if there was a way to Shadow. We tried both connecting to 1 host via logmein with no luck. I searched and found a way to shadow via RDP.

1.) I was log’d host via logmein (could easily be RDP)
2.) I then created another domain admin user called test since I was on as administrator. They logged into another host on the same network via logmein as the test user
3.) Then they RDP’d as the user test to the server I was logged into as administrator
4.) I opened remote desktop services manager and looked to see the session number administrator was logged in as (it was session 3)
5.) They opened command prompt (right clicked run as administrator). In the command prompt they typed: shadow 3
6.) I was prompted “Do you want to relinquish control” which I did.
7.) They could then see my desktop and do whatever in it, but I couldn’t see
8.) I X’d out and reconnected and we were golden.
9.) + stops the shadow

For more info, see: http://support.microsoft.com/kb/278845

#Windows #RDP

Exchange 2010: All db’s unmounted error -1032 file locked

A client had issues with their exchange server tonight…. All the mail DB’s were unmounted.

When I tried mounting the db’s exchange immediately shot back errors. I then tried running a soft recovery (http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/)of the exchange dbs as the logs were all ok, but I received a strange error from eseutil when I tried recovering: operation terminated with error -1032 file locked

I then stopped all exchange services to ensure exchange didn’t have a lock and retried still getting the same error. I then tried to write to the drive holding the logs and I was unable to write to it…. I then verified free space which was good, SAN for issues…it was OK. I then rebooted and retried thinking it was a fluke…no go. I rebooted into safe mode and ran:

diskpart

list volume

select volume 2

Ran the command:

attributes volume clear readonly

I did this on all volumes, made sure I could write to them all then rebooted and tested exchange satisfactory.

Force static IP clients to move to DHCP

The following will set the client to use DHCP:

netsh interface ip set address “Local Area Connection” dhcp

Unfortunately, you will need to do the same with DNS as well (otherwise it remains statically assigned)

netsh interface ip delete dns “Local Area Connection” all

Place that in GPO as a startup script after testing.