Exchange server has 2 for instance.
 
But my question is, does installing TDP require 1 extra normal client license?
The way I do it is.
 
Register the client (2 processor = 2 licenses) and register the same client again with 
a different name allowing it to run with a different schedule and running the 
exchfull.cmd file.
This would result in running 2 schedules on the same machine and thus using 1 extra 
license?
 
But I might have got I all wrong.
 
 
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 22, 2004 11:31 AM
To: Klaas Talsma - KTL
Subject: RE: how many licenses needed
 

Klaas, 

First of all I would have to know how many processors all clients have. 

Richard. 



 
"Klaas Talsma - KTL" <[EMAIL PROTECTED]> 
22-06-2004 11:47 
        
        To:        <[EMAIL PROTECTED]> 
        cc:         
        Subject:        RE: how many licenses needed



Hallo Richard,

Even voor de goede orde, ik zou de vraag niet stellen op de lijst als er niet enige 
onduidelijkheid was over de situatie die ik voor me heb.

Mocht je als medegebruiker van de lijst nog een antwoord kunnen geven dan zou ik dat 
uiteraard op prijs stellen.

Mvg,

Klaas Talsma


--
Bell Microproducts Europe BV

This message is intended only for the use of the person(s) (\"the intended 
recipient(s)\") to whom it is addressed.  It may contain information which is 
privileged and confidential within the meaning of applicable law.  If you are not the 
intended recipient, please contact the sender as soon as possible.  The views 
expressed in this communication may not necessarily be the views held by Bell 
Microproducts Europe BV.




--
Bell Microproducts Europe BV

This message is intended only for the use of the person(s) (\"the intended 
recipient(s)\") to whom it is addressed.  It may contain information which is 
privileged and confidential within the meaning of applicable law.  If you are not the 
intended recipient, please contact the sender as soon as possible.  The views 
expressed in this communication may not necessarily be the views held by Bell 
Microproducts Europe BV.

Reply via email to