Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Client Management Suite
Showing posts in English
Terry Cutler | 29 Oct 2007 | 0 comments

In mid September of this year (2007), the updates to Altiris RTSM, OOBM, and OOBSC provided support for the following Intel vPro and Centrino Pro capabilities:

First, take a look at a previous article\post about Intel AMT versions and features. At the bottom of that article, the Intel SCS versioning is explained.

With the latest release of Altiris OOBSC, the Intel SCS version is 3.0. If unsure what version you are running, check the AMTconfig windows service version information. Intel SCS version 3.0 is the latest Altiris validated version. However, if you want to try a newer version, click here. NOTE:Test this offline from the production systems before deploying.

With that - some key items you'll notice in the Altiris Client Management Suite with the latest release:

  • Ability to central change Intel AMT...
MBHarmon | 23 Oct 2007 | 6 comments

In our organization we have some very security sensitive managers, one of whom was wholeheartedly for Local Security Solution (LSS). However, he quickly became concerned that passwords, after being disclosed, were opening security holes. While limited to those computers, he was still concerned enough and he has enough pull to have this issue block our full implementation of Local Security Solution. Therefore, it quickly became important to address his issues. Instead of upping our password reset interval for everyone, I came up with the idea of just reseting those passwords that had been disclosed.

After looking through the default LSS reports I found one that almost immediately fit our needs. After ripping it apart I was able to come up with a collection of computers that have had their current Local Security Solution passwords disclosed....

R-Vijay | 19 Oct 2007 | 0 comments

Gacutil must not be called from a custom action. Gacutil is not designed to be used during installation.

Gacutil.exe works, but it is a developer tool, and developer tools go into SDKs and not runtime packages typically. It isn't really appropriate to put more tools into the runtime because that causes it to get larger, which makes it more difficult for applications to redistribute because of increased download size, etc.

In general, installing an assembly to the GAC is an application deployment activity, and is most often done during application setup. One should use Windows Installer to install your application. Starting with version 2.0, Windows Installer has built-in functionality to install assemblies to the GAC - the MsiAssembly and MsiAssemblyName tables in particular.

Its always better to use a MSI as an installer and directly authoring files, registry and GAC installation steps using built-in Windows Installer functionality instead of using a batch...

erikw | 18 Oct 2007 | 6 comments

I found a great video about Intel vPro working on Dell hardware. It's a good quick overview about a technology that's getting a lot of buzz.

Below you find the link.
Enjoy it.

http://nl.youtube.com/watch?v=VV_v_OEOhH0

Regards
ErikW

R-Vijay | 15 Oct 2007 | 3 comments

Here's a command you can use to assign permissions to a registry key. You can write this action using VBScript or WiseScript. As this script needs admin privileges to work, run this action in system context in deffered execution.

SetACL.exe -on "hklm\software\microsoft\policies" -ot reg -actn ace
-ace "n:domain1\user1;p:full"

This command sets 'full' permissions on the registry key 'HKEY_LOCAL_MACHINE\Software\Microsoft\Policies' for user 'user1' in domain 'domain1'.

Cheers'
Vijay Raj

R-Vijay | 02 Oct 2007 | 1 comment

You can use the Windows Installer to detect missing components or files and then reinstall features containing the missing components. Because the installer installs features, and not components, it must first resolve to which component a missing file belongs and then install the feature containing that component.

If more than one feature is linked to that component, the installer installs the feature requiring the least disk space. Calling MsiGetComponentPath verifies that the key file of a component is present; however, it is still possible that other files belonging to the component are missing.

In this case, call MsiInstallMissingFile. The installer then resolves to which component the file belongs and installs the feature that is linked to the component that requires the least disk space. If the MsiGetComponentPath function...

dougj | 28 Sep 2007 | 0 comments

Here's a sample vbscript to use in Custom Inventory for Windows to convert a datetime stamp to NSDatetime format. It doesn't have all possible error checking, but it does have the main conversion logic. The entire vbscript will create an NSI file directly.

 Attribute definition: 

  objTextFile.WriteLine("<s:AttributeType name=""c1"" rs:name=""DateCreated"" rs:number=""2"" rs:keycolumn=""true"" mifAttrId='2'>")
  objTextFile.WriteLine("  <s:datatype dt:type=""dateTime""/>")
  objTextFile.WriteLine("</s:AttributeType>")

Call to function in rs:data section: 

  "c1="""  + nsDate(CStr(objFile.DateCreated)) + """" _ 

Function to convert the date: 

function nsDate(curDate)
  'remove " AM" and " PM" from the end of the value
  cd = Mid(curDate,1,len(curDate)-3)
    
 'Separate date & time values
  pos=InStr(cd," ")
  dt...
Andrew Souter | 27 Sep 2007 | 3 comments

There is a known problem that sometimes arises when using Summary report definition. The COUNT does not report correctly but when drilling down the next level of the report is correct. For example the summary level of the report might show 58 computers of a particular operating system but when you drill down there are 65 computers listed, which is the correct number.

The issue usually surfaces when selecting data from multiple tables. To limit the data to the resource type selected, a view called vResourceEx is used. When fields are selected from the other tables the combining of the data from the view and the other tables is not done properly. It is simple to correct the problem with just a few steps using the Advanced edit button which opens the Report Query Builder.

  1. Open a summary report
  2. Click Edit this report....
R-Vijay | 26 Sep 2007 | 0 comments

Hi All,

This is a microsoft MSDN extract, I have still posted it because many of us do not follow these rules while packaging .NET applications.

Hope it is useful.

The Installer can install, remove and update Win32 and .NET assemblies, including side-by-side and private assemblies in Windows XP. To avoid common problems, follow these rules when using assemblies:

General:

  • A component should contain no more than one assembly.
  • All of the files in an assembly should be in a single component.
  • Each component that contains an assembly should have an entry in the MsiAssembly table.
  • The strong assembly cache name of each assembly should be authored into the MsiAssemblyName table.
  • Use the Registry table instead of the Class table when you register COM Interop for an assembly.
  • Assemblies that have the same strong name are the same assembly. When the same assembly is installed by different applications, the...
daggy_b | 21 Sep 2007 | 9 comments

At our company we manage seven different computer models. They're all HP, but not all of them have the same chipset.

Here's a problem we ran into and, of course, how we solved it.

La Problema

We had problems using the same image for the HP DC5000, DC5100, and DC5700 models. I could get one image to work between the DC5100 and the DC5000, but not the DC5700. Then I tried another image and got it to work with the DC5700 and DC5100 but not the DC5000.

It turns out that Intel has drivers that work with the DC5000 and DC5100, and then another that works with the DC5700 and the DC5100, but no driver that will work between the DC5000 and DC5700. I did some research on Intel's website and looked at older drivers to confirm this.

La Solución

The solution for us is to have one image that works on all...