I can't even
-
@ccwtech said in I can't even:
The tech responded by posting a link to a CISCO article covering very large enterprise environments. He's dealing with offices of 20 computers or less and can't understand why SMB would be any different than a significantly big enterprise network.
Even there, it's not for performance. You can have a million phone users and VLAN isn't for performance. You want VLANs, but for management purposes. It would be a nightmare to manage otherwise. But that's very different from performance.
-
@scottalanmiller said in I can't even:
@ccwtech said in I can't even:
The tech responded by posting a link to a CISCO article covering very large enterprise environments. He's dealing with offices of 20 computers or less and can't understand why SMB would be any different than a significantly big enterprise network.
Even there, it's not for performance. You can have a million phone users and VLAN isn't for performance. You want VLANs, but for management purposes. It would be a nightmare to manage otherwise. But that's very different from performance.
100% agree.
-
@scottalanmiller said in I can't even:
@ccwtech said in I can't even:
The tech responded by posting a link to a CISCO article covering very large enterprise environments. He's dealing with offices of 20 computers or less and can't understand why SMB would be any different than a significantly big enterprise network.
Even there, it's not for performance. You can have a million phone users and VLAN isn't for performance. You want VLANs, but for management purposes. It would be a nightmare to manage otherwise. But that's very different from performance.
Right. We have many but it's for management and security.
-
@stacksofplates said in I can't even:
@scottalanmiller said in I can't even:
@ccwtech said in I can't even:
The tech responded by posting a link to a CISCO article covering very large enterprise environments. He's dealing with offices of 20 computers or less and can't understand why SMB would be any different than a significantly big enterprise network.
Even there, it's not for performance. You can have a million phone users and VLAN isn't for performance. You want VLANs, but for management purposes. It would be a nightmare to manage otherwise. But that's very different from performance.
Right. We have many but it's for management and security.
Exactly. They certainly have their place. Generally for management, sometimes for security, but that's about it. This weird obsession with VLANs on tiny networks for "performance" is just bizarre.
-
@scottalanmiller said in I can't even:
@stacksofplates said in I can't even:
@scottalanmiller said in I can't even:
@ccwtech said in I can't even:
The tech responded by posting a link to a CISCO article covering very large enterprise environments. He's dealing with offices of 20 computers or less and can't understand why SMB would be any different than a significantly big enterprise network.
Even there, it's not for performance. You can have a million phone users and VLAN isn't for performance. You want VLANs, but for management purposes. It would be a nightmare to manage otherwise. But that's very different from performance.
Right. We have many but it's for management and security.
Exactly. They certainly have their place. Generally for management, sometimes for security, but that's about it. This weird obsession with VLANs on tiny networks for "performance" is just bizarre.
Some is also management and security together if that makes sense. Like someone accidentally brings up a "rogue" DHCP server, it will only affect that specific VLAN. It could be malicious but a lot of times it's security for yourself in case of an accident.
-
@stacksofplates said in I can't even:
@scottalanmiller said in I can't even:
@stacksofplates said in I can't even:
@scottalanmiller said in I can't even:
@ccwtech said in I can't even:
The tech responded by posting a link to a CISCO article covering very large enterprise environments. He's dealing with offices of 20 computers or less and can't understand why SMB would be any different than a significantly big enterprise network.
Even there, it's not for performance. You can have a million phone users and VLAN isn't for performance. You want VLANs, but for management purposes. It would be a nightmare to manage otherwise. But that's very different from performance.
Right. We have many but it's for management and security.
Exactly. They certainly have their place. Generally for management, sometimes for security, but that's about it. This weird obsession with VLANs on tiny networks for "performance" is just bizarre.
Some is also management and security together if that makes sense. Like someone accidentally brings up a "rogue" DHCP server, it will only affect that specific VLAN. It could be malicious but a lot of times it's security for yourself in case of an accident.
Sure. And sometimes people just want "ease of management" for some aspect of VoIP. Which isn't needed, but might "make sense" in their scenario. It can happen. But once they claim performance..... that's where we know they've lost it.
Same logic is why we don't use VLANs with SANs. We use dedicated hardware when doing that.
-
This was posted on a data recovery group I am a member of. (this didn't happen to me, but it's worth a share)
*I just had a client bring in a Surface Pro for data recovery. She said she had just come from the Microsoft store where she took it because it was no longer powering on. The tech at the Microsoft store took the Surface, smacked it really hard on the back 15 times right in front of the client, and then tried to power it on. When it did not power on he handed it back to the client and told them 'looks like you are going to need data recovery'.
It's nice to know that Microsoft is using such high tech troubleshooting techniques.
Hopefully it made you laugh as much as it did me.*
-
@ccwtech said in I can't even:
This was posted on a data recovery group I am a member of. (this didn't happen to me, but it's worth a share)
*I just had a client bring in a Surface Pro for data recovery. She said she had just come from the Microsoft store where she took it because it was no longer powering on. The tech at the Microsoft store took the Surface, smacked it really hard on the back 15 times right in front of the client, and then tried to power it on. When it did not power on he handed it back to the client and told them 'looks like you are going to need data recovery'.
It's nice to know that Microsoft is using such high tech troubleshooting techniques.
Hopefully it made you laugh as much as it did me.*
Are you sure she didn't take it to Best Buy?! wtf . . .
-
@dustinb3403 I know right!? @tech1 says she would have hit him 15 times and then said, 'looks like you're going to need a hospital'.
-
@ccwtech said in I can't even:
@dustinb3403 I know right!? @tech1 says she would have hit him 15 times and then said, 'looks like you're going to need a hospital'.
haha... right. Let me just hit you repeatedly and tell you to go find some support. . .
-
@ccwtech said in I can't even:
This was posted on a data recovery group I am a member of. (this didn't happen to me, but it's worth a share)
*I just had a client bring in a Surface Pro for data recovery. She said she had just come from the Microsoft store where she took it because it was no longer powering on. The tech at the Microsoft store took the Surface, smacked it really hard on the back 15 times right in front of the client, and then tried to power it on. When it did not power on he handed it back to the client and told them 'looks like you are going to need data recovery'.
It's nice to know that Microsoft is using such high tech troubleshooting techniques.
Hopefully it made you laugh as much as it did me.*
I've been to an MS store before. The "I can't even" should be that she set foot in the place.
-
@ccwtech said in I can't even:
This was posted on a data recovery group I am a member of. (this didn't happen to me, but it's worth a share)
*I just had a client bring in a Surface Pro for data recovery. She said she had just come from the Microsoft store where she took it because it was no longer powering on. The tech at the Microsoft store took the Surface, smacked it really hard on the back 15 times right in front of the client, and then tried to power it on. When it did not power on he handed it back to the client and told them 'looks like you are going to need data recovery'.
It's nice to know that Microsoft is using such high tech troubleshooting techniques.
Hopefully it made you laugh as much as it did me.*
That's bad man, it is incompetence at a high level. Hitting technology devices does not fix things actually makes it worst in most cases.
-
@dbeato Except for printers. Beating them always works.
-
@momurda said in I can't even:
@dbeato Except for printers. Beating them always works.
If it doesn't, you're not hitting it hard enough.
-
@dafyre said in I can't even:
@momurda said in I can't even:
@dbeato Except for printers. Beating them always works.
If it doesn't, you're not hitting it hard enough.
Obligatory.
-
@momurda said in I can't even:
@dbeato Except for printers. Beating them always works.
Of course and then you hear the paper clip sliding down.
-
Just seen this on
2 node Hyper-v 2016 cluster + san setup questionsBasically he's got (hardware already there) two servers and a SAN with SAS connectors
What's to setup a failover cluster but is talking about installing win2016 on bare metal connecting to the San then hyper v role.
Oh deer lol
-
@hobbit666 said in I can't even:
Just seen this on
2 node Hyper-v 2016 cluster + san setup questionsBasically he's got (hardware already there) two servers and a SAN with SAS connectors
What's to setup a failover cluster but is talking about installing win2016 on bare metal connecting to the San then hyper v role.
Oh deer lol
I believe I answered on that question.
-
@dbeato Yes you did, wasn't sure if that was you
-
@hobbit666 said in I can't even:
@dbeato Yes you did, wasn't sure if that was you
Yep, awake all night so might as well post
