nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Owner column in OpenDeploy Admin UI

Lex

What controls the value that shows up in the "Owner" column on the OpenDeploy Admin UI? For some of our deployments it shows a user ID (e.g. "CORP\dluther"), however, for most is shows "SYSTEM". I'd like to have that column show the user ID of the user who submitted the deployment, but I can't figure out how that value is being set. I have made sure the owner of the deploy step on the workflow is set to the user and "iwodcmd start" is used to start the deployment. I'm baffled. Any help will be greatly appreciated. Thanks!

Find more posts tagged with

Comments

vikasp

What controls the value that shows up in the "Owner" column on the OpenDeploy Admin UI? For some of our deployments it shows a user ID (e.g. "CORP\dluther"), however, for most is shows "SYSTEM". I'd like to have that column show the user ID of the user who submitted the deployment, but I can't figure out how that value is being set. I have made sure the owner of the deploy step on the workflow is set to the user and "iwodcmd start" is used to start the deployment. I'm baffled. Any help will be greatly appreciated. Thanks!

If you start the deployment from OD UI directly then you will find owner as user ID(e.g. "CORP\dluther").If your deployment starts by the TeamSite workflow then you will find owner as "SYSTEM"

Lex

If you start the deployment from OD UI directly then you will find owner as user ID(e.g. "CORP\dluther").If your deployment starts by the TeamSite workflow then you will find owner as "SYSTEM"

Thanks for the reply. I'm not sure that's the answer, though, as none of these where the user ID shows up were deployed from the OD UI directly. We don't deploy anything via the OD UI - all of the submissions for deployment are done through the TeamSite UI or via .Net web apps we have written.

Adam Stoller

Thanks for the reply. I'm not sure that's the answer, though, as none of these where the user ID shows up were deployed from the OD UI directly. We don't deploy anything via the OD UI - all of the submissions for deployment are done through the TeamSite UI or via .Net web apps we have written.

I suggest you spend a bit more time closely monitoring the system so that you can check directly after a deployment has been made and note:

Once you collect a decent sample of data (10+ deployments?) you can then start drawing conclusions as to cause-and-effect.

Vendim Birbili

If you start the deployment from OD UI directly then you will find owner as user ID(e.g. "CORP\dluther").If your deployment starts by the TeamSite workflow then you will find owner as "SYSTEM"

Is there anyway to change the Owner of the Deployment When it starts by the TeamSite Workflow? we are deploying files using OD from one UAT to DEV and the owner of the file shows as "system". we want to show as the user that initiate the workflow or maybe some generic user instead of System.
any help or Guide appreciated.

font.png

fonttest.png

Adam Stoller

Please read this post and then try posting your question again.

Vendim Birbili

Please read this post and then try posting your question again.

Sorry about that!

We are using TS 7.3.2 Windows SErver 2008 R2. we have created a workflow that user deployment task to push code from DEV to UAT/PROD. The files when they go to the received Side are marked as modifed by System and also the owner of the file is "System". Is there anyway to handle that? I am the owner of the task for the workflow and deployment so why the files are passing as modified by System?

any help or Guide appreciated.

nipper

Read the OD manual - there are configuration file settings specifying target file ownership/permissions/etc - Use them

Vendim Birbili

I did follow all the manual but seems it doesn't work. I have PreserveAcls =yes on the deplyments configs for the target but still the files are showing as modified by system....

nipper

preserve acls will work if you share the domain between source and destination. I.E. the file is owned by DOMAIN\andy on the sender and the DOMAIN\andy is a valid user on the receiver.

Vendim Birbili

Yes the user ( domain\user) is both on the sender and receiver. Also the sender and the receiver are on the same domain. Still no luck.

nipper

Look through the sender log, in the beginning you will see the parameters it is using, check that

The relevant portion should look something like this:

deployment=.push.MYDEFINITIONNAME.runtimeserver
ts_file_list_based
file_list=C:\Windows\Temp\deploytask-filelist-1910065215477841470.txt
area=/default/main/branch/STAGING/
local_directory=.
user=myuser
group=mygroup
file_perm=755
dir_perm=755
date_different
ignore_acls
remote_directory=\app\LSDSdocroot
;
;

That is a Linux RTE not DOS, so the parameters will be different.

nipper

One other point,

If you deploy to an external replication farm defined in odnodes.xml and you define path in odnodes, you should permissions in odnodes as well, rather than in the deployconfig.xml

Adam Stoller

Jumping back to the beginning of this thread - having taken a second look at the title...

You're looking at the OD Admin UI.
Are the deployments initiated:

If more than one of the above - are you seeing any pattern between the way the deployment was initiated and the information that shows up in the OD Admin UI?