Windows RT – Create the recovery drive

Important note: You need to perform the update before installing Windows 8.1 from the store. If the system is bricked during the 8.1 upgrade and you don’t have a recovery disk. Then you need to contact Microsoft or a friend who has not update yet.

Before starting you will need to have a USB disk between 4 GB to 16 GB depending on the applications on the system.

Follow these steps to create a USB recovery disk on a Surface RT:

1. From the Start screen, tap the Desktop tile to open the Windows Desktop.

2. Slide your finger in from the right to fetch the Charms bar and then tap the Settings icon.

3. On the Settings Pane, tap the words Control Panel from the pane’s top edge.

4. On Desktop Control Panel, tap the System and Security section and then tap File History.

5. On File History window, tap Recovery in the bottom, left corner.

6. Tap Create a Recovery Drive when the Recovery window appears.

The program walks you through inserting a USB flash drive of 4GB or larger into the Surface RT’s lone USB port. Then it copies the Surface’s recovery partition to the flash drive, creating a recovery drive.

Reboot from the recovery drive

If your Surface won’t load properly, follow these steps to boot from the recovery drive:

1. Turn off your Surface and then insert the recovery drive into your Surface RT’s USB port.

2. While pressing the Volume Down switch, press and release the Surface RT’s Start button.

After a minute or two, the Surface RT wakes up and loads from the USB recovery drive, leaving you at the opening screen.

Follow the steps to reset your Surface RT to factory conditions, just like the Surface’s Reset command. Use this as a last resort.

90 Days to MCSA: SQL Server 2012 Edition

 

Born to learn have just posted some helpful information for those going for an MCSA in SQL 2012. Check out the following link;

http://borntolearn.mslearn.net/btl/b/weblog/archive/2013/03/04/90-days-to-mcsa-sql-server-2012-edition.aspx#fbid=ZAegHI_Wg3A

90 Days to MCSA: SQL Server 2012 Edition

At the start of 2013, many database pros in the global Microsoft Certified Professional community reviewed 2012 accomplishments and set new goals for earning or upgrading certifications in the new year. In my conversations with MCPs on various forums and social networks, I heard many questions about exam prep resources and saw several requests for support from peers. Our team then took these points and discussed with several Microsoft Certified Trainers, and together, we have assembled a new package of resources just for you. Modeled after the success of last year’s “60 Days to MCSE for Private Cloud,” please meet “90 Days to MCSA: SQL Server 2012 Edition.”

All the information and links can be found at 90daystoMCSA.com.

Sysprep still required for imaging and cloning

There has been a number of posts on when to use Sysprep and even if it is required. Based on the Microsoft TechNet document here http://technet.microsoft.com/en-us/library/hh824816.aspx, it is still required.

A Sysprep image is the best used when cloning or reimaging a computer. There are a number System Administrations out there who are still using cloning without running Sysprep /generalize. The sysprep /generalize removes unique information from your Windows installation so that you can safely reuse that image on a different computer.

So before cloning, taking an image or duplicating a disk, run SysPrep.

Sysprep is including in Windows 7, Windows 8, Windows 2008 R2 and Windows 2012. It is located in the %WINDIR%\system32\sysprep directory.

Hyper-V did not find virtual machines to import

 

When doing some export and imports of the VM using Hyper-V I found an issue related to security. When System Centre VMM is used in the environment, a security ID is placed on all VM. This security ID stops you from importing the VM into Hyper-V.

When importing via the GUI you get the following message;

clip_image002

While doing some testing I found the following section inside the virtual machine configuration file.

<security>

