How are Exchange 2007 CALs installed in the Licensing MMC when the 'Product View' does not show Exchange 2007 server? Is there a manual method of making Licensing see and use the application? Basically our client has a very simple, stable single domain installed in 2002 with 2 xDCs and a single Exchange 2000 install for 80 or so users. No problems for 6 years. Recent successful introduction of Win2003R2 x64 on 3rd new server and full upgrade to AD to support Exchange 2007. Exchange 2007 fully installed and several users migrated successfully from old Exchange 2000 to new Exchange 2007 server. No problems with this (apart from falling foul of the 4Gb freespace size min to the Hub queues and failing transport sevice starts - beware the DELL default, its far too small - but that's a different story). So the mail system works well. The problem now is that the 'Product View' in the Licensing MMC does not show the Exchange 2007 installation and there is no way of adding it manually. License logging is installed and running on both the new server and the old Exchange server and replication works across them as expected. But still no "Microsoft Exchane 2007 Server" entry in Product View on either server. In itself this would appear not to be a great problem, the Exchange server install was a fresh Volume Licensing copy with the Product Code from thedisc packet. BUT since the Licensing doesn't know the server exists I cannot add any CALs. Interestingly the 4 users attached so far have not raised any errors in the Event viewer about missing licenses and they attach cleanly. Is this as expected for a VLM product? And if so is the Licensing tool redundant for Exchange 2007 VLM? Or is this system broken and needs fixing? My next move is to move the license files and hopefuly force the servers to add their applicaitons afresh. However I think this is quite drastic and would rather not run the risk of throwing off the users (20hrs /day inc VPN remote users). There seems to be absolutley no info about this anywhere. Have I looked in any of the right places? Please advise. Any comments much appreciated. Rupe

There's no forced CAL monitoring system involved in Exchange 2007 that I know of. Admins are supposed to find manual or 3rd party methods to monitor that their systems comply with bought licenses.

Thanks KarriR Wehavea suspicion this may be the case. ButI would be much reasssured if I could see this as a declaration by Microsoft of this as fact and there is no funny business with closing any connections over 50 etc. Surely integrating licensing for such an heavily embedded product as Exchange 2007 into AD would be the obvious thing to do to enforce license compliance especially as the have already done it with previous versions. Just strange there's no mention of it anywhere. Perhaps I've simply not been looking in the right places... Anyone?

Hi Rupe, From your post, I understand that your main problem is that Exchange 2007 not shows in Licensing MMC and due to it, you cannot add CALs for Exchange Server 2007. Regarding the Licensing MMC, I would like to clarify that I am not a expert in this aspect. Per my research, It might function differently based on the version and edition of the operating system that is installed. As Licensing MMC is a Operating system component, I am not sure whether it is by default not showing in the MMC. So I advise you also post this issue to Platform Server Newsgroup, or you can submit a case to our Professional Support Service. By the way, Here is a article about Licensing MMC, which I found from TechNet Windows Server library, I hope it helps. http://technet2.microsoft.com/windowsserver/en/library/3745d53b-717e-422d-8618-f3e452143d2b1033.mspx?mfr=true More information about Exchange 2007 license: Exchange Server 2007: Platforms, Editions, and Versions http://technet.microsoft.com/en-us/library/bb232170(EXCHG.80).aspx Exchange Server 2007 Licensing Q&A http://www.microsoft.com/uk/howtobuy/exchange2007-faq.mspx regards, Jason

Thanks Jason, I'll post in the Server Platform group too. I've looked at these pages you mention previously but amongst the marketing guff, boilerplate and Std v Ent issues there doesn't seem to be any mention anywhere about license compliance and AD registration and manipulation. I should have mentioned previously that our client uses per client licensing rather than per server and that the licensing is working fine assigning server and exchange2000 licenses (and throwing up 'event's when they ran out previously). No sign of exchange 2003 or Windows Server 2003 however in hte Licensing app. It be good to have a definitive technical note about how it has changed.