Things Programmers Shout #470
“Ok, I know what I have to do. Just create a new class…” *stares at screen for half an hour wondering how to name it*
// submitted by @cecilyacat
2025 on Tumblr: Trends That Defined the Year
No title available
Show & Tell
$LAYYYTER
let's talk about Bridgerton tea, my ask is open

titsay

❣ Chile in a Photography ❣

Game Changer & Make Some Noise
Xuebing Du
The Bowery Presents
Monterey Bay Aquarium
untitled

Jar Jar Binks Fan Club
sheepfilms

No title available
EXPECTATIONS

roma★
🩵 avery cochrane 🩵
Interview Vampire Daily
h
seen from United States
seen from United States

seen from Poland
seen from Thailand

seen from France
seen from United States

seen from United States
seen from Canada
seen from Morocco
seen from Germany
seen from United States
seen from Saudi Arabia
seen from Russia
seen from United States

seen from Türkiye
seen from Uruguay

seen from United States
seen from United States

seen from Argentina
seen from Poland
@adventures-in-systemsland
Things Programmers Shout #470
“Ok, I know what I have to do. Just create a new class…” *stares at screen for half an hour wondering how to name it*
// submitted by @cecilyacat
Things Programmers Shout #455
“What do you mean variable not defined?!?! I just defined it, you sorry excuse of a language.“ // submitted by @aggressivelyshipsallships
Things Programmers Shout #454
“A different error message! Finally some progress!” // submitted by @falterfire
User says 10G network is not enough
by John
When my laptop starts acting funny
Alerts when an outage starts
by Briggs
Alerts when an outage starts
by Briggs
Get Dirsync status with PowerShell
One of the biggest challenges I faced while automating mailbox creation and migration within a hybrid Exchange/O365 environment was figuring out when Dirsync had finished running.
By default, Dirsync runs x hours after the time the last cycle completes, which means that Dirsync never really runs on a fixed schedule. But, how does Dirsync know when the cycle completed?
Turns out, there’s a value in Get-MsolCompanyInformation called LastDirsyncTime. Get that value, store it in a variable, run Dirsync, then use a while loop to compare the value in your variable with the current value of LastDirSyncTime until the current value exceeds your variable value.
Here’s the code snippet, and the full function I use for O365 to On-Prem migration is below the cut.
$DirSyncTimeBefore = Get-MsolCompanyInformation | select LastDirSyncTime $dstimeb = $DirSyncTimeBefore.LastDirSyncTime Write-Output "Time before is $dstimeb"
$ScriptBlock = { Invoke-Command -ComputerName dirsyncserver.domain.com {C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe ` -psconsolefile "C:\Program Files\Windows Azure Active Directory Sync\DirSyncConfigShell.psc1" ` -command "Start-OnlineCoexistenceSync"} } while ($timetest -ne $True){ $DirsyncTimeNow = Get-MsolCompanyInformation | select LastDirSyncTime $dstimen = $DirsyncTimeNow.LastDirSyncTime $timetest = $DirsyncTimeNow.LastDirSyncTime –gt $DirSyncTimeBefore.LastDirSyncTime Write-Output "Time now is $dstimen" Start-Sleep(20)
So many tickets, so little time...
by @ReesReb
Using "cat" instead of "tail"
by donttrustcats
Accidental chmod -R on /
by infra
How to respond about on-going outages
uaiHebert
When staging/pre-prod is broken
by JK
The service is broken for no apparent reason 10 minutes before the presentation
by mkzero
Monday morning‘s requests
by Vincus
Replacing all the SSL certs again, for SHA-1 to SHA-2 migration
by euc
SELINUX=enforcing
by Briggs