As you probably know, Sage Intelligence is no longer billed monthly. They no longer have a monthly unlimited plan.
I had a client that was on this plan, and I had to update their Sage Intelligence keys. Here are some things that I found that I had to do. It was actually pretty simple.
I did not have to change their license key in Sage Intelligence. That key was automatically updated with the number of licenses that they purchased. It all seemed to update properly.
I found that I had to manually go through and remove, by right-clicking on the customer number in the upper left corner of License Manager, any of the old workstations that had been left in and were registered because it was previously an unlimited Sage Intelligence registration. Sage Intelligence now balked at that.

My client had purchased three Report Manager licenses. What I did was I cleared out and made sure there were only three workstations showing up underneath that customer number in the License Manager as assigned to licenses. If you do not remove excess licenses, you’re going to get the message that shows down below. Plus, when you remove licenses, Sage Intelligence is going to require you to re-run the Perform registration as well.
Because the customer never had to worry about how many workstations were licensed, they never paid attention to how many workstations were assigned a license key. Remember, in Sage Intelligence, the licensing is different, and it’s a named user license.
Once I had all the licenses properly assigned (meaning I had purchased three report managers and only three were assigned), then I ran through and did the registration. That updated Sage with the proper licensing. Other users did not have to do this. I only had to do this on one workstation, and it flowed through to everybody.
I know that for 99.999% of you, you already know this. I’m just memorializing this for the 0.0001% like me, who don’t work with Sage Intelligence all that frequently and might log in and look for this someday in the future.


Leave a Reply
You must be logged in to post a comment.