tag:blogger.com,1999:blog-5976686513564131325.post8184312207797231313..comments2024-03-17T15:34:05.492-06:00Comments on MPECS Inc. Blog: Further to Licensing Office in a Terminal Services EnvironmentPhilip Elder Cluster MVPhttp://www.blogger.com/profile/06082028960643490292noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-5976686513564131325.post-45582433558659544982011-07-29T00:19:39.130-06:002011-07-29T00:19:39.130-06:00Care to update the post above to include Eric Ligm...Care to update the post above to include Eric Ligman's comment? The article he wrote and linked to seems to agree with what Anonymous #2 said. Your examples are great, the total numbers are just a little off when you include the "Secondary Use Right" (now called "Portable Device" in the current <a href="http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx" rel="nofollow">PUR</a>.)<br /><br />Just assign the licenses to the user's PC, and the laptop device license is included. (Again, we are talking about one user per PC and the same user for the laptop.)<br /><br />This makes the totals for your original four examples: 22, 11, 22, 22.Williehttps://www.blogger.com/profile/00716983968292660728noreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-52800972837085236722010-05-13T08:50:04.587-06:002010-05-13T08:50:04.587-06:00Its a pain when tracking users who use remote devi...Its a pain when tracking users who use remote devices at a library. In this case you'd probably be better licencing per user (but that does get expensive if all of your users run in shifts).<br /><br />This part of terminal server licencing really does not make things easy to track.<br /><br />However, in a small business environment, it's unlikely (although possible) that multiple shifts are used so per user is probably better.Absoblogginlutely!https://www.blogger.com/profile/10375412476973524867noreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-38810541265432811982010-05-12T07:47:30.354-06:002010-05-12T07:47:30.354-06:00The ability to install on a laptop that you are re...The ability to install on a laptop that you are referring to is called, "Secondary Use Rights," and you will see this covered in my, "How is Microsoft Office licensed?" post: http://blogs.msdn.com/mssmallbiz/archive/2007/12/06/6684366.aspx<br /><br />- Eric LigmanEric Ligmanhttp://www.EricLigman.comnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-17758279133015243532010-05-12T02:57:37.729-06:002010-05-12T02:57:37.729-06:00I'm not disagreeing with you that each device ...I'm not disagreeing with you that each device must be licensed. I'm saying that Microsoft Office purchased under a volume license agreement also gives the primary user of the device portable use rights (e.g. laptop) and network use rights (terminal server). A single license covers all three devices for that one user. You can read the FAQ on the Microsoft page I linked to if you don't believe me. It's also clearly spelled out (OK, maybe not clearly, but buried in the fine print) of the end user license agreement.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-72211119462497799272010-05-11T21:30:56.640-06:002010-05-11T21:30:56.640-06:00My point on the licensing based on each device cam...My point on the licensing based on each device came straight out of Eric's e-mail. I do believe that it was quite clear that _any_ device accessing Office must be licensed.<br /><br />TS License Managment issues a token to all devices that connect. Usage should be able to be monitored there.<br /><br />PhilipPhilip Elder Cluster MVPhttps://www.blogger.com/profile/06082028960643490292noreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-2988526059459308922010-05-11T19:52:34.519-06:002010-05-11T19:52:34.519-06:00In response to the first comment, you may access ...In response to the first comment, you may access your licensed device from any other device, so it doesn't matter if a user accesses Office on the terminal server from a different remote PC each time.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-25348205107199996612010-05-11T19:46:33.462-06:002010-05-11T19:46:33.462-06:00A point of clarification: Microsoft Office, purcha...A point of clarification: Microsoft Office, purchased under a volume license agreement, entitles the primary user of the device to also install Office on a portable device, e.g. laptop and also access Office on a terminal server (all with a single license). So in the example you provide, the four remote users with PCs and laptops only require one Office license each. Here's a link to some FAQs about Office licensing: http://office.microsoft.com/en-us/products/ha102333141033.aspx By the way, I passed Microsoft Exam 70-121: Designing and Providing Microsoft Volume License Solutions to Small and Medium Business, so I have some idea of what I'm talking about :-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-83399948919050249382010-05-11T18:51:33.003-06:002010-05-11T18:51:33.003-06:00So how do you track this? If SBS licensing is bas...So how do you track this? If SBS licensing is based on per user, how do you know if the remote user is at their remote PC or at their home PC? Or at a hotel needing to work on a document?<br /><br />I can see a situation where a user is at a hotel, uses the business center to RDP into the terminal server and work on a document. Technically, he would be allowed to logon to the TS, but NOT open Office.<br /><br />I assume that MS knows this may occationally happen - so they use the 'honor' system for value licensing. But if this starts happening alot and you want to try and best as honorable as possible and purchase another license - how do you know that you need to do this? Can you track the # of devices that open office via a log somewhere? Can you automate an alert for each 'unknown' device that opens office?Anonymousnoreply@blogger.com