5 replies
by bill
Ok.. first things first... a VPN, is nothing more than an extension of your existing network, just another node. So you're 'logging' in to the local machine and mapping drives based on your access. Unless you're using the VPN to support Terminal Server (TS) access or something like that.
If you're logging into the LAN/WAN via a TS connection, you'll need to establish profiles for each user on that server, because, in essence that is where they're working, and getting their 'interface' from.
I hope this gets you started, if not, give me some more detail and we can take it a bit further... sounds to me like you've already done the hardest part.
by ebob
Like bill.coupe said, you've now simply established an extension of your network. So your users cqan now connect to their applications "as usual".
Maybe that's with a TS session (good for BW conservation) or maybe with "normal" windows tools likeconnecting to network shares with UNC names or drive maps.
If it's necessary for the remote users to connect only with certain apps then they need to be setup that way. And it's not particularly relevant if they're connecting through VPN or sitting right in the office.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending