Hello

Can anyone provide me document which says why DHCP environment required for Deployment Solution and how much is the challenge we have to face if dont have DHCP Environment.

Probably user would like to know all list of managed endpoints in a single report and filter them out by their NIC(s) properties and see all available installed NIC(s) per client PC.

1. This report provides ability to filter out all managed endpoints by their installed NIC(s) by their properties, such as:

• NIC is routable or non-routable
• NIC is physical or non-physical
• Endpoint has 2 or more NIC(s)

2. Via mouse double click on any available managed endpoint, you will see drill-down report with detailed information about client connectivity state for "Lan", "Wan", "Internet" or "None Connectivity"

3. Via mouse right-click menu you will be able to see all available actions per this managed endpoint, such as: Resource Manager, etc.

• Download this attached .xml report "Managed endpoints report for NIC(s) properties and client connectivity state.xml" and import it on your NS server.

How to import existing .xml report

• Open SMP Console -> go to "Reports" -> mouse right click menu on root "Reports" folder -> click "Import" -> choose required .xml -> click "OK".

• You can edit SQL Query via "Edit" mode for imported report.

Note:

Report was created in CMS 7.5 SP1 HF4 server, but wasn't checked for 7.1 SP2 MP1.1 vX versions.

Introduction

We've been doing Hardware Independent Imaging (HII) since DS 6.5, long before DeployAnywhere came along. When were first determining the process, we looked at several driver management tools and they all had the same issues. They worked fine for 95% of the drivers, but there were always 5% that just would not work, even though the drivers auto-installed just fine if they were in the Windows DevicePath. Finally we decided that the benefits of a driver database and avoiding driver replication just weren't worth the hassle. The method we've been using since then was developed on Windows XP and has worked flawlessly on every release of windows since then (actually getting simpler with the death of HAL files in Vista).

Preparation

First we set the DevicePath in our base image to add C:\Drivers. We then take advantage of the Driver packs available from most major business PC manufacturers (we use Dell and HP and both work great). We have a driver repository in a windows share called 'Drivers' on each site server. This share contains a folder for each model with subfolders containing drivers for each OS version we support, and a third folder called 'Common' for drivers that work for any windows OS. Within these folders we extract the driver packs. We also add one batch script we call 'OEMSetup.cmd' which for the vast majority contains nothing. In the very few cases we have drivers not fully install automatically during minisetup, we add command lines to this script to be performed after imaging in production. These driver folders can be synchronized using whatever method of fileshare replication you like (DFS for example).

The job scripts also need several tokens (Settings>Deployment>Tokens) to access the driver folders:

Siteserver token:

select c.name from TaskTargetDeviceCache vc 
   left outer join Inv_Client_Task_Resources ctr 
      on ctr._ResourceGuid = vc.Guid 
         And vc.Guid = '%COMPUTERID%' 
   left outer join Inv_Client_Task_Servers cts 
      on cts.ClientTaskServerGuid = ctr.ClientTaskServerGuid 
   join vcomputer c on cts._ResourceGuid = c.guid

SymUser token:

Select '<symantec network username>'

​SymPwd token:

Select '<symantec network user password>'

Deploy Image Jobs

Our image deployment jobs then contain a deploy image task with DeployAnywhere unchecked, a Driver Copy run script task appropriate to the OS being deployed, a boot to production task, and a run script task to execute the 'OEMSetup.cmd' script. 

The Driver Copy run script looks like this:

@Echo off
REM Copy Drivers to production for Win7 x64
Setlocal EnableDelayedExpansion

Echo Authenticating with Site Server
net use \\%Siteserver%\drivers %SymPwd% /user:<domain>\%SymUser%

Echo Retrieving Model Name...
For /F "tokens=2 delims==" %%A In ('WMIC computersystem get model /format:VALUE') Do Set STR=%%A
SET MODELNAME=%STR%
For /L %%A in (1,1,50) Do If "!MODELNAME:~-1!"=="" (Set MODELNAME=!MODELNAME:~0,-1!)

