I've got the Office suite deplying from an administrative point. Word, Excel, PowerPoint and Access are all installing seperately with their own MSIs and MSTs.


All apps are installing as required, all are steamlined and running Ohotfix if needed.


The last thing I have to do before putting these applications into production is to remove the license key from the admistrative point to disable users from installing the applications themselves and also to stop users copying the installation and taking it from the building to run elsewhere.


Anyone got an idea how I do this? I've tried googling it and haven't come up with anything.


Thanks in adavnce.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Gidday Blu_Demon,

Just an idea.
Could you deploy a separate msi with just the product code, so that it's added through your deploy method. You could run an encrypted script which could populate the neccessary registry entries and embed it in it's own msi.

Cheers
Wayne
Answered 05/24/2006 by: WayneB
Blue Belt

Please log in to comment
0
OK, might try that. Maybe as an MST though.



Do you know where I cut the product/license key out of the installs I have set up already?
Answered 05/24/2006 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
Sorry mate,

Like you, I'd have to do some digging around. You might want to log the install verbosely, which might point you in the right direction.

Cheers
Wayne
Answered 05/24/2006 by: WayneB
Blue Belt

Please log in to comment
0
Ok... will try.




Have been looking around the properties of the MSI and MST but cannot find anything.... [:@]
Answered 05/24/2006 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
At a loss on this one.


Within the MST I have located the PIDKEY string. When I delete it, the app still installs without having to put in a product key.



Just cannot locate where the administrative install writes the product key when it install to the server. Have had a look at the setup.ini files and nothing in there either.
Answered 05/25/2006 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
Blue_Demon,

Have you got the MSORK installed? In there you'll find the spreadsheet with the reg info. for Office. regkey.xls.
Do a Find on "Product"(no quotes); I don't know if this is the control your after.

Cheers
Wayne
Answered 05/25/2006 by: WayneB
Blue Belt

Please log in to comment
0
No don't have MSORK installed, as far as I know.


What is it?



Anyway, have been told to re-do all these apps I have done, rather then steamline them in an administrative install, just copy the install files from the CD to the server, run the installations from there and update the Service Pack with a script.

I can put the PIDKEY in the application object, have tested this and it works OK.
Answered 05/28/2006 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
Mate,

Microsoft Office Resource Kit.

Also, if your using Wise Package Studio, it gives instructions on how to create first use settings. This creates a transform with the installation PID keys captured. You can then deploy to target PC's. Saw it there this morning when I was looking at something else. Might be useful, though never used it myself.

Cheers
Wayne
Answered 05/28/2006 by: WayneB
Blue Belt

Please log in to comment
0
Oh, sorry, ORK. Yeah, have it.[:)]

Used the CIW to create my MSTs.





The problem with the administrative install is that all users have access to the drive, so what the manager doesn't want is a situation where they can just click on the MSI and it installs, instead of the application being associated with their user accounts through their NAL window.

And also to stop users copying the MSIs and bringing them out of the office for personal use.
Answered 05/28/2006 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
Blue_Demon,

You can't place the transform into a secure directory. That way they wouldn't be able to copy the transform with the PID to run the install. I've found that to run the Office install correctly, we've had to run the setuppro.exe (which calls the setup.ini file) in the setuppro.ini we've specified where the transform and profiles folder reside. This is in a secure dir. that is limited to certain network admin.

Cheers
Wayne
Answered 05/28/2006 by: WayneB
Blue Belt

Please log in to comment
0
Can or can't place in a secure dir?
Answered 05/30/2006 by: Blue_Demon
Orange Senior Belt

Please log in to comment
0
Sorry,

It was a question, can you place the transform in a secure dir?

Cheers
Wayne
Answered 05/30/2006 by: WayneB
Blue Belt

Please log in to comment
0
Yeah, possibly.


We are looking at packaging this a different way now, so all the work I had done last week on getting everything steamlined etc is out the window!


Running the original MSIs from the server, PIDKEY into the application objct, then have a VB script that runs Ohotfix, then starts the app.

The thing is though, that it adds approx 4 mins to the first install as ohotfix has to run.


Right now I'm trying to work out what is stopping ohotfix running on a locked down users machine, probably doesn't have rights to run msiexec or something![8|]

Will keep plugging away! Appreciate your help Wayne, thanks a million.
Answered 05/30/2006 by: Blue_Demon
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity