1 server, 10 workstations, 1 idiot, 1 cup
-
Administrative personal follows closely in their hate.
Our admins loved their Palms, which was nightmarish because we used Lotus Notes for email and you need to make a pact with Satan to make Lotus Notes talk to a Palm.
(And even once you had it working, days later you'd find the sync program crashed because Lotus Notes tried to sync a calendar event that ended before it began. Because you can make those in Lotus Notes. Because it's motherfucking awful.)
-
is a lot of local config on workstations based on specialised uses
All config goes into the container. We interact a lot with serial devices and USB-to-serial thingies. And printers. Of the type with a safari themed logo.
-
DCs don't have local accounts (including local admin) unless they're in DSRM. The admin account would be the domain admin account.
-
What's your point? Are you claiming the demo wouldn't work?
-
hire a network guy
Unless you're in a smaller setup where everyone has to do a bit of everything I generally wouldn't expect a network-focused person to have a lot of expertise in AD and vice-versa. The fun comes when you consult at a larger enterprise and they look at you funny when you suggest that the network guys should be looking after DNS and DHCP with something like InfoBlox rather than your domain admins with AD.
-
Re-reading your post I don't even understand what the hell you were even doing.
-
it sorta worked
Yeah most of the time they don't get that mostly works doesn't cut it.
-
Oh I hate these black and white striped pieces of utter shit and evil. Their label printer and the star trek theme named scanners from another manufacturer can die, die and die already.
-
if you have more than 5 users or 10 devices, you're probably running a domain
*snort*
If you need a server
Ah, ok. :) (our "server" is google docs and dropbox)
because it gets to be a nightmare to manage if you don't.
IT doesn't. They manage Macs. We manage our own machines. This is good. And bad.
-
We had a lot of complaints when we tried to move to scanners that had colour screens and WiFi. Even though our app on the scanner is black and white, text only.
-
snort
He meant should be.
It's not exactly difficult to set one up and use it. And, with samba, it's also free.
-
After cleaning all of the virii from everything, patching them and retrieving 1,000s of files sprayed across every hard drive, I had them properly joined to their Small Business Server domain with group policy locking everything down to ensure that files were stored on a server that was being backed up.
How much time passed before the users started to demand domain admin rights so that they could continue doing their jobs without making even the slightest change in their workflow?
-
I had a bunch of folks try to reverse engineer the barcode font on ours to make it work with other models of programmable scanners. If course this didn't at all go wrong when used for patient treatment verification. And they tried to sue us over it too.
-
Fortunately in that situation it wasn't a problem. The users were volunteers who were only around for a few weeks at a time, and although I was also a volunteer I was effectively the CIO, so as well as fixing and upgrading things I was also creating IT policy for the organisation.
Filed under: It's good to be the King
-
(And even once you had it working, days later you'd find the sync program crashed because Lotus Notes tried to sync a calendar event that ended before it began. Because you can make those in Lotus Notes. Because it's motherfucking awful.)
But what if I need to schedule a 30 minute meeting starting at the first 1:45 am on the Sunday that Daylight Saving Time shifts backwards? I HAVE A USE CASE, IBM!
Of course, TRWTF is storing a start timestamp and end timestamp, instead of a start timestamp and an interval duration.
Also, TRTRWTF is, of course, Daylight Saving Time and Windows:
[B]efore 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year. The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar. -- Source
-
So wait, Israel having DST rules that were fundamentally different to how everyone else worked is Microsoft's fault?
-
Can't blame Israel for using the calendar they've been using for 4k or so years?
-
Oh I hate these black and white striped pieces of utter shit and evil. Their label printer and the star trek theme named scanners from another manufacturer can die, die and die already.
They were trying to pass the scanners off as an Enterprise solution.
Edit: Also, my joke was so bad it caused server cooties.
-
Can't blame Israel for using the calendar they've been using for 4k or so years?
When everyone else, their dogs, and their dog eggs have switched to Gregorian? Yes, I can.
-
Why not? It's not like our calendar system hasn't changed over the centuries. Oh ... wait it did.
Edit: 504 OK
-
I find it extremely difficult to believe they had Daylight Savings Time 4,000 years ago.
Everywhere else, the concept was implemented during WWI.
-
Well, it started in at least 1995 and ended in 2013. It took nearly 20 years and two changes by Israeli legislation to get an operating system that could correctly do their DST, and they did it by allowing the prevailing calendar to rule it, essentially working around the problem. So... 20 years and MS couldn't figure out how to create zone data files to represent a one-to-one map between two calendars? Particularly after the change in 2005 -- hell, you could have someone sit down and define them manually for the next 50 years at that point -- yes, that strikes me as just a little bit of bullshit.
-
Calendar != clock. I meant them having rules based on their own calendar after 2005.
-
So wait, Israel having DST rules that were fundamentally different to how everyone else worked is Microsoft's fault?
Everything is Microsoft's fault, didn't you know that?
-
Back to the "It's AD, everything is always AD" we had an outage, ~12 years ago, when machines suddenly started getting duplicate IP addresses.
Turns out there was a new Windows server on the network that was configured as a DHCP server pushing out addresses in the same range as the "proper" DHCP server (suppose that was mildly better than sending out IPs in some other random range).When we tracked down the culprit he said "But I made it a domain controller of its own test domain - I thought it would only give IP addresses to machines on its domain..."
I haven't often had to wheel out the 7-layer OSI network model diagram but I needed it that day.
Edit: Now that I re-read this, there is a second WTF which is that if it did work in the way the network wazzock thought it would, then it should have farmed out IP addresses in a different range. But he was still an under-trained, over-admin'd twit
-
So wait, Israel having DST rules that were fundamentally different to how everyone else worked is Microsoft's fault?
Huh? I thought he was blaming Windows' handling of Israeli DST on Microsoft. Or did they outsource that bit?
-
That reminded me of my previous workplace, which I keep complaining to the sole Operations guy about a secondary DHCP giving out old addresses when the internal IP network was changed to accommodate the new router set up by a different ISP.
He kept claiming that was no such servers and refuse to investigate, till I chuck out a wireshark log to show him the fucking broadcasts by the rogue DHCP somewhere in the network.
-
I feel the pain.
I am trying to get a site upgraded at the moment who cannot run our application because they still run windows 98 workstations. They currently use a 7 year old version of the software over citrix, because their ws hardware doesnt have the necessary oomph.
Ew, gross.
And half of the systems the hospitals use need some obscure .net version installed which is a real problem for us because we need the "modern" version of .net 4. But installing that crashes some custs .net 2 only systems.
Hey, if anybody ever asks why
System.Reflection.Assembly.LoadWithPartialName()is deprecated: now you know!Most of the stuff I work on now is all .Net 4 so that still seems pretty modern to me, but that's because I mostly work with PowerShell 4 these days when I'm in a .Net environment.
Some days I need a lot of lavender tea to keep calm.
That's how you know you're in IT.
-
One of my doctors recommended I read The Digital Doctor. So far it's had several interesting insights to health IT. It also has helped explain some issues I've noticed since I've been at a health IT company the past few years.
-
-
If I had been able to show that picture, I'm sure the conversation would have been significantly shorter...
"So, in this scenario, the kitty in the green box is serving DHCP addresses, whereas your AD shit is waaaaay up there in the pink and blue kitty boxes"
-
I'm saving this picture for future use if necessary. Explaining using cats to
peopleidiots seems to be widely accepted.
-
If I had been able to show that picture, I'm sure the conversation would have been significantly shorter...
It appears to be missing a layer.
-
My only real complaint with that picture is that the layers aren't numbered.
-
It appears to be missing a layer.
Nice :) we should use a big fluffy white cat for that layer, like the one the bond villain have!
-
Sounds like a layer 8 issue to me.
-
Sounds like a layer 8 issue to me.
I didn't realize people were part of the OSI model?
-
How can you have any model that doesn't include PEBKAC?
-
The model I learned had management at layer 9.
-
Wouldn't management be layer potato?
-
only if users are layer jelly.
-
I did ask about Citrix which earned me a blank stare.
Asking about Citrix would be getting me running for my life to the door.
-
As it should. Shittrix is a thing.
-
There is a reason I am trying to get someone else to do it.
-
But with a Sean Connery acshent?
-
Shittriksh! Yes, I'd even hire someone from Embra.
-
only if users are layer jelly.
That was not supposed to be a reference to jellypotato. I thought the management layer number should be tangential to the actual numbers, so at first I was thinking imaginary numbers, but I also wanted to convey complete lack of understanding of the layers. As in,
-
