Vol. 19, #2 - January 13, 2014 - Issue #962
Migrating a Hyper-V cluster between domains
- Editor's Corner
- From the Mailbag
- Migrating a Hyper-V cluster between domains
- Tip of the Week: Internet Explorer not remembering last window size
- Recommended for Learning
- Quote of the Week
- Admin Toolbox
- Admin Tools We Think You Shouldn't Be Without
- Events Calendar
- Webcast Calendar
- Register for Webcasts
- Tech Briefing
- Cloud Computing
- Enterprise IT
- Windows Server
- Windows Server News
- An argument for the single cloud vendor approach
- Vendor options for VDI deployment -- sans Microsoft
- Is there a magic number: Finding the best server consolidation ratio
- No need to reinvent the wheel with Windows desktop manager commands
- WServerNews FAVE Links
- This Week's Links We Like. Fun Stuff.
- WServerNews - Product of the Week
- Microsoft Active Directory, Exchange and SQL Backup - Veeam® Backup & Replication™.
- SAVE THIS NEWSLETTER so you can refer back to it later for helpful tips, tools and resources!
- FORWARD THIS NEWSLETTER to a colleague who you think might find it useful!
- SEND YOUR FEEDBACK to [email protected] if you have any comments or suggestions!
This week's newsletter examines how to move a Hyper-V cluster between Active Directory domains with a guest editorial by Quentin Gurney, Operational Excellence Project Manager for Enterprise Services with Ingersoll Rand. Moving server workloads is never easy, but then moving your possessions when you buy a new house isn't so simple either because if you don't hire the right moving company you could have problems as this Dilbert comic illustrates:
Spotlight on this Issue
Be sure to see this issue's Tip of the Week and provide feedback if you have suggestions on how it could be improved. Also check out the Recommended for Learning section for some new books on different aspects of cloud computing.
From the Mailbag
We've recently examined whether the file server is dead in two issues of this newsletter, Issue #958 Is the File Server dead? and Issue #961 Revisiting the File Server's Untimely Demise. Our readers continue to send us their feedback on this topic, here's a sampling:
A reader that goes by the initials D.G. who was a former Information Systems Security Officer said:
I have read over the past several years all of the cloud computing hype. I see that more and more companies are moving all their data onto the cloud servers for management. I personally think that the cloud server data base is appropriate for people such as the sales force or others that do a lot of traveling as part of their jobs. The cloud provides a data source that is available anywhere including airlines in flight.
As a former Information Systems Security Officer I do have a couple of questions that every company should answer before they put all of their apples onto a cloud server:
1. When the company providing your cloud service has a server crash or is off line due to some natural phenom (hurricane, ice storm, earthquake, etc.), how long can your company survive without access to your data?
2. When the company providing your cloud service is hacked and your proprietary company information is compromised, do you really believe they are going to inform you?
3. Do you really want to allow some other company to have total access to and provide security for your company proprietary data?
4. Are you willing to only be able to have access to your data but no control over backups or permanent storage (if appropriate)?
It might be appropriate for companies to consider some combination of both cloud service and local file servers. Keep the really important stuff local to the company so that you have total control over it. Then any compromise is truly your problem. Use the cloud for remote access to data that you can copy down locally and store at your own frequency, but is still available to those traveling to have access.
I basically agree that the best solution for most companies nowadays is a hybrid approach that integrates an on-premises IT infrastructure with a cloud provider's service offerings. The key is to figure out which stuff to keep on-site and which to migrate into the cloud. Any more suggestions concerning this? Email me at [email protected]
Andrew, an IT Support Manager in Australia, had this to say:
I just had to chip in here with an overseas perspective. The Government of the USA has almost guaranteed that the file server, on premise, will remain with the outing of their current snooping campaign. Companies in the US may like to think that they are not going to be affected by these revelations, but the day will be coming when the Chinese having a back door into my router is a lot less oppressive than a supposed ally snooping on my business data, on almost any device connected to the network, any network.
Over the next 3 years you'll see all of the major hardware players come out with Hardware certified for use overseas (outside the US and its territories) to protect their business models. If they don't what you'll find is that an NSA proof overseas vendor will be formed to develop these systems on the server and desktop end to stop the snooping.
The cloud is the greatest risk to security that has ever existed. Would you put all of your personal banking and credit card details in the cloud? Me neither.
This is obviously a hot topic in the news media these days, and many are saying the NSA revelations spell the end of the cloud as a viable business model. My own perspective is different however: I don't think anything is going to stop the march to the cloud. The reason is simply that cloud computing is too alluring from a cost-cutting perspective because it enables companies to fire their IT staff and replace up-front hardware acquisition costs with predictable monthly budgeting.
The bottom line for companies of all sizes is making a profit, and reducing cost is always going to trump other considerations like security and privacy. After all, just look at how companies jumped on the outsourcing bandwagon a few years back by moving their helpdesk operations to countries where the labor costs are low. The result of course is that customer satisfaction with customer service is at an all time low, but do most companies care? Not really.
So basically I think the fallout from the NSA revelations isn't going to last. The reason of course is that most of the outrage expressed by other countries against the USA is simply posturing and striving for an advantage. After all, most other nations are doing something similar. Things will change of course, laws will be passed and regulations will be implemented, but ultimately everything will still pretty much remain the same. Agree? Disagree? Let me know at [email protected]
Another reader from Australia said:
Been reading the topic on whether or not people think the file server is dying out, interesting to get other peoples thoughts.
Last year, we had a fire at a major telco's exchange, wiped out telecommunications to about one quarter of the state, 60,000+ connections where off line for 2 weeks and a lesser percentage still off line after 3 - 4 weeks.
No phones (landlines or mobile), no EFTPOS, no internet. Banks closed because their security systems were unable to talk back to their HQ's. All this and of course, no cloud.
I was working on selling cloud services to businesses in that part of the state, now I've completely dropped the idea.
I can't see file servers ever being removed entirely from businesses large or small. There are savings and benefits with cloud services, but I believe the risk outweighs the benefits.
Good story, but as you indicate such an event affects more than just whether businesses can connect to cloud services they've subscribed to. If you can't use your landline or cellphone you can't do business, and if you can't process financial transactions you can't do business. I think your story doesn't just show how vulnerable cloud computing is to disasters, but how vulnerable virtually all aspects of today's businesses are to these kinds of happenings.
A Canadian reader named Carl from Calgary, Alberta said:
Sorry to keep dragging this topic out, but I laughed aloud when I read this: "Lastly, to put the final nail in the file server coffin, my local telco (frontier telecom -- in Portland Oregon) has been quietly upgrading their fiber switches to support gigabit to the remote premise! in other words, soon, we will all be gig-capable connected "
I'm in a major Canadian city with a population of over 1 million and I still can't get DSL at the full rated speed due to the lack of infrastructure at the telco.
I can only dream about things like fiber.
Yes that definitely is a problem! But in a big city like Calgary? Yikes!
A reader named Israel shared as follows:
I completely agree with some of the comments…There is nothing that compares to on-site file servers, for storage or application. I warned my employer of this when we took our main sql-based SaaS to the cloud, it is so slow we are at times nonfunctional, and this is on a 100Mbps channel. Now we are tied to a 5 year contract, 1 down, 4 to go. If you need speed-critical access to your files/apps my only advice is, don't do it!
Gotta watch out for those long-term contracts!
A reader named Marlin said:
My biggest problem with the one size fits all approach is that all of the IT vendors are making assumptions that bandwidth is the same across the country. I know in my company, we are working open source software into our computer center because of this problem and increasing costs of software.
One point I think you should mention is that once the big IT vendors have gone too far south on pricing, it is inevitable that there will be price increases which won’t be small. That will force individual companies to once again consider the price of moving from the cloud which was once quite cheap, back to in-house computing centers. The cost of doing so with be enough to make people think twice about it, but there will be a move back to purchasing licenses as they have for years, and quite possibly start using open source solutions when the IT vendors try to stop the backslide from the cloud.
Frankly, I guess I have been involved in IT long enough as a VAR that what we see today is no different than the old IBM mainframe and DEC minicomputer days of time-sharing, etc. If you think about those days and the problems we ran into, what is basically different? It’s the same ebb and flow…
History repeats itself, and we never seem to learn from the past. Such is mankind.
Finally, a reader named Tom from Washington State, USA said:
I have never been a proponent of moving away from company owned and managed servers and have always made the point of losing control to third party vendors. This is especially true when it comes to email, as no third party entity gives a tinker's damn about you or your company spinning wheels, unable to produce, when the mail server goes down. Being an Exchange and Outlook pro, and having an actual care about my clients, results in very limited down time when it comes to email. Like the third party vendor, I'm just a phone call away, but I'm here, not 1 or several states (or countries) away, and again; I care and will address the issue right then and there.
As for storing my company's info somewhere else, the same train of thought goes. The proponents of this 'cloud' strategy first and foremost mission is taking your IT $, and far down the list is any speedy, take ownership of the issue mentality, once they have you, you're at their mercy. While there are some cloud companies that actually do have a valid service record, in dealing with third party vendors over the years, these are few and far between. The only true benefit to off site server usage is to those whose business has veered into that service area.
Too true unfortunately. Some vendors are fly-by-night operators you simply can't trust. Others promise the sky and actually think they can deliver it but when push comes to shove they can't. The really big ones may be reliable, but their size gives them leverage that can make it hard to negotiate good terms. But the business world has always been this way, hasn't it?
And now on to our guest editorial by Quentin Gurney...
Migrating a Hyper-V cluster between domains
Sometime during your IT career you will have to deal with a company merger or sale. That means you will need to migrate all the assets from one AD domain to another. There are some tools that can help you do this, but what you will find is that none of them support moving a cluster from one domain to another. In fact you will find that there is no support available from Microsoft for that kind of a mission. With many companies using Hyper-V clusters, you will very quickly have a big problem on your hands unless you can find a trail of "electronic breadcrumbs" left behind by those that have blazed the trail before. In this article we will walk through the process of moving a Hyper-V cluster between domains. The process described is the safest one possible, but of course there is risk involved, so make sure have a current back up of everything before you push any buttons, and you understand each step and the whole process before you attempt it.
Migrating a cluster from one domain to another is basically destroying the cluster in one domain and building it again in the other domain. It this method, we will have two separate clusters active at the same time. We will take parts from one cluster, migrate them to the new domain and bring up the cluster in the new domain. Then as we remove pieces from the old cluster, we will move them across till all the pieces are in the new domain. It is also possible to do it all at once but there is more perceived risk in that approach -- although you will find it to be faster. The following instructions cover 2008 R2 and 2012. If you have a 2008 cluster, you would be best off building a new one as the technology is vastly superior in subsequent versions and by now the hardware is likely out of warranty.
- Get your patch levels current for both OS and hardware. If you are not fully patched for your OS and hardware you could find yourself battling issues that would not otherwise have caused you problems. For instance there is a patch in 2008 R2 SP1 that enables cluster setup using credentials from a trusted domain.
- Run a cluster validation before you even think about doing anything. If your hardware kit will not pass a validation before you move, then the odds of it building correctly in the new domain is just about zero. If your cluster does not pass validation, you will not have any support from Microsoft if you call in on a case, and while you may be able to skip validation, there are no guarantees that it will assemble properly either.
- Please -- no questions on why I know that 1 and 2 are very important……
- Make a note of the existing cluster IP for the cluster name object, and make sure you have a spare IP address to be used for the new cluster since you will have to have two cluster name objects at the same time, one for the cluster in the old domain and one for the cluster in the new domain.
- Make a list of your VMs per Cluster Shared Volume (CSV). CSVs cannot be shared across clusters so making a list is a good thing to do as they will not be visible in the console.
- Make a note of all the folder names under the C:\ClusterStorage namespace and how they map to your CSVs. If you happen to have any snapshots, please merge them to make this as simple as possible. Make a screenshot of the c:\clusterstorage directory and the folders underneath and save it off to a safe location. When you create the new cluster the folder names will need to match. These folders have the VM names and files in them.
- Take screenshots of any LUN mappings including any pass through LUNs so you will be able to re-create them when we map them in the new cluster. This will not likely be needed, but better safe than sorry. If you happen to user cluster file sharing, make notes of names/IPs and LUN mapping.
- Make a note of all the networks you have and what their names are if you have given them custom names.
- Make sure you know how your witness disk is set up and take some screenshots for future reference.
- Move all VMs off of one node in preparation to evict it.
- Evict the node on which you just removed the VMS from the existing cluster. This is done in the failover cluster manager.
- Do a /forcecleanup on the node that was just removed. The command for 2008 R2 is: "cluster node servername /forcecleanup" In 2012 server, use PowerShell command: "Clear-ClusterNode -Name servername --Force"
- Join the node you just cleaned up to the new domain. This will require a reboot.
- Change your DNS servers in IP settings to be servers in the new domain. Change any domain suffix search orders as necessary -- (for instance add the new domain, and its DNS servers)
- Make sure you have a cluster name object account created in the new domain. This will require a cluster name object created by a domain admin, with appropriate rights delegated to you unless you happen to be a domain admin. (Full control of object plus all child objects). The cluster name object needs to be in a disabled state when you create the new cluster.
- Create a new cluster on the node in the new domain using the new cluster name object and a new cluster IP address. You will need a new IP address for the cluster name object when you do this because it would otherwise conflict with the other part still in the old domain. You will be prompted to run a cluster validation which you should do.
- Shut down all the VMs on the old cluster in the old domain on the CSV(s) that will be moved to the new cluster.
- Delete the VMs from Failover Cluster Manager (FCM). They are no longer highly available, but they still exist and you will need them. Do *NOT* delete the VM from Hyper-V Manager
- Take the CSV(s) offline and remove it (them) in the cluster manager.
- Take the storage volume hosting the CSV offline and delete the disk from FCM along with any other LUNs you have other than the witness disk LUN (e.g. pass through LUNs or cluster file share LUNs). The witness disk must stay till the cluster is destroyed.
- Ensure that these LUNs are not presented in any form to the old cluster.
- Present the LUNs to the host in the new cluster in the new domain.
- Enable cluster shared volumes in the failover cluster manager on the new cluster.
- Open up Computer Management on a node in the new cluster, go to Storage and re-scan for new storage.
- Bring those LUNs online (as default SAN policy is Offline Shared). If its prompting to Initialize the disks, Don't *DO* that, and this needs to be investigated further.
- In FCM, go to Storage -- Add Disk -- Select the disk you brought on previously
- Go to Cluster Shared Volumes -- Add Storage -- select the storage added previously
- It may have the same name but if not tename the new folder under the C:\ClusterStorage namespace back to what it was previously called (i.e., the namespace(s) as per previous cluster configuration). You saved a snapshot of this.
- Open Hyper-V Manager, the VM status should change from Critical to Normal
- Evict all the other nodes from the old cluster. The last one you will have to do a "destroy cluster" because it will not let you remove the last node.
- Do a force cleanup on each evicted node as done previously on the first node.
- Join all the nodes to the new domain. This will require a reboot.
- Present the witness disk to the new cluster and configure it the same way it was previously. You may get a warning that your configuration is wrong. That will go away after all nodes are joined provided it was not complaining before migration.
- One by one, join the remaining nodes to this new cluster.
- Change DNS and DSSO settings to ones appropriate for the new domain on each server you join.
- Rename any networks you had before as they were named prior to migration.
- If you used a temporary IP for the cluster name object, then swap it back out for the one previously used on the cluster before it migrated.
- Make all VMs highly available using FCM.
- Start the VMs. Distribute VMs to nodes as you bring them up so the load is balanced on the cluster.
- If you happened to use Cluster File Shares, recreate the virtual servers and re-assign their former IPs.
- Do another cluster validation so you are confident everything is working as it should and you will be able to get support if needed.
While that sounds really complicated, it is a logical straightforward process. It boils down to destroying and recreating a cluster while not touching the hyper-V settings. After the new cluster is back together, they Hyper-V components find all the references they had previously and all is well again. As long as you do not touch the Hyper-V settings you should be fine. A more complicated way to do this would be to completely rebuild the nodes from a fresh install. If you do that, you will have to export all your VMs and re-import them. That will take a lot more time.
You can use a very similar process with migration of SQL clusters as well. The bad news in that situation is that SQL will have to be re-installed completely from scratch after moving to the new domain, so if you do an SQL cluster, make sure you export all logins, all maintenance jobs, and any other custom configuration. You should be able to detach the DBs and reattach, but recreation of some of the custom configuration would be difficult if you had not saved it. Another tip for SQL is to make sure that everything is patched to a known level, then when it is re-installed patch to the same level before bringing your DBs back.
In this article we have discussed moving Hyper-V host clusters between domains and have laid out an approach that seeks to minimize risk and give the best outcome. It is definitely something that is a more advanced topic of server management, but one that you can certainly accomplish with some patience and study. As for all those VMs -- they are easy. You can migrate them with any of the popular tools or even do them manually. Best of luck to all who venture into these waters!
About Quentin Gurney
Quentin Gurney, MBA, BSEE, is currently an enterprise architect working for a fortune 100 company. His past job history has included time spent in IT, Finance, Engineering Program management, and a stint as a beekeeper. Lately he has been involved in virtualization strategy, active directory domain restructuring, and crafting corporate governance policies. He spends his spare time riding his bike through the counties of central Indiana.
You can find out more about him on LinkedIn at:
Send us feedback
Got questions or comments concerning anything in this issue? Let us know at [email protected]
Tip of the Week: Internet Explorer not remembering last window size
This one has been nagging me for quite a while. I'm still using Windows 7 on my main workstation and one of the big annoyances I have with it is that Internet Explorer won't remember its last window size. For example, I open IE, manually resize the window to the size I want it to be, close IE, reopen IE, and it doesn't remember how I sized it. This can get frustrating if for some reason I starts opening with a very small window size as it means every time I launch the program I have to resize the window, argh...
I searched the help forums on this issue, but none of the suggestions they offered seem to work. Then this morning while writing this newsletter I found a way to make Internet Explorer remember how I resize its window. Here's what I did:
- First, I have IE pinned to the taskbar so I can launch it quickly.
- Next, I closed all IE windows that were open.
- Then I held down both the CTRL and SHIFT keys and clicked the IE icon on my taskbar.
- IE opened, and I resized the window the way I wanted by dragging the title bar and corners of the window.
- I closed IE and then opened it again by clicking the IE icon on the taskbar.
- Presto! IE remembered the way I resized it.
- I then resized the window differently, closed IE and reopened it.
- Wow, it remembered the NEW size this time!
In other words, it seems that closing all IE windows and then holding down both CTRL and SHIFT while clicking the IE icon the taskbar somehow "reset" IE so that it can now remember the last way I resize its window.
I don't know if this is documented anywhere, but I invite readers to play with this and see if it works for other Windows programs and on other versions of Windows. Please let me know at [email protected] if you come up with anything more on this topic and I'll share it with our readers, thanks!
GOT TIPS you'd like to share with other readers? Email us at [email protected]
Recommended for Learning
This week we have ten new books on cloud computing you might want to check out:
Managing Risk and Security in Outsourcing IT Services: Onshore, Offshore and the Cloud
Cloud Computing: A Hands-On Approach
Performance and Availability Analysis of Cloud Computing Centers
CompTIA Cloud Essentials Certification Study Guide (Exam CLO-001)
Cloud Computing: Third International Conference, CloudComp 2012, Vienna, Austria, September 24-26, 2012, Revised Selected Papers
Hacking Exposed: Virtualization & Cloud Computing: Secrets & Solutions
NIST Cloud Computing Standards Roadmap
Cloud Storage Forensics
Office 365: Migrating and Managing Your Business in the Cloud
The Great Cloud Migration: Your Roadmap to Cloud Computing, Big Data and Linked Data
We also have the following announcements from the Microsoft Virtual Academy:
January 21: Windows 8.1 Developer Training: Geek Edition
Attention HTML and XAML developers, build on your core skills, have some fun, and take advantage of awesome new features in Windows 8.1. Join Microsoft Virtual Academy (MVA) as we dive deep into gadgets and devices, including USB, Bluetooth, point of sale, and even 3d printing. And we’ll look at some early versions of great toolkits. Register here:
January 23: Windows Performance Jump Start
Want to learn about the tools used by Microsoft Global Business Support Premier Field Engineers when they need to make a CEO's computer run faster? Want to improve performance for computers that are starting slowly? Join us for a deep dive on the free Windows Performance Toolkit (WPT). Download the toolkit here:
and get ready to tackle real-world Windows performance issues that can impact organizations of all sizes running Windows Vista, Windows 7, and Windows 8. Register now for this free, live, online training from Microsoft Virtual Academy (MVA) at:
Quote of the Week
"I don't measure a man's success by how high he climbs but how high he bounces when he hits bottom." -- General George S. Patton
Note to subscribers: If for some reason you don’t receive your weekly issue of this newsletter, please notify us at [email protected] and we’ll try to troubleshoot things from our end.
Admin Tools We Think You Shouldn't Be Without
Windows Server 2012 introduced industry sweeping changes to the way we think about Operating Systems, storage, Hyper-V, networking, and clouds. R2 preview continues on that path and adds many more improvements and features to the cloud OS vision. Download this ebook to quickly learn about the new and enhanced features of Windows Server 2012 R2 preview!
Server performance problems? Find out why with FactFinder Express. See whether the issue is a slow app, slow SQL requests, or a CPU/Memory/Disk bottleneck. 30 day free trial.
Want to know how your Exchange messaging system is being used or misused? Want to know most active users, who are overusing the system and what is being stored in their mailboxes?
Free web filtering utility to protect children online:
Automate repetitive web browser tasks with iMacros:
Project Conference, 2014 on February 2-5 in Anaheim, California
Lync Conference 2014 on February 18-20, 2014 at The Aria in Las Vegas, Nevada
SharePoint Conference 2014 on March 3-6, 2014 at The Venetian in Las Vegas, Nevada
Microsoft Worldwide Partner Conference (WPC 2014) coming in July, 2014 in Washington, D.C.
European SharePoint Conference on May 5-8, 2014 in Barcelona, Spain
Add your event
PLANNING A CONFERENCE OR OTHER EVENT you'd like to tell our 95,000 subscribers about? Contact [email protected]
Register for Webcasts
Add your Webcast
PLANNING A WEBCAST you'd like to tell our subscribers about? Contact [email protected]
This section is organized topically by platform/product and provides you with links to tips, tools, information and other resources that can help you in your job role whether you're an IT professional or an IT decision-maker.
Is Hybrid Cloud the future for enterprises? (The Next Web)
HP Expands Cloud Portfolio With CloudSystem (Data Center Knowledge)
Questions to ask about Cloud and Backup (Third Tier)
Repeat After Me: SATA Does Not Belong In Servers Part Deux (Third Tier)
Dell Printer Management Pack Microsoft System Center Operations Manager (SCOM) and System Center Essentials (SCE) (Flo's Datacenter Report)
Using Cloud and Virtualization to Deliver Next-Generation Workloads (Data Center Knowledge)
Wireless Changes in Windows 8.1 and Server 2012 R2 (WindowsNetworking.com)
IPv6 is like global warming (Howfunky)
MANTIS Cyber-Intelligence Management Framework (WindowSecurity.com)
Open DNS Resolver Check Website Released (Infosec Island)
Important Changes To The Forefront Product Line (Jorge's Quest for Knowledge)
Benefits of Deploying Windows Server 2012 R2 Core Installation (CanITPro)
Cluster-in-a-Box Platform Earns Certification for Windows Server 2012 R2 (DataOn)
How to Run ChkDsk and Defrag on Cluster Shared Volumes in Windows Server 2012 R2 (Failover Clustering and Network Load Balancing Team Blog)
An argument for the single cloud vendor approach
The golden IT rule has always been avoid putting your eggs in one vendor basket – but is the cloud changing this commonly held belief? Read on to hear the case for single-vendor private cloud deployment.
Vendor options for VDI deployment -- sans Microsoft
Even for the Windows-based IT shop, there are a variety of options when it comes VDI deployment that lack the Microsoft label. Explore today’s VDI vendor landscape and some lesser-known Microsoft alternatives for desktop virtualization.
Is there a magic number: Finding the best server consolidation ratio
It’s essential to understand server consolidation isn’t a single static number – but every business must establish realistic consolidation goals that meet the unique needs of their IT environment. Gain advice from our experts on how to determine your best-fit server consolidation ratio.
No need to reinvent the wheel with Windows desktop manager commands
Desktop admins typically rely on advanced management tools from product lines such as Microsoft’s System Center, but there are a variety of functions that can be performed without having to invest in expensive management software. Read on to uncover them today.
This Week's Links We Like. Tips, Hints And Fun Stuff
GOT FUN VIDEOS or other fun links to suggest you'd like to recommend? Email us at [email protected]
Reader Mark Thorndyke sent us this link to the Amazing T-Rex Illusion:
Wow, thanks! GOT FUN VIDEOS or other fun links to suggest you'd like to recommend? Email us at [email protected]
Amazon Prime Air - unmanned aerial vehicle delivers your package in 30 minutes or less.
Landrover enthusiasts from Norway show that they can do better than Volvo and Jean-Claude Van Damme.
9-year-old Amira Willighagen gave a stunning rendition of the opera classic 'Nessun Dorma' and became the well deserved final winner of Holland's Got Talent 2013.
David Thibault became an overnight YouTube sensation with his cover of 'Blue Christmas' by Elvis Presley. Now Ellen invited him to perform on her show ...
WServerNews - Editors
Mitch Tulloch is Senior Editor of WServerNews and is a widely recognized expert on Windows administration, deployment and virtualization. Mitch was lead author of the bestselling Windows 7 Resource Kit from Microsoft Press and has published hundreds of articles for IT pros. Mitch is also a seven-time recipient of Microsoft's Most Valuable Professional (MVP) award for his outstanding contributions in support of the global IT pro community. Mitch owns and runs an information technology content development business based in Winnipeg, Canada. For more information see www.mtit.com