• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
[Fed-Talk] Re: Fed-talk Digest, Vol 6, Issue 249
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fed-Talk] Re: Fed-talk Digest, Vol 6, Issue 249


  • Subject: [Fed-Talk] Re: Fed-talk Digest, Vol 6, Issue 249
  • From: Kim Hersh <email@hidden>
  • Date: Thu, 17 Sep 2009 17:17:51 -0400

If you are looking at what you need for security reasons, it depends mainly on what the security requirements for your area are.  If I had to guess, I would say that Bluetooth would not be allowed, but you would have to check what the security plan for the network to which you would be attaching the machine.

In any case, most of the time, when security requires something like a docking station, it isn't necessarily because it requires the docking station, it's because they don't allow you to switch the monitor, keyboard, and mouse from one machine to another by unplugging and re-plugging cables.  They don't like users swapping cables on machines.

A cheaper, and likely just as acceptable setup, would be a dedicated USB keyboard and mouse (and you'll probably want the mouse for the laptop anyway - most people do like having one to supplement the finger pad), as well as a dedicated display that you could plug into.  Or, there are also two station USB KVM switches that would work.  Those would start getting close in price to the docking station, however.  But... if you plan to share the monitor, you may need one anyway.  And if you have one, you may not really need the docking station, unless you really want it.

For the most part, docking stations don't seem to be required anymore.  Everyone seemed to realize that they were just an unnecessary expense that didn't really add much other than possibly reducing the number of cables you have to hook up, and that's minimal... hardly justifies the cost.

The best way to know for sure is to check what your security people will require.  Don't forget about the network connection either.... if you are attaching to the local network, you'll likely have to ask for an additional connection, and you'll need to know if that will mean any additional hardware (whomever provides your network connection may just want to split off your current connection using a hub, and if so, will they require that you buy it, or is it already in place?)

Kim

Kimberly Cummings Hersh
Apple Team Lead
NSA Systems and Network Analysis Center (SNAC)
410-854-5192
email@hidden

On Sep 17, 2009, at 3:06 PM, email@hidden wrote:

------------------------------

Message: 5
Date: Thu, 17 Sep 2009 11:21:36 -0400
From: "Villano, Paul Mr CIV USA TRADOC" <email@hidden>
Subject: Re: [Fed-Talk] Recommended Docking Station for MacBook Pro
To: Joel Esler <email@hidden>
Cc: Apple Fed Talk <email@hidden>
Message-ID: <email@hidden">email@hidden>
Content-Type: text/plain; charset=us-ascii

Thanks.  I thought the bluetooth was a no go?  And what kind of cables do you use?  My main concern is hooking up to a (Samsung) monitor.  Though if my USB mouse and keyboard work, too, all the better.  The docking station was more for security than anything else.


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: [Fed-Talk] Re: Fed-talk Digest, Vol 6, Issue 249
      • From: Allan Marcus <email@hidden>
  • Prev by Date: Re: [Fed-Talk] Recommended Docking Station for MacBook Pro
  • Next by Date: [Fed-Talk] Army production macs on Pentagon network (Nipirnet)
  • Previous by thread: Re: [Fed-Talk] Recommended Docking Station for MacBook Pro
  • Next by thread: Re: [Fed-Talk] Re: Fed-talk Digest, Vol 6, Issue 249
  • Index(es):
    • Date
    • Thread