Ever need to wake up a computer on a subnet that the “magic” packet can’t reach? Use PSEXEC to remote to a powered on computer on that subnet then run WOL.
psexec \\computername -c wol.exe mac_address
(e.g. psexec \\comp1 -c wol.exe D4BDE9989116)
PSTools – http://www.sysinternals.com
When trying to delete a folder you get an error that says, “An unexpected error is keeping you from deleting the folder. If you continue to receive this error, you can use the error code to search for help with this problem. Error 0x80070091: The directory is not empty.”
Problem is the directory is empty. After a reboot you still get the error.
- Right click the drive that the folder is on & click Properties.
- Select the Tools tab.
- In the Error checking frame click Check.
- When prompted click Scan and repair drive. (Damn forgot to take a screenshot)
- On the Your drive was successfully repaired screen click Close.
- Press Additional Functions.
- Press 2 & 8 at the same time.
- Press Additional Functions.
- Press Copier.
- Press Function.
- Press Clear.
- Press PWD-CLR.
- Press OK.
Windows 8.1 Pro with the Hyper-V Role installed. One physical NIC with a static IP address.
Configure an External Virtual Switch bound to the physical adapter.
Virtual machines can get to the Internet just fine but the Hyper-V server cannot.
Hyper-V server can’t even ping Bing.
Hmmmm…can’t even resolve bing.com. Looking at the IPv4 properties of the vEthernet (External) NIC there is no DNS configured.
Add the IP of the router (or whatever DNS server you use) back in for the DNS server(s). Now the Hyper-V server can access the Internet.
When creating the External Virtual Switch a dialog box popped up that said, “Pending changes may disrupt network connectivity. This computer may loose blah, blah, blah”. But then it says, “These changes also may overwrite some static changes. If that happens, you must reapply the static changes to restore network connectivity.”
So there you go. When configuring Hyper-V to use a NIC that has a static IP configured you may loose some or all of it when it moves those settings to the vEthernet NIC.
When booting a Dell OptiPlex 760 to Darik’s Boot and Nuke (DBAN) you receive a few messages/errors that say:
- BIOS EDD facility v0.16 2004-June-25, 0 devices found
- EDD information not available.
- Warning: unable to open an initial console.
Solution – Upgrade the BIOS to A15 then try again.
After rebooting the vCenter server & logging into the vSphere Web Client I noticed that all objects in the Inventory List had a quantity of 0.
A quick glance at the services showed that the VMware VirtualCenter Server, VMware VirtualCenter Management Webservices, & a few others were stopped. When starting the VMware VirtualCenter Server service I received an error that said, “Windows could not start the VMward VirtualCenter Server on ServerName.”
In the Application log there is an Event ID 1000 that says, “The description for Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Failed to initialize VMware Virtual Center. Shutting down… the message resource is present but the message is not found in the string message table.”
There is also a corresponding Event ID 7024 in the System log that says, “The VMware Virtual Server service terminated with service-specific error The system cannot find the file specified.”
Browse to %ALLUSERSPROFILE%\VMware\VMware VirtualCenter\Logs & open the newest vpxd-XX.txt file. Near the end of the file you find some entries similar to:
2014-03-07T19:23:54.477-06:00 [01784 warning ‘Default’] Closing Response processing in unexpected state: 3
2014-03-07T19:23:54.478-06:00 [01784 error ‘[SSO][SsoFactory_CreateFacade]’] Unable to create SSO facade: Invalid response code: 404 Not Found.
2014-03-07T19:23:54.478-06:00 [01784 error ‘vpxdvpxdMain’] [Vpxd::ServerApp::Init] Init failed: Vpx::Common::Sso::SsoFactory_CreateFacade(sslContext, ssoFacadeConstPtr)
Restart the VMware Identity Management Service. Then start the VMware vSphere Profile-Driven Storage Service, VMware VirtualCenter Server, & VMware VirtualCenter Management Webservices services.