Best Practices - Multiple Users

[Erin]

I have 10 employees using Windows XP Pro SP2 who need to remotely access a
single desktop also running Windows XP Pro SP2. They could also use the
desktop on-site. We have a local server in the office and a remote server at
corporate (which users would be routed through if they are working out side
the office through VPN), neither of which I will be able to make any changes
to.

Users need to be able to run proprietary applications and save/move files to
and from this machine to their laptops. We have one administrator level user
profile setup that everyone uses as their login on that computer.



I currently have everyone set up on NetMeeting with the desktop allowing
remote desktop control. The 3 biggest issues:

1. If someone is working on the desktop locally, they lose control of the
computer if someone else logs in remotely.

2. If the desktop is re-booted, the IP address changes. (We have had issues
with some of the programs working if we use a static IP).

3. Because it is my user profile that is set up on the desktop, I am the
only one that can access My Documents outside of NetMeeting (by setting up a
share relationship across the network for the desktop C drive). Other users
must save their documents to the C root to move them from the desktop to
their laptops remotely.

I am sure there is a better way to do this. My knowledge of networking is
limited, so don't laugh at my duct tape solution! Any suggestions/best
practices would be appreciated!

Thank you!

 

[Shenan Stanley]

I have 10 employees using Windows XP Pro SP2 who need to remotely
access a single desktop also running Windows XP Pro SP2. They
could also use the desktop on-site. We have a local server in the
office and a remote server at corporate (which users would be
routed through if they are working out side the office through
VPN), neither of which I will be able to make any changes to.

Users need to be able to run proprietary applications and save/move
files to and from this machine to their laptops. We have one
administrator level user profile setup that everyone uses as their
login on that computer.



I currently have everyone set up on NetMeeting with the desktop
allowing remote desktop control. The 3 biggest issues:

1. If someone is working on the desktop locally, they lose control
of the computer if someone else logs in remotely.

2. If the desktop is re-booted, the IP address changes. (We have
had issues with some of the programs working if we use a static IP).

3. Because it is my user profile that is set up on the desktop, I
am the only one that can access My Documents outside of NetMeeting
(by setting up a share relationship across the network for the
desktop C drive). Other users must save their documents to the C
root to move them from the desktop to their laptops remotely.

I am sure there is a better way to do this. My knowledge of
networking is limited, so don't laugh at my duct tape solution!
Any suggestions/best practices would be appreciated!

1) is probably because you made them administrators.
2) Can you statically assign the IP using your DHCP server?
3) I don't know much on this one.

Why NetMeeting?

 

[Erin]

1) is probably because you made them administrators.
2) Can you statically assign the IP using your DHCP server?
3) I don't know much on this one.

Why NetMeeting?

I used NetMeeting because I knew how to make it sort of work. I am looking
for any solution - using NetMeeting or not - to make this work well.

1. it doesn't matter if they are administrators...NetMeeting is set up to
accept any incoming call and hand over control if you have the password. I
don't know how to get around this one.

2. I have no idea how to assign the IP address using DHCP server (and
honestly have no idea what that is!)

Thanks,

Erin

 

[Sooner Al [MVP]]

Can your network administrators setup Terminal Server at corporate and
access the desktop that way through the VPN and Remote Desktop? I would work
with your corporate folks on this issue.

The bottom line though is even with Remote Desktop only one user at a time,
ie. either local on the PC or remotely, will be able to work on the desktop
at any given time.

This sounds, at least to me, like the applications and database(s) should
reside on the corporate server.

By the way having all users being able to use admin permissions to access
the desktop is a HUGE security risk.

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

 

[Erin]

Thank you for your input. Unfortunately, they will not allow this to reside
on the corporate server...this is considered a "local issue" and the
applications are not supported by our IT group (even though they are part of
the biggest software agreement the company has ever contracted)!

I will set up a user name that does not have administrative rights. With
our current employees, I do not believe this is an issue, but if we have any
new hires...

Thank you for your time and thoughts.

 

[Sooner Al [MVP]]

Ok...

Here is some help with Remote Desktop with an XP host and client(s) in case
you wanted to try that versus NetMeeting. Remember NetMeeting is no longer
available if you upgrade to Vista.

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

http://support.microsoft.com/kb/280828

I think you need to ping on corporate about this issue though in the long
run...

Good luck...

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375