Deploying apps by assigned - dilema
Hey guys,
When you deploy office by assign does it have to install on first use for every component in the program? I have it set to install the whole thing but it will still keeps doing it component by component when first used. It's not a huge deal but causes 2 problems:
My outlook won't automatically configure (%username% etc) because not all the pieces are installed. It will say it can't find something to open the outlook profile. But when I add the profile myself it opens fine.
2nd, Desktop users that also have laptops which aren't used often. Say they hook it up to download the software to it. Problem is if all the components don't install and they take it with them. They try to use the program but it says the component isn't installed. It won't get installed because it's not on the network.
So anwyay, should I just publish that kind of stuff?
Thanks for all your help,
Matt
When you deploy office by assign does it have to install on first use for every component in the program? I have it set to install the whole thing but it will still keeps doing it component by component when first used. It's not a huge deal but causes 2 problems:
My outlook won't automatically configure (%username% etc) because not all the pieces are installed. It will say it can't find something to open the outlook profile. But when I add the profile myself it opens fine.
2nd, Desktop users that also have laptops which aren't used often. Say they hook it up to download the software to it. Problem is if all the components don't install and they take it with them. They try to use the program but it says the component isn't installed. It won't get installed because it's not on the network.
So anwyay, should I just publish that kind of stuff?
Thanks for all your help,
Matt
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
A-Baum
20 years ago
I thought if you used the publish method, it's worse than the assign method. Isn't published where the software is available, and the user has to go into add/remove programs to select what they want installed? I don't like that method at all.
Are you using a transform file with your Office MSI?
Are you using a transform file with your Office MSI?
Posted by:
snooper47374
20 years ago
Published isn't so bad. As long as they're not power users or administrators they can't do any harm there. All they can do is add the programs you allow.
Yeah, I am using a transform.
For the laptop users I decided I'd just publish office to them to fix my 2nd problem. That way it will install everything completely. I believe with 2003 you can assign it per user to install all after first logon. Unfortunally I'm still 2000.
I'm not sure how I will resolve my first issue yet. I need to test out our new 2003 software but my boss has yet to get me a enterprise edition cd yet. I believe you MUST use these to create a administrative install. Correct me if I'm wrong.
Yeah, I am using a transform.
For the laptop users I decided I'd just publish office to them to fix my 2nd problem. That way it will install everything completely. I believe with 2003 you can assign it per user to install all after first logon. Unfortunally I'm still 2000.
I'm not sure how I will resolve my first issue yet. I need to test out our new 2003 software but my boss has yet to get me a enterprise edition cd yet. I believe you MUST use these to create a administrative install. Correct me if I'm wrong.
Posted by:
craig16229
20 years ago
BTW, you are right about needing an Enterprise edition disc to create an admin install point. This is true with Office XP through Office 2003.
craig --<>.
craig --<>.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.