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

Altiris 7.1 SP2 MP1 released

Created: 03 Oct 2012 • Updated: 29 Nov 2012 • 96 comments
Pascal KOTTE's picture
+12 12 Votes
Login to vote

2012-10-03: From news on Anthony P. blog an available release MP1 for the SP2. Reviewed 2012-10-26. Re-Reviewed 2012-11-21.

Before upgrading, you must also check this article, can change in the time and obosolete this blog a little:

http://www.symantec.com/docs/TECH197966

IT Management Suite 7.1 SP2 MP1 Release Notes

here it is: http://www.symantec.com/docs/DOC6052

and the IT Management Suite 7.1 SP2 MP1.1 Release Notes

http://www.symantec.com/docs/DOC5955

Notice: You should install the MP1.1, that is including all MP1 (do not install MP1 for installing MP1.1)

Important: If you already installed version MP1, MP1.1 will install only the fix described in TECH198556.

Notice 2: already Rollup are there also (must ask it to support if required) - Thanks to tell me, and if others :)

SMP 7.1 SP2 MP1 Rollup Version 1 Information Notes

   |  Created: 2012-10-31  |  Updated: 2012-11-08  |  Article URL http://www.symantec.com/docs/HOWTO81832

This is a good news, with about 20 pages of fixes, and I find a few we currently know our side, such problems with SP2, we were thinking about requesting a rollup v4 to Symantec support...

Is it my own? Am I alone to feel the "Symantec Quality/stability" is going a little bit down, (all the same I make an abstract of the nice "beta" version 7.0 ITMS, should never deploy in production) ? I hope this MP1+MP1.1 will stronger the Altiris platorm. Perhaps some relation the Altiris development moved from Australia to India+Lituanie in 2011?

Please Symantec: here some suggestions:enlightened

  1. Simplify
  2. Improve the platform strength: better testing ? better tuning ? Reduce internal complexity !
  3. Force "other extensions" respecting the standard "interface" and user presentation
    (like Mobile Management creating a type "Mobile", but no view "vMobile" ! no)
  4. Organize Symantec support to concentrate all incidents a "same" installation in a single support session,
    instead of spreading multiple tickets and support contacts !
  5. ...

We need being able to rely on SMP: Simplify and tune the base processing, for reliability, strength, performance and ergonomy. It is difficult to build stable solution, on a platform consumming such support time for simply maintaining it operationnal.

Thanks reading this, and answer me your own personal feeling about. 

