I need to use TEM to deploy a variety of PowerShell scripts which generate txt file output written to a SMB path. This is all well and good when all servers are in the same authentication domain and there are no firewalls in the way, however I now need to expand the use of these scripts to cross both these boundaries where basically the only common pathways in/out is TEM and monitoring.
Is there anyway I can use TEM to somehow capture the output of these scripts and then use the TEM internals to transfer the files back to the main authentication domain/security zone and then write that output to this SMB path? Ultimately I am wanting to leave the PowerShell scripts intact as much as possible, so was thinking if I alter the output path of scripts to something like C:\Temp and then use TEM to grab the files, bring them back and them write them out to the intended SMB path.
Does this sound feasible? Is tehre a better way? How might I go about this?
The agents are running as local system so connecting to an SMB path that isn’t mounted as a drive is problematic as there are no credentials to use to connect to the SMB path. The SMB path could also be a wide open anyone can write mountpoint but that isn’t a good idea either.
Yeah, that is another hurdle/item to be cleaned up. Was thinking I’d break the requirement into at least two action scripts. 1st ActionScript would be for the existing PowerShell scripts writting out to C:\temp. 2nd would contain another PowerShell script to move the file over to the SMB path using a low privileged service account using this technique
after uploading, you can use some batch file to process the file from IEM server to SMB server. After this verify that file has been copied successfully and you can delete the file from IEM server.