Windows Server - 2008 Retail Licence

I am the proud owner of a copy of 2008 Enterprise with 25 Cals, as of Friday
there :)

I have one question, and I know that should really know the answer to this,
but....

I am about to purchase hardware for this fine product, but I want to give it
a blast right now, which got me thinking, I know I can install it onto some
existing piece of hardware and just use it in pre-activation mode (eval?) for
the tryout, but will I be able to move it to another server if it has been
activated on another? Will the license allow this? I mean what happens if you
want to upgrade your server to a better model, can it be done? or will I have
to look out for black sedans?

Thanks for any help

  Peter Foldes replied...

You have 25 Cals. The answer is obvious
--=20
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

Friday=20
this,=20
give it=20
some=20
(eval?) for=20
been=20
if you=20
I have=20

  Headsu replied...

Okay....

I will take that as yes, that I can move from one hardware platform to another
if I have to.

Headsup

of stability issues. I have now been asked to provide a quote for upgrading the hardware to something proper. But as the company already has a SBS 2003 Standard license (OEM SBS 2003 again. The question I have is as follows: - If I purchase new server hardware to replace the current hardware, am I allowed to re-use the OEM license that came with the old Hardware? Knowing that the OEM license was bought as a seperate piece of software from the old hardware. Last thing. . . The person that put the old Hardware spec and software together is no longer in business, so I will not be able €¢Monday (1) Montreal (1) No, the OEM software lives and dies with the server hardware. I assume the former IT guy was a licensed reseller and just put the server they have loaded, or are we allowed to migrate the extra CALS to new server Hardware (if the new Hardware has a new SBS 2003 license)? Regards, Raoul. Same issue with

I love it so far. Now someone tell me, WTF did Vista ever come out? - - AF Windows Server SBS Discussions Windows Server 2008 (1) Office 2007 (1) Windows 7 (1) Vista try for 30 days when SP1 came out, both 32 and 64 bit, good solid hardware, and could not stand it. For the most part it was fine, nothing more than down in 17 where it took Vista 30-45. Everything opens much faster, and wow, hardware that worked with XP, did not work with VISTA, and somehow does work with Windows wanted it, did not tweak anything in Windows 7 yet, it has been a week. - - AF I must be abnormal then because my Vista's browse fine, work fine and Win in my vocabulary. Considering my oldest boy is a fed, it will stay this way :-). - - AF Check again with your sources. - - AF This is what it says: Windows 7 build 6.1.7000.0.081212-1400 - - AF Cris That might be, the case. I got it the "right way", since I get my stuff in my locker when I go to my short grave yard shift. - - AF Yep, have to agree Susan. I have 15 domain users on Vista with SBS 2003

Moving SBS 2003 to new hardware Windows Server We are a small organisation with only "IT"-man (me, with little experience issue now and want to move the whole installation to a new box. As the hardware changes I assume we need to do a clean install of SBS 2003 with all procedures (that is Acronis' terminology, other do similar) bring up the image on the new hardware. For SBS03 the US$50 Macrium Reflect will allow full image to disk and restore is quite likely (depending on the HDD subsystem) that SBS will boot on the new hardware anyway. Method 5 is to virtualise the SBS by doing a P2V conversion. This has not licensed" for the moves. . We plan on putting the current software onto a new hardware platform, after which the old server will be decomissioned. . . We will not be using the your answer, but unless I misunderstand, it looks like that I'd be needing 3 hardware platforms to perform for a swing migration. As said we are only a small organisation to do this with. I only will have 2. The old server and the new hardware. Thanks for the suggestion though. You do if the original software is OEM. It lives and dies with the hardware, and will not activate on the new hardware. If it was retail then you can

receommended 'best practice' to configure. I would not disable EDNS0 if this is working. Ace AF> Good find, Jonathan. Merci. AF> What query command did you use with Dig to AF> determine this, or did you use nslookup? Neither. I used my own tool. I just you for the RFC EDNS0 note. I thought it was longer than 8 years. :-) Ace AF> I would welcome seeing such a list. I will give it some further consideration. For to get this set up again. Thanks. Andrew. AH> http: / / support.microsoft.com / kb / 968372 AF> I have not seen this issue yet, with 2008. [. . .] I do not see forcing AF> this entry to help resolve some TLDs, = A0unless there is something AF> else this key does with EDNS0 that is not stated in the following AF> article. it is a bodge. It has all of the hallmarks of one. Stopping things

I have read about migrating from SBS2003 to SBS2008, but that talked about using different hardware. Since my hardware under performs with SBS2003, I want to use the same hardware I currently own. In addition to the added support for my hardware, I want to be able to do opportunistic TLS with exchange. Another organization we do best way to handle this would be to do a swing migration out to different hardware, and then migrate back to the original server. It won't be completely painless, but 32bit and SBS 2008 is 64bit. and since you don't want to get new hardware, you pretty much end up flattening and starting over. But 5 GB of RAM won I have read about migrating from SBS2003 to SBS2008, but that talked about using different hardware. Since my hardware under performs with SBS2003, I want to use the same hardware I currently own. In