Re: 2 questions, 1 concerning Roaming Profiles and 1 concerning Sharing Directories
- From: "Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Mon, 19 Nov 2007 16:19:08 -0600
Inline:
--
Les Connor [SBS MVP]
"Roveer" <roveer@xxxxxxxxx> wrote in message news:bdb119a8-692b-44c5-b92d-f279e803e42c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm beginning to configure my SBS server and have come across Roaming
profiles that leads to to ask for some advice.
Our office is small, probably will be just fine within the 5 user
limit of my SBS. May eventually have to add 5 licenses, so you get
the idea.
2 of my users are "in the office" at their desks, in front of their
PC's and that is not likely to change. They never go to a different
PC, they just work on their machines. Myself and 1 other user will
likely log in from our PC's at our desk, but also from laptops in the
office on the wireless lan, and through VPN provided by our firewall/
router from numerous other owned PC's in and out of the office.
Why not forget the VPN, and use RWW to log onto your desktop computer. All of you applications are already installed, the computer has access to all the resources, your profile is already there, etc.
I am also likely to have a few gadgets that will connect, probably for
email, but who knows, maybe even authenticate to the domain. Right
now, I'm thinking blackberry, or possibly a windows CE device
eventually.
You'd want a Windows Mobile device.
Are there benefits for me to set up Roaming Profiles based on my
description above? I'm am concerned about long logins on possibly
weak wan links, but then again, internet speeds have improved so much
It isn't so much of a factor any more. I'm able to VPN and RDC from
my Sprint EVDO card and most of the time it's just zippy.
Try Remote Web Workplace instead.
But, I still would appreciate some input as to whether I should
consider Roaming Profiles for my users.
Next Question: Sharing directories
My plan is to basically share just one directory on my data volume to
all of our users. That is how we've run our environment for the past
5 years and it's not likely to change. We have a subdirectory
structure for storing all of our files that everyone is familiar with
and changing it now would wreak havoc. So, today I just Share a
directory called "Server" on my data drive, manually map a drive to it
from each workstation with "reconnect on login", I believe I renamed
it "Server" so they don't see the ugly name and everything works. Is
this basically the same strategdy for SBS? I noticed that I can put a
volume name in when sharing the directory which I believe will cut out
a step, but I want to make sure I'm doing this the right way. Is
there a way I'm supposed to get the workstations to connect to this
share? Would that be a NET USE statement in a login script? or is it
just easier to connect (the whole whopping 4 workstations) via file
manager like I am today?
It makes no difference in such a small environment. If you want to automatically map drives via login, you can extend the SBS login script that's already there, call your own, or just go and map the drives. Note you don't really need to map drives for this purpose \\servername\sharename and creating a shortcut will do.
SBS has so much functionality, but when I've got so few workstations,
I have to question whether it's easier to do things the old fashioned
way. BUT, in the same breath I want to get as much out of SBS as I
can. Looking for input here.
Finally, yeah, I snuck a 3rd question in. What's your take on user
directories? I gave them on our original network (XP machine acting
like a server), but nobody ever used them. I gave them drive U: as
user and drive M: as shared space. My thinking was if they were going
to have personal files, at least get them on a server so we can back
them up. Since they never used them, I've kept harping about not
storing files on PC's, so they have been pretty good at saving things
to the shared drive. I occasionally image their PC's so when disaster
strikes I can at least get back some of their stuff. I'm thinking of
NOT having user directories, just one more piece to worry about. They
really don't create that many files that aren't stored on the server.
Interested in your input on this one.
The users shared folders are already there, created when you run the add user wizard. In addition, if you then run the wizard to configure my documents direction, the users my documents folder structure will be automatically moved to the server. They'll remain private to the user. You can use the other share (Server, you called it) for non-private/personal documents.
Thanks,
Roveer
.
- References:
- Prev by Date: Re: Question about Sharepoint, https, passwords and exposing it all to the internet...
- Next by Date: Using a network hard drive with Backup Exec 11d
- Previous by thread: 2 questions, 1 concerning Roaming Profiles and 1 concerning Sharing Directories
- Next by thread: Question about Sharepoint, https, passwords and exposing it all to the internet...
- Index(es):
Relevant Pages
|
Loading
