Deploy to NFS (Network Shared path) on WINDOWS

Hi,

I have a situation where I need to deploy files to a UNC path/Shared Path on a network. I have found the following link from the search results:

http://h20435.www2.hp.com/t5/HP-OpenDeploy/Deploy-to-NFS-Network-File-Share/m-p/258643#M18598

The solution in the above link suggests modifying the user context on which OD service runs. I'm wondering what is the impact when I do this. Will this disturb any of the existing deployments? Does OD service on Teamsite (OD Base) has any dependencies that it should run only on SYSTEM account?

Also, when I change the user context, is there any other permissions that I need to provide to the ad user (under which the service will run to be able to access the NFS) or any other configuration files that I should modify accordingly?

Thanks,

Nagesh K

Find more posts tagged with

Comments

Quick_Learner

oh! forgot to ask. is there any other alternative solution where in I could trigger a OD deployment instance with the required ad user so that the service still runs under SYSTEM but the deployment gets executed on the ad user context?

Thanks,

Nagesh K

nipper

This is more of an Windows/NFS issue rather than an OD issue. If a user logged in as an admin can have complete permission to create, modify and delete files and folders, then you are good to go. Often that is only available to a domain admin and certain users. In the Unix world (which NFS is part of) you can specify Root/Admin access to a mount, which means that Admin on the client has Admin rights. If you cna do that, you are golden.

If you move to run OD as a specific user, you are likely going to run into issues with existing deployments that have been working runder Admin, because the new user likely does not have permission to change some files.

Finally, there is a specific license for deployment to a network share. Make certain you have purchased that.

Quick_Learner

Hi Andy, thanks for the quick response. Unfortunately, I'm bit confused and so I will try to break this down a more granular level to be sure of getting this right.

Scenario:

I have Teamsite server (windows 2003) in which OD base is installed and that OD service is running under Local System account.

Desired Result:

This OD service should be able to publish content to a Shared/UNC path something like \\xyz.net\sharedpath\

Problem:

As OD service is running under Local System account, this deployment cannot happen due to the security context (obviously Local System does not have access to the shared/UNC path \\xyz.net\sharedpath\)

Questions:

When you mentioned "If a user logged in as an admin.....", which user are you referring to here? Local system account? Or the User who is triggering the workflow/deployment?

Yes, I dont like messing with the OD service. But is there any option where I could make the service talk to the shared path?

And finally, is there a way to automate the installation of OD rcvr with all default options? This is the main reason we are having to deploy to a shared path.

Thanks,

Nagesh K

nipper

I suggest that you talk to a Windows Admin and see if they can configure the UNC mount so that a local system account has the ability to create and modify everything on that mount. That *may* be possible, and yet it may not.

If that user cannot change that path, OD has to run as a different user. This is not an OD issue, it is a system configuration issue. That is why you need a sys admin involved.

There are methods to auto install/upgrade OD. You can also use OD, with DNR to update its configuration files, though I have never done that and am not certain the wisdom of it. This is more comples than you know and there are hard coded server names in some config files.

Quick_Learner

Thanks Andy. I will check with an administrator. I will update if I find any other solutions

Thanks,

Nagesh K