VMware Communities: Message List - Server 2008 MS volume license install on VM

Re: Server 2008 MS volume license install on VM

Texiwill — Fri, 03 Jul 2009 12:49:53 GMT

Hello,

Moved to Virtual Machine and Guest OS forum.

Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'
Also available 'VMWare ESX Server in the Enterprise'
SearchVMware Pro|Blue Gears|Top Virtualization Security Links|Virtualization Security Round Table Podcast

Re: Server 2008 MS volume license install on VM

spc1968 — Thu, 02 Jul 2009 21:26:31 GMT

Found it. Thx again.

Re: Server 2008 MS volume license install on VM

RParker — Thu, 02 Jul 2009 21:00:07 GMT

32 bit version of 2008, there is no option under Windows > Server 2008 32 bit

It's there you must have missed it. Server 2008 is fully supported 32 and 64.

Mount a 32 bit Server VM with the wmtools, copy that msi over to that VM and install from the msi file. There should be a folder called vmtools, you can edit the CD/DVD on any VM and mount the iso.

I think the real issue surfaced here from 'No description for 'Server 2008 32 bit'

Look at EACH entry Carefully... Windows 2008 Server 32-bit is RIGHT there

Re: Server 2008 MS volume license install on VM

spc1968 — Thu, 02 Jul 2009 19:24:27 GMT

Hello RParker,

Nice to hear from you again.

I know it's not a physical. Are you referrering to VMWare tools? If so I tried that as well but found it didn't like the description 'Other' as the OS type. So I had to trick it into thinking it was 64 bit.

If you were referring to VMWare tools, here is what I found out. When originally installing the 32 bit version of 2008, there is no option under Windows > Server 2008 32 bit . Now there is an option for Server 2008 64 bit(yeah!), but this is not what we were installing so I selected bullet mark Other (then I typed manually Server 2008 (32 bit) it let me install the OS but it I guess the VMWare tools doesn't like "Other" no way and no how. So I manually changed that back to 64 bit.... Even though it really is not.

Wham - It then let me Install VMWare tools. And once again, BAM - It not found the Ethernet controller driver or detected it.

I think the real issue surfaced here from 'No description for 'Server 2008 32 bit' Is this by design? I guess I would have thought VM would include 32 bit as that? OR would they.. How should the 32 bit army handle that for future reference? Or are we the trend-setters as of today?

I am not a 32 bit army fan, I am just trying to help others going down that path. 64 bit is surely the standard moving forward.

Re: Server 2008 MS volume license install on VM

RParker — Thu, 02 Jul 2009 18:25:28 GMT

So I tried to use that adapter driver for my 32-bit installation and it didn't like it, so I went down the list of all the Intel listings and so far I've not found the right one.

It's a VM, that Intel is a physical device, no device exists in VM. That's why you ALWAYS install the tools. ALL the correct device drivers will be needed and you don't need ANY OTHER driver.

Server 2008 MS volume license install on VM

spc1968 — Thu, 02 Jul 2009 18:14:09 GMT

Hello All,

Recently after using a standard volume license ISO CD for server 2008 (32-bit) the only thing that didn't go quite right was it could not find the driver for the Ethernet controller.

So I did a comparison of a completed 2008 install that was (64-bit) MSDN ISO CD, it used the Intel(R) PRO/1000 MT Network Connection Adapter

See attachment below.

So I tried to use that adapter driver for my 32-bit installation and it didn't like it, so I went down the list of all the Intel listings and so far I've not found the right one.

Here is some background info if this helps. Not sure why it didn't detect the Ethernet driver here?

The ESX server is 3.5 ESX and it's hardware is IBM 3650 model 7979-C1U

The Virtual Center server that talks to the ESX is running on an IBM 346 model.

Any thoughts of what driver to use? Your help is greatly appreciated.