Can't quite figure out why MS has made this so different than normal Office Apps.
I have been deploying MS titles across networks automagically for years.

With MP, it seems to be a pain.

Anyway, I have 20 or so copies I need to push to my users. I have figured out the setup.exe /a to make the Admin Network Install, and the /qn switches to make it silent, but end users would still see the EULA and Activation Page when launching it.

I need to automate the Activation. (Like Office does, you pass the key to the MST, and it activates it in the background with no user intervention). But you can't use the Office Customization Tool with MP.

Please, someone help.

Thanks.

Hi SamCayze,

Welcome to the forums!

What version of the software? Is this your first experience with MapPoint?

I think there's a switch in the registry as to whether or not to pop up the EULA screen?

Also, the MSDN install of MapPoint (maybe also called the Corporate or OEM version, no idea what is the official name) does not require activation. I don't know if you can get ahold of a copy of that? But that version should be appropriate and easier for distribution. As long as you have proof of the licensing, it should be no problem to use.

Obviously the MapPoint desktop product is not really the same code base as the Office stuff, it's a totally different team, and although MapPoint sometimes appears under the banner of Office products (since it's work-related, and not OS or Entertainment) it's really not an Office product per se, thus the differences. Of course I'm not privy to the real story or details, that's just my take

Eric