Slashdot Mirror


User: OriginalSpaceMan

OriginalSpaceMan's activity in the archive.

Stories
0
Comments
54
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 54

  1. Re:forcefully on Handling User Grown Machines on a Large Network? · · Score: 1

    sorry... I should read what you reply to before I reply, eh? haha, tired... I'll sleep now

  2. Re:forcefully on Handling User Grown Machines on a Large Network? · · Score: 2, Interesting

    I don't work for MS or Symantec. I do work with over 700 different end users every year. I was mearly posting an option. It's not hard to have the user login to an AD domain, then hand out a major security update. If the user is on your network, wouldn't you want them to be secure? If I owned and ran a major campus network, I would only let users join the network on my terms. This doesn't have to be done by using an Active Directory domain, but should be done and noted that it will be done if it is. One way to look at it is the physical security on a major campus. Lets say that students need to use an ID card to enter and exit a building (domain). If they don't feel they should have to use the ID card, then I don't feel they should have to attend school there. Now, lets say a major health issue came up. Wouldn't you, as a school, want to force all the students to get some sort of immunity? If you don't make them get an immunity it will be a bigger problem. That's that. I don't know... maybe my point was lost, maybe not. I'm tired and typing and that's not a good combination.

  3. Re:forcefully on Handling User Grown Machines on a Large Network? · · Score: 1

    Yes, Maybe I should have beeen more descriptive. I was initially thinking of SUS. I guess I assumed that people would know what I'm talking about. My bad...

  4. forcefully on Handling User Grown Machines on a Large Network? · · Score: 3, Insightful

    Force them to login to an Active Directory domain and hand out updates...