You might like
Connecting a Windows Server 2025 using nvme over tcp to a pure storage system is not trivial compared to the ease it was with esxi. Why make it so complicated?
Ok, so using a service account (ad user) is bad and we should all be using service principals, however not all actions with Azure SQL support service principals because applications cannot impersonate other applications, so the sql server resource should have a managed identity🤬
Wondering why my Pester test using scriptanalyzer gets a different result than running scriptanalyzer manually
Whoopsy, my SQL installation script set the tempdb log file fixed to 8mb
Again the PowerShell Conference EU was worth it - learned new stuff, reminded of old stuff and just the best people
Regex is really growing on me - not that everything should be solved by regex
The only Windows 2025 In-place upgrade succes I have is a server with IIS. Doing an In-place upgrade of a SQL server 2016 and an Axapta Object Server left them in a non working condition.
In the mysterious land of Sweden we will ascend the twisted tower and obtain the tomes of Powershell secrets from the wizards #PSConfEU
In-place upgrade to Windows Server 2025 might remove registry entries breaking the installed applications. Broke Axapta 2012R3 and SQL Server 2016 and SQL Server 2022
I find copilot helpful when doing PowerShell, but are we doing ourselves a disservice in the long term, when we stop training in problem-solving and rely on AI to do most of it
Making ConvertFrom-Json -AsHashTable functionality working in 5.1 and then discover that 7 converts dates diffently than 5.1 when you convert them manually 🥺
Unprepared for the obscene number of errors in my code, that have been dorment for quite a while, trying to put it into the sampler framework.
I appreciate copilot doing the synopsis for me, but it would be nice if it did it the same way in every function, and not randomly do really weird stuff instead or ask for the function code
It was supposed to just be a quick migration of a script to a module using sampler - note to self - make sure the script is ready for that - damn you pesky tests
Why would using an assembly and a dll from PowerShell 5.1 work in a local function but not when the function is in a module?
For the developers of Teams it might have seen like a great idea to install in app data of each user, for the enterprise very much less so
Get-LocalGroupMember fails if the group contains an orphan SID 😬
United States Trends
- 1. Vandy 5,832 posts
- 2. Carnell Tate N/A
- 3. Vanderbilt 5,360 posts
- 4. French Laundry 2,915 posts
- 5. Christmas 125K posts
- 6. Julian Sayin 1,976 posts
- 7. Clemson 7,823 posts
- 8. #HookEm 2,404 posts
- 9. Jeremiah Smith 1,030 posts
- 10. Dalot 17.6K posts
- 11. Amad 20.5K posts
- 12. Arch Manning 2,036 posts
- 13. Jim Knowles N/A
- 14. ESPN 78.5K posts
- 15. Buckeyes 2,892 posts
- 16. Disney 89K posts
- 17. Colin Simmons N/A
- 18. Ryan Wingo N/A
- 19. Casemiro 20.7K posts
- 20. #NFOMUN 8,488 posts
Something went wrong.
Something went wrong.