Here the process to install MP1 (or MP1.1)

  1. backup the full server + dump of the base... In case of!
    ALSO: create a "support package" (SIM > [Settings] > [Create a support package]) to collect current versions & logs state... In case of!
  2. You log on SMP server with the previous installation "service account",
    (and with all extended SQL sysadmin righs into the SQL instance (not only the Symantec_CMDB base)
  3. SIM auto-upgrading to 7.1.238 (http://www.symantec.com/docs/HOWTO80647)

You must go on SIM "Run as Admin" (update the products.pl.xml):
Notice: SIM will auto-upgrade and switch to a new Products List: http://www.solutionsam.com/solutions/pl/symantec_v2.pl.xml.zip

You should see this as an uprade, and you will see:

New option for being able to upgrade the version you'll prefer, that's cool, thanks Symantec. yes
See more here: https://www-secure.symantec.com/connect/videos/basic-walk-through-new-sim-upgrade-process-video

Plan a 2-3 hours maintenance, with services stopped. So plan a 8h maintenance in case of "Rollback".

  1. Stop IIS (as suggested in comment)
  2. Check step ask for removing ASDK: proceed using the provide link => NOTICE: this is stopping AexSVC NSE processing.
    (Don't search how/where to get the new version, it is inside the SMP now: Why removing not integrated? Mystery!)
  3. Warning Workflow will not be updated 
    (nothing about in the release note install process. Why upgrade not integrated? Not a mystery, reducing damage risk custom workflows!)
  4. Can have an Internet Warning about crl.microsoft.com cannot access: can bypass (probably firewall protection blocking, all the same proxy provided) use the link to fix (disabling this check)
  5. If using HIERARCHY: carefull procced as HOWTO44016 or http://symantec.com/docs/HOWTO21657 
    (unplug, update childs 1st, update parents, re-plug)
  6. Check you SQL server not in mode "full" for a "disk overload because of the LOG file growing a big lot", switch in mode simple
    (that is not in the best practice KB, this should be added from my point of view. Upgrade crashes because of SQL log disk over space)
  7. Restart the server, and check the logs and check errors.
    ALSO: REcreate a new "support package" (SIM > [Settings] > [Create a support package]) to collect current versions & logs state... In case of!

For our current install: CMS + AMS (no SMS) here the update list below:

Symantec Management Platform 7.1 SP2 MP1 (7.1.8400)
Activity Center 7.1 SP2 MP1 (7.1.7858)
Altiris CMDB Solution 7.1 SP2 MP1 (7.1.7858)
Altiris Asset Management Solution 7.1 SP2 MP1 (7.1.7858)
Altiris Asset Management Suite 7.1 SP2 MP1 (7.1.33)
Symantec Barcode Solution 7.1 SP2 MP1 (7.1.1230)
Altiris IT Analytics Client Server Management Pack 7.1 SP2 (7.1.2060) (already installed)
Altiris Real-Time Console Infrastructure 7.1 SP2 (7.1.7580) (already installed)
First Time Setup Portal 7.1 SP2 (7.1.7580) (already installed)
Altiris Patch Management Solution 7.1 SP2 MP1 (7.1.7858)
Altiris Patch Management Solution for Windows 7.1 SP2 MP1 (7.1.7858)
Altiris Patch Management Solution for Linux 7.1 SP2 MP1 (7.1.7858)
Altiris Patch Management Solution for Mac 7.1 SP2 (7.1.7580) (already installed)
Altiris Client Management Suite 7.1 SP2 MP1 (7.1.33)
Altiris Event Console 7.1 SP2 (7.1.7580) (already installed)
Altiris Inventory Solution 7.1 SP2 MP1 (7.1.7858)
Altiris Software Catalog Data Provider 7.1 SP2 (7.1.7580) (already installed)
Altiris Inventory for Network Devices 7.1 SP2 (7.1.7580) (already installed)
Altiris Out-of-Band Management 7.1 SP2 (7.1.7580) (already installed)
Altiris Software Management Solution 7.1 SP2 MP1 (7.1.7858)
Altiris Power Scheme Task 7.1 SP2 (7.1.1304) (already installed)
Symantec pcAnywhere Solution 12.6.7 (12.6.8096) (already installed)
Altiris Client Management Suite Portal Page (7.1.1005) (already installed)
Altiris Real-Time System Manager 7.1 SP2 (7.1.7580) (already installed)
Wise Connector 7.1 SP2 (7.1.7580) (already installed)
Symantec Endpoint Protection Integration Component 7.1 SP2 (7.1.1037) (already installed)
Altiris IT Analytics Symantec Endpoint Protection Pack 7.1 SP2 (7.1.2060) (already installed)
Altiris Deployment Solution Complete Suite 7.1 SP2 MP1 (7.1.7858)
Altiris Deployment Solution Linux Support 7.1 SP2 MP1 (7.1.7858)
Altiris Deployment Solution WinPE Support 7.1 SP2 MP1 (7.1.7858)
Altiris Deployment Solution Core 7.1 SP2 MP1 (7.1.7858)
Altiris Deployment Solution with Winpe Support 7.1 SP2 MP1 (7.1.7858)
Migration 7.1 SP2 MP1 (7.1.8400)
  • For the time duration and the download size: Can vary a LOT, about 3 hours in our case, and 2,5 GB !
  • I put PCA in bold above, be carefull if you do not apply the latest PCA update, you can be in the previous release, and the crypting is changing. So if you are not already 8096 build, you will have surprise: no backward compatibility, must wait all client updated for remote control back. (keep a PC not updated as a temp helpdesk console, or a VM or a TS)

Post-install process

   Review

  • Check logs Altiris, review erors, fix or escalate those recurents. (Or keep open in your "known not critical? error list")
  • From Windows scheduled task run daily at night (not all a time but in the planning order, 1h, 2h, 3h10): fix or escalate recurents.
  • Repeat for weekly task (I don't think existing monthly?)
  • Go to CONSOLE web: open each "portal", verify no error display & altiris logs
  • CONSOLE: open "Computer" + "tasks" + "Policies" + "Software": and all OK.
  • CONSOLE: open all settings, expand all, click on each and verify no error.
  • More tricky: see if not any missing item... For the one you well know by heart.
    (I ask Support for a check missing or not updated items reports, still wait a solution)

   Cleaning

  • ZIP install logs, move a safe place, delete.
  • empty %temp% system one, and altiris running account one. (ccleaner is nice)
  • If physical machine: Defrag, if virtual, some told me useless to defrag... ???
  • Perform a database defragment of the Symantec CMDB Database (see HOWTO8589) [no LOG files problem if you follow my 1st recommend]
  • For those using DS 7.1 (and not any more DS 6.9, not sure a good Idea): Move FIRM.EXE into the correct location per TECH198111

   Workfow updating

  • see http://www.symantec.com/docs/HOWTO61681,
  • as you are on the server, just look under <YourAltirisNSinstallPath>\Workflow\Web\Agent,
  • This is upgrading EXE/DLL (Altiris\Workflow\Tools) from 7.1.1400 to build 7.1.1500 (except ThemeEditor.exe)

   Settings & agents/plugins review

Most of the time, install deactivate the upgrade process of plugins, and (re)activate a few undesired policies:

  • I do not check for this MP1, as I deactivate my own, before, all plugins upgrade policies.
  • Try to avoid upgrading any plugins on a "not upgraded" SMP/NS base agent.
  • Check on a pilot part, can be a good Idea before overall... Myself, I deploy all plugins at once, but only on pilot machines (30 computers in PROD).
    (I deploy once a time when deploy "new" plugins)
  • (RE)DEACTIVATE: The legacies policies: legacy task, and worst legacy Windows package server agent upgrade
    (See in advanced Site server settings under Notification server):

If you reinstall a server with a previous NS6 package/task server, all the same "removed" NS6 agent, can have some surprise when your server auto-upgrade as a site server, and replicate all packages local disk. Hope not installed agent on C drive your server, that is a very bad Idea, especialy if C drive not enough space for all packages... And your server the company file server... Your upgrade will have some visible bad results... crying You can laugh, I do that already, not a pleasure.

... any addition feedback? You are welcome :)

Comments 96 CommentsJump to latest comment

Pascal KOTTE's picture

Symantec support confirm soon availability, end this week :)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
KSchroeder's picture

We're weeks away from rolling out to production, so I'm tempted to install this first, but don't want to be the guinea pig! Then of course 7.5 coming early December...

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

-1
Login to vote
Pascal KOTTE's picture

Ready to go, start it.

Honnesty, I am not sure all the users of a standard SP2, we are already "guinea pig" cheeky

I do not see yet if some our surprising new bugs, like

* save script output, gives tasks allways success: is solved in this release. 

But we have a few more or less small problems, and I don't feel a bad Idea to update. Any way: If we want to escalate any problem or bug to Symantec support, I guess the MP1 installation will be one of the 1st support question...

Yes, I still escalated bugs to Symantec support, all the same the time this is consumming.

I will keep you updated what result we have :)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-5
Login to vote
Pascal KOTTE's picture

Hum, we do the "guinea pig", don't laught :(

We currently cycle the install at 66%, configuring: 1 of 40 tasks, Tasks cycling displaying: 3 threads ID

  • TID 6: Configuring task 14 of 40: Configuring SoftwareManagement... (all 5 seconds)
  • TID 17: (same)
  • TID 11: (same)

TID 69: SIM: cycling on:

  • configuring task 14 of 40: Configuring SoftwareManagement - Import items - Symantec

Previously TID 69 was successfull on: (reverse time order)

  • Configuring task 14 of 40: Configuring SoftwareManagement - Import items - Software Package Contains Software Installation file
  • Configuring task 14 of 40: Configuring SoftwareManagement - Installing Resource Management - Installing resource types - Software Package 
  • Configuring task 14 of 40: Configuring SoftwareManagement - Installing Resource Management - Installing resource types - Windows Script Installation File
  • Configuring task 14 of 40: Configuring SoftwareManagement - Installing Resource Management - Installing resource types - EXE software Installation file
  • ...

start cycling at 14h12 CEST, still cycle 18h05 :( 

Wait for call support, but plan a reboot the SQL server, + Altiris server + redo...

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+7
Login to vote
Pascal KOTTE's picture

Before upgrading see the number of Software Components

select COUNT(*) AS 'Total SoftwareComponent items'
from vSoftwarecomponent
For 30290 in our case, this was taking more 6 hours to update this part.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+3
Login to vote
Pascal KOTTE's picture

Hey I do another MP1 update, near 50'000 software components, Not taking such a long time: I suspect SQL maintenance default on the previous SQL... 

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Pascal KOTTE's picture

Hum, curious, I was thinking I was already install the MP1 My LAB, but in fact it was installing the sp2b... I do not see any more the MP1 update from my LAB ?? Symantec retire the MP1 now. Too much problem ?

We will see.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-1
Login to vote
Mark Jn's picture

Just checked. MP1 is still on solutionsam. What PL file name do you use?

-9
Login to vote
Pascal KOTTE's picture

http://www.solutionsam.com/solutions/pl/symantec.p...

and the last change date is: 3 october 2012 5h37 (CEST)

still not propose any upgrade... I will check thos file URL and result from different locations, perhaps an internet "cache" effect. (are Symantec using Akamai or similar workwide cache solution?)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Dmitri_Gornev's picture

Hi Pascal,

please note that switch to another PL happens on upgrade to MP1 - this is http://www.solutionsam.com/solutions/pl/symantec_v2.pl.xml.zip. Original PL doesn't contain MP1 items, it only asks SIM to upgrade to the latest version and new SIM does the switching.

+1
Login to vote
Pascal KOTTE's picture

Yes, that was the problem my LAB ? I was having to switch this new PL manualy :( Why me ?

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Pascal KOTTE's picture

Great, in fact we were having to be very PATIENT - The upgrade is working after a very long time to work on the "SoftwareComponent" table: 

select * from vSoftwareComponent 

was not answering any more and fall in timeout during this condiguration stage 14 of 40 of SoftwareManagement... 

Starting at 14h, finishing at 20h => taking more 6 hours to proceed. (the SQL server seems not overloading CPU or DISK, but limited 8GB RAM: Not sure more RAM or better disks could accelerate this process)

But for sure, because of the patch management and all the software we got currently a total: near 30300 Software components.

I do not remember the upgrade from 7.0 to 7.1 was taking such a long time... A huge "MP" it is !!

So DON'T PANIC, and be as we were, patient, and resisting to click "Cancel". Plan this as we were doing: before a week-end :)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+3
Login to vote
Ch@gGynelL_12's picture

I hope this release would be perfect!

-1
Login to vote
SharkSmart's picture

I'd urge some caution with this release if you make extensive use of AD Imports from groups.

In my testing I found that all of a computers rows in the Inv_Security_Groups table were removed and replaced each time a rule ran.  That table is used by the filters the AD Import rule creates so this affects software delivery and what-ever else you use AD Imports from AD Security groups for.

For example:

Workstation1 - member of AD Security groups "Group 1" & "Group 2"

AD Import Rule 1 - Imports "Group 1"

AD Import Rule 2 - Imports "Group 2" 

  1. Trigger an Update Import of AD Import Rule 1
  2. Refresh SMP filters for "Group 1" & "Group 2"
  3. Workstation1 is only a member of filter "Group 1"
  4. Trigger an Update Import of AD Import Rule 2
  5. Refresh SMP filters for "Group 1" & "Group 2"
  6. Workstation1 is now only a member of filter "Group 2"

So if you have more than one AD Import rule importing groups the last rule to run will over-write any other previous imports of security groups - for computers in that last rule (if that makes sense).

Can anyone else confirm they are seeing this?  I see no errors in the logs on imports.

Please "Mark as Solution" those posts which resolve your problem - its a free way to give something back to those who contribute their time and knowledge to these forums.

+1
Login to vote
Pascal KOTTE's picture

Hi, did you open a Symantec case for a bug confirmation ? If not, you should. :) Not sure I have cases with that, but for sure, we were planning building similar. So very interested in following the result of that.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
SharkSmart's picture

Yes a case has been logged with Symantec.  I just thought it would be best to warn others about this one as its not an immediately obvious issue.

I know of several implementation that use AD groups as the source of truth for software delivery.  The import of these AD groups is often split over several import rules.  Any such implementations would be badly affected by this.

Please "Mark as Solution" those posts which resolve your problem - its a free way to give something back to those who contribute their time and knowledge to these forums.

+1
Login to vote
Pascal KOTTE's picture

Thanks a lot for the Warning

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
SharkSmart's picture

Symantec Support have confirmed they can reproduce this.  No word yet on a fix.

So a warning to anyone looking to install this - if you have multiple import rules for AD Groups this MP1 release could cause problems with your existing configuration.  You could consolidate all the security group imports into one import rule or wait for a fix from Symantec.

Please "Mark as Solution" those posts which resolve your problem - its a free way to give something back to those who contribute their time and knowledge to these forums.

+5
Login to vote
Mark Jn's picture

I agree it looks like an issue but it is by current design. Please feel free to report the incident.

But AD import in MP1 still has big advantages comparing to original SP2.

-1
Login to vote
andykn101's picture

What are those advantages? We use AD import for computers and it works well.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

-1
Login to vote
dcuoq's picture

I can't upgrade my CMS to the last 7.1 SP2 MR1 because this last version is not compatible for Altiris Recovery Solution 7.1.3919.

I hope that Symantec will make an update for Recovery Solution.

Cordialement | Best Regards
DAVID CUOQ
Coordinateur Technique Micro-Informatique
a-SIS

+1
Login to vote
Pascal KOTTE's picture

Too bad... I check regarding the Mobile Management Solution: It is supported and update a SP2 for MMS. I run one (other) MP1 ITMS + SP2 MMS currenctly, I will keep updated the result :)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-1
Login to vote
Damon_Covey's picture

There was an issue in the initial MP1 release which caused Recovery Solution to be uninstalled. We are currently finalizing an updated MP1 which is slated to release early next week which will resolve the issue for Recovery Solution being forced to uninstall. 

Please note that Altiris Recovery Solution is an End of Life product that has not been certified with 7.1 SP2 MP1. While it is likely that Recovery Solution will work properly with the application of MP1, verification in a pre-production environment is strongly recommended before applying MP1 in a production environment if you intend to continue the use of Recovery Solution.

Best Regards,

Damon

+5
Login to vote
Antti's picture

Hi

We ran into some problems with SP2 MP1 update. Installation itself went through fine (Altough it lasted quite long, several hours). Our PXE environment worked fine before update but now for some reason we can´t get computers to boot into PXE. Were currently rebuilding the PXE environment and I´ll try to report back when we have more information.

-7
Login to vote
Antti's picture

Rebuild made no difference.
PXE fault was due to missing sbsmtftp.exe file. This was due to update (nothing else done at the server between tests) file was recovered from backup and now tftp service starts ok (file is dated before update). I´ll try a basic image deploy tomorrow via PXE. Second site where we do some maintenance, the customer also made the update and there the whole deploy side dropped. Support has tried to sort that during the day (as far as i know) with no luck. 

In our own environment "manage computers" search option is some how not working. For example a f-secure program is reported to be installed on 100 computers but in reality software is installed only 40 computers. list includes few computers that are manually cleaned from all f-secure stuff.

+1
Login to vote
Pascal KOTTE's picture

I feel happy I was telling my migrated customer keeping the DS 6.9 for the Win7 migration, instead of moving on DS 7.1... Thanks for your sharing those information.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
andykn101's picture

Me too. Lets hope DS 6.9 support Windows 8 soon.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

-1
Login to vote
Pascal KOTTE's picture

see also, for those using DS 7.1:

https://www-secure.symantec.com/connect/forums/mp1-broke-imaging-anyone-else

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-5
Login to vote
Pascal KOTTE's picture

I add the part for Workflow server upgrading (from build 1400 to 1500), must go console Manage/Workfows, but useless to download again, already on the server, go to folder

<Altiris>\Workflow\Web\Agent

Run the Symantec.Workflow.Setup.exe, must be version 7.1.1500.2056... 

Why not auto-executed ? Just have a chance to avoid loosing yours :)

