Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Tip/How to
Showing posts in English
Screenbert | 23 Jun 2009 | 1 comment

When working with our core image for Windows 7 I found that restoring an image that has not been syspreped results in a boot error. You can go through the windows repair and let it try to "fix" the issue. Or you can simply use bcdedit to "reset" to boot information. I never had this problem with Windows Vista Images, so it seems to be the new boot manager with Windows 7 that cause this issue. It's probably a good thing to keep unauthorized (and un-sysprepped) images off of your network.

1   ) Restore the Windows 7 image onto the computer
2   ) Boot with the latest version of your Altiris bootdisk.
3   ) Run these commands:
3a ) bcdedit /set {default} device partition=c:
3b ) bcdedit /set {default} osdevice partition=c:
3c ) bcdedit /set {bootmgr} device partition=c:

MBHarmon | 23 Jun 2009 | 0 comments

We recently had a request that seemed to make way too much sense for us to have not done it already. 
A helpdesk worker wanted to be able to view everything associated to an asset (monitors, incidents, people, software licenses) quickly and easily. 

By creating a task we were able to make that happen right away. 

Once you've set whatever parameters you want to make it viewable just drop this line into the "Base URL" section.


Quick and easy. 

Hope it helps.

CJett | 23 Jun 2009 | 0 comments

Periodically, packages deployed using NS7 to newly installed agents that have not been rebooted yet may fail with an Exit code of 1618.

imagebrowser image

This is caused by a hung instance(s) of the MSIEXEC.EXE service (this is the Windows Installer component used to install deployed MSI packages).  It is likely that you will see multiple instances of this process in process explorer.

imagebrowser image

In order to resolve this deployment issue and expedite the installation of the packages in a failed state, simply end all of the processes using the MSIEXEC.EXE service (make sure you're NS7 agent is not currently installing any packages, and that you are not installing any software outside of the agent).  After terminating all instances of the MSIEXEC.EXE process, attempt to run the installation of the...

G Ross | 17 Jun 2009 | 0 comments

Notification Server 6.5 SP3 + R11
Recently encountered an old problem after running a console repair and a repair of the Notification Server.  I was no longer able to drill down on the CMDB locaitons created for Asset Management under Manage > Asset and Inventory > Resources > Organizational Types > Location.  The hierarchy of locations created was often 4-5 levels deep, going from North America > State > City > Office > Floor.  In this particular case I was unable to drill down below the first level "North America"', to make use of the sub locations. When I would click on the + sign, it would just spin like it was trying to process the request and it would never come back with an error or timeout in any way.  Initially we suspected there was an issue with the 6.5 console since we were able to drill down on the locations in the 6.0 console fine.  After doing some...

Screenbert | 16 Jun 2009 | 0 comments

To install a MUI Language for XP we folow these steps:

1 ) Download the the MUI Pack with the language(s) you need.
2 ) Get the latest MUIsetup.exe from SP3 and replace the one included in the MUI pack download.
3 ) Execute it using this command line where "0416" is your language code, in this case Portugese.
muisetup.exe /i 0416 /d 0416 /r /s

4 ) Then we execute another command that changes Regional Settings for all users that log onto that machine again using the language code in the BR.TXT file.

rundll32.exeshell32,Control_RunDLL intl.cpl,,/F:"BR.TXT"

The BR.TXT file has the following information:
LanguageGroup = 1
UserLocale = 00000416
SystemLocale = 00000416
InputLocale = 0416:00000416
MUILanguage = 0416
UserLocale_DefaultUser = 00000416
InputLocale_DefaultUser = 0416:00000416
MUILanguage_DefaultUser =... | 10 Jun 2009 | 0 comments

I recently upgraded altiris to 6.0.308. I received the error message below when testing creating a new incident. I found that the default values for customer_id and contact_id were incorrect. I changed both values to 1 (the default contact for new incidents) and it corrected my problem.

Steps To Change The Default Values For customer_id and contact_id on a new Incident:

SQL Server 2000
1. In SQL Server, find the workitem table in the Altiris_Incidents Database.
2. Right Click on the workitem table and select "Design Table".
3. Select the contact_id field.
4. In the Columns tab set the value for "Default Value" to 1.
5. Repeat steps 3 and 4 for the customer_id field.

Exception - Altiris.Helpdesk.Services.ContactException: The contact does not exist in the database. Contact ID: 0
The originator of the previous log entry was itself an Exception. The last non-Exception occurred at stack index 1: Altiris....

G Ross | 08 Jun 2009 | 0 comments

Notification Server 6.5 SP3 + R10
Suites Installed: 
Altiris IT Analytics
Altiris IT Analytics Asset Management Pack
Altiris IT Analytics Client Management Pack

We recently received new licenses for our NS as a part of the AUP maintenance and after installing the new licenses we noticed the number of licenses had increased for some of the suites we owned but our IT Analytics licenses were not in synch and as a result IT Analytics stopped working.  IT Analytics Client Management Pack was exceeded due to the fact that our Patch Management, Software Delivery, and other Invetory licenses had increased beyond what IT Analytics was originally
imagebrowser image

After uninstalling and reinstalling the updated license files all of the IT ...

rpoag | 02 Jun 2009 | 6 comments

I created a custom inventory in CMS 7 using powershell and it would not submit data for some reason.   I spoke with support and they said that powershell 1.0 does not support variant types and so cannot be used for custom inventory purposes.  Powershell 2.0 will support variant types but for now vbscript is the only option available.  Just a heads up.

atliste | 29 May 2009 | 0 comments

The new Dell Optiplex 960 model line isn't currently fully supported by the Dell Client Manager 2.2 and also apparently 3.0, although I have had limited testing with that.  In particular there was a need to change a BIOS setting for the 960's pertaining to the C-State control.  The issue that was coming up is stuttering video in some applications due to the C-State control under performance settings in the Dell BIOS.  To remedy this we created a VB Script to query the Dell OMCI via WMI and change the setting to off for the C-State control.

Option Explicit

Dim strNameSpace
Dim strClassName
Dim strKeyValue
dim strPropName
Dim strPropValue

strNameSpace = "root/Dellomci"
strClassName = "Dell_SMBIOSsettings"
strKeyValue = "0"
strPropName = "CStatesControl"

Set objInstance = GetObject("WinMgmts://./" & strNameSpace & ":" & strClassName & "=" & Chr(34) &...
Terry Cutler | 22 May 2009 | 0 comments

This blog entry is primarily for those who are looking to acquiring a VeriSign certificate for vPro remote configuration. If you've already acquired and are using the certificate, VeriSign will likely be calling you with an update.

On May 17th, VeriSign transitioned to a new root certificate for G1 standard certificates - read statement from VeriSign:

Without going into great detail - how does this affect vPro remote configuration with a VeriSign certificate?

The good news is that VeriSign certificates are available for vPro remote configuration. Take a look at the landing page -