Windows Server 2008 R2 from MSDNAA (Final build? Buggy?)

[Eric.]

So I've been running this on my home fileserver for a while and can't help but think that something isn't right. The OS is activated, but in the bottom right corner the build number is still there like evaluation, RTM, and Release Candidates typically do. The build number is 7600, which corresponds to the RTM build number for Windows 7. I've had this installed for a few months, and the system has yet to be able to pull any updates. Also, when browsing through the filesystem it is common for a kernel error to pop up and say something about Explorer.exe having an error. If you hit ignore it goes away and nothing bad appears to have happened.

Its also slow as hell, given the hardware specs. Gigabyte G41M-ES2L motherboard, Core 2 Duo E6600 2.4Ghz CPU, 3GB of 800Mhz RAM.

There also seem to be issues with the video driver, at times when hovering over a menu item, the tooltip box will appear pink for just a fraction of a second before it can load up text.

Adding to the list, it has started disappearing from the network now, and I can't see what's going on because its accessed via remote desktop only.

Help?

 

[GTP_Deathwalker]

ive just got it off Microsoft for evaluation, ive noticed so many bug after using it for a day or two its unbelievable

 

[GilesGuthrie]

We've got a couple of servers running R2 x64 Datacenter edition, and generally speaking they're fine. There's a bug in the Group Policy engine that screws ODBC connections, but that's been there for at least a year. We've got a call in to Premier Support to see if there's a fix.

We're running it on HP BL460c G6 blade servers. Single Xeon 5520, 12GB RAM 2x 146GB SAS.

 

[Eric.]

Hm. I might have to try downloading a Server 2008 R2 image "elsewhere" and seeing if I can get a key working (oddly enough the two (legit) keys I've had are one-time-use and never seem to be valid again - might have to make a phone call). As of now its been mostly fine though. And it seems like those explorer issues only happen when I'm accessing the system physically rather than using remote desktop like 99% of the time. Network functionality has stayed up also.

 

[wfooshee]

In your first post I can't see that you identify the OS. You say you're running "this" on your server, and then say it shows "build 7600."

Is it Win7, or is it Svr2008? Either way, if it's showing that build, it's a release candidate, with a time-bomb key. Keys for those run for 120 days (I think) then the OS stops doing things, like updates. That may be what you're calling one-time use, an expired release candidate key.

Your reference to getting an image "elsewhere" and "finding" a key seem pretty dang close to talking piracy. You might need to clarify or stop.

EDIT: Oh, I see your version in the thread title. Sorry about my first sentence. Literacy is such a gift!
Did you put this on top of a release candidate without wiping the disk? Did you use a release candidate key (which shouldn't have worked anyway?) Not being a student, I don't have access to the MSDNAA set of downloads, different from the Partner Action Pack subscription I have access to as an employee of a Microsoft Partner.