70-217 - publishing office 2000

Author

publishing office 2000

me? I dunno...

2002-09-15, 1:14 am

I'm trying to publish office 2000 to an OU, a search of the cdrom files shows that there are two .msi files, Data1, and MSOWC. There is also a MSOWC shown as a .cab file.

The wininstall le programme won't allow me to use either MSOWC or Data1 for the .msi file. Neither have an extension shown... why won't the installer program recognize either of these files as a .msi?

simply adding a .msi extension doesn't cut it.

jeff_j_black

2002-09-15, 8:58 am

Are you staging the install files from a network share?

For example:
Share your CD-Rom as 'installs'.

The data1.msi is the correct one to use.

Good luck.

CyberDude

2002-09-15, 12:30 pm

As they are already msi's, then there is no need to use WinStallLe. Just use the software settings in the GPO and point it to the msi file. Use the office config tool to create custom setup configs. This will also be attached to the GPO. I believe that you are even asked for this whilst setting up the GPO.

jeff_j_black

2002-09-15, 6:52 pm

Ooops!!! Yeah, I didn't even read the part where you said using winstaller!!! Just open the desired level of gpo and assign to computer; or publish or assign to user under 'software settings' 'software installation' right click 'new package' browse to msi file and set options for package deployment.

Slinky

2002-09-15, 10:31 pm

quote:
Originally posted by CyberDude
As they are already msi's, then there is no need to use WinStallLe. Just use the software settings in the GPO and point it to the msi file.

Yep. The MSOWC is the Microsoft Office Web Components. Like Jeff said the Data1.msc is the one you need to use. I've deployed Office 2000 Pro this way before and I know that it works. The only thing I couldn't figure out is how to script it to use the product key automatically. Refer to avatar.

CyberDude

2002-09-16, 4:06 am

If you use the offise config tool, you are able to enter the product kex that way.

me? I dunno...

2002-09-16, 1:59 pm

client can see dist folder through network neighbouhood, install will begin, but stall wanting a local drive to look for installation files, all this of course is irrelevant because I want to use the Veritas software instead.

I am having trouble with the DATA1.NAI file. I have tried the Veritas console but it cannot convert the NAI file to MSI giving an access denied message. I am configuring under admin account and have enabled full control to administrators/Users, and Everyone groups.

one other thing, I have also tried to create an installation package under domain group policy and get the message "cannot verify path is a network location." Actually, upon recheck, the same message appears when attempting to create a package in the test OU. this seems odd, as I can see all the files from a client. Then again, the client doesn't seem to know to look at the dc for the install files, though it does see them in network neighbourhood.

I can see C:\apps install\DATA1.MSI in windows explorer, I can see it from a client, but the group policy\software installation package cannot see it?

me? I dunno...

2002-09-16, 2:10 pm

By the way, that was the third attempt at relating my situation, the first two (lengthy) attempts both got bleeped into outer space.

I did have it to the point where the app was published to the client and I could see it in add/remove progs, but it still wouldnt install completely, just the start menu icons would install, and only after I went through add/remove, they weren't there prior. Now it is no longer showing up there either.

btw, Cyberdude, where do I find the Office Config tool? doesn't show up on a search.

me? I dunno...

2002-09-16, 8:34 pm

Does this cause problems?

I think I'm going to just dump the
DC and start over. It will be good practice and I will be able to shuffle the disk and increase the size of the boot partition.

CyberDude

2002-09-17, 1:50 am

I have found no problems using the defrag program, it is a lot btter than the one for the 95 kernel.

I still do not see why you want to create a new msi package from a tried and tested msi package?

If you read the readme file on the office CD, there is an explanation on deployment. It also says where this tool is. The name is probably different because I cannot remember it. What it does is ask you all the Q's that you normally get during an attended install. You can choose which programs to install, etc. Assigning to a computer will have it installed as soon as the computer connects to the network. Assigning it to the user will have it installed when the user logs on. Publishing to the user, will add it to the add/remaove programs list, and will also be installed by file extension activation.

I also received the massage stating that it could not find a network share, but it still works. M$ recommends using a hidden share anyway, so that only the GPO can use it, instead of all users.

me? I dunno...

2002-09-17, 2:05 am

Actually, it wasn't the defrag prog I was pointing to so much as all the bent files and lack of white space on the partition.

I thought we were supposed to learn assigning and publishing using the veritas stuff? Does office 2000 pave the way for an end run around the 3rd party installers?

Oh well, I guess I'll read the read me on the CD tomorrow, thanks

CyberDude

2002-09-17, 2:10 am

You only need to use veritas on products that do not have an msi. All M$ products are now in the msi format. If you cannot use the veritas program to create a msi for a program, then your only other choice is zap files.

Recommended deployment choices in order of preference:

Original MSI
Created MSI
ZAP

Remember with ZAP files, that you can only publish them, they will not self heal, plus anything else a msi file provides.

Also, when creating your own msi, you have to have a mchines that is clean installed with only that relevant OS that the package will be installed to.

Sponsored Links