Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Deployment Solution
Showing posts in English
CondorMan | 18 Apr 2008 | 3 comments

PowerShell is the new powerful scripting language created by Microsoft. You can install it to Windows XP and above and it is included in Windows Server 2008.

Here is how to run a PowerShell Script through Deployment Server.

  1. Create a new job.
  2. Add a Copy File task
    • The source path points to MyScript.ps1 on the Deployment Server.
    • The destination path is .\MyScript.ps1
  3. Add a Run Script task as the following:
    powershell -command "& { .\MyScript.ps1; exit $lastexitcode }"
    set ret=%errorlevel%
    del .\MyScript.ps1
    exit %ret%
    
    
Shadrocks | 16 Apr 2008 | 6 comments

A simple tip to track changes is to create a registry key under "HKLM\Software\\". When you run scripts or installations it is simple through almost all languages to add a string value with some information like install time.

By creating these keys, it becomes very simple to create logic in DS deployment scripts to make decision trees for future deployments and upgrades. This is also helpful for future auditing.

REG (REG /? from a DOS prompt to get help) is a magnificent tool to add registry entries with through DOS and it’s built into XP SP2. It can also be used to Query your key. Vbscript uses RegWrite and RegRead to perform the same actions.

Good luck with your new tracking options!

Shadrocks | 16 Apr 2008 | 0 comments

It has been through experience that we learn new ways to solve problems when we are confronted with them. Here are a few tricks that I have used to get around some Altiris DS limitations.

Use Add/Remove Programs to track distributions through Deployment Solution.

For image updates I utilize an Add/Remove Programs entry to track the image version. I can then track how many of each version has been deployed. I can also use this to deploy fixes to specific images if needed.

The entry can be added under “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall”. Just add a new key with the name of your choosing and place a string value called DisplayName in it with the information you want displayed. By doing this, you can use your DS console to filter for information you have deployed using the ‘Application...

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...