If it seems like you just can’t get the screen bright enough, try this:
The problem is due to Adaptive Brightness.
This is what you need to do if the screen does not go past a certain brightness level on Windows 7 or Windows 8.
- Go to the Start bar on the Desktop and move your mouse all the way to the right to find the Battery icon.
- Click the battery icon. A little popup box should show up. Click “More Power Options”
- Select your plan and click “Change Plan Settings”
- Click “Change Advanced Power Settings”
- Scroll down to Display and click the little + sign next to it.
- Scroll down to “Enable Adaptive Brightness” and click the little + sign next to it.
- Change “On Battery” and “Plugged In” to make sure it is Off for both of them.
In a response to user outcry, Microsoft has made Office 2013 licenses transferable.
Updated transferability provision to the Retail License Terms of the Software License Agreement for Microsoft Office 2013 Desktop Application Software:
Can I transfer the software to another computer or user? You may transfer the software to another computer that belongs to you, but not more than one time every 90 days (except due to hardware failure, in which case you may transfer sooner). If you transfer the software to another computer, that other computer becomes the “licensed computer.” You may also transfer the software (together with the license) to a computer owned by someone else if a) you are the first licensed user of the software and b) the new user agrees to the terms of this agreement before the transfer. Any time you transfer the software to a new computer, you must remove the software from the prior computer and you may not retain any copies.
reposted from: http://blogs.office.com/b/office-news/archive/2013/03/06/office-2013-retail-license-agreement-now-transferable.aspx
I found this while trying to get a Cisco ASA vpn tunnel up. For some reason the secure mobility anyconnect tunnel would not encapsulate dns or dhcp traffic. This prevented me from being able to access my domain. I figured I’d give the 64-bit legacy client a try and after the fix below, it worked fine. Here is what you need to do after you install the legacy client to get it to work.
Reposted from: http://social.msdn.microsoft.com/Forums/en-US/windowsdeveloperpreviewgeneral/thread/6fe817f3-27fe-4068-995a-aced4508ee3e/
Just to update, the legacy Cisco VPN client (5.0.07.0440 for x64, 5.0.07.0410 for x86) is working for some people. You need to apply a small workaround as explained below –
· Open Registry editor by typingregedit in Run prompt
· Browse to the Registry Key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA
· Select the DisplayName to modify, and remove the leading characters from the value data upto “%;” i.e.
o For x86, change the value data from something like “@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to “Cisco Systems VPN Adapter”
o For x64, change the value data from something like “@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to “Cisco Systems VPN Adapter for 64-bit Windows”
· Try connecting again
Please do revert back if this solution does not work.
This is a test Jetpack post from Scheh.com