It doesn't help that even today, in the year of our lord twenty-fucking-seventeen, a lot of SQL-oriented products still have documentation that recommends that SQL be installed on its own physical server, and there are still a lot of old-school SQL DBAs who consider that to be best practice.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
It doesn't help that even today, in the year of our lord twenty-fucking-seventeen, a lot of SQL-oriented products still have documentation that recommends that SQL be installed on its own physical server, and there are still a lot of old-school SQL DBAs who consider that to be best practice.
bowen on
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
yea, there are just people who have a really difficult time with the idea of "single purpose servers" today really means "single purpose VM/OS install"
I have been trying really hard not to call them servers now, I just say "an exchange install" or "A SQL instance" or something like that, meaning it's a VM with a server OS and SQL, and that's it.
Edit: saw the security thread and think this is a better fit there. Sorry!
TheBlackWind on
PAD ID - 328,762,218
0
lwt1973King of ThievesSyndicationRegistered Userregular
How often do you restart your Comcast/Charter business modems? We had some issues with a VPN and Comcast said to just restart the modem as they were getting ping loss to it (even though the internet was fine).
"He's sulking in his tent like Achilles! It's the Iliad?...from Homer?! READ A BOOK!!" -Handy
How often do you restart your Comcast/Charter business modems? We had some issues with a VPN and Comcast said to just restart the modem as they were getting ping loss to it (even though the internet was fine).
I find that cable modems degrade over time for whatever reason. Poor heat dissipation, maybe? I dunno.
This is household, not business, but I just replaced my Cisco DPC3008 with an ASUS CM-16 because the DPC3008 slowly went from needing a reboot once every 3-4 months to needing a reboot every month to needing a reboot every 1-2 weeks.
edit: Comcast
Feral on
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
How often do you restart your Comcast/Charter business modems? We had some issues with a VPN and Comcast said to just restart the modem as they were getting ping loss to it (even though the internet was fine).
I find that cable modems degrade over time for whatever reason. Poor heat dissipation, maybe? I dunno.
This is household, not business, but I just replaced my Cisco DPC3008 with an ASUS CM-16 because the DPC3008 slowly went from needing a reboot once every 3-4 months to needing a reboot every month to needing a reboot every 1-2 weeks.
edit: Comcast
I think it's a combination of poor heat dissapation and too many read/write cycles to a shitty memory controller. The hardware in those things is never really any good.
I think a lot of the problem is that people see "on a different machine" and think that it's for catastrophic protection - if physical server A catches on fire and melts, at least our database...
Wait, that doesn't make sense either. There's no implied redundancy by having your database on a separate physical machine...
But it's also likely that this guy hasn't thought through it that far.
I think a lot of the problem is that people see "on a different machine" and think that it's for catastrophic protection - if physical server A catches on fire and melts, at least our database...
Wait, that doesn't make sense either. There's no implied redundancy by having your database on a separate physical machine...
But it's also likely that this guy hasn't thought through it that far.
I haven't actually even had time to talk to him today, and he's off Thursday, but I realized earlier this morning that the design he came up with would actually still have the VHDs for all the VM's on one SAN, which makes this even more absurd.
The basis for that was "if I need to update something, it won't take down my database"
"I need to update nginx on the production server, so it's going to be offline for a few minutes. Good thing my database will still be available to all the users who can't access the site that connects to the database!"
I guess the upside is that you can still connect via ssh and run raw queries?
The basis for that was "if I need to update something, it won't take down my database"
"I need to update nginx on the production server, so it's going to be offline for a few minutes. Good thing my database will still be available to all the users who can't access the site that connects to the database!"
I guess the upside is that you can still connect via ssh and run raw queries?
A lot of applications don't communicate with RESTful APIs. So internally, you might have a few web resources that go down, but the homebrewed C++ app that's doing server->client with mysql will still work if you needed to update nginx.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
I think a lot of the problem is that people see "on a different machine" and think that it's for catastrophic protection - if physical server A catches on fire and melts, at least our database...
Wait, that doesn't make sense either. There's no implied redundancy by having your database on a separate physical machine...
But it's also likely that this guy hasn't thought through it that far.
The primary consideration for separation was always resource utilization. Application developers want everything all to themselves and as much as you can give. Separation of roles was second but beyond a few benefits with maintenance is really one and the same as the first issue. Redundancy would be a distant third and due to the complications with implementation has always been covered as a separate topic in any install guide I've read.
Just remember that half the people you meet are below average intelligence.
The basis for that was "if I need to update something, it won't take down my database"
"I need to update nginx on the production server, so it's going to be offline for a few minutes. Good thing my database will still be available to all the users who can't access the site that connects to the database!"
I guess the upside is that you can still connect via ssh and run raw queries?
A lot of applications don't communicate with RESTful APIs. So internally, you might have a few web resources that go down, but the homebrewed C++ app that's doing server->client with mysql will still work if you needed to update nginx.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
How often do you restart your Comcast/Charter business modems? We had some issues with a VPN and Comcast said to just restart the modem as they were getting ping loss to it (even though the internet was fine).
I find that cable modems degrade over time for whatever reason. Poor heat dissipation, maybe? I dunno.
This is household, not business, but I just replaced my Cisco DPC3008 with an ASUS CM-16 because the DPC3008 slowly went from needing a reboot once every 3-4 months to needing a reboot every month to needing a reboot every 1-2 weeks.
edit: Comcast
I think it's a combination of poor heat dissapation and too many read/write cycles to a shitty memory controller. The hardware in those things is never really any good.
Yep, same with DSL modems. They make these things without fans for the sake of aesthetics, and that's a brick in my wall.
Oh, boy. A tangentially related manager found out we were using clonezilla for some really basic imaging and wants to pick a fight about not using something we have to pay for instead. "But it can't be good, it didn't cost me a million dollars."
$User can't get to $Website.
Must be a LAN problem.
I'm dealing with people between the ages of 20 and 40 who haven't grasped the finer points of monitor resolution.
+2
TL DRNot at all confident in his reflexive opinions of thingsRegistered Userregular
Ok, this is one of those kind-of-embarrassing gaps in knowledge that come from having never had any formal training and just having made a career out of learning on the fly
Why is it that one of our clients tends to have issues with, for instance, domain user authentication when using the format acmecompany\timtheory versus acmecompany.com\timtheory? Did someone just miss a step when setting up local DNS?
Bonus weirdness, when setting up an app for same client, the app's admin console demanded acmecompanycom, sans the period.
Ok, this is one of those kind-of-embarrassing gaps in knowledge that come from having never had any formal training and just having made a career out of learning on the fly
Why is it that one of our clients tends to have issues with, for instance, domain user authentication when using the format acmecompany\timtheory versus acmecompany.com\timtheory? Did someone just miss a step when setting up local DNS?
Bonus weirdness, when setting up an app for same client, the app's admin console demanded acmecompanycom, sans the period.
DNS weirdness can cause all sorts of shit in AD so I never rule that out. However, the fact that they can log in with the FQDN suggests that DNS isn't the problem here.
Are you absolutely sure that acmecompany is the correct NetBIOS-format domain name and not acmecompanycom?
Is there any possibility that bothacmecompany and acmecompanycom exist as domains in the forest?
Fire up Active Directory Domains and Trusts. In most small businesses you should only see one domain (in your case, acmecompany.com). If you see two or more... well, that's interesting.
Right-click on the domain and go to Properties. Verify that the "Domain name (pre-Windows 2000)" is what you think it is.
Click on the Trusts tab. Look for any other domains you have trust relationships with.
Once you verify that all that looks in order then I would dig down into other problems.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
Ok, this is one of those kind-of-embarrassing gaps in knowledge that come from having never had any formal training and just having made a career out of learning on the fly
Why is it that one of our clients tends to have issues with, for instance, domain user authentication when using the format acmecompany\timtheory versus acmecompany.com\timtheory? Did someone just miss a step when setting up local DNS?
Bonus weirdness, when setting up an app for same client, the app's admin console demanded acmecompanycom, sans the period.
The first example is using the NetBIOS domain name. The second is using the FQDN. Both are valid in a single forest, but you can have issues when trying to use the legacy NetBIOS version across forest trusts. Of course if you've got problems with AD/DNS, that can cause all sorts of issues. But if the issue is in an application, it's most likely with its own authentication mechanism. Some things are written to only accept the NetBIOS version and they've never been updated so they mangle the username otherwise.
The old Windows NT NetBIOS version also more likely to be used because it's been around forever and it's shorter. If the applications support it, you're better off getting people to sign in with their UPN ([email protected]).
As for the third issue, I'd say that app's authentication is badly broken and just be glad it works at all.
SiliconStew on
Just remember that half the people you meet are below average intelligence.
What a day.
First stop nice a quick.
Second stop I go 45 minutes over expected time - internet issues meaning I couldn't download what I needed for them, plus not having any account info needed for the firewall swap, plus the new firewall having less ports than a $45 Dlink router.
Third stop I had to install a backup system and AV. The previous AV turns out had an auto-installer agent from Solarwinds that simply reinstalled the old software and fucked with my install, took twice as long as it should have. Backup system seems to be fucked out of the box and wouldn't create a volume to store backups on.
Finally get home, multiple after hours calls come through. I also have a ticket for the morning to look at a server issue. I take a peek at it and nope, this isn't a Thursday morning job when I have shit scheduled at 10AM already and people need their servers. I've been resizing disks for the past 3+ hours now due to a host running out of space and killing email and file shares.
Because if you're going to attempt to squeeze that big black monster into your slot you will need to be able to take at least 12 inches or else you're going to have a bad time...
Our new owners/domain are the first place I've worked at where everything goes by upn instead of logon name.
I always thought it was funny to see it in AD as "pre windows 2000 name" when it's been decades and whoops everyone's using it.
Also, of course, this being the fist place I've ever worked using the UPN and the netbios domain name is different from the fqdn name (CONTOSOCORP\ vs contoso.com)
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
Our new owners/domain are the first place I've worked at where everything goes by upn instead of logon name.
I always thought it was funny to see it in AD as "pre windows 2000 name" when it's been decades and whoops everyone's using it.
Also, of course, this being the fist place I've ever worked using the UPN and the netbios domain name is different from the fqdn name (CONTOSOCORP\ vs contoso.com)
Nice thing about UPNs is being able to tell your users that their username is the same as their email address.
Just remember that half the people you meet are below average intelligence.
+3
RandomHajileNot actually a SnatcherThe New KremlinRegistered Userregular
Our new owners/domain are the first place I've worked at where everything goes by upn instead of logon name.
I always thought it was funny to see it in AD as "pre windows 2000 name" when it's been decades and whoops everyone's using it.
Also, of course, this being the fist place I've ever worked using the UPN and the netbios domain name is different from the fqdn name (CONTOSOCORP\ vs contoso.com)
Nice thing about UPNs is being able to tell your users that their username is the same as their email address.
Our new owners/domain are the first place I've worked at where everything goes by upn instead of logon name.
I always thought it was funny to see it in AD as "pre windows 2000 name" when it's been decades and whoops everyone's using it.
Also, of course, this being the fist place I've ever worked using the UPN and the netbios domain name is different from the fqdn name (CONTOSOCORP\ vs contoso.com)
Nice thing about UPNs is being able to tell your users that their username is the same as their email address.
Unless it isn't.
Recipient address policies ftw
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
the "no true scotch man" fallacy.
0
RandomHajileNot actually a SnatcherThe New KremlinRegistered Userregular
Our new owners/domain are the first place I've worked at where everything goes by upn instead of logon name.
I always thought it was funny to see it in AD as "pre windows 2000 name" when it's been decades and whoops everyone's using it.
Also, of course, this being the fist place I've ever worked using the UPN and the netbios domain name is different from the fqdn name (CONTOSOCORP\ vs contoso.com)
Nice thing about UPNs is being able to tell your users that their username is the same as their email address.
Unless it isn't.
Recipient address policies ftw
Unless you're still using Lotus Notes.
(Actually, this would be really easy to set up in Notes. Like, a four line script. Maybe even a field in the server config doc. Unfortunately, we don't own the internet .com for our internal domain .com, so it's kind of a moot point. I'd be better off renaming/migrating our internal domain to match our external, but that's a lot of work.)
Oh my favorite thing to see when using MWB Chameleon.
What was the big stuff that required chameleon?.
I.
Will.
Give.
You.
One.
Just one.
Fucking.
Guess.
Coupon app?
Ding ding ding
Tell him what he's won, Johnny.
I don't understand your users. I've seen coupon apps install useless adware like DriverSupport or MindSpark garbage, but I've never seen one so bad it needed Chameleon. Where are they getting this stuff?
Oh my favorite thing to see when using MWB Chameleon.
What was the big stuff that required chameleon?.
I.
Will.
Give.
You.
One.
Just one.
Fucking.
Guess.
Coupon app?
Ding ding ding
Tell him what he's won, Johnny.
I don't understand your users. I've seen coupon apps install useless adware like DriverSupport or MindSpark garbage, but I've never seen one so bad it needed Chameleon. Where are they getting this stuff?
I don't know.
Our networking team has over 250 clients, but only about 100 of them are hosted on our servers. That means we have to be reactionary sysadmins to over 150 different banks because we quite literally cannot tell them what to do. Our biggest task is networking service insofar as to keep our own proprietary suite of software up and running so they don't have downtime. We can't monitor their traffic, set policy, or enact any changes without bank approval and, well, let's just say that when they say "we'll get back to you" they never, ever fucking do.
So, my entire networking team is essentially Kif from Futurama.
We're fighting against a current of ignorant users, part-time IT guys who know just enough to seriously break everything, third party "security" companies who don't even know how to create a service to run their programs, and small-town bank presidents who want impossible things enacted with a ridiculously short timetable.
Not to mention management that has no desire to temper expectations, developers who want us to fix their shit without them telling us how it works, and internal management for our direct team who don't have enough of a spine to call out how much bullshit it is. But I figure these latter 3 complaints are pretty ubiquitous, so just a cherry on top.
jungleroomx on
+2
TL DRNot at all confident in his reflexive opinions of thingsRegistered Userregular
Ok, this is one of those kind-of-embarrassing gaps in knowledge that come from having never had any formal training and just having made a career out of learning on the fly
Why is it that one of our clients tends to have issues with, for instance, domain user authentication when using the format acmecompany\timtheory versus acmecompany.com\timtheory? Did someone just miss a step when setting up local DNS?
Bonus weirdness, when setting up an app for same client, the app's admin console demanded acmecompanycom, sans the period.
DNS weirdness can cause all sorts of shit in AD so I never rule that out. However, the fact that they can log in with the FQDN suggests that DNS isn't the problem here.
Are you absolutely sure that acmecompany is the correct NetBIOS-format domain name and not acmecompanycom?
Is there any possibility that bothacmecompany and acmecompanycom exist as domains in the forest?
Fire up Active Directory Domains and Trusts. In most small businesses you should only see one domain (in your case, acmecompany.com). If you see two or more... well, that's interesting.
Right-click on the domain and go to Properties. Verify that the "Domain name (pre-Windows 2000)" is what you think it is.
Click on the Trusts tab. Look for any other domains you have trust relationships with.
Once you verify that all that looks in order then I would dig down into other problems.
The only domain in the forest is acmecompany.com but as you suggested the pre-Windows 2000 name is acmecompanycom (no period), compared to my local network which is MSPcompany.com in ADDT and MSPcompany in the pre-Windows 2000 name.
Is this getting into the territory of 'well, best practice is _____ but at this point it isn't worth breaking things to make the change a relatively-simple network'?
As for the third issue, I'd say that app's authentication is badly broken and just be glad it works at all.
The initial thing that I caught notice of was with Windows logons and OWA, not a third-party app. I can log in with acmecompany.com\timothy but not acmecompany\timothy.
The third-party app that demands what I now know to be the pre-Windows 2000 domain name is a new install of a LexisNexis product.
TLDR: can users log in with the correct NetBIOS name?
acmecompanycom/username
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
the "no true scotch man" fallacy.
0
TL DRNot at all confident in his reflexive opinions of thingsRegistered Userregular
edited April 2017
Yep
edit: reiterating that this isn't a problem per se, more of a curiosity.
TL DR on
+2
jungleroomxIt's never too many graves, it's always not enough shovelsRegistered Userregular
edited April 2017
"WE GOT A NEW MONITOR AND NOW MY ICONS ARE ALL SMALL AND I HAVE GLAUCOMA WHY ARE THEY SO SMALL"
You know what I'm dealing with you after lunch.
I just spent 3 hours setting up the SQL reporting services for the web hub for a new bank and I need to replenish my giveafucks, which have been all wasted.
"WE GOT A NEW MONITOR AND NOW MY ICONS ARE ALL SMALL AND I HAVE GLAUCOMA WHY ARE THEY SO SMALL"
You know what I'm dealing with you after lunch.
I just spent 3 hours setting up the SQL reporting services for the web hub for a new bank and I need to replenish my giveafucks, which have been all wasted.
This is super easy. I just give them smaller desktops.
Want the icons bigger? 800x600 or some other variation for you!
Seidkona on
Mostly just huntin' monsters.
XBL:Phenyhelm - 3DS:Phenyhelm
0
RandomHajileNot actually a SnatcherThe New KremlinRegistered Userregular
"WE GOT A NEW MONITOR AND NOW MY ICONS ARE ALL SMALL AND I HAVE GLAUCOMA WHY ARE THEY SO SMALL"
You know what I'm dealing with you after lunch.
I just spent 3 hours setting up the SQL reporting services for the web hub for a new bank and I need to replenish my giveafucks, which have been all wasted.
This is super easy. I just give them smaller desktops.
Want the icons bigger? 800x600 or some other variation for you!
640x480, 16 colors, high contrast, low DPI, Extra Large icons.
no that's actually useful, give them Hot Dog Stand
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
Posts
the "no true scotch man" fallacy.
I have been trying really hard not to call them servers now, I just say "an exchange install" or "A SQL instance" or something like that, meaning it's a VM with a server OS and SQL, and that's it.
Good luck!
I find that cable modems degrade over time for whatever reason. Poor heat dissipation, maybe? I dunno.
This is household, not business, but I just replaced my Cisco DPC3008 with an ASUS CM-16 because the DPC3008 slowly went from needing a reboot once every 3-4 months to needing a reboot every month to needing a reboot every 1-2 weeks.
edit: Comcast
the "no true scotch man" fallacy.
I think it's a combination of poor heat dissapation and too many read/write cycles to a shitty memory controller. The hardware in those things is never really any good.
Wait, that doesn't make sense either. There's no implied redundancy by having your database on a separate physical machine...
But it's also likely that this guy hasn't thought through it that far.
I haven't actually even had time to talk to him today, and he's off Thursday, but I realized earlier this morning that the design he came up with would actually still have the VHDs for all the VM's on one SAN, which makes this even more absurd.
"I need to update nginx on the production server, so it's going to be offline for a few minutes. Good thing my database will still be available to all the users who can't access the site that connects to the database!"
I guess the upside is that you can still connect via ssh and run raw queries?
A lot of applications don't communicate with RESTful APIs. So internally, you might have a few web resources that go down, but the homebrewed C++ app that's doing server->client with mysql will still work if you needed to update nginx.
The primary consideration for separation was always resource utilization. Application developers want everything all to themselves and as much as you can give. Separation of roles was second but beyond a few benefits with maintenance is really one and the same as the first issue. Redundancy would be a distant third and due to the complications with implementation has always been covered as a separate topic in any install guide I've read.
the "no true scotch man" fallacy.
Yep, same with DSL modems. They make these things without fans for the sake of aesthetics, and that's a brick in my wall.
I thought we were past this.
$User can't get to $Website.
Must be a LAN problem.
the "no true scotch man" fallacy.
I'm dealing with people between the ages of 20 and 40 who haven't grasped the finer points of monitor resolution.
Why is it that one of our clients tends to have issues with, for instance, domain user authentication when using the format acmecompany\timtheory versus acmecompany.com\timtheory? Did someone just miss a step when setting up local DNS?
Bonus weirdness, when setting up an app for same client, the app's admin console demanded acmecompanycom, sans the period.
@TL DR
DNS weirdness can cause all sorts of shit in AD so I never rule that out. However, the fact that they can log in with the FQDN suggests that DNS isn't the problem here.
Are you absolutely sure that acmecompany is the correct NetBIOS-format domain name and not acmecompanycom?
Is there any possibility that both acmecompany and acmecompanycom exist as domains in the forest?
Fire up Active Directory Domains and Trusts. In most small businesses you should only see one domain (in your case, acmecompany.com). If you see two or more... well, that's interesting.
Right-click on the domain and go to Properties. Verify that the "Domain name (pre-Windows 2000)" is what you think it is.
Click on the Trusts tab. Look for any other domains you have trust relationships with.
Once you verify that all that looks in order then I would dig down into other problems.
the "no true scotch man" fallacy.
The first example is using the NetBIOS domain name. The second is using the FQDN. Both are valid in a single forest, but you can have issues when trying to use the legacy NetBIOS version across forest trusts. Of course if you've got problems with AD/DNS, that can cause all sorts of issues. But if the issue is in an application, it's most likely with its own authentication mechanism. Some things are written to only accept the NetBIOS version and they've never been updated so they mangle the username otherwise.
The old Windows NT NetBIOS version also more likely to be used because it's been around forever and it's shorter. If the applications support it, you're better off getting people to sign in with their UPN ([email protected]).
As for the third issue, I'd say that app's authentication is badly broken and just be glad it works at all.
First stop nice a quick.
Second stop I go 45 minutes over expected time - internet issues meaning I couldn't download what I needed for them, plus not having any account info needed for the firewall swap, plus the new firewall having less ports than a $45 Dlink router.
Third stop I had to install a backup system and AV. The previous AV turns out had an auto-installer agent from Solarwinds that simply reinstalled the old software and fucked with my install, took twice as long as it should have. Backup system seems to be fucked out of the box and wouldn't create a volume to store backups on.
Finally get home, multiple after hours calls come through. I also have a ticket for the morning to look at a server issue. I take a peek at it and nope, this isn't a Thursday morning job when I have shit scheduled at 10AM already and people need their servers. I've been resizing disks for the past 3+ hours now due to a host running out of space and killing email and file shares.
I always thought it was funny to see it in AD as "pre windows 2000 name" when it's been decades and whoops everyone's using it.
Also, of course, this being the fist place I've ever worked using the UPN and the netbios domain name is different from the fqdn name (CONTOSOCORP\ vs contoso.com)
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
Nice thing about UPNs is being able to tell your users that their username is the same as their email address.
This is a clickable link to my Steam Profile.
Recipient address policies ftw
the "no true scotch man" fallacy.
(Actually, this would be really easy to set up in Notes. Like, a four line script. Maybe even a field in the server config doc. Unfortunately, we don't own the internet .com for our internal domain .com, so it's kind of a moot point. I'd be better off renaming/migrating our internal domain to match our external, but that's a lot of work.)
This is a clickable link to my Steam Profile.
I am not opposed to overtime pay. As a SINK, I will take all the overtime you want to give me.
GIVE IT TO ME.
I don't understand your users. I've seen coupon apps install useless adware like DriverSupport or MindSpark garbage, but I've never seen one so bad it needed Chameleon. Where are they getting this stuff?
I don't know.
Our networking team has over 250 clients, but only about 100 of them are hosted on our servers. That means we have to be reactionary sysadmins to over 150 different banks because we quite literally cannot tell them what to do. Our biggest task is networking service insofar as to keep our own proprietary suite of software up and running so they don't have downtime. We can't monitor their traffic, set policy, or enact any changes without bank approval and, well, let's just say that when they say "we'll get back to you" they never, ever fucking do.
So, my entire networking team is essentially Kif from Futurama.
We're fighting against a current of ignorant users, part-time IT guys who know just enough to seriously break everything, third party "security" companies who don't even know how to create a service to run their programs, and small-town bank presidents who want impossible things enacted with a ridiculously short timetable.
Not to mention management that has no desire to temper expectations, developers who want us to fix their shit without them telling us how it works, and internal management for our direct team who don't have enough of a spine to call out how much bullshit it is. But I figure these latter 3 complaints are pretty ubiquitous, so just a cherry on top.
The only domain in the forest is acmecompany.com but as you suggested the pre-Windows 2000 name is acmecompanycom (no period), compared to my local network which is MSPcompany.com in ADDT and MSPcompany in the pre-Windows 2000 name.
Is this getting into the territory of 'well, best practice is _____ but at this point it isn't worth breaking things to make the change a relatively-simple network'?
The initial thing that I caught notice of was with Windows logons and OWA, not a third-party app. I can log in with acmecompany.com\timothy but not acmecompany\timothy.
The third-party app that demands what I now know to be the pre-Windows 2000 domain name is a new install of a LexisNexis product.
acmecompanycom/username
the "no true scotch man" fallacy.
edit: reiterating that this isn't a problem per se, more of a curiosity.
You know what I'm dealing with you after lunch.
I just spent 3 hours setting up the SQL reporting services for the web hub for a new bank and I need to replenish my giveafucks, which have been all wasted.
This is super easy. I just give them smaller desktops.
Want the icons bigger? 800x600 or some other variation for you!
XBL:Phenyhelm - 3DS:Phenyhelm
This is a clickable link to my Steam Profile.
no that's actually useful, give them Hot Dog Stand
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies