| Computing.Net: Over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to sign up now, it's free! |
Office 2000
|
Original Message
|
Name: Maria
Date: January 14, 2003 at 15:26:10 Pacific
Subject: Office 2000OS: Windows 2000 Advanced SerCPU/Ram: 256 |
Comment: I REALLY need help with this. I'm doing a project where it calls for different parts of Office 2000 to be available to users on the network (ex. Human Resources need Word and Excel, Accounting need Word and Access, etc.) I'm not allowed using Office XP (teacher's rule), I shouldn't need to use custom .mst files, and simply assigning permissions to the associated file .exe isn't an "ideal" alternative either. My teacher said it can simply be done assigning policies to the program, but with only one .msi file, I am completely lost and beyond frustrated. Anyone have ideas on a simple solution? The help is VERY appreciated.
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: Zoe
Date: January 14, 2003 at 16:19:59 Pacific
|
Reply: (edit)To my knowledge, .msi files are for installing the program, not for running it. You would use the .msi file in a Group Policy Object to automatically install Office on all computers within a specified group. I don't know what else .msi files might be used for. One way for users on the network to use an application that is not installed on their computer would be to use Terminal Services. Provided the application is installed on Windows 2000 Server and Terminal Services is configured, users can use a Terminal Client to log in remotely onto the server from their machine. They'll be able to run the application as if they were sitting in front of the server. This teacher doesn't sound like he's teaching much!
Report Offensive Follow Up For Removal
|

Post Locked
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
Go to Windows 2000 Forum Home