Skip to main content

Windows Server 2003 Code Name "R2"

February 03, 2005

Published: February 11, 2005

Please note:Portions of this transcript have been edited for clarity

Introduction

Anne_MSFT (Moderator):
Welcome! We will be answering your questions related to Microsoft Windows Server 2003 Code Name “R2.” This is an executive chat so we'll be giving priority to the business level questions over the most technical ones.
Also, for those of you under NDA (beta testers), this chat is public, so do not post any confidential information (for example, stuff you heard at yesterday’s private chat).

Anne_MSFT (Moderator):
We are pleased to welcome our experts for today. I will have them introduce themselves now.

iain mcdonald [ms] (Expert):
Hi,
I am Iain McDonald - I’ve been with Microsoft for 13 years. Started in Australia answering the phones in product support - moved to the US in 1992 & was the original escalation engineer for Email products. Pretty soon after that I move to the msmail/Exchange dev team - worked on the last couple of versions of msmail (anyone ever use msmail 3.5? - that was me, another guy & I think a well trained golden retriever). I worked on the original version of Exchange Server & then was the project manager for Exchange 5.0 & 5.5. At the end of 1998 I moved to windows to be the project manager for win2000. I was then project director for winxp & win server 2003. I moved to the Server team ~18 months ago in this role I have program management & development of a couple of things - most notably Terminal Server reporting to me. in this role I own (along with a number of people) roadmap/direction of server & report to bob muglia. I like the jumper Mark is wearing

Mark Aggar [MS] (Expert):
Hi, I'm Mark Aggar and am the product planner for Windows Server Releases @ MS

Eric Kidd [MSFT] (Expert):
Hi everyone. My name is Eric Kidd and I'm a Director in Windows Server. I work for Iain as part of the Central Program Management Team and am leading the R2 release.

Wendy [R2 Beta Team] (Expert):
Hi, my name is Wendy and I'm the R2 Beta PM

Eduardo_MS (Expert):
Hi, I'm Eduardo Melo, program manager responsible for R2 Setup.

Anne_MSFT (Moderator):
Let’s begin the chat!

Start of Chat

Mark Aggar [MS] (Expert):
Q:
will you be including network access protection in R2?
A: NAP will be delivered as part of Longhorn Server.

Mark Aggar [MS] (Expert):
Q:
1. When will we see MSH? Do we really have to wait another 2 years (for longhorn)??
A: MSH is not going to be included in R2

Eduardo_MS (Expert):
Q:
Eduardo: will there be a slipsream DVD option for R2 - 2 CDs sounds like NT4 Setup....
A: Current plan is that R2 will only ship in CDs. But we will provide the ability to chain the CD1 setup and CD2 setup.

Eduardo_MS (Expert):
Q:
Will R2 include WMI support?
A: Yes, although there is no change to the WMI core infrastructure in R2. Some R2 components will add new WMI providers

Eric Kidd [MSFT] (Expert):
Q:
There has been no mention of whether Small Business Server 2003 will get a "refresh" when R2 ships. Can you comment on this? Are any of the R2 technologies going to make it in to SBS?
A: The Small Business Server team is presently considering plans for an update release (i.e., an "R2" release). More information will be published as it becomes available.

iain mcdonald [ms] (Expert):
Q:
Will .NET Passport Smartcard logon be included in R2 wave ?
A: no - changes of that level go against the prime directive of R2 - don't change the core of the system. a change to winlogon would do that.

Mark Aggar [MS] (Expert):
Q:
next release coming soon? The beta1 is really buggy about everywhere
A: Our next beta is currently targetted for Q2 of this year

Anne_MSFT (Moderator):
Q:
Why this chat open for public ??
A: We have a variety of chats to support several purposes. The private chats let beta testers ask questions under NDA, but public ones (like this one) address more general questions from non-beta testers.

Eduardo_MS (Expert):
Q:
Eduardo: then please provide a method, tha tis supported, to enable us to do what you won't (cut to 1 dvd)
A: You can copy the R2 bits (CD1 and CD2) to a DVD and follow the unattended setup instructions. Have you seen them on the NGs?

Mark Aggar [MS] (Expert):
Q:
Is there any plans to allow consolidation of servers without using Virtual Server software ? I'm willing to physicaly merge several current servers but still be able to see them as two separate servers in network ..
A: Not in R2.

Eduardo_MS (Expert):
Q:
Are there any changes/bugfixes in IIS6 planned for R2?
A: No, we are not changing IIS in R2