If you build your own workflows, and don't want loosing them just have a look there: http://www.symantec.com/docs/HOWTO44050

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+5
Login to vote
Viswa123's picture

Good to see lot of fixes,but I'm not sure whether it will resolve the performance issue with software portal 7.1

With regards,

Viswanath Sampath

Thanks & Regards,

Viswanath Sampath

http://www.linkedin.com/in/viswanathsampath

-1
Login to vote
Pascal KOTTE's picture

1st feedback my 1st customer, console goes quicker ! Don't know which part... But in the release notes, ther is a lot "improve performance"... But I think we still are not able to "import" a software component :(

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Carsten Giese's picture

Here is a small script to import XML-files from an exported Software Resources:

Import_SoftwareResource.zip
http://www55.zippyshare.com/v/35815724/file.html

+3
Login to vote
shrishail.jivani's picture

Symantec Management Platform 7.1 SP2 MP1 released, there are 170+ major fixes. I have upgraded to SP2 MP1 and it looks improved a lot and console much faster!!!

+3
Login to vote
Pascal KOTTE's picture

Results both upgrade keep or extend, a ton of:

Unable to find node named "statusEvt". Found node "" instead

Curiously I got a serious problem another part: 

The "Software Management Solution Upgrade" policy is just missing in the console, can search no way, not just moved another place, the GUID not in the vItem... 

