The Most Convoluted Network EVER!
-
@tonyshowoff said:
@JaredBusch said:
You all forget that it is AJ, the thief, that stated in the other thread to just use the DNS and DHCP because it did not matter if you had CALs or not.
A thread about licensing? Please link
-
Thread has been modded to protect AJ's buddy's personal identify. Please no one copy any of the previously mentioned very private information. Identifying your own employer or yourself you are allowed to do. Please no one identify innocent third parties who aren't here to request redaction.
-
@JaredBusch said:
You all forget that it is AJ, the thief, that stated in the other thread to just use the DNS and DHCP because it did not matter if you had CALs or not.
STFU @JaredBusch.
-
Our business has two separate divisions, one is adult entertainment and the other is MSP, additionally we partly own some actual stores. I never even talk about where any of these things are located (except I've mentioned we run our adult entertainment stuff out of the Netherlands, nothing more), and I never mention names of anything, for a good reason. Primarily because I don't want any other business I'm involved with to be connected with adult entertainment, since that's off putting to people, but also just in case, because I may piss off someone online and if they know what these sites or businesses are, it could become a bad situation. If I were you AJ I'd never mention working at where you do, instead I'd say "office retailer" or something. I'll talk all day long about the technology we use, but you'll never find a post of me saying where it's used at, I'm even hesitant talking about it in PM with people, lest they bring it up, even by accident in public, though AFK/IRL in person I do mention names sometimes.
PS I'm not the one who down voted you, in fact the STFU made me laugh out loud, but full disclosure, him calling you a thief also made me lol.
-
Mixing networks is completely normal. While this IS a complex network, it does not appear to be ridiculously complex. If the primary concern is around having both Windows and UNIX in the same network, I don't see anything wrong there, at least not at this level.
Sure, with lots of analysis, we might determine cost savings or feature advantages by going down to just Windows or UNIX, but we'd need a lot more information to make that determination. Tons of companies have both. Large networks are complex things. The way an SMB works is little related to how an enterprise works.
-
@tonyshowoff said:
Our business has two separate divisions, one is adult entertainment and the other is MSP, additionally we partly own some actual stores. I never even talk about where any of these things are located (except I've mentioned we run our adult entertainment stuff out of the Netherlands, nothing more), and I never mention names of anything, for a good reason.
Heck, I don't even put my current employer on Linkedin or Facebook for good reason. Don't just my real name much of anywhere either.
-
@thecreativeone91 said:
@tonyshowoff said:
Our business has two separate divisions, one is adult entertainment and the other is MSP, additionally we partly own some actual stores. I never even talk about where any of these things are located (except I've mentioned we run our adult entertainment stuff out of the Netherlands, nothing more), and I never mention names of anything, for a good reason.
Heck, I don't even put my current employer on Linkedin or Facebook for good reason. Don't just my real name much of anywhere either.
Made the mistake of using my real name on SW, but I've been switching over to this handle everywhere else, too late to switch on SW I think.
-
@thanksajdotcom said:
@JaredBusch said:
You all forget that it is AJ, the thief, that stated in the other thread to just use the DNS and DHCP because it did not matter if you had CALs or not.
STFU @JaredBusch.
Sure thing.
-
@scottalanmiller said:
Mixing networks is completely normal. While this IS a complex network, it does not appear to be ridiculously complex. If the primary concern is around having both Windows and UNIX in the same network, I don't see anything wrong there, at least not at this level.
Sure, with lots of analysis, we might determine cost savings or feature advantages by going down to just Windows or UNIX, but we'd need a lot more information to make that determination. Tons of companies have both. Large networks are complex things. The way an SMB works is little related to how an enterprise works.
I've never worked anywhere that was solely windows. we've always have some Linux or Unix, or FreeBSD. my current temp contract is a full Linux based environment, though we are probably pretty rare.
-
It's not the fact that they mixed *nix and Windows together that concerns me. I've seen plenty of places do that. I guess I can't really explain it. Not usually at a loss for words but I am now.
-
@thanksajdotcom said:
It's not the fact that they mixed *nix and Windows together that concerns me. I've seen plenty of places do that. I guess I can't really explain it. Not usually at a loss for words but I am now.
The only difference would be they are well integrated which isn't a bad thing. Many SMBs will use windows as the primary and *Nix just kinda poorly thrown on top of it.
-
@thecreativeone91 said:
@thanksajdotcom said:
It's not the fact that they mixed *nix and Windows together that concerns me. I've seen plenty of places do that. I guess I can't really explain it. Not usually at a loss for words but I am now.
The only difference would be they are well integrated which isn't a bad thing. Many SMBs will use windows as the primary and *Nix just kinda poorly thrown on top of it.
The place this is implemented has had many issues though. I haven't personally seen the network so everything I know is second-hand, but I've been told they've had all kinds of issues with their setup.
-
@thecreativeone91 said:
@scottalanmiller said:
Mixing networks is completely normal. While this IS a complex network, it does not appear to be ridiculously complex. If the primary concern is around having both Windows and UNIX in the same network, I don't see anything wrong there, at least not at this level.
Sure, with lots of analysis, we might determine cost savings or feature advantages by going down to just Windows or UNIX, but we'd need a lot more information to make that determination. Tons of companies have both. Large networks are complex things. The way an SMB works is little related to how an enterprise works.
I've never worked anywhere that was solely windows. we've always have some Linux or Unix, or FreeBSD. my current temp contract is a full Linux based environment, though we are probably pretty rare.
I can't say that I have either. I've been in pure UNIX, but never pure Windows. Even the SMB Startup that I was at in 2000, with only twelve users, was mixed 50/50.
-
@thecreativeone91 said:
@thanksajdotcom said:
It's not the fact that they mixed *nix and Windows together that concerns me. I've seen plenty of places do that. I guess I can't really explain it. Not usually at a loss for words but I am now.
The only difference would be they are well integrated which isn't a bad thing. Many SMBs will use windows as the primary and *Nix just kinda poorly thrown on top of it.
I've seen that a lot. Sometimes it is a single integrated network, sometimes they are loosely related with almost no connection between them.
-
@thanksajdotcom said:
@thecreativeone91 said:
@thanksajdotcom said:
It's not the fact that they mixed *nix and Windows together that concerns me. I've seen plenty of places do that. I guess I can't really explain it. Not usually at a loss for words but I am now.
The only difference would be they are well integrated which isn't a bad thing. Many SMBs will use windows as the primary and *Nix just kinda poorly thrown on top of it.
The place this is implemented has had many issues though. I haven't personally seen the network so everything I know is second-hand, but I've been told they've had all kinds of issues with their setup.
Never worked in a college but, I'd say any college of decent size will have lots of issues.
-
In the mid-90s I worked at a national US ISP and all of the servers either ran SunOS (later Solaris) or UNIX 6, or briefly there were a lot of Redhat servers as well. I'm not sure what they run today, but I think it's nothing except Linux, not sure what distro though. There were absolutely no Windows servers, though there were Windows workstations for client developers and I remember NT 4 was used for the domain but later replaced with OpenLDAP, and finally the only Windows machines left were only for client development, even server development (at least when I was there) was on Sun machines. I wouldn't really consider it a mixed environment, as it was apparent to me from everyone that if they could only use Unix that's what they'd use.
So certainly as mentioned above, when it comes to single type environments, Windows-only is pretty rare. Even at Microsoft they don't have Windows only environments, hotmail used some form of Unix or Linux for a very long time. There was an article about this, but I cannot find it, it detailed how Microsoft tried switching hotmail to Exchange but it was a huge failure for a long time. I imagine now it uses it though, probably some cutdown version of it better suited for such a large environment. Microsoft, though, isn't great on scalability, except SQL Server and modern versions of .NET can do a pretty good job at it (even surprises me). SQL Server's own advancements since 2005 have been very impressive.
-
@thecreativeone91 said:
Never worked in a college but, I'd say any college of decent size will have lots of issues.
I did long ago. Some issues, not horrible. but it was the 90s.
