@matteo-nunziati said

this is the list of things provided by the full agent

I wish that chart broke it down by

MS LIS and agent

We think that the issue was tied to performance. We saw the system being driven really hard, there is a lot going on behind the scenes. Our infrastructure upgrade this morning seems to have addressed the issue well.

@gjacobse said in Sodium: Custom Ticket Views:

@danp said in Sodium: Custom Ticket Views:

@quixoticjeremy said in Sodium: Custom Ticket Views:

that being said it's being worked on from the standpoint of logins should timeout ....overnight.... so you should have to login in the morning anyways.

Has this change been pushed out? FWIW, I didn't get auto-logged out overnight.

I dont' get auto-logged out either.

No one does yet.

@quixoticjustin said in Sodium: Apply Updates:

Yeah, lots of cleaning up needed for the patch system. It is early and mostly works, but leaves a lot to be desired yet 🙂

We are working on a design for a patching dashboard that will give a lot more power specifically around patching.

Exactly, not a lot going to be fixed up on the way it looks currently when a lot of work is going to be going into this in the near future to give a lot more functionality.

@gjacobse said in Stupid Annoying O365/OWA tricks:

can't see it being a time out issue. But this is really ridicules .. Is anyone else encountering this

See the timeouts for OWA, usually is every 6 hours
https://support.office.com/en-us/article/Session-timeouts-for-Office-365-37a5c116-5b07-4f70-8333-5b86fd2c3c40
Maybe is an authentication token expired.

@danp said in Sodium: Ticket layout:

@scottalanmiller said in Sodium: Ticket layout:

Having delete anywhere that people look at it all of the time is probably bad. That's a super special case button that should almost always route to a manager for approval and should be trivially disabled as it often would need to be forbidden.

Along this lines, perhaps this should be a setting under Group Permissions.

This could definitely be a good route to go with this.

Curious

Here is the issue:

Pithos running for Pandora - Audio Output fine.

Plug in SignaLink usb soundcard for decoding signals on HF - and the audio settings change. Pithos tries to route audio to it.

Due to this change - the computer can't key the radio correctly.

If Pithos is running, and the Singlalink is connected, changing the volume will key cycle the radio (transmit/receive/transmit) which is not healthy on the radio.

2_1504794011319_IMG_1475.PNG

1_1504794011319_IMG_1474.PNG

0_1504794011318_IMG_1473.PNG

Hopefully soon-ish there will be workflows for things like ticket closings so that there can be customer defined actions, checks, or whatever when something like that happens.

@gjacobse said in Soduim: Workstation OS/CPU Information page:

This is just a formatting item:

0_1504709380320_2017-09-06 10_12_15-Sodium.png

Any chance to expand the CPU % in use at the bottom?
@Sodium

I'll be sure to take a look 🙂

@stacksofplates said in Lowest Possible WiFi AP:

You'll likely spend more in time trying to figure something out than just buying a Ubiquiti AP and turning it down.

AP: "Hi, I'm your new Ubiquiti, how can we hook up your network today?"
Me: "Oh sorry, we've decided to go in another direction."

^^^ Me turning down the Ubiquiti.

@scottalanmiller said in Dual boot file storage:

Consider something like NextCloud, why store the files locally?

In the Use Case; Not on:

local network wifi completely detached from network(s)

@scottalanmiller said in O365: OWA Recover deleted Calendar:

Now that we can mark them, I'm going to slowly try to work through getting them all closed.

I was going to unmark as question - since it was so old. I don't know if you can do that, but on topics of a certain age, you may do this rather then bringing them forward.

Up to you of course.

Another example taken from another script:

import-module activedirectory $domain = "domain.mydom.com" $DaysInactive = 90 $time = (Get-Date).Adddays(-($DaysInactive)) # Get all AD computers with lastLogonTimestamp less than our time Get-ADComputer -Filter {LastLogonTimeStamp -lt $time} -Properties LastLogonTimeStamp | # Output hostname and lastLogonTimestamp into CSV select-object Name,@{Name="Stamp"; Expression={[DateTime]::FromFileTime($_.lastLogonTimestamp)}} | export-csv OLD_Computer.csv -notypeinformation

LOL - Pithos just stopped... I'm like WHAT?

Oh, it went to sleep.. oops.

@quixoticjustin said in Sodium: Tab / Page title:

Good idea, maybe direct links to different sections as well so that they can be opened directly and saved as default pages or whatever. Different people will want to start with different numbers of tabs and at different points.

Cool.. I tried the Scroll wheel click to open in new tab and that didn't work... which is a separate issue,.. but ...

@nerdydad said in Hurricane Harvey:

Expect gas prices to go up as the refineries are also along the Texas Gulf coast. because they will use any and every excuse to raise gas prices.

@quixoticjeremy said in Sodium: Device Uptime:

@scottalanmiller said in Sodium: Device Uptime:

Uptime in friendly numbers, rather than seconds, would be nice, too.

What? You don't want to figure out what 4829383 seconds is in terms up of days, hours, minutes and seconds? Here I thought everyone enjoyed that math.

Can't we convert it to a Star Date?