Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Deployment Solution
Showing posts in English
riva11 | 28 Mar 2008 | 0 comments

Se non usate un print server per la gestione delle stampanti e avete la necessità di uno script per l'installazione di una stampante di rete in workgroup, allora consiglio di usare questi due semplici comandi. Nella nostra organizzazione abbiamo creato con successo con questi due comandi un unico job di Deployment Server con successo. (Notare che questi comandi funzionano per Windows XP (non è supportato Windows 2000 e non sono ancora stati verificati per Windows Vista):

  1. Per creare una porta stampante:
    cscript //NoLogo %SYSTEMROOT%\system32\prnport.vbs -a -r IP_192.168.1.100 -h 192.168.1.100 -o raw -n 9100
     
     

    Nota:

    • Sostituire l'indirizzo IP address al posto di 192.168.1.100.
    • 9100 è la porta.
  2. Per installare il driver stampante in questa porta usare:
    RUNDLL32...
lamiet | 28 Mar 2008 | 1 comment

If you are not using print servers to manage printer installs and need to script the install of networked workgroup printers, you can use these two simple commands to get the job done. We use the combination of these two commands in a single Deployment Server job with great success. (Note that these work for Windows XP (not 2000) and have not been tested with Vista):

  1. To create the printer port:
    cscript //NoLogo %SYSTEMROOT%\system32\prnport.vbs -a -r IP_192.168.1.100 -h 192.168.1.100 -o raw -n 9100
    
    

    Notes:

    • Substitute your printer's IP address in place of 192.168.1.100.
    • 9100 is the port.
  2. To install the printer driver on this port use:
    RUNDLL32 PRINTUI.DLL,PrintUIEntry /if /b "Lab Printer HP2300" /f \\%DSSERVER%\express\printers\HP\2300\hpc2300b.inf /r "...
riva11 | 18 Mar 2008 | 0 comments

Hai mai avuto la necessità di cancellare una partizione in WinPE? Forse il computer aveva una precedente immagine di Vista e adesso la nuova immagine non è possibile installarla. WinPE ha una utility molto potente , DiskPart , che consente di gestire partizioni. E' complicata all'inizio ma seguendo le istruzioni è possibile creare e cancellare partizioni in pochissimo tempo .

Da prompt dei comandi di WinPE , digitare "Diskpart.exe". Questo comando avvia il prompt comandi all'interno di Diskpart.

Per cancellare la partizione primaria usa i seguenti comandi :

  • List Disk
  • Select Disk 0
  • List Partition
  • Select Partition 1
  • Delete Partition override

Modifica il disco o il numero della partizione per adeguare l'esempio al tuo ambiente. Usare cautela quando si esegue il comando di cancellazione perchè questo cancellerà ogni cosa dalla partizione attiva. In caso di dubbi, ogni comando ha disponibile un aiuto in...

riva11 | 06 Mar 2008 | 0 comments

Nel caso sia stato creato un ambiente di pre-boot Linux (PXE, Automation BootDisk, Network BootDisk, ecc), ma per qualche problema non viene montato un disco che punta ad una condizione sul server DS. Come è possibile collegare manualmente da prompt"/#" una condivisione in modo da fare un test?

Eseguire il comando seguente:

"mount -t cifs -o username=[nome utente],workgroup=[workgroup/dominio],password=[password] //[dsname/IP/FQDN]/express /mnt/ds"

Se il comando ha avuto successo, viene visualizzato un prompt "/#", altrimenti si ottiene un avviso su schermo o un messaggio di errore.

Per controllare che sia stato montato correttamente, digitare "mount" che visualizzerà la lista di tutte le cartelle, device, ecc.

"cd mnt/ds" fornisce inoltre l'accesso alla cartella condivisa del server DS.

Digitando successivamente il comando "ls" sarà fornita la lista delle directory della condivisione sul...

SK | 05 Mar 2008 | 5 comments

A Linux pre-boot environment has been created (PXE, Automation BootDisk, Network BootDisk, etc), however, when it runs it fails to mount to the DS. How can the mount process be tested from the "/#" prompt?

Run the following command:

