Re: Remote User Management
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 3 Oct 2006 11:11:05 -0400
In news:FB337E5C-69D3-4E14-9C28-F7BB8662DC70@xxxxxxxxxxxxx,
Mike <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
I am working in a company that has close to fifty percent of it users
working remotely. There are not enough of these users in any one
location to warrant a Active Directory Site, and many of them work
from home.
Currently we do not have any remote computers setup as members of the
Active Directory domain that is configured. Each computer simply
participates in a local workgroup and then uses our VPN to establish
connectivity to domain resources.
For obvious reasons we would like to have all of our computers become
members of the domain.
I don't see that as obvious at all. What's your goal/justification for that
decision? What potential advantage do you see, given that you still won't be
able to manage them remotely if they're using VPN clients? I suggest you
rethink this.
I seem unable to find any whitepapers or the like that directly
addresses this issue from Microsoft or the general web. I have
searched Google web and groups, as well as Microsoft's website
extensively and I seem to be missing it.
The specific problems I don't see documentation for are:
Connectivity, many of our salesmen spend a great deal of time in
Hotels etc. They are not going to be able to logon to the VPN until
they have logged on to the local machine and established a connection
with the hotel's wireless or wired service. Some use wireless at home
and experience a similar problem, however I believe there is a way to
configure Windows to automatically logon to a known wireless network
before user logon, correct? Last some use Cingular AirCards and need
to logon in order to start Cingular's Connection Manager.
Options and features available to us, for example I see there are
Slow Link options for Group Policy objects etc. I am sure all the
information I need is documented in its respective location, however
I do not see any documentation that attacks the problem from the
remote user vector? How can we still use all the desktop management
features and what are the effects of the user being disconnected a
large percentage of the time? For example, will the users ever
receive new startup scripts, new logon scripts, and what all options
are available to us to control its behavior?
Sorry for the long post and thank you in advance for your time.
Unless these users were in remote offices with site-link VPN or leased line
connectivity to the HQ network where the DCs lived, group policy/remote
management/login scripts/updates are really not going to work as you wish.
Perhaps you should look into Terminal Services ?
.
- Follow-Ups:
- Re: Remote User Management
- From: Mike
- Re: Remote User Management
- Prev by Date: Re: Backup up DHCP
- Next by Date: Re: Backup up DHCP
- Previous by thread: Re: AD name change
- Next by thread: Re: Remote User Management
- Index(es):
Relevant Pages
|
