Tuesday, September 4, 2012

Installing Remote Server Administration Tools (RSAT) on Windows 8 RTM

On August 16th, Windows 8 RTM became available through the Volume License Service Center (VLSC), for company with Software Assurance for Windows. Since the company I’m working for has an Enterprise Agreement and Software Assurance, I was able to download it and get the license key.

I had downloaded it already the day before through my Technet Plus subscription and installed it on my test laptop at home but now that it was available on the VLSC, I could install it on my work computer as well and this is exactly what I’ve done.

I decided to try upgrading directly from Windows 7 and it went very well. It warned me about the software I should uninstall because they are not compatible with Windows 8 and asked me to disable Bitlocker for the duration of the installation. It took a while but installed without any problem. My applications were still working after the installation and it kept all my data, customization and themes.

The only problem I had was when I tried to install the Remote Server Administration Tools (RSAT). I found out RSAT hasn’t been release yet for Windows 8 RTM but is was for Windows 8 Release Preview. You can find it here.

The catch is that it won’t install on Windows 8 RTM. Here’s the error message I got:

image

But after some research, I found how it could be installed manually. Here’s what I found:

  • Download the RSAT for Windows 8 Release Preview from here.
  • Extract the files in a local folder on your computer. You can use a tool such as WinRAR or 7zip or use the following command line:

expand –F:* Windows6.2-KB2693643-x64.msu c:\temp

  • Start CMD with elevated privileges and go to the local folder where you extracted the .msu file.
  • Then execute the following command with the full path and name of the CAB file in the folder:

pkgmgr /ip /m:c:\temp\Windows6.2-KB2693643-x64.cab

  • Start Task Manager and wait until Windows Package Manager process stops running.
  • There you go, RSAT is installed.

Hope this will be useful!

Tuesday, August 21, 2012

Windows 8 RTM Enterprise Activation issue

As a Technet Plus Subscriber, I was impatiently waiting for August 15th to get my hands on Windows 8 RTM. At about 1:00pm EST, it became available and I started my downloads (Pro & Enterprise in x86 & x64).  It was a bit of a challenge because the site kept giving me error messages probably because it was overloaded by people like me who wanted to get their hands on the latest release. Anyway, after a few tries, I’ve got my first download started which was the Windows 8 RTM Enterprise x64 version.

Getting the key was a challenge as well.  But around mid-afternoon I was finally able to get it. Then I started the installation on my test Laptop. The installation went well and it was very fast. It discovered all my hardware even though I had trouble finding some drivers when I installed Win 7 on it. For example, I had to install the Vista video card drivers on Windows 7 because they didn’t exist for Windows 7. But Windows 8 detected my video card, installed a Windows 8 driver for it and it’s working like a charm (no pun intended)!

The only problem I had was the Activation. I kept getting the same message over and over: “Windows can't activate right now. Error Code: 0x8007232B”

At first, I thought the site was overloaded like it was for the downloads and the keys. However, after a while I noticed that it wasn’t asking me for my license key and that it was trying to activate with a key that was already built-in. If you’re trying to activate your Windows 8 RTM Enterprise and you’re stuck like me, here are the solutions I found:

Option 1:

From the Charm bar, type SLUI 3. It will start the Windows Activation Center and prompt you to change your key. Once it’s done, you should be able to activate your copy of Windows.

image

 

Option 2:

From an elevated Command Prompt (CMD running as Administrator), run:

slmgr.vbs -ipk "YOUR_PRODUCT_KEY"

image

 

I used the Option 2 and I was finally able to do the activation. I’ve been using it since then and I really like it so far.

Good luck!

Thursday, September 22, 2011

What’s the difference between Business Continuity and Disaster Recovery?

 

What’s the difference between Business Continuity (BC) and Disaster Recovery (DR)?  This is a question I have had to answer multiple times.  It is a very good question and the answer is not simple!  So, as a good lazy 'techy', I tried to find the answer on the web.  That way, when I am asked, all I would have to do is send a link.

I have used this approach multiple times for other questions I have received.  It is convenient and a great way to avoid re-typing an answer.  However, this time, I was not very successful in my quest to find an answer.  I searched the web, multiple times, for hours without finding the perfect "pre-written answer" I was looking for.  So I decided to stop being lazy and write it myself.

Now, if you are like me, and you've been looking for an answer to this question, feel free to use this one.

So, let’s start with a few definitions from the Business Continuity Institute (BCI) Glossary:

Disaster Recovery (DR): “The strategies and plans for recovering and restoring the organizations technological infrastructure and capabilities after a serious interruption. Editor’s Note: DR is now normally only used in reference to an organization’s IT and telecommunications recovery.

Business Continuity (BC): “The strategic and tactical capability of the organization to plan for and respond to incidents and business disruptions in order to continue business operations at an acceptable predefined level.”

First, I’d like to say that I have a slightly different view of DR than BCI.  Now, who am I to disagree with what BCI is saying?  Well, bear with me a little longer and you will see how my interpretation of DR might help people understand the differences between DR and BC better.  So here’s my definition:  DR is the strategies and plans for recovering and restoring the organizations (scratch technological) infrastructures and capabilities after an interruption (regardless of the severity).

Unlike the BCI, I don’t make a distinction between the technological infrastructure and the rest of the infrastructures (the buildings for example) and nor I do differentiate between the types of interruptions.  In my opinion, either a system is down or a building is burnt or flooded, both should be considered a disaster and therefore both require a disaster recovery plan.

Therefore DR is the action of fixing a failing, degraded or completely damaged infrastructure.  For example, the 2nd floor of a building was on fire; the fire is now out so the initial crisis is over.  Now the damage caused by fire must be dealt with; there is water and smoke on the 2nd floor, the 3rd floor has damages caused by smoke and the 1st floor has water damage.  The cleanup, replacement of furniture, repair of the building and its structure, painting, plastering, etc. are all part of the disaster recovery plan.

What is Business Continuity then?  Business Continuity is how you continue to maintain critical business functions during that crisis. Back to the example, when the fire started, the alarm went off and people were evacuated from the building.  Let say you had a Call Center on the 2nd floor and this just happens to be a critical area of your business.  How would you continue to answer calls while people are being evacuated?  How would you answer calls while the building is being inspected, repaired or rebuilt? Keeping the business running during this time is what I call Business Continuity.

The same approach can be taken with a system crash or when the performance of a system has degraded to the point that it has impacted business operations.  So fixing the system is DR and the action of keeping the business  operations running without the system being available is BC.

In conclusion, BC is all about being proactive and sustaining critical business functions whatever it takes whereas DR is the process of dealing with the aftermath and ensuring the infrastructure (system, building, etc.) is restored to the pre-interruption state.

Thursday, August 18, 2011

It’s all About Me!

No, it’s the about the single “It’s All About Me” by Mýa or the British sitcom “All About Me”. It’s all About Me, Me and only ME!!

More seriously, about.me is the new service I discovered recently that allows you to create your own personal splash page with a short bio and links to your multiple online profiles from the different social networks. Here’s mine: http://about.me/EricGagnon

imageThe cool thing about this service is that it doesn’t only display static link to your different profiles but also allows you to enable dynamic content.  For example, when people clicks on your Twitter link, they can see your recent tweets, follow you and follow the link to your twitter profile.

You also have access to a dashboard that provides statistics on how many people viewed your profile where they clicked and from which website they found you (Links to You).

Have you been using about.me?

Let me know what you think!