I just started working for a company who uses Citrix Metaframe 1.8 w/ sp3, and terminal services on a windows 2000 based network. I know this is a terribly vague question, but does anyone have any suggestions for common issues (like printing I see is a biggie). One thing that I am looking into is installing win2k sp3, but it looks like it might not be worth it until sp4. I don't want to louse things up in my first couple weeks on the job. Any advise/links would be greatly appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Newbie to Citrix 1
- Thread starter spiider
- Start date
Do not put sp3 on your servers if they are working fine now. We did that and now we have to reboot every night because they have problems.
Printing is one of the biggest problems. They usually fall in to two categories.
1. The printer name is not exactly like Citrix names it and so it does not map.
2. The client name of the connection, the name used when installing the Citrix client is the same as another install and when they try to connect the server gets confused as to who it is.
JON
Printing is one of the biggest problems. They usually fall in to two categories.
1. The printer name is not exactly like Citrix names it and so it does not map.
2. The client name of the connection, the name used when installing the Citrix client is the same as another install and when they try to connect the server gets confused as to who it is.
JON
-
1
- #3
CitrixEngineer
Technical User
3rd issue with printers is drivers that simply do not work with Terminal Services. If the printer has a driver that is on the list that is available from the Windows 2000 Server CD, or is on HP's list of "Certified" printers, then it will work. If it is not, then it may well not work.
The other "biggie" is applications other than MS Office (and sometimes MS Office itself!).
1. ALWAYS install applications after opening a cmd prompt and typing change user /install.
2. If the application has *.ini files, and does not work properly after installation, copy the *.ini files to the user's Windows folder in their profiles.
3. If you can, use roaming profiles. If your company already does, and you have no experience of how they work, there is a 168-page document on Microsoft's site that, apart from being a great cure from insomnia, contains all the information you need. If your company doesn't, then research them, and phase in a gradual implementation to potentially score brownie points.
Note: many people are actively against the use of roaming profiles because they can be time-consuming to setup and manage initially. Once they're up and running, however, they can help reduce troubleshooting to a matter of minutes.
I wrote a couple of "fun" FAQs on testing - although the tone is light, it is an area that I actively encourage, because it pays you, the administrator, dividends, IME. If you are thinking of deploying SP3 or 4, TEST IT FIRST!!
Hope this is helpful CitrixEngineer@yahoo.co.uk
The other "biggie" is applications other than MS Office (and sometimes MS Office itself!).
1. ALWAYS install applications after opening a cmd prompt and typing change user /install.
2. If the application has *.ini files, and does not work properly after installation, copy the *.ini files to the user's Windows folder in their profiles.
3. If you can, use roaming profiles. If your company already does, and you have no experience of how they work, there is a 168-page document on Microsoft's site that, apart from being a great cure from insomnia, contains all the information you need. If your company doesn't, then research them, and phase in a gradual implementation to potentially score brownie points.
Note: many people are actively against the use of roaming profiles because they can be time-consuming to setup and manage initially. Once they're up and running, however, they can help reduce troubleshooting to a matter of minutes.
I wrote a couple of "fun" FAQs on testing - although the tone is light, it is an area that I actively encourage, because it pays you, the administrator, dividends, IME. If you are thinking of deploying SP3 or 4, TEST IT FIRST!!
Hope this is helpful CitrixEngineer@yahoo.co.uk
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question