iain mcdonald [ms] (Expert):
Q:
2. Will WUS be built into R2. and if not, why not!
A: We looked at that &, frankly, the team is so slammed getting the next version up that it would have been silly for us to slow the release down by putting it in R2. It was a basic project management type decision.

iain mcdonald [ms] (Expert):
Q:
Oops, wrong Q, wil R2 contain MSI support.
A: All the features msi enabled, but an update to core msi is not happening - goes against the 'prime directive' idea...

Eric Kidd [MSFT] (Expert):
Q:
Can you explain what has changed in FRS ... is it still whole-file or partial, how often can we push changes, any additional value-prop for branch offices ?
A: One of the great features we're planning to deliver as part of R2's new replication service is use of Microsoft's Remote Differential Compression technology. This will vastly improve replication performance by sending across the wire only the changes in the file, rather than the entire file. We're also planning a new admin console for both DFS and replication which has some great new features and enhancements.

Mark Aggar [MS] (Expert):
Q:
With SP1 and R2 coming relatively close together, why would I want to deploy SP1, versus waiting and deploying R2?
A: Because R2 is built on SP1 (its a pre-requisite) its well worth the time to test WS03 boxes for compatability with SP1 ahead of deploying the additional functionality provided by R2. You'll also get additional time to evaluate security capabilities such as Security Configuration Wizard provided in SP1.

Eduardo_MS (Expert):
Q:
Eduardo: I've got a quick question before I decide when I'm going to actually upgrade to the R2 beta. I realize that if I upgrade to Beta1, it won't upgrade to Beta2. But, when the beta is finished, will I be able to manually upgrade to the RTM version?
A: Beta 1 to Beta 2 upgrade is not supported but we plan to support Beta 2 to RC0 and RC0 to RTM upgrades

Mark Aggar [MS] (Expert):
Q:
What is the current estimated RTM for R2?
A: We are still on track for 2nd half of 2005.

Mark Aggar [MS] (Expert):
Q:
Unfortunately, without meeting driver parity with the 32-bit release, such quick transition will not be possible.
A: Agreed. R2 is based on the SP1 codebase so the 32-bit version of R2 supports the same set of drivers.

iain mcdonald [ms] (Expert):
Q:
If the "prime directive" of R2 is not to change the core system, why not ship R2 as just downloadable bits (download.microsoft.com) for everybody, subject to them having updated their Windows Server 2003 systems to SP1 (or whatever the prerequisites r)
A: 1) R2 will require sp1. frankly, most people i talk to don't really believe the stuff up as downloads are real & question the amount we support them. having them in the box legitimises them far more.

Eduardo_MS (Expert):
Q:
eduardo: will PSS support this?
A: Not sure but let me follow up with them.

Eric Kidd [MSFT] (Expert):
Q:
What are the cases when you would recommend upgrade WS2003 -> R2?
A: This R2 release will integrate the great work done in WS2003 SP1 with selected new features/components (introduced in R2) and a small number of previously released feature packs rolled-in. Because R2 is based on WS2003+SP1, a WS2003 customer would upgrade only those servers on which they want to run new R2 features. Since we plan that R2 will be serviced with the same service packs and patches as WS2003, it makes mixing WS2003 systems and R2 systems in a single environment very easy.

iain mcdonald [ms] (Expert):
Q:
Do you have a list of H/W vendors participating in NAP testing right now?
A: nap really is outside of what we're talking about today - unfortunately right now we can't say. but the list is pretty obvious...

Eduardo_MS (Expert):
Q:
If Small Business Server consultants want to make their views known to MS on a potential R2 version of SBS, who should we contact? :-)
A: I'll get a contact for you

Eduardo_MS (Expert):
Q:
Will any improvement comming in the RDP/Terminal Server field ?
A: No in R2. TS improvements are being made in LH

iain mcdonald [ms] (Expert):
Q:
Beta testing has shown that a majority of the 32-bit drivers shipped in W2K3ES is no longer available in the 64-bit counterpart. Deployment and certification of production systems had been done in preparation for rapid migration as soon as it ships.
A: you'll see a big wave of driver updates for server in sp1. i don't expect the drivers to be 100% the same - it depends on ihvs business palns. persoanally i think they'd be crazy not to be looking at the coming x64 wave as a good new business pop for them

iain mcdonald [ms] (Expert):
Q:
Any estimates as to R2 pricing as of yet?
A: we really don't talk about pricing at this stage of a project. i wanted to joke, but it'd be on all the noise sites in 3 minutes...

