Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
dmorrison | 09 Jul 2007 | 1 comment

Sometimes it's desirable to create 4 collections for inventory tasks so software audits only occur on a particular day for 1/4 of the computers in the environment without dealing with the random execution of AexRunControl. Or your CIO wants to evenly distribute a software delivery over 10 days to reduce risk and you would like to avoid creating 10 dynamic collections.

One of the challenges we often face in Notification Server is creating collections that evenly divide computers into several groups to distribute inventory processing or software delivery.

The SQL script below provides a simple way to create a dynamic collection which will be roughly 1/4 of the computers in your Notification Server. It contains 2 variables: @Groups and @GroupNumber. To create another collection for the different 1/4's of your computers, change the...

riva11 | 22 Jun 2007 | 0 comments

Quello che cercavo era un metodo per installare nei miei computer l'Agente Altiris in maniera silenziosa. Per questo motivo, ho cercato la documentazione necessaria per trovare il metodo migliore. In Notification Server 6.0 SP3 Reference (e precisamente nelle pagine 15 e 16 per maggiori dettagli) viene spiegata la strada migiore per come poter fare questa operazione. La script seguente è quella che regolarmente utilizzo per questa installazione:

ECHO Installing Altiris Agent
aexnsc.exe -s -a ns="ServerName" NOSTARTMENU NOTRAYICON /s /NOADDREMOVE

Per la lista dei comandi, con dettagli relativi al loro utilizzo, fare riferimento alla documentazione citata in precedenza.

Per trovare il file "aexnsc.exe" , seguire il seguente percoso : "C:\Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\NS...

riva11 | 22 Jun 2007 | 4 comments

For correct application packaging, particular attention should be paid to check if all drivers are Microsoft Windows Certified. In fact, some issues can be tracked to the inclusion of unsigned drivers.

I use File Signature Verification utility (Sigverif.exe) to check -- in advance -- all drivers designed for Microsoft Windows and to identify drivers that are not certified.

This tool is a free standalone graphical program supplied in Windows XP and is an easy and fast way to detemine signed and unsigned drivers running in the computer.

Read more details and a short guide in the original Microsoft article: Unsigned Drivers - Use Sigverif.exe.

A short tip in this article in case you identify an unsigned driver:...

trb48 | 22 Jun 2007 | 4 comments

I really wanted a way to silently install Altiris Agent on my computers. So, I hunted around until I found out how. The Notification Server 6.0 SP3 Reference (check out pages 15 & 16 for all of the details) explains how to do this. Here is the script that I used to finally get it to work:

ECHO Installing Altiris Agent
aexnsc.exe -s -a ns="ServerName" NOSTARTMENU NOTRAYICON /s /NOADDREMOVE

To find out what all of the tags do, please see the above mentioned documentation.

To find the "aexnsc.exe" file, go to the following location: "C:\Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\NS Client Package" on your Notification Server.

riva11 | 22 Jun 2007 | 0 comments

Per una corretta creazione di pacchetti per la installazione di applicazioni, particulare attenzione deve essere data per verificare se tutti i drivers sono certificati per Microsoft Windows. Infatti, in caso di inclusione di drivers non certificati , questo può comportare il verificarsi di errori software.

Per evitare questo , uso l'utility File Signature Verification (Sigverif.exe) per verificare -- in fase preparatoria -- tutti i driver per progettati per Microsoft Windows e per identificare i driver che non sono certificati.

Questo tool è un programma grafico gratuito fornito in Windows XP ed è una semplice e sicuro metodo per identificare tutti i driver , sia certificati e sia non ceritficati, che sono eseguiti nel computer.

Leggere l'articolo orginale Microsoft per ulteriori dettagli e maggiori informazioni : Unsigned Drivers - Use Sigverif.exe...

trb48 | 21 Jun 2007 | 1 comment

Have you ever wanted to script a rotating backup through Deployment Solution? Have you ever wanted to unleash the power of the command prompt? Have you ever wanted to assign a drive letter to a folder? If you answered yes to any of those quetions, check out this sweet resource I ran across:

Batch File Recap

trb48 | 17 Jun 2007 | 0 comments

It seems if you dig deep enough you can tweak just about any part of Windows. (Useful if you're working to create a custom image for deployment). The problem is that most of those tweaks occur in the registry. That is a good thing, but who has the time to scour thousands of keys to find the solution to a problem?

I found the answer. I bumped into a post on MSFN that answered all of my questions. One of the contributors made a little package that contains tons and tons of registry tweaks. I was able to find some tweaks that are going to make their way into my image ASAP. Here is the link:

RegTweaks Collection v0.4

trb48 | 14 Jun 2007 | 1 comment

One important step in creating an image for deployment is getting rid of all of the extra programs that are installed. Sometimes this can be a difficult thing to do, because they don't show up in the Add/Remove programs list. If you want to get rid of something, but it is not on the list, what are you supposed to do?

I ran across an article today that answers that question. Here is the link:
Show hidden software in Add/Remove programs

The cool thing about this method is that you can reverse engineer it. You can add the "hide" to programs contained in the file, thus preventing the end user from removing the application.

jessedo | 11 Jun 2007 | 1 comment

When we first installed the Altiris Helpdesk solution we created a number of notifications to help enforce SLAs. Though this is a very useful feature of the helpdesk system, it makes for a lot of messages in your inbox every Monday.

We started looking for a way to limit the policies only to run on certain days of the week, but the shared schedules in the notification server don't allow for running on only specified days of the week. Instead, we solved the problem by making a simple modification to the WHERE clause in the SQL that controls the notification.


If you haven't modified the SQL in these policies before here is a quick rundown of how to do it.

  1. Navigate to the notification policy you want to edit.
  2. Click 'Edit...
WiseUser | 08 Jun 2007 | 6 comments

This tip actually covers several conditions and how they are used. It does not cover every situation but it should be able to guide you in the right direction to find the set of conditions you need for your solution with Wise installation products. These Conditions can vary for InstallShield-based applications.

These conditons can be used in custom actions, in Tables, and Component installations.

You can execute a custom action or make the component install using conditions as per the requirement.

  1. Action run only during Install
    Condition: NOT Installed AND NOT PATCH
  2. Action only runs during removal of MSI
    Condition: REMOVE
  3. Action runs during Install and repair
    Condition: NOT REMOVE
  4. Action runs during Install and remove
    Condition: There must be no condition
  5. Action calls EXE installed by MSI
    Condition:NOT Installed AND NOT PATCH
  6. Run on initial installation only:
    NOT Installed...