"mount -t cifs -o username=[username],workgroup=[workgroup/domain],password=[password] //[dsname/IP/FQDN]/express /mnt/ds"

If this action is successful, the "/#" prompt will return, otherwise an error or usage screen will be returned.

To check the mount, type "mount" which will display all mounted devices, directories, etc.

"cd mnt/ds" will provide access to the DS mount point.

Typing "ls" will provide a directory listing of the DS mount point.

scotthansenpaysoneast@gmail.com | 05 Mar 2008 | 2 comments

You just installed a Hot Fix that included a new AClient and you notice that as Auto Update is enabled, it only updates 15 clients at a time. You may find yourself asking, "How can I change the AClient Auto Update value from 15 clients at a time to a different value?"

When a newer version of AClient is installed into the Deployment Share, the managed computers automatically update their copy of AClient to match this newer version. Starting with Deployment Solution 6.5 Hotfix 2, the AClient Auto Update feature only updates 15 computers at a time, to reduce the network traffic used when a new version of AClient is installed.

To view or change the auto update value:
On the computer that Deployment Server is installed on, run Regedit.

Locate and select the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris eXpress\Options

Locate and double-click the UpdateAgentsConcurrentlyMax DWORD entry...

scotthansenpaysoneast@gmail.com | 03 Mar 2008 | 1 comment

You can reduce the size of your PC Transplant Solution folder by removing unnecessary directories or files, depending on your needs. You might find that you don't need to include many of the utilities that shipped with PC Transplant Solution. You might be surprised how little it takes to have the application work for you on your present or another server.

Try removing some of the following items and see if the program still works the way you need it to:

  • The AClient folder is 5.84 MB, and contains the 6.0.47 version and will not be needed if aclient will already be installed or will be managed currently by the Notification Server or Deployment Server.
  • Various language folders range from 7.5 MB to 8.29 MB. If you only need the English Language, only keep it and then your folder will be 40.3 MB smaller.
  • The License...
CondorMan | 29 Feb 2008 | 5 comments

If you plan on installing Vista Service Pack 1 when it is released (highly recommended), you might want to run the cleanup command afterward.

To do this, open the run dialog (Win-R) and type "vsp1cln.exe" (without quotes) and press enter.

This will remove the ability to uninstall the service pack (so make sure to test everything before running the cleanup), and it will cleanup 1GB worth of data off of your hard drive.

gbromage | 08 Feb 2008 | 5 comments

Recently, VMware released their Update Manager to handle patch management of ESX servers.

For those of you who haven't implemented it, here's a setup of reasonably robust scripts to do the patching via the Deployment console.

Use the ESX-100xxxx patch number as the job name.

1. Check to see if the patch is installed

#Check to see if this patch is already installed
#!/bin/sh
esxupdate query | grep %JOBNAME%

Set this job to STOP on a "Success" (exit code zero), and Continue (sucessfully) on exit code 1.

grep will return exit code 0 if the text is found (ie patch is installed), 1 if it is not.

2. Check that the host is in maintenance mode

#Check maintenance mode status
#!/bin/sh
#There needs to be a 2 minute delay, just in case this is running straight after another patch which caused a reboot
sleep 120
test `vimsh -n -e hostsvc/runtimeinfo | grep 'inMaintenanceMode' |awk '{print $3}' | sed 's/,//'` = true

...

ianatkin | 07 Feb 2008 | 0 comments

Many organizations can configure local environment variables on their systems that can detail useful information such as asset details, location or even printer configuration.

When imaging computers to fix issues, this information has to be uploaded to the server, so it can be restored as a post-imaging task.

The most obvious way is to run a script on the client which,

  1. Maps a drive to the Deployment Server
  2. Exports the selected environment variables as a batch file env-%ID%.bat in \Express\temp

Using this approach requires,

  1. Your Clients and DS to be in the same Domain, or a common credential to be shared across your PC estate
  2. Windows Networking to be reliable... ;-)

The Workaround

A workaround which we have found to be quite robust is to run a job before imaging a client computer which exports the required environment variables to fake Add/Remove program entries. These can then be picked...