Mark Aggar [MS] (Expert):
Q:
Will 64 bits release(s) eventually supersede all others and be focus for future OS's
A: 64-bit hardware will be the default for new server hardware very soon (its pretty much happened already). However, many apps (and drivers) will continue to be 32-bit for some time, so it will be a while before a complete transition is made. The good news is that many 32-bit apps will work on WS03 x64 without performance penalty - the biggest issue is having 64-bit drivers available. The WS03 x64 editions will kick start the IHV/ISV industry into making 64-bit server apps and drivers. I believe that when we ship LHS that the majority of new server applications will support 64-bit OS natively.

iain mcdonald [ms] (Expert):
Q:
What is the pricing stucture going to look like for R2 or is it included in SP1?
A: (see my previous comments on r2 pricing) service packs are free - i believe they always should be. r2 is a feature update for server & will have some cost associated with it.

Eric Kidd [MSFT] (Expert):
Q:
If the "prime directive" of R2 is not to change the core system, why not ship R2 as just downloadable bits (download.microsoft.com) for everybody, subject to them having updated their Windows Server 2003 systems to SP1 (or whatever the prerequisites r)
A: R2 contains many new features which represent significant value to our customers - some of them are features which would not otherwise be offered as free downloads to existing WS2003 customers. By incorporating these features into an OS release (such as R2), we're able to deliver tighter integration across the features and ensure a cohesive end-to-end experience for our users. We're also planning to service the new bits of R2 along with the original bits of WS2003, which means all future WS2003 service packs and patches can be applied to both WS2003 systems and WS2003 "R2" systems. This will be a great convenience for existing WS2003 customers.

