Topics created by Jonathan.Engstrom

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

Thanks, I've filed this as OT-275

There have been no changes to the way our products connect to databases in many years, so this is unrelated to an upgrade. However, it seems to be some sort of indication that SQL Server must be overloaded, or a network problem. This can typically be diagnosed / reviewed by the SQL Server DBA, who can see incoming connections, and which queries are taking too long, etc. But in my experience, just restarting the server you have SQL Server installed on fixes it like 80% of the time.

Apparently this was updated in BuildMaster but not Otter, here is the documentation for the updated version that also applies to yours, substituting $CredentialProperty for $GetCredentialProperty: # ProGetCreds is an instance of Inedo Product Credentials (i.e. InedoProduct::ProGetCreds) with 'Allow encrypted properties...' checked set $key = $CredentialProperty(ProGetCreds, ApiKey); set $host = $CredentialProperty(ProGetCreds, Host); Log-Debug Getting ProGet package from $host with API key: $key; ProGet::Get-Package( Credentials: ProGetCreds, Feed: hdars-1k, Name: hdars, Directory: $WorkingDirectory ); Additionally, I will notify our product director to add an issue to fix this in Otter (it would still be backwards compatible, but the canonical name would become $CredentialProperty)

Those are handled at different abstraction layers; the agent code doesn't have any knowledge of the context its being run in (i.e. OtterScript, the Service, etc). That's the intent of that "with credentials" setup, to allow this information to pass down.

Alright, after messing around with that information, I was able to get it to work. I am able to update the variables. Interesting thing is that it doesn't appear I can change just one variable, I have to change all of them, or at least enter all of them as they are? Thanks for your help!

For Ensure-RegistryValue, you can use the Kind property to control the type: Ensure-RegistryValue ( Name: 2100, Value: 3, Kind: DWord, Hive: LocalMachine, Key: SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3 ); Valid values for this property are listed here.

Hello, after trying for a half hour, I was not able to get the $PSEval to successfully do any math operations for me, but something I hadn't tried in my hours of troubleshooting this is try putting the variable last and the number first, and the PSEnsure worked great at that point.

Dean, that's great news! Thanks!

Dean, thanks for the reply. I am hoping it makes it into this release, as each server I import I have to go into the properties of each one manually and change the raft from not configured to default. While I am trying to build traction for this product, this process of touching each machine does not give a good impression. Thanks for the update!

Since I wanted all of my values in the array to be true to have success in my PSEnsure I thought of different ways I could do this. I settled on counting the items in the array, and using the fact that $true -eq 1 and $false -eq 0 to build a value that should match the count. I added this to the end: $array.ForEach({if ($) {$val += $}}) $array.Count -eq $val Thanks for your help!

I'm not sure I totally understand what you mean by "had the path of where I stored the PoSh script"? Basically, when you create an asset in Otter, it is stored in a Raft, which is a sort of abstract file system. So, it's basically just a file (script-name.ps1) stored in this raft. We are working on building out our training videos (sadly, they take quite a while), but we'd love to learn what your overall goals are, and how we can build good content to help you reach those goals. In a lot of organizations, one of the most important things is "showing the value/success" of automation, infrastructure as code, etc. So we want to help with that too. Anyways, it's obvious quite a "big topic", so your best would be to get in touch with us, so we can work together directly.