I am considering using Server 2008 Standard x64 with a Hyper-V installation of SBS 2003. Anyone see any drawbacks in doing this?
you can buy it today from dell bundled up.. so its just a matter of time Right now I"m using 2008 std with hyper-v and sbs2008 in trial mode until a cert and key comes available. and it runs good. You just need a shed load of ram.
Well it all depends on how many users the SBS machine is going to host. but in a hyper-v I had to set it to 4 gig or it wont install period. and with just a handful of users (home endusers) its idling around the 4gig mark in hyper-v. But most people recommend 8 gigs or more depending on the size of the network etc.. From what I understand, 4gigs of ram is least amount you need for under 5 users. Since I'm on a home network, I also have to you the POP3 connector/smtp relay to send & receive my emails. But with the POP3 connector, I just click on the notworking@home.com email address and click on send to this mailbox. With the catch all mailbox, I don't know enough but a solution was posted on MS site forum using edge transport since the hub transport was total rewritten for Exchange 2007.
Ok, my SBS2008 OEM server came in today. If someone would be so kind as to help me get the information needed out of this machine, I would greatly appreciate it. I would love to share whatever is needed. I will put out this small caveat, there is a chance I don't have an actual OEM copy and just a pre-installed retail key as when I ordered the OEM option wasn't in the official channel. I guess I'll know when I boot up and find out if the key is different than the sticker. -- E: Good news, it looks like I did get OEM so soon you should all be able to do whatever it is you need to do with this stuff. I have the OEM key from Magic Jelly Bean I have the PID from system info I have the 2,731 byte OEMCERT.XRM-MS from tokens.dat My SLIC table is 374 bytes according to everest. Bad news: Neither HWDirect nor ACPIScope can run, even copied to the HD and even as administrator and even as administrator w/ compatibility mode. Neither can load their driver. So, any alternate methods of pulling that SLIC table? Is there anything else we need? Now, once I (and all of you) have this information, it will be possible to install SBS2008 on any hardware w/ SLIC table support, including Dells purchased sans OS, correct? Is there an easy way to integrate these into those BIOS emulation hacks so that we could use this for VMWare/Hyper-V?
Run Everest to find out what SLIC table shows. , It might just say Dell system, the last few dell servers with Windows 2008 std ed. I have ordered for my clients say that. I can't see them changing for SBS, but your right to check, you never know. I have a few Hyper-v servers going here, I try out the key. , Does ACPI scope load if you boot up with driver signing is set to be disabled ? Moto
In Everest, how do I peak in on the SLIC table? I have v3.80.952 and it just shows that there is an SLIC table, the address, and size really. Also, I was able to get hwdirect to run w/ the driver signing disabled. But 1.88 won't let me save the dump w/o a registry key that I don't have. However ACPIscope does not run, and I'm wondering if that has to do with SBS2008 being x64.