Mark Aggar [MS] (Expert):
Q:
Will there be any sort of option for current Win Server 2k3 users to purchase the R2 enhancements seperate from the full OS, so as not to have to buy another copy of Win Server 2k3 exclusively for the added r2 features?
A: Customers who have their servers covered by Software Assurance or Enterprise Agreement will receive R2 as part of their benefits. There are no plans to make an "upgrade" available (just as there isn't an upgrade from Win2k Srv -> WS03)

Eduardo_MS (Expert):
Q:
Will you release a W2k3 R2 DVD?
A: No, R2 will ship as 2 CDs.

Mark Aggar [MS] (Expert):
Q:
Can you clarify for everyone the licensing requirements for an organization to upgrade to R2? Will the CALs need to be upgraded, etc.?
A: Please see my earlier response on this. There is no new CAL requirement (WS03 CALs are required to connect to an R2 box)

Eduardo_MS (Expert):
Q:
Are there any plans to include the .NET framework in any of the CD/DVD OS / SP releases before LH? And if you know a good reason not to, I'd rather hear some than just none.
A: R2 will ship with the new version of the framework

Eric Kidd [MSFT] (Expert):
Q:
Forgive me, perhaps I'm misunderstanding about the difference between just installing SP1 vs installing R2. As far as I can see R2 is basically just 2003 plus SP1 plus the extra stuff that one could download today. Is that incorrect? Thanks.
A: That's not quite right. WS2003 R2 has incorporated into the release a small number of feature packs (which have been released as web downloads for WS2003 customers) for purposes of improving integration and ease of consumption. While you're right that we're integrating the great work of SP1 with R2, most of the work going into "R2" is development of significant new features being released for the first time in "R2".

Eduardo_MS (Expert):
Q:
Will the R2 bits be installable on a vanilla Windows Server 2003 system once it's upgraded to SP1? In other words, will WS2003 + SP1 be essentially identical to R2's CD1 install?
A: You bet. You will be able to do this. The only thing to remember is that when you're running the CD2 setup, you will be prompted for a R2 product key. And unless you're using a Volume License key, you will need to activate the server after that

Eduardo_MS (Expert):
Q:
Is the new Event logging component going to be developed for other OSs e.g. WinXP? It would be easier to program to one Event logger and be able to take advantage of the new features.
A: This is coming in LH

Mark Aggar [MS] (Expert):
Q:
The issue is driver support for 64-bit < and != 32-bit in W2K3, therefore update-in-place for the production data centers will impose delays if driver availability is not secured.
A: To be clear there will be a 32-bit version and 64-bit version of R2. There is no requirement to migrate to 64-bit to get R2.

iain mcdonald [ms] (Expert):
Q:
Is the any way to get more API information exposed to control RRAS server ? I'm still unable to assign schedule to dial-in devices. They must be turned off during work hours, but accept dial-in connections during night ..
A: not really part of this talk, but check out http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rras/rras/router_administration_functions.asp

Eduardo_MS (Expert):
Q:
Will R2 require a second key for volume license customers or is it keyless?
A: It will require a R2 key. You can use the R2 VL key when installing the base OS (CD1) or later when running the CD2 Seutp. irrespective, you won't need to activate the box if you use VL keys

Eduardo_MS (Expert):
Q:
Will there be MOM 2005 feature packs for the new features of R2 ?
A: Yes. We're still working on that but there will be mom packs for the r2 components

Eric Kidd [MSFT] (Expert):
Q:
Why you requere us to use different CD media for Web / Standart / Enterprise server editions ? Why this is impossible to use a single CD ?
A: The simple answer is that each edition contains different bits/files which are unique to that edition. While many of the files on the media are the same across editions, there are differences which make each edition distinct.

iain mcdonald [ms] (Expert):
Q:
(Iaian McDonald). Many MS products have had free feature packs. MS could ship R2 as a feature pack for WS2003, but I can see why Marketing might not approve. Can we install R2 bits on a vanilla WS2003 system once it's upgraded to SP1?
A: i've found there is pretty wide mistrust of feature packs & they are nto seen as legitimate - especially when the support is questionable - we wanted to get away from that idea. i

Eduardo_MS (Expert):
Q:
(Eduardo_MS) You're saying the R2 bits need activation, or that installing any or all the R2 bits will trigger a REactivation of the base WS2003 OS?
A: There are two scenarios to consider. Clean install (use a R2 key to install CD1 and CD2). This will require a activation, just like you need to activate server 2003 RTM today. The second scenario is if you have a WS03 RTM or SP1 box (in this case you used a WS03 RTM key) that is already activated and then you install R2. When you install R2, you need to 're-key' the machine. And this will require a new activation

iain mcdonald [ms] (Expert):
Q:
Will Azman be soon used as on Access Control provider for the File System (other the basic ACL) ?
A: we will be doing this in a future release (wish we had it ready to do in a mainstream way now)

Eduardo_MS (Expert):
Q:
If you do a SBS2003 install, and "forget" to complete the install after CD1 (i.e. you get a vanilla WS2003 system), the OS is timebombed to get unhappy after a couple of weeks and starts restarting automatically to "remind" you to do the rest of setup.
A: That is correct. In R2, we will only remind you once that you need to complete setup.

iain mcdonald [ms] (Expert):
Q:
Can you please try to answer my questions?
A: yeah - there's only 3 of us & eric is a slow typist

iain mcdonald [ms] (Expert):
Q:
How R2 will be a next milestone in the DSI initiative ?l
A: it's not, longhorn is.

Eduardo_MS (Expert):
Q:
Is there a relation between R2 and Srv 2k3 SP2? Will R2 be needed for upgrading or must R2 installed before SP2 is applied (OK, this is far away, but...)
A: There is a relation in the sense that SP2 will service R2 boxes. As a matter of fact, SP2 will service 'vanilla' WS03 and R2 boxes, the same service pack.

iain mcdonald [ms] (Expert):
Q:
Will Azman be soon used as on Access Control provider for the File System (other the basic ACL) ?
A: in a future release, yep. i want it now as well...

Mark Aggar [MS] (Expert):
Q:
Mark Aggar: let's face it, right now, R2 looks like WS2003 SP1 with some extra bits on a second CD. Comparing a WS2003 -> R2 upgrade with a W2k -> WS2003 is a bit disigenious I think. How do we push our customers to upgrade to R2 while they wait 4 LH?
A: We are not expecting or pushing customers who are on WS03 to upgrade all of their servers to R2. There are a number of server roles that are prime candidates to upgrade to R2 (branch offices/web servers) if you're on WS03, but for the most part customers will run WS03 and WS03 R2 side by side. NT4/Win2k customers who are upgrading should look to R2 as their upgrade target.

Eduardo_MS (Expert):
Q:
Are you saying that valid R2 keys will actually work on a vanilla WS2003 CD1 (i.e. not R2 media), then you throw in R2's CD2 and you're all set? Or are you changing the keys for the base WS2003 CD1 once R2 ships?
A: You can use R2 keys with the WS03 SP1 CD. WS03 RTM CDs don't recognize R2 keys. The new R2 keys were only added in the SP1 timeframe

iain mcdonald [ms] (Expert):
Q:
Is a "better" telnet Client planned? example: with a ssh option.
A: looking at this, but frankly, there are some better ones out there already from other people.

Eduardo_MS (Expert):
Q:
Are there are plans to integrate the Windows Sharepoint Services directly into either Windows Server 2003 R2 or Longhorn Server?
A: Yes, Sharepoint is one of the R2 components. Among other options, we will have a 'one-click' setup for Sharepoint. You click a checkbox and you get sharepoint installed in a default configuration (which uses WMSDE).

Mark Aggar [MS] (Expert):
Q:
Iis activation required for volume license customers?
A: This will be the same as it is for WS03 customer today (so no if you have VL media/keys) - you will need a new R2 VL key though.

Anne_MSFT (Moderator):
Q:
Sorry, I have to leave early, when may we expect a transcript?
A: Transcript will be posted to http://www.microsoft.com/technet/community/chats/trans/default.mspx in a few days.

Eduardo_MS (Expert):
Q:
Is it planned to make all the R2 components deployable using GPOs/Windows Installer? Remote updating of server could be really neat if this all worked... :-) but I'm assuming it won't :-(
A: R2 components will support the same deployment options currently available for other windows optional components such as IIS. I may be wrong, but i don't think GPOs support deployment of windows optional components

Eduardo_MS (Expert):
Q:
Why isn't the Windows Firewall not turned on by default in Windows Serve R2?
A: The firewall settings are initiall configured by the SP1 installation. R2 won't interfere with that.

Eric Kidd [MSFT] (Expert):
Q:
Will you add new boot storage devices to CD ? Like a Silicon Image SATA/RAID controllers ?
A: In "R2," hardware support will be identical to what's included in WS2003+SP1.

Eduardo_MS (Expert):
Q:
Will there be a datacenter edition of R2?
A: Yes, it is planned

Mark Aggar [MS] (Expert):
Q:
One of the goals of R2 is to make the branch office servers act like cache servers (file and print). Will this caching concept eventually be extended to web caching as well?
A: I believe this is one of the features of ISA server.

Eduardo_MS (Expert):
Q:
Eduardo_MS: can you at least give the Longhorn server team a kick in the butt and suggest they look at Windows Installer technology for all future components of the OS? It would be really great to push things like that out through Group Policy rather..
A: It will be my pleasure to do this... :D Seriously, i know that the LH folks are making significant improvements to GPO and installation technologies.

iain mcdonald [ms] (Expert):
Q:
Bo/DFRS - Any plans to implement a way of finding the source (server) for documents?
A: i guess you mean which server a document was put on in the first place?

Eduardo_MS (Expert):
Q:
Will R2 be only for Enterprise Edition or will it work for Standard, SBS, Web Server, etc.?
A: Current plan is for R2 releases of Standard, Datacenter and Enterprise. The SBS team is investigating a R2 releases focuses on SORGs

Mark Aggar [MS] (Expert):
Q:
Will R2 be only for Enterprise Edition or will it work for Standard, SBS, Web Server, etc.?
A: Enterprise Edition is the only thing being released as part of the beta (as per usual with a server beta). There will be other editions of R2.

Eduardo_MS (Expert):
Add/Remove Components is how you install the new R2 components

iain mcdonald [ms] (Expert):
Q:
Can you information why Microsoft will release a separate version of 2003 for Cluster, Storage and so on?
A: ummm - i don't get the question really. we have a different edition for storage - that is really directed at being a great single use server. we have a thing called compute cluster edition coming but that's off topic from today. they are just different version directed at specific stuff

Eric Kidd [MSFT] (Expert):
Q:
Is R2 also an option for existing Win Storage Server or upcoming Data Protection Server?
A: I'm not quite sure what you mean when you ask if R2 is an "option" for these other releases. I think you're asking if there will be an "R2" release of these other products. So I'm clear in my answer: the release we're talking about here is Windows Server 2003 "R2." There are separate releases known commonly as "Windows Storage Server" and "Data Protection Server." While these other releases will include some of the new features of Windows Server 2003 "R2," they are separate products and timing is such that it wouldn't fit for us to release an "R2" version of those products in this timeframe.

Eduardo_MS (Expert):
Q:
given than Branch Office seems to be a Big Idea (TM) in R2, can you suggest to the SBS team that this would be very interesting to many SBS shops. A second server in the SBS network running R2 but at a remote location.
A: i'll pass the feedback to them.

iain mcdonald [ms] (Expert):
Q:
It will complicate the support and upgrade stages. MS did this in NT TS version and revert to normal method in Win2k
A: i don't get this one either. in retrospect the nt4 ts version was not well thought out. it was problematic to do upgrades & hard to deal with. i think we've done a much better job on this in the last 2 verisions.

iain mcdonald [ms] (Expert):
Q:
Will there be a solution for the problems using Exchange OWA and Sharepoint Services 2 on the same server ?
A: not in r2. sorry.

Wendy [R2 Beta Team] (Expert):
There will be feature-specific public chats scheduled where experts from each area will be available to answer detailed configuration and implementation questions. A copy of the schedule will be posted on BetaPlace and microsoft.com.

Eric Kidd [MSFT] (Expert):
Q:
Will pre-SP1 Exchange Server 2003 be supported in the next update of Windows Server R2? I get an error when I try install, I get an incompatibility warning.
A: Since R2 is based on WS2003+SP1, it will have the same application compatibility as WS2003 with SP1 installed. Unfortunately, I can't very well comment on the specific error you're seeing.

iain mcdonald [ms] (Expert):
Q:
This may be out of scope, but then if having the features included in the SP itself is important as a sales tool and legitimizes the additional functionality as supported, then why the strong push to compartmentalize features and functionality, thereby...
A: yeah but every time we include features in an sp we get our heads nailed to the floor by customers telling us to not do that. i guess we can't please everyone...

Eduardo_MS (Expert):
Q:
Eduardo_MS: sorry, I've had a couple of glasses of wine with dinner tonight: what are SORGs ? ;-)
A: You don't know what SORG means?!?!?!? Just kidding. SORG stands for Small ORGanizations. My bad habit of using acronyms... :D

Eduardo_MS (Expert):
Q:Q:
Will R2 be detected by security scanners and the like as WS2003 or as a new product? How will e.g. WUS / SUS / hfnetchk / Shavlik and friends cope? Will R2 get identical patches? PLEASE don't ship R2-specific stuff that WS2003 needs too...
A: R2 boxes will look like WS03 boxes for WUS, SUS and etc.

Mark Aggar [MS] (Expert):
Q:
What are your top 3 new features/enhancements in R2, and why?
A: 1) Improved Branch Office Server management - (improved caching - saves bandwidth, removes need for backup in branches)
2) Streamlined Access Management across security boundaries (ADFS - improved TCO and security when collaborating with partners)
3) Storage Management Efficiencies (Simplified SAN management for IT generalists, improved quota management)
Plus it's built in the improved security, reliability & performance of SP1.

