Video Screencast Help

Passing Package Server or Task Server to OS as Environment Variable - Office 365 Pro Plus

Created: 16 May 2014 • Updated: 21 May 2014 | 3 comments
This issue has been solved. See solution.

Does anyone know if there is a way to pass an Altiris Client machine's Package Server or Task Server to the OS as an environment variable automatically?  I do not want this to be statically set as machines move around.

The reason for asking is we are working on setting up deployment for Office 365 Pro Plus and within the configuration.xml file we would like to use \\%Taskserver%\path-to-updates for the machine to pull down Office updates.  We do not want 100 machines (or more) to go out to Microsoft and download 1GB or more each month on Patch Tuesday!  It seems to me there must be a way to get the OS to know or have set the task server or package server as an environment variable.

As a side note, in our environment, each package server is also a task server so either will work.

Thanks for any insight on either topic you can provide!

Operating Systems:

Comments 3 CommentsJump to latest comment

SK's picture

Why dont you disable the office update mechanism and use pms instead, as that uses the ps infrastructure?

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

Thomas Baird's picture

SK's advice is better, as is using a SWD task.

That said, there is a KB that will create a token for the Task Server which can be used in a task to do whatever, including setting an environment variable if necessary.  :D

Thomas Baird
Enthusiast for making things better!

jms97's picture

Thanks guys.  Since we are not using Patch just yet, we had come up with just what Thomas had said using setx to set the environment variable for the task server on the client.