Saturday, 11 May 2013

Windows 8 and Wake on Lan

Wake on Lan (WOL) issues with Windows 8

Wake-on-LAN behavior in Windows 8
http://support.microsoft.com/kb/2776718

Windows 8:  In Windows 8, the default shutdown behavior puts the system into hybrid shutdown (S4) and all devices are put into D3. Remote Wake-On-LAN from hybrid shutdown (S4) or classic shutdown (S5) is unsupported. Network adapters are explicitly not armed for Wake-On-LAN in both the classic shutdown (S5) and hybrid shutdown (S4) cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of spurious wakes when explicit shutdown was requested. As a result, Wake-On-LAN is only supported from sleep (S3) or hibernate (S4) in Windows 8.

To resolve this follow the below steps

To disable hybrid shutdown (S4) in Windows 8 (not recommended), use these steps:
  1. Open the Power Options in Control Panel
  2. Select “Choose what the power buttons do”
  3. Uncheck “Turn on fast startup (recommended)"
  4. Select "Save Settings"

Friday, 26 April 2013

How to decommission a Windows enterprise certification authority

http://support.microsoft.com/kb/889250?wa=wsignin1.0

Move DPM_SYSTEM_STATE to other location

When using Data Protection Manager to back-up the system state of your servers you will find that a folder with the name DPM_SYSTEM_STATE is created on your C:\ drive on the protected server. When disk space is insufficient to support this additional data, you can alter the location where this data is stored:

On the Protected Server:
  • Edit the %system drive%\Program Files\Microsoft Data Protection Manager\DPM\Datasources\PSDataSourceConfig.xml file
  • You will find the default the path is %system drive%\.
  • Change it to the appropriate location and save the file.
On the DPM Server:
  • Modify the Protection Group
  • Run Consistency Check on the System State datasource
Thanks to Kapil Malhotra for this tip!

Fixing Java KVM client error with 'Connection Failed'

Java 8u171 disables the use of the 3DES_EDE_CBC cipher. Solution is to reconfigure Java by editing and removing 3DES_EDE_CBC from the follow...