Eduardo_MS (Expert):
Q:
Will RIS (Remote Installation Services) be updated in anyway during future Window Server 2003 releases. It's lacking quite a few features and could do with an update?
A: it is not being updated in R2 but they're making changes in LH

Eduardo_MS (Expert):
Q:
Will all R2 components be patchable with WUS?
A: Yes

Eduardo_MS (Expert):
Q:
This may be out of scope, but then if having the features included in the SP itself is important as a sales tool and legitimizes the additional functionality as supported, then why the strong push to compartmentalize features and functionality, thereby...
A: Currently GPMC is not in R2 but we're analyzing the feasibility of adding it to the release.

Eduardo_MS (Expert):
Q:
Eduardo_MS: if R2 boxes look like WS2003 boxes, how will you detect patches for the R2 components when security flaws are discovered in them, as I guess they will be?
A: I don't know the technical details but WUS looks at more stuff than just the OS version to know what it needs to patch.

Mark Aggar [MS] (Expert):
Q:
Since the 64-bit driver issues has not been answered, why has not all (100%) hardware from the 32-bit release (retail) already on media been ported to x64 slated for RTM release in a few months? What is not already out-of-the-box creates too many problems.
A: We are working proactively with our IHV/OEM partners to provide as much in-box driver coverage as possible, but ultimately the partner needs to sign up to do the work *and* support it for the life of the product.

