- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I appreciate you keeping up on this one! I had thought about trying method two but really assumed that they would have fixed it by now. Method one is surprising because I used the migration fling initially to migrate our working 2.x Acrobat stack to 4.x and that's where I ran into the licensing problem.
I've been using the 2.18.0.25 agent since then without a problem. Funny enough, I upgraded the manager to 2009 (4.2) this weekend and installed the 2.18.6 agent and ran into the same licensing problem. As soon as I installed the 2.18.0.25 agent on the base it all worked again. That's why the first workaround that they gave you working is surprising to me. For me it's based on the agent version on the base image and not what it was captured with.