IT Management Suite

I am in the middle of an in-place upgrade that I started yesterday morning. 

 

SMP Upgrade

-I backed up nscap by zipping it with 7-zip and copyingthe zip and my .gho images on to a seperate server.  I then took snapshots of my DB, NS, and main TS.

-The SIM upgrade and the product upgrade went fairly well.  I let it do the .net 4.5.1 install and that too was seamless.  I did have to cancel SIM a few times during the product download portion because the downloads kept stalling.  Thankfully after verifying what was already downloaded, it picked up where it left off. I'm not sure if it was an issue on my end or Symantec's.

 

Site Server Upgrade

-Here's where things got harry. I read the upgrade guide and I didnt come across any mention of the site servers requiring .net 4.5.1.  If I missed it, can someone point out to me where that is?  I didn't realize it was a requirement until none of my task servers were upgrading so I decided to do one manually.  During the install of TaskServerSetup.exe it prompted me that .net 4.5.1 was installed and I couldn't go any further until this was done.  Joy.  I would recommend, unless symantec suggests otherwise, installing .net 4.5.1 on all of your task servers BEFORE you begin your upgrade.  Do not install it on the NS... let SIM do that for you.

Client Task Agents

I haven't had any major issues here except for... in "nscap\bin\Win32\X86\NS Client Package" what is the difference between AeXNSC.exe, AeXNSChttp.exe, and AeXNSChttps.exe.  If I am doing a manual install because I am impatient, which one would I use?  In the past there was only AeXNSC.exe.

Deployment Solution

I haven't tested imaging yet but I did seem to lose the boot disks I created in BootDiskCreator.  Not a big deal, however, I can create an ISO but not an USB.  It seems to error out on one of the final steps.

Thanks, really useful. Id install .NET 4.5.1. and patch it manually rather than let SIM do it. Also I usually use SIM to create an install package first to download and cache all the install files before I go for an install or upgrade.

The only mention I was able to find so far about the .net requirement for task servers was in http://www.symantec.com/business/support/index?page=content&id=DOC7978 on page 114.

About SMA installation package:

AeXNSC.exe - package doesn't contain pre-defined NS URL and SMA settings

AeXNSChttp.exe - package contains NS URL HTTP address and other settings from Communication profile

AeXNSChttps.exe - package contains NS URL HTTPs address, certificates and other settings from Communication profile.

Igor,

  Thank you.

 

Other issues

Deployment Solution

I am having issues with boot disks and automation folder creation.  If I attempt to make a usb boot disk it errors during compression.  If I attempt to make automation folders, bootwiz.exe runs and creates the files but once they are installed on a client, the client doesn't recognize them to boot to them. 

I attempted to repair DS but I recieved these two errors:

I get this error with boot disk creator whether I am making an x64 or x86 boot disk with winpe 4.0.  I receive a similar error if i attempt to make a linux pe.

 

Hi,

Regarding the Deployment Solution issue, it will be great if we get the complete and detailed steps to know more about this issue.

Can you please provide the detailed steps for the same ?

Thanks!.

peeyushd,

   I am not quite sure that I follow you...

Support directed me to move my winpe40 folder and recreate it by uploading a fresh version of winpe4.0.  After I did this I encounter the same error as above when creating a usb boot disk.  I am able to recreate the automation folders and they are now bootable.  However, when a client boots in to automation I get the below errors:

 

pectagent.log

[2015/03/12 11:24:33.848 1224:1228 2] Log File Created.
[2015/03/12 11:24:34.395 1224:1228 2] AgentGlobals.h:139 RegisterLibrary: x:\program files\Symantec\Deployment\Client Task Agent.dll has been registered sucessfully
[2015/03/12 11:24:34.411 1224:1228 2] AgentGlobals.h:139 RegisterLibrary: x:\program files\Symantec\Deployment\AeXNetComms.dll has been registered sucessfully
[2015/03/12 11:24:34.411 1224:1228 2] AgentGlobals.h:112 RegisterLibrary: LoadLibrary Failed to load x:\program files\Symantec\Deployment\AeXBasicInventory.dll
[2015/03/12 11:24:34.411 1224:1228 0] AgentGlobals.h:114 Agent Exception, Could not laod file ErrorCode=0, SystemError=6
[2015/03/12 11:24:34.411 1224:1228 2] PECTAgent.cpp:152 Stopping PECTAgent. Please check for Network configuration or server name resolving problem and try again.

smp.log

 

<event date='03/12/2015 11:24:33.8480000 -08:00' severity='4' hostName='minint-3vk1ad0' source='PectAgent' module='PECTAgent.exe' process='PECTAgent.exe' pid='1224' thread='1228' tickCount='41546' >
  <![CDATA[Version 7.06.1395]]>
</event>
<event date='03/12/2015 11:24:34.4110000 -08:00' severity='1' hostName='minint-3vk1ad0' source='PectAgent' module='PECTAgent.exe' process='PECTAgent.exe' pid='1224' thread='1228' tickCount='42109' >
  <![CDATA[AgentGlobals.h:114 Agent Exception, Could not laod file ErrorCode=0, SystemError=6]]>
</event>

 

I checked the path for aexbasicinventory.dll and it looks like its there in both the x86 and x64 directories

 

Hi,

We are trying to reproduce this issue at our end. Needed few more details for steps what you are performing:

1. "Support directed me to move my winpe40 folder and recreate it by uploading a fresh version of winpe4.0.  After I did this I encounter the same error as above when creating a usb boot disk"

What exactly are you doing when you say 'move winpe 4.0' ? Can you please elaborate on this step?

2.For  the errors that you are seeing in automation environment, did you check if your client could ping the NS by its hostname ?

Coz from the logs - "2015/03/12 11:24:34.411 1224:1228 2] PECTAgent.cpp:152 Stopping PECTAgent. Please check for Network configuration or server name resolving problem and try again."

it seems like the NS name is not getting resolved from the client machine.

 

3.I believe you are perfoming an upgrade over here. Can you tell us which upgrade path you have taken here?

Thanks.

Has there been a solution to this PECTAgent issue?

I noticed it was mentioned in this thread, but was not the topic. I will start a new thread, as we already had done the upgrade and I sorted through some issues on my own, but now I am stuck. Curious to see if anyone made progress and just didn't say anything.

 

Thanks!

I started a thread about my particular issue, which appears to be part of this thread. In case anyone gets interested and this thread does stay stale.

 

https://www-secure.symantec.com/connect/forums/winpe-pxe-booted-machine-does-not-register-pectagent-issue

 

Thanks