Google Chrome for Android (Ice Cream Sandwich) has been updated to allow users to be able to toggle between mobile/desktop view whereas before it only supported mobile view.
http://chrome.blogspot.co.uk/2012/04/chrome-for-android-update.html
Go checkout it out at Google Play (previously Market), only works on Ice Cream Sandwich devices so far.
Every fancied changing your Windows 7 logon screen background? take a look at the following blog post:
http://frustrateditengineer.wordpress.com/2012/03/03/windows-7-logon-screen-background-changer/
So I had a Acer netbook 10.1 lying around and thought I would attempt to install Windows 8 so I could get a true experience (minus the touchscreen) of the operating system.
All went well during the installation, until I decided to open up the Store and download some apps only to be greeted with “This app can’t open, The screen resolution is too low for this app to run, change your screen resolution” This occurred for any of the built in apps as well.
Easy to resolve I thought, I’ll just change my screen resolution, except it was already set at the maximum resolution of 800×600.
Windows 8 even states on the screen resolution page that screen resolutions lower than 1024×768 that the apps may not open.
So to conclude Windows 8 seems like it doesn’t like devices with screen resolutions lower than 1024×768 to work properly. Not a big issue, I can still continue to test on VMware Workstation 8. If anyone does know a workaround please let me know (I haven’t done a lot of research for a solution).
Update:
It would seem there’s a way to change the resolution via the registry.
Change the “Display1_DownScalingSupported” setting
I would recommend backing up the registry first, and being careful… but seeing as your probably testing Windows 8 like me… you may just want to take the risk!
To do this, fire up the registry via Windows Key + R to get to the run box, type regedit and click ok.
Then CTRL + F to open the find box and type “Display1_DownScalingSupported” – click Find Next.
Once found you will need to change the value from 0 to 1. There may be more than one “Display1_DownScalingSupported” in the registry, so hit F3 (find next) and change all the values from 0 to 1. On my netbook there was only one option. Others have reported more than one.
Once the values have been changed, restart the netbook and you should be able to change the resolution to a higher value.
Now the apps within Windows 8 should open! 
Today one of my colleagues was trying to create an image of one of our new Dell machines whilst in the process he tried to use Windows Update and was instead redirected to http://support.microsoft.com/kb/2497281. Frustrated, we tried a different proxy server and at first thought it was WSUS causing the issue. Windows Update worked on other PCs no problems.
So we did some research on the Interweb and noticed a few posts by similiar people having the same issue. Seems to have happened over the last week by the sounds of it, have Microsoft broke something?
The fix is to either reinstall Service Pack 3 which is time consuming or obtain the latest Windows Update Agent 3.0 from http://support.microsoft.com/kb/949104 which will resolve the issue.
Today I noticed that some of our devices were not updating to version 10.3.0. Upon further investigation I noticed the clients were not downloading the update correctly from the satellite server. I came to this conclusion by checking the overall size of the cache folder and forcing a refresh through Zen. What I noticed was the cache would increase to a certain size and then stop. When checking the files/folders within the cache folder (C:\Program Files\Novell\ZENworks\cache) I noticed the Zen 10.3 updates files were much smaller in size and not representing the correct file size.
The only thing I could think of was that the satellite repository must have inconsistency. I decided to log-on to a satellite and see what commands are available to try and resolve this issue. I came across the following:
I decided to run the “zac cvc” command first to ensure the content was correct followed by a “zac cchk” to double check the checksum of the files were also correct. The time for these commands may vary depending on content size. These took around 3 minutes each to complete.
This fixed the problem I was having whereby the content was downloading incorrectly. It then occurred to me that this would be good to have on a bundle that ran at least one a month to ensure all content is consistent on the satellites. Seeing as I have 100 satellites, trying to do this manually would be a pain!
This has since fixed the issue with updating and also some other issues relating to bundles.