<sd type=”string”>O:S-1-0-0D:(OA;;CC;5cf72d6e-61d5-4fbe-a05c-1e3c28d742fa;;S-1-5-21-4026737508-1815974660-2349268802-1111)(OA;;CC;5cf72d6e-61d5-4fbe-a05c-1e3c28d742fa;;S-1-5-21-4026737508-1815974660-2349268802-1109)(OA;;CC;5cf72d6e-61d5-4fbe-a05c-1e3c28d742fa;;S-1-5-21-4026737508-1815974660-2349268802-1107)(OA;;CC;5cf72d6e-61d5-4fbe-a05c-1e3c28d742fa;;S-1-5-21-4026737508-1815974660-2349268802-1110)(OA;;CC;5cf72d6e-61d5-4fbe-a05c-1e3c28d742fa;;S-1-5-21-4026737508-1815974660-2349268802-1105)(OA;;CC;5cf72d6e-61d5-4fbe-a05c-1e3c28d742fa;;DA)(OA;;CC;5cf72d6e-61d5-4fbe-a05c-1e3c28d742fa;;S-1-5-21-4026737508-1815974660-2349268802-1104)(OA;;CC;5cf72d6e-61d5-4fbe-a05c-1e3c28d742fa;;S-1-5-21-4026737508-1815974660-2349268802-500)</sd>

</security>

 

The quick fix is to remove this security element from the xml configuration file.

I have also found that this happens when you remove a Hyper-V from a domain or VMM structure without first removing the virtual. In this case Hyper-V will report no Virtual Machines found on the Hyper-V server. To correct this, remove the security from the configuration files and refresh Hyper-V manager. The virtual machines will all appear again.

WordPress HTTP 500.0 Internal Server Error with Windows Platform Installer

When trying to install WordPress using the Windows Platform Installer you get the following error;

HTTP Error 500.0 – Internal Server Error

File monitoring is enabled for a file which could not be found

Detailed Error Information:

Module FastCgiModule
Notification ExecuteRequestHandler
Handler PHP53_via_FastCGI
Error Code 0x80070003
Requested URL http://php.skybel.com.au:80/index.php
Physical Path C:\inetpub\WebSites\Test_PHP\index.php
Logon Method Anonymous
Logon User Anonymous

When checking the error it appears that the Windows Platform Installer adds some Handler Mappings which are incorrect.

The installer adds two handlers;

  • PHP53_via_FastCGI
  • PHP54‑via_FastCGI

On my system, I have only PHP 5.4 installed. If I check the handlers, I can see that the handler PHP53_via_FastCGI points to a PHP 5.3 directory which does not exist on my system.

To correct the issue, open IIS Manager and navigate to your site creating the problem.

  1. Open Handler Mappings
  2. Scroll down till you find PHP53_via_FastCGI
  3. Delete the handler PHP53_via_FastCGI

image

You should only need to have the PHP54_via_FastCGI handler. The site should now work fine.

All Dreams Are Now Welcome, Imagine Cup 2013

IC2013_Hero_Web_Banners-4

“I’m John Scott Tynes, your new Imagine Cup Competition Manager, and it’s my very great pleasure to announce the start of our new season. Today we take our first steps on the road to St. Petersburg, Russia, where all of our efforts will culminate in our Worldwide Finals in July, 2013. To get started, I’m excited to share some great news!”

Read the full blog on the Imagine Cup site here.

Index of UX guidelines for Metro style apps

Microsoft have released the UX guidelines for Metro style apps. See the below link for more information.

http://msdn.microsoft.com/en-US/library/windows/apps/hh465424

Migration Guide: Migrating to AlwaysOn Availability Groups from Prior Deployments Combining Database Mirroring and Log Shipping

Migration Guide: Migrating to AlwaysOn Availability Groups from Prior Deployments Combining Database Mirroring and Log Shipping – SQL Server AlwaysOn Team Blog – Site Home – MSDN Blogs

http://blogs.msdn.com/b/sqlalwayson/archive/2012/08/20/migration-guide-migrating-to-alwayson-availability-groups-from-prior-deployments-combining-database-mirroring-and-log-shipping.aspx

Windows Server 2012 Now Available in the Windows Azure Virtual Machine Gallery

Windows 2012 has been added to the Azure platform. Check out the below link for more info.

http://blogs.msdn.com/b/windowsazure/archive/2012/08/16/windows-server-2012-now-available-in-the-windows-azure-virtual-machine-gallery.aspx