Looking to upgrade your infrastructure to Exchange 2010, then Microsoft has a tool to help make the process a little smoother. They’ve published an updated version of their Exchange 2010 Deployment Assistant, which now supports migration paths from Exchange 2007 as well as help with new 2010 installs. Previously, the assistant would only advise users of Exchange 2003.
The Deployment Assistant allows administrators to create Exchange 2010 deployment instructions that are customized to their environment. The Deployment Assistant asks a small set of questions, and based on your answers, it provides a set of instructions that are designed to get you up and running on Exchange 2010. Instead of reading dozens of topics in the Exchange 2010 library, you simply answer a few questions, and the Deployment Assistant gives you customized content to install Exchange 2010.
The assistant is strictly web based, and does not require you to run anything on your systems. It does require you to have intimate knowledge of your Exchange environment for the results to be very helpful. You can find it over at Technet.
Just a reminder, Windows 2000 will reach it’s end of life in July. Microsoft has outlined July 13, 2010 as the date Windows 2000 will no longer be supported by Microsoft. There are already a variety of security threats in the wild where Microsoft has said they will not be releasing updates to protect Windows 2000 because they say it is not feasible. After next July, no support or new updates (except for online self-help) will be available.
In a related bit of news, Microsoft is addressing an issue latest Forefront antimalware client update won’t install on Windows 2000 when the installation is run via Automatic Updates. When this issue occurs, the update uninstalls the previous version of the antimalware client, and then tries to install the new version and fails, leaving the system without the antimalware service. Microsoft’s published workarounds are to decline the updates for Windows 2000 systems (976669 is the FCS slipstream client) and make sure that the previous FCS antimalware updates are approved (971026 and original FCS client), or run the install interactively as a logged on user.
My workaround… stop using a 11 year old operating system and upgrade to at least Windows 2003.
If the pending purchase of Sun (owner of MySQL) by Oracle scares you, and you’re looking to get your data out of MySQL before it gets eaten up by that other evil empire, then Microsoft has a tool for you.
They’ve released a test version of their new migration assistant to help database administrators make the change over. There is a version for both SQL 2005 and for SQL 2008 or SQL Azure. The tool provides an assessment of migration efforts as well as automates schema and data migration from MySQL to SQL Server. The tool will migrate any MySQL 4.1, 5.0 or 5.1 database.
Microsoft makes other migration assistants available for Oracle, Access, and a variety of other database formats, so this new tool is not unprecedented. It is however the first time it has made tools for the open-source MySQL available.
There are many less than glamorous roles that a Windows server can take on. Not all of them are born to be an Exchange server, a domain controller, or even a web server. Some are destined to take on the role of managing printers. And for every role in Windows server, there is a team of programmers and engineers behind it, and they need your help.
If use the Print Server role in your environment, Microsoft is looking for your feedback, especially if you’re using the print server management packs for System Center Operations Manager 2007. Your input will help form the future manageability plans for the print server role in Windows Server. If you deal with printers like I do, you probably know how frustrating they can be so you’ve probably got a lot of feedback to give. (Although truthfully none of my issues are really Microsoft’s fault — I’m looking at you Xerox)
Head over to the OpsMgr public site on Microsoft Connect and fill out the “Print Server Management Survey” You’ll need to login to Connect using your Windows Live ID but Microsoft claims the survey is anonymous and should take about 5 minutes to fill out the 11 questions.
Microsoft has posted a little bit of light reading, a document titled Changes in Functionality in Windows Server 2008 R2 that outlines exactly that, the differences between the R2 release and the original 2008 release. It only weighs in at 1.1MB and 211 pages. You can grab it from the Microsoft Download Center in Microsoft Word format or browse the document online through Technet.
Topics such as new features in Active Directory, DNS (including DNSSEC), Group Policy, iSCSI, IIS, clustering, Windows Deployment Server and many other elements are all covered in great detail. If you’re looking at a server wondering if you’d see any significant benefit to upgrading, other then getting the latest guts of Windows, this is a helpful guide.
Windows Server 2008 was released in February 2008, followed by R2 which was released in October 2009. R2 is Microsoft’s first 64-bit only operating system release and is based on many of the same core programming as Windows 7.
Looking to upgrade your infrastructure to Exchange 2010, then Microsoft has a tool to help make the process a little smoother. They’ve published an updated version of their Exchange 2010 Deployment Assistant, which now supports migration paths from Exchange 2007 as well as help with new 2010 installs. Previously, the assistant would only advise users of Exchange 2003.
