Archived from groups: microsoft.public.windowsnt.terminalserver.applications,microsoft.public.windowsnt.terminalserver.client,microsoft.public.windowsnt.terminalserver.connectivity,microsoft.public.windowsnt.terminalserver.domain,microsoft.public.windowsnt.terminalserver.setup (More info?)
Well, were at a cross-road here and I'm not sure how to handle this.
I have a dedicated 2003 Terminal Server server (Dual Xeon, 3GB RAM, 50
Device CAL), and want to move my remote office users into this box.
All of the remote users have Cable Internet connections with 3mbps
inbound and 512/768kbps outbound from their locations. The main office
has a 3mbps inbound and a 1mbps outbound connection - all test at the
full rated speed and never seem to falter.
All sites are connected to the main office via dedicated IPsec tunnel
appliances.
All sites currently have workstations that are part of the main offices
domain. They also have local USB attached printers, some have a single
serial port device, some users have MS Publisher installed, others
don't. All printers are shared on the network and listed in the
Directory.
Everyone in the company uses roaming profiles mapped to the main offices
server and their "My Documents" are also redirected to a share in the
main office - as you can imagine, this can be slow at times as users
profiles grow. The intent is to take them off their local boxes and run
them through RD to the TS in the main office so that their bandwidth
intensive apps and files are a non-issue (since the entire main office
has a gig backbone).
So, since we have a mix of Office XP and Office 2003 I tested the TS
server with installing the full Office XP suite (Outlook XP, Word,
Excel, PPT) and skilled Publisher. The intent is to remove all the
licensed installs of Office from all users machines to match the number
of users that will be accessing Office XP on the TS.
I have pointed everyone TS profiles to the same locations as their
roaming profiles - not sure if that's right or not.
I notice that anyone using Outlook XP can use Outlook XP installed on
the TS without any setup/change/error, but the Office 2003 users running
Outlook 2003 get an error when they open Outlook XP on the Terminal
Server - I can set them up with Outlook XP, but if they switch back to
their normal non-RD desktop and open Outlook 2003 it's broke and
requires it to be reset.
Everything else seems to work perfectly - although I was amazed at how
long it takes to print - it seems that anything they print while in TS
must be fully sent (complete file) back to their local computer before
it starts printing - and it's real slow. This would be the only issue we
have.
So, by questions:
Does it sound like I've got the right ideas -
1) mapping the TS profiles to the same locations as their roaming
profiles (since I need to have everything the same if they TS or just
login to the domain at the local computers in their offices).
2) Nothing I can do about the printing speed
3) Installing Office XP on the TS for all users and then uninstalling
Office XP and 2003 from their local machines to account for the same
number of licenses?
what would you do differently.
Thanks.
--
spam999free@rrohio.com
remove 999 in order to email me
Well, were at a cross-road here and I'm not sure how to handle this.
I have a dedicated 2003 Terminal Server server (Dual Xeon, 3GB RAM, 50
Device CAL), and want to move my remote office users into this box.
All of the remote users have Cable Internet connections with 3mbps
inbound and 512/768kbps outbound from their locations. The main office
has a 3mbps inbound and a 1mbps outbound connection - all test at the
full rated speed and never seem to falter.
All sites are connected to the main office via dedicated IPsec tunnel
appliances.
All sites currently have workstations that are part of the main offices
domain. They also have local USB attached printers, some have a single
serial port device, some users have MS Publisher installed, others
don't. All printers are shared on the network and listed in the
Directory.
Everyone in the company uses roaming profiles mapped to the main offices
server and their "My Documents" are also redirected to a share in the
main office - as you can imagine, this can be slow at times as users
profiles grow. The intent is to take them off their local boxes and run
them through RD to the TS in the main office so that their bandwidth
intensive apps and files are a non-issue (since the entire main office
has a gig backbone).
So, since we have a mix of Office XP and Office 2003 I tested the TS
server with installing the full Office XP suite (Outlook XP, Word,
Excel, PPT) and skilled Publisher. The intent is to remove all the
licensed installs of Office from all users machines to match the number
of users that will be accessing Office XP on the TS.
I have pointed everyone TS profiles to the same locations as their
roaming profiles - not sure if that's right or not.
I notice that anyone using Outlook XP can use Outlook XP installed on
the TS without any setup/change/error, but the Office 2003 users running
Outlook 2003 get an error when they open Outlook XP on the Terminal
Server - I can set them up with Outlook XP, but if they switch back to
their normal non-RD desktop and open Outlook 2003 it's broke and
requires it to be reset.
Everything else seems to work perfectly - although I was amazed at how
long it takes to print - it seems that anything they print while in TS
must be fully sent (complete file) back to their local computer before
it starts printing - and it's real slow. This would be the only issue we
have.
So, by questions:
Does it sound like I've got the right ideas -
1) mapping the TS profiles to the same locations as their roaming
profiles (since I need to have everything the same if they TS or just
login to the domain at the local computers in their offices).
2) Nothing I can do about the printing speed
3) Installing Office XP on the TS for all users and then uninstalling
Office XP and 2003 from their local machines to account for the same
number of licenses?
what would you do differently.
Thanks.
--
spam999free@rrohio.com
remove 999 in order to email me
Facebook
Twitter
Instagram