Topics created by Jonathan.Engstrom

Hi @MaxCascone , No problem; I deleted the "alternate" accounts that were auto-created, and then I changed your forum email to the new one. Cheers, Alana

Hi @Jonathan-Engstrom, Have you reviewed the Backing up Otter documentation? We outline how to backup and restore a ProGet instance in there. If you are missing configurations, it shoulds like you may not have copied all of the files from your git repository or the configurations were not stored in the Git raft. Do you still have access to your old server? You could also navigate to Administration -> Rafts and download your Git raft as a zip file as well. Thanks, Rich

Hi @Jonathan-Engstrom , Have you tried wrapping your PSEnsure inside of a with block to force everything to run as a specific Resource Credential? Example using a resource credential named AdAdminResourceCredentials: with credentials = AdAdminResourceCredentials { PSEnsure ( Key: RSHStuff, Value: True, Collect: >> $ErrorActionPreference = 'SilentlyContinue' $TargetOU = 'Users' $Value = (Get-ADComputer -Identity $env:COMPUTERNAME).DistinguishedName -match $TargetOU $CurrentValue = (Get-ADComputer -Identity $env:COMPUTERNAME).DistinguishedName ((($Value -eq $true) -and (($env:COMPUTERNAME) -match 'MyComputerName')) -or ($env:COMPUTERNAME -notmatch 'MyComputerName')) >>, Configure: >> $samAccountName = $ServerName $newOU = [adsi]"LDAP://$TargetOU" $comp= ([adsisearcher]"samaccountname=$($ServerName)$").FindOne() Write-Host $comp.GetDirectoryEntry() >>, Debug: true, Verbose: true ); } Please note that my PowerShell in collect and configure is not 1 to 1 with yours, I would replace my PowerShell script with yours in those two properties. I also was talking with one of the solutions architects on a similar Otter execution question. He suggested that sometimes it is easier to figure out PowerShell issues by running PSExec under the local system account and attempting to run your PowerShell commands that way. It will sometimes show you more detailed errors than Otter. I would try running PSExec -s powershell, which will open up a PowerShell console as the local system account, and then typing in the lines of PowerShell you have had trouble with. Thanks, Rich

Hello; For this, we recommend just doing a Backup and Restore. Of course, the Detatch/Reattach is effectively the same thing, but don't forget the config. For the Git-based raft, the Database just contains the connection information to the Bitbucket repository... so it will just come over with the database.

Alright, fair enough. As I use Otter almost exclusively for checking for compliance, I will look forward to this. Nontrivial asks are always the best ones, right? :D

Thanks for tracking those down, I updated owner on them :)

We hope to include this ability in a future release, but it's a bit more complicated to get the details worked out. For now, just uninstall, then reinstall (pick version you want) will work.

In what context would this protocol be used? My understanding is that BITS is used for background/asynchronous transfers, and in the common Otter use-case, the package needs to be available on the server in order to progress through a configuration plan, therefore the only benefit I can see is the network throttling.

So I looked over OT-331, and while close, I am looking for each role to report the status of each server that has that role assigned to it, and whether it has drifted or is current. Thanks!

Alright, I have my one token agent I had to update. Thanks!

hi Jonathan, can you help me with a test case on the duplicate server issue? Are you trying do an infrastructure import that has the same server name defined twice in the same JSON document?

There haven't been any other feature requests for this, and we haven't researched the feasibility of doing it; however we did add Impersonation and Process Isolation, both which were in-demand features.

I actually added this but it wasn't released as part of the beta; it will be an option in the Status filter e.g. "Agent error", "Collect/remediate error", and "Any error"

Hello Jonathan, We use Proget to deploy our PSModules. The deployement is driven with an Otter PSEnsure fonction- check if module exist with a specific version, if not deploy - Each new server is linked to an Otter role and after remediation, the module is installed. To update the module, we change version number in a otter variable. Otter remediation make the job We call PS function from local script or from Otter plan directly or from module. Don't know if this your need but it is working fine for us.

Basically, you would create a Git-based raft in both instances of Otter, and have them both point to the same Git repository. The biggest gotcha would be that both instances can potentially update the raft, but as long as you're aware of that it wouldn't be a problem.

Got it! Then this would likely fall inline with an upcoming major feature, and the communication between Otter servers ("main" and "secondary" as you describe) would be done using API/HTTPS/Web requests, in a direction of ("Publisher" -> "Listener").

Just as an FYI, we're continuing our investigation and exploration of this under ticket EDO-5623 UPDATE: we've addressed a lot of these in the current version of Otter.

Adding for ideas: Will need cmdlets to create, edit, delete, start and stop configuration and orchestration work. Allow to accept pipeline input. That way I can schedule at that time, to run an orchestration job, pick the servers based on the results of the orchestration, and run a job at that time for those servers, environments, or roles that fit the criteria.

John, while on the subject of execution ID's and such, during the logging of a psensure, can we add the psensure key to the log so it always outputs what it is checking and validating? How it is now: INFO : 2018-12-11 20:31:07Z - Configuration drift detected. DEBUG: 2018-12-11 20:31:07Z - Adding to execution plan. DEBUG: 2018-12-11 20:31:11Z - Collecting configuration... DEBUG: 2018-12-11 20:31:11Z - Comparing configuration... INFO : 2018-12-11 20:31:11Z - Configuration matches template. DEBUG: 2018-12-11 20:31:14Z - Collecting configuration... DEBUG: 2018-12-11 20:31:14Z - Comparing configuration... INFO : 2018-12-11 20:31:14Z - Configuration matches template. and so on. Maybe it could log something like "Collecting configuration <key>" and "<key> matches template". That way it would make each line meaningful and bring more value into keeping the logs. Eventually I would like to have a way to save a copy of the txt execution into servicenow so we have a record of it in change management system as well. The url you shared previously will help in doing that I think. This improvement would help as documentation for each change. Thanks!

Ticket is submitted along with additional information