zenwsimport resolution problem 1

[LawnBoy]

Researching ZFD 4.01, hope to implement soon. I see a problem resolving zenwsimport.

I'm a small subnet on a rather large WAN. DNS is handled by the WAN carrier. Another agency is already using Zen, consequently zenwsimport resolves to their server and that won't change (their needs rank higher politically than mine). Cooperation between our two agencies is, shall we say, highly unlikely.

I really don't want to keep track of 120 hosts files, but do I have any choice?

Any chance this name resolution could be handled by SLP?

Thanks.

 

[ITsmyfault]

FWIW
What we did here was push out a host file update as a 'force run' job. You can just add a line to their hosts file and voila. If it ever changes, you can create a job to remove it, or replace it. Welcome to Zenworks.

Create an application object, make it a force run.
Under "distribution options" select "text files" from the drop down. Choose hosts (browse to it with the FILE button) and add the line you want by clicking on ADD-->CHANGE add text to the file, add text to the beginning of the file, and then tell it what to add. Associate it with a container or group or whatever.. Under Run Options - Application --> check off "run once" and "install only" (this is also where you set the 'force run') then under 'availability'-->system requirements, enter the logic of which boxes this should go on. Our basic thing is
show: false
Type: OS Version
Ubject: WinNT/2000
Operator: >=
Value: 4.0.x

We only have a couple of NT machines left and the rest are 2k so this is a "do them all" bit of code for us. YMMV.

Clients have to have NAL running, or it can be run as part of a login script or manually etc.

 

[LawnBoy]

Heh, I do still have the pre-Zen mindset, don't I? AAAAUUUMMMM...

Thx.