Deployment Solution

Hi,

 

I have a scripted OS install setup that would go through 12 steps. The 1st step is to prepare the disk, then deploy drivers and then install OS. It finishes the OS install and then reboots. The 4th step is to install the Windows Updates. But after the OS install it will show that the machine is offline in DS console. Although the machine is online. It is sitting at the login screen . If I login to the PC, it will activate the agent and the PC will come online under DS and then proceed to step 4. I am not sure why the machine goes offline after the OS install. I have tried 2 different models (Dell Optiplex 3010 and Latitude E5440), it does the same thing.

 

I am unable to restart the  "Altiris Deployment Agent" service on the machine remotely. Any help is appreciated.

Thanks !!

Does the msi install of your DAgent during the scripted install have the scripted_install=1 paramter?

Yes, The msi for dagent installs during the scripted OS and is set to 1. It seems that once I login to the machine the dagent is triggered and it comes online. I do not want to login to all pc when I am installing OS for 10-15 pc at a time. Please advise.

 

Thanks!

I would like to clarify, I am not using the builtin scripted OS. I am using replace tokens and the Run Script option to install the OS. The dagent install option is provided in the script and the answer file.

Script:

REM Create Altiris folder and copy DAgent
cd\
C:
md DAgent
cd\
copy "%ALTIRIS_SHARE%\Agents\AClient\dagent.msi" "C:\DAgent\dagent.msi"

 

Answerfile:

 

 

Please advise.

 

Thanks !!

 

 

I'm not sure what else to suggest. My image build is fully scripted and I've run it loads of times and the DAgent always starts on it's own once installed by setupcomplete. The only other things I can suggest are to log the msi install in setupcomplete and turn on agent logging as part fof the install. I don't have those swiches to hand but should be able to dig them out tomorrow.

You cannot see the DAgent until you login because your unattend.xml isn't installing the DAgent until you login.

And you said you used the scripted_install=1 parameter but I can't see it in your command line, but if you aren't installing the DAgent until you log in it's probably not necessary.

The built in Scripted install job uses setupcomplete in:

\Deployment Server\Deploy\WinOS005\sources\sources\$OEM$\$$\Setup\Scripts

to install the DAgent. This way it's installed after all the other Setup commands and config have run and DS can then do post deployment config without conflicting with Windows Setup.

I've amended the default command to turn on DAgent logging:

C:\DAgent\DAgent.msi /quiet server_tcp_addr=DSAlias server_tcp_port=402 scripted_install=1 LAUNCHUI=FALSE LOGERRORS=1 LOGFILE="C:\Program Files\Altiris\Dagent\DAgent.log" LOGINFORMATION=1 LOGSIZE=512

The DAgent msi is in:

\Deployment Server\Deploy\WinOS005\sources\sources\$OEM$\$1\DAgent

 

Andy - Looking closely at the Answer file, I see that the DAgent is installed at the FirstLogonCommand and is offline in DS until I login. Where do I specify the DAgent install in Answer file so that it installs the DAgent post OS install and I do not have to login for the DAgent to kick in the install.

 

The information you provided above is a great help. I will try it with the builtin scripted Task and update you.

 

Thanks !!

You don't need to use the built in scripted task, just use the $ folders in your source files with a setupcomplete.cmd file.