Deployment Solution

As the title states I'm wondering if the token is available in Linux PE on DS 6? After testing a few times with a wait job I've had no luck mapping it in the Linux Pre OS. I went in through the PXE Config Utility to change the settings for the pre os. I'd assume I'm either doing something wrong or it's only available for WinPE. If so, is there any way of going about including it. I've found the article below among a few others.

 

https://www-secure.symantec.com/connect/articles/readydynamic-mapped-shares-using-pxe-tokens

Happy New Year b3tts32 !!

This isn't a database token, it's an environment variable.  Within linux, you can access this as  $ALTIRIS_PXE_IP$

Kind Regards,
Ian./

Happy New years to you too! You have no idea how much easier you've made life with the imageinvoker and your input here on Connect.

 

Perfect! That's exactly what I was looking for. Do you know where I might be able to track down a list of the other enviromental variables?

 

Also I've been following a few post of yours about getting local Package Servers setup as image hosts as well. You mentioned using the %SITE% token and populating the field in add/remove programs somewhere through cmdline.txt. I've got that part down and I imagine I can use custom inventory to pull that info in, my question is how you populated the info into sql? Or do you have a script of some sort that you ran locally on the deployment server? I've found the table and column that it belongs to but I kind of stopped there. You mentioned something about writing an article about it but I couldn't find it.

For linux... just type 'set' in the terminal and you'll see all the environment variables which are configured within Linux automation. Here's a few of the Altiris related ones which are set, as taken from my test setup...

 

 

 ALTIRIS_BDC=BDC6.9.9172.371
ALTIRIS_BOOTDEVICE=PXE
ALTIRIS_BOOTDISK=
ALTIRIS_BOOTTYPE=AUTOMATION
ALTIRIS_DS_SERVER=ALTIRIS-DS
ALTIRIS_DS_SHARE=eXpress
ALTIRIS_PREBOOT=LINUX
ALTIRIS_PREBOOT_ID=LINUX_X86
ALTIRIS_PREBOOT_NAME=LinuxPE
ALTIRIS_PREBOOT_NAME2=LinuxPE
ALTIRIS_PREBOOT_SUBSUBTYPE=LINUX
ALTIRIS_PREBOOT_SUBTYPE=LINUX
ALTIRIS_PREBOOT_UID=LINUX_X86
ALTIRIS_PROCESSOR=x86
ALTIRIS_PXE_BOOTPATH='MenuOption130\X86PC'
ALTIRIS_PXE_CLIENTMAC=000C291F60BF
ALTIRIS_PXE_ID=130
ALTIRIS_PXE_INTERFACE=eth0
ALTIRIS_PXE_IP=192.168.157.100
ALTIRIS_PXE_OID=130
ALTIRIS_PXE_RID=130
ALTIRIS_PXE_SERVER=altiris-ds
ALTIRIS_SHARE=/mnt/ds
ALTIRIS_UNC=//ALTIRIS-DS/eXpress
ALTIRIS_VER=DS6.9 

 

In the main, not very exciting....

For the site server thing -yes I should get my finger out and document this. Was held up by a slight loss of work from a harddisk failure and I feel a certain anguish having to re-write some of my unpublished work from scratch. Losing data is painful, not to mention really, really stupid.

Moving on from my data berevement,  I'll have this site server image share piece within PXE posted within the next couple of days ;-)

Kind Regards,
Ian./

I should have said of course $ALTIRIS_PXE_IP or ${ALTIRIS_PXE_IP} -the second dollar is in error!

Yeah that's never fun. I've been living on the edge myself and don't have a few of my things backed up. I'm definitely looking forward to your article. I'm currently working on getting my test environment (esxi host) in order so I can separate 7.2 beta testing and 6x remote image testing. I'm looking at dd wrt to separate my guests into separate vlans to separate the traffic.

Article in progress!

Any progress on the article? I'm anxiously awaiting!

Ah...Many shiny distracting things...

I have deftly caught this falling item and put it back on my plate.... will put in another couple hours of hard labour on it tomorrow!

Article complete and in the pipe with Ohzone. Can't believe it took nearly 2 months. I did mention an abundance of shiny distracting things, right?
 

This is the article ianatkin is referring to:

WAN Nirvana with Deployment Server 6.x

...so many shiny distractions... great job as always Ian!

Thanks!
Cheryl