No such luck on that one. What you could do though, if you are deploying to computers, is use AD groups that you put computer accounts into. If you apply the software to a specific group (and remove authenticated users) you can then count the computers in the group for licensing purposes, if that is the goal. We do that with a lot of limited license software that we have, but someone needs to be responsible for counting them =)
-Bonnie From: Glen Johnson [mailto:[email protected]] Sent: Wednesday, July 01, 2009 10:47 AM To: NT System Admin Issues Subject: RE: GP software deployment Ok.. I was hoping it would count the number of installs. Oh well, another worthless feature MS put in. From: Miller Bonnie L. [mailto:[email protected]] Sent: Wednesday, July 01, 2009 1:45 PM To: NT System Admin Issues Subject: RE: GP software deployment Yes. That value doesn't count installed computers, it counts how many times you have deployed or redeployed that application in that GPO. For example, when we first Deployed Office 2003 on SP1, the deployment count was 0. When we slipstreamed SP2, it required the software be redeployed, so now the count is 1. I'm not sure what someone might really use it for, but that's what it does. -Bonnie From: Glen Johnson [mailto:[email protected]] Sent: Wednesday, July 01, 2009 10:33 AM To: NT System Admin Issues Subject: GP software deployment Anyone doing this and see the deployment count show anything other than 0. We've got Office 2003 and 7 deployed and both show count of 0. Packages are assigned to computer in several ou. I know that isn't accurate as we have many people using the deployed packages. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
