This is an interesting feature request; from Otter's early design, we wanted to support environments with complex communication restrictions.

Our idea was to accomplish through an agent relay of sorts. Basically

                                         --->  [Inedo Agent A]
[Otter] ---> [Inedo Agent Relay Service] --->  [Inedo Agent B]
                                         --->  [Inedo Agent C]

For example, you would configure a server in Otter like:

• Server Name: server123
• Host Name: server123.client.corp
• Relay: bridge-server.local

In this case, bridge-server.local can talk to server123.client.corp, where as the Otter server cannot. However, if the Relay Service was installed on the bridge-server, then Otter could still orchestrate server123.

Is that what you were referring to?

Dear Alana,

I think your organisation should take problems of your users more seriously, because this issue has been open for two months. You said it was a problem on our side... but now i see in the releasenote from proget 5.1.11 it was a problem on your side.

https://inedo.com/proget/versions#v5.1

It is fixed now.

Ok i will get back on this after i checked with our network department.

The strange thing is when i access the url with an internet browser on the machine where proget is installed i get a nice XML.

<?xml version="1.0" encoding="UTF-8"?>
<proget currentVersion="5.1.5"/>

So i think it is a ProGet issue.

https://inedo.com/pg/ was set in the advanced settings, ihave changed it to https://inedo.com/pg/update. After a restart from the service, the problem still occurs.
I will ask the network deparpment.

We still have this issue.. restart of the service does not fix the problem.

The update checker was working in our Proget enviroment for a while today we get this:

INFO: Checking for updates from inedo.com...ERROR: Error checking for updates: System.Net.WebException: The remote server returned an error: (411) Length Required.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<GetUpdatesXmlAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<ExecuteAsync>d__1.MoveNext()

What could this be?

Product: ProGet
Version: 5.1.4

Alana,

Thank you for answering, but would you be so kind to give aswers to all of my questions?

Can proget run properly on a domain account that is not a member of the local administrator group?
If yes what are the minimal requirements for the account?

Hi,

I work at a company were i am implementing proget in our ALM enviroment.
I installed Proget on our acceptance enviroment to see how it should run within our organisation.

On the support page i tried to find the minimum requirements for running Proget with a windows domain account (service account) found some recommendations and implement them.

I want to run Proget in a following way.

• Web Server IIS
• Windows Authentication
• SQL Server Database
• Running under a domain service account
• Installing Proget when logged in with a domain account which is member of the local administrator group.

Our company has UAC enabeled on all our servers and we have to install progams on the D-drive.

I got proget running with some configurations on version 5.0.13 a couple of weeks a go and it looked fine.

• gave the service account access to specific folders, log on as a service and made it owner of the database
• gave iisusr access to the web folder

All seem to be working fine until i wanted to update to proget version 5.1.3 using the inedo hub. I got an error that the installer had no access to a specific folder on the d-drive.

After that i could fix it manualy and got proget working again after a reinstall with the offline installer, but this is not a good method to update ProGet every time.

Putting the proget service account in the local administrator groups solves the issue but our security officer is not happy about that.

So my question is:

Can proget run properly on a domain account that is not a member of the local administrator group? If yes what are the minimal requirements for the account?

Kind regards,

Gert-Jan Spoelstra

Product: ProGet
Version: 5.1.3