Wednesday, December 18, 2013

This Map Of Al Qaeda In Iraq Is Terrifying

Fighters from al Qaeda fighters are bombing strategic targets in parts of western Iraq as they seek to wreak havoc on security and establish an Islamic emirate.
The map below gives and indication of how successful they have been, and it is quite troubling given that sectarian killings are rising along with the groups influence.
The scariest part is not even highlighted: Next door in Syria, Islamic State in Iraq and al-Sham (ISIS) administrates the largest rebel-held city, Raqqa, and fights to control the borders with both Iraq and Turkey.
“Establishing a geographical area comprising natural resources such as oil and gas and totally dominated by Sunnis is a priority for the [ISIS] in this stage,” a retired senior military officer who was responsible for making plans to combat al Qaeda told Reuters.



 This Map Of Al Qaeda In Iraq Is Terrifying | Business Insider


Tuesday, December 10, 2013

HONI SOIT QUI MAL Y PENSE - Tropfest Australia 22 2013 Third Prize (TSI ...

Image of COOP x OXOP 8" Qee "Stoner Bear" vinyl Toy

Image of COOP x OXOP 8" Qee "Stoner Bear" vinyl Toy

Image of DEVIL GIRLS Painted Resin Statue

Image of DEVIL GIRLS Painted Resin Statue

Don't Freak Out About Ultrasonic Malware (Yet) | Gizmodo Australia

The internet’s been abuzz lately with news that computer scientists have found a way to transmit malware using ultrasonic audio signals. If true, this means that you’d never be safe from the hackers, as long as your computer has a microphone and speakers. But don’t freak out just yet.

We reached out to the cybersecurity experts at Kaspersky Lab to find out how much of a threat this capability might really be. It’s entirely possible, they said, that the German computer scientists who originally tested the idea of transmitting malware using nothing but sound were successful; after all, people have been ex-filtrating data through technology like FM radio for some time. However, it’s not like this thing is going to bring the mainframe crashing down.

“The problem is that the receiver needs to be physically close to the victim computer(s),” David Jacoby, Senior Security Researcher at Kaspersky Lab, told Gizmodo. “What they have proven is that it’s possible to exfiltrate data in non-traditional ways, but to make it possible the victim computers still need to be infected with some kind of malware.”
So hackers would already need to have accessed your computer physically to install the malware and would then need to be just a few feet away to activate it. Depending on how closely you watch your computer, this is pretty unlikely. It’s certainly not something that could enable hackers to punt a virus into a computer mainframe, like the Stuxnet worm was passed on to the computers in Iranian nuclear facilities without the help of a network. They used a USB stick, not this sort of super-acoustic sorcery.
Of course, don’t let this news tempt you into dropping your guard. There are plenty of other ways for prying eyes to sneak into your life.





Don't Freak Out About Ultrasonic Malware (Yet) | Gizmodo Australia

Saturday, August 31, 2013

CW's Wonder Woman Series AMAZON is Still in Development

In case you were wondering what's been going on with CW's Wonder Woman series, some of you will be happy to hear that it's actually still in development. The network is just taking their time with it, and it's currently in the process of being redeveloped. 

While talking to reporters recently, CW President Mark Pedowitz emphasized that the series is still very much a part of the network's future plans. Here's what he said when asked about it:
Oh God yes. It is being redeveloped. We're waiting for the script to come in. We have not seen it yet. We are preparing to pilot it off-cycle should the script be what we want it to be. We do not want to produce something that doesn't work for that particular character. It is the trickiest of all the DC characters to get done.


The series was previously said to focus on Wonder Woman as a "young, budding superhero, rather than a fully formed defender of liberty. (Think, but instead of a 'no tights, no flights' rule, this show might have a 'no bracelets, no crown' mandate.)" We also have a previously released description of the series that you can check out here.
She comes from a remote, secluded country and until now has spent most of her life as a soldier and a leader on the battlefield. Because of relentless brutality of her life at home, Iris looks at our world with absolute awe and astonishment. She’s delighted and just as often horrified by the aspects of everyday life that we take for granted: skyscrapers, traffic, ice cream. It’s all new and fascinating and sometimes slightly troubling to her. Iris is completely unschooled in our world, our culture, our customs. And she’s completely inexperienced at interpersonal relationships. She has no social filter, does not suffer fools, and tends to do and say exactly what’s on her mind at all times. She’s bluntly, refreshingly honest. She can tell when you’re lying to her. And she doesn't have time or patience for politics or tact because she’s too busy trying to experience everything our world has to offer. There are too many sights to see and things to learn and people to care for. Hers is a true, noble, and generous heart. And she will fight and die for the people she loves. Iris is a fierce warrior with the innocent heart of a romantic and she will fight to the death to make the world safe for innocents and true romantics everywhere.
Since they're redeveloping the series I have no idea how much of this stuff will be included, but I imagine it will have the same tone. I guess we'll see. Hopefully the CW can pull it off!


CW's Wonder Woman Series AMAZON is Still in Development — GeekTyrant

Wednesday, August 21, 2013

10 virtualization tips every administrator should consider

Virtualisation can reduce costs, simplify administration, and enable organizations to get more mileage out of their tech investments. These tips will help you reap those benefits.



Virtualisation has become a necessity for companies of all sizes. From testing sandboxes to production services, virtualization helps businesses get more out of their hardware and do more for their companies than they ever could before. For many companies, this technology is quite new. For others, it's old hat. Regardless of where you fall, virtualization is a vast technology with numerous moving parts. Having the knowledge to get the job done to best suit your needs should be the primary goal for you and your IT staff. With that in mind, here are 10 tips that shouldn't be overlooked by any administrator considering virtualization (or already deep in the trenches of this tech).

1: Plan hardware for virtual capacity

 When you are in the early stages of planning your virtual environment, do not make the mistake of purchasing hardware that can't handle the strain virtualization will put on it. You need to think bigger than usual. Remember, this server might well be hosting numerous virtual machines, so it's going to need the raw horsepower and the space necessary for growth. The last thing you need is to have your host server choke and run out of space for virtual machines. Measure twice, cut once applies. Don't assume a virtual machine will take up little space on that server. And don't assume you'll be hosting only one virtual machine.

2: Keep track of the entire lifecycle of every virtual machine

I've heard of administrators unleashing a virtual machine and leaving it do its thing with little to no monitoring. You need to be keeping track of every one of your virtual machines from birth to death. You should always know how large those VMs have become, the status of their snapshots, how much traffic they are getting, and just about every other piece of information you can get your hands on. It's very tempting to "set and forget" virtual machines, but that is a grievous error and could land you in a world of trouble.

3: Don't virtualize everything

Not everything should be virtualized. That FTP server that gets only internal traffic of maybe a half dozen users? Probably not. Printer server? Probably not. You need to make a specific plan and have sound reasons for everything that is virtualized. The first thing you should ask yourself is, "Why do we need to virtualize Server X?" When you can answer that question with a modicum of certainty, apply that same reasoning to every server you think might benefit from virtualization.

4: Monitor virtual traffic as well as you do non-virtual traffic

Make sure you monitor your virtual traffic as well as you do your non-virtual traffic. Don't be lulled into thinking the virtual hosts are safer simply because you can spin up a snapshot at a moment's notice. That is a false sense of security and should not be considered a substitute for security. But monitoring goes well beyond security. You need to keep abreast of both internal and external traffic to your virtual machines. After a certain period of time, you will know whether specific machines need to be given more resources and whether other virtual machines would be best served as stand-alone.

5: Don't give away virtual resources for free

I've seen it plenty of times: Virtual machines seem to take up so little space and are easily given over to the realm of "free." Don't do this. Don't even migrate a server from stand-alone to virtualized for free. The client needs to understand the benefit they gain from their server being virtualized -- and along with all that comes with virtualization, there is a price. Besides, the technology required for virtualization has a cost associated with it, and sometimes that cost is high. Your organization can't foot that bill alone.

6: Use virtual machines for disposable systems

This might seem a bit strange to some, but there are times when you need a system or service temporarily. There's no better way to supply a temporary service than with virtual machines. Need a temporary FTP server? Virtual machine. Need a temporary print server or Web server? Virtual machine. The nice thing about virtual machines is that they don't cost you the resource of hardware, so bringing a machine to life is quite easy. You could even create specific virtual machines for specific "disposable tasks" and bring them up only as needed.

7: Create virtual machine templates for easy deployment

If you know you'll want to deploy numerous virtual machines based on specific configurations or needs, create a set of templates so that deployment of these machines is as efficient as possible. This can really save you time and effort if you sell a specific service -- say, Web servers -- and sell them often. There's no need for you to constantly reinvent the wheel. Create a template and use it as often as necessary. That time saved is money in the bank for both you and the client.

8: Use "thick provisioning" for disks when performance is key

Most admins will create dynamically allocated disks for their virtual machines. For those VMs that need as much performance as possible, you should allocate thick provisioning. In other words, set an actual size for the disk in the VM configuration. Yes, you will need to make sure you've done the necessary planning to ensure the host machine has enough space to accommodate those thick provisioned virtual machines. But the performance gains you get will definitely be worth the time invested.

9: Install all guest add-ons and virtualization tools

This should be a no-brainer. Most virtual machine tools (like VMware and VirtualBox) offer guest add-ons and other virtualization tools created to improve the experience and performance and to make the communication between the guest and host more seamless. A lot of admins neglect these installations, assuming them to be unnecessary. Install them. Mouse integration, display drivers, guest-to-host time sync, and more can be installed to help make the virtual life a more efficient one. Though they are not required, they do a great job of improving the front-end usability.

10: Keep your host system fully patched at all times

Most assume all the weight is on the guest OS. Although that is true for the virtual machine, the host plays a huge role in this process. The last thing you need is to have your VMs hosted on a vulnerable machine. Sure, if that server isn't hosting a litany of virtual machines, the only thing at risk is a single server's worth of data. But since that server is hosting any number of VMs (some of which could be for clients), the threat of loss is significantly greater. Because of this, you will want to make sure that the host machine is patched up and always secure.

The payoff

At some point, your company is going to want to make the investment in virtual technologies. At that time, you will want to be as prepared as possible. With enough due diligence and work on your part, your virtual machines will save you money, time, and effort -- which, in the end, can make your clients very happy.





10 virtualization tips every administrator should consider - TechRepublic

Review: Free DD-WRT network router firmware

Most network routers have fairly basic firmware that limits the hardware's full potential. You can change that.

In most situations, a network router's normal purpose is to facilitate in connecting computers together to form a network, either for internal use or for granting access to the World Wide Web. Admittedly, if you actually want to do anything interesting with the hardware, most routers have fairly basic firmware that limits the hardware's full potential. I know this first hand, as I picked up an ASUS RT-N12 router from a good friend of mine recently to replace my underwhelming Belkin branded one. Although ASUS hardware is mostly of high quality, the firmware felt rather raw and unpolished. With that in mind, I did some research online and found that custom router firmware was available and I decided to give it a try.

DD-WRT

Product Information

Eventually, I settled on DD-WRT, which is quite honestly one of the best router firmware packages I've ever used. For those who are unfamiliar with it, DD-WRT can be flashed on any compatible router in order to grant the user extra functionality, which hardware manufacturers seem reluctant to include in stock software. Once you flash your router, you probably won't want to go back. You quite literally get everything but the kitchen sink at your fingertips.



For an idea of what DD-WRT can do for you, I will highlight some of my favorite features included with the firmware.
If you wanted to set up an OpenVPN gateway for all systems that connect through the router, you can add your VPN cert and private key, flip a few switches to determine the encryption and tunnel type, and voila! Every computer that connects to the router will pass right into the VPN. No client end VPN software is necessary.
I also like how DD-WRT is extremely verbose on stats, showing you total inbound and outbound traffic to date, as well as router performance information, including free memory and CPU activity. Having access to this panel will give you insights into what kind of traffic you are dealing with and if you need additional hardware down the road.

DD-WRT_2.png

An example of some of the available router stats
Finally, DD-WRT just seems to improve network performance by a decent margin. For instance, after switching the firmware from stock to custom, surfing web pages and downloads seemed a bit snappier than before. Not to mention, I could be more discriminatory of what protocols (i.e. Bittorrent) could do what it needed to do with the network to improve balance.

Installing takes some research

Now, when it comes to getting DD-WRT installed to the router, there really is no one-size-fits-all method, as hardware from different manufacturers is handled on a case by case basis. There are some routers that are unable to be flashed too, so if you are shopping around for a new router, it would be advisable to refer to the DD-WRT hardware compatibility database first before committing to a purchase.
Fortunately, for my router, installation was as simple as dropping into the firmware upgrade menu, selecting the custom-tailored ROM file for my hardware make and model, and then uploading it over the network. After a several minute upload process, followed by a mandatory router reboot, I was up and running in DD-WRT. In the unfortunate event of an endless reboot or other strange issue that might arise in the process of flashing, I also have the option to boot into the router's low-level recovery mode in order to roll back to the stock firmware and try again.
With all this interest surrounding router modifications, it goes without saying that flashing with un-official custom firmware could invalidate your warranty coverage and cause other problems. If this all sounds too risky, companies like Buffalo actually offer routers with DD-WRT firmware already flashed and ready to go with full warranty coverage. This way, you won't have to worry about accidentally bricking any hardware if you don't feel adventurous.
DD-WRT is available to everyone as freeware under the GNU GPLv2 license. So long as your router make, model, and revision are all listed, you should be good to go. One thing to note: if you have less than 8MB of flash storage space on your router, you won't be able to take advantage of every feature available. Therefore, you will need to choose the mini firmware "edition" that best suits your needs for the hardware.






Review: Free DD-WRT network router firmware - TechRepublic

Rescue a Windows XP installation in Windows 8 with Zinstall XP7

Learn how to get and use Zinstall XP7 to move your Windows XP installation from a hard disk to your Windows 8 system.



A friend of mine got a new Windows 8 system and was running it along side of his old Windows XP box so that he could get used to Windows 8 yet still be able to run his older applications in Windows XP. Everything was going fine with this set up until recently when he called and told me that his Windows XP computer died and wanted to know if I could help him rescue his XP system. After talking with him for a while I discovered that the power supply on the old system had bitten the dust. While the old system would not power on, he said that the last time he used it, the system worked fine and he had shut it down like he normally did. Suspecting that the hard disk was still intact, I told him that we could probably retrieve his data and put it on the new computer. He said that while that would be great, what he really wanted was a way to revive the Windows XP computer. We initially discussed replacing the power supply, but when I told him about Zinstall XP7 and how you could use it to move a Windows XP installation from a hard disk into a virtual environment that could be run in Windows 8, he liked that idea.
Later, we took IDE hard disk out of the old computer, connected it to his new computer via an IDE to USB adapter, and verified that it was still accessible and in good condition. We then used Zinstall XP7 to move the entire Windows XP installation into his Windows 8 system. The entire procedure was very easy and the end result provided such a slick way to switch between operating systems that I thought I should revisit this product and show you how it works in Windows 8. (Back in 2010, I wrote an article about using Zinstall XP7 to perform an in-place migration of Windows XP to Windows 7.)
In this article, I'll show you how get and use Zinstall XP7 to move your Windows XP installation from a hard disk to your Windows 8 system. As I do, I'll explain each step in the procedure.
Note: Even though the product name "XP7" implies a Windows XP to Windows 7 path, it works perfectly in Windows 8.

Overview

Keep in mind that while you can use Zinstall XP7 on two computers and move Windows XP into Windows 8 using a network connection, I am going to cover moving Windows XP into Windows 8 using just the hard disk. Furthermore, while I used an IDE to USB adapter to move my friend's Windows XP installation, on my example system for this article, I simply removed the SATA hard disk from my Windows XP computer and connected it to the second SATA connector in my Windows 8 system.

Getting and installing Zinstall XP7

Zinstall XP7 is a commercial product which sells for $89. You can purchase and download the product from the Zinstall site.
Since I'm going to be moving Windows XP into Windows 8 using just the hard disk, I'll download and install Zinstall XP7 on a Windows 8 system. Once the download is complete, just run the executable file. In a few moments you'll be prompted to enter the serial number you received along with the email address you used to purchase the product, as shown in Figure A.

Figure A 

 











You'll be prompted to enter the serial number you received in order to activate Zinstall XP7.

Performing the transfer

As soon as the installation is complete, Zinstall XP7 will launch and prompt you to identify your migration scenario. Since I am running the program on my Windows 8 system with the Windows XP hard disk connected, I will identify the migration scenario by selecting I only have this PC and the selecting Yes, I am migrating from another hard drive, as illustrated in Figure B.

Figure B

 In this scenario, you select the migrating from another hard drive option.















You'll then see a Zinstall window that will begin searching for the Source and Target computers. When it finds them, the Go button turns green, as shown in Figure C, and you can click it to begin the migration procedure. Here you can see that Zinstall found the 160GB hard disk that contains the Windows XP installation and will migrate it to a folder on my Windows 8 system.

Figure C

 



 
 
 
 
 
When the Go button turns green, you can click it to begin the migration procedure.
The actual migration is a lengthy process involving multiple operations, as shown in Figure D, and can take several hours depending on the size of your Windows XP installation. For instance, my 160GB hard disk took a little over an hour to finish.

Figure D

 











The actual migration is a lengthy process that involves multiple operations.

Working with the two systems

Once you complete the migration step, you'll see a Zinstall icon in the system tray of you Windows 8 system. To access your Windows XP installation, you can just double-click on the Zinstall icon. You can also access your Windows XP installation by right-clicking on the Zinstall icon and selecting the Switch to Guest Desktop command.
When you are in Windows XP, you'll also find a Zinstall icon in the system tray. To go back to your Windows 8 installation, you can just double-click on the Zinstall icon or right-click on the Zinstall icon and select the Switch to Host Desktop command. This process, which Zinstall refers to as switching channels, is illustrated in Figure E.

Figure E 

You can use the Zinstall icon in the system tray to switch between Windows 8 and Windows XP.















You'll also find several shortcuts on your Windows 8 desktop that allow you to initiate the desktop switch and access Windows XP's My Documents folder inside of Windows 8; however, I found both of those shortcuts much more time consuming than simply double-clicking the Zinstall icon and changing to the Windows XP channel.
You'll also discover that Zinstall XP7 places shortcuts to all of your Windows XP applications on Windows 8's Start Screen and each one is prefixed with a Z^ to make it easy to identify. If you find that this makes the Start Screen overcrowded, you can remove all the shortcuts using the Advanced tool.
Right-click on the Zinstall icon and select the Advanced command. When you see the Advanced application, select the Remove shortcuts on Exit check box, as shown in Figure F, and click OK. Then, shut down Windows XP and restart Windows 8. When you get back to Windows 8, you'll see that all of the shortcuts have been removed.

Figure F 

 




















You can Remove the Windows XP shortcuts from the Start screen.
To make working with the two systems as easy as working on one system, the Windows 8 and Windows XP environments are fully integrated. This means that you can copy files and text between the two systems just like you copy files between two folders and text between different applications. For example, to copy a file from the Windows 8 environment to the Windows XP environment, just right-click on the file, select Copy, switch to Windows XP, and paste the file.
For larger-scale file copy operations, access your Windows XP environment and go to My Computer where you will find a drive letter Z: under the Network Drives section. When you open it, you will find links to all of the drives on your Windows 8 system as well as a link to the Documents folder on your Windows 8 system.
Network and Internet access is automatically enabled. If Windows 8 has access, so does Windows XP. This works with any kind of connection, wireless included.

What's your take?

Will you use this Zinstall XP7 to migrate your Windows XP system to Windows 8? As always, if you have comments or information to share about this topic, please take a moment to drop by the TechRepublic Community Forums and let us hear from you.

More information

Virtualization has swept through the data center in recent years, enabling IT transformation and serving as the secret sauce behind cloud computing. Now it's time to examine what's next for virtualization as the data center options mature and virtualization spreads to desktops, networks, and beyond.

Also read:






Rescue a Windows XP installation in Windows 8 with Zinstall XP7 - TechRepublic

Migrate VMware virtual machines and View desktops to a new SAN



Learn how to move VMware data from an old storage array to a new one using storage vMotion and Rebalancing for VMware View desktops.

vmware-view-client-081513.jpg
I spend a lot of time doing storage migrations to new storage arrays because the company I work for sells storage arrays. It's actually not too difficult, and sometimes you can even do it without downtime.



Here's a list of some of the things to check before you start VMware's vSphere storage vMotions. I also address how to move VMware View desktops.

The basics

In order to use storage vMotion to migrate virtual machines (VMs) to a new array, you need to zone your ESXi servers to both arrays. I'm not going to cover that in detail in this article, but essentially you need to make sure the hosts can see datastores from both the old and the new array. You also need to have at least an Enterprise vSphere license; any license lower than that doesn't offer you the ability to do storage vMotion while the VMs are powered on. If you have all of that and no Raw Device Mappings (RDMs), you can go ahead and just storage vMotion your VMs to the datastores on the new array. 

Steps to storage vMotion:
  1. Bring up vCenter using the vSphere client or the web client.
  2. Right-click the VM you're planning to move and click Migrate.
  3. Choose to migrate to a new datastore.
  4. Choose the datastore on the new array you'd like to move it to.
  5. Click OK or Finish and watch as the task progresses.
It's pretty simple, albeit somewhat tedious depending on how many VMs you have and the size of the hard disks. The question I get asked at least twice last week is: How do you migrate VMs with raw device mappings? These are luns that are connected directly to the VM instead of going through Virtual Machine File System (VMFS). There are two types of RDMs: physical and virtual. Read VMware KB article 2009226 to learn about the differences between the two RDMs. For the purpose of this article, you just need to know that you can't storage vMotion a physical RDM, only a virtual. You can get around this, but it requires a reboot of the VM. I also recommend only doing one at a time, so you don't confuse which RDM belongs to which VM.

Steps to convert from a physical RDM to a virtual RDM:
  1. Right-click the VM and click Edit Settings.
  2. Click the hard disk labeled Raw Device Mapping.
  3. Record the SCSI device it's using, because you will need to re-add it to that device later. You might even want to take note of the size of the hard disk, so you can be sure you're re-adding the right one back later.
  4. Remove the hard disk and delete it entirely. This will not remove data from the hard disk -- it simply deletes the pointer.
  5. Click OK.
  6. After that task is complete, go back into Edit Settings and add a hard disk.
  7. Add an RDM, but this time choose virtual mode. 
  8. Make sure you're adding the correct RDM to the original SCSI device.
  9. Power on the VM and ensure the disk shows up within the operating system.
After you convert it to a virtual RDM, you can storage vMotion the VM. If you don't change anything, it will simply remove the pointer from the original datastore and move it to the new one. However, sometimes you don't want to have to deal with RDMs anymore. If the application you're running on that VM supports it, you can storage vMotion the RDM to a Virtual Machine Disk format (VMDK) on one of the new datastores with no downtime. When doing a storage vMotion, you need to follow the steps above, but instead of leaving the format to be "same as the original," you need to change it to either thin or thick provisioned.  After you do that and choose a new datastore, it will convert your hard drive to a VMDK file from an RDM.
The last caveat I've run into is when the environment has VMware View (Horizon View) desktops. You should never storage vMotion linked clone desktops. There is a rebalance feature in the View Administrator that can be used to move the desktops to the new datastores. For more information, read the VMware View documentation and VMware KB article 1028754.

Steps to follow to move virtual desktops:
  1. Ensure your end users are logged out of their desktops. During the rebalance, you will get the option to either force them off or have it wait to move the VM until after they choose to log off.  It's up to you how you do this, but I recommend just getting it done so you don't remove the old array and lose that desktop. 
  2. Make sure your users have saved all their data to persistent disks if necessary.
  3. Log in to View Administrator (View Connection Server).
  4. Click the pool(s) you want to migrate.
  5. In the pool, click vCenter settings and change the datastores to the datastores on the new array (make sure to remove the checks next to the datastores on the old array). This will not affect the current desktops that have been provisioned.
  6. When you're ready, go back into the pool and under the View Composer drop-down box select Rebalance.
  7. In the Rebalance wizard, choose to force users to log off (if you like) and fill out the other options if you like. You can leave the defaults, though.
  8. You'll see the desktops go into Maintenance Mode, and then they will migrate to the new datastores. If you have them set up to power on automatically in the pool settings, you'll see them become available again after they've finished migrating. If they only say provisioned, they are not set up to power on automatically. You either need to change that or power them on manually.
If you have any questions, comments, or other helpful hints about this process, please feel free to leave them in the comments section.
Also read: Virtualizing the Enterprise, a Special Feature from TechRepublic and ZDNet



Migrate VMware virtual machines and View desktops to a new SAN - TechRepublic

Cabling tips

With a little planning and a few best practices, you can avoid the problems and maintenance headaches that come with improper cabling.


Your data center is the heart that pumps the lifeblood of your business. Without it, everything stops. And when it has problems, so does your business. Myriad issues can plague a data center. And although most people don't realize it, improper cabling can be one of those issues. But with some easy planning and work up front, you can maximize the efficiency and reliability of your data center cabling.
I have put together 10 tips to help you get the most out of your data center's cabling. With these tips, you'll have a more reliable data center and your staff will have a much easier time maintaining it.

1: Measure twice, cut once

It's an old adage, but an important one. Not only do you create a tangled mess if you don't carefully measure your cables, you also create a lot of expensive waste. You may think that two feet of wasted cable doesn't amount to much, but those wasted feet add up. In the end, you could save yourself a lot of time, headaches, and money by measuring twice and cutting once.

2: Label, label, label

If you don't label your cables, you're only making more work for yourself. Every cable should have a label on both ends, even short runs and patch cables. Why? Imagine you have to test a bunch of circuits -- quickly. You scramble and unplug a few patch cables and, when it's time to reset them back to their default locations, you have no idea where each cable goes. Avoid this problem by taking a little time to slap a label on each end. Make sure your labeling system is consistent. Don't just go ad hoc with this or you'll confuse yourself and those who work for you.

3: Don't skimp on terminations

Don't buy cheap because they're cheap and don't rush through the process of terminating cables. If you have cables that lose their connection if you wiggle them, you need to redo them. If you can't terminate cables in your sleep, you need to practice. You may think you're saving time and money. But in the end, you're going to wind up with a monstrous headache as you troubleshoot all those terminations.

4: Don't skip the test

After you create a cable, test it! And don't accept "Star Pass" tests (a test that barely passes). If a test doesn't pass 100%, redo that cable. If, after a few tries at termination, the cable still doesn't pass, trash it. And make sure you're using a quality tester for your cables (and that you know precisely how to use it). This simple step can prevent a lot of extra work in the end.

5: Keep patch cables short

You have servers in a rack that are within a foot of each other. Don't slap three-foot patch cables on those servers -- it not only looks bad, it's incredibly inefficient. And if you have an odd length between servers, use your termination (and testing) skills to create patch cables that reach perfectly. With that extra length on your cables, you invite tangles, kinks, and confusion.

6: Color code

This may sound a bit over the top, but stick with a single color for your patch cables and cable runs. The only time you should break that rule is when using a specific color cable for a specific purpose. But don't use colors randomly. Make sure each color has a purpose and stay with it. That will make it easier to follow cable runs and troubleshoot issues. And yes, it also makes for a better-looking data center -- which has its merits.

7: Upsize your conduit

Don't buy conduit sized for what you need NOW. Buy conduit sized for what you will need in the future. You never know when you'll be adding on, and you'll want to be able to make use of already-run conduit. You can't do that if you purchased a size that just barely fits your needs at planning time. Go big or go home.

8: Make your design cable-friendly

When you lay out your data center plans, do so in a cable-friendly way. Don't put a rack in a location where it's impossible to successfully run cable. Otherwise, you'll wind up with cable on the floor or hanging from the ceiling. Plan carefully to avoid later disaster. Also make sure to plan with expansion in mind. Run extra conduit, extra drops -- more than you think you'll need.

9: Separate Cat5 and power lines

Do not run Cat5 and power together. You might think it's too minimal to be of concern, but those power lines can leach signal and cause interference with your Cat5. Yes, bunching a lot of Cat5 together can do the same thing, but not with nearly the ill effect of running them alongside power. Keep power and networking separate at all costs.

10: Keep cables cool

You may think only the servers need to be cool -- but that would be a poor assumption. Cable can get warm as well, and if you have a massive amount of cable, that extra temperature can lead to disaster. Design your data center in such a way as to keep your networking runs cooled, as well as the server racks.

Spaghetti prevention

Cabling is often an afterthought. But when you treat it as such, you are running the risk that you'll find yourself elbow deep in a spaghetti bowl of networking cables, attempting to resolve issues that could have been prevented with just a bit of care up front.



Cabling tips

Evaluating Lync Server 2013: Installation steps

John Joyner takes you through the steps to prepare and install an evaluation copy of Lync Server 2013.
Microsoft’s real-time communications (RTC) and collaboration application Lync has gained a lot of users and even fans in the last few years. Building on preceding Microsoft products, Live Communications Server (LCS) and Office Communications Server (OCS) going back a decade, Lync 2010 was a major step forward and provided deep and useful integration into the Office suite as well as Exchange.
In April of 2013, Microsoft released the latest version, Lync Server 2013. There is a long list of new and improved features in Lync 2013 server compared to Lync 2010 server. If you are a current OCS or Lync customer with on-premise RTC server computers, you can consider upgrading to Lync Server 2013. You should carefully check out the cloud-based options for both Lync Online and Lync services as part of Office 365. A direct on-premise replacement of an older RTC solution might or might not be the right decision.

Preparing to install Lync Server 2013

Perhaps to help you make the decision of an on-premise Lync server or a cloud-based solution, kick the tires in a Lync Server 2013 evaluation. In the case of the previous release, Lync Server 2010, Microsoft provided a ready-to-use downloadable Virtual Hard Drive (VHD) image to make it easier to evaluate Lync 2010. To date, Microsoft has not released a downloadable VHD image for Lync Server 2013. To evaluate Lync Server 2013, you install the Lync software on an existing computer on-premise or in your private cloud.
A wizard-driven install experience includes three main activities to complete to get Lync Server 2013 running in your environment for simple evaluation:
  • Prepare Active Directory
  • Install Lync Server System
  • Install Administrative Tools
Download the Microsoft Lync Server 2013 Evaluation setup DVD (.ISO file image) from this link: http://technet.microsoft.com/en-us/evalcenter/hh973393.aspx

Prepare to install Lync Server 2013

Follow these steps to evaluate Lync Server 2013 on a single computer:
#1 Prepare a computer to install Lync 2013 Server, for example spin up a virtual machine (VM) running Windows Server 2012 with all updates.
#2 Install the Web Server (IIS) role, Windows Identity Foundation 3.5, the Desktop Experience under User Interfaces and Infrastructure, .NET Framework 3.5 and 4.5 including HTTP Activation, and the Remote Server Administration Tools Active Directory Administrative Center features using Server Manager.
#3 Run the Microsoft Lync Server 2013 setup.exe located in the \Setup\amd64 folder on the software distribution media.
#4 “In order to run the software on this CD, the Microsoft C++ 2012 x64 Minimum Runtime - 11.0.50727 Package must be installed. Do you wish to install it?” Click Yes.
# 5 At the Specify the location for the installation files, as shown in Figure A, you can select the default location, C:\Program Files\Microsoft Lync Server 2013 and press Install.
FIG-A-Lync-Server-Install-Location.jpg
Confirming the Lync Server 2013 installation location
# 6 Accept the license agreement and installation of Microsoft Lync Server 2013, Core Components will begin.
#7 The Lync Server 2013 Deployment Wizard welcome screen will appear as shown in Figure B. To continue, click on the first task, Prepare Active Directory.
FIG-B-Lync-Server-Deployment-Wizard.jpg
Lync Server 2013 Deployment Wizard guides installation.
#8 Preparing AD for Lync Server involves seven (7) steps that are clear and easy to execute from the tasks shown in composite screen shot in Figure C. Begin by clicking Run on the first step, and follow the tips from the wizard to complete the seven steps. Click Back when all steps are complete.
Prepare Active Directory for Lync Server has 7 steps.
#9 Returning you to the Lync Server 2013 Deployment Wizard seen in Figure A, click on Prepare First Standard Edition Server, which becomes available after preparing AD. Figure D shows the next section of the wizard, and lets you know that SQL Server 2012 Express will be automatically installed and configured. Click Next and the remainder of the setup including SQL Server 2012 Express is hands-off.
FIG-D-Prepare-Standard-Edition-Lync-Server.jpg
Starting to prepare the first Standard Edition Lync server.
#10 Configure your private DNS records: You will define DNS SRV records (_tcp_sipinternals: 5061) and host records for the meet, dialin, and admin names that point to your Lync 2013 server.
#11 Again at the Lync Server 2013 Deployment Wizard seen in Figure A, click now on Install Administrative Tools. Following this, you will find some tiles on your desktop as seen in Figure E. Run the Lync Server Topology Builder application and select New Topology.
FIG-E-Lync-Administrative-Tools-Desktop.jpg
Lync Server 2013 Administrative Tools
 #12 In the Create New Topology dialog page, enter the primary SIP (Session Initiation Protocol) domain for your company. On a following page you can specify additional supported SIP domains. You will need to name your Lync site and provide some location details--you can add additional Lync sites later using the New Site wizard.
#13 After creating the new topology, continue with the New Front End Wizard task. Figure F shows the first page of this wizard and the bullets list the main tasks to be completed.
FIG-F-Define-the-New-Front-End-Pool.jpg
Define New Front End Pool wizard provisions your Lync server.
#14 To deploy a Standard Edition Lync server, enter the AD fully qualified domain name (FQDN) of the Lync server computer when prompted. Next you will decide what additional Lync features to install as shown in Figure G. Instant Messaging (IM) and presence are always enabled, and while most other options are only used with enterprise voice and advanced setups, consider deploying the conferencing features for your evaluation.
FIG-G-Select-Features.jpg
Selecting additional Lync server features to deploy.
#15 In following wizard pages, for your evaluation, you can bypass the Mediation and Edge Pool services without entering anything, just click Next. Likewise, for your evaluation, accept the default settings regarding using SQL Server Express and creating a file share.
#16 At the Specify the Web Services URL page, modify the External Base URL to match the public DNS name that will be used for Internet-based Lync services.
#17 At the Select an Office Web App Server page, for your evaluation, unselect the Associate pool with and Office Web App Server option. (This means you can’t share PowerPoint presentations during meetings. If you need to evaluate this feature, follow the steps in the wizard to set up a new Office Web App Server.) Click Finish to complete the front end deployment.

Publish Lync topology and install Lync Server

After completing the server setup steps, the next task is to publish the Lync topology. Follow these steps to publish the topology, essentially deploying and activating the Lync features you selected with the configuration settings defined during server setup.
  1. From the Lync Server 2013, Topology Builder screen, select Action -> Publish Topology. At the Publish the Topology page, click Next.
  2. A “to-do” list will appear in Notepad after the wizard is complete. The list will remind you of the DNS hostname entries that are required and that certificates may need to be issued or reissued to match the listed hostnames.
  3. From the Lync Server 2013 Deployment Wizard, select the link Install or Update Lync Server System. Execute the four steps shown in Figure H to complete the server installation. Consult the reference at More Information below on detailed steps.
FIG-H-Deployment-Wizard.jpg
Running the install or update Deployment wizard is the last step.

More Information

Microsoft has a free e-book, Microsoft Lync Server 2013 Step By Step for Anyone, by Microsoft Lync MVP Matt Landis that gives step by step instructions on how to install Lync Server 2013 on Windows Server 2012:
http://gallery.technet.microsoft.com/Lync-Server-2012-9d6fe954



Evaluating Lync Server 2013: Installation steps - TechRepublic

Saturday, August 17, 2013

NYT hackers resurface with new arsenal

Summary: The hacking group behind attacks on The New York Times have returned -- with a new selection of weapons and a new campaign.

A hacker group that is believed to be behind a four-month campaign against The New York Times has returned with a new bevy of tools at its disposal, according to researchers.
The Chinese advanced persistent threat group, known as APT 12, "persistently" attacked the media outlet for months. The hackers, specializing in the acquisition of sensitive data, went after journalist passwords in an attempt to find out the details of human rights activists. However, the group have also been known to target governmental and military agencies in the past.

The Times believed the attacks were related to an investigation the outlet carried out which found that the Chinese Prime Minister had accumulated "several billion dollars through business dealings."
According to a blog post published by research firm FireEye, after laying low for several months, APT 12 appears to be mounting assaults with new-and-improved malware.
The latest campaign, believed to be part of a "massive spying operation based in China," leverages updated versions of malware Backdoor.APT.Aumlib and Backdoor.APT.Ixeshe.
The new variants were discovered after the security team investigated attacks against an "unidentified organization involved in shaping economic policy."
"We cannot say for sure whether the attackers were responding to the scrutiny they received in the wake of the episode," the report says. "But we do know the change was sudden. Akin to turning a battleship, retooling TTPs of large threat actors is formidable. Such a move requires recoding malware, updating infrastructure, and possibly retraining workers on new processes."
The new version of Aumlib is now able to encode types of HTTP communications. Aumlib has been used for years in targeted attacks and has a well-known signature. The malware now contains a new POST request which is encoded unlike the previous version. It is believed that this small change could allow the malware to circumvent existing IDS signatures designed to detect older variants of the Aumlib malware family.
The latest version of Ixeshe, often used when targeting systems in East Asia, uses new network traffic patterns, which FireEye believes may be an upgrade to avoid traditional network security systems.
Both malware types have not been changed since 2011. Groups that are able to systematically take on networks that require heft behind campaigns -- and therefore are likely to have substantial financial backing -- don't need to draw unnecessary attention, making the evolution of such tools significant.

The researchers note:
"Knowing how attackers' strategy is shifting is crucial to detecting and defending against today’s advanced threats. But knowing the 'why' is equally important. That additional degree of understanding can help organizations forecast when and how a threat actor might change their behavior -- because if you successfully foil their attacks, they probably will."


NYT hackers resurface with new arsenal | ZDNet


Tuesday, August 13, 2013

Corporate espionage or fearmongering? The facts about hardware-level backdoors

Spying accusations against Chinese companies like Huawei have resulted in bans by US, UK, and Australian government agencies. Is there any technical merit to these charges?
Over the last few years, accusations of unlawful spying have been made against some of China’s largest technology firms. Among the people making the allegations are former NSA and CIA head Michael Hayden, as well as in a 2012 House Intelligence Committee report. Accordingly, various government agencies in the United States, Canada, Australia, the United Kingdom, India, and New Zealand have banned the use of equipment made by various Chinese manufacturers under fears that hardware-level backdoors could exist in these products.
But, how feasible could creating such a backdoor be? In the age of the Web, and with organizations like iFixIt tearing each new gadget they can get their hands on apart, typically within a day of launch, how could such a backdoor be deployed without anyone noticing? A closer look into the claims being made and their technical feasibility is vital to understand if the accusations have merit, or are just fear mongering.

Lenovo

Out of the companies targeted, Lenovo Is the most visible to consumers and IT professionals. Lenovo largely became a household name across the world after buying up IBM’s PC business in 2005. Lenovo is partially owned by the PRC, through some abstraction: the state organization “Chinese Academy of Sciences” (CAS) owns 38% of Legend Holdings, which is Lenovo’s largest shareholder at 34%.
Lenovo hardware is reportedly banned from the US CIA, as well as the UK’s MI5 and MI6, as well as the Australian Security Intelligence Organization (ASIO) and Secret Intelligence Service (ASIS). As of the time of writing, no evidence of any wrongdoing on the part of Lenovo has been presented by any of governments who have banned their hardware from use in intelligence services.
On devices as open as computers, and especially with Lenovo’s ThinkPad product line, which has been long venerated for being foremost among laptops designed with modularity in mind—featuring detailed disassembly manuals and readily available replacement parts—it is difficult to imagine that many opportunities exist to hide a hardware backdoor in a relatively open product. Combined with the fact that the vital components (processor, RAM, etc.) aren’t made by Lenovo, there are few opportunities for Lenovo to introduce a hardware-level backdoor in a way that wouldn’t be glaringly obvious to any engineer armed with a screwdriver.
Of note, it is important to remember that the BIOS/UEFI which ships on computers is controlled by either Phoenix Technologies, a California company, or American Megatrends, Inc., a Georgia company. The chances of a BIOS-level exploit are low, but it remains a technical possibility. For software-level exploits, best practice is always to wipe the drive of a new system and include a fresh installation of the operating system of your choice. This approach also does away with unhelpful crapware one typically finds on a new computer.

Huawei

The recent criticism of Huawei has come primarily from ex-CIA and NSA head Gen. Michael Hayden, where, in an interview, he stated that Huawei has engaged in espionage on behalf of China. It is vital here to note that Hayden currently serves as a Director of Motorola Solutions, a competitor to Huawei. It is similarly important to note that Huawei and Motorola Solutions have been in a lengthy Intellectual Property dispute, which was settled in 2011 with Motorola paying an undisclosed sum to Huawei.
Huawei’s statement on the comments made by Hayden called it “tired nonsense we’ve been hearing for years” and “politically-inspired and racist corporate defamation”.
The technical merit behind the argument of Huawei spying on users is given life from the frequently opaque and closed nature of telecommunications equipment. Mobile phones are as closed off to the user as is possible to prevent tampering or unauthorized modification to the software or firmware to prevent users from accessing things that carriers typically charge more money for, such as tethering to a laptop. In turn, networking equipment is as closed off to the user as is possible to prevent particularly enterprising individuals from modifying their modems to do any number of undesirable things to the detriment of other network users. In short, there isn’t a level of mutual trust between vendor and user, which has breathed life into claims of espionage.
Cognizant of those concerns, Huawei offered to disclose the source code to its products to be considered for a bid to build the Australian National Broadband Network (NBN), a process which it has been formally excluded from. This gesture has not dissuaded the NBN authority from barring Huawei the opportunity to submit a bid for building the network.

ZTE

The case against ZTE is quite a bit stronger than it is against Lenovo and Huawei; actual evidence has been produced of a backdoor existing in a ZTE product. Last May, a backdoor was identified in the ZTE Score M, a budget-minded smartphone for US prepaid mobile carriers MetroPCS and Cricket. ZTE released a patch for the phone shortly thereafter, calling the exploit a “technical defect” that exposes units to “potential third-party exploitation”.
In this instance, it might be more prudent to rely on Hanlon’s razor: Never attribute to malice that which is adequately explained by stupidity. However, carelessness on the part of ZTE is all that a hacker—state-sponsored or not—requires to obtain sensitive information. If there is a reason to avoid ZTE products, it would be because of their lacking quality, or at least quality assurance procedures, not because of their complicity in spying. To their credit, the issue was patched quickly after it was discovered.

Final thoughts

The players in this debate appear all too willing to point fingers without providing hard evidence to support their claims. Surveillance activity has been a recurring topic in the news over the past several weeks, bringing worries of potential security threats to the forefront. The firms having accusations made against them are easy targets for their geographic location and business operations. However, hardware-level exploits are much more difficult to deploy without detection, and are more obvious than software exploits, which will likely continue to be the primary attack threat for the foreseeable future.

Corporate espionage or fearmongering? The facts about hardware-level backdoors - TechRepublic

Snort :: Home Page




Snort :: Home Page

Infographic: Finding the right security solution for the data center

This infographic from Cisco illustrates the issues that data centers face trying to deploy comprehensive security systems.

By Evelyn de Souza, Security Technology Group at Cisco

Today’s savvy information technology professional wants security tools and understands that protecting your organization is something that opens doors, rather than closes them. The right security solution can move businesses beyond buzzword bingo to a place where they can actually achieve these hoped-for efficiencies.
Many times as InfoSec professionals, it can be difficult to associate security investments with ROI. However, when it comes to data centers, the ROI associated with employing a comprehensive security solution goes well beyond hard numbers. The right security solution can result in avoiding higher costs and consequences stemming from potential data breaches – which are far more damaging in the long run than taking necessary preliminary precautions early.
This infographic from Cisco dives into problems that data centers face today, and how finding the right security solution can make all the difference.





Infographic: Finding the right security solution for the data center - TechRepublic

Breach Detection Systems take aim at targeted persistent attacks

You've just been told to get a Breach Detection System in place. Where do you start? How about a buyer's guide created by an independent test facility?
I’ve been asked how to prevent illicit network penetration enough times to realize an esoteric discussion of the recent advances in intrusion detection and firewall protection is not what’s needed. What is needed is a clear picture of available preventative measures, and which of the preventative measures work as advertised.
Getting up to speed, for me, means paying attention to a certain independent test lab. For the past two years, the people at NSS Labs have been testing how well Breach Detection Systems deal with Targeted Persistent Attacks.

Different terminology


It’s entirely understandable if Targeted Persistent Attacks (TPA) and Breach Detection Systems (BDS) are unfamiliar, or appear to be incorrect acronyms. To get that sorted out, I talked to John Pirc, Research Vice President at NSS Labs and published author. Starting with Targeted Persistent Attacks, I asked John why NSS Labs didn’t use Advanced Persistent Threats (APT) like everyone else. “The truth of the matter is that an APT is sometimes made up of known exploits / vulnerabilities that are not that Advanced; so the term APT doesn't define the action correctly. TPA highlights that the actor is going after a specific target such as company X or an entire industry sector like financial services, and will be persistent in attacking the target”
John also mentioned there was a detailed examination of APT versus TPA in this blog. Next, I asked John why NSS Labs prefers to use Breach Detection System instead of Next Generation Intrusion Prevention System and Next Generation Firewall:
“The BDS, NGIPS, and NGFW products are similar in that all three can contain signatures and heuristics for identifying malware. However, a BDS separates itself from the pack with its ability to analyze the patterns of network traffic, identify malicious domains, and model the behavior/impact of files that are being downloaded and executed on an attack surface.
In some cases, BDS vendors are able to detect zero-day malware at various stages of propagation, and provide remediation. The ability to identify still-unnamed malware on your network is almost like having your own zero-day research team on site.”
BDS technology having proactive capabilities plus remediation is significant. I asked John how that was accomplished:
“What separates BDS from IDS/IPS is detecting unknown malware. Breach Detection Systems, unlike IDS/IPS, have the ability to model malware behavior through emulation and sandboxing or a combination of both. This places BDS at a distinct advantage over IDS/IPS; as they can identify the presence of dropped files, analyze them, determine if they are known bad or unknown bad, and monitor for command and control callbacks.”
Now that we’re on the same page, I’d like to look at how NSS Labs goes about testing Breach Detection Systems.

BDS testing

To start, this excerpt from the BDS Test Methodology paper describes what the testers will be looking for:




  • Centralized management of multiple devices.
  • Breach detection capabilities using one or more of the following methods:
    • Malware identification (signatures, heuristics, or both).
    • Network traffic analysis (flow monitoring, content analysis, or both).
    • Sandboxing that allows for modeling internal systems (workstations and servers).
    • Browser emulation.
    • Domain reputation to identify malicious domains.
  • Response mechanisms (for example, alerting, session termination).
  • Reporting.
The remaining 18 pages of the test methodology report go into intimate detail explaining how the engineers at NSS Labs determine whether a BDS device meets expectations or not.

Test results

At the beginning of this article, I mentioned my reliance on NSS Labs to get a clear picture of this complex technology. To get that clarity, besides reading how NSS Labs tests BDS, I also read their annual Breach Detection Systems Buyer's Guide. The 14-page report is chock-full of analysis and recommendations. For example, here are some overall conclusions of the systems tested this year:
  • A BDS is able to detect threats by using a network appliance or stand-alone endpoint, or by using a combination of both.
  • A BDS can identify pre-existing breaches as well as malware that is introduced to the system through side channels.
  • A BDS that is unable to identify side-channel attacks or command and control traffic from infected machines is little more than a network AV device.
  • While high-end network core switches will be capable of supporting most BDS requirements, NSS engineers have noted port-spanning issues with many workgroups switches.
Next NSS Labs offered the following advice for those thinking about purchasing a BDS: “Enterprises looking to deploy a BDS should understand that there are differences in the maturity, technology, and scalability of the solutions that are offered by different vendors.”
Both the paper on BDS test methodology, and the BDS buyer’s guide provide an abundance of information, affording IT pros the opportunity to get familiar with Breach Detection Systems.
Here’s a list of vendors that are offering BDS products.
  • Check Point
  • Damballa
  • Fortinet
  • McAfee
  • Palto Alto networks
  • Sourcefire
  • Trend Micro
John mentioned that not all of the above vendors have submitted systems for testing as of this post, and to contact NSS Labs to see if there is a test report on a system you are considering.

Final thoughts

With something as complex as Breach Detection Systems, I’m glad there is such a thing as a buyer’s guide. I’d be nervous having to base a decision on one vendor’s market-speak versus another’s.


Breach Detection Systems take aim at targeted persistent attacks - TechRepublic





Restore Windows 8 with System Image Recovery

In a recent series of blog posts, I've shown you how to use two of Windows 8's new recovery tools, Refresh your PC and Reset your PC. While the Reset your PC tool will allow you to essentially start from scratch and the Refresh your PC tool will allow you to install a new copy of the operating system while retaining your data, you may also want to have a backup of your full system - data and applications - on hand, just in case you encounter a catastrophic hard disk failure.
If so, you'll be glad to know that the tried and true System Image tool still exists in Windows 8 and as long as you have created a system image of your hard disk, you can use the System Image Recovery tool to recover your entire system in the event of a hard disk failure. In other words, if your hard disk goes south, you can purchase a new hard disk and use the System Image Recovery tool to restore your system to the state it was in at the time that you created the image.
Now, keep in mind that for this type of backup to be truly effective, you need to regularly create new System Images so that in the event of a recovery, you will have a recent version of your system.
In this edition of the Windows Desktop Report, I'll show you how to use System Image Recovery tool from the Recovery Drive to restore your hard disk. As I do, I'll also show you how to create a System Image on a set of optical discs.
This post is also available as a Slideshow Image Gallery.

What you need

In order to run the System Image Recovery tool as I'll describe in this article, you'll need to have created a Recovery Drive as I showed you in the article Create a Recovery Drive in Windows 8. You'll also need a set of optical discs or on an external drive on which to create a system image of your hard disk.

 

Creating a System Image

As I mentioned, in order to use the System Image Recovery tool you must have created a system image of your hard disk. As such, I'll begin by walking you through the steps required to create a system image.
To create a system image in Windows 8, you'll start by accessing the oddly named Windows 7 File Recovery window. (Why not just call it File Recovery or Windows Backup and leave it at that?) To do so, use the [Windows] + W keystroke to access the Search Settings page. Then, type Windows 7 File in the text box and click Windows 7 File Recovery, as shown in Figure A.


Accessing the Windows 7 File Recovery tool from the Start screen is easy.[Figure A]






In a moment, you see the Windows 7 File Recovery user interface and you should select the Create a system image command on the left side of the screen to launch the creation tool. On the first screen you will need to choose where you are going to create a system image. For my example, I am going to create the system image on a set of DVD+R discs in the DVD RW drive, as illustrated in Figure B.

 
On my test system, I'll create the system image on a set of DVD+R discs.[Figure B]















When you click Next, you will be prompted to confirm your backup settings, as shown in Figure C. As you can see, in addition to the main partition, the System Reserved partition is also selected to be backed up. On my test system, which is pretty bare bones at this point, the system is indicating that the image will take up 36GB of space. (When the operation was complete, the system image, with compression, only required three 4.7GB DVD+R discs.) When you are ready, just click the Start backup button.

 
On the Confirm your backup setting page take a look at the information presented and then click the Start backup button.[Figure C]
















As Windows begins preparing for the operation, it will prompt you to label and then insert the first DVD disc This process is illustrated in Figure D.

 
To get started, insert the first disc and click OK.[Figure D]












Once you insert the blank disc, you'll be prompted to format it. Make sure that you select the Don't ask me again for this backup check box before you click the Format button. The operation will then format the optical media, as shown in Figure E.

 
Make sure that you select the Don't ask me again for this backup check box.[Figure E]











As the backup operation gets under way, you'll see progress indicators letting you know the status of the operation, which includes verification of the media once the backup portion is complete. After each disc is verified, you'll be prompted to insert a new disc. This process is illustrated in Figure F.

 
Creating a System Image on DVDs includes a verification operation.[Figure F]











When the System Image creation procedure is complete, you'll be prompted to create a System Repair disc, as shown in Figure G. However, as you may remember, a System Repair disc is the same as the Recovery Drive and if you have already created a Recovery Drive, you can just click No and you will be notified that the backup completed successfully.

 
In Windows 8, the System Repair disc is the same as the Recovery Drive.[Figure G]











Now that you have a System Image backup, you are ready for an emergency situation.

 

Launching System Image Recovery

In the case of a hard drive failure, you can restore Windows 8 by running the System Image Recovery tool from the Recovery Drive. While I am booting from a USB Recovery Drive, you can just as easily boot the Recovery Drive from the optical disc. (As a part of my research for this article, I ran the System Image Recovery tool after booting from an optical disc and the procedure is basically identical.)
After your system boots from the Recovery Drive and you are prompted to choose an option, select the Troubleshoot tile as shown in Figure H.

 
When you are prompted to choose and option, select the Troubleshoot tile.[Figure H]













When you see the Troubleshoot screen, as shown in Figure I, select the Advanced options tile.

 
From the Troubleshoot screen, select the Advanced options tile.[Figure I]













When you see the Advanced options screen, as shown in Figure J, select the System Image Recovery tile.


 
From the Advanced options screen, select the System Image Recovery tile.[Figure J]












You'll then be prompted to choose the operating system that you want to recover, as shown in Figure K. Now, when performing a system image recovery operation, it seems redundant to have to select the operating system, but you must click the Windows 8 tile to get started.

 
Choose Windows 8 [Figure K]

 

 

 

 

 

 

 

The recovery process

As soon as you click the Windows 8 tile, you'll see the Re-image your computer wizard and the tool will immediately begin looking for media containing the system image, as shown in Figure L.


The Re-image your computer wizard will immediately begin looking for media containing the system image.[Figure L]
When it can't find the system image, it will prompt you to insert a disc. Take note that when restoring from DVD, you must first insert the final disc in the set, as shown in Figure M. The reason being is that when you create a system image, information required by the restore operation is saved on the final disc.

Information required by the restore operation is saved on the final disc. [Figure M]
When you insert the final disc, the Re-image your computer wizard will read the information on the final disc and then display the details of the system image, as shown in Figure N. As you can see, my system image is on drive F, it was created on 2/25 at 11:28 PM, and it is the image for the computer named Jovian-8. When you are ready, just click Next.

When Re-image your computer wizard is ready to begin, it will display the system image details.[Figure N]
You'll then see the second screen of the Re-Image Your Computer wizard, as shown in Figure O. As you can see, this screen provides you with several options. If you are restoring to the same hard disk, you don't need to select the Format and repartition disks check box. (For my example, I selected the Format and repartition disks check box, just to see if that changed the process in any way. Other than possibly adding a little time to the process, the steps and the end result were the same.) If you are restoring to a new hard disk, chances are that the Format and repartition disks check box will be selected by default and will be unavailable. If that is the case, there is nothing to worry about as long as the new hard disk is of the same capacity or greater than the old one.

The second screen in the Re-Image Your Computer wizard provides you with a number of options to choose from.[Figure O]
If you have multiple drives you can click the Exclude Disks button and choose the drive(s) you want to leave untouched. If you click the Advanced button, you'll see a dialog box that will present you with two additional options. An Automatically Restart check box will be selected by default and you'll have the option to enable a disk check operation as a part of the procedure. (Now, if none of the options are available on this dialog box, you may have to install drivers for the disks you are restoring by clicking the Install Drivers button.)
When you click Next, you'll see the confirmation screen of the Re-Image Your Computer wizard, as shown in Figure P. To continue, just click Finish.

To complete the Re-Image Your Computer wizard, just click Finish.[Figure P]
Of course, there is one more confirmation to work through, as shown in Figure Q. Just click Yes to get started.

Just click Yes in the final confirmation dialog box.[Figure Q]
You'll then be prompted to insert the first DVD in the set, as shown in Figure R. Once you do so, just click OK.

Once the operation is set to begin, you'll be prompted to insert the first disk in the set.[Figure R]
In a moment, the restore operation will begin and you'll see a progress bar that keeps you apprised of the status of the restore operation. Depending on how big your hard disk is, the restore operation can take a few hours. As each DVD in the set is restored, you'll be prompted to insert the next one.
When the restore operation is complete, you'll be prompted to click the Restart now button. If you happen to be away from your desk when this occurs, your system will restart on its own, as shown in Figure S.

If you happen to be away from your desk when the restore operation is complete, your system will restart on its own.[Figure S]
When, your system restarts, you'll see the familiar logon screen.



Restore Windows 8 with System Image Recovery - TechRepublic



Related Posts Plugin for WordPress, Blogger...