RE: [ActiveDir] OT: Server With Hyperthreading/Multicore Licensing

[Edwin]

Microsoft Windows does not distinguish between physical and logical processors.  Windows simply fills out the license limit using the first processors counted by the BIOS. http://www.microsoft.com/windows2000/server/evaluation/performance/reports/hyperthread.asp   SQL Server does not have this luxury.  SQL Server counts each logical processor as an individual processor.  But you do not need to obtain a separate license to be in compliance when using HTT. http://www.microsoft.com/sql/howtobuy/SQLonHTT.doc   Edwin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marc A. Mapplebeck Sent: Monday, October 24, 2005 10:40 AM To: ActiveDir@mail.activedir.org Subject: [ActiveDir] OT: Server With Hyperthreading/Multicore Licensing   Sorry for the OT post, I have a quick question that one of my students asked and I am not sure myself of the correct answer. How does a multithreaded processor affect licensing and server abilities. What would happen if you had a quad CPU server, but the CPUs were also hyperthreaded, effectively making it an 8 CPU system, could you use Server 2003 Standard, or would you need to get Enterprise? How would this affect other server products with per-cpu licensing such as SQL. And how about a CPU that is multi-core, 8 seperate processes, 4 chips but with 8 CPU cores. Any help would be appreciated. - Marc   _-_-_-_-_-_-_-_-_- -"During times of universal deceit, telling the truth becomes a revolutionary act." - George Orwell, 1984 _-_-_-_-_-_-_-_-_- Marc A. Mapplebeck, MCP/MCDST/N+/A+/CNA IT Manager, City Animal Hospital Ltd. MCP#: 3146827 CompTIA#: COMP001002835054 [EMAIL PROTECTED] [EMAIL PROTECTED] _-_-_-_-_-_-_-_-_- P: 506-471-7044 ICQ: 26743793 Yahoo!: mmapplebeck MSN: [EMAIL PROTECTED] _-_-_-_-_-_-_-_-_- This e-mail communication (including any or all attachments) is intended only for the use of the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this e-mail, any use, review, retransmission, distribution, dissemination, copying, printing, or other use of, or taking of any action in reliance upon this e-mail, is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete the original and any copy of this e-mail and any printout thereof, immediately. Your co-operation is appreciated. Le présent courriel (y compris toute pièce jointe) s'adresse uniquement à son destinataire, qu'il soit une personne ou un organisme, et pourrait comporter des renseignements privilégiés ou confidentiels. Si vous n'êtes pas le destinataire du courriel, il est interdit d'utiliser, de revoir, de retransmettre, de distribuer, de disséminer, de copier ou d'imprimer ce courriel, d'agir en vous y fiant ou de vous en servir de toute autre façon. Si vous avez reçu le présent courriel par erreur, prière de communiquer avec l'expéditeur et d'éliminer l'original du courriel, ainsi que toute copie électronique ou imprimée de celui-ci, immédiatement. Nous sommes reconnaissants de votre collaboration.     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Sent: October 24, 2005 09:38 To: ActiveDir@mail.activedir.org Subject: [ActiveDir] Geographic Domain Setup Hello Everyone.   The company that I work for has been divided into two isolated parts.  As a result the corporate domain that is used will also need to be divided.  The employees of the old domain will remain in their place while others will be put into a new domain.  One domain will have nothing to do with the other.  I have been tasked with heading the creation of a new domain that will be used in different geographic locations;   Atlanta, Georgia Miami, Florida Orlando, Florida Houston, Texas Fremont, California Vancouver, Canada   I have built a domain before but this was for one office of less than 100 employees.  This domain is of a much larger scale and more complex.  I have read a few MSFT articles and have a little bit of information as to what I am getting myself into.  I was hoping that I would be able to get more information from the community in hopes of getting real life experience knowledge than a document that outlines best practices.   When I built the single site domain I had the below configuration that worked very well for me.  I think that I am going to create a similar if not exact root domain.  I think that I would am having more problems with considering the geographic issues that I will be facing.   2 Domain Controllers             Both DNS Servers             FSMO roles divided             Both Global Catalogs 1 File Server             Roaming Profiles             Centralized Storage for User Files 1 Anti-Virus Server 1 WSUS Server 1 Exchange Server   Thank you all for your replies, Edwin