Re: what to do with local and remote users for a SBS Network?

I've asked about CALs in a separate message--but this thread involves
scenarios much like one that I am migrating from sbs-2000 to sbs-2003, and I
need to pick between User and Device cals.

My inclination is to go with User cals--but I'd love to hear whether anyone
in this thread has a rule of thumb that they use for thinking about this
issue.

I'm seeing increasing remote usage, and portable devices, and thinking that
User makes more sense than Device, given that trend.
--

"Leythos" <void@xxxxxxxxxxx> wrote in message
news:NTAyf.14739$PY6.2733@xxxxxxxxxxxxxxxxxxxxxxxxx
> In article <O6cy0diGGHA.1124@xxxxxxxxxxxxxxxxxxxx>,
> mwport@xxxxxxxxxxxxxxxxxxx says...
>> Exchange mail is doable with either POP3 Connector or a 3rd party POP3
>> email
>> hoster (in combination with the POP3 Connector) and a free DDNS account.
>> I
>> use this setup at several sites and it works well.
>>
>> The bigger issue is with User1. Given the security problems with offsite
>> laptops (theft of the laptop, data confidentiality, HIPAA requirements,
>> or
>> company policy regarding data security), almost all of User1's
>> requirements
>> could be met with RWW and without a VPN. Even if he were in the office
>> and
>> decided to use his laptop, he could RWW (or RDP) into his desktop.
>> Everything then stays on his desktop or the SBS server at the office.
>> The
>> only time it would be a problem is if he absolutely needed (and was
>> allowed)
>> access to company data files when he did not have a suitable Internet
>> connection available.
>
> Yea, in the case of Medical I can see the concern, but this client is a
> realestate office and the User1 is in/out 50/50 and has to have their
> files at both locations.
>
> I also have to apply this type of scenario to small offices that have
> already (before my involvement) purchase 2003 Standard, not SBS2003
> Standard.... Being able to apply a single solution makes it easier to
> manage, but the SBS platform has it all hands down :)
>
> Thanks.
>
> --
>
> spam999free@xxxxxxxxxx
> remove 999 in order to email me


.

Relevant Pages

  • Re: RWW Missing a PC
    ... I have a small network with an SBS Server and 4 PCs. ... RWW has been ... own laptop, other client's servers, etc.), I can see and connect to the ... OK for his office computer. ...
    (microsoft.public.windows.server.sbs)
  • RE: laptop can connect to RWW but cannot connect to workstations o
    ... The laptop is being used by my while working in the field.. ... I used to be able to connect to any of my customer's RWW and from there ... connect to the computer or server with the problem. ... Click Services tab and select Hide All Microsoft Services and Disable ...
    (microsoft.public.windows.server.sbs)
  • Re: Setting up three laptops, should I or shouldnt I join them to SBS
    ... user (laptop for home and travel) and one user that will be their primary device, though, mostly out of the office. ... I'll have outlook setup for rpc over http, two users will use RWW to connect to their PCs at work, and the other user will eventually use RWW to connect to a terminal server client at the office. ... The only resources they may need from the laptop will be having to print at the office, though that also can be setup through http if I wanted. ...
    (microsoft.public.windows.server.sbs)
  • Re: what to do with local and remote users for a SBS Network?
    ... decided to use his laptop, he could RWW into his desktop. ... >> routers at least have some limited port blocking and I would forward ... >> I would setup User 1's Laptop with Outlook over Htttp which gives him his ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Email
    ... Make sure you have added the cert on the sbs server to your trust root authorities on the client laptop. ... Outlook over HTTP is the only way to go and you don't have to change settings between the office and home...it can connect via that method both in and out of the office. ... > Outlook from home when she takes her laptop home. ...
    (microsoft.public.windows.server.sbs)