Eric Kidd [MSFT] (Expert):
Q:
(continued)... I hope there are no plans to do this with R2. So R2 buyers can install CD1 and "forget" CD2 if they like - is this right?
A: I can't see on my end the beginning of your question - only what's shown here. To answer this, I'll say generally that to complete OS setup, you must complete the CD2 portion of setup. Without CD2 setup, the box would not include the new R2 features and system changes and would not be in a supported state. Once setup is completed properly, our present is that CD2 would only be needed when installing one of R2's new optional components. Of course, if you installed from a share, rather than media, you wouldn't need CD2 media for optional component install.

Eduardo_MS (Expert):
Q:
When SBS2003 was in beta, there was a promise that WSS and Exchange OWA could be run off the default web site. Someone promised me a recipe at the time. It never appeared. Can you pass this on to the dev team for either SBS R2 or SBS200X?
A: i'll pass your feedback

iain mcdonald [ms] (Expert):
Q:
Is there any chance to be able to put Access Control on a file based on rules like (RO access for Mike when accessing the ressource from the LAN1 with a basic authentication and Full Control access for him from VPN with strong auth mecanism)?
A: great idea - i will pass it along

Anne_MSFT (Moderator):
Q:
thanks for nice chat
A: You bet! Thanks for coming!

Mark Aggar [MS] (Expert):
Q:
You mentioned Standard, DataCenter and Enterprise ... what is the current plan for Storage Server edition ?
A: An R2 version of Storage Server is planned to be made available to our OEMs at the same time we RTM R2.

