Search results matching tags 'Exchange' and 'Windows Server 2003'

SBS 2003 to SBS 2008 migration thoughts and issues

doverton — Mon, 19 Jan 2009 21:03:00 GMT

I've been part of a lively debate on the Yahoo UK SBS Group about how to migrate from SBS 2003 to SBS 2008 and what the issues are. The information I have so far is good, but I need much more to take it to the product teams.

For sure, the issues so far are:

Concerns around the "state" of AD before a migration is started - how do you check it - look at this blog post
Concerns around the Exchange migration in terms of time taken and failure scenarios - how to remove the chances of this?
Concerns around "on-site" versus "off-site" strategies
Concerns around recovery options in the event of failures (restore from backup not being ideal if you want it diagnosed)

My problem is that I have no data to take to the Microsoft product teams, which means I can't ask them to fix things so this is a two fold open invitation.

If you have had an issue, share it via comments below, but also PLEASE e-mail (doverton@microsoft.com) as well so I can get in touch with you and potentially the product teams too. If you put your mail in the blog then others can see it. You are also welcome to just e-mail me, but then there will not be discussion in public, which might be a shame.
Share other concerns so I can get them documented and addressed, but also use the Microsoft support - you can always send me the SR numbers if you want me to tie them together.

That is it - may the knowledge sharing continue!

David

Technorati Tags: SBS 2003,SBS 2008,migration,Microsoft,Small Business Server,SBSC,Community,Partners

Adding Exchange 2007 to an SBS 2003 / Exchange 2003 network

doverton — Tue, 04 Sep 2007 22:44:13 GMT

This question has come up lots of times and the general statement is that it is not trivial. In fact the normal question is can Exchange 2007 be run on an SBS 2003 box. The answer to this is a resounding NO. Exchange 2007 is 64-bit and SBS 2003 is 32-bit and never the twain shall meet. The closest you can get is installing a Windows Server 2003 64-bit system and putting Exchange on it. You will have to buy a Windows Server license, Exchange 2007 license and CALs for each client that uses it. (note if you want Outlook Voice Access then you need Enterprise CALs even if you are only installing Exchange 2007 Standard edition).

Once this is done you need to decide if you are going to keep your Exchange 2003 box or forward ports to the new system. If you are keeping both then you also need to be aware of (note this comes from an e-mail from Karan in our support team and should not be considered complete, but a pointer in the right direction):

Please note that Exchange 2007 would appear in a different administrative group on 2003 snap in and they will not be able to completely manage 2007 from 2003 and vice versa. ESM and EMC are very different to each other and do not allow to perform all administrative task like LCR etc. I would like to use EMC to manage 2003 and switch back to ESM as and when required.
The recommendations are:
You must use the administrative tools that are specific to the Exchange server version that you are managing.
· You manage Exchange 2007 server roles and mailbox recipients by using the Exchange Management Console or the Exchange Management Shell in Exchange 2007.
· You manage Exchange 2000 and Exchange 2003 servers by using Exchange System Manager.
· If you are using any features from Exchange 2000 that are not supported in Exchange 2003 or Exchange 2007, you must use Exchange 2000 System Manager to manage those features.
· You can manage Exchange 2000 and Exchange 2003 recipients by using a management computer on which the administrative tools for both Active Directory and the Exchange 2003 are installed.
Mailboxes that are located on Exchange 2000 and Exchange 2003 servers are also displayed in the Exchange Management Console in Exchange 2007.
· You can manage the Exchange 2000 and Exchange 2003 mailbox properties by using the Exchange Management Console in Exchange 2007.
· To move mailbox recipients from Exchange 2000 and Exchange 2003 to Exchange 2007, you must use the Move-Mailbox cmdlet in the Exchange Management Shell
Link: Http://technet.microsoft.com/en-us/library/aa998604.aspx
Additional:
http://blogs.msdn.com/mstehle/archive/2006/10/09/FYI_3A00_-Exchange-Team-Blog_3A00_-Exchange-2007_2F00_2003-System-Management-Coexistance_2E002E002E00_.aspx

Also, I have not done this yet (I'm purely running SBS Cougar on my test system).

ttfn

David

Technorati Tags: Exchange 2007, SBS 2003 R2, SBS 2003

May security updates for Server DNS and Office 2003/2007 and IE7. Also Quicktime needs an update

doverton — Tue, 08 May 2007 20:16:00 GMT

I did a quick scan and it seems that this month Office is the main target of updates, along with one critical one for Windows Server (for DNS RPC attack) and one for IE7. Worth a quick download and install :-)

I also got this in the mail today: Apple QuickTime 7.x must be upgraded to 7.1.5 or higher.

On the security updates:

Microsoft is releasing the following new security bulletins for newly discovered vulnerabilities:

Bulletin Number Maximum Severity Affected Products Impact