Echo Copying Driver files...
xcopy "\\%Siteserver%\drivers\%MODELNAME%\Common\*.*" C:\drivers /S /Y /I
xcopy "\\%Siteserver%\drivers\%MODELNAME%\Win7\X64\*.*" C:\drivers /S /Y /I
If %ERRORLEVEL% Neq 0 Goto DriverFail
Goto End

:DriverFail
REM driver copy failed.  This may be because C: is not mounted or is 
REM mounted as RAW.  Retry after manually assigning C: using diskpart
Exit 253

:End

The script authenticates with the site server share, queries the model name of the computer via wmic and then copies the contents of the appropriate OS and Common folders from \\%SiteServer%\drivers\%modelname%\ into C:\Drivers. Note that for WinXP you may also need to copy correct HAL files into place. We stopped supporting XP before we switched to 7.x so you'll need to track down that information elsewhere. Mini-setup then installs all the drivers automatically during the boot to production. Finally after the boot to production the OEMSetup.cmd script is run to finalize anything that doesn't work automatically.

Integrating New Hardware

With all this in place our process for adding a new computer model is:

1. Determine the full model name (also known as productname in the BIOS) for the new computer and create a folder named this in our driver repository.
2. Download the driver pack cabs for each OS we support from Dell or HP and extract them to the appropriate subfolders.
3. Determine if any drivers are universal (applicable to all OS versions) and move them to the Common subfolder.
4. Copy in a blank OEMSetup.cmd to this folder.
5. Perform initial deployment on the first new computer (which deploys our standard image) and verify that all drivers installed correctly.
6. Add custom unattended installation command lines for drivers that didn't install automatically (rare, so far only bluetooth drivers)

Closing

This works extremely well for us. We currently support 24 different models, both Dell and HP, laptops and desktops, and only two require any OEMSetup customization (both older models, both bluetooth drivers). We've never had a single issue with USB3 drivers, which seem to plague everyone else. Note that extended configuration applications for things like video cards (like AMD Catalyst) do not automatically get installed. If you want these (we generally don't) their setup command lines need to be added to OEMSetup.

The one downside to our method is driver duplication. Since many models have the same base hardware, the drivers are duplicated in each model subfolder. The total storage required for all 24 models' driver folders is currently 21GB per site server. Honestly, slow storage is cheap and we really don't care about this. In fact it makes it easier when some models are finicky about certain (older) driver versions working better than others.

Hopefully this helps those of you looking for a simple alternative to DeployAnywhere. Good luck!

After a Service Pack, Hot fix or platform upgrade it is necessary all the SMA and all the SMA plug ins are up to date.

A quick bird-eye view of the environment SMA versions is possible following the steps below:

1 - Download the SSE reports XML file at link:

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

2 - Import "SSE_Reports.xml" into the Reports tree of the Symantec Management Platform (right-click on "reports" folder -> import)

3 - Find "Agent Version Detail" under: SSE Reports -> Agent:

4 - Filter by "Agent Name":

NOTE:

If you found the above information useful, please give this article a thumbs-up(top right of the post) or add a comment below. Your feedback will help the Symantec tech community – Thank you, Mauro

Announcing the availability of ITMS 7.5 SP1 HF5.

This release is available through SIM and contains fixes for the following components:

• Deployment Solution
• Inventory Solution
• Software Management Windows
• Network Discovery
• NS Agent
• NS Server
• PPA
• SMF
• Task Server
• ULM

Also added is official support for

Release notes are available at http://www.symantec.com/docs/DOC7954

Cheers,

-Hugo

When troubleshooting ghost errors it may be necessary to run the "deploy image" job using ghost switches.

The Ghost switches list at link below can be used as reference:

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

To locate the console command line option in Deployment Solution open the "Deploy Image" task and locate the "advanced" button as from picture below:

after accessing the advanced options, select the command line tab:

NOTE:

