I’ve got some action code that seems to work fine on 32-bit Windows machines (server 2003) but the download never seems to actually happen on 64-bit machines. Any ideas?
Here’s a piece of code that I’m trying to troubleshoot with:
In the above example I’ve got a data folder on my BES server in the downloads folder and there’s an xml file in there for a bunch of computers (one per machine - named machine.xml). On 32bit machines when this runs it downloads the file and then creates an ‘__appendfile’ with the text “data.xml exists”. On the 64 bit machines the files does not get downloaded and the __appendfile doesn’t get created at all. I would at least expected it to get created with the ‘does not exist’ string.
Any idea how I can troubleshoot what’s going with these 64bit machines?
So - further developments after looking at this all day.
I was under the impression that if you place a file in the downloads folder on the BES server and you ‘download’ the file in action script on a client the client isn’t going directly to the BES server to get the file but actually goes through the relay to get the file. Is this not the case?
It appears the machines that are failing are all in our DMZ and don’t have direct access to the BES server on our internal network and that’s why the file is not getting downloaded.
Am I missing something here as to how this is supposed to work? I need to be able to publish these files into the downloads folder on our BES server and then be able to download them to all clients (including the ones in the DMZ that only have access to our DMZ relay).
Any suggestions on what I’m doing wrong here? Or what I could try differently to get this to work?
If you use the “download” command, the agents will download through the relays as you describe (the agents will NOT download the file themselves directly from the source). However, if you use the “download now” command, the agents will download directly from the source.
Unfortunately, the “download” command doesn’t work with relevance substitution (because the relays pre-cache the files)… There isn’t currently a download command that will download through the relays with relevance substitution… So I am not sure what to tell you…
I think I found a solution. I’m going to put a copy of the xml files on both the BES server and on our DMZ relay and then have the policy actions set with applicability relevance so all the DMZ machines will run the policy that will download from the DMZ relay directly with “download now” and the rest of the machines will go directly to the BES server as they are now. Tried with one machine and it seems to work great. I’ll just have to rework the task into 2 Policy actions (as I want to download and evaluate these files every 4 hours on each machine).
Thanks for the info - it helped me get where I need to go.
I’m not sure I understand why you need two actions. Can you just use an if statement to run a different download command based on whether the currently selected relay is a DMZ relay?
Note that if you have a lot of clients and/or the size of the download is “not small”, by using the ‘download now’ command you are going to put a lot of direct load on your DMZ relay and server that the relay architecture is designed to alleviate. You should monitor the performance carefully.
Also, keep your eye out for the ability to use relevance substitution in download commands in our next release.
I am actualy putting this into one with relevance to determine the download location - good call. Right there are about 4000 files in the download folder with each only about 400 bytes (very small). I am interested in changes to future versions and the ability to use relevance substitution. I’ll keep my eye out for that.