Eduardo_MS (Expert):
Q:
Is it possible that GPMC will the default GPO editor in R2?
A: GPMC is not in R2 as of right now but we're analyzing the feasibility of adding it to our release

Eduardo_MS (Expert):
Q:
If R2 requires W2K3SP1+ as a requirement, and introduces new functionality equivilant to past feature-packs, why not just release it as W2K5 to keep it simple?
A: At this point, we won't yet have the official name for this release.

Mark Aggar [MS] (Expert):
Q:
About the web caching, ISA is not well adapted to branch office scenarios when only web caching is needed.
A: Understand your concern here. We are looking into ways to address this, but I can't be more specific.

Mark Aggar [MS] (Expert):
Q:
R2's feature set has changed over time; is there an up to date list of improvements of R2 over 2003 BESIDES the feature packs and SP1?
A: We plan to be more public about this in the near future. However beta customers can see for themselves.. :-)

Eduardo_MS (Expert):
Q:
Re: Support. Will there be support issues as R2 will be considered a separate version of Windows, creating a convenient excuse for IHV/ISVs on which to blame problems? Will there be patches, fixes that are R2 or SP1 specific and create problems?
A: To avoid this problem, we are making a very small number of changes to existing SP1 files. With this, patches that are applicable to SP1 boxes will also be applicable to R2 boxes. Future Service Packs (SP2, etc) will service SP1 and R2 boxes

Eduardo_MS (Expert):
Q:
So, will R2 be changing name before the final release?
A: We don't have a official name yet.

Eric Kidd [MSFT] (Expert):
Q:
Will there be a wizard for SFU/Interix installation ? and for NFS ? Problem with a NFS Server (SUN) that NFS creates a guest account with -27...
A: As with all R2 optional components, users will add them by going to Add/Remove Windows Components, selecting the component, and then following the string of interactive screens to complete component setup. While this isn't necessarily the "Wizard" experience some people might think of, it does give good assistance for successful setup.

Eduardo_MS (Expert):
Q:
... than through Add/Remove Components.
A: Yes, this is how you install the R2 components

Mark Aggar [MS] (Expert):
Q:
Any idea when the R2 releases will be made available to MSDN subscibers?
A: We are are currently targetting beta2, but no firm commitments yet

iain mcdonald [ms] (Expert):
Q:
(continued) wait for Longhorn Server, which according to roadmaps from years ago, we ought to be getting Real Soon Now (TM)
A: not sure what this is continued from. this is off topic. i will say i wish we'd hit the milestones we said - you can believe us more when you see the first beta of longhorn.

Eduardo_MS (Expert):
Q:
Could there be a fill out form based approach to setting up active directory instead of Wizard process? I think I pressed next about 13 times to setup.
A: This is good feedback but we're not making changes to dc promo in R2. i'll pass the feedback to the Active Directory team, anyhow

Eduardo_MS (Expert):
Q:
Sorry Eduardo, but what I meant is not what the new name is going to be, but simply is the name going to change from R2?
A: It might. It may not be officially called 'r2'

iain mcdonald [ms] (Expert):
Q:
Why isn't the CD Burning wizard feature not in Server 2003? I turned on the CD Burning IMAPI Service, but I'm not able to drag files and burn to CD-RW.
A: this is off topic from todays discussion. check out sp1.

Mark Aggar [MS] (Expert):
Q:
According to OS competitor offers, is Microsoft now considering offering a native iSCSI Target for Windows Server (at least for Storage Edition) ?
A: There are no published plans for an iSCSI target in Windows Server

Eduardo_MS (Expert):
Q:
Will the MMC 2.1 be backported to WinXP and Win2003 once .NET 2.0 is out? It seems a worthless to have all these great new R2 features if the snap-ins can only run from R2.
A: The MMC team is looking at down-level support. they haven't finalized their plans yet but they know very well that there is a huge business case to support down-level clients and remove management

