deploying office 2003

0 pts.
Tags:
3Com
Altiris
Automated
Availability
Avaya
Bandwidth
Billing and customer care
Billing Support Systems
Cabling
Cisco
Computer Associates
DataCenter
Dell
Desktop management applications
Development
Enterasys
Foundry
Functional
Hardware
Hewlett-Packard
Hubs
Intel
Juniper Networks
LANDesk
Lifecycle development
Networking
Performance/Load
Routers
Software testing
Software testing tools
Switches
Systems management software
Web
I want to Look at problems in deploying office 2003 in terminal server environments and get user experiences on aspects like performance
ASKED: March 10, 2006  8:37 AM
UPDATED: March 21, 2006  2:32 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Eduado,

1. It’s nice when all terminals are the same and are recent enough to let office display all it’s little goodies with default settings. If you’re using Citrix, those little vga monitors on old systems will need console work with Citrix settings behind the scenes or attaching individual profiles to each login (blegh!!)

2. Unless you have a very dependable 100mgb/full-duplex network and fast servers, you might want to force any login to be active for a minimum amount of time to bend user habits away from “quickies.” This is because terminal servers usually instance a full environment for each login. Circa 1998, only one company offered a partially shared environment space (dll’s only) and I don’t remember who that was.

3. Go to the trouble of configuring individual (or better yet, group) profiles to limit down features that should not be needed for that class of user and turn off as many goodies as possible like picture screen savers, animated menues, etc. Usually, terminal workforces already have definite pre-defined tasks and you can model what they can access after their job descriptions.

4. I’d go with hard ip’s, not dhcp. If you lose the netbios name, you can still track down a problem without sorting through the server logs.

5. Have as much functionality served via Rumba or Reflections using mainframe screens rather than those screens’ Windows counterparts.

6. Make sure the Windows licensing is hunky-dorey on the server (unless you buy a roll-out pack of licenses, each instance’s product key must be properly registered with MicroSoft) so that any verification problems don’t bring down the whole floor.

7. A more complex arrangement is to put MS support dll’s and libraries on the client and merely execute from the server. More installation, but much faster.

HTH, :) Gene

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following