Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management News Blog

ITMS 7.5 Hotfix 1 Released November 18th!

ITMS 7.5 Hotfix 7.1 is now available!
Created: 18 Nov 2013 • 14 comments
jon_sharp's picture
+3 3 Votes
Login to vote
We're pleased to announce the availability of 7.5 Hotfix 1. This update is available through the Symantec Installation Manager and addresses many issues--including a number related to Deployment Solution, Task Server, Cloud-enabled Management and Mac management.
 
For information on what's included in this release (as well as to determine if this hotfix applies to you) see the release notes here: http://www.symantec.com/docs/DOC6860

Comments 14 CommentsJump to latest comment

dcgarbutt's picture

Upgraded my dev environment overnight.  DS 7.5 HF1 not recognising existing, valid license and has reverted to a trial license.

Awesome.

angry

David Garbutt

0
Login to vote
awslyall's picture

Same issue here, please see image

DSlicense.JPG
0
Login to vote
plit's picture

Hi Awslyall,

It's happening for all HF1 installations, but does it affects you anyhow? On my install, i have same licensing issue - but it does not stop me from running any Deployment tasks.

0
Login to vote
awslyall's picture

Hi plit

Not presently, but the license is due to expire in 5 days, so Ill know more then.

Thanks

Andy

0
Login to vote
dcgarbutt's picture

Well, the node count is only 10 licenses.

We're about to kick off several hundred machines for refresh.  I don't think 10 trial licenses that expire in 5 days is going to do the job!

David Garbutt

0
Login to vote
ziggy's picture

FYI to all.  I just installed 7.5 three nights ago, then installed HF1 last night, and our licensing is ok.  I suspect it is OK becuase we have Sym Ed Bundle licensing model,  (which rocks by the way).  We are looking good so far.

P.S.  Good work Jon.  Might want to check on licensing models and type of licesne files used as Sym Ed licesnes are ok (at least in my dev environment)

0
Login to vote
jon_sharp's picture

Thanks for the information everyone. We're working as quickly as possible to get this resolved. I'll update this post when I have more information.

Thank you for your patience!

Sr. Product Manager
Endpoint Management and Mobility Group
Symantec Corp.

+1
Login to vote
plit's picture

Issue have been resolved. New PL file have been uploaded to SolutionSam.

open SIM >
Go to Settings >
Update SIM PL - "Click Update Now" >
After This back to main SIM select "Add/Update licenses" >
Verify that no "Deployment Solution HF1 Trial Licenses" are listed.
 

+1
Login to vote
mabdelnabi's picture

Done that but still showing the same thing. Tried restarting couple of times but still no go.

0
Login to vote
dcgarbutt's picture

I never had an issue with applying licenses within Symantec Installation Manager.

The error that myself and Andy are experiencing can be seen from the First Time setup portal.  This is caused by the ProductGuid in the Product table being modified by Deployment Solution 7.5 HF1...

Anyway, support on working on this and hopefully we'll have a KB/HF1.1 soon?

David.

David Garbutt

0
Login to vote
SK's picture

So HF1 has a new ProductGuid for DS, yes?

If this is the actual cause, then you could simply update the relevant row in that table with the previous guid as a quick work around; however, if the error only occurs from the FTS page, then I would probably wait for an official fix as all those items can be accessed from other areas within the console.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

0
Login to vote
dcgarbutt's picture

Yes - Just waiting for an official "fix" or valid workaround from Symantec Support such as reverting the productguid in the product table.

In the meantime:  http://www.symantec.com/docs/HOWTO9763

This issue kills off Deployment Solution altogether whenever you have:  More than the 10 eval nodes OR the trial license period expires.

So right now I'm completely dead with Deployment Solution in this environment - with a deadline looming to have this functional.

My advice:

Don't apply DS HF1 if you haven't already done so.  If you have, roll back - if you can....

David Garbutt

0
Login to vote
Guido Langendorff's picture

So, these HF's were created/tested/released before Symantec 4.0?

0
Login to vote
Thomas Baird's picture

So guys, you need to know a few details.

First, the "fix" to the PL that is supposed to correct this issue only corrects where the license appears in the SIM.  If you think about it logically, the PL only controls what is listed when the SIM runs.  Where this the only place the issue occurred though, then the license check would never list the product.  Translation, it's also in the DB, so fixing the PL fixes only what appears in the SIM.

In the DB, the product is still listed.

That said, a closer inspection will show you that there are two DS products listed.  One will have your normal licenses applied and work.  The other is the "new" bogus product that shouldn't have appeared at all.

As for functionality, we need to check what is causing the problems if/when the licenses expire.  I've personally spoken with and worked with  customers who are fully functional both in excess of that license count AND post expiration of those licenses.  We ran several tests on it.  If DS is "down" we need to do more checking on why and I recommend logging a case to find out.  I'm not saying the license did NOT affect you, just that for the majority of people I've worked with, it has not.

For all others reading this thread, please note that there are essentially 3-4 issues that you may see with this, that are MOSTLY cosmetic:

  • Originally, you'd see a new product in the SIM.  This is resolved for anyone currently downloading the HF.
  • On the First Time Setup page, you'll see a new product along-side the old product with either an functional or expired trial license.
  • In the logs, every 30 minutes by default, any system above 10 that you have will "fail to obtain a license" on our regular license check for this product.

You should not see any other issues.

NOTE: For those who are executing deployment "jobs" and get a license error, do a bit more checking.  First, see if you have a quick-delivery task included and see if removing that helps.  Second, see if you can boot a system into automation and JUST run a deploy image task, no job, just a task.  Third, try a copy-file task in production and in automation.  IF this license issue is the source of those problems, you wont be able to even schedule a job against these clients.  Quick-run tasks will "start" and immediately fail, but if you try to schedule (or drag the task to a client, which kicks open the schedule screen) it should fail before you can even schedule it.  IF the license is an issue.  If not though, it'll attempt to run and fail for a different reason.  Finally, if you confirm a license issue, call us.  Don't wait for a fix.  Let us know so we an get you up and running!

Thomas Baird
Enthusiast for making things better!

 

0
Login to vote