Mark Aggar [MS] (Expert):
Q:
Have you a full cache AD Controller branch office. ?
A: Not in R2.

Eric Kidd [MSFT] (Expert):
Q:
Are they any changes to NTBACKUP? Like backing up sharepoint services in the system state?
A: There are no changes to NTBACKUP in "R2." It will be the same as it is in WS2003+SP1.

Eduardo_MS (Expert):
Q:
I'd like to suggest that Microsoft does not make the 2 CD setup process anything like MCE '05. They should make sure that each CD only needs to be put into the drive once for setup to be completed and not more than that:
A: I investigated the MCE05 design and we did a lot of hard work to ensure that you don't need to swap CDs back and forth. Once you start using CD2, you won't need CD1 anymore to complete setup

Eduardo_MS (Expert):
Q:
i.e insert CD1 and run setup, then insert CD2 and let that install and not have to put CD1 back in
A: This is precisely how it will work. :D

iain mcdonald [ms] (Expert):
Q:
Can you information why Microsoft will release a separate version of 2003 for Cluster, Storage and so on? It will complicate the support and upgrade stages. MS did this in NT TS version and revert to normal method in Win2k
A: i think i answered this. nt4 ts was an abberation - these versions are totally different things

iain mcdonald [ms] (Expert):
Q:
About iSCSI, do you figure out that Microsoft is also selling a Storage Edition of Windows ?
A: i don't ge tthe question. we do have released iscsi support

Anne_MSFT (Moderator):
Q:
Anne: Will the questions that they aren't able to get to be answered in the transcripts?
A: We may be able to answer some of the questions in the transcripts.

iain mcdonald [ms] (Expert):
Q:
Will R2 have better management pack support bundled in product
A: do you mean an update to the admin pack? no we don't - we have new snapins, but no update to the admin pack.

Eduardo_MS (Expert):
Q:
If R2 is going to be marketed as a complete OS (w/ W2k3 sp1), why is a seperate setup necessary? (that is, why not extend the setup over the 2 CDs, prompting the user for Disc 2 when needed, as opposed to having a seperate setup program for the OS and R2?
A: We tried to do this but it would require significant changes to the existing ws03 setup. The best trade-off we could get was what you see, the separate setup. The good thing is that there is support for unattended installs, so you can just fire off the setup script, go have a cup of coffee and when you come back, r2 will be completely installed.

Mark Aggar [MS] (Expert):
Q:
Does that mean that the drivers supplied on the 32-bit media are supplied from vendors and included in the retail package? What happens when SCSI or network device vendors exit the business, are the drivers not built from source?
A: I'm not an expert in this area. Drivers supplied by vendors are tested by Microsoft and normally we have the sources.

Anne_MSFT (Moderator):
Thank you for joining us today on a Microsoft Community Chat to talk about Microsoft Windows Server 2003 Code Name “R2.” If you would like further information on this topic, please visit http://www.microsoft.com/windowsserver. And please come back on Feb. 16 at 3p (Pacific) to chat with Bob Muglia about IT Generalists in the medium-business space!

[Questions answered after the chat finished]

Eduardo_MS (Expert):
Q:
ping -> Eduardo_MS: email me at james (at) reather (dot) com if you've got an SBS contact...
A: Privately sent him this info

Eduardo_MS (Expert):
Q:
Any thoughts of including the Microsoft Antispyware bits on the server with R2?
A: This feature won’t be included in R2

Eduardo_MS (Expert):
Q:
Any improvements to the naming of the SQL instance when Sharepointis installed if the machine name contains an underscore?
A: I don’t think the name of the SQL instance is changing in R2

Eduardo_MS (Expert):
Q:
Has any thought been given to having the setup automatically cache the setup files (i386, etc.) on the hard drive during setup so that updates and installs dont require the CDs? (similar to the Office 2k3 experience)
A: This capability exists today but requires that you specify a command-line argument, this is not going to change in the R2 timeframe

Eduardo_MS (Expert):
Q:
RE: MMC 2.1. I understand there are some issues to backporting to windows 2000. I think most people would be happy with WinXP and Win2003 (not R2).
A: The MMC team is investigating down-level support and WinXP and Win2003 are Pri1 platforms.

Eduardo_MS (Expert):
Q:
Will R2 support fully unattended deployment using SMS 2003 SP1?
A: Yes

Eduardo_MS (Expert):
Q:
Can MS add File Share over HTTP (like RPC over HTTP) in R2?
A: This feature is not planned for R2