I try a repair: no better result :(

Here the current agent version we deploy on pilot clients: The last red should be 7.1.7858, as others :(

Altiris Agent (Version=7.1.15400.8400)
Altiris Software Update Agent (Version=7.1.7858)
Altiris Application Metering Agent (Version=7.1.7858)
Altiris Base Task Handlers (Version=7.1.15400)
Altiris Client Task Agent (Version=7.1.15400)
Altiris Client Task Scheduling Agent (Version=7.1.15400)
Altiris Inventory Agent (Version=7.1.7858)
Inventory Rule Agent (Version=7.1.8400)
Symantec pcAnywhere Agent (Version=12.6.8096)
Software Management Framework Agent (Version=7.1.8400)
Software Delivery Results Pickup Agent (Version=7.1.7858)
Software Management Solution Agent (Version=7.1.1443)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+3
Login to vote
shrishail.jivani's picture

Oh,really. I did't face Software Management Solution Agent issue, it has been upgarded to 7.1.7858, but i observed Server inventory solution for windows removed from console.

I think this had happened because of Software Management Solution Agent (Version=7.1.1443) which was oldest version. Recent version was 7.1.7580 before 7.1.7858, I think, if you upgarde on oldest version i.e 7.1.1443 it may remove it from console. What was the vesion of inventory or patch or Application Meterin?.Is that same 7.1.1443 or 7.1.7580??

--> Anyone observed Deployment Solution Plug-in default filters have not updated machine names[“Computer with latest deployment plug-in installed in windows (x86)” and “Computer with latest deployment plug-in installed in windows (x64)”]. In these filters they have put build number >=2316 which was latest version of deployment solution. After migration of Altiris 7.1 SP2 MP1, deployment solution build number has been changed from 2316 to 7858.

Now issues is, the filter “Computers requiring Deployment Plug-in upgrade on Windows (x86)” and “Computers requiring Deployment Plug-in upgrade on Windows (x64)” have not updated computer names in these two filters because of build number condition >=2316 instead of  >2316

Here we need to clone it default filter and remove the ' = ' sign from cloned filters then we can able to resolve this issue. Anyone different idea??.

+2
Login to vote
Scott W. Allen's picture

shrishail, did you find a better solution than cloing “Computers requiring Deployment Plug-in upgrade on Windows (x86)” and “Computers requiring Deployment Plug-in upgrade on Windows (x64)”?

Scott

-3
Login to vote
shrishail.jivani's picture

Hello  Swallen,

No, Are you facing same issue in your environment. Please let me know if you have any other solution.Thanks!!

-3
Login to vote
shrishail.jivani's picture

Oh,really. I did't face Software Management Solution Agent issue, it has been upgarded to 7.1.7858, but i observed Server inventory solution for windows removed from console.

I think this had happened because of Software Management Solution Agent (Version=7.1.1443) which was oldest version. Recent version was 7.1.7580 before 7.1.7858, I think, if you upgarde on oldest version i.e 7.1.1443 it may remove it from console. What was the vesion of inventory or patch or Application Meterin?.Is that same 7.1.1443 or 7.1.7580??

--> Anyone observed Deployment Solution Plug-in default filters have not updated machine names[“Computer with latest deployment plug-in installed in windows (x86)” and “Computer with latest deployment plug-in installed in windows (x64)”]. In these filters they have put build number >=2316 which was latest version of deployment solution. After migration of Altiris 7.1 SP2 MP1, deployment solution build number has been changed from 2316 to 7858.

Now issues is, the filter “Computers requiring Deployment Plug-in upgrade on Windows (x86)” and “Computers requiring Deployment Plug-in upgrade on Windows (x64)” have not updated computer names in these two filters because of build number condition >=2316 instead of  >2316

Here we need to clone it default filter and remove the ' = ' sign from cloned filters then we can able to resolve this issue.

Anyone have different idea??.

+1
Login to vote
Pascal KOTTE's picture

Hi. try the (open an Admin CMD, change path to your bin at Notification server folderm and run:

AexConfig /configureall

, and please let us know the result... I seel also some missing updated Filters in one our MP1 deployment, I will check more and update here.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
JaredSeth's picture

Pascal,
For what it's worth, I've applied this to two servers so far (I'll be doing three more this weekend) and both still have the Software Management Solution Plug-in Upgrade policies intact.

+1
Login to vote
Pascal KOTTE's picture

Thanks your post, yes I got another MP1 install with a Soft.Manage plugin upgrade intact also.

That is for just this upgraded site: I will try a trick just gived Danijal at Symantec Support:

  • AexConfig /reconfigureall

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
Ilmar's picture

Hi!

Software Management Solution can be repaired by following way:

Run CMD.EXE as administrator.

Go to Altiris\Notification Server\Bin folder and Run AeXConfig /configure <path to product installation file>.

Example for Software Management

AeXConfig /configure ""C:\Program Files\Altiris\SoftwareManagementSolution\Config\SoftwareManagementSolutin.config"

Restart Symantec Management Console.

+1
Login to vote
dsmith1954's picture

Man, what a pain. Altiris 6 wasn't this bad. As for Client Management, we'll be sticking with Deployment Server 6.9. smiley

As for Windows 8 support, who cares? Windows 8 is so ugly and unusable that we'll probably skip it like we did Vista. Windows 7 will be supported for another 5-10 years anyway. Why go to Windows 8?

+1
Login to vote
Pascal KOTTE's picture

I see immediat 2 following main reasons, but not last:

  • Because Windows 8 will also support application design for Mobile, on desktops.
  • From November, most new OEM/public pre-installed systems will be version 8 native. 

So public will push their own companies to version 8.

History: For 2000 to XP migration, end-users was'nt care about this migration managed from IT.

Now: with Windows 7, IOS, Android, Windows 8: end-users are back their IT with: "When will you updated? we are late, I am Windows 8 at home from 6 monthes" (next year...:)

I am thinking all companies ending Win7 migration, will start integrating Windows 8 less than 3 years after.

The world is moving, just hope more good than bad :)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
dsmith1954's picture

None of our users have Windows Mobile devices, so they won't care about having Windows 8.

Everyone I've shown it to thinks it's so butt-ugly that they don't want it. What used to only take 3 clicks, now takes 5-6. Just not usable in my opinion.

We have an Enterprise Agreement, so we'd be able to stay on Windows 7 as long as we need to. If they don't sell downgrade rights for our business units that don't fall under the EA, we'll be force to endure that, or maybe move to Linux or Crapple.

We can always put Linux on the desktop and use Citrix for apps. That way there'd be no need to look at that ugly UI.

I could be wrong, but I don't think there will be many people asking for Windows 8, at least not in our part of the world.

+1
Login to vote
JaredSeth's picture

We've got some business units that are contractually obligated to be running Windows 8 within 90 days of official release, so we'll be supporting it on new devices pretty quickly. Whether we'll upgrade existing systems is another matter altogether and still a subject of debate here.

That aside, I'm inclined to agree with Pascal that we'll have users clamoring for it in short order once they start buying home systems with Windows 8 pre-installed. (Heck, I'm looking forward to a Win8 tablet and being able to do Altiris console work from pretty much anywhere.)

+1
Login to vote
dlopes's picture

I updated my SIM to 7.1.238 and still no updates for 7.1 SP2 MP1 are shown in my updates...

Is it officially released?

Regards,

Daniel Lopes de Oliveira
Technical Team Leader - Endpoint Management & Mobility

+3
Login to vote
Pascal KOTTE's picture

check your source PL file in SIM settings

must switch to

http://www.solutionsam.com/solutions/pl/symantec_v2.pl.xml.zip

normaly, the auto-upgrade of SIM does the switch, but in my LAB, it was not the case, and must manual edit a new product list file, to add on the previous default:

http://www.solutionsam.com/solutions/pl/symantec.pl.xml.zip

not having the MP1

Why this way ? Ask for Symantec... 

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
Pascal KOTTE's picture

Here the version of the agents/plugins after MP1, except the Soft.Manage we got an upgrade problem for...

For the Soft.Manage solution agent: should be, guess it ?

  • 7.1.7858 wink

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+3
Login to vote
Pascal KOTTE's picture

I find something strange, see also

https://www-secure.symantec.com/connect/forums/bug-or-bug-did-you-have-some-your-w2003-clients-updating-their-plugins-base-agent

There is a missing system filter for "Updated Base NS agent's computers" with the "current build"...

And the filter: Windows Computers Requiring Symantec Management Agent Upgrade

Does display a random result... see this post in link.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+5
Login to vote
Stefan S.'s picture

It looks like I have the same problem with the Software Management Solution Plug-in Upgrade but not only that it seems like I have a problem with the Install too and also with the Software Update Plug-in Upgrade.

If I check the Upgrade Policy I find the packageGuid {00000000-0000-0000-0000-000000000000}

If I check the install policy I find the packageguid {3a7fb8b2-1c34-4b9a-a742-e811fca07ba4} which also seems to be missing on the server.

I have created I case with Support and will see what they come back with.

@Pascal: What package guid does it show in your upgrade / install policy?

+7
Login to vote
shrishail.jivani's picture

Hello Stefan,

I could see packageGuid {21cba955-d604-452e-bae4-9c30eea303f1}
for software Management solution task plug-in upgarde. Please find the attached screenshot. It's works nicely for my environment.

SWD_Upgrade.png
-1
Login to vote
Stefan S.'s picture

As a matter of fact the software management solution agent was also on 7.1.1443 on my NS. Here plug-ins on the NS before MP1 upgrade:

and after MP1:

Support then told my I have to fix the plug-ins first on Parent and Child NS and on Site Server before the plug-in upgrade will work. I did a "manual" remove and install of the plug-in which worked. But still neither the install or the upgrade policy works.

The problem might only occur for those who upgraded from a certain rollup. This infrastructure was on rollup v4 and we had some other point-fixes installed.

At least it seems conistent in the way that none of the plug-in works.

I have tried also the repair which was mentioned earlier:

Example for Software Management

AeXConfig /configure ""C:\Program Files\Altiris\SoftwareManagementSolution\Config\SoftwareManagementSolutin.config"

During the repair I can see 2 warnings:

So actually I am not so surprised that it does not work.

I have not tried the /configureall yet but maybe that is the next step. First I will try again with Support with my open case....

+1
Login to vote
Pascal KOTTE's picture

We got same issue one our MP1. Was a previous sp2b standard, not any rollup applied, except the fix

KNOWN ISSUE: Specific NSE files from clients are not processing. These NSE become stale and never process. Article:TECH195347

As I see, the 7.1.1443 is the SP1 version, not the sp2 or sp2b version for Software Management plugins. So you perhaps got a similar issue during the sp1 to sp2 process.

Currently, we also see the sytem filter "windows computers requiring Software Management Plug-in upgrade", does not get the correct SQL statement, and filter versions below 1400 instead of 7800, as it is on "correct" MP1 install platform.

Did you have same issue you own filter (below, 1400 should display 7800) ? 

<item guid="{d5441d72-60dc-45a2-b255-a491fb239ede}" classGuid="{aeca2d91-c615-4d99-bad5-612ca159da4f}">

- <!--  Type: Altiris.NS.StandardItems.Collection.NSDataSrcBasedWithExplicitResourceCollection  -->

- <!--    Assembly: Altiris.NS.StandardItems, Version=7.1.8400.0, Culture=neutral, PublicKeyToken=d516cb311cfb6e4f -->

<name>Windows computers requiring Software Management Plug-in upgrade</name>

<alias />

<ownerNSGuid>{57b3b127-d8fc-4645-b0af-dbcbef4f9240}</ownerNSGuid>

<productGuid>{ad3f5980-d9e9-11d3-a318-0008c7a09198}</productGuid>

<itemAttributes>NoReplication, Readonly</itemAttributes>

- <itemLocalizations>

- <culture name="">

<description>All Windows computers that have a version of the Software Management Solution Plug-in that is older than the version available on the Altiris Notification Server.</description>

<name>Windows computers requiring Software Management Plug-in upgrade</name>

</culture>

</itemLocalizations>

<originNS guid="{57b3b127-d8fc-4645-b0af-dbcbef4f9240}" name="GE-SRV-ALTIR02.chopard.world" url="http://GE-SRV-ALTIR02.chopard.world/Altiris/NS/" />

<isManualUpdate>false</isManualUpdate>

<manufacturer />

- <dataSource typeGuid="b29ba3f7-cc80-4988-a341-d8471b05ea1d">

- <configuration>

- <base>

<parameters />

</base>

- <query>

- <![CDATA[

SELECT      c.[Guid]

    FROM  ( SELECT    DISTINCT _ResourceGuid

                FROM  Inv_AeX_AC_Client_Agent

                WHERE [Agent Class Guid] = '43043A36-0302-4375-8086-F7DD368DCADC'   -- Windows Altiris Agent

                AND   [Product Version] LIKE '7.1.%'    -- all  AltirisAgent 7.1 and any SP

                --AND   [Build Number] < ????           -- only AltirisAgent 7.1

          ) AS                      a

    JOIN    vRM_Computer            c ON c.[Guid] = a._ResourceGuid

    JOIN    Inv_AeX_AC_Client_Agent s ON s._ResourceGuid = c.[Guid]

    WHERE   c.IsManaged = 1

    AND     s.[Agent Class Guid] = '6E7FDCA4-E61F-4F5B-BE67-CE6E4E1774E1'     -- Win SMSAgent

    AND   ( s.[Product Version] LIKE '7.0.%' OR                               --    SMSAgent 7.0

           (s.[Product Version] LIKE '7.1.%' AND s.[Build Number] < 1400) )   -- or SMSAgent 7.1

]]>

</query>

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+7
Login to vote
JaredSeth's picture

Stefan,
I'm seeing the same issue (GUIDs on those two plug-in policies are {00000000-0000-0000-0000-000000000000}). Have you heard anything back from Support, before I go and open my own incident? I saw the document linked below about restoring the database from before the upgrade and running a SQL script to fix but I'd really rather not lose all the work we've done in the past week.

-1
Login to vote
JaredSeth's picture

I'm also considering just trying an 'aexconfig /configureall' this weekend, so if you don't hear back from them before Monday I can let you know if that works.

+1
Login to vote
Stefan S.'s picture

I have following query:

SELECT      c.[Guid]
    FROM  ( SELECT    DISTINCT _ResourceGuid
                FROM  Inv_AeX_AC_Client_Agent
                WHERE [Agent Class Guid] = '43043A36-0302-4375-8086-F7DD368DCADC'    -- Windows Altiris Agent
                AND   [Product Version] LIKE '7.1.%'    -- all  AltirisAgent 7.1 and any SP
                --AND   [Build Number] < ????           -- only AltirisAgent 7.1
          ) AS                      a
    JOIN    vRM_Computer            c ON c.[Guid] = a._ResourceGuid
    JOIN    Inv_AeX_AC_Client_Agent s ON s._ResourceGuid = c.[Guid]
    WHERE   c.IsManaged = 1
    AND     s.[Agent Class Guid] = '6E7FDCA4-E61F-4F5B-BE67-CE6E4E1774E1'     -- Win SMSAgent
    AND   ( s.[Product Version] LIKE '7.0.%' OR                               --    SMSAgent 7.0
           (s.[Product Version] LIKE '7.1.%' AND s.[Build Number] < 7581) )    -- or SMSAgent 7.1
 

Which I guess is not fully right either as it should be < 7858

Additionally it seems I face the issue described here:

http://www.symantec.com/docs/TECH190565

I could disable the policies mentioned but I am not able to delete the duplicates because they have the atttribute "nodelete".

I am also waiting for reply from support regarding my findings.

-5
Login to vote
Pascal KOTTE's picture

So you do not have the same curious "not updated" filter like we have on a customer site. We were having the TECH190565 before the Mp1 install, with both Patch & inventory plugins. Not software manage plugin, "funny" after upgrade MP1, solve both, but create this "soft manage" plugin problem.

Except I believe the problem was before in fact, during Sp1 to sp2b process...

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-1
Login to vote
Stefan S.'s picture

I have found an other article TECH155562 and the error seems to be the same I see in the log for the Software Mangagement Solution and for the Software Update agent plug-in. The article suggest to contact the support to receive the fix. So basically I have asked the question and now I am just waiting for a reply....

+1
Login to vote
jobby's picture

Has anyone checked out the Best Practices since yesterday.  Apparently, they left out a step, and after yesterday, there is now another step (step 10) that was added.
 

http://www.symantec.com/business/support/index?page=content&id=TECH197966

Also, they released a known issue along with this added step:

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH198556

Would have been nice to have known this before we started, but its par for the course for them.

-9
Login to vote
dlopes's picture

Darn...

What about a fix for those that don´t have a database backup? Since aparently everything went well...

Regards,

Daniel Oliveira

Daniel Lopes de Oliveira
Technical Team Leader - Endpoint Management & Mobility

-9
Login to vote
jobby's picture

We had a few issues afterwards with that before they released the extra step that matched what the error was.  After a couple of days, they went away, but we were having inconsistencies with computers not matching the correct guids, or computers not showing.  We ran 'aexconfig /configureall' from an administrator command prompt and it fixed all the issues we were having (took about six hours), though we had to reconfigure the items the preinstall best practice said to take note of.

+1
Login to vote
DerikDavis's picture

I have a couple questions regarding installing ITMS 7.1 SP2 MP1.

Do I use the “Upgrade Installed Products” or “Install New Products” option in SIM?

When upgrading to SP2 it was recommended to use the Installed New Products to install SP2 for ITMS.

If I am to use “Upgrade Installed Products” do I pick all the individual products that make up ITMS 7.1 SP2 or do I just pick “Altiris IT Management Suite SP2 MP1”?

Thanks

Derik

-1
Login to vote
Pascal KOTTE's picture
  1. “Upgrade Installed Products”
  2. “Altiris IT Management Suite SP2 MP1”
     

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-3
Login to vote
Stefan S.'s picture

Does anyone know which version the ULM agent should have after the upgrade? I have still 7.1.8282 on my test MAC with OS X 10.6.8.

-1
Login to vote
Andrei Fedulin's picture

As I know MP1 doesn't include any updates for ULM agent. So it should stay as before upgrade

+1
Login to vote
Stefan S.'s picture

The Software Management Solution Agent seemed to have an update:

.\Notification Server\NSCap\bin\UNIX\Software Management\Mac\universal

smsagent"
pb_product_revision="7.1.7858"

pb_product_builddate="Tue Sep 25 23:08:13 MDT 2012"

That is why I was wondering if there was an update for ULM agent. The date of the Altiris Agent files are from November 2011.

-1
Login to vote
Pascal KOTTE's picture

I think all new stuff for Macintosh are in the next 7.5, as I see in WTS 2012 last week.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-7
Login to vote
DerikDavis's picture

Is there a list of the versions for all the Agent/Plug-ins for ITMS 7.1 SP2 MP1?

Thanks
Derik

+1
Login to vote
andykn101's picture

CMS 7.1 SP2 MP1 contains:

  • Symantec Installation Manager (7.1.238)
  • Symantec Management Platform 7.1 SP2 MP1 (7.1.8400)
  • Altiris Real-Time Console Infrastructure 7.1 SP2 (7.1.7580)
  • First Time Setup Portal 7.1 SP2 (7.1.7580)
  • Symantec Management Platform 7.1 SP1 (7.1.6851)
  • Altiris Patch Management Solution 7.1 SP2 MP1 (7.1.7858)
  • Altiris Patch Management Solution for Windows 7.1 SP2 MP1 (7.1.7858)
  • Altiris Patch Management Solution for Linux 7.1 SP2 MP1 (7.1.7858)
  • Altiris Patch Management Solution for Mac 7.1 SP2 (7.1.7580)
  • Symantec Management Agent for UNIX, Linux and Mac 7.1 SP1 (7.1.6851)
  • Altiris IT Analytics 7.1 SP2 (7.1.2060)
  • Altiris Client Management Suite 7.1 SP2 MP1 (7.1.33)
  • Altiris Event Console 7.1 SP2 (7.1.7580)
  • Altiris Inventory Solution 7.1 SP2 MP1 (7.1.7858)
  • Altiris Software Catalog Data Provider 7.1 SP2 (7.1.7580)
  • Altiris Inventory for Network Devices 7.1 SP2 (7.1.7580)
  • Altiris Out-of-Band Management 7.1 SP2 (7.1.7580)
  • Altiris Software Management Solution 7.1 SP2 MP1 (7.1.7858)
  • Altiris Power Scheme Task 7.1 SP2 (7.1.1304)
  • Symantec pcAnywhere Solution 12.6.7 (12.6.8096)
  • Altiris Client Management Suite Portal Page (7.1.1005)
  • Altiris Real-Time System Manager 7.1 SP2 (7.1.7580)
  • Altiris IT Analytics Client Server Management Pack 7.1 SP2 (7.1.2060)
  • Wise Connector 7.1 SP2 (7.1.7580)
  • Symantec Endpoint Protection Integration Component 7.1 SP2 (7.1.1037)
  • Altiris IT Analytics Symantec Endpoint Protection Pack 7.1 SP2 (7.1.2060)
  • Altiris Deployment Solution Complete Suite 7.1 SP2 MP1 (7.1.7858)
  • Altiris Deployment Solution Linux Support 7.1 SP2 MP1 (7.1.7858)
  • Altiris Deployment Solution WinPE Support 7.1 SP2 MP1 (7.1.7858)
  • Altiris Deployment Solution Core 7.1 SP2 MP1 (7.1.7858)
  • Activity Center 7.1 SP2 MP1 (7.1.7858)
  • Altiris Client Management Suite Documentation 7.1 SP2 (7.1.3010)
  • Altiris Deployment Solution Documentation 7.1 SP2 (7.1.3019)
  • Altiris Inventory for Network Devices Documentation 7.1 SP2 (7.1.3017)
  • Altiris Inventory Solution Documentation 7.1 SP2 (7.1.3021)
  • Altiris IT Analytics Documentation 7.1 SP2 (7.1.3007)
  • Altiris IT Analytics Documentation 7.1 SP2a (7.1.3020)
  • Altiris IT Analytics Documentation 7.1 SP2b (7.1.3035)
  • Altiris IT Analytics Documentation 7.1 SP2c (7.1.3045)
  • Altiris Monitor Solution for Servers Documentation 7.1 SP2 (7.1.3021)
  • Altiris Out-of-Band Management Documentation 7.1 SP2 (7.1.3022)
  • Altiris Patch Management Solution Documentation 7.1 SP2 (7.1.3006)
  • Altiris Real-Time Console Infrastructure Documentation 7.1 SP2 (7.1.3017)
  • Altiris Real-Time System Manager Documentation 7.1 SP2 (7.1.3017)
  • Altiris Software Management Solution Documentation 7.1 SP2 (7.1.3023)
  • Enhanced Console Views Documentation 7.1 SP2 (7.1.3018)
  • Symantec Endpoint Protection Integration Component Documentation 7.1 SP2 (7.1.3018)
  • Symantec Management Platform Documentation 7.1 SP1 (7.1.6848)
  • Symantec Management Platform Documentation 7.1 SP2 (7.1.3021)
  • Symantec pcAnywhere Documentation 12.6.7 (12.6.2024)
  • Wise Connector Documentation 7.1 SP2 (7.1.2016)

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

+1
Login to vote
Pascal KOTTE's picture

Hum, Client + Server Management Suites, thanks for this extended list :)

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-1
Login to vote
andykn101's picture

CMS 7.1 SP2 MP1.1 contains exactly the same components as the above list.

Edit: Although when I go to actually Install instead of creating an install package it reports:

"Symantec Management Platform 7.1 SP2 MP1.1 (7.1.8401)"

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

+3
Login to vote
Pascal KOTTE's picture

Hello, care, a new MP 1.1 is out

http://www.symantec.com/business/support/index?page=content&id=DOC5955

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
shrishail.jivani's picture

Altiris 7.1 SP2 MP1.1 released

SIM should be able to stop the IIS & WWW services while upgrading solution, but it didn't stop the services while upgrading MP1.1. It was encountered error. Finally I had stopped the services manually then ran the upgardation, so it worked fine for mesad

+2
Login to vote
burndtjammer's picture

I have not yet installed MP1. I plan to upgrade to MP1.1 early next week. Are there any suggestions?

Full database backup
Snapshot NS
Stop IIS/WWW
Follow upgrade guide

Anything else?

+3
Login to vote
shrishail.jivani's picture

Hello,

Above mentioned things are more than enough, but for good practice please disable the policies/tasks which have enabled in console. After completion of upgradation you can enable it.

+1
Login to vote
burndtjammer's picture

Excellent, Ill start in on it first thing after Sundays Full Maintenance routine.  Ill report back here my findings.

-1
Login to vote
burndtjammer's picture

In the middle of the upgrade as we speak and I I was getting a few HIDS notifications for registry changes and the like... However, I thought this one was interesting:

+3
Login to vote
Nonos's picture

I just read the link you provided, and since you said this happened during the upgrade phase and no one seemed to have reported the same problem, I was wondering if you weren't infected before the upgrade and the upgrade just made a call to the infected DLL and you got the warning from McAfee.

So my question would be, are you 100% sure that it is the package from Symantec that infected your platform?

Maybe you should download the packages on another platform and launch a scan with McAfee before and after download.

As I don't have DS7.x in my environment and I am not planning to install it any time soon, I didn't get this problem.

But I am still curious to know if this is really coming from a Symantec infected package or just your platform being infected before the upgrade.

Regards.

-1
Login to vote
Pascal KOTTE's picture

I also don't believe the original symantec was infected, we don't get this. But never know, be sure if it was, file was replaced now :)

There is a signature validation and a verification from the SIM (except you activate the check bypass registry), so it is a very low possible the source file was infected.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
Stefan S.'s picture

For those who are planning to install MP1.1 and for those who already have it installed. There is a Rollup Version 1 available...

SMP 7.1 SP2 MP1 Rollup Version 1 Information Notes

http://www.symantec.com/docs/HOWTO81832  
 

+3
Login to vote
Scott W. Allen's picture

Where does one get the Rollup Zip file? I don't see it mentioned in the article.

Scott

-1
Login to vote
mclemson's picture

Symantec Support.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

+1
Login to vote
burndtjammer's picture

I put a request in to support last week but have yet to get anything back. It would be great if they could add stuff like this as a hotfix or update in SIM.

+1
Login to vote
jobby's picture

I had to get hold of them via their chat.  Nobody there knew about the mp1 rollup v2.  After going through five (literally) people there, with none of them knowing what I was talking about, they transferred me to level 2.  Level 2 Knew what I was talking about, but had to transfer me to the Development Team to get the file.  Development Team got me both zip files I needed to proceed to upgrade from MP1.1.

By the way, does anyone with MP1 Rollup v2 have any problems installing the SP2 products from SIM, or does it error out on the prerequisite check?  I got a screenshot to support (they were helping with another issue, but had to manually, without using SIM, install the products that were getting reinstalled).

-3
Login to vote
kevinlai's picture

I am going to do an off-box upgrade from 6.0 to 7.1 in this week. I have already tested 7.1 SP2 in a testing server, so far ok. However, since the new version 7.1 SP2 MP1 is released, I installed the 7.1 SP2 MP1 from the new downloaded SIM 7.1.238. According to the upgrade guide, I have to upgrade from 6 to 7.1 SP2 and then upgrade to MP1.1. Is it correct?

Another question is that client 7.1 SP2 got version - SP2, SP2a and SP2b, I should use SP2 for the off-box upgrade and migration from 6.0 to 7.1, correct?

Thanks!

+1
Login to vote
carlsson's picture

After upgrade to MP1.1 I have this issue

Unable to generate policy XML for item: Software Update Plug-in Install for Windows x86 (0bba4205-5de3-41eb-b50a-3ac5d48cf308)

Did anyone get a fix for this ?

C

Hojiblanca

-1
Login to vote
jobby's picture

carlsson,

The released SMP 7.1 SP2 MP1 Rollup Version 2 on October 31.  Information on this can be found at:
http://www.symantec.com/business/support/index?page=content&id=HOWTO81832&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1357665203037lm1bArbVymn4rrz186k7Uy1foBu5OfMM9y2mT

If I remember from reading, one of the things fixed was that it wasn't processing NSEs, along with a ton of other issues that MP1.1 had.

+1
Login to vote
burndtjammer's picture

Where would one go about downloading the release from?  My SIM updated on the 21st but theres no upgrades or hotfixes listed.

+1
Login to vote