Were you able to get the query Garth blogged about to work? I get "@CollID - "Must declare the scalar variable "@CollID".
________________________________ From: listsadmin@lists.myitforum.com <listsadmin@lists.myitforum.com> on behalf of tgonza...@tins-swtx.com <tgonza...@tins-swtx.com> Sent: Thursday, March 31, 2016 10:39 AM To: ms...@lists.myitforum.com Subject: RE: [mssms] Microsoft True Up Report I am going through one right now, I'm using MAP 9.3 and using custom queries from what garth has blogged. As of yesterday, I wrote a new query that is pulling back when last used and we will be doing a reclamation on those items soon. The map tool is more in line for sql to look at core/proc, and is also used since we have over 15 domains in house. Sent via the Samsung Galaxy S® 6 edge, an AT&T 4G LTE smartphone -------- Original message -------- From: Brian McDonald <mcdonald...@hotmail.com> Date: 3/31/2016 10:17 AM (GMT-06:00) To: ms...@lists.myitforum.com Subject: [mssms] Microsoft True Up Report Good day, I have been tasked with putting together the Microsoft True Up report. I've been doing some searching online and it looks like folks are saying there are limitations with what you can do with Asset Intelligence. I saw a query posted by Garth here: http://smsug.ca/blogs/garth_jones/archive/2013/02/07/microsoft-true-up-report.aspx - Although the query isn't working at it states "@CollID - "Must declare the scalar variable "@CollID". Microsoft True Up Report - Garth Jones<http://smsug.ca/blogs/garth_jones/archive/2013/02/07/microsoft-true-up-report.aspx> smsug.ca Pingback from Microsoft True Up Report | My CMS. June 10, 2013 5:41 PM This Blog I'd like to know how others are doing True Up Reports? Is BDNA Normalize worth looking into? Here is another guide that looks very intriguing. http://myitforum.com/myitforumwp/2012/07/13/performing-a-software-true-up-in-under-5-minutes/ I would need to convince management to purchase the software, of course. Love to hear what people know about this to get me down the right path. Thank you, Brian M.
