HPlum78

Voices

Multiverse

Still (Still Game the comedy series) i was hoping for Mind Crime one of the best albums...

Operation

Horn...

Dance..

Wizards

$results = invoke-command {your script block here} Then the results will be in the local var.

@chaplic is bang on there.

Chess..

Poisoning

Rod...

$csv = import-csv C:\localdata\serverinfo.csv $out = New-Object System.Collections.ArrayList foreach ($row in $CSV){ if ($obj.Computer -eq $roW.computer){ Write-Host -for yellow "updating details for $($obj.Computer)" $row.WindowsVersion = "Server 2012 my very own version build" } $out.Add($row) } $out | Export-CSV -Force -NoTypeInformation "C:\localdata\serverinfo.csv" thats what I have in my mind, needs altering to do the correct matches but is a starter for 10 (I hope)

Goats.

In my mind you are going to have to import the csv and then foreach loop it, at logon mind its going to be resource hungry...

I built one of these in sharepoint, so it depends on if you want do some development? Oh and if you use SP in any way...

You can integrate your on prem PBX with teams, and you probably dont need any additional licences for your users.

Unless they are installing ILS on the 18th fairway this is nonsense! More a case of cannot be bothered so come up with an excuse not to take on the work.

You should make sure that you are using the v2 exchange module as the performance increase is massive. I would also have a group setup for this for so when someone essentially wants to opt out you can remove them from the group!

There is no good way of doing this... I dont know if you use OWA and the Outlook client app but if you do they store their auto complete entries in different places from memory an all! Also MS added a hidden folder under the contacts part of a users folder The Recipient Cache folder although this still has not had any real documentation released to its use! But is also involved in auto complete. I do not know of a way of removing 1 entry from the cache unfortunately and there are so many places this is pulled from its a difficult one. I am not even sure I want to open PowerShell to start kicking at this stone!

So my guess is that you are passing the Azure auth part of this and that error is being thrown by FD. Guess is it is what is in the claim is there no better app logs?

What is the actual error? (look at the sign in logs in Azure) have you installed saml trace on your browser (chrome/ chrome based and Firefox browsers) ? If not get it. Also setup claims xray so you can test and see how and what is leaving in the claim (Don't embellish the claim with more than is needed!) . Also test in an in private browser so you know that you are getting a fresh token. I have migrated around 30 apps in the past few weeks but have no experience of freshdesk will take a look....

So the simple way would be select-string with a pattern match. Here is what MS has: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/select-string?view=powershell-7.1 Good resource here: https://adamtheautomator.com/powershell-grep/ And Ed Wilson (Dr Scrpto) post from 2011 is a good read as well https://devblogs.microsoft.com/scripting/use-an-easy-powershell-command-to-search-files-for-information/

I know I have touched upon this with you in the past @tri_94 (and by the way nice bit of coding by @fordea) you could approach this a slightly different way. So instead of testing a servers config you could use DSC (desired state config) to say this is my configuration and I want you (the server) to make sure that your configuration matches. By doing this you do two things you build your configuration documents for your servers as you go, and you can also build a pester test to verify that configuration, using essentially the same artifacts. The PowerShell team release a 6 month statement of investment (I don't know if you look at this, if not I would suggest you take a look. Look for Steve Lee PowerShell in Google and you will find him..). Essentially in the next sprint they are looking at decoupling DSC from PowerShell (so they can develop them both separately, and we are not waiting on PS versions to unlock developments in DSC). Also in this sprint they have said they would look at getting DSC to support JSON rather than MOF files for the configuration management, if that becomes possible we will be able to use that directly and consume these JSON files within Pester tests that we can run against servers and pump out and in turn report on configuration. Slightly different approach than writing a a load of scripts and tooling when there are some good tools already out there that you could make fit your requirements, and gain a load of community support. H.

I am going to point you at Kevin's excellent post about all things hash tables (Kevin knows his onions, I have been in many of his presentations at PowerShell conferences all over the world, and MS have stolen parts of this post for their own docs... ) https://powershellexplained.com/2016-11-06-powershell-hashtable-everything-you-wanted-to-know-about/