Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Deployment Solution
Showing posts in English
Nelo | 15 May 2008 | 6 comments

The size of the WinPE boot file looks scary when multiple clients are downloading it in a PXE boot. I have found a way to reduce the size of the boot.wim file to 33% less in size than the boot file that Boot Disk Creator creates and of course it downloads 33% faster. The end result should have a 110 Meg size WinPE boot file.

In order to create a play environment, create a second WinPE PXE configuration, meaning create a MenuOption that will not be the first WinPE. The first WInPE PXE configuration is set by default to MenuOption131. We want to play on PXE MenuOption160 or greater.

Also, this assumes that WAIK is installed in your DS server or the Altiris WInPE 2.1 installers were installed.
One more thing, this example is only for x86 proc. The batch file could easily be configured to make the changes for x64 and ia64.

The...

TilakGovind | 08 May 2008 | 3 comments

There are cases where an application needs access to a drive like H: to complete the installation of an application. Since, for example, you might be working on a VMware machine using a local user account.

Here's a trick to help you overcome this obstacle.

Instead of mapping your drive to a production drive, you can fake a drive on the machine using the Subst.exe command. You can fake an existing folder on the machine as a drive.

For creating an H: drive

  • Create a folder under "C:" eg. C:\test
  • Then use this command at command prompt:
    subst H: C:\test
    
    

Open My computer and you will see an H: drive there.

MyersW | 05 May 2008 | 14 comments

So the debate went through our office about what is the best pre-image environment... WinPE, BartPE, Linux or DOS. Consequently, we tried to do a complete analysis of many of the factors and determine what is really the fastest route to take. In the end, it all comes down to how quick we can get our imaging done and move on to other projects.

We took an older Compaq D5M as workstation to image and ran it through some tests. The workstation has a 10/100 MB NIC and was imaged from a server across a LAN link. All networking equipment in the link was at least 10/100 MB. We first pulled down a 4.5 GB image using each of the pre-image environments. What we found was...

Environment Time Approx. Avg. Speed
DOS 20:29 10-15 Megs
BartPE...
Kinetic | 24 Apr 2008 | 11 comments

I was setting up an NS server today for the first time and ran into some problems.

Everything installed just fine. Across the board everything looked green, but then I tried to setup up the proxy configuration in the console.

IIS crashes. I reset it and again it crashes.

What in the world did I do wrong?

I didn't RDP into the server using the /console switch:

mstsc /console

After that, I did a complete reinstall and everything went smooth.

This is VERY important when working with servers, especially an Altiris server. In fact, you should probably just set a shortcut to always use the /console switch. Seems like something we all take for granted, until the one time you don't use it and everything gets hosed.

UPDATE - With Vista the switch is mstsc /admin. - Thanks Caleywoods!

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