MS07-023 Critical Microsoft Excel (all currently supported versions) Remote Code Execution

MS07-024 Critical Microsoft Word 2000, 2002, 2003, 2004 (Mac) Remote Code Execution

MS07-025 Critical Microsoft Office (all currently supported versions) Remote Code Execution

MS07-026 Critical Microsoft Exchange (all current versions) Remote Code Execution

MS07-027 Critical Internet Explorer - all current versions on all currently supported versions of Microsoft Windows Remote Code Execution

MS07-028 Critical CAPICOM, BizTalk Server Remote Code Execution

MS07-029 Critical Windows 2000 (server), Windows Server 2003 Remote Code Execution
Summaries for these new security bulletins may be found at the following pages: http://www.microsoft.com/technet/security/bulletin/ms07-May.mspx Customers are advised to review the information in the bulletins, test and deploy the updates immediately in their environments, if applicable.

Microsoft Windows Malicious Software Removal ToolMicrosoft is releasing an updated version of the Microsoft Windows Malicious Software Removal Tool on Windows Server Update Services (WSUS), Windows Update (WU) and the Download Center. Note that this tool will NOT be distributed using Software Update Services (SUS). Information on the Microsoft Windows Malicious Software Removal Tool can be located here: http://go.microsoft.com/fwlink/?LinkId=40573 High-Priority Non-Security Updates on Microsoft Update (MU), Windows Update (WU), Windows Server Update Services (WSUS) and Software Update Services (SUS)Microsoft is also releasing High-Priority NON-SECURITY updates today on WU, MU, SUS and WSUS. For complete details on non-security updates being released today please review the following KB Article: http://support.microsoft.com/?id=894199 TechNet Webcast:

Title: Information about Microsoft May Security Bulletins (Level 200)

When: Wednesday, 9 May 2007 11:00 AM (GMT-08:00) Pacific Time (US & Canada)

URL: http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032327015

Replay: http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032327015

ttfn

David

Technorati tags: Security, Office 2007, Office 2003, IE7, SBS 2003

Its a sad day, but Vlad no longer runs his business on SBS - well, maybe not sad as he still runs lots of SBS businesses and he has grown beyond his SBS server

doverton — Sat, 13 Jan 2007 12:13:42 GMT

They said it could happen, but no-one believed them. Could and would people out-grow SBS? Well the answer is yes, people do - we see sales of the transition pack going through the system so we know it happens :-)

Did Vlad use the transition pack - it sounds unlikely as he has lost his wizards, which you do get to keep (but no guarantees about the scalability of them). For more information on the Transition Pack (which saves you money moving to non-SBS editions) have a look here. For Vlads post on leaving the SBS fraternity, go here.

Whilst we are on the subject, congratulations to Vlad for getting his 2nd MVP award too. Well done - perhaps this was an indication that you were always going to outgrown SBS :-)

For other information on the Transition Pack, have a look at http://search.live.com/results.aspx?q=sbs+transition+pack

ttfn

David

Need a machine to practice or simulate Windows Server, Exchange 2007, SQL 2005 or ISA 2006? Download the pre-configured VHDs for these virtual machines

doverton — Sun, 19 Nov 2006 21:55:20 GMT

I am sure you have seen these already, but if not, these are great tools to help when you quickly need a machine to test something on, or spend longer learning about a product. I know you can get the disks in the action pack, but then you have to load it up on a PC or VPC - this saves you all the trouble.

Windows Server 2003 R2
Windows Server 2003 R2 helps to simplify branch server management, can improve identity and access management, helps to reduce storage management costs, provides a rich Web platform, and offers cost-effective server virtualization. In this VHD, you'll have the opportunity to road-test new and improved features and functionality of Windows Server 2003, including management and usability enhancements to Active Directory.

Exchange Server 2007
Learn how to take advantage of key features of Exchange Server 2007. This VHD provides an exploration of Active Directory and the new features in Exchange Server 2007, new features in Outlook Web Access 2007, enforcing compliance and retention policies in Exchange Server 2007, and more.

SQL Server 2005
SQL Server 2005 is data management and analysis software that helps deliver increased scalability, availability, and security to enterprise data and analytical applications while helping to make them easier to create, deploy, and manage. In this VHD, you will get to experience many of the new features in SQL Server 2005.
ISA Server 2006 VHD
This download comes as a pre-configured VHD. ISA Server 2006 is the integrated edge security gateway that helps protect your IT environment from Internet-based threats while providing users with fast and secure remote access to applications and data.
For a complete list of Microsoft products and technologies in a VHD, visit the VHD Download Center.

Source: Run IT on a Virtual Hard Disk

iQubed on Vista vs Linux - and not from Microsoft, but a partner who has sold both Microsoft and Linux Solutions

doverton — Mon, 16 Oct 2006 14:16:03 GMT

