Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Deployment Solution
Showing posts in English
jjesse | 12 Sep 2008 | 0 comments

Just a quick note, that if you are imaging and deploying SUSE Enterprise Linux on VMWares's ESX server you need to be on the latest version for it to work correctly.

If you are running 3.1 when you deploy the images, eth0 does not come active after the reboot and you must manually reconfigure it through YaST.

If you upgrade your ESX box to 3.5 the deployment of the image functions correctly.

dnorris | 10 Sep 2008 | 10 comments

BIOS updates can be automated along with your standard deployment routines. A single job can be used regardless of the model being deployed.

We'll first make use of the Condition feature on DS jobs and then of a command-line parameter available on Dell BIOS update files.

Create a new job in your Deployment console, click the Setup button in the Condition section and create a new condition. Name the new condition to describe the computer model.

This example shows the condition for a Latitude D630.
For the...

CondorMan | 29 Aug 2008 | 3 comments

If you ever need to script NTFS permission changes, SetACL is a powerful alternative to CACLS. Here is a command line that will use SetACL to grant full control to the Administrators and System accounts on folder and all subfolders:

SetACL.exe -on "C:\Program Files" -ot file -actn ace -ace "n:administrators;p:full" -ace "n:system;p:full" -actn clear -clr "dacl,sacl" -actn rstchldrn -rst "dacl,sacl"

erikw | 29 Aug 2008 | 0 comments

In the deep, dark recesses of my harddisk I found this very useful demonstration Joel Russel created.

It explains the installation for the DS 6.8 console and the difference for the Thin Client version. Watch and enjoy.

CondorMan | 28 Aug 2008 | 0 comments

The DSWeb Console and NS Console require .Net Framework 1.1 to be registered with IIS.

A quick way to fix this (or script this for multiple installs) is to run the following command:

%SystemRoot%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i -enable

CondorMan | 25 Aug 2008 | 1 comment

To silently install .Net Framework 2.0 with SP1, follow these two steps.

  1. Download NetFx20SP1_x86.exe from Microsoft
  2. Distribute NetFx20SP1_x86.exe via Deployment Server or Software Delivery Solution with the command-line parameters: /q /norestart

If the silent install finishes with return code 3010, that means that a reboot is required.

CondorMan | 25 Aug 2008 | 0 comments

If you need to silently install the .Net Framework 1.1 to multiple computers, you can follow these two simple steps.

  1. Download the Microsoft .NET Framework Version 1.1 Redistributable Package (dotnetfx.exe)
  2. Crete a Software Delivery Task or Deployment Server Distribute Software Task that runs dotnetfx.exe with the command line parameters: /q:a /c:"install /q"
Dan Waksman | 20 Aug 2008 | 3 comments

If you are beginning to test Vista, and are looking into the various activation methods, you will quickly learn that KMS activation requires a minimum of 25 PCs. Therefore you may need to begin testing with a MAK key and later switch to activating against a KMS server.

In order to switch back to KMS activation, use the following command lines for Vista Enterprise:

slmgr.vbs /ipk VKK3X-68KWM-X2YGT-QR4M6-4BWMV
slmgr.vbs /skms SERVERNAME
slmgr.vbs /ato

For Vista Business, substitute the key with YFKBB-PQJJV-G996G-VWGXY-2V3X8. See for more details on Volume Activation 2.0.

If you need to switch back to a MAK key,...

Dan Waksman | 07 Aug 2008 | 0 comments

Previously I had been using netdom.exe from the Server 2003 Support Tools to join computers to a domain automatically. However, using VBScript and WMI is slightly easier because it doesn't require any extra files.

The example below will create a new Computer object in the Active Directory OU that you specify. The following variables should be set according to your own environment:

strDomain - domain name
strUser - user id with rights to create a computer object
strPassword - the password for the user id specified in strUser
strOU - the Active Directory OU where the Computer object will be created, in FQDN format

strDomain = "DOMAIN_NAME"
strUser = "USER_NAME"
strPassword = "PASSWORD"
Set objNetwork =...
Dan Waksman | 06 Aug 2008 | 1 comment

If you have created a Vista image using a Scripted OS Install task, then you most likely left the command line to install the DAgent: C:\DAgent\DAgent.msi /quiet server_tcp_addr=%DSSERVER% server_tcp_port=402 scripted_install=1 LAUNCHUI=FALSE

However, you have now created an image that will connect the DAgent to whatever Deployment Server the image was created on. If you are using multiple Deployment Servers and are trying to use the same image, obviously this will be an issue. To work around this, I created a task to run immediately after a Distribute Image Task in WinPE pre-boot automation, which switches the DAgent to the correct Deployment Server, by modifying the registry:

REM Point DAgent to correct DS

reg load HKLM\TEMP c:\windows\system32\config\software
reg add "HKLM\TEMP\Altiris\Client Service" /v DSIp /t REG_SZ /d "%...