Inside info on Windows 2003
Posted by Steven Parker on 09 February 2003 - 16:55 · 13 comments & 512 views
- Advertisement
-
-
#1 Posted by Jason on 09 Feb 2003 - 17:04
- CPP keys will no longer work for 3764 and up.
-
(2 replies)
#2 Posted by danbalsh on 09 Feb 2003 - 17:11
- Yes, it's all coming together nicly now.
But, this is my question:
What will the beta mokeys have to do now
-
#2.2 Posted by y_notm on 09 Feb 2003 - 18:25
- [neoquote=#2.0 by danbalsh]Yes, it's all coming together nicly now.
But, this is my question:
What will the beta mokeys have to do now
[/neoquote]
I expect Longhorn to really gear up after winserv2k3
plus XPSP2, MCE Update, Yukon, Office 11 beta 2, 2000 SP4.
Oh yes, its going to be an interesting summer
-
(1 reply)
#3 Posted by frazell on 09 Feb 2003 - 18:00
- Well if your hardpressed to use it as long as you can you can activate and use it for a year
, Given you dont format...
As when i installed my MSDN RC2 copy it stated its a 360Day License... -
#3.1 Posted by danbalsh on 09 Feb 2003 - 18:09
- [neoquote=#3.0 by frazell]Well if your hardpressed to use it as long as you can you can activate and use it for a year
, Given you dont format...
As when i installed my MSDN RC2 copy it stated its a 360Day License...[/neoquote]
Or if your like me, i've got 6 copies of RC2 lol and 6 keys non of em activated
-
(3 replies)
#4 Posted by neos on 09 Feb 2003 - 18:48
- [quote]The code that is RTM has to survive about 15 days of ESCROW before RTM.[/quote] What does ESCROW mean?
-
#4.1 Posted by Dessimat0r on 09 Feb 2003 - 19:53
- It means that it is given to loads of crows, and they are made to try and escape with the product.
-
#5 Posted by wI-OSMAN- on 09 Feb 2003 - 19:14
- well the beta monkeys will have to play with copys of windows longhorn.. which i'm running and very stable.
Submit to reddit
Submit to blinklist
Bookmark on del.icio.us
Add to furl
Share on Facebook
Add to Windows Live
ESCROW is final stage where Microsoft deploys the build on their own production servers
Windows Server 2003 Build 3757
This build was NOT meant to be published, but Microsoft Dev Team badly wanted to release a new feature for public testing - ”IE Hardening”
Basically, it’s a policy that you set for the server, and it makes Internet Explorer only reach sites listed in ”Trusted Sites”.
Windows Server 2003 Build 3760
Targeted for ESCROW, this was first targeted as ”the final RC build”. A few problems surfaced and id did not make it.
Windows Server 2003 Build 3763
New build targeted for ESCROW, to be ”final RC build” to go public. Build 3763 is the last one to have public BETA RC PID.
Starting with Build 3764 real PID’s apply. Old BETA-keys do not apply.
Windows Server 2003 Build 3764
Finalized Thursday and publish Friday morning, this is the same as build 3763 but has the new “full” shipping PID’s. Otherwise it’s identical to 3763.
Windows Server 2003 Build 3765
Targeted for 2003-02-07, published 2003-02-08 and ESCROW, intended as RTM/GOLDEN. Minor changes compared to 3764.
The final build number will differ from 3765, but if build 3765 is stable – survives testing without showstoppers – it’s the code in this build that will be “golden”.
No new code will be checked in after this date, if not a “showstopper”.
RTM
Time is critical. With the commitment of launch the 24th of April (boxes in stores), Microsoft has to RTM the code March 12, 2003.
The code that is RTM has to survive about 15 days of ESCROW before RTM.
Important Dates
April 23, 2003 Release of GPMC
April 24, 2003 Launch of Windows Server 2003 in USA
May 1, 2003 Release of ADS (Automated Deployment Services)
May 12, 2003 Release of ADAM (AD Application Mode)
RTM + 90 days Release of Metadirectory Service
June 2, 2003 Release of SharePoint Services
June 15, 2003 Release of Real Time Services
June 15, 2003 Release of Digital Rights Management