I like Vijay - he never lets me get away with cutting corners and has an honest perspective on many things. His personal review of what Exchange, Vista and Office will bring to the world is refreshing because he can say he has been there!!

Vista vs Linux
October 13, 2006 on 6:51 pm | In Linux, Vista |
As Vista nears the business launch date of November 2006 the articles doing a comparison are appearing thick and fast. Firstly, let me say I’m an advocate of Open Source and what it has brought to the world. It’s given us some great solutions and powers the heart of the internet as we know it and companies like Google have built their business on it. That’s not a bad achievement!
However, Microsoft has a formidable offering to both consumers and businesses alike. This offering is only getting stronger through EVO (Exchange Server 2007, Vista and Office 2007) and issues such as the WGA debacle and delays in Vista aren’t going to make the impact of these new technologies any less dramatic.

Source: iQubed Blog » Vista vs Linux

Compatibility Chart for Windows Small Business Server 2003 (Product, Server applications and desktop)

doverton — Fri, 29 Sep 2006 21:54:59 GMT

A great new set of pages that shows what works and does not work with SBS 2003. using a simple traffic light system

= The product is an integrated component of Windows SBS, or it is known to be compatible with Windows SBS. The product was tested and you can obtain support for this configuration.

= The product has not been fully tested on Windows SBS and support for this configuration is not available from the Windows SBS product support team. Other groups may offer support for this configuration; contact the appropriate group for information. Some product features may not be fully functional in a Windows SBS environment.

= Not compatible. The product is known not to work and you should not install the product in a Windows SBS environment.

Product Technologies Compatibility Chart for Windows Small Business Server 2003

An at-a-glance compatibility chart for installing and running standalone versions of SBS 2003 technology on a server running Windows Small Business Server 2003.

Server Application Compatibility Chart for Windows Small Business Server 2003

An at-a-glance compatibility chart for installing and running Microsoft collaboration and line-of-business applications on your SBS 2003 server.

Desktop Technology Compatibility Chart for Windows Small Business Server 2003

An at-a-glance compatibility chart for installing and running Microsoft desktop technology on your SBS 2003 network.

ttfn

David

Transition Pack for Windows SBS 2003 R2

doverton — Mon, 18 Sep 2006 15:45:00 GMT

Very small and simple documentation on how to move from SBS 2003 R2 to Windows Server Standard 2003 R2, Exchange 2003 SP2 etc. These documents cover Standard and Premium editions.

Download details: Transition Pack for Windows SBS 2003 R2

ttfn

David

How patching should be done for all servers and clients - by Susan Bradley (super Jedi)

doverton — Mon, 18 Sep 2006 10:07:54 GMT

I still fear Susan and what she would do if I ever made a serious security blunder. Luckily for me, I haven't yet. I also love the way she tells you the way it should be and makes it easy.

I went through the process of evaluating my patches and then installing those I thought were needed (I do have some Office components on my test server, but I am hoping she will let me off for that).

I was thinking on how to write this up when I say Susan's entry The risk evaluation of patching and saw she put it exactly how I would have done.

What is my message - use her process and your customers will be as safe as can be expected. In fact, I applied the IMF patch immediately, which resulted in Exchange being offline for a few minutes, which when using Outlook 2003 or 2007 is no biggie at all.

ttfn

David

UK Partner Technical Specialists... Who are they, who were they?

doverton — Wed, 06 Sep 2006 04:50:00 GMT

So I WAS a PTS and now there is a different team, but Susanne has blogged on it, so go read her blog on who they are now and learn what I used to do :-) I am obviously above being part of that elite group, but I am still here for the community. They do cover a wide range of technologies and solutions from Microsoft, so they are a great place to get information, visit blogs and see what is what.

If the PTS do not cover the technology you want, then as a member of SBSC you get access to managed newsgroups (which means you get prompt answers from MS people and the community).

Now, the photo on the left is a bit old, but we were having a nice time out on the town - so much so that we had a drink or two - and I studiously took the photo, so I am not in it. My head was so muddled that when they found Keira Knightley in the bar, they got her autograph on someone's hand and rather than going downstairs with a camera and taking a snap, I snapped the autographed hand!!

ttfn

David

Bulletin Number	Maximum Severity	Affected Products	Impact
MS07-023	Critical	Microsoft Excel (all currently supported versions)	Remote Code Execution
MS07-024	Critical	Microsoft Word 2000, 2002, 2003, 2004 (Mac)	Remote Code Execution
MS07-025	Critical	Microsoft Office (all currently supported versions)	Remote Code Execution
MS07-026	Critical	Microsoft Exchange (all current versions)	Remote Code Execution
MS07-027	Critical	Internet Explorer - all current versions on all currently supported versions of Microsoft Windows	Remote Code Execution
MS07-028	Critical	CAPICOM, BizTalk Server	Remote Code Execution
MS07-029	Critical	Windows 2000 (server), Windows Server 2003	Remote Code Execution