CAL and the Meaning of Life

[Guest]

Hello,

I am wanting to purchase and install window 2003 server software. However,
we have a unique setup were we only use the server for DHCP services (for
aprox. 500 machines). We remotely access the server from our home offices
using Remote Desktop. The users never (they can't even see the server) the
services on the server, except for DHCP requests. Do I still need a CAL for
each user?

Cheers,

Mac

 

[roop]

Hello,

I am wanting to purchase and install window 2003 server software. However,
we have a unique setup were we only use the server for DHCP services (for
aprox. 500 machines). We remotely access the server from our home offices
using Remote Desktop. The users never (they can't even see the server) the
services on the server, except for DHCP requests. Do I still need a CAL for
each user?

Cheers,

Mac

 

[Guest]

Roop,

I don't think your reply posted.

Mac

 

[Lanwench [MVP - Exchange]]

In

Hello,

I am wanting to purchase and install window 2003 server software.
However, we have a unique setup were we only use the server for DHCP
services (for aprox. 500 machines). We remotely access the server
from our home offices using Remote Desktop. The users never (they
can't even see the server) the services on the server, except for
DHCP requests. Do I still need a CAL for each user?

Cheers,

Mac

My first question is, why do you want to buy & install Win2003 just for
DHCP? That sounds like an incredible waste of money/resources.
My second question is, what does "remotely access the server from our home
offices" mean - Terminal Services?

 

[Guest]

Hello,

Thank you for your response. Provisioning. We have Call Center personel
(non techs) who access and build scopes for our interenet users. The MS
interface is easy for them to use.

Remotely access, that is to provision the DHCP server. Our call center and
geographically displaced from the servers. We use Remote Desktop to connect
and provision the DHCP scopes.

I'm presuming that Terminal Services are used by Remote Desktop?

Cheers,

mac

 

[Lanwench [MVP - Exchange]]

Hello,

Thank you for your response. Provisioning. We have Call Center personel
(non techs) who access and build scopes for our interenet users. The MS
interface is easy for them to use.

OK. I find this an odd choice still, as there are so many alternatives, but
that's no matter. Re CALs for users, I doubt you need them, but you should
call Microsoft licensing for this, to make sure you get the correct answer
from the source.

Remotely access, that is to provision the DHCP server. Our call center
and
geographically displaced from the servers. We use Remote Desktop to
connect
and provision the DHCP scopes.

I'm presuming that Terminal Services are used by Remote Desktop?

No. Remote Desktop is for admin only use (which it sounds like you're using)
and TS is something else entirely - it's RD but for users to use/share as a
big fat desktop, essentially. You're fine without it.

 

[Guest]

I don't disagree with your comment concerning our choice of DHCP servers.
What other options did you have in mind? We have one site that uses Cisco's
CNR. Not particularly resiliant, but it gets the job done.

I think our application is not the typical enterprise. Each user has their
own scope (and virtual network). I would love to hear what you have say.

Cheers,

Mac

 

[Lanwench [MVP - Exchange]]

I don't disagree with your comment concerning our choice of DHCP servers.
What other options did you have in mind? We have one site that uses
Cisco's
CNR. Not particularly resiliant, but it gets the job done.

I think our application is not the typical enterprise. Each user has
their
own scope (and virtual network). I would love to hear what you have say.

I'm afraid I may be getting a little out of my depth <blush>. Seriously, I'm
not sure what your needs are, nor why the configuration you're using is in
place/what it's used for. Try posting with more detail in a networking group
to see what you can see.