The "ITMS Technical Resource Kit" has been published.

[Migration User]

We have published the ITMS Technical Resource Kit. It features Symantec and 3rd-party tools that can be helpful in diagnosing problems with IT Management Suite and its components.

To access the resource kit, go to http://www.symantec.com/docs/HOWTO77027.

 

[Pascal KOTTE]

Hum, the link is not working :(

[Migration User]

We're working on getting the document bck online - thanks for your patience!

Cheryl

[Triinu Gross]

the article is available now:
http://www.symantec.com/docs/HOWTO77027

[Migration User]

Hello,

we had to take this article offline for a couple of weeks, but will re-publish as soon as possible. We apologize for any inconveneience this may cause.

 

[Scott W. Allen]

Am I going to have a problem?

 

Scott

 

 

[Migration User]

Scott, no, withdrawing the link for the time being is not related to technical issues.

[ianatkin]

Will this ever come back? This is referenced in SIM for people installing ITMS -it's not very professional to have this link broken.

Kind Regards,
Ian./

 

[Pascal KOTTE]

Hi Ian, Yes the link is working now :) But allways try 2 times, the 1st try often go home support page instead. :P Not joking...

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

[Pascal KOTTE]

Hum the MSI install an obsolete SSEtools.exe you can get latest from the

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

It is a nice portable program :)

Notice if you run the MSI above, you got an update proposal, accept, this auto download latest version, no problem.

If you got the "windows cannot access the specified device path file..." just add the "execute-read" for your account on the parent folder "Altiris", as the tools copy it on the root the install program folder.

Strange, also why a 32 bit package ? Perhaps SSE tools can run a client to access logs not from the server... If yes, would be great ! I already try to get the "Log viewer" as stand alone, without success :(

I feel the tools SoftwareReplicator.EXE, could be nice, except why coming when all work done manually already :(

Symantec Software Resource Replicator

Used in an upgrade scenario from Symantec Management Platform 7.0 to 7.1. Currently, the 7.0 to 7.1 migration tool does not migrate software resources from 7.0 to 7.1. The Symantec Software Resource Replicator utility migrates "logical" information for deliverable software resources from one Notification Server to another. Note that the utility does not migrate physical packages. Physical packages should be migrated manually For more information, go to http://www.symantec.com/docs/TECH166711

Well, thanks a lot Symantec for publishing such requested tools from years... As we were having with Altiris NS6, some long years ago, before 2008 :P

[Migration User]

The issue has been resolved and the ITMS Technical Resource Kit is once again available.

Thanks!
Cheryl

[Pascal KOTTE]

Hum, the Queue Monitor seems stop working, not sure but seems from MP1...

Server queue is empty display, only agent queue are available... :(

 

 

See the end of this message for details on invoking 

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

   at System.ThrowHelper.ThrowKeyNotFoundException()

   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

   at Symantec.SseTools.QueueMonitorFormMain.updateQueueDataTable(List`1 directoryInfos)

   at Symantec.SseTools.QueueMonitorFormMain.setupQueuePath(String queuePath, DataGridView gridView)

   at Symantec.SseTools.QueueMonitorFormMain.beginMonitoring()

   at System.Windows.Forms.Form.OnShown(EventArgs e)

   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)

   at System.Threading.ExecutionContext.runTryCode(Object userData)

   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)

   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

----------------------------------------

ssetools

    Assembly Version: 1.9.3.1

    Win32 Version: 1.9.3.1

    CodeBase: file:///C:/temp/ssetools.exe

----------------------------------------

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5460 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5462 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 8.0.0.0

    Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

----------------------------------------

System.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.5420 built by: Win7SP1

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

mkxcdfbw

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Data

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

 

[Clint]

Is there supposed to be an attachment with all of the tools in HOWTO77027 as I don't see anything in the KB article itself?  If not, where can I get the msi file mentioned?

[Migration User]

The msi files should now be available as an attachment.

[Clint]

Should the msi be installed on the SMP server itself or were they meant to be loaded on a workstation for remote troubleshooting?  Also, what's the difference between the 2 attachments as the KB article says nothing about this?

[Pascal KOTTE]

Seems the fact a 32bit attachment MSI, look like you can install on workstation, but I feel SEEtools should be on NS. So I believe this second 32bit package, is for 7.0 NS servers :)