Do I have to buy SBS 2003 also?
Smitty
PC and run it on my XP Workstation so I can test out my new found knowledge
without causing any problems on my "real" server. In particular, I want to
start testing out Group Policy. After I load Virtual PC, do I load my
original SBS 2003 on my pc as well? Am I going to have a licensing problem?
Mike Brannigan [MSFT]
news:B2365B4B-226B-45BC...@microsoft.com...
Yes you have a licensing issue.
You treat each virtual machine just as you would a "real" device as regards
licensing.
So to install SBS on your VM you need to buy another license for SBS.
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Smitty" <Smi...@discussions.microsoft.com> wrote in message
news:B2365B4B-226B-45BC...@microsoft.com...
Robert Vincent
Robert
Chris Hedlund
Microsoft, the answer is always YES! Just kidding of course :-)
Once you have installed the SBS software on your server, the license is tied
to that machine and cannot be installed on another, including a virtual
machine.
Chris Hedlund
ched...@alltel.net
http://spaces.msn.com/members/officsba
http://www.activewin.com
Juhani
you were installing had a per processor licensing option then you could
install several copies of that under VPC on a machine with only one
processor (and presumably a lot of memory). [It was SQL Server 2K I think]
Are you saying that isn't true or just that SBS 2003 doesn't have a per
processor licensing option ?
Juhani
"Mike Brannigan [MSFT]" <mike...@online.microsoft.com> wrote in message
news:%23mzfK9P...@TK2MSFTNGP12.phx.gbl...
Mike Brannigan [MSFT]
news:ug2TqYVH...@TK2MSFTNGP14.phx.gbl...
>I saw a reply elsewhere from some other Microsoft guy that if the software
>you were installing had a per processor licensing option then you could
>install several copies of that under VPC on a machine with only one
>processor (and presumably a lot of memory). [It was SQL Server 2K I think]
>
> Are you saying that isn't true or just that SBS 2003 doesn't have a per
> processor licensing option ?
While we may offer per processor licensing - this does not mean that if you
install the product on a physical device and then on a VM you only pay for
the processor in the physical device.
VMs are regarded just as a physical device are for licensing.
So you can use per processor licenses on a VM to remove the requirement for
client access licenses (CALs) but this does not work around the licensing
for the software licensing per machine (virtual or real)
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Juhani" <juh...@nospam.discussions.com> wrote in message
news:ug2TqYVH...@TK2MSFTNGP14.phx.gbl...
Juhani
thread.
i.e. it didn't just save CALs it was stated that if you were running on a
one processor (real) machine you needed one copy of a one processor licence
piece of software for that machine irrespective of whether you were running
several copies of it in VPC or not.
Again not wishing to be rude (really!) but as MS licensing is a black art,
are you a licensing specialist or a VPC specialist?
If the latter could we get someone from the former group of people here ?
Juhani
"Mike Brannigan [MSFT]" <mike...@online.microsoft.com> wrote in message
news:%237tSazX...@TK2MSFTNGP12.phx.gbl...
Paul Adare
microsoft.public.virtualpc news group, Juhani
<juh...@nospam.discussions.com> says...
> If the latter could we get someone from the former group of people here ?
>
These are peer support news groups. If you want an official answer on
any licensing question, this is not the place to ask. You should be
contacting your regional Microsoft office and speaking to a licensing
specialist.
--
Paul Adare
"On two occasions, I have been asked [by members of Parliament],
'Pray, Mr. Babbage, if you put into the machine wrong figures,
will the right answers come out?' I am not able to rightly apprehend
the kind of confusion of ideas that could provoke such a question."
-- Charles Babbage (1791-1871)
Mike Brannigan [MSFT]
> Without wishing to be rude, this isn't I'm sure what was said in that
> other thread.
>
> i.e. it didn't just save CALs it was stated that if you were running on a
> one processor (real) machine you needed one copy of a one processor
> licence piece of software for that machine irrespective of whether you
> were running several copies of it in VPC or not.
>
> Again not wishing to be rude (really!) but as MS licensing is a black art,
> are you a licensing specialist or a VPC specialist?
Juhani,
Per processor licensing does not extend from the physical machine to any
virtual machines running on that system.
You license a VM exactly as you would a real PC (this avoids it becoming a
"black art" as a VM is regarded exactly as a real PC or Server for licensing
of all Microsoft products)
So if you purchase a per processor licensed product it may be installed to
either a single real device or a single Virtual Machine.
If we are providing you with conflicting information can you direct me to
the other thread you mention.
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Juhani" <juh...@nospam.discussions.com> wrote in message
news:uhhjFDZH...@tk2msftngp13.phx.gbl...
Mike Brannigan [MSFT]
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Juhani" <juh...@nospam.discussions.com> wrote in message
news:uhhjFDZH...@tk2msftngp13.phx.gbl...
Mike Brannigan [MSFT]
- but it does look like the PM for Virtual Machines (Brad) did say something
along these line on Feb 18th, so I am conferring with him to see if we can
clear this up
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Paul Adare" <pad...@newsguy.com> wrote in message
news:MPG.1c8cdddf9...@msnews.microsoft.com...
Paul Adare
microsoft.public.virtualpc news group, Mike Brannigan [MSFT]
<mike...@online.microsoft.com> says...
> - but it does look like the PM for Virtual Machines (Brad) did say something
> along these line on Feb 18th, so I am conferring with him to see if we can
> clear this up
>
THat would be Ben, not Brad, and when it comes to per-processor
licensing, he is correct.
Have look specifically at Example 2 in this document:
http://download.microsoft.com/download/0/f/e/0fed01e1-1743-42d8-8c35-
dd96eb789d50/virtual-machine-environment.doc
2 instances of BizTalk Server, in two separate virtual machines, yet
only 2 per-processor licenses are required.
Having said that, SBS can't be licensed per processor so none of this
applies to SBS.
Mike Brannigan [MSFT]
I am aware of that document as it is basically the same as spreading a
multiple proc per proc license between multiple machines with a lower number
of processors that sum to the correctly purchased license.
My understanding of the original posters question was that they wanted to
run 2 copes of one lciesed product one on pyshical and one on VM (SBS in
their case).
The poster then brought up
"...
I saw a reply elsewhere from some other Microsoft guy that if the software
you were installing had a per processor licensing option then you could
install several copies of that under VPC on a machine with only one
processor (and presumably a lot of memory). [It was SQL Server 2K I think]
Are you saying that isn't true or just that SBS 2003 doesn't have a per
processor licensing option ?
..."
This gave the impression to me that they still wanted to use a per proc
licese "multple" times in the VMs.
I think we are all OK with this now so will pen an apropraite repsonse to
the orginal poster.
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Paul Adare" <pad...@newsguy.com> wrote in message
news:MPG.1c8ce60ec...@msnews.microsoft.com...
Mike Brannigan [MSFT]
After a little discussion.
You license each VM as you would a regular device.
If you buy a product that is per proc licensing -- say for example you buy a
2 CPU license then you may install that to a physical system with 2 CPUs or
you could install that copy into 2 separate VMs (as each VM only has one
CPU).
What you cannot do is install the 2 CPU license to the physical system and
then install it again into any VMs on that system as the licensed number of
CPUs (2 in this case) has been used by the physical system.
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Juhani" <juh...@nospam.discussions.com> wrote in message
news:uhhjFDZH...@tk2msftngp13.phx.gbl...
Mike Brannigan [MSFT]
http://download.microsoft.com/download/0/f/e/0fed01e1-1743-42d8-8c35-dd96eb789d50/virtual-machine-environment.doc
and the associated End User License Agreement for each product and the
Microsoft Product Use Rights
http://www.microsoft.com/licensing/resources/downloads/default.mspx
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Juhani" <juh...@nospam.discussions.com> wrote in message
news:uhhjFDZH...@tk2msftngp13.phx.gbl...
hughes_ja
testing you can install all the demo products, and they now no longer are
time limited.
MSDN may also have some solutions, but I belive it costs more than TechNet.
Paul Adare
<mike...@online.microsoft.com> says...
> I am aware of that document as it is basically the same as spreading a
> multiple proc per proc license between multiple machines with a lower number
> of processors that sum to the correctly purchased license.
>
Sorry Mike, but this is clearly not the case, especially when dealing
with Virtual Server as there is no way to isolate a VS guest to a single
proc in a multi-proc system, and this is even stated quite clearly in
the document I point you to. In the FAQ section examine the last FAQ
questioning the number of licenses required for the ISA Server example.
It clearly states that because both procs are available to the OS in the
guest that is being used to run ISA, you need a 2 proc license for ISA.
Now extend that to the example with BizTalk above. Again, a 2 proc
system, so you need a 2 proc license for BizTalk, however, notice that 2
instances of BizTalk are being run in 2 separate guests, yet only a
total of 1 2 proc license is required. If what you're trying to say here
were true, in the BizTalk case one would require 2 2 proc licenses, and
that just isn't the case.
Mike Brannigan [MSFT]
I have already issued the correction in my post
Date: Tue, 1 Mar 2005 09:37:26 -0000
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
"Paul Adare" <pad...@newsguy.com> wrote in message
news:MPG.1c8f5d9c2...@msnews.microsoft.com...
Rick
already a client in a SBS domain? Rule #1 for SBS - there can only be 1 in a
domain. I'd love to find a way around this, but as soon as we fire up the
virtual SBS, it sees the "real" SBS and operates in a limited mode.
Rick
Bill Grant
NIC in "local only" mode and using a new domain name. He could even add a
vm running a client OS as a member of this new domain for testing, also
running in local. It never sees the domain on the "real" network. But he may
still have a licencing problem. Each instance of an OS, whether on a real or
virtual machine, counts towards your licence limit.
"Rick" <Ri...@discussions.microsoft.com> wrote in message
news:AF9E517C-2074-468D...@microsoft.com...