If you found the above information useful, please give this article a thumbs-up(top right of the post) or add a comment below. Your feedback will help the Symantec tech community – Thank you, Mauro

I have been using the DS 6.9 SP6 console for several years and am trying to replicate the same in my lab under the 7.5 platform. I have gone through the docmentation and the modules in the elibrary but can't seem to get things going in this new layout.

Over 2 years ago we migrated all image files from gho to wim. The Win 7 image is bare bones with additional configuration tasks and software installs sequenced accordingly.  I have attempted to do the same in 7.5 put it is not working out. Do I really need to revert back to gho images?

I did get my wim image file imported into the Disk Images folder in the console (don't ask me how, I have to figure out how to reproduce this)

I created a task to map the drives, it reports as successfully, but nothing is listed when running a net use to confirm.  Then had the deploy image job pointing to my wim, but it simply says failed.  I also tried to include an install antivirus job but the execution failed. 

Anyone have any reference material I can use to get this going or offer any assistance?

This is a walk through of adding windows 8.0 (PE 4) Drivers to the Symantec Boot Disk Creator from TECH 223404. I will follow the steps noted in TECH227489.   We will go over how to download, extract driver files from the NIC manufacturer web page.   You will need to add drivers to the Boot Disk Creator if your Ghost boot disk boots up but you do not have network support. 

Although this video is discussing using a boot disk for Ghost the same steps can be followed when adding drivers to the DS boot wizard. 

Video Upload: 

adding drivers.mp4

Introduction

Script Tasks in Altiris 7.x have 2 types of Tokens available. The more well know token type can be found in the 7.x Symantec Management Console under Settings > Deployment > Tokens. These tokens provide data to the script at run time through database queries, an example being %COMPNAME% which adds the computer's name to the task instance being started. There is plenty of documentation on this type of token so I won't be including any further details in this article.

The second type of token is what I'm currently calling Unmanaged Tokens that look like %!Some Text!% and allow for manual input when a task is scheduled against a target. I call them unmanaged because they're not managed outside the script(s) that use them like the other type are. If anyone knows what this type of token is really called please let me know, documentation is basically non-existent.

Unmanaged Tokens

My example is a small computer rename script written in vbscript. Saving the following into a Script Task will cause the Quick Run button to be hidden requiring that the script be executed through the New Schedule button, this is because Altiris identified %!New Computer Name!% in the script.

NewPCName = "%!New Computer Name!%"
If NewPCName = "" then WScript.quit 13
If NewPCName = "%COMPNAME%" then WScript.quit 13

Set objWMIService = GetObject("Winmgmts:root\cimv2")

' Call always gets only one Win32_ComputerSystem object.
For Each objComputer in objWMIService.InstancesOf("Win32_ComputerSystem")
        Return = objComputer.rename(NewPCName,"","")
        If Return <> 0 Then
           WScript.quit Err.Number
        Else
           WScript.quit 0
        End If
Next

Clicking New Schedule results in a standard virtual window with one addition, there's an input box named after whatever is between the %! !% symbols as seen in the following image. Multiple tokens can be used in a single script.

Note: This example script must be configured with domain credentials that allow for changing a machine's name in Active Directory. I believe technically the AD permissions are create/delete objects.

Jobs

When including these scripts in client jobs more functionality is exposed. As seen in the next image.

With the task highlighted in the job you see the Task Input options on the right. By default "Prompt me for task input each time this job is run" is selected. Using one of the other options like "use a set value" allow you to re-use the same script in many jobs each with their own value based on the job's purpose. <EDIT>The option to "use output from a previous task" combined with script name - Script output only works if the previous tasks output is only the value, vbscripts that include the logo text in the output don't work so a Command Prompt script is better.</EDIT> I also haven't seen any difference between the original default option and "prompt at run time".

Conclusion

In addition to Script Tasks I've also found these tokens useful in SQL Query tasks, and they appear to be standard in many Automation Policy tasks. For those interested the input values are stored in the TaskInputParameterValue table and and can be referenced by TaskInstanceGuid and includes a Name column for the token and the Value.

Hopefully the information in this article is useful to others.

Credit: I don't remember the name of the script but I got the idea to start researching these tokens a few years ago based on a script from a DS 7.1 sample pack.

Please consider updating the <scriptCommandLine> tag of the VBScript Item (DE2893DC-E9D6-4551-9B9D-2A8FCA5513FA) used by client side Script Tasks to include //NoLogo. Currently there is a feature of script tasks documented at https://www-secure.symantec.com/connect/articles/h... that describes near the end the option to use the output of a previous script in a follow up script of a client job. This is not possible with VBScript while the "logo" is enabled.

Current state:

<item guid="{de2893dc-e9d6-4551-9b9d-2a8fca5513fa}" classGuid="{9f82ea20-c8e5-410e-9bc4-23a9548b4d87}">
  <!--  Type: Altiris.TaskServerTasks.ScriptTask.ScriptTypes  -->
  <!--  Assembly: Altiris.TaskServerTasks, Version=7.5.3153.0, Culture=neutral, PublicKeyToken=99b1e4cc0d03f223  -->
  <name>VBScript</name>
  <alias />
  <ownerNSGuid>{338ee7c1-2f96-4457-8765-d33c062a3699}</ownerNSGuid>
  <productGuid>{d1341aa4-95d3-4335-ad2f-a7f3389783b6}</productGuid>
  <itemAttributes>Normal</itemAttributes>
  <itemLocalizations>
    <culture name="">
      <description><![CDATA[Run VBScript]]></description>
      <name><![CDATA[VBScript]]></name>
    </culture>
    <culture name="de">
      <description><![CDATA[VBScript ausführen]]></description>
      <name><![CDATA[VBScript]]></name>
    </culture>
    <culture name="es">
      <description><![CDATA[Ejecutar VBScript]]></description>
      <name><![CDATA[VBScript]]></name>
    </culture>
    <culture name="fr">
      <description><![CDATA[Exécuter VBScript]]></description>
      <name><![CDATA[Script VB]]></name>
    </culture>
    <culture name="it">
      <description><![CDATA[Esegui script VB]]></description>
      <name><![CDATA[VBScript]]></name>
    </culture>
    <culture name="ja">
      <description><![CDATA[VBScript の実行]]></description>
      <name><![CDATA[VBScript]]></name>
    </culture>
    <culture name="ko">
      <description><![CDATA[VBScript 실행]]></description>
      <name><![CDATA[VBScript]]></name>
    </culture>
    <culture name="pt">
      <description><![CDATA[Executar VBScript]]></description>
      <name><![CDATA[VBScript]]></name>
    </culture>
    <culture name="ru">
      <description><![CDATA[Выполнить сценарий VBScript]]></description>
      <name><![CDATA[Ñöåíàðèé VBScript]]></name>
    </culture>
    <culture name="zh-Hans">
      <description><![CDATA[运行 VB 脚本]]></description>
      <name><![CDATA[VB ½Å±¾]]></name>
    </culture>
    <culture name="zh-Hant">
      <description><![CDATA[ˆÌÐÐ VBScript]]></description>
      <name><![CDATA[VBScript]]></name>
    </culture>
  </itemLocalizations>
  <scriptExtension>vbs</scriptExtension>
  <scriptCommandLine>cmd.exe /c cscript "!s"</scriptCommandLine>
  <filterCollections>
    <filterCollection guid="e3a71b08-1612-44a6-9f71-7d359d5475b4" />
  </filterCollections>
  <parentFolderGuid>d12f8d5f-36c6-4d27-abc4-f1d38f17a132</parentFolderGuid>
  <originNS guid="{338ee7c1-2f96-4457-8765-d33c062a3699}" name="CPALTSMP1.kidsnet.childrenshc.org" url="http://CPALTSMP1.kidsnet.childrenshc.org/Altiris/NS/" />
  <sourceNS guid="{338ee7c1-2f96-4457-8765-d33c062a3699}" name="CPALTSMP1.kidsnet.childrenshc.org" url="http://CPALTSMP1.kidsnet.childrenshc.org/Altiris/NS/" />
  <security owner="@APPLICATION_ID" inherit="True">
    <aces>
      <ace type="reserved" name="@APPLICATION_ID">
        <permissionGrants>
          <permissionGrant guid="{eca6254f-5017-4730-9b3f-5add230829b7}" name="Delete" />
          <permissionGrant guid="{983a2d22-7a82-4db0-a707-52c7d6b1441e}" name="Read" />
          <permissionGrant guid="{ac296df1-eb40-4592-899f-25d5c07d45f6}" name="Write" />
          <permissionGrant guid="{819dae1e-b1a5-4643-81a1-26ef95feb8a8}" name="Change Permissions" />
          <permissionGrant guid="{726b1c09-7108-450d-ae24-5f8e93135ed6}" name="Clone" />
          <permissionGrant guid="{4ddc04c3-f0a5-4e88-84aa-c44c8c5ebcc4}" name="Read Permissions" />
        </permissionGrants>
      </ace>
    </aces>
  </security>
  <itemReferences />
</item>

Suggested change:

<scriptCommandLine>cmd.exe /c cscript "!s" //NoLogo</scriptCommandLine>

Note, hacking the State column in the Item table works but only for script tasks created after the change. If this does somehow make it into an ITMS update it would be great if it could cover existing tasks as well.

In this Video we will discuss how to add simple automation to the boot disks created with the BDC.  Additionaly we will add command line switches to the ghost32.exe and ghost64.exe.   

For referance see Apendix A from the Ghost Implementation Guide  for more use examples. 
See Switches: Alphabetical list of switches for a list of most of the ghost command line switches. 
Refer to Ghost Compatibility with Microsoft Surface Pro Tablets for more information and use of specific Ghost command line switches to be used while imageing a MS surface Pro tablet
 See Cloning Solid State Disk (SSD)  for more information on errors and workarounds for some SSD drives. 

For More Boot Disk Creator instructional videos see. 
Symantec Ghost 3.0 boot disk tutorial for TECH223404
Adding Drivers to the Symantec Boot Disk Creator TECH227489 Video 

Video Upload: 

ghost automation.mp4

SSE is a collection of reports commonly used by Backline support and Sustained Engineering. They are very useful for monitoring, administering and troubleshooting.

An example can be seen at link below: (ITMS 7.5 - Checking Agent Plug-ins versions via SMP reports)

https://www-secure.symantec.com/connect/blogs/itms-75-checking-agent-plug-ins-versions-smp-reports

(Please note that not all the reports have been tested with ITMS 7.x)

1 - Download the SSE reports XML file at link:To import the SSE reports into the SMP console:

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

2 - Import "SSE_Reports.xml" into the Reports tree of the Symantec Management Platform (right-click on "reports" folder -> import)

See below the list of available reports within the SSE package:

• AGENT:
• Agent Upgrade Status (This report bases its calculations from the highest known Product Version of each agent. It will show 100% when all agents are at the same version)
• Agent Version Detail (List of computers with version, for a specified Plug-in)
• Basic Inventory data not reported within 'N' days (Computers that have not reported Basic Inventory data within the specified number of days)
• Computers created or last modified by dataclass (This is intended to help troubleshoot where a computer came from or what last modified it ie (AD Import, network discovery, Basic Inventory etc))
• Computers not requesting configuration in Last 'N' days (Computers that are not communicating with the SMP, many times data is updated through other processes but configuration requests must come from the agent)
• SERVER:
• Deleted Items (Shows Items that have been deleted, including available item management information)
• GUID search (Find all tables that contain a specific GUID)
• Site Server Summary (Provides a client count for each Site Server by site and service)

Database:

• Current Table sizes (Display the sizes of all tables beyond the specified parameters)
• Index Fragmentation (View the fragmentation level for all indexes created on tables in the SMP database)
• SQL Object Search
• Table Growth (Row or Size in KB) Report

Performance:

• Server Performance (not updated)

Replication:

• Replication rule and job status (Shows latest Replication Job status for each Replication Rule)

Security:

• Security permission comparison (Items)
• Security privilege comparison
• Single Item - Resource permission list
• Windows-based security role membership (Lists the Windows-based security roles in the CMDB that the user running this report is a member of)

Task:

• Currently running tasks (This report lists all running tasks so you can find them and stop them in the console)
• Latest task status (This report provided as-is, only for use as a supportability template)
• Task schedules
• Task table status

• SOLUTIONS:

Inventory:

• Inventory solution data not reported within 'N' days (Computers that have not reported Inventory Solution data within the specified number of days)
• Server inventory data not reported within 'N' days (Computers that have not reported Server Inventory Solution data within the specified number of days)

Monitor Solution:

• Monitor solution data not reported within 'N' hours (Monitor Agents that have not reported detailed data for more than 'N' hours)

Patch Management:

• Computers assigned to more than one software update configuration policy (DSUAP)
• Patch filters

• SUBREPORTS:
• Client configuration request details (Performance Drilldown)
• Installed agents selector
• Site name-GUID selector
• Site Service name-GUID selector

• USER:
• Latest user logon and logoff (Displays the latest logon and logoff events recorded for each user and computer)

• Problem:

When booting an "unknown" machine, the following error is shown at startup:

Windows Boot Manager

Windows failed to start. A recent hardware or software change might be the cause.

Status: 0xc000000f

• Cause:

boot.wim missing or corrupted at Site Server location:

C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Images\WinPE 4_0 x64\x64\sources

please note the folder WinPE 4_0 x64 correspond to my custom WinPE x64 pre-boot configuration:

and NBS is set to respond to "unknown" computers using the WinPE 4_0 x64 pre-boot configuration:

• Solution:

Re-create the preboot environment and make sure bootwiz.exe is running at the site server for re-creating boot.wim

If bootwiz.exe does not start, troubleshoot bootwiz.exe:

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

check boot.wim has been created or date and time have been updated:

If successful the client will then boot into Automation, register with the SMP and, in my example, launch "initial deployment" or run the next assigned task :

NOTE:

If you found the above information useful, please give this article a thumbs-up(top right of the post) or add a comment below. Your feedback will help the Symantec tech community – Thank you, Mauro

Just throwing this out there to maybe save someone else some pain for some items you might want to back up pre upgrade.

After upgrading to 7.5 a year ago and being in a world of hurt (missing images, DA broken), I didn't touch our CMS environment since in fear of breaking something else (and I was working with support on DA regularly).

I got everything working as I wanted to a week or so ago, so decided to upgrade now that SP1 has been out for awhile before 7.6 is released.  

The upgrade process itself seemed to go OK.  I contacted DS support pre upgrade who suggested I go to latest HF pre SP1, wait a day, upgrade to SP1, wait a day, then upgrade to latest SP1 HF.  There were no errors during the upgrades themselves.  However, in the console, every deploy task doesn't work anymore.  Each deploy task produces an error in the console and in logs when I click on them, and all existing jobs using those tasks also don't load and produce errors in console.  

Luckily, I can create new deploy tasks and jobs, but I'm not able to see the existing jobs to remember what XYZ software tasks were in the job.  Support is working with me on that.  Support asked if I had gone into my deploy jobs folder in console, right clicked, and done an export.  I hadn't, but this may have saved me some pain to know the contents of the corrupted jobs, so I'll be doing that from now on pre upgrade, and you may want to as well.  Support never saw my issue before though, so it's probably unlikely you'll see it.

Also, my custom sysprep files were deleted during the upgrade, I searched the whole server for *.xml.  Luckily, with shadow copies, I got those back with some digging and have since backed them up elsewhere.  If you use those, back those up too.  I'm not sure if there's some 'safe' place they're supposed to be in the server, but apparently where I have them isn't it.

I also had some technician permission issues, but support quickly got that sorted out.

Here's to hoping that's all that's wrong in our environment, and I can get by not upgrading for another year.

One bright point, though, is I am very happy with the level of support I am getting now.  I put a few tickets in and got a call back same day from US based techs who knew what they were doing.  It seems the days of me getting overseas support who doesn't understand the basics of CMS/DS and me begging for escalation may be over - and I couldn't be happier about that.  This great increase in level of support makes me so much more confident in the product whereas this time last year I was ready to jump ship.  Thanks to the new management for implementing some positive change.

When imaging, rather than imaging through the console, our techs rely on the list of jobs popping up for them once in PXE.

The list is configured under Settings - Deployment - Initial Deployment for both unknown and known/managed computers.

It would be nice to have the ability to re-order Jobs in those lists to put new or important jobs at the top.

Currently to do this (7.5.1 HF5), to add a new job to the top of the list, I believe you have to remove all jobs listed and re-add in the order you want.  Not the end of the world, but it'd be nice to not have to start over to edit the order.

Thanks!

On Friday I did the update to HF5.  Now when I try to run an image job it fails rigth away with an error message (see attachments). I have tried to create a new Client job to image with the same resualts. I have tried this on differnet computers and laptops that I know worked prior to the upgrade. I have also attached the log files from one of the computers that i have tried

To test I created a new deploy job and the results were the same as with the orginal job.

Hi Everyone,

If you've got an idea that you've got for ImageInvoker, please drop a comment here. Anything from annoying typos and inconsistencies, to new functionality.

At the moment I've got listed these items to work on,

• Full 64-bit WinPE and support
   
• An optional chain-job screen so that a number of jobs can be selected manually to provide an on-the-fly customised delivery. So following the ImageInvoker menu selection, you'll optionally have the ability to add extra software jobs on-the-fly to the ImageInvoker schedule queue
   
• Allow menu to be refreshed within the menu presentation windows (to take into account menu changes after client has booted into automation)
   
• Allow ImageInvoker client to be restarted (instead of just exiting) in the event of an error.
   
• Check support for Ghost Solution Suite 3

Kind Regards,
Ian./

I have one PC getting the error above in WinPE.  The authenticating network connection takes a very long time and then throws this error.

This is a KB with a similar issue, but all of the fixes would not apply here.  We can image anything else with no issues.

http://www.symantec.com/business/support/index?pag...

I have removed this computer from AD and Altiris multiple times before starting the image, but it still fails with this authentication issue.  I double checked our PXE config to verifiy we have the correct account setup, and checked AD to make sure the account isn't locked or disabled.

All information I can find on this error makes it seem like it should be effecting all pcs or none.

Any help would be wonderful.

I am trying to figure out which systems came from which image.  I have built a custom report that reports the date the system was imaged, and that is slightly useful at best.  That report reports on the [Operating System].[Install Date] field but that gives the date the  system was imaged, not the date that is in the image.  This information is stored in the system registry at HKEY_LOCAL_MACHINE\SYSTEM\Setup Clone Tag as a REG_MULTI_SZ key in the format of 'Day Mon ## ##:##:## ####'

  I feel this is something that should be a built in inventory and report item.  It could be very useful to an organization trying to isolate systems imaged with a certain image if something is discovered that needs to be resolved within them or to report on the number of systems imaged with a particular image.

I was wondering if there was a documented cleanup process of personality captures on the Site Servers.  I haven't been able to find much on if its manual or automated.  It doesn't seem to be automated as were never seeing the captures cleaned up.

Were currently running ITMS 7.5 SP1 HF2, so this might of been resolved in a later HF but I haven't seen any mention of it in the release notes.